Breno Leitao | 22 Jul 16:39 2014
Picon

Bug#706185: (no subject)

Hi,

This is the third version of the patch, addressing some concerns by Helmut. The
changelog compared to the version two is:

 - Created a entry in the changelog
 - Fixes the patch directory, so, now you can apply with patch using -p1 instead
of -p2.

Thanks
Breno
Index: libpam-ldap-184/debian/changelog
===================================================================
--- libpam-ldap-184.orig/debian/changelog
+++ libpam-ldap-184/debian/changelog
 <at>  <at>  -1,3 +1,11  <at>  <at> 
+libpam-ldap (184-8.7) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Do not remove config files when removing the package from one architecture
+    in a multiarch environemnt.  Closes: 706185
+
+ -- Breno Leitao <brenohl <at> br.ibm.com>  Tue, 22 Jul 2014 14:31:57 +0000
+
 libpam-ldap (184-8.6) unstable; urgency=low

   * Non-maintainer upload.
Index: libpam-ldap-184/debian/libpam-ldap.postrm
(Continue reading)

Debian Bug Tracking System | 22 Jul 16:33 2014
Picon

Processed: severity of 755684 is serious

Processing commands for control <at> bugs.debian.org:

> # actually caused by twisted
> severity 755684 serious
Bug #755684 [torbrowser-launcher] torbrowser-launcher: cannot launch the Tor Browser
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
--

-- 
755684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755684
Debian Bug Tracking System
Contact owner <at> bugs.debian.org with problems

Debian Bug Tracking System | 22 Jul 16:24 2014
Picon

Processed: severity of 755684 is important

Processing commands for control <at> bugs.debian.org:

> # apparently not reproducible everywhere
> severity 755684 important
Bug #755684 [torbrowser-launcher] torbrowser-launcher: cannot launch the Tor Browser
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
--

-- 
755684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755684
Debian Bug Tracking System
Contact owner <at> bugs.debian.org with problems

Vlad Orlov | 22 Jul 16:06 2014
Picon

Bug#754220: virtualbox: FTBFS with GCC 4.9 as default

I see there's a new fixed version waiting at http://mentors.debian.net/package/virtualbox
Aaron M. Ucko | 22 Jul 16:03 2014
Picon

Bug#755698: libcutl: FTBFS on non-amd64: symbols not fully as expected

Source: libcutl
Version: 1.8.0+ds1-1
Severity: serious
Justification: fails to build from source

Builds of libcutl for non-amd64 processors have been failing with
mismatches in precise C++ symbol names, as detailed at 

https://buildd.debian.org/status/logs.php?pkg=libcutl&ver=1.8.0%2Bds1-1&suite=sid

Could you please account for these differences?

Thanks!

Michael Biebl | 22 Jul 15:39 2014
Picon

Bug#755274: bluez: BT adapter isn't powered on at boot

Instead of having each udev rule having to work around this issue, it
would be much better to simply mount /usr via the initramfs and
discourage the use of a separate /usr partition.
dracut can already do that, for initramfs-tools there is [1].

As a reality check you might be interested in the attached list.

Cheers,
Michael

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652459
--

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
alsa-utils/rules.d/90-alsa-restore.rules:ACTION=="add", SUBSYSTEM=="sound",
KERNEL=="controlC*", KERNELS!="card*", TEST=="/usr/sbin", TEST=="/usr/share/alsa", GOTO="alsa_restore_go"
alsa-utils/rules.d/90-alsa-restore.rules:TEST!="/etc/alsa/state-daemon.conf",
RUN+="/usr/sbin/alsactl -E HOME=/var/run/alsa restore $attr{device/number}"
alsa-utils/rules.d/90-alsa-restore.rules:TEST=="/etc/alsa/state-daemon.conf",
RUN+="/usr/sbin/alsactl -E HOME=/var/run/alsa nrestore $attr{device/number}"
barry-util/rules.d/10-blackberry.rules:	RUN="/usr/sbin/bcharge -p %p"
barry-util/rules.d/10-blackberry.rules:	RUN="/usr/sbin/bcharge -d"
barry-util/rules.d/10-blackberry.rules:	RUN="/usr/sbin/bcharge -g -p %p"
barry-util/rules.d/10-blackberry.rules:	RUN="/usr/sbin/bcharge -g -p %p"
barry-util/rules.d/10-blackberry.rules:	RUN="/usr/sbin/bcharge -g -p %p"
barry-util/rules.d/10-blackberry.rules:	RUN="/usr/sbin/bcharge -p %p"
bilibop-rules/rules.d/66-bilibop.rules:# you can run
/usr/share/bilibop/bilibop_rules_generator to create a
(Continue reading)

Debian Bug Tracking System | 22 Jul 15:15 2014
Picon

Processed: Forcemerging 749853 into 749853

Processing commands for control <at> bugs.debian.org:

> forcemerge 749853 754893
Bug #749853 [wysihtml-el] wysihtml-el: fails to upgrade from wheezy
Bug #754893 [wysihtml-el] wysihtml-el: on upgrade from wheezy to jessie chokes on compilation causing
emacs and list package upgrades to fail
Severity set to 'serious' from 'normal'
Marked as found in versions wysihtml/0.13-5.1.
Added tag(s) sid, jessie, and patch.
Bug #749853 [wysihtml-el] wysihtml-el: fails to upgrade from wheezy
Added tag(s) unreproducible.
Merged 749853 754893
>
End of message, stopping processing here.

Please contact me if you need assistance.
--

-- 
749853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749853
754893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754893
Debian Bug Tracking System
Contact owner <at> bugs.debian.org with problems

Debian Bug Tracking System | 22 Jul 14:57 2014
Picon

Processed: forcibly merging 755067 755476

Processing commands for control <at> bugs.debian.org:

> forcemerge 755067 755476
Bug #755067 [virtualbox-guest-x11] xserver-xorg-core upgrade wants to remove virtualbox-guest-x11
due to incompatible ABI version
Bug #755476 [virtualbox-guest-x11] virtualbox-guest-x11 depends on xorg-video-abi-15 which isn't in repository
Severity set to 'serious' from 'important'
Merged 755067 755476
> thanks
Stopping processing here.

Please contact me if you need assistance.
--

-- 
755067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755067
755476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755476
Debian Bug Tracking System
Contact owner <at> bugs.debian.org with problems

Gerrit Pape | 22 Jul 14:34 2014

Bug#752075: daemontools-run: Add systemd support

On Fri, Jul 18, 2014 at 12:03:41PM +0000, Gerrit Pape wrote:
> I'm really not keen to add a dependency to daemontools-run, esp. not to
> the runit package, just for (un)installing and starting/stopping a
> service.

Hi, I've now prepared this changeset.  Do you have any comments on it?

Author: Gerrit Pape <pape <at> smarden.org>
Date:   Tue Jul 22 12:26:42 2014 +0000

      * debian/systemd/daemontools.path, debian/systemd/daemontools.service:
        new; daemontools-run systemd unit files (thx Michael Biebl, Jonathan de
        Boyne Pollard, Milan P. Stanic).
      * debian/rules: install daemontools-run systemd unit files.
      * debian/daemontools-run.postinst, debian/daemontools-run.postrm: enable
        and start, disable and stop respectively daemontools units if systemd
        is process 1.

diff --git a/debian/changelog b/debian/changelog
index 8d124f4..d2d4efc 100644
--- a/debian/changelog
+++ b/debian/changelog
 <at>  <at>  -1,3 +1,15  <at>  <at> 
+daemontools (1:0.76-3.1) UNRELEASED; urgency=low
+
+  * debian/systemd/daemontools.path, debian/systemd/daemontools.service:
+    new; daemontools-run systemd unit files (thx Michael Biebl, Jonathan de
+    Boyne Pollard, Milan P. Stanic).
+  * debian/rules: install daemontools-run systemd unit files.
+  * debian/daemontools-run.postinst, debian/daemontools-run.postrm: enable
(Continue reading)

Dejan Latinovic | 22 Jul 14:19 2014

Bug#754751: chealpix: FTBFS on mips: E: Caught signal ‘Terminated’: terminating immediately


Hi,

it seams that build of chealpix fails only on Cavium machines.
Even on Cavium, tests execute successfully but
it takes a lot of time.

On Broadcom and Loongson boards,
chealpix builds successfully for me.

The same conclusion could be made from
build logs:
https://buildd.debian.org/status/logs.php?pkg=chealpix

Could we ask for a blacklist chealpix on Cavium boards
corelli, gabrielli and lucatelli?
And ask for a give-back for mips?

Best Regards,
Dejan

Paul Wise | 22 Jul 14:01 2014
Picon

Bug#755684: torbrowser-launcher: cannot launch the Tor Browser

Package: torbrowser-launcher
Version: 0.1.0-1.2
Severity: serious

There is some sort of error with twisted preventing the version check
information from being downloaded, which in turn prevents the Tor
Browser from starting at all.

pabs <at> chianamo ~ $ curl https://check.torproject.org/RecommendedTBBVersions
[
"3.6.2-Linux",
"3.6.2-MacOS",
"3.6.2-Windows"
]
pabs <at> chianamo ~ $ rm -rf .torbrowser/
pabs <at> chianamo ~ $ torbrowser-launcher
/usr/lib/python2.7/dist-packages/twisted/internet/_sslverify.py:184: UserWarning: You do not
have the service_identity module installed. Please install it from
<https://pypi.python.org/pypi/service_identity>. Without the service_identity module and a
recent enough pyOpenSSL tosupport it, Twisted can perform only rudimentary TLS client
hostnameverification.  Many valid certificate/hostname mappings may be rejected.
  verifyHostname, VerificationError = _selectVerifyImplementation()
Tor Browser Launcher
By Micah Lee, licensed under GPLv3
version 0.1.0
https://github.com/micahflee/torbrowser-launcher
Initializing Tor Browser Launcher
Warning: can't load mirrors from /usr/local/share/torbrowser-launcher/mirrors.txt
Creating GnuPG homedir /home/pabs/.torbrowser/gnupg_homedir
Importing keys
(Continue reading)


Gmane