Bug#760102: gnome keyring & gpg agent

[Michael Biebl]

Am 05.06.2015 um 08:16 schrieb Daniel Kahn Gillmor:
> make sense?  does this work for you?  please let me know if you're
> having any trouble with it, i'm happy to help.

Seems to work ok for unlocking the keys. Haven't tried the "Save in
password manager" option yet, though.

That said, the package doesn't ship any translations apparently, and the
leading '_" in _Save, _OK and _Cancel look there is something broken
with i18n.
I think before we consider switching to pinentry-gnome3, this should be
fixed and the package should provide a basic set of translations, at
least for the more popular languages.

Regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?


signature.asc
Description: OpenPGP digital signature

Bug#787795: grub: please build rescue ISO and floppy reproducibly

[Daniel Kahn Gillmor]

Source: grub
Version: 2.02~beta2-23
Severity: wishlist
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
Control: block -1 with 787793

The ISOs (/usr/lib/grub-rescue/grub-rescue-cdrom.iso and
/usr/lib/grub-rescue/grub-rescue-floppy.iso) that are created by the
grub build process embed subtle variations in the timestamps and the
extents of each file.

This is one of the things that keeps the package from producing
byte-for-byte identical binary builds.

(see https://reproducible.debian.net/rb-pkg/unstable/amd64/grub2.html)

I think this can be fixed with a couple steps in debian/rules: sort
the files by extent, and fix the timestamps.  See some of the scripts
sketched here for example:

   https://lists.gnu.org/archive/html/bug-xorriso/2015-06/msg00013.html

However, it won't be completely reproducible until we get a newer
version of xorriso in debian so that we can "-alter_date_r c" (see
#787793, which blocks this bug).

Note that there are other parts of the package which are also
unreproducible (/usr/share/qemu/grub.bin and
usr/lib/grub-xen/grub-i386-xen.bin binaries differ in ways i have not
examined, and there are timestamps in
usr/share/info/grub-dev.info.gz).  These probably will be covered with
separate bug reports.

Regards,

   --dkg


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-1-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)


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

Bug#765541: dash: drop privileges if uid != euid

[Salvatore Bonaccorso]

Hi,

On Wed, Oct 15, 2014 at 10:23:33PM -0400, Michael Gilbert wrote:
> package: src:dash
> severity: important
> version: 0.5.7-4
> tags: security
> 
> As a hardening measure, dash should drop privileges early.  See:
> http://blog.cmpxchg8b.com/2013/08/security-debianisms.html
> http://article.gmane.org/gmane.comp.shells.dash/841

This has been done now in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1215660/comments/6

Regards,
Salvatore


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

Bug#760102: gnome keyring & gpg agent

[Daniel Kahn Gillmor]

On Fri 2015-06-05 00:36:04 -0400, Michael Biebl wrote:
> Am 05.06.2015 um 06:20 schrieb Daniel Kahn Gillmor:
>> If gnome-keyring can Depend: pinentry-gnome3 (#787786), it should be
>> able to build with --disable-gpg-agent.
>
> I just installed pinentry-gnome3 to give it a try, but apparently it
> needs further configuration to be used by gnome-keyring.
> Can you explain, how?

You need to:

 * disable gnome-keyring's gpg-agent mechanism (either by rebuilding
gnome-keyring with --disable-gpg-agent or by fiddling with
/etc/xdg/autostart/gnome-keyring-gpg.desktop) , and

 * make sure the gnupg-agent package is installed, and that gpg-agent is
running in your session (usually started by
/etc/X11/Xsession.d/90gpg-agent for gpg-agent < 2.1, or automatically
when needed for gpg2 and gpg-agent >= 2.1)

Then any gpg or gpg2 process that wants to talk to the gpg-agent will
find it.  when gpg-agent wants a passphrase, it will invoke pinentry,
which should now be provided by pinentry-gnome3.  this uses gcr for
prompting, and uses libsecret to (optionally) store passphrases with
gnome-keyring.

make sense?  does this work for you?  please let me know if you're
having any trouble with it, i'm happy to help.

   --dkg


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

Bug#787794: lifimage fails to successfully boot on hppa

[⁣ ⁣]

Package: installation-reports

Forwarded: debian-h...@lists.debian.org

Debian-installer-version: debian-7.0, debian-8.0, both are sid snapshots
uname -a: N/A
Date: Sat Jul 04 13:03:37 CET 2015
Method: netboot

Machine: HP712/100
Processor: PA7100LC
Memory: 128 MB
Root Device: SCSI, /dev/sda
Root Size/partition table: N/A
Output of lspci: N/A

Base System Installation Checklist:

Initial boot worked:[E]
Configure network HW:   [ ]
Config network: [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Create file systems:[ ]
Mount partitions:   [ ]
Install base system:[ ]
Install boot loader:[ ]
Reboot: [ ]

[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

>From images at http://ftp.debian-ports.org/debian-cd/hppa/

debian-8.0/lifimage 13.8M
debian-7.0:
lifimage 13.2M
lifimage.latest 13.2M
lifimage.old 19.1M

only lifimage.old is able to boot on a subject machine. Other bring it
into an endless "HP SDC: Transaction add failed: transaction already
queued ?" print loop. Sure the installation was still possible via
that lifimage.old with some tinkering, but how long it will be hosted,
and how long it will be suitable?

Looking at the image sizes... Perhaps something ramdisk size related?
Is it a way to fix, or what is the current workaround method for
loading other images?

Quite related ancient bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302700


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

Bug#787793: libisoburn: new upstream version 1.4.0 available

[Daniel Kahn Gillmor]

Source: libisoburn
Version: 1.3.2-1.1
Severity: wishlist
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps toolchain

libisoburn 1.4.0 is available upstream as of 2015-05-17.

This update in particular includes the following changeset that allows
for setting of ctime in the generated ISO, which is needed for being
able to create reproducible ISOs with xorriso:

 http://libburnia-project.org/changeset/5190

For reproducibility alone, the two relevant changes to apply if
libisoburn debian packaging is rebuilding the docs from the texinfo
would just be:

   
http://libburnia-project.org/changeset/5190/libisoburn/trunk/xorriso/parse_exec.c
   
http://libburnia-project.org/changeset/5190/libisoburn/trunk/xorriso/xorriso.texi

But upgrading to the newest version would avoid the need for any sort
of special patches.

Thanks for maintaining libisoburn in debian!

Regards,

--dkg


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-1-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)


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

Bug#786727: crashes with segfault when drawLineH is called

[John Millikin]

I've not been able to reproduce this on my workstation, which is running
Jessie. Installed package versions:

ghc: [7.6.3, 7.8.4, 7.10.1]
c2hs: [0.17.2]
haskell-ncurses: [0.2.7, 0.2.11]
libncursesw5-dev: [5.9+20140913-1+b1]

That stack trace posted in the OP is suspicious. It looks like drawBorder
is being called somehow, but there is no path for the posted code snippet
to reach drawBorder. This makes me believe the stack is getting corrupted.

The only change between 0.2.7 and 0.2.11 that seems related is
08137f194f66796a68bf38886d3944caf7b9d08e, which added support for
c2hs>=0.18.2 by adding ifdefs for some new pointer semantics. I believe
this change is semantically a no-op, but there might be something going on
in the FFI code that I'm not aware of.

What version of c2hs are you using? I'll try building with that to see if
it triggers the issue for me.


On Sun, May 24, 2015 at 4:00 PM, Joey Hess  wrote:

> Package: libghc-ncurses-dev
> Version: 0.2.11-1+b1
> Severity: normal
>
> This program crashes with a segfault.
>
> import UI.NCurses
> main = runCurses $ do
> w <- defaultWindow
> updateWindow w $ do
> drawLineH (Just (Glyph ' ' [])) 80
>
> This didn't used to happen; the library was working when I wrote scroll
> earlier
> this spring. Something, perrhaps the new version of C ncurses, or the
> upgrade
> from ncurses-0.2.7 to 0.2.11, or the update from ghc 7.6.3 to 7.8.4, must
> have
> broken it.
>
> FWIW, I get the same crash if I install ncurses with cabal.
>
> (gdb) bt
> #0  __memcpy_sse2_unaligned ()
> at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33
> #1  0x00415ede in ncurseszm0zi2zi11_UIziNCurses_drawBorder3_info ()
> #2  0x in ?? ()
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages libghc-ncurses-dev depends on:
> ii  ghc [libghc-transformers-dev-0.3.0.0-6458c]  7.8.4-6
> ii  libc62.19-18
> pn  libghc-base-dev-4.7.0.2-bfd89
> pn  libghc-containers-dev-0.5.5.1-d4bd8  
> ii  libghc-text-dev [libghc-text-dev-1.1.1.3-1cb5a]  1.1.1.3-2+b2
> ii  libncurses5-dev  5.9+20150516-2
> ii  libncursesw5 5.9+20150516-2
> ii  libncursesw5-dev 5.9+20150516-2
> ii  libtinfo55.9+20150516-2
>
> libghc-ncurses-dev recommends no packages.
>
> Versions of packages libghc-ncurses-dev suggests:
> ii  libghc-ncurses-doc   0.2.11-1
> pn  libghc-ncurses-prof  
>
> -- no debconf information
>
> --
> see shy jo
>

Bug#785272: mate-panel: "window list" applet is unusable on vertical panel

[Individual User]

Hi Vlad,

Sure, it will not be included upstream.
It is possible to make a Debian-specific fix for this Debian-specific bug.


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

Bug#787792: python3-usb: please push to Sid

[Alexandre Detiste]

Package: python3-usb
Version: 1.0.0~b2-1
Severity: minor

Hi,

I've been using this package for while;
can you consider pushing it to Unstable ?

This would update python-usb too of course.

Cheers,

Alexandre



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages python3-usb depends on:
ii  libusb-1.0-0  2:1.0.19-1
pn  python3:any   

python3-usb recommends no packages.

python3-usb 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

Bug#770374: ITA: socket-wrapper -- socket wrapper library

[Laszlo Boszormenyi (GCS)]

Control: retitle -1 ITA: socket-wrapper -- socket wrapper library
Control: owner -1 !

After some discussion with Jakub, I take over this package. Thanks for
all the fish!


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

Bug#787502: [Pkg-shadow-devel] Bug#787502: uidmap: newgidmap man page synopsis wrong

[Serge Hallyn]

Thanks - I've fixed that in the upstream git tree.


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

Bug#787791: xdg-utils: xdg-open "incorrect" browser update-alternatives

[Allan Wind]

Package: xdg-utils
Version: 1.1.0~rc1+git20111210-7.4
Severity: normal

Dear Maintainer,

I tried to open a link in Pidgin which was configured to use the browser
Desktop Default.  Instead of using Iceweasel as expected it opened the link in
Chrome.   Checked on update-alternatives and I have iceweasel as my preference.
Then I tried to check on xgd-settings which was unhelpful:

allan@vent:~$ xdg-settings get default-web-browser
xdg-settings: unknown desktop environment

Maybe use the same logic as xdg-open which has:

detectDE

if [ x"$DE" = x"" ]; then
DE=generic
fi

Although maybe defectDE should just return generic?  There are many copies of
this function it seems.  I run xmonad without a desktop environment.

Downloaded the Pidgin source to figure out that it calls xdg-open.  The man
page for xdg-open is unhelpful to figure out where it is getting that setting
from so I traced the script to figure out that it calls `xdg-mime query default
x-scheme-handler/http`.  The man page for xdg-mime is unhelpful to figure out
where it gets its information from, so I trace that script to finally find the
source as /usr/share//applications/defaults.list.  To me it is weird that a
configuration file lives in /usr/share.

The defaults.list file contains no references to Iceweasel, so not sure if
Iceweasel should populate that file.  It didn't, btw, when I reconfigured 
iceweasel.

I noticed that trace shows that the per-user file
$HOME/.local/share//applications/mimeapps.list.  Neither man -k 
mimeapps.list or mimeapps yield anything, so I copy this to the 
file and call it a day:

[Default Applications]
application/xhtml=iceweasel.desktop;
text/html=iceweasel.desktop;
text/xml=iceweasel.desktop;
x-scheme-handler/ftp=iceweasel.desktop;
x-scheme-handler/http=iceweasel.desktop;
x-scheme-handler/https=iceweasel.desktop;

I had to look in that file anyways to figure out what to configure, so using
xdg-mime just didn't seem worth it, now that I think about what program I could
have used.

I noticed that xgd-open sets the BROWSER variable to what seems most sensible:

BROWSER=x-www-browser:firefox:seamonkey:mozilla:epiphany:konqueror:chromium-browser:google-chrome:www-browser:links2:elinks:links:lynx:w3m

but then never used.  I already configured my system preference with
x-www-browser so xdg-open should really consult that data source.

Shouldn't xdg-mime have an easy way to query its entire database?  I would have
zero chance of guessing that I needed to configure x-scheme-handler/http, or
the rest of them.

Anyways, feel free to down-prioritize, I am probably the rare exception running
without a desktop environments, and split what would be helpful to individual
tickets.

-- System Information:
Debian Release: 8.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates')
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)

xdg-utils depends on no packages.

Versions of packages xdg-utils recommends:
pn  libfile-mimeinfo-perl  
pn  libnet-dbus-perl   
pn  libx11-protocol-perl   
ii  x11-utils  7.7+2
ii  x11-xserver-utils  7.7+3+b1

Versions of packages xdg-utils suggests:
pn  gvfs-bin  

-- no debconf information

-- 
Allan Wind
Yaxto - Runs My Business



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

Bug#760102: gnome keyring & gpg agent

[Michael Biebl]

Am 05.06.2015 um 06:20 schrieb Daniel Kahn Gillmor:
> If gnome-keyring can Depend: pinentry-gnome3 (#787786), it should be
> able to build with --disable-gpg-agent.

I just installed pinentry-gnome3 to give it a try, but apparently it
needs further configuration to be used by gnome-keyring.
Can you explain, how?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#760102: gnome keyring & gpg agent

[Daniel Kahn Gillmor]

Control: retitle 760102 gnome-keyring: please build with --disable-gpg-agent
Control: block 760102 with 787786

On Thu 2015-06-04 22:30:21 -0400, Neal H. Walfield wrote:
> At Thu, 04 Jun 2015 22:14:25 -0400, Daniel Kahn Gillmor wrote:

>> >> >   - An update to Gnome-Keyring that disables it GPG Agent proxy.
>> >> 
>> >> Maybe we need to offer them a patch.  the goal here is just to disable
>> >> gnome-keyring's gpg-agent proxy implementation by default, right?
>> >
>> > That's correct.  It should be sufficient to configure gnome keyring
>> > with --disable-gpg-agent (but I haven't tested this).
>> 
>> that would make it so that users who wanted to use gnome-keyring as the
>> gpg-agent (e.g. those who don't have smartcards, don't use gpgsm, and
>> who otherwise ignore the concerns Werner has raised about
>> gnome-keyring's incomplete gpg-agent support) would be unable to do so.
>> 
>> It's a more invasive change than just disabling the functionality as per
>> runtime defaults.
>> 
>> Then again, that might keep us from dealing with a lot of extra bug
>> reports :)
>
> I spoke with Stef (the maintainer of GNOME Keyring, cc'ed) and he
> agrees that removing the proxy is the correct way forward.
>
> The only reason that the proxy exists is to cache passwords.
> pinentry-gnome3 does exactly that in a cleaner way.  In other words:
> it makes the proxy completely redundant.
>
> A GSoC student is working on finishing the changes to GNOME Keyring
> and pinentry-gnome3 (e.g., extending GCR to deal with all of GnuPG's
> prompts).  Nevertheless, the current pinentry version already more
> complete than the proxy.

Great, this sounds like a good assessment.

I'm forwarding this info to https://bugs.debian.org/760102, which is
already asking for some resolution of this situation.

If gnome-keyring can Depend: pinentry-gnome3 (#787786), it should be
able to build with --disable-gpg-agent.

Thanks for your work on this, all the coordination.

Regards,

--dkg


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

Bug#787790: ossim: please make the build reproducible

[Juan Picca]

Source: ossim
Version: 1.8.16-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that ossim could not be built reproducibly.

The attached patch removes extra timestamps from the build system:

* avoid_overwrite_build_date.patch: avoid overwrite OSSIM_BUILD_DATE
  through TODAYS_DATE in CMakeLists.txt if OSSIM_BUILD_DATE was already
  defined.

* debian-rules.patch: modify debian/rules to set the variable
  OSSIM_BUILD_DATE in cmake command line.

Once applied, ossim can be built reproducibly in our current experimental
framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds


-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Description: Avoid overwrite build date.
 Previous to use the current date to set the variable OSSIM_BUILD_DATE check if
 it was already defined in command line.
Author: Juan Picca 
Last-Update: 2015-06-04
---
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -148,7 +148,9 @@ endif ( ZLIB_FOUND )
 #---
 # Call the OSSIM macros in OssimUtilities.cmake
 #---
-TODAYS_DATE(OSSIM_BUILD_DATE)
+if ( NOT OSSIM_BUILD_DATE )
+TODAYS_DATE(OSSIM_BUILD_DATE)
+endif()
 SET(OSSIM_SVN_REVISION_NUMBER "UNKNOWN")
 GET_SVN_REVISION()
 if ( NOT ${Project_WC_REVISION} EQUAL 0 )
diff -ruNp ossim-1.8.16/debian/rules ossim-1.8.16.new/debian/rules
--- ossim-1.8.16/debian/rules	2014-11-02 10:12:44.0 -0200
+++ ossim-1.8.16.new/debian/rules	2015-06-04 15:45:25.611943209 -0300
@@ -1,5 +1,8 @@
 #!/usr/bin/make -f
 
+LAST_CHANGE=$(shell dpkg-parsechangelog -S Date)
+BUILD_DATE=$(shell LC_ALL=C date -u "+%Y%m%d" -d "$(LAST_CHANGE)")
+
 OSSIM_VERSION=$(shell dpkg-parsechangelog|grep Version:|cut -d' ' -f2|cut -d- -f1)
 OSSIM_VERSION_TAG=$(subst .,_,$(OSSIM_VERSION))
 
@@ -21,6 +24,7 @@ endif
 # Add here any variable or target overrides you need.
 CMAKE_OPTS = \
-DCMAKE_INSTALL_PREFIX=/usr \
+   -DOSSIM_BUILD_DATE=$(BUILD_DATE) \
-DBUILD_OSSIM_FRAMEWORKS=ON \
-DBUILD_OSSIM_FREETYPE_SUPPORT=ON \
-DBUILD_OSSIM_ID_SUPPORT=ON \

Bug#787789: X windows icon gone

[積丹尼 Dan Jacobson]

Package: chromium
Version: 43.0.2357.65-1
Severity: wishlist

In icewm the chromium window icon is now just an "X".

# su - nobody
No directory, logging in with HOME=/
nobody@jidanni2:/$ HOME=/tmp chromium
[12573:12573:0605/112718:ERROR:master_preferences.cc(99)] Failed to read 
preferences from /usr/share/chromium

#that is the problem, I bet.


Home directory not accessible: Permission denied

#that is wrong too.


libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: i915
getrlimit(RLIMIT_NOFILE) failed
getrlimit(RLIMIT_NOFILE) failed
[12573:12601:0605/112817:ERROR:channel.cc(300)] RawChannel read error 
(connection broken)
[12573:12601:0605/112832:ERROR:channel.cc(300)] RawChannel read error 
(connection broken)
nobody@jidanni2:/$ HOME=/tmp firefox

Firefox is fine.


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

Bug#760474: smokeping configuration for apache2 no longer working

[Antoine Beaupré]

Control: tag 708615 pending
Control: tag 759483 pending
Control: tag 783229 pending
Control: tag 695438 pending
Control: tag 669799 pending

On 2015-04-24 03:37:46, Nagarasa Sakirnth wrote:
> Hallo
>
> I have this bug too. What's the status?

I'm working on an upload.

A.

-- 
One of the things the Web teaches us is that everything is connected
(hyperlinks) and we all should work together (standards). Too often
school teaches us that everything is separate (many different
'subjects') and that we should all work alone.
 - Aaron Swartz


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

Bug#753859: diodon: depends on libgee2 which is deprecated

[Michael Biebl]

Hi Oliver

On Mon, 25 May 2015 17:07:07 +0200 Oliver Sauder  wrote:
> I actually fixed this a couple of months ago but I couldn't find a
> sponsor for the new package.
> 
> So I have uploaded the package again to Mentors which fixes this issue.
> 
> You can find it here  resp.
> 
> 
> Could you sponsor it?

Package looked fine, so I uploaded it. Thanks Oliver!

There is just one minor nit which you may want to fix in a future upload:

W: diodon source: dep5-copyright-license-name-not-unique (paragraph at
line 80)
N:
N:This paragraph defines an already defined license.
N:
N:According to the specification, short license names are required to be
N:unique within a single copyright file.
N:
N:Refer to
N:https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for
N:details.
N:
N:Severity: normal, Certainty: possible
N:
N:Check: source-copyright, Type: source
N:


The issue here afaics, is that you are defining the LGPL-2.1+ license
twice. You should only do that once, and the simply refer to it.
See [1] as an example.

Cheers,
Michael

[1]
http://metadata.ftp-master.debian.org/changelogs/main/t/tracker/unstable_copyright

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#787788: alsa-utils: snd_seq and snd_seq_midi modules no longer loaded

[Forrest Cahoon]

Package: alsa-utils
Version: 1.0.28-1
Severity: normal

Kernel modules snd_seq and snd_seq_midi are no longer loaded at boot in Debian
unstable.

I apologize if this is the wrong package; this functionality was formerly
implemented in alsa-base, but that is a dummy package now. I believe this
continued to work for some time after the alsa-base implementation went away
though, so I think this functionality was maintained in the switch but recently
became broken.

I fixed this on my own system by creating the file /etc/modules-load.d/alsa-
seq.conf with the contents

snd_seq_midi

Since snd_seq_midi depends on snd_seq, this one line loads all the required
modules.




-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-1-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 alsa-utils depends on:
ii  kmod20-1
ii  libasound2  1.0.28-1
ii  libc6   2.19-18
ii  libncursesw55.9+20150516-2
ii  libsamplerate0  0.1.8-8
ii  libtinfo5   5.9+20150516-2
ii  lsb-base4.1+Debian13+nmu1
ii  whiptail0.52.17-1+b1

alsa-utils recommends no packages.

alsa-utils 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

Bug#783068: smokeping init script status always return false

[Antoine Beaupré]

Control: fixed -1 2.6.9-1
Control: merge 699799 783068

On 2015-04-21 10:34:27, Roman Pertl wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Package: smokeping
> Version: 2.6.8-2
>
> This affects the wheezy version of smokeping. We are running OpenVZ
> Kernel (might be relevant): 2.6.32-openvz-042stab106.4-amd64
>
> The init script of smokeping doesn't correctly detect if smokeping is
> running. Although it is running, the status command always return 3.
>
> The problem is that the pid file of smokeping is not in the standard
> location and the pid of the binary /usr/bin/smokeping cannot be found.
>
> See the attached output. I propose the attached patch which correctly
> sets the pid file when checking the status.

Hi!

Sorry for the delays.

This was already fixed in version 2.6.9-1, uploaded in july 2014 into
Debian stable (Jessie).

I don't believe we should expect this to be fixed in wheezy at this
point, so I'll just close this bug report.

Sorry!

A.

-- 
Five out of four people have a problem with fractions


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

Bug#787004: FTBFS on amd64

[Wookey]

Package: linux
Version: 4.0.4
Followup-For: Bug #787004

I just tried this in a clean unstable amd64 chroot and it does indeed fail
near the end, just as the buildd did.

This is causing linux-libc-dev multiarch skew so multiarch-built
crosstoolchains are currently unbuildable (on amd64). 

The issue is that
installer/amd64/modules/amd64/scsi-extra-modules lists i2o_block and
i2o_scsi
and installer/modules/scsi-extra-modules lists i2o_block
But the modules are not built because CONFIG_I2O_BLOCK and
CONFIG_I2o_SCSI are not set

The changelog says: "Disable i2o"

So I presume the correct fix is to stop asking to install the modules into
the scsi-extra-modules udeb (As opposed to enabling the config options).

This does indeed allow the build to complete. Patch attached.


And whilst I am here, the package doesn't build (with
dpkg-buildpackage -S ) a second time, with all these changed files
left over:
dpkg-source: info: local changes detected, the modified files are:  
 linux-4.0.4/arch/s390/include/asm/cmb.h.1  
 linux-4.0.4/drivers/dma-buf/reservation.c.1  
 linux-4.0.4/drivers/dma-buf/seqno-fence.c.1  
 linux-4.0.4/drivers/gpu/drm/i915/i915_irq.c.1  
 linux-4.0.4/drivers/scsi/constants.c.1  
 linux-4.0.4/drivers/usb/gadget/function/f_acm.c.1  
 linux-4.0.4/drivers/usb/gadget/function/f_ecm.c.1  
 linux-4.0.4/drivers/usb/gadget/function/f_obex.c.1  
 linux-4.0.4/drivers/usb/gadget/function/f_serial.c.1  
 linux-4.0.4/drivers/usb/gadget/function/f_subset.c.1  
 linux-4.0.4/include/linux/reservation.h.1  
 linux-4.0.4/kernel/sys.c.1  
 linux-4.0.4/lib/crc32.c.1  
 linux-4.0.4/sound/soc/soc-cache.c.1  
 
 Changed date and build bath in man page. 
Only in linux-4.0.4.new/arch/s390/include/asm: cmb.h.1
diff -ur linux-4.0.4/debian/changelog linux-4.0.4.new/debian/changelog
--- linux-4.0.4/debian/changelog	2015-05-26 02:30:07.0 +0100
+++ linux-4.0.4.new/debian/changelog	2015-06-05 03:13:13.936808845 +0100
@@ -1,3 +1,10 @@
+linux (4.0.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS on amd64 (Closes: #787004)
+
+ -- Wookey   Fri, 05 Jun 2015 03:11:53 +0100
+
 linux (4.0.4-1) unstable; urgency=medium
 
   * New upstream stable update:
diff -ur linux-4.0.4/debian/config.defines.dump linux-4.0.4.new/debian/config.defines.dump
diff -ur linux-4.0.4/debian/control.md5sum linux-4.0.4.new/debian/control.md5sum
diff -ur linux-4.0.4/debian/installer/amd64/modules/amd64/scsi-extra-modules linux-4.0.4.new/debian/installer/amd64/modules/amd64/scsi-extra-modules
--- linux-4.0.4/debian/installer/amd64/modules/amd64/scsi-extra-modules	2015-05-11 14:22:50.0 +0100
+++ linux-4.0.4.new/debian/installer/amd64/modules/amd64/scsi-extra-modules	2015-06-05 02:18:32.352722659 +0100
@@ -1,4 +1,2 @@
 #include 
 dpt_i2o -
-i2o_block
-i2o_scsi
diff -ur linux-4.0.4/debian/rules.gen linux-4.0.4.new/debian/rules.gen
Only in linux-4.0.4.new/drivers/dma-buf: reservation.c.1
Only in linux-4.0.4.new/drivers/dma-buf: seqno-fence.c.1
Only in linux-4.0.4.new/drivers/gpu/drm/i915: i915_irq.c.1
Only in linux-4.0.4.new/drivers/scsi: constants.c.1
Only in linux-4.0.4.new/drivers/usb/gadget/function: f_acm.c.1
Only in linux-4.0.4.new/drivers/usb/gadget/function: f_ecm.c.1
Only in linux-4.0.4.new/drivers/usb/gadget/function: f_obex.c.1
Only in linux-4.0.4.new/drivers/usb/gadget/function: f_serial.c.1
Only in linux-4.0.4.new/drivers/usb/gadget/function: f_subset.c.1
Only in linux-4.0.4.new/include/linux: reservation.h.1
Only in linux-4.0.4.new/kernel: sys.c.1
Only in linux-4.0.4.new/lib: crc32.c.1
Only in linux-4.0.4.new/sound/soc: soc-cache.c.1

Bug#787444: [Reproducible-builds] Bug#787444: help2man: support externally-supplied --date for reproducibility

[Daniel Kahn Gillmor]

On Thu 2015-06-04 21:51:37 -0400, Brendan O'Dea wrote:
> Local times, and daylight savings are just too much of a PITA.  Just
> use UTC and if builds on the first of the month are possibly different
> to the changelog, so be it.

I agree with Brendan here.

If there are no objections to the idea that we're sticking with ISO-8601
in UTC, preferably with the Z suffix (e.g. 2015-06-05T01:08:20Z) then we
just need to settle on what the right name is.

Lunar^, you'd mentioned that there had been discussions about a
preferred variable name that you might like better than SOURCEDATE.

Any preference?

Where should we document this?

  --dkg


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

Bug#787639: [pkg-gnupg-maint] Bug#787639: Bug#787639: [PATCH] pinentry_setbufferlen returns pin when already large enough

[Daniel Kahn Gillmor]

On Thu 2015-06-04 15:44:06 -0400, Werner Koch wrote:
> On Thu,  4 Jun 2015 19:54, n...@walfield.org said:
>
>> It's a pretty significant bug in that it renders the curses backend
>> completely unusable.
>
> Okay.  I'll do it tomorrow.

It would be great if we could address
https://bugs.gnupg.org/gnupg/issue1996 before the 0.9.4 release as well,
as it represents a pretty nasty regression for users of pinentry-gtk2
with passwords longer than 31 characters.

Regards,

 --dkg



signature.asc
Description: PGP signature

Bug#781640: Downgrading bug severity

[Daniele Tricoli]

Hello,

On Sunday 31 May 2015 12:00:17 Moritz Mühlenhoff wrote:
> What's the status?

Sorry for the delay! I cherry picked and adapted the patch for pyjwt
version in Jessie. I worked on this branch:
https://anonscm.debian.org/viewvc/python-modules/packages/pyjwt/branches/0.2.1/

The package build fine (also twice in a row) in a pbuilder chroot.

Luke, do you know if is there any test case for asymmetric keys
used as HMAC secrets?

I have some questions (maybe d-mentors is the right place but :
1. I have to use 0.2.1-1+deb8u1 as version, right?
2. Since there is not a CVE, I have to mention
   TEMP-0781640-F16931 in the changelog, right?
2. Can I ask to my sponsor to upload it on jessie-security?

Many thanks!

Kind regards,

-- 
 Daniele Tricoli 'Eriol'
 https://mornie.org

signature.asc
Description: This is a digitally signed message part.

Bug#787444: [Reproducible-builds] Bug#787444: help2man: support externally-supplied --date for reproducibility

[Brendan O'Dea]

On 5 June 2015 at 04:40, Ximin Luo  wrote:
> On 04/06/15 19:30, Daniel Kahn Gillmor wrote:
>> What TZ should SOURCEDATE have?  ISO8601 is capable of supplying a TZ as
>> well, so the current time could be written in a wide variety of ways
>> while meaning the same instant:
>>
>> 0 dkg@alice:~$ date '+%FT%T%z' && date -u '+%FT%T%z'
>> 2015-06-04T13:25:25-0400
>> 2015-06-04T17:25:25+
>> 0 dkg@alice:~$
>>
>> I feel like we should we always set it to UTC, so that the inbound
>> parsed offset would be +.  sound sensible?
>>
>
> I had thought about this a bit, and not yet decided the best way - hence why 
> I haven't yet written this idea up on the Debian Wiki. FWIW, here are my 
> thoughts:
>
> - Always setting it to UTC would be "simplest", but then our format wouldn't 
> be ISO8601 - we'd have to say "ISO8601 but omit the offset / ignore any 
> offset". RFC 2822 and 3339, the other formats mentioned in `man date`, also 
> include an offset.

Given that you're basically creating a standard here, you get to
mandate the format.

I would say that it must be in ISO 8601 format, in the UTC timezone,
preferably using the "Z" suffix, and if the program interprets that
date and emits it in some way then it should be also in UTC.

  2015-06-05T01:08:20Z
  2015-06-05T01:08:20+

> - It's neater to keep the TZ-offset the same as in debian/changelog. 
> Generated dates will then be consistent with debian/changelog. If 
> debian/changelog says "Mar 2015", then the generated documentation will say 
> "Mar 2015".

Local times, and daylight savings are just too much of a PITA.  Just
use UTC and if builds on the first of the month are possibly different
to the changelog, so be it.

> - However, it seems awkward to get date(1) to preserve the original offset. I 
> suppose this is an artefact of using localtime(3) as you mentioned. In 
> general the libc time stuff seems to have disastrous behaviour if you want to 
> play with time zones other than local time or UTC, and this affects some 
> other languages like python.
>
> - One can maybe hack around it with the TZ envvar, but it has a very weird 
> syntax [1], and the hack is dependent on the actual value:

The TZ syntax dates back to when all systems were in the Northern
Hemisphere, and pretty much all folks cared about was EST5EDT
(Eastern) and PST8PDT (Pacific).

> $ date -d "2015-06-04T20:18:13+0800" --iso-8601=seconds
> 2015-06-04T14:18:13+0200 # nope, my local TZ is different
>
> $ TZ="UTC+08" date -d "2015-06-04T20:18:13+0800" --iso-8601=seconds
> 2015-06-04T04:18:13-0800
>
> $ TZ="UTC-08" date -d "2015-06-04T20:18:13+0800" --iso-8601=seconds
> 2015-06-04T20:18:13+0800 # argh, TZ expects the opposite sign
>
> [1] http://www.gnu.org/software/libc/manual/html_node/TZ-Variable.html
>
> - A possible workaround is to advise people to just extract the information 
> directly out of SOURCEDATE using a regex (or strip off the last 5 chars of 
> SOURCEDATE before giving it to localtime, maybe). But such advice is extra 
> mental work for developers who may not bother reading the document that we 
> put such advice on.

Mandate input/output in UTC and give a few examples.

  export SOURCEDATE=2015-06-05T01:08:20Z

  Shell:
$ date -u -d $SOURCEDATE;
Fri Jun  5 01:08:20 UTC 2015

  Perl:

use Time::Local 'timegm';
my $sourcedate = $ENV{SOURCEDATE};
my ($year, $mon, $mday, $hour, $min, $sec) =
$sourcedate =~
/^(\d{4})-(\d\d)-(\d\d)T(\d\d):(\d\d):(\d\d)(?:Z|\+)$/;
my $d = timegm $sec, $min, $hour, $mday, $mon-1, $year;
print scalar gmtime $d;

  Python:

etc.

>>> It would be awesome for help2man to support this.
>>
>> help2man (and any other tool that accepts $SOURCEDATE) would also need
>> to ensure that it extracts the parts it wants in a TZ-independent
>> fashion as well.  (not parsing back to localtime)

I'm happy to add this.

--bod


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

Bug#787690: [pkg-gnupg-maint] Bug#787690: pinentry-gtk2: always fails with "No passphrase given"

[Daniel Kahn Gillmor]

Control: forwarded 787690 https://bugs.gnupg.org/gnupg/issue1996

On Thu 2015-06-04 21:21:58 -0400, brian m. carlson wrote:
> On Thu, Jun 04, 2015 at 08:38:27PM -0400, Daniel Kahn Gillmor wrote:
>> What's particularly weird is that this file doesn't seem to have changed
>> since 0.9.2, and i can't seem to reproduce the problem with
>> pinentry-gtk-2.  What was the last version of pinentry-gtk-2 that you
>> used that didn't have this problem?
>
> I only saw this problem yesterday (local time), as it prevented me from
> running git commit -S, so according to dpkg.log that means it first
> appeared in 0.9.3-1 or 0.9.3-2 (time in UTC):

Yep, i just ran it down to the particular upstream commit that
introduced the problem, as noted in the upstream bug above.  I'm working
on understanding the rationale for that commit, and figuring out why
it's causing this behavior.  What we're definitely seeing is that the
secmem_malloc's memset is clearing the contents of the original buffer.

Thanks for your patience as we sort this out,

--dkg


signature.asc
Description: PGP signature

Bug#787787: python-stdeb: does not understand dependencies in a pbr-based setup

[Clint Adams]

Package: python-stdeb
Version: 0.8.2-4

Perhaps dependency information can be gleaned from
pbr.packaging.parse_requirements() when appropriate.


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

Bug#758939: mayavi2: diff for NMU version 4.3.1-4.1

[Olly Betts]

Dear maintainer,

I've uploaded an NMU for mayavi2 (versioned as 4.3.1-4.1) which
reapplies the lost changes from my earlier NMU 4.3.1-3.1 to update the
package to use wxpython3.0.

Cheers,
Olly
diff -Nru mayavi2-4.3.1/debian/changelog mayavi2-4.3.1/debian/changelog
--- mayavi2-4.3.1/debian/changelog	2015-05-27 02:08:10.0 +1200
+++ mayavi2-4.3.1/debian/changelog	2015-06-05 12:44:58.0 +1200
@@ -1,3 +1,12 @@
+mayavi2 (4.3.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload, reapplying lost changes from previous NMU
+4.3.1-3.1 made with maintainer's permission.
+  * Update for wxpython3.0 (Closes: #758939):
++ New patch: wxpy3.0-compat.patch
+
+ -- Olly Betts   Fri, 05 Jun 2015 12:44:19 +1200
+
 mayavi2 (4.3.1-4) unstable; urgency=medium
 
   * Add a patch to fix python interpreter (Closes: #785627)
diff -Nru mayavi2-4.3.1/debian/control mayavi2-4.3.1/debian/control
--- mayavi2-4.3.1/debian/control	2014-03-16 17:06:34.0 +1300
+++ mayavi2-4.3.1/debian/control	2015-06-05 12:43:05.0 +1200
@@ -14,7 +14,7 @@
 Package: mayavi2
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends},
- python-traits, python-traitsui, python-wxgtk2.8, python-numpy,
+ python-traits, python-traitsui, python-wxgtk3.0, python-numpy,
  python-vtk (>= 5.4.2-5), python-pkg-resources, python-envisage,
  python-apptools (>= 4.0.0-1), libjs-jquery, python-configobj
 Suggests: python-scipy, ipython
diff -Nru mayavi2-4.3.1/debian/patches/series mayavi2-4.3.1/debian/patches/series
--- mayavi2-4.3.1/debian/patches/series	2015-05-27 02:05:52.0 +1200
+++ mayavi2-4.3.1/debian/patches/series	2015-06-05 12:42:25.0 +1200
@@ -1,3 +1,4 @@
 pyinterpreter.diff
 help.diff
 ipython.diff
+wxpy3.0-compat.patch
diff -Nru mayavi2-4.3.1/debian/patches/wxpy3.0-compat.patch mayavi2-4.3.1/debian/patches/wxpy3.0-compat.patch
--- mayavi2-4.3.1/debian/patches/wxpy3.0-compat.patch	1970-01-01 12:00:00.0 +1200
+++ mayavi2-4.3.1/debian/patches/wxpy3.0-compat.patch	2015-06-05 12:41:56.0 +1200
@@ -0,0 +1,127 @@
+Description: Fixes for wxPython 3.0
+ Retains compatibility with 2.8 - there wx.InitAllImageHandlers() is a no-op,
+ wx.HIDE_READONLY is 0, and wx.PySimpleApp() issues a deprecation warning.
+Author: Olly Betts 
+Bug-Debian: https://bugs.debian.org/758939
+Forwarded: no
+Last-Update: 2014-09-20
+
+Index: mayavi2-4.3.1/tvtk/pyface/ui/wx/init.py
+===
+--- mayavi2-4.3.1.orig/tvtk/pyface/ui/wx/init.py
 mayavi2-4.3.1/tvtk/pyface/ui/wx/init.py
+@@ -22,10 +22,6 @@ if wx.VERSION < (2, 6):
+ _app = wx.GetApp()
+ 
+ if _app is None:
+-_app = wx.PySimpleApp()
++_app = wx.App(False)
+-
+-# Before we can load any images we have to initialize wxPython's image
+-# handlers.
+-wx.InitAllImageHandlers()
+ 
+  EOF ##
+Index: mayavi2-4.3.1/tvtk/util/wx_gradient_editor.py
+===
+--- mayavi2-4.3.1.orig/tvtk/util/wx_gradient_editor.py
 mayavi2-4.3.1/tvtk/util/wx_gradient_editor.py
+@@ -392,7 +392,7 @@ class wxGradientEditorWidget(wx.Panel, G
+ (lookuptable) ``*.grad`` (gradient table for use with this program), 
+ and ``*.jpg`` (image of the gradient)
+ """
+-dlg = wx.FileDialog(self, "Save LUT to...", style=wx.SAVE)
++dlg = wx.FileDialog(self, "Save LUT to...", style=wx.FD_SAVE)
+ wildcard = "Gradient Files (.grad)|*.grad|"   \
+"All files (*.*)|*.*"
+ dlg.SetWildcard(wildcard)
+@@ -405,7 +405,7 @@ class wxGradientEditorWidget(wx.Panel, G
+ """
+ Load a ``*.grad`` lookuptable file using wxpython dialog
+ """
+-style = wx.OPEN | wx.HIDE_READONLY
++style = wx.FD_OPEN
+ dlg = wx.FileDialog(self, "Open a file", style=style)
+ wildcard = "Gradient Files (.grad)|*.grad|"   \
+"All files (*.*)|*.*"
+@@ -510,7 +510,7 @@ def main():
+ """If we had a vtk window running, update it here"""
+ print("Update Render Window")
+ 
+-app = wx.PySimpleApp()
++app = wx.App(False)
+ editor = wxGradientEditor(table,
+   on_color_table_changed,
+   colors=['rgb', 'a', 'h', 's', 'v'],
+Index: mayavi2-4.3.1/docs/source/mayavi/auto/wx_embedding.py
+===
+--- mayavi2-4.3.1.orig/docs/source/mayavi/auto/wx_embedding.py
 mayavi2-4.3.1/docs/source/mayavi/auto/wx_embedding.py
+@@ -60,7 +60,7 @@ class MainWindow(wx.Frame):
+ kind='subpanel').control
+ self.Show(True)
+ 
+-app = wx.PySimpleApp()
++app = wx.App(False)
+ frame = MainWindow(None, wx.ID_ANY)
+ app.MainLoop()
+ 
+Index: mayavi2-4.3.1/docs/source/mayavi/auto/wx_mayavi_embed_in_notebook.py
+

Bug#758939: mayavi2: diff for NMU version 4.3.1-3.1

[Olly Betts]

Control: found -1 4.3.1-4
Control: tags -1 -jessie
Control: tags -1 +squeeze

[I originally sent this before my NMU, but the BTS rejected it because
the bug was archived, so resending.]

On Tue, Oct 07, 2014 at 07:58:12PM +1300, Olly Betts wrote:
> I've uploaded an NMU for mayavi2 (versioned as 4.3.1-3.1).
> 
> This is the same diff I sent before but with the changelog
> entry tweaked.

Your upload 4.3.1-4 doesn't include the changes from my NMU 4.3.1-3.1.

Cheers,
Olly


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

Bug#787786: gnome-keyring: please introduce a dependency on pinentry-gnome3

[Daniel Kahn Gillmor]

Package: gnome-keyring
Version: 3.16.0-2
Severity: wishlist
Control: affects -1 pinentry-gnome3 gnupg-agent

pinentry 0.9.3-2 now produces a pinentry-gnome3 binary that uses gcr
for prompting and has a checkbox to enable the user to cache their
passphrase in the system keyring.

This is part of a larger project to reduce superfluous dependencies on
headless servers that use GnuPG while improving the user experience
for desktop users of GnuPG (see also https://bugs.debian.org/753163
and https://bugs.debian.org/765406).

Thanks for maintaining gnome-keyring in debian!

Regards,

--kg


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-1-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 gnome-keyring depends on:
ii  dbus-x11 1.8.18-1
ii  dconf-gsettings-backend [gsettings-backend]  0.24.0-2
ii  gcr  3.16.0-1
ii  libc62.19-18
ii  libcap-ng0   0.7.6-1
ii  libcap2-bin  1:2.24-8
ii  libdbus-1-3  1.8.18-1
ii  libgck-1-0   3.16.0-1
ii  libgcr-base-3-1  3.16.0-1
ii  libgcrypt20  1.6.3-2
ii  libglib2.0-0 2.44.1-1
ii  p11-kit  0.23.1-2

Versions of packages gnome-keyring recommends:
pn  libpam-gnome-keyring  

gnome-keyring suggests no packages.

-- debconf-show failed


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

Bug#787690: [pkg-gnupg-maint] Bug#787690: pinentry-gtk2: always fails with "No passphrase given"

[brian m. carlson]

On Thu, Jun 04, 2015 at 08:38:27PM -0400, Daniel Kahn Gillmor wrote:
> What's particularly weird is that this file doesn't seem to have changed
> since 0.9.2, and i can't seem to reproduce the problem with
> pinentry-gtk-2.  What was the last version of pinentry-gtk-2 that you
> used that didn't have this problem?

I only saw this problem yesterday (local time), as it prevented me from
running git commit -S, so according to dpkg.log that means it first
appeared in 0.9.3-1 or 0.9.3-2 (time in UTC):

  2015-06-03 01:16:34 upgrade pinentry-gtk2:amd64 0.9.2-1 0.9.3-1
  2015-06-03 01:16:34 status half-configured pinentry-gtk2:amd64 0.9.2-1
  2015-06-03 01:16:34 status unpacked pinentry-gtk2:amd64 0.9.2-1
  2015-06-03 01:16:34 status half-installed pinentry-gtk2:amd64 0.9.2-1
  2015-06-03 01:16:34 status half-installed pinentry-gtk2:amd64 0.9.2-1
  2015-06-03 01:16:34 status unpacked pinentry-gtk2:amd64 0.9.3-1
  2015-06-03 01:16:34 status unpacked pinentry-gtk2:amd64 0.9.3-1
  2015-06-04 01:37:00 upgrade pinentry-gtk2:amd64 0.9.3-1 0.9.3-2
  2015-06-04 01:37:00 status half-configured pinentry-gtk2:amd64 0.9.3-1
  2015-06-04 01:37:00 status unpacked pinentry-gtk2:amd64 0.9.3-1
  2015-06-04 01:37:00 status half-installed pinentry-gtk2:amd64 0.9.3-1
  2015-06-04 01:37:00 status half-installed pinentry-gtk2:amd64 0.9.3-1
  2015-06-04 01:37:00 status unpacked pinentry-gtk2:amd64 0.9.3-2
  2015-06-04 01:37:00 status unpacked pinentry-gtk2:amd64 0.9.3-2

I suspect it's the former, since I probably upgraded on the 3rd, and due
to gpg-agent's 86400-second passphrase caching, I wouldn't have been
prompted again until probably around 23:00 on the 3rd or 00:00 on the
4th.
-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#773361: ceph: osd dies, something corrupts journal

[Christian Balzer]

Hello,

see my thread in the Ceph ML named: 
"OSD trashed by simple reboot (Debian Jessie, systemd?)"

I believe that upgrading to 0.80.9 will fix this problem.

Christian
-- 
Christian BalzerNetwork/Systems Engineer
ch...@gol.com   Global OnLine Japan/Fusion Communications
http://www.gol.com/


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

Bug#483724: [pkg-gnupg-maint] Bug#483724: gnupg2 alternatives

[Daniel Kahn Gillmor]

On Thu 2015-06-04 20:08:08 -0400, brian m. carlson wrote:
> It would be really great if we could get gnupg2 as an alternative.  Lots
> of programs, like git, expect to use "gpg" as the binary name, and it
> would be nice not to have to have a wrapper script for all those
> programs.

We're aware of this, and we're considering how to best make a transition
like this.

I think the team is leaning at the moment toward a hard cutover, as
sketched here:

 https://wiki.debian.org/Teams/GnuPG/Transition

We'd rather not have to diagnose problems many years into the future
with different variants of gnupg acting as /usr/bin/gpg, and
/etc/alternatives seems likely to prolong that particular agony.

Anyway, be aware that this is on our plate as a team, but we don't have
an answer for you yet.

   --dkg


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

Bug#785456: Pending fixes for bugs in the fonts-ipamj-mincho package

[pkg-fonts-devel]

tag 785456 + pending
thanks

Some bugs in the fonts-ipamj-mincho package are closed in revision
1965a8ef87abb0337e903d21faa0be2092eb810b in branch 'master' by
Nobuhiro Iwamatsu

The full diff can be seen at
http://anonscm.debian.org/gitweb/?p=pkg-fonts/fonts-ipamj-mincho.git;a=commitdiff;h=1965a8e

Commit message:

Update package description (Closes: #785456)

Signed-off-by: Nobuhiro Iwamatsu 


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

Bug#725175: Any news?

[Russ Allbery]

Lars Hanke  writes:

> I ran into this issue recently and filed this bug to nslcd: #787020 and
> #766606. So it persists for more than 2 years and made it across Debian
> release. I use k5start / nslcd to authenticate to samba4 AD. I'm
> surprised that it should be such a rare scenario.

> The situation actually looks quite wiered. Retrying after login always
> succeeds. Retrying in /etc/rc.local or by cron @reboot in general never
> works. On a i686 system running Wheezy it always succeeds. So if timing
> is the root of all evil, the required delay seems to be quite long.

> Could you please try to co-operate with Arthur to hunt down and
> eventually fix the issue?

There isn't anything to hunt down -- I know what the problem is, which is
that if the initial authentication fails, k5start will exit, but it should
keep running and keep retrying.  I think this is already fixed in Git, and
just requires a new release.  However, with a job change that's been
interesting but much more time-consuming (and less focused on Kerberos)
than I had expected, I've had almost no time to work on k5start.

I still hope to get a new release out with this fix, but I don't know
when.  Sorry.  :/

-- 
Russ Allbery (r...@debian.org)   


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

Bug#787690: [pkg-gnupg-maint] Bug#787690: pinentry-gtk2: always fails with "No passphrase given"

[Daniel Kahn Gillmor]

On Thu 2015-06-04 20:27:41 -0400, brian m. carlson wrote:
> On Thu, Jun 04, 2015 at 07:59:22PM -0400, Daniel Kahn Gillmor wrote:
>> Yikes, i can confirm this.  Thanks for the report.
>> 
>> Interestingly, if i paste a string of 34 characters into pinentry-gtk-2,
>> it works fine.  It's only if i type them one at a time that the failure
>> happens.
>> 
>> Temporary workaround while i sort this out with upstream:
>> 
>>   * you can try installing pinentry-gnome3, which will use the gcr
>> message prompting, or pinentry-qt4 if you prefer the qt toolkits.
>
> I've found another temporary workaround, which is to #define MIN_SIZE to
> 32 in gtksecentry.c.  I think what's happening is that the code to
> increase the buffer size is failing somewhere.  I thought I'd mention
> that it solves the problem for me in case it's helpful for
> troubleshooting.  It should work for 0 < len(passphrase) < 64.

What's particularly weird is that this file doesn't seem to have changed
since 0.9.2, and i can't seem to reproduce the problem with
pinentry-gtk-2.  What was the last version of pinentry-gtk-2 that you
used that didn't have this problem?

 --dkg


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

Bug#787785: please add at least one (1) example of how to use this package

[積丹尼 Dan Jacobson]

Package: python-messaging
Version: 0.5.12+debian-1
Severity: wishlist

Please add at least one (1) example of how to use this package.
E.g.,
$ echo 0791889623048092040... | /no/idea/what


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

Bug#787781: [pkg-gnupg-maint] Bug#787781: gnupg-agent: broken pipe error when a program using agent is invoked by stdbuf -oL

[Daniel Kahn Gillmor]

Control: affects 787781 + pass
Control: tags + help moreinfo

On Thu 2015-06-04 19:04:53 -0400, nfb wrote:
> i have a script that uses pass [0] password manager, which on his hand
> uses gpg-agent to remember the master passphrase, as you can see.
> Also i have to filter its output, so i pipe it into another script,
> but since i want the output to be unbuffered to get a more real-time
> feedback, i tried calling it this way:
>
> stdbuf -oL pass 
>
> which buffers on a per line basis. On my x86 pc everything is fine,
> while on my arm device i get:
>
> gpg: error writing to `-': Broken pipe
> gpg: handle plaintext failed: Broken pipe
>
> but after that the script works as expected.

Is that the only difference between your arm device and your x86 device?

>From the footer in your bug report, you're using pinentry-curses on the
arm device.  is this true for x86 as well, or are you using a different
pinentry there?

on each machine, what do these show?

  readlink -f /etc/alternatives/pinentry
  grep pinentry ~/.gnupg/*.conf

> So i was wondering if any tool using gpg-agent invoked with stdbuf
> with '-oL' option gives this error. I tried using '-o0' instead of
> '-oL' as stdbuf option, and this gives no problems. I also tried
> doing some symmetric encryptions/decriptions (not involving gpg-agent)
> to make sure the issue was on the agent side, invoking every time gpg
> with stdbuf, and indeed no error is showed when the agent is not used.

I think the issue might be related to the choice of pinentry on the
different platforms, but i'm not sure.  Maybe the pass developers can
shed some light on the subject?

 --dkg


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

Bug#787690: [pkg-gnupg-maint] Bug#787690: pinentry-gtk2: always fails with "No passphrase given"

[brian m. carlson]

On Thu, Jun 04, 2015 at 07:59:22PM -0400, Daniel Kahn Gillmor wrote:
> Yikes, i can confirm this.  Thanks for the report.
> 
> Interestingly, if i paste a string of 34 characters into pinentry-gtk-2,
> it works fine.  It's only if i type them one at a time that the failure
> happens.
> 
> Temporary workaround while i sort this out with upstream:
> 
>   * you can try installing pinentry-gnome3, which will use the gcr
> message prompting, or pinentry-qt4 if you prefer the qt toolkits.

I've found another temporary workaround, which is to #define MIN_SIZE to
32 in gtksecentry.c.  I think what's happening is that the code to
increase the buffer size is failing somewhere.  I thought I'd mention
that it solves the problem for me in case it's helpful for
troubleshooting.  It should work for 0 < len(passphrase) < 64.
-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#483724: gnupg2 alternatives

[brian m. carlson]

It would be really great if we could get gnupg2 as an alternative.  Lots
of programs, like git, expect to use "gpg" as the binary name, and it
would be nice not to have to have a wrapper script for all those
programs.
-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#785585: gcc-5-doc uploaded and accepted!

[GUO Yixuan]

Hello,

I'm closing this bug as gcc-5-doc is accepted into sid.

Regards,
Yixuan


signature.asc
Description: Digital signature

Bug#787784: Subject: xserver-xorg-core: xserver crashes with sis chipset

[Stéphane Blondon]

Package: xserver-xorg-core
Version: 2:1.17.1-2
Severity: important


The xserver crashes with the latest version in testing version:
xserver-xorg-core=2:1.17.1-2 xserver-xorg-video-vesa=1:2.3.3-1+b4

It works with:
aptitude install xserver-xorg-core=2:1.16.4-1
xserver-xorg-video-vesa=1:2.3.3-1+b3
(forcing a downgrade to those versions fix the problem.)

The CPU architecure is x86 and the video chipset is a SiS.


$ grep EE /var/log/Xorg.1.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  9786.227] (EE) Failed to load module "sis" (module does not exist, 0)
[  9786.229] (EE) Failed to load module "modesetting" (module does not exist, 0)
[  9786.230] (EE) Failed to load module "fbdev" (module does not exist, 0)
[  9786.230] (EE) Failed to load module "vesa" (module does not exist, 0)
[  9786.230] (EE) No drivers available.
[  9786.230] (EE)
[  9786.230] (EE) no screens found(EE)
[  9786.231] (EE)
[  9786.231] (EE) Please also check the log file at
"/var/log/Xorg.1.log" for additional information.
[  9786.231] (EE)


$ lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 741/741GX/M741
Host (rev 03)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] AGP Port (virtual
PCI-to-PCI bridge)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL
Media IO] LPC Controller (rev 25)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2/3 SMBus controller
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE Controller
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS]
SiS7012 AC'97 Sound Controller (rev a0)
00:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1
Controller (rev 0f)
00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1
Controller (rev 0f)
00:03.2 USB controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900
PCI Fast Ethernet (rev 90)
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS]
661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter

This is the information provided by reporbug. First for the new
(bugged) version, then the previous (working) version:

1. The Bugged Version


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jun 26  2011 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2544344 May  5 00:49 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: Silicon Integrated Systems
[SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter
[1039:6330]

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 8
-rw-r--r-- 1 root root 412 Jan  8  2012 10-monitor.conf
-rw-r--r-- 1 root root 396 Dec 29  2011 10-monitor.conf~

KMS configuration files:

/etc/modprobe.d/i915-kms.conf:
  options i915 modeset=1
/etc/modprobe.d/radeon-kms.conf:
  options radeon modeset=1

Kernel version (/proc/version):
---
Linux version 3.16.0-4-686-pae (debian-ker...@lists.debian.org) (gcc
version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3
(2015-04-23)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 40560 Nov 17  2011 /var/log/Xorg.17.log
-rw-r--r-- 1 root root 40560 Nov 19  2011 /var/log/Xorg.18.log
-rw-r--r-- 1 root root 40560 Nov 19  2011 /var/log/Xorg.19.log
-rw-r--r-- 1 root root 40560 Nov 19  2011 /var/log/Xorg.20.log
-rw-r--r-- 1 root root 40560 Nov 21  2011 /var/log/Xorg.21.log
-rw-r--r-- 1 root root 40560 Nov 21  2011 /var/log/Xorg.22.log
-rw-r--r-- 1 root root 40564 Nov 21  2011 /var/log/Xorg.23.log
-rw-r--r-- 1 root root 41134 Nov 23  2011 /var/log/Xorg.24.log
-rw-r--r-- 1 root root 41126 Nov 23  2011 /var/log/Xorg.25.log
-rw-r--r-- 1 root root 41122 Nov 23  2011 /var/log/Xorg.26.log
-rw-r--r-- 1 root root 41122 Nov 24  2011 /var/log/Xorg.27.log
-rw-r--r-- 1 root root 41122 Nov 24  2011 /var/log/Xorg.28.log
-rw-r--r-- 1 root root 41126 Nov 24  2011 /var/log/Xorg.29.log
-rw-r--r-- 1 root root 41122 Nov 25  2011 /var/log/Xorg.30.log
-rw-r--r-- 1 root root 41122 Nov 25  2011 /var/log/Xorg.31.log
-rw-r--r-- 1 root root 41122 Nov 27  2011 /var/log/Xorg.32.log
-rw-r--r-- 1 root root 41126 Nov 27  2011 /var/log/Xorg.33.log
-rw-r--r-- 1 root root 41122 Nov 27  2011 /var/log/Xorg.34.log
-rw-r--r-- 1 root root 41128 Nov 28  2011 /var/log/Xorg.36.log
-rw-r--r-- 1 root root 41132 Nov 29  2011 /var/log/Xorg.37.log
-rw-r--r-- 1 root root 41140 Nov 29  2011 /var/log/Xorg.38.log
-rw-r--r-- 1 root root 41128 Nov 30  2011 /var/log/Xorg.39.log
-rw-r--r-- 1 root root 41128 Nov 30  2011 /var/log/Xorg.40.log
-rw-r--r-- 1 root root 41132 Nov 30  2011 /var/log/Xorg.41.log
-rw-r--r-- 1 root root 41126 Nov 30  2011 /var/log/Xorg.42.log
-rw-r--r-- 1 root root 41128 Dec  3  2011 /var/log/Xorg.43.log
-rw-r--r-- 1 root root 41128 Dec  4  2011 /var/log/Xorg.35.lo

Bug#787690: [pkg-gnupg-maint] Bug#787690: pinentry-gtk2: always fails with "No passphrase given"

[Daniel Kahn Gillmor]

Hi Brian--

On Thu 2015-06-04 19:22:09 -0400, brian m. carlson wrote:
> I have some more debugging information.  I've rebuilt the package with
> debugging statements and have determined that the return value from
> gtk_secure_entry_get_text (around pinentry-gtk-2.c:189) is a string
> consisting of literally 0 characters (entry line s):
>
>   want_pass: 1
>   s 0x7fc1a343ea28 (len 0)
>   passphrase_ok: 1
>   pin 0x7fc1a343e188 (len 0)
>
> So gpg-agent is correct when it says "No passphrase given".  I'm not
> clear on why this is happening.
>
> This is completely reproducible with a passphrase of 32 characters or
> more.  Apparently my passphrase is unreasonably secure.  Typing a
> passphrase of "passwordpasswordpasswordabcdefgh" (exactly 32 characters,
> but not my passphrase, of course) causes a failure, while leaving off
> the last character (resulting in 31 characters) results in a bad
> passphrase error.

Yikes, i can confirm this.  Thanks for the report.

Interestingly, if i paste a string of 34 characters into pinentry-gtk-2,
it works fine.  It's only if i type them one at a time that the failure
happens.

Temporary workaround while i sort this out with upstream:

  * you can try installing pinentry-gnome3, which will use the gcr
message prompting, or pinentry-qt4 if you prefer the qt toolkits.


Further debugging techniques, if you want, without worrying about
strings being sent to gpg or gpgsm:

 0) invoke pinentry manually from the command line, and type "getpin" at
its prompt.

 1) this should display a simplified passphrase dialog (via whatever
 mechanism you've selected).  When you've clicked "OK" or enter, it
 should echo whatever you type back in the terminal.

 2) when you're done playing with it, ctrl-d in the terminal should quit
pinentry and leave you back at the shell.

Here's a transcript from me playing with it:

0 dkg@alice:~$ pinentry-gtk-2 
OK Your orders please
getpin
OK
getpin
D 123456789012345678901234567890123
OK
getpin
ERR 83886179 canceled
0 dkg@alice:~$

That's me typing a 33-char passphrase manually into the dialog, then
pasting the passphrase, then hitting cancel, running "getpin" each time
to get a new dialog.

   --dkg


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

Bug#787783: libvirt: Please install nfs-common in the build-dep (showmount exec)

[Laurent Bigonville]

Source: libvirt
Version: 1.2.16-1.1
Severity: normal

Hi,

It seems that the configure looks for the showmount executable.

If I'm not wrong, if it is not available during the configure the
SHOWMOUNT macro is not properly replaced in
src/storage/storage_backend_fs.c

nfs-common should be installed during build time IMHO

Cheers,

Laurent Bigonville

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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


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

Bug#760941: googleapi doesn't run on Python 3

[Diane Trout]

Upstream's version 1.4.0 does work. 

Diane


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

Bug#787690: [pkg-gnupg-maint] Bug#787690: pinentry-gtk2: always fails with "No passphrase given"

[brian m. carlson]

On Wed, Jun 03, 2015 at 10:50:30PM -0400, Daniel Kahn Gillmor wrote:
> On Wed 2015-06-03 21:44:31 -0400, brian m. carlson wrote:
> > Trying to sign any file fails with the following:
> >
> >   vauxhall no % gpg2 -b foo
> >   gpg: signing failed: No passphrase given
> >   gpg: signing failed: No passphrase given
> >
> > I'm prompted using pinentry-gtk2, and whether or not I select the option
> > to integrate with the password manager, gpg produces the above error
> > message.  I've killed all existing gpg-agent and dirmngr processes, but
> > it still doesn't help.  I've also moved the gpg-agent.conf out of the
> > way, which also doesn't help.
> 
> What version of gpg2 are you running?  which version of gnupg-agent?
> I'm unable to reproduce this report with gpg2 version 2.1.4-1 (from
> debian experimental) or with 2.0.28-1 from sid.

I have some more debugging information.  I've rebuilt the package with
debugging statements and have determined that the return value from
gtk_secure_entry_get_text (around pinentry-gtk-2.c:189) is a string
consisting of literally 0 characters (entry line s):

  want_pass: 1
  s 0x7fc1a343ea28 (len 0)
  passphrase_ok: 1
  pin 0x7fc1a343e188 (len 0)

So gpg-agent is correct when it says "No passphrase given".  I'm not
clear on why this is happening.

This is completely reproducible with a passphrase of 32 characters or
more.  Apparently my passphrase is unreasonably secure.  Typing a
passphrase of "passwordpasswordpasswordabcdefgh" (exactly 32 characters,
but not my passphrase, of course) causes a failure, while leaving off
the last character (resulting in 31 characters) results in a bad
passphrase error.
-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#787782: libvirt: Please install libpolkit-gobject-1-dev during the build

[Laurent Bigonville]

Source: libvirt
Version: 1.2.16-1.1
Severity: important

Hi,

I think that libpolkit-gobject-1-dev should be installed during the
build to detect if pkcheck_supports_uid is set to true in the .pc file.

The uid support for pkcheck is available in all the version
(unstable/experimental) versions of policykit in debian but libvirt
should test if it supports it.

see:
http://anonscm.debian.org/cgit/pkg-utopia/policykit.git/tree/debian/patches/cve-2013-4288.patch

Cheers,

Laurent Bigonville

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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


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

Bug#777073: Current version doesn't seem able to factor... 1 !

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

> Hi,
> 
> On Wed, May 27, 2015 at 10:08:34PM +0200, Jerome BENOIT wrote:
>> > Yes, because I noticed that the code I pasted needs to be compiled like 
>> > this in Debian:
>> > 
>> > gcc -o test test.c -lecm -lgmp
>> > 
>> > (when run: "No factor found")
>> 
>> On my box:
>> 
>>  ldd /usr/lib/libecm.so
>> linux-vdso.so.1 =>  (0x7fff1adff000)
>> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f86edf38000)
>> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f86edbad000)
>> /lib64/ld-linux-x86-64.so.2 (0x7f86ee44a000)
>> 
>> So my understanding/guessing is that libecm brings the math library with it 
>> (or something).
> 
> Definitely ; but in one case I need to be explicit about it.
>  
>> Can you compare the config.log files ?
> 
> Uh... I'm typing the compilation lines directly, so which config.log do you 
> want me to check?
> 

I would compare the config.log as produced by the currently available gmp-ecm 
pacakge
and config.log related to Sage: the idea is to detect some differences as the 
one reported
you reported at tehn end of your last email: your working Sage builts against a 
static version
of the ECM library.


>> > 
>> > while within sage, it's:
>> > 
>> > gcc -o test test.c -I -L -lecl -lgmp -lm
>> 
>>   
>> is it a typo ?
> 
> Yes it is.

ok
> 
>> > 
>> > (when run: "1")
>> > 
>> > You'll notice that the -I and -L switch are normal, since I link against 
>> > non-system things. But why the -lm switch?
>> > 
>> > Snark on #debian-science
>> > 
>> > PS: here is a more complete version of my sample code (justifies there is 
>> > no error):
>> > #include 
>> > 
>> > int
>> > main(int argc, char *argv[])
>> > {
>> >   mpz_t n, f;
>> >   int res;
>> > 
>> >   mpz_init(n);
>> >   mpz_set_d(n, 1);
>> >   mpz_init(f);
>> >   res = ecm_factor (f, n, 100, NULL);
>> >   if (res == ECM_NO_FACTOR_FOUND)
>> > gmp_printf("No factor found\n");
>> >   else if (res == ECM_ERROR)
>> > gmp_printf("ECM_ERROR\n");
>> >   else
>> > /* factor.c says ECM_FACTOR_FOUND can be returned...
>> >  * but it doesn't exist!
>> >  */
>> > gmp_printf("%Zd\n", f);
>> >   return 0;
>> > }
>> > ECM_NO_FACTOR_FOUND
>> 
>> You can complicate it by printing errno: I get 22 when (res == 
>> ECM_NO_FACTOR_FOUND)
> 
> What is the point of printing an error number if there is no error ? I'm not 
> sure errno means anything in that case.

I was half serious half kidding: the issue looks so weird.


> 
> Since yesterday, I noticed that sage doesn't compile a dynamic version of ECM 
> : it only has a static version!

Is it the static material provided by Debian ?


 I also saw that the debian 
> libecm0 package only depends on libc6, while I need -lgmp on the command line.

I have noticed it too: it will be fixed in the coming package.

 And ldd libecm0.so doesn't link to gmp either.

This is  related to the previous issue.

 I don't know if 
> it's annoying :-/

Same in this side.

> 
> It doesn't really explain the difference yet...

What is not clear at this point: is your Sage use the ECM material from Debian 
or the one from Sage ?
I do not like the static story.

> 
> Snark on #debian-science

Thanks,
Jerome

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBAgAGBQJVcN1DAAoJEIC/w4IMSybjGYAH/2Es8ugJ6m1kHDrAtNgGRKQn
1RprMRpHrD0rM3LubnCh7fVTvcNzcfVoR9yl72HIuiYJBrYfsPyQCHdZjvIcWH41
pmDE1j90XV2d9m/v1lLmh0YIlhcvbp+pc2OqGhNGtb1PYbW9Gjf8yVKq2XeJxUq2
H3F9cfaO2NpfGacF97pIG8drO1KEM/Oinlny/TDD17D1AkPRVXvDIrg8pHlaergr
6ngpn8X31o5OF3lUl4KrXz5UMvjOiPqsm8l7ozL/vT9vdDHfRyAKyXRUnZ2cEiIc
Avy6k+NeglLeMcot8alS8a/tgOcfF5Uf8GsLbsHmZ+k3oIg6jFPI9ro/rDqxwJQ=
=R56F
-END PGP SIGNATURE-


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

Bug#787781: gnupg-agent: broken pipe error when a program using agent is invoked by stdbuf -oL

[nfb]

Package: gnupg-agent
Version: 2.0.27-2
Severity: normal

Hi,
i have a script that uses pass [0] password manager, which on his hand
uses gpg-agent to remember the master passphrase, as you can see.
Also i have to filter its output, so i pipe it into another script,
but since i want the output to be unbuffered to get a more real-time
feedback, i tried calling it this way:

stdbuf -oL pass 

which buffers on a per line basis. On my x86 pc everything is fine,
while on my arm device i get:

gpg: error writing to `-': Broken pipe
gpg: handle plaintext failed: Broken pipe

but after that the script works as expected.
So i was wondering if any tool using gpg-agent invoked with stdbuf
with '-oL' option gives this error. I tried using '-o0' instead of
'-oL' as stdbuf option, and this gives no problems. I also tried
doing some symmetric encryptions/decriptions (not involving gpg-agent)
to make sure the issue was on the agent side, invoking every time gpg
with stdbuf, and indeed no error is showed when the agent is not used.


P.S.:
I really didn't know if this issue had the requisites to be reported
as bug, so forgive me in case it's not, or let me know if more details
are needed.


[0] http://www.passwordstore.org



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armhf (armv7l)

Kernel: Linux 3.8.11 (SMP w/2 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 gnupg-agent depends on:
ii  libassuan0  2.2.1-1
ii  libc6   2.19-18
ii  libgcrypt20 1.6.3-2
ii  libgpg-error0   1.17-3
ii  libpth202.0.7-20
ii  libreadline66.3-8+b3
ii  pinentry-curses [pinentry]  0.9.2-1

Versions of packages gnupg-agent recommends:
ii  gnupg   1.4.19-3
ii  gnupg2  2.0.27-2

gnupg-agent 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

Bug#714372: libvirt: Please enable firewalld support

[Laurent Bigonville]

Package: src:libvirt
Followup-For: Bug #714372

Hi,

The following patch seems to work with and without firewalld running

Cheers,

Laurent Bigonville

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libvirt-1.2.16/debian/rules libvirt-1.2.16/debian/rules
--- libvirt-1.2.16/debian/rules	2015-06-03 08:45:18.0 +0200
+++ libvirt-1.2.16/debian/rules	2015-06-05 00:22:59.0 +0200
@@ -33,6 +33,7 @@
   WITH_SANLOCK= --with-sanlock
   WITH_INIT_SCRIPT=	--with-init-script=systemd
   WITH_SYSTEMD= --with-systemd-daemon
+  WITH_FIREWALLD  = --with-firewalld
   WITH_AUDIT  = --with-audit
   WITH_SELINUX= --with-selinux --with-secdriver-selinux --with-selinux-mount=/sys/fs/selinux
   WITH_APPARMOR   = --with-apparmor --with-secdriver-apparmor --with-apparmor-profiles
@@ -68,6 +69,7 @@
   WITH_NETCF  = --without-netcf
   WITH_INIT_SCRIPT=	--with-init-script=none
   WITH_SYSTEMD= --without-systemd-daemon
+  WITH_FIREWALLD  = --without-firewalld
   WITH_AUDIT  = --without-audit
   WITH_SELINUX= --without-selinux
   WITH_APPARMOR   = --without-apparmor
@@ -117,7 +119,7 @@
 	$(WITH_DTRACE)   \
 	$(WITH_AUDIT)\
 	--without-hal\
-	--without-firewalld  \
+	$(WITH_FIREWALLD)\
 	--without-attr
 
 DEB_BUILDDIR := $(CURDIR)/debian/build

Bug#787482: ITP: sachesi -- BlackBerry 10 device utility

[Clint Adams]

On Mon, Jun 01, 2015 at 08:50:45PM -0700, Dara Adib wrote:
> 1) Request an OpenSSL linking exception from the author.

A better alternative is to switch away from OpenSSL.


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

Bug#787780: hostname patch for musl support

[Szabolcs Nagy]

Source: hostname
Version: 3.15+nmu1
Tag: patch

The hostname tool depends on libnsl and associated headers
which prevents it from compiling on musl (and possibly on
other systems).  The observable behaviour of the tool should
not change with the attached patch on a glibc based system.
diff -Nru hostname-3.15/Makefile hostname-3.15+nmu1/Makefile
--- hostname-3.15/Makefile  2013-11-03 14:25:42.0 +
+++ hostname-3.15+nmu1/Makefile 2015-06-04 22:12:11.0 +
@@ -1,4 +1,4 @@
-CFLAGS+=-O2 -Wall
+CFLAGS+=-O2 -Wall -D_GNU_SOURCE
 
 # uncomment the following line if you want to install to a different base dir.
 #BASEDIR=/mnt/test
@@ -9,7 +9,7 @@
 OBJS=hostname.o
 
 hostname: $(OBJS)
-   $(CC) $(CFLAGS) -o $@ $(OBJS) $(LDFLAGS) -lnsl
+   $(CC) $(CFLAGS) -o $@ $(OBJS) $(LDFLAGS)
ln -fs hostname dnsdomainname
ln -fs hostname domainname
ln -fs hostname ypdomainname
diff -Nru hostname-3.15/debian/changelog hostname-3.15+nmu1/debian/changelog
--- hostname-3.15/debian/changelog  2013-11-03 14:41:12.0 +
+++ hostname-3.15+nmu1/debian/changelog 2015-06-04 22:44:17.0 +
@@ -1,3 +1,15 @@
+hostname (3.15+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fixes build on musl libc.
+  * Use _GNU_SOURCE feature test macro, instead of glibc internal __USE_GNU.
+  * Use getdomainname instead of yp_get_default_domain because it is more
+widely available and avoids the -lnsl dependency.
+  * localnisdomain is kept, even though it should be the same as localdomain,
+so the behaviour is not changed in case of an error.
+
+ -- Szabolcs Nagy   Thu, 04 Jun 2015 22:13:09 +
+
 hostname (3.15) unstable; urgency=low
 
   * Applied patch to make it possible to install binaries and man pages into
diff -Nru hostname-3.15/hostname.c hostname-3.15+nmu1/hostname.c
--- hostname-3.15/hostname.c2013-11-03 14:26:51.0 +
+++ hostname-3.15+nmu1/hostname.c   2015-06-04 22:37:59.0 +
@@ -37,13 +37,11 @@
 #include 
 #include 
 #include 
-#define __USE_GNU 1
 #include 
 #include 
 #include 
 #include 
 #include 
-#include 
 
 #define VERSION "3.15"
 
@@ -52,20 +50,19 @@
 char *progname;
 
 /*
- * Return the name of the nis default domain. This is just a wrapper for
- * yp_get_default_domain.  If something goes wrong, program exits.
+ * Return the name of the nis default domain. Same as localdomain below,
+ * but reports failure for unset domain.
  */
 char *
 localnisdomain()
 {
-   char *buf = 0;
+   /* The historical NIS limit is 1024, the limit on Linux is 64.  */
+   static char buf[1025];
int myerror = 0;
 
-   myerror = yp_get_default_domain(&buf);
-
-   /* yp_get_default_domain failed, abort. */
-   if (myerror) {
-   printf("%s: %s\n", progname, yperr_string(myerror));
+   myerror = getdomainname(buf, sizeof buf);
+   if (myerror || strcmp(buf, "(none)")) {
+   printf("%s: Local domain name not set\n", progname);
exit (1);
}
 

Bug#787779: autofs: ntfs-3g: Unknown option '-s'

[root]

Package: autofs
Version: 5.0.8-2
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

When i tried this command with mount, it's a success:
mount -t ntfs-3g /dev/sda2  /mnt/windows8

But with autofs:

automount -f -v
Starting automounter version 5.0.8, master map /etc/auto.master
using kernel protocol version 5.02
lookup(dir): dir map /etc/auto.master.d missing or not readable
lookup(file): failed to read included master map dir:/etc/auto.master.d
lookup(file): failed to read included master map auto.master
mounted indirect on /mnt with timeouts disabled
ghosting enabled
attempting to mount entry /mnt/.hidden
key ".hidden" not found in map source(s).
failed to mount /mnt/.hidden
attempting to mount entry /mnt/windows8
>> ntfs-3g: Unknown option '-s'.
>> ntfs-3g 2014.2.15AR.2 integrated FUSE 28 - Third Generation NTFS Driver
>>  Configuration type 7, XATTRS are on, POSIX ACLS are on
>> Copyright (C) 2005-2007 Yura Pakhuchiy
>> Copyright (C) 2006-2009 Szabolcs Szakacsits
>> Copyright (C) 2007-2014 Jean-Pierre Andre
>> Copyright (C) 2009 Erik Larsson
>> Usage:ntfs-3g [-o option[,...]]  
>> Options:  ro (read-only mount), windows_names, uid=, gid=,
>>   umask=, fmask=, dmask=, streams_interface=.
>>   Please see the details in the manual (type: man ntfs-3g).
>> Example: ntfs-3g /dev/sda1 /mnt/windows
>> News, support and information:  http://tuxera.com
mount(generic): failed to mount /dev/sda2 (type ntfs-3g) on /mnt/windows8
failed to mount /mnt/windows8


The exactly command in my autofs file:
windows8
-fstype=ntfs-3g,defaults,uid=1000,gid=1000,locale=fr_FR.utf8:/dev/sda2


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

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

Versions of packages autofs depends on:
ii  libc6  2.19-18
ii  libxml22.9.1+dfsg1-5
ii  multiarch-support  2.19-18
ii  ucf3.0030

Versions of packages autofs recommends:
ii  kmod18-3
ii  nfs-common  1:1.2.8-9

autofs 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

Bug#787778: O: ftjam

[Yann Dirson]

Package: wnpp
Severity: normal

ftjam is unmaintained upstream, the current release is 9 years old.
Even plain jam is more maintained (and popcon shows ten times more
users), so ftjam users should probably switch.

Nevertheless, it would not be fair to our users to just frop it, if
someone really depends on it and is willing to take over maintainance.
If noone steps in a reasonable time, we'll go the RM route...


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

Bug#787462: libfile-sync-perl: FTBFS with perl 5.22

[Dominic Hargreaves]

Control: retitle -1 libfile-sync-perl: FTBFS with perl 5.22 and eatmydata
Control: severity -1 minor

On Tue, Jun 02, 2015 at 10:44:26PM +0200, gregor herrmann wrote:
> Control: tag -1 + unreproducible
> 
> On Mon, 01 Jun 2015 20:45:02 +0100, Dominic Hargreaves wrote:
> 
> > Source: libfile-sync-perl
> > Version: 0.11-2
> > Severity: important
> > User: debian-p...@lists.debian.org
> > Usertags: perl-5.22-transition
> > 
> > This package FTBFS with perl 5.22:
> 
> Builds for me.
> Also no CPAN RT ticket and nothing with perl 5.2[12] on cpantesters.

The test in question is this:

File::Sync::fsync_fd($fd) && print 'not '; print "ok 7\n";
($! == EBADF) || print 'not '; print "ok 8\n";

thus it's not surprising that the cause is eatmydata (which
intercepts fsync calls):

(perl-exp)dom@callisto:/tmp/libfile-sync-perl-0.11$ prove -b t/02_error.t 
t/02_error.t .. ok   
All tests successful.
Files=1, Tests=8,  0 wallclock secs ( 0.03 usr  0.00 sys +  0.03 cusr  0.00 
csys =  0.06 CPU)
Result: PASS
(perl-exp)dom@callisto:/tmp/libfile-sync-perl-0.11$ eatmydata prove -b 
t/02_error.t 
t/02_error.t .. Failed 2/8 subtests 

Test Summary Report
---
t/02_error.t (Wstat: 0 Tests: 8 Failed: 2)
  Failed tests:  7-8
Files=1, Tests=8,  0 wallclock secs ( 0.03 usr  0.02 sys +  0.04 cusr  0.00 
csys =  0.09 CPU)
Result: FAIL

Retitling/downgrading accordingly. I guess it's worth keeping open
if only so that it doesn't confuse anyone else, even if it's not
really a bug in the package.

Dominic.


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

Bug#787777: release-notes: Mention debian-annou...@lists.debian.org regards release announcements

[Karl O. Pinc]

Package: release-notes
Severity: wishlist

Hello,

You may wish to mention the debian-annou...@lists.debian.org
email list (https://lists.debian.org/debian-announce/)
as a way to receive notice of new releases.

In section: 4.3. Preparing sources for APT,
in the last paragraph before section 4.3.1
the following text may be appropriate between
the 2nd to last sentence and the last sentence.

One way to receive announcements of new Debian
releases is to subscribe to the https://lists.debian.org/debian-announce/";>debian-annou...@lists.debain.org
email list.

Regards,
Karl

-- System Information:
Debian Release: 7.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.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


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

Bug#787776: regression: ssh-add loses comments on keys

[Jasper Wallace]

Package: ssh
Version: 1:6.7p1-5
Severity: important
Tags: upstream

Dear Maintainer,

When trying to use ssh-agent-filter or ssh-add -c it's very handy to have
meaningfull comments on sshkeys so you can see which key is being used for
what.

Unfortunatly openssh 6.7 introduced a bug where all key comments end up as
"w/o comment", this is fixed in openssh 6.8:

https://bugzilla.mindrot.org/show_bug.cgi?id=2306

with this commit:

https://github.com/openssh/openssh-portable/commit/1195f4cb07ef4b0405c839293c38600b3e9bdb46

(I tagged this with upstream, but i don't know if thats the correct way to
use that tag, sorry if it's wrong!).

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

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

Versions of packages ssh depends on:
ii  dpkg1.17.25
ii  openssh-client  1:6.7p1-5
ii  openssh-server  1:6.7p1-5

ssh recommends no packages.

ssh 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

Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

[nusenu]

>> systemd version is on both (fresh and upgraded) systems 215-17, what
>> else should I check?
> 
> Eg. diff the list if installed packages you get via dpkg
> --get-selections and look for suspicouos diffs.

The upgraded system has sysvinit installed, the fresh one doesn't.
Both have systemd-sysv.

kernel matches;
3.16.0-4-amd64: 3.16.7-ckt9-3~deb8u1


> Local modifications, like custom fstab entries which override cgroupfs
> settings, stuff like that.

fstab looks common (no special changes)


> Can you provide steps how to reproduce the problem

Ok, I'll try to install a VM with an old debian -> upgrade -> test


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

Bug#787774: RFP: libjs-openpgp -- OpenPGP JavaScript Implementation

[W. Martin Borgert]

Package: wnpp
Severity: wishlist

Package name: libjs-openpgp
Version : v0.10.1
Upstream Author : OpenPGP Development Team 
URL : http://openpgpjs.org/
License : LGPL3+
Programming Lang: JavaScript
Description : OpenPGP JavaScript Implementation

>From the web page:

"This project aims to provide an Open Source OpenPGP library in
JavaScript so it can be used on virtually every device. Instead
of other implementations that are aimed at using native code,
OpenPGP.js is meant to bypass this requirement (i.e. people will
not have to install gpg on their machines in order to use the
library). The idea is to implement all the needed OpenPGP
functionality in a JavaScript library that can be reused in other
projects that provide browser extensions or server applications.
It should allow you to sign, encrypt, decrypt, and verify any
kind of text - in particular e-mails - as well as managing keys."


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

Bug#787775: libxml-easy-perl: FTBFS with perl 5.22 (Module::Build)

[Dominic Hargreaves]

Source: libxml-easy-perl
Version: 0.009-2
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition

This package FTBFS with perl 5.22, since Module::Build has been
removed from perl core:

perl Build.PL --installdirs vendor --config "optimize=-g -O2 -fstack-pro
tector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2" --config "ld
=i586-linux-gnu-gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-secu
rity -Wl,-z,relro"
Can't locate Module/Build.pm in @INC (you may need to install the Module::Build 
module) (@INC contains: /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.22.0 /usr
/local/share/perl/5.22.0 /usr/lib/i386-linux-gnu/perl5/5.22 /usr/share/perl5 
/usr/lib/i386-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl 
/usr/lib/i386-linux-gnu/perl-base .) at Build.PL line 5.
BEGIN failed--compilation aborted at Build.PL line 5.

The fix is to add a build dependency on libmodule-build-perl.

This bug will become release critical nearer the time of the perl 5.22
migration.

Cheers,
Dominic.


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

Bug#787773: Samba 4 upstream versions 4.1.18 / 4.2.1+ (stable) reportedly fix ntlm_auth NTLMv2 failures

[Michael Evans]

Package: samba

Version: 4.1.17+dfsg-2

Severity: important

Tags: fixed-upstream

 

Having spent the last day enabling additional debugging output, and manually
decoding NTLM packets, I've come across a likely root cause for my woes:

 

https://bugzilla.samba.org/show_bug.cgi?id=10016

 

The solutions for this bug include: Using the updated Samba which allows
improved client security to function, forcibly downgrading security on all
clients to older (vulnerable) versions of the NTLM protocol, requiring
stored passwords and plain text auth via PAM instead of accounts (single
sign on won't work).

 

The included patch exists in 4.1.18 and 4.2.1+

 

https://www.samba.org/samba/history/samba-4.1.18.html 

https://www.samba.org/samba/history/samba-4.2.0.html << Note: not included,
but other nice things.

https://www.samba.org/samba/history/samba-4.2.1.html 

Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

[Michael Biebl]

Am 04.06.2015 um 23:37 schrieb Michael Biebl:
> Am 04.06.2015 um 23:12 schrieb nusenu:
>>> Can you find out what is different between the upgraded and fresh Debian
>>> installation?
>>
>> systemd version is on both (fresh and upgraded) systems 215-17, what
>> else should I check?
> 
> Eg. diff the list if installed packages you get via dpkg
> --get-selections and look for suspicouos diffs.
> 
> Local modifications, like custom fstab entries which override cgroupfs
> settings, stuff like that.

or different kernel, obsolete packages etc.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

[Michael Biebl]

Am 04.06.2015 um 23:12 schrieb nusenu:
>> Can you find out what is different between the upgraded and fresh Debian
>> installation?
> 
> systemd version is on both (fresh and upgraded) systems 215-17, what
> else should I check?

Eg. diff the list if installed packages you get via dpkg
--get-selections and look for suspicouos diffs.

Local modifications, like custom fstab entries which override cgroupfs
settings, stuff like that.

Can you provide steps how to reproduce the problem



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth



signature.asc
Description: OpenPGP digital signature

Bug#787750: wmstickynotes: Does not remember the virtual screen; always restored on first one

[Doug Torrance]

Control: tags -1 pending

On 06/04/2015 03:36 PM, Heath N. Caldwell wrote:
> Thanks for bringing this up.  I have committed a fix and released a new
> tarball for it (0.6).  Let me know if it works as expected.

Thanks, Heath!  The new version fixes the issue for me.  I'll upload a
new Debian package soon.

Doug


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

Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

[Michael Biebl]

Am 04.06.2015 um 23:16 schrieb nusenu:
> 
>> Do you maybe have anything installed on your upgraded system which might
>> interfere with systemd, like cgmanager, lxc, cgroup-bin etc.
> 
> upgraded-system#  dpkg -l cgmanager lxc cgroup-bin
> dpkg-query: no packages found matching cgmanager
> dpkg-query: no packages found matching lxc
> dpkg-query: no packages found matching cgroup-bin

Anything else which is cgroup related?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#786987: evidence

[Daniel Kahn Gillmor]

On Thu 2015-06-04 11:22:01 -0400, Colin Watson wrote:
> On Thu, Jun 04, 2015 at 10:35:37AM -0400, Micah Anderson wrote:
>> . it is used as a selector in NSA's XKEYSCORE queries in conjunction
>>  with the metadata database of potentially exploitable services
>>  (BLEAKINQUIRY) by the NSA group "S31176" for targeted exploit and
>>  compromise[1][2]
>
> This is a somewhat more compelling argument; I'll think about it.

Thanks, Colin  :)

> Upstream's non-configurable default is to include the OpenSSH version in
> the banner (e.g. "OpenSSH_6.8p1").

Hm, i think Upstream's non-configurable default is actually
"SSH-2.0-OpenSSH_6.8" (even in the portable version).  Debian has added
the trailing "p1" in debian/patches/package-versioning.patch.

> https://bugzilla.mindrot.org/show_bug.cgi?id=764; but that's WONTFIX
> upstream for good reason, because it's still necessary to use the
> version for protocol compatibility tweaks.  The most recent version of
> itself that OpenSSH needs to distinguish in this manner is as recent
> as 6.6p1, to deal with a key exchange bug in its implementation of
> ED25519, and something different comes along here every couple of
> years or so; this is not an archaic thing that can safely be
> discarded.

Yeah, that part is too bad, and the bug was present in 6.5 and 6.6
before being fixed in 6.7.  one approach to getting roughly the same
functionality would be to have a version-independent
"incompatible-feature" string announced in the header; so upon the
bugfix, you'd add "fixed-25519-dh" (or just "N", where N is a
monotonically increasing number that indicates the set of OpenSSH
accumulated signalling-worthy-fixes, which are assumed to all be
applied) -- it doesn't have to be updated with each version.

(and the worst that happens with the bug you mention is a 0.2% chance of
handshake failure with unpatched peers, fwiw; this might be a cost some
people are willing to bear for the sake of minimizing leakage)

But anyway, this bug report is specifically about the default for
DebianBanner, not about removing the upstream version string.

> As such, the best that we can do without causing real and significant
> interoperability problems is to advertise "SSH-2.0-OpenSSH_6.7p1" rather
> than "SSH-2.0-OpenSSH_6.7p1 Debian-5" in our banner.  You'll still have
> to argue with people about these version strings; in fact, if you're
> having to do so right now, disabling DebianBanner will almost certainly
> cause you to have to do so more often.

Colin is certainly right here, but if micah has turned off DebianBanner
on his servers, he's probably already dealing with that situation.

>> . its used in CTF (capture the flag) events, in order to know what OS is
>> running on a system that only has ssh running, and what version of ssh
>> is running so that you can look at exploits that could be used to
>> compromise the system for a flag.
>
> Yeah, though dealing with this seems like a drop in the ocean compared
> to things like TCP stack fingerprinting that are much harder to address.

Fixing TCP stack fingerprinting is not in scope for the OpenSSH package,
though.  And someone trying to fix TCP stack fingerprinting might not
bother because "hey, the OS and version info are all leaked by apache
and OpenSSH anyway, why should we bother?"

Helping to resolve tricky issues like fingerprinting is a collective
action problem, and each part of the ecosystem needs to improve.  I know
you understand this, Colin, but i don't want the "don't bother fixing X
because Y is also broken" argument to get traction.  In an environment
as ugly and broken as the Internet, that just leads to despair and
complete inaction :)

Thanks for the consideration here,

   --dkg


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

Bug#787772: Samba 4 upstream versions 4.1.18 / 4.2.1+ (stable) reportedly fix ntlm_auth NTLMv2 failures

[Michael Evans]

Package: samba

Version: 4.1.17+dfsg-2

Severity: important

 

I'm re-submitting because I don't think it liked me adding the Tags:
fixed-upstream pseudo-header.

 

Having spent the last day enabling additional debugging output, and manually
decoding NTLM packets, I've come across a likely root cause for my woes:

 

https://bugzilla.samba.org/show_bug.cgi?id=10016

 

The solutions for this bug include: Using the updated Samba which allows
improved client security to function, forcibly downgrading security on all
clients to older (vulnerable) versions of the NTLM protocol, requiring
stored passwords and plain text auth via PAM instead of accounts (single
sign on won't work).

 

The included patch exists in 4.1.18 and 4.2.1+

 

https://www.samba.org/samba/history/samba-4.1.18.html 

https://www.samba.org/samba/history/samba-4.2.0.html << Note: not included,
but other nice things.

https://www.samba.org/samba/history/samba-4.2.1.html 

 

Bug#787447: tshark shows 'Segmentation fault' on exit

[Bálint Réczey]

Control: forwarded -1 https://code.wireshark.org/review/#/c/8765/
Control: tags -1 upstream

Hi Joao,

2015-06-02 13:54 GMT+02:00 Joao S Veiga :
>> Please install wireshark-dbg and run "ulimit -c unlimited" before
>> reproducing the issue. This will generate a core file which you can
>> analyze with gdb.
>> Please attach the stack trace to see what is crashing.
>>
>> I ran a quick test on my computer and tshark ran fine.
>>
>> Cheers,
>> Balint
>
>
> Thank you Balint, it seems it is liblua;
>
> the back trace shows this:
>
> Core was generated by `tshark -c 1 -i eth0 -f host 200.232.120.2'.
...
> #0  lua_close (L=0x0) at lstate.c:318
> #1  0x7f697b3d5b60 in wslua_cleanup () at
> /build/wireshark-fAHyh_/wireshark-1.12.1+g01b65bf/epan/wslua/init_wslua.c:877
> #2  0x7f697b348002 in epan_cleanup () at
> /build/wireshark-fAHyh_/wireshark-1.12.1+g01b65bf/epan/epan.c:142
> #3  0x0040b99c in main (argc=572523360, argv=0x0) at
> /build/wireshark-fAHyh_/wireshark-1.12.1+g01b65bf/tshark.c:2232
>
> Please let me know if you need any more information or tests.
Thank you, this seems to be enough to fix the issue.

Cheers,
Balint


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

Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

[nusenu]

> Can you find out what is different between the upgraded and fresh Debian
> installation?

systemd version is on both (fresh and upgraded) systems 215-17, what
else should I check?

> Can you post the complete service file you are using, please?

working service file
(to make it fail on upgraded systems, enable the 4 commented-out Read*
lines):


[Unit]
Description = Anonymizing overlay network for TCP
After = syslog.target network.target nss-lookup.target

[Service]
Type = simple
ExecStartPre = /usr/bin/tor -f /etc/tor/enabled/%i.torrc --verify-config
ExecStart = /usr/bin/tor -f /etc/tor/enabled/%i.torrc --runasdaemon 0
ExecReload = /bin/kill -HUP ${MAINPID}
KillSignal = SIGINT
TimeoutSec = 30
Restart = on-failure
#WatchdogSec = 1m
LimitNOFILE = 32768

## Hardening
PrivateTmp = yes
PrivateDevices = yes
ProtectHome = yes
ProtectSystem = full

#ReadOnlyDirectories = /
#ReadWriteDirectories = /var/lib/tor
#ReadWriteDirectories = /var/log/tor
#ReadWriteDirectories = /var/run/tor

NoNewPrivileges = yes

CapabilityBoundingSet = CAP_SETUID CAP_SETGID CAP_NET_BIND_SERVICE
PermissionsStartOnly=yes

AppArmorProfile=-system_tor

[Install]
WantedBy = multi-user.target



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

Bug#787771: Version 0.6.3-1 breaks puppet

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: ruby-augeas
Version: 0.6.3-1
Severity: important

The new version breaks puppet with the following message:
   Could not evaluate: private method `open' called for Augeas:Class

Downgrading to 0.5.0-2+b2 solves the problem.

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (500, 'testing'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.5 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to 
de_DE)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ruby-augeas depends on:
ii  libaugeas0  1.2.0-0.2
ii  libc6   2.19-18
ii  libgmp102:6.0.0+dfsg-6
ii  libruby2.1  2.1.5-3
ii  libxml2 2.9.2+dfsg1-3

ruby-augeas recommends no packages.

ruby-augeas suggests no packages.

- -- no debconf information

- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJVcL9UAAoJEKZ8CrGAGfas8k4MAIA2wI3LmsXxvZ4lWkOl7lg2
7ShvRrEUzReE0exioXMIPTf8kxNe61DYG4Q4KrQ+liVpuuNDSNxXK0Tfb1rnnU8n
m/WjPsWN48hnsqAVrklja96HiBIfoXUabBgeD86ajXuUL6UrGLjTI1x4Y0QVwO8S
1VKji0r/XiCCETpAl78ZYrQJCpkl8uX4juqlvGqd3opAbm3/Sk4YOf+ICX+p5Q2c
nZrw+3o3fpPhHeIlnDaOQ8IT5Ct/CiRX4UstfreDO+gbvW3O/Yt4gN2uSU+nDqEu
fPolaXvwxbyuy+SRkXCz4BkinVEaawWv00yKu3CCIolnTJkWA3E35wCgBkkq86e9
f7z2m3RM9fp0SwRMG2CZ62Bozhv6S6ytolwQ3m13ajrVgMesiWmPqc+wASbCxFfS
ahK9eXpZ42SN8Ztv8sgkFjCWEd/HoAcL8D+B/qrpd0aRQmJMYxfD9nEZv8PR20lo
HladojmQ4zpjuURtM9gxpyPt2MRsv/hLVduLH01vMA==
=XhJM
-END PGP SIGNATURE-


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

Bug#772628: Patch for kmod package to support compression

[Andreas Mohr]

Since I managed to mess up things
by telling my own new story
rather than having stumbled upon
this detailed pre-existing item
(via proper research, that is...),
I now see it as my duty to at least reference
the new discussion's URL here:
"[PATCH] modules: CONFIG_MODULE_COMPRESS: add hint that userspace support may 
easily be missing." https://lkml.org/lkml/2015/5/31/90


Given current direction / results of that discussion,
I'd want to vote
for gaining at least *some* amount of compression support
directly in Debian binary package defaults.

Thanks,

Andreas Mohr


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

Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

[nusenu]

> Do you maybe have anything installed on your upgraded system which might
> interfere with systemd, like cgmanager, lxc, cgroup-bin etc.

upgraded-system#  dpkg -l cgmanager lxc cgroup-bin
dpkg-query: no packages found matching cgmanager
dpkg-query: no packages found matching lxc
dpkg-query: no packages found matching cgroup-bin


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

Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

[Michael Biebl]

Am 04.06.2015 um 23:00 schrieb Michael Biebl:
> Am 04.06.2015 um 20:36 schrieb nusenu:
>> Package: systemd
>> Version: 215-17
>>
>> when using a multi-instance systemd service file with
>> ReadOnlyDirectories the service fails if it is attempted to start on a
>> Debian 8 system that has been upgraded from a previous release.
>>
>> Error message is:
>> Failed at step NAMESPACE spawning /usr/bin/tor: No such file or directory
>> service: main process exited, code=exited, status=226/NAMESPACE
>>
>> The same config works on a fresh Debian 8 installation.
> 
> Can you find out what is different between the upgraded and fresh Debian
> installation?
> Can you post the complete service file you are using, please?

Do you maybe have anything installed on your upgraded system which might
interfere with systemd, like cgmanager, lxc, cgroup-bin etc.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#787770: ITP: w1retap -- Data logger for 1-Wire weather sensors

[Thomas Stewart]

Package: wnpp
Severity: wishlist
Owner: Thomas Stewart 

* Package name: w1retap
  Version : 1.4.2
  Upstream Author : Jonathan Hudson 
* URL : http://www.zen35309.zen.co.uk/wx/tech.html
* License : GPL with some Expat
  Programming Lang: C
  Description : Data logger for 1-Wire weather sensors

The w1retap package reads weather sensors on a 1-Wire bus and logs the 
retrieved  data to the configured databases or files. It supports a
number of different 1-Wire host bus adapters and 1-Wire sensors designed
by Dallas Semiconductor Corp (now Maxim Integrated) and compatible
sensors including those from AAG Electrónica and other hobby sensors.


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

Bug#787758: 'Failed at step NAMESPACE spawning' when using ReadOnlyDirectories in multi-instance service file

[Michael Biebl]

Am 04.06.2015 um 20:36 schrieb nusenu:
> Package: systemd
> Version: 215-17
> 
> when using a multi-instance systemd service file with
> ReadOnlyDirectories the service fails if it is attempted to start on a
> Debian 8 system that has been upgraded from a previous release.
> 
> Error message is:
> Failed at step NAMESPACE spawning /usr/bin/tor: No such file or directory
> service: main process exited, code=exited, status=226/NAMESPACE
> 
> The same config works on a fresh Debian 8 installation.

Can you find out what is different between the upgraded and fresh Debian
installation?
Can you post the complete service file you are using, please?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#787323: gthumb: Memory leaks with freehand rotations

[Riccardo Boninsegna]

On Sun, May 31, 2015 at 4:19 PM, Herbert Parentes Fortes Neto <
h...@ig.com.br> wrote:
>How did you monitored the mem usage ? Did you use the [arrows at the top] ?
>Can you test the version in 'testing' ?

No, the issue is with the freehand rotation: http://imgur.com/Lw2jgNv

Trying it with version 3:3.4.0-2 and appropriate updates of all
dependencies to the version current in stretch, the bug is still present:
in fact, immediately after clicking the button in the previous screenshot,
the image size in pixels changes to a ridiculously high size, which may be
connected to this issue: http://imgur.com/Cmgfuhd

Example of leak after rotating about 20 seventeen megapixel images:
http://imgur.com/yMTP5aV

This may likely be an upstream bug, as I recall it happening on another OS
(not sure whether it was Arch Linux or a still-in-testing Jessie) a few
months ago...

Bug#779057: More info

[Fabrizio Regalli]

On Tue, 2 Jun 2015 12:31:46 -0300 
=?UTF-8?Q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?= 
 wrote:
> In my case the problem was an entry in fstab that was no longer valid.

Same here.
I commented out the following line in /etc/fstab

none /proc/bus/usb usbfs devgid=121,devmode=664 0 0

and worked again.


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

Bug#787601: Info received (libsane 1.0.24-13 segfaults looking for network Samsung scanner SCX-4833FD)

[Bryan Cebuliak]

Upgrade to libsane 1.0.25+git20150528-1 from experimental [also sane-utils
and libsane-common] fixes  the problem.

On 3 June 2015 at 19:09, Debian Bug Tracking System 
wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Jörg Frings-Fürst 
>
> If you wish to submit further information on this problem, please
> send it to 787...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 787601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787601
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#787769: mon: Monitor pod docs are not included in installed man pages.

[Karl O. Pinc]

Package: mon
Version: 1.2.0-6
Severity: wishlist

Hi,

The pod docs in the program text of the monitors
in /usr/lib/mon/mon.d/ are not included as man pages.
As a result the monitors are not well documented.

To read the docs:

  pod2man foo.monitor | man -l -

I know Debian package are required to include
man pages for all programs.  Someone who knows
more about policy than me might classify this
bug as a policy violation.

-- System Information:
Debian Release: 7.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.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


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

Bug#787768: mon: local-syslog.monitor output in an email alert begins with "messages"

[Karl O. Pinc]

Package: mon
Version: 1.2.0-6
Severity: minor

Hi,

When local-syslog.monitor reports matching lines in a
log file and the result is emailed, the email has
a spurious "messages" string that appears at the
beginning of the first line of log output
in the "detailed text" at the bottom of the email.

Regards,
Karl

-- System Information:
Debian Release: 7.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.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


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

Bug#787767: [uscan] wrong sort order during recursive scanning

[Daniel Leidert]

Package: devscripts
Version: 2.15.4
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Consider the following watch file content:

version=3
http://www.abinit.org/downloads/packages/(\d+)-(\d+)\.(\d+)/ 
.*/abinit-([\d.]+)\.tar\.gz$

So there is some recursive scanning involved. Now it picks up the wrong
version (debug output):

uscan debug: matching pattern 
(?:(?:http://www.abinit.org)?\/downloads\/packages\/)?(\d+)-(\d+)\.(\d+)
- -- Found the following matching hrefs (newest first):
 http://www.abinit.org/downloads/packages/7-0.5 (7..5)
 http://www.abinit.org/downloads/packages/7-0.4 (7..4)
 http://www.abinit.org/downloads/packages/7-0.3 (7..3)
 http://www.abinit.org/downloads/packages/7-10.4 (7.10.4)
 http://www.abinit.org/downloads/packages/7-10.2 (7.10.2)
 http://www.abinit.org/downloads/packages/7-10.1 (7.10.1)
 http://www.abinit.org/downloads/packages/7-8.2 (7.8.2)
 http://www.abinit.org/downloads/packages/7-8.1 (7.8.1)
 http://www.abinit.org/downloads/packages/7-6.4 (7.6.4)
 http://www.abinit.org/downloads/packages/7-6.3 (7.6.3)
 http://www.abinit.org/downloads/packages/7-6.2 (7.6.2)
 http://www.abinit.org/downloads/packages/7-6.1 (7.6.1)
 http://www.abinit.org/downloads/packages/7-4.3 (7.4.3)
 http://www.abinit.org/downloads/packages/7-4.2 (7.4.2)
 http://www.abinit.org/downloads/packages/7-4.1 (7.4.1)
 http://www.abinit.org/downloads/packages/7-2.2 (7.2.2)
 http://www.abinit.org/downloads/packages/7-2.1 (7.2.1)
uscan debug: newest_dir => '7-0.5'
uscan debug: requesting URL http://www.abinit.org/downloads/packages/7-0.5/
uscan debug: redirections: 
uscan debug: received content:

Now why does it do that? Further why does it output "7..5" instead of "7.0.5"
in the output above? Might this be related to the wrong result?


Regards, Daniel


- -- Package-specific info:

- --- /etc/devscripts.conf ---

- --- ~/.devscripts ---
DEBSIGN_KEYID=C296D05D
DEBUILD_LINTIAN=yes
DEBUILD_LINTIAN_OPTS="-i -I -E --pedantic"
DEBCHANGE_RELEASE_HEURISTIC=changelog

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (850, 'unstable'), (700, 'testing'), (560, 'stable'), (110, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages devscripts depends on:
ii  dpkg-dev 1.18.1
ii  libc62.19-18
ii  perl 5.20.2-6
ii  python3  3.4.2-2
pn  python3:any  

Versions of packages devscripts recommends:
ii  at  3.1.16-1
ii  curl7.42.1-2+b1
ii  dctrl-tools 2.24-1
ii  debian-keyring  2015.05.17
ii  dput0.9.6.4
ii  equivs  2.0.9
ii  fakeroot1.20.2-1
ii  file1:5.22+15-2
ii  gnupg   1.4.19-3
ii  libdistro-info-perl 0.14
ii  libencode-locale-perl   1.03-1
ii  libjson-perl2.61-1
ii  liblwp-protocol-https-perl  6.06-2
ii  libsoap-lite-perl   1.11-1
ii  liburi-perl 1.64-1
ii  libwww-perl 6.08-1
ii  lintian 2.5.31
ii  man-db  2.7.0.2-5
ii  patch   2.7.5-1
ii  patchutils  0.3.4-1
ii  python3-debian  0.1.27
pn  python3-magic   
ii  sensible-utils  0.0.9
ii  strace  4.10-1
ii  unzip   6.0-17
pn  wdiff   
ii  wget1.16.3-2+b2
ii  xz-utils5.1.1alpha+20120614-2+b3

Versions of packages devscripts suggests:
ii  bsd-mailx [mailx]8.1.2-0.20150408cvs-1
ii  build-essential  11.7
pn  cvs-buildpackage 
pn  debbindiff   
pn  devscripts-el
ii  gnuplot  4.6.6-2
ii  gpgv 1.4.19-3
ii  libauthen-sasl-perl  2.1600-1
pn  libfile-desktopentry-perl
ii  libnet-smtp-ssl-perl 1.01-3
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
ii  libyaml-syck-perl1.27-2+b2
ii  mutt 1.5.23-3
ii  openssh-client [ssh-client]  1:6.7p1-6
ii  svn-buildpackage 0.8.5+nmu1
ii  w3m  0.5.3-21

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJVcGm5AAoJEEvNBWfCltBdZRUP/1EA/a84Tfe/KHcGZ3TNJiE7
lZ9TL52V4SV67KC2j3R1nU/h2z8Nw4tbB0IAcujpMoRjh75m5daAVQ+/Qy/RlM1D
iG0ZxnItOcDKhPJ+PHOAfWd/OQzNKyPHlxl+I1hEOw/73SPhnhqwLKh2Hk6PGZ7W
dhPVKjr9z6uMFNOSXgthpY6gQc6w+TkcIihzDEPkJEDWZQlCCGfthOwhzHsgyxw6
OCVjdF2NhQwMBxLFiw2NGygjs5qeDUv7bybZQM7yOjO9XGHEbJt707zGMlrf/COU
VZo05AwjFH9Q53ULa9qajbBKnL+OeBDklrfBGqJCcdapGTOq7srAUk

Bug#787750: wmstickynotes: Does not remember the virtual screen; always restored on first one

[Heath N. Caldwell]

Hi Doug, and Andreas,

Thanks for bringing this up.  I have committed a fix and released a new
tarball for it (0.6).  Let me know if it works as expected.

Thanks,
  - Heath

On 2015-06-04 12:32, Doug Torrance wrote:
> Forwarded: hncaldw...@fastmail.fm
> 
> Hi Heath,
> 
> I just received this bug report for the Debian wmstickynotes package.
> Would you be interested in adding this feature at some point?
> 
> Thanks!
> Doug
> 
> On Thu, Jun 4, 2015 at 11:45 AM, Andreas Tscharner  wrote:
> > Package: wmstickynotes
> > Version: 0.5-1
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > I have several virtual screens on my desktop. I have docked wmstickynote to 
> > my
> > dock.
> > Now I write a note on my 4th screen. Then I leave WindowMaker, and then I
> > come back, wmstickynotes (which is auto started) restores my note, but on 
> > the
> > first screen instead of the 4th

-- 
Heath Caldwell
hncaldw...@fastmail.fm


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

Bug#787766: mon: local-syslog.monitor silently fails when lacking read permission

[Karl O. Pinc]

Package: mon
Version: 1.2.0-6
Severity: normal

Hi,

The local-syslog.monitor program silently fails when
it does not have read permissions on the log file
it is to monitor.

One approach to getting it to work is to add the
"mon" user to the "adm" group, but this is likely
inapproprate for the package to do.

An indication of this problem is a "-1"
for a file position in the status file
(the 2nd of two entries on the one line in the file).

Logging a message regards the problem is
probably the right solution.

Regards,
Karl

-- System Information:
Debian Release: 7.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.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


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

Bug#643595: snes9x: changing back from ITP to RFP

[Sergio benjamim Rocha filho]

I made one package, here:

http://mentors.debian.net/package/snes9x

Sérgio Benjamim


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

Bug#766458: lynx-cur: some tables are not rendered correctly

[Denis Briand]

tags 766458 unreproducible moreinfo
thanks

Hello Vincent,
Thank you for your bug report.
I can't reproduce this bug.
The attached file contains exactly the two similar tables.
Where is the issue?
The provided URL have a 404 error.

Best regards

Denis Briand


signature.asc
Description: Digital signature

Bug#787765: cassiopee: please make the build reproducible

[marivalen]

On Thu, 04 Jun 2015 22:00:36 +0200 Maria Valentina Marin
 wrote:
> The attached patch changes the value of HTML_TIMESTAMP in upstream's
and here comes the patch
Description: Changed the value of the variable HTML_timestamp from YES to NO

--- cassiopee-1.0.3+dfsg.orig/src/Doxyfile.in
+++ cassiopee-1.0.3+dfsg/src/Doxyfile.in
@@ -932,7 +932,7 @@ HTML_COLORSTYLE_GAMMA  = 80
 # page will contain the date and time when the page was generated. Setting
 # this to NO can help when comparing the output of multiple runs.
 
-HTML_TIMESTAMP = YES
+HTML_TIMESTAMP = NO
 
 # If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
 # files or namespaces will be aligned in HTML using tables. If set to

Bug#768532: ITA debmirror

[Thaddeus H. Black]

That is, if you wish to help, let me know at t...@debian.org.
(E-mail to that other address won't reach me.)



signature.asc
Description: Digital signature

Bug#787679: sqlitebrowser: testsuite fails in several environments, TestImport::csvImport(utf8chars) Compared values are not the same

[peter green]

On 04/06/15 17:58, Arto Jantunen wrote:

The obvious big difference between the normal amd64 build daemon and the
reproducible test one is that reproducible builds with pbuilder instead
of sbuild. I assume raspbian is built the normal way with sbuild?

Yes the raspbian autobuilders use sbuild.

On 04/06/15 19:38, Arto Jantunen wrote:

Sbuild (the build succeeds):

LANG=C.UTF-8 locale
LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_PAPER="C.UTF-8"
LC_NAME="C.UTF-8"
LC_ADDRESS="C.UTF-8"
LC_TELEPHONE="C.UTF-8"
LC_MEASUREMENT="C.UTF-8"
LC_IDENTIFICATION="C.UTF-8"
LC_ALL=

Pbuilder (the build fails):

LANG=C.UTF-8 locale
LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=C

For some reason when running under pbuilder setting LANG doesn't affect
the other locale settings

I think we have found the problem.

There is a priority order in determining what locale settings should be 
used.


LANG is the lowest priority
LC_ has a medium priority
LC_ALL has the highest priority

If you need specific locale settings in a script you should either use 
LC_ALL (if using the same locale for all categories is appropriate) or 
if you need to contol different categories individually make sure LC_ALL 
is not set.



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

Bug#787747: [pkg-xtuple-maintainers] Bug#787747: postbooks: FTBFS due to missing build dependency libqt4-webkit

[Lisandro Damián Nicanor Pérez Meyer]

On Thursday 04 June 2015 21:25:01 Daniel Pocock wrote:
[snip]
> Ok, the build deps have been updated, they only depend on
> libqtwebkit-dev now and not on libqt4-webkit
> 
> I'm also happy for people to NMU these packages just as long as you
> make the changes through Git and tag when you upload

I was expecting to do this tonight but you beat me to it, thanks a lot!
 
> Thanks for taking the time to provide this feedback about the packages.

Please be sure to ping us Debian Qt/KDE maintainers if you need assistance 
with the Qt5 porting :) I can't warrant that we will be able to help, but at 
least we will try :)


-- 
Wiki is not WysiWyg. It's an intelligence test of sorts to be able to edit a
wiki page. It's not rocket science, but it doesn't appeal to the VideoAddicts.
If it doesn't appeal, they don't participate, which leaves those of us who
read and write to get on with rational discourse.
  http://www.c2.com/cgi/wiki?WhyWikiWorks

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#787241: More info

[Amaya]

This has been reported in xfce upstream here:
https://bugzilla.xfce.org/show_bug.cgi?id=11627

-- 
 .''`.The world breaks everyone, and afterward, some are
: :' :strong at the broken places.- Ernest Hemingway
`. `'   
  `-Proudly running Debian GNU/Linux


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

Bug#768532: ITA: debmirror

[Thaddeus H. Black]

I am hardly the ideal maintainer for this package.  Nevertheless,

  * I have used the package for years;
  * the package is implemented in Perl, a language with which
I am familiar and which I often use;
  * I have recently spent some hours to learn a little about
the package's software internals;
  * among the package's outstanding bug reports is one with
a patch by me;
  * the package has a not insignificant number of users;
  * the package has now been orphaned six months; and
  * no other maintainer seems to be stepping forward to adopt
the package.

So, I'll adopt it, at least for now, and we shall see how it goes.
If the adoption does not work out, then I'll orphan the package again,
and we'll be no worse off than we now are.

I miss former maintainers Frans Pop (deceased) and Joey Hess (retired),
two of my favorite DDs of all time.  Those were important DDs, giants
of Debian; whereas I am so unimportant a DD that (despite my having been
a DD ten years), 90 percent of the project's members have never heard
of me.  That's just as well, and I'll not fill Frans' or Joey's shoes;
but still, after the great have left, the less must carry on.

If you wish to help, let me know.



signature.asc
Description: Digital signature

Bug#787765: cassiopee: please make the build reproducible

[Maria Valentina Marin]

Source: cassiopee
Version: 1.0.3+dfsg
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps

Hi,

While working on the “reproducible builds” effort [1], we have noticed
that cassiopee could not be built reproducibly.

The attached patch changes the value of HTML_TIMESTAMP in upstream's
doxyfile to NO. Once applied cassiopee can be built reproducibly in our
current experimental framework.

Patching upstream doxyfile is necessary in this case because of the
following reasons:

1. Even though the doxygen upstream changed the default value of
HTML_TIMESTAMP from YES to NO this does not affect this package because
the value of HTML_TIMESTAMP is explicitly set to YES.

2. Upstream's doxyfiles cannot reliably be modified to change the value
of HTML_TIMESTAMP during the build process because dh_doxygen is only
run after the build already completed and even adding a new dh command
cannot solve the problem because there exists no sane and reliable
solution to detect the file which will be used as the configuration file
for doxygen (it is not always called doxyfile).

3. In case of this source package a patch against upstream is necessary
in contrast to a patch against Debian rules because this source package
does not call doxygen in debian/rules.

Please also consider forwarding this patch upstream.

Cheers!
akira

 [1]: https://wiki.debian.org/ReproducibleBuilds


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

Bug#787764: libvpx2: vp9 encoding is significantly slower in 1.4.0 than in 1.3.0

[Matt Zagrabelny]

Package: libvpx2
Version: 1.4.0-3
Severity: normal

Dear Maintainer,

Thank you for your work on Debian and for free software. I appreciate
it!

I'm using ffmpeg to encode some DVDs into webm (vp9,vorbis) and have
noticed a significant decrease in speed since upgrading ffmpeg from
2.6.2-1 to 2.6.3-1. This is when libvpx2 was pulled in for dependency
resolution.

I'm using the same ffmpeg wrapper scripts to encode the vob files before
the upgrade and after. I wouldn't normally file a bug like this, but the
difference in encoding time is so stark. Without having hard
measurements yet, I'd say it is around a 4x to 6x slowdown.

I don't know whether to file the bug here or with ffmpeg, but I thought
I would start here. Please correct me if I am wrong.

Thanks for your time,

-mz

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-1-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 libvpx2 depends on:
ii  libc6   2.19-18
ii  libgcc1 1:5.1.1-7
ii  libstdc++6  5.1.1-7

libvpx2 recommends no packages.

libvpx2 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

Bug#787639: [pkg-gnupg-maint] Bug#787639: [PATCH] pinentry_setbufferlen returns pin when already large enough

[Werner Koch]

On Thu,  4 Jun 2015 19:54, n...@walfield.org said:

> It's a pretty significant bug in that it renders the curses backend
> completely unusable.

Okay.  I'll do it tomorrow.

> How about a 0.93.1 release rather 0.94 given that it is the only
> change?

Ah no.  0.9.4 is just fine.  


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


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

Bug#787763: util-linux: 'unshare -m' broken

[James Long]

Package: util-linux
Version: 2.25.2-6
Severity: important

Dear Maintainer,

'unshare -m' no longer works, mounts persist and are visible to all:

# unshare -m /bin/bash
# mount -t nfs -o ro,vers=3,tcp 10.4.5.101:/opt /mnt
# df -Th
>snip<
10.4.5.101:/opt nfs92G   17G   71G  20% /mnt
# exit
# logout
$ df -Th
>snip<
10.4.5.101:/opt nfs92G   17G   71G  20% /mnt

Thanks in advance,

Jim


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

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

Versions of packages util-linux depends on:
ii  initscripts2.88dsf-59
ii  libblkid1  2.25.2-6
ii  libc6  2.19-18
ii  libmount1  2.25.2-6
ii  libncurses55.9+20140913-1+b1
ii  libpam0g   1.1.8-3.1
ii  libselinux12.3-2
ii  libslang2  2.3.0-2
ii  libsmartcols1  2.25.2-6
ii  libtinfo5  5.9+20140913-1+b1
ii  libuuid1   2.25.2-6
ii  lsb-base   4.1+Debian13+nmu1
ii  tzdata 2015d-0+deb8u1
ii  zlib1g 1:1.2.8.dfsg-2+b1

util-linux recommends no packages.

Versions of packages util-linux suggests:
pn  dosfstools  
ii  kbd 1.15.5-2
ii  util-linux-locales  2.25.2-6

-- 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#787241: xserver-xorg-video-intel: VT never returns from powersave on Haswell

[Amaya]

Aftyer playing around a bit, I am no longer experiencing this with
a different window manager (meta), so I doubt this bugs belongs to
xserver-xorg-video-intel. I have no idea which xfce package, though.

Thanks!


-- 
 .''`.The world breaks everyone, and afterward, some are
: :' :strong at the broken places.- Ernest Hemingway
`. `'   
  `-Proudly running Debian GNU/Linux


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

Bug#783381: upgrade from wheezy to jessie on a PowerMac G4 Silver/Confirmation

[Alois Zoitl]

I gave this a try as I'm also using yaboot. Purging mkvmlinuz solved this
issue for me as well.

And now to the graphics problems :-(

On Thu, Jun 4, 2015 at 9:01 PM, Manfred Stock <
manfred.stock+deb...@gmail.com> wrote:

> Package: upgrade-reports, linux-image-3.16.0-4-powerpc
> Followup-For: Bug #783381
>
> I also had this problem on an iBook G4, but had not rebooted, yet. When I
> started to look into it, I looked at the mkvmlinuz package page [1] and
> upon
> reading the description, I just decided to remove/purge the mkvmlinuz
> package,
> since I'm using yaboot as bootloader. That way, I got rid of this error,
> and
> the configuration of the kernel package was successful. I did not have
> issues
> during the reboot either, so at least in my setup, mkvmlinuz does not seem
> to
> be required. I do have other issues on this system though (mainly with the
> graphics card, and suspend to ram/disk), but I think they are not related
> to
> the problem with mkvmlinuz.
>
> Kind regards
> Manfred
>
> [1] https://packages.debian.org/jessie/mkvmlinuz
>
> --
> To unsubscribe, send mail to 783381-unsubscr...@bugs.debian.org.
>

Bug#787762: dolibarr: CVE-2015-3935: dolibarr HTML injection

[Salvatore Bonaccorso]

Source: dolibarr
Version: 3.5.5+dfsg1-1
Severity: important
Tags: security upstream fixed-upstream

Hi,

the following vulnerability was published for dolibarr.

CVE-2015-3935[0]:
HTML Injection

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-3935
[1] https://github.com/Dolibarr/dolibarr/issues/2857
[2] 
https://github.com/Dolibarr/dolibarr/commit/f32215a9fc3abfa69c34d4cf65a044b60ff8e93a

Regards,
Salvatore


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

Bug#787747: [pkg-xtuple-maintainers] Bug#787747: postbooks: FTBFS due to missing build dependency libqt4-webkit

[Daniel Pocock]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256



On 04/06/15 19:29, Lisandro Damián Nicanor Pérez Meyer wrote:
> On Thursday 04 June 2015 19:18:57 Daniel Pocock wrote:
>> On 04/06/15 18:43, Lisandro Damián Nicanor Pérez Meyer wrote:
>>> Source: postbooks Version: 4.7.0-2 Severity: serious 
>>> Justification: FTBFS due to missing dependency
>>> 
>>> Hi! Your package *build* depends on libqt4-webkit, which is no
>>> longer available in the archive, and so it FTBFS.
>>> 
>>> Sadly I missed it when preparing the transition to remove this 
>>> transitional packages because I did not expect people depending
>>> on a non-dev package as it is useless. Now Qt4 has been
>>> uploaded and this FTBFS will be triggered on the next rebuild
>>> :-(
>> 
>> The xTuple upstream developers are aware of the transition and
>> qt5 will be supported with a new upstream release, maybe 4.9.0 or
>> 4.10.0.
>> 
>> I believe the timeline for this is within 3 - 6 months.
>> 
>> Can you please leave libqt4-webkit in the archive until upstream
>> finish testing and release with qt5 support?
> 
> Hi Daniel! You are mixing two things here:
> 
> - One is using qt4 webkit. There is another bug filed for that. We
> do not expect to do the removal soon, but we expect to start
> pushing things harder whenever the KDE stack gets updated. I would
> say at least 3 months, can be more.
> 
> - Another one is the problem which motivates this bug. You are
> using libqt4-webkit as a build dependency, when that package does
> not provides any headers. This is the package that got removed. You
> are already build depending on libqtwebkit-dev, so simply removing
> libqt4-webkit from the build dependencies should do the trick.
> 
> I think the same goes for postbooks-updater.

Ok, the build deps have been updated, they only depend on
libqtwebkit-dev now and not on libqt4-webkit

I'm also happy for people to NMU these packages just as long as you
make the changes through Git and tag when you upload

Thanks for taking the time to provide this feedback about the packages.

Regards,

Daniel

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJVcKYNAAoJEOm1uwJp1aqDskUP/j6p35IxvtR9V/VEPjzkQjT6
ckkJsgn5s1cPeJBZJZfYQj/50go68SuMFVPMt2CvA0jvmEdgBcILmHjJ1qCCI6xJ
4zuH4nQu9dHdjcQiVFvFb4QjTn44F3XVKKxGSefNRjrKccPUUfx2rYTtnTjGhCWU
BKiWtCUhLJ3Vo6dCJSWYu5K/5EHBnpCv3k2hClUyECCLwFYMukj2U/P9Cl+xhfb6
m/TSq20BWq94ViQYRSx1uDyCOS1dPWFPa7h9zYluwfUO593DUJFW4sujoI2qPyIA
+PpS0cJ6OzqW7rruJAR4+LRjqqyxK0QDfdKI5v7w2zqd1vDhmZX6PeYh7HKHKLwt
mbFTpjvGGIYuFWFblcNXGFKrjyQlMrq7QpZXxL3KyjKuBTPHSzHWRTVN8DpBvBYg
RuEsRxRa7qrPP582pz3nN3tqtoE55n29PULBLq8ie2ZSo7vrWzu86U3AymOGw/RX
uuDEztxjfqZTruwIFkC05UgGwetVz5jXHS75Y0Rg1OOHlxb7rpzSPkxbe6zlzXdZ
o2IdRp5ABRH/my5hFDJeTNeATtdyxmezR4AM7OHECkTCSnpK0vBygc7ZRTdv5ioi
XU7lA+iucvEVP0O4leoZh5+sCzVIScQkd8zgNCLavbbDC1JURQqzAOb2/73zW9eP
FeNLwkdRyvkiriyiGI2L
=9+Vc
-END PGP SIGNATURE-


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

Bug#787162: g++-mingw-w64-i686: error adding symbols: File format not recognized

[Stephen Kitt]

Salut Mathieu,

On Fri, 29 May 2015 12:19:04 +0200, Mathieu Malaterre 
wrote:
> On Fri, May 29, 2015 at 12:16 PM, Stephen Kitt  wrote:
> > Excellent find, thanks! I agree that it's a nasty bug, I'll leave the
> > severity at important and try to get a fix in a point-release.
> 
> That would be terrific ! Thank you.

Could you try the binaries available on http://sk2.org/mingw-w64/ to make
sure they work with your libraries? They would be the candidates for a stable
upload.

Thanks,

Stephen


pgp0OSmKLvyrs.pgp
Description: OpenPGP digital signature