Bug#670437: pygopherd: diff for NMU version 2.0.18.3+nmu4

[gregor herrmann]

On Mon, 08 Dec 2014 17:49:27 -0800, Cameron Norman wrote:

> Unfortunately I have discovered there is an issue in this set of changes.
> The gophermap file is modified by the admin in basically all cases of
> pygopherd being actually used to serve a gopher site. Overwriting it (on
> installation/upgrade) or deleting it (on removal/purge), which this NMU
> does, is deleting the data of the site.

Oh, good catch; sorry for missing this aspect.
I'll cancel the NMU later today.
 
> I have supplied a more minimal NMU to fix #771501 that does not mess with
> the gophermap file other than installing it if it was not there before.

Where is this new patch? It seems that I don't see it right now :)
 
> I will hopefully address the unowned file issue (#670437) in a later set of
> changes.

Ack.
 
> Thanks for sponsoring the first upload, Gregor.

Thanks for providing the patch(es) in the first place!


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   BOFH excuse #191:  Just type 'mv * /dev/null'. 


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

Bug#772615: mpv: incorrect aspect ratio

[Ritesh Raj Sarraf]

Package: mpv
Version: 0.7.1-1+ffmpeg
Severity: important

With this new release, the aspect raito of the video is completely
broken. I have verified the same video with mplayer and it renders
correct.


The same video worked fine with mpv version: 0.6.2+ffmpeg

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.17.0-trunk-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: sysvinit (via /sbin/init)

Versions of packages mpv depends on:
ii  libasound2  1.0.28-1
ii  libass5 0.10.2-3
ii  libavcodec-ffmpeg56 7:2.5-1
ii  libavdevice-ffmpeg567:2.5-1
ii  libavfilter-ffmpeg5 7:2.5-1
ii  libavformat-ffmpeg567:2.5-1
ii  libavresample-ffmpeg2   7:2.5-1
ii  libavutil-ffmpeg54  7:2.5-1
ii  libbs2b03.1.0+dfsg-2.1
ii  libc6   2.19-13
ii  libcdio-cdda1   0.83-4.2
ii  libcdio-paranoia1   0.83-4.2
ii  libcdio13   0.83-4.2
ii  libdvdnav4  5.0.1-1
ii  libdvdread4 5.0.0-1
ii  libegl1-mesa [libegl1-x11]  10.3.2-1
ii  libenca01.16-1
ii  libgl1-mesa-glx [libgl1]10.3.2-1
ii  libguess1   1.2-1
ii  libjack-jackd2-0 [libjack-0.116]1.9.10+20140719git3eb0ae6a~dfsg-2
ii  libjpeg62-turbo 1:1.3.1-11
ii  liblcms2-2  2.6-3+b3
ii  liblircclient0  0.9.0~pre1-1.1
ii  liblua5.2-0 5.2.3-1.1
ii  libmpg123-0 1.20.1-2
ii  libpostproc-ffmpeg537:2.5-1
ii  libpulse0   5.0-13
ii  libsdl2-2.0-0   2.0.2+dfsg1-6
ii  libswscale-ffmpeg3  7:2.5-1
ii  libuuid12.25.2-3
ii  libva-glx1  1.4.1-1
ii  libva-x11-1 1.4.1-1
ii  libva1  1.4.1-1
ii  libvdpau1   0.8-3
ii  libwayland-client0  1.6.0-2
ii  libwayland-cursor0  1.6.0-2
ii  libwayland-egl1-mesa [libwayland-egl1]  10.3.2-1
ii  libx11-62:1.6.2-3
ii  libxext62:1.3.3-1
ii  libxinerama12:1.1.3-1+b1
ii  libxkbcommon0   0.4.3-2
ii  libxrandr2  2:1.4.2-1+b1
ii  libxss1 1:1.2.2-1
ii  libxv1  2:1.0.10-1+b1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages mpv recommends:
ii  youtube-dl  2014.08.05-1

mpv 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#768730: python-mne REMOVED from testing

[Andreas Tille]

Hi,

seems we waitet to long. :-(

Yaroslav, would you be willing / able to sort things out with the
release team since my backlog from vacation is to heavy to try to
get this back into testing (if possible at all).

Kind regards

   Andreas.

On Mon, Dec 08, 2014 at 04:39:20PM +, Debian testing watch wrote:
> FYI: The status of the python-mne source package
> in Debian's testing distribution has changed.
> 
>   Previous version: 0.8.4+dfsg-1
>   Current version:  (not in testing)
>   Hint: 
> Bug #768730: python-mne: FTBFS in jessie: Tests failures
> 
> The script that generates this mail tries to extract removal
> reasons from comments in the britney hint files. Those comments
> were not originally meant to be machine readable, so if the
> reason for removing your package seems to be nonsense, it is
> probably the reporting script that got confused. Please check the
> actual hints file before you complain about meaningless removals.
> 
> -- 
> This email is automatically generated once a day.  As the installation of
> new packages into testing happens multiple times a day you will receive
> later changes on the next day.
> See https://release.debian.org/testing-watch/ for more information.
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de


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

Bug#772614: RFS: qgis/2.6.1-1~exp1

[Bas Couwenberg]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "qgis"

 Package name: qgis
 Version : 2.6.1-1~exp1
 Upstream Author : qgis-develo...@lists.osgeo.org
 URL : http://qgis.org/
 License : GPL-2+
 Section : science

It builds those binary packages:

 qgis - Geographic Information System (GIS)
 qgis-common  - QGIS - architecture-independent data
 libqgis-core2.6.1- QGIS - shared core library
 libqgis-gui2.6.1 - QGIS - shared gui library
 libqgis-analysis2.6.1- QGIS - shared analysis library
 libqgis-networkanalysis2.6.1 - QGIS - shared network analysis library
 libqgisgrass2.6.1- QGIS - shared grass library
 libqgispython2.6.1   - QGIS - shared Python library
 libqgis-customwidgets2.6.1   - QGIS custom widgets for Qt Designer
 libqgis-dev  - QGIS - development files
 qgis-plugin-grass- GRASS plugin for QGIS
 qgis-plugin-grass-common - GRASS plugin for QGIS - 
architecture-independent data
 qgis-plugin-globe- OSG globe plugin for QGIS
 qgis-plugin-globe-common - OSG globe plugin for QGIS - 
architecture-independent data
 python-qgis  - Python bindings to QGIS
 python-qgis-common   - Python bindings to QGIS - 
architecture-independent files
 qgis-providers   - collection of data providers to QGIS
 qgis-providers-common- collection of data providers to QGIS - 
architecture-independent files
 qgis-server  - QGIS server providing various OGC services
 qgis-api-doc - QGIS API documentation

To access further information about this package, please visit the following 
URL:

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


Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/main/q/qgis/qgis_2.6.1-1~exp1.dsc

More information about QGIS can be obtained from http://qgis.org/.

Changes since the last upload:

  [ Jürgen E. Fischer ]
  * Release of 2.6.1

  [ Bas Couwenberg ]
  * New upstream release.
  * Add upstream metadata.
  * Refresh patches.
  * Update symbols for amd64.
  * Replace qgis-mapserver by qgis-server using Provides/Conflicts/Replaces.
  * Add patch from release-2_6 branch to fix layer selection issue.


Regards,
 Bas Couwenberg


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

Bug#772444: libsixel: missing debian/watch

[NOKUBI Takatsugu]

At Sun, 07 Dec 2014 14:17:34 +0900 (JST),
Tatsuya Kinoshita wrote:
> --- /dev/null
> +++ b/debian/watch
> @@ -0,0 +1,2 @@
> +version=3
> +http://githubredir.debian.net/github/saitoha/libsixel /v(\d.*)\.tar\.gz

githubredir.debian.net is obsolete, so I'll add github style watch file.
https://wiki.debian.org/debian/watch/#GitHub

> BTW, I have merged arakiken's w3m remoteimg branch to Debian's w3m
> to support the -sixel option using the img2sixel command provided
> by your libsixel package.

It sounds good.


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

Bug#772607: tor: Tor fails to start at boot

[Peter Palfrader]

On Mon, 08 Dec 2014, Matt Kraai wrote:

> When I boot my system, Tor fails to start automatically.  I haven't been able
> to find much additional information, and it does start if I run either of the
> following commands manually:
> 
>  * sudo systemctl start tor.service
>  * sudo /etc/init.d/tor start
> 
> Here are the only lines relevant to this I could find in /var/log/syslog:
> 
>  Dec  8 20:29:20 hpe-490t systemd[1]: tor.service: control process exited,
> code=exited status=1
>  Dec  8 20:29:20 hpe-490t systemd[1]: Failed to start LSB: Starts The Onion
> Router daemon processes.
>  Dec  8 20:29:20 hpe-490t systemd[1]: Unit tor.service entered failed state.
> 
> I don't see anything related to this in /var/log/tor/log.

What does 'service tor status' say?

-- 
   |  .''`.   ** Debian **
  Peter Palfrader  | : :' :  The  universal
 http://www.palfrader.org/ | `. `'  Operating System
   |   `-http://www.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#772613: python-apt: apt_pkg.Dependency().target_pkg should be native version for multi-arch: Foreign

[Russell Stuart]

Package: python-apt Version: 0.9.3.11 Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

apt_pkg.Dependency objects returned by apt_pkg.Version.depends_list
select a apt_pkg.Dependency.target_pkg that has the same architecture
as the apt_pkg.Version that generated it (Architecture: all packages
aside).  Usually this is the right thing do to.

The one time is isn't is when target_pkg is "multi-arch: Foreign".
In that case you always want the native package, if it is available.

Eg consider a system that wants both libgcc1:amd64 and libgcc1:i386
installed.  libgcc1 PreDepends on multiarch-support.
multiarch-support:amd64 conflicts with multiarch-support:i386, so
you can't have both installed.  But currently if you just use the
suggested target_pkg, you will attempt to install both.  apt-get and
aptitude resolve this by only installing the native version, and it
would be nice if apk_pkg did the same.

Example:

  import apt_pkg
  apt_pkg.init()
  cache = apt_pkg.Cache()
  dep_cache = apt_pkg.DepCache(cache)
  libgcc1_i386 = cache["libgcc1:i386"]
  version = dep_cache.get_candidate_ver(libgcc1_i386)
  depends = version.depends_list["PreDepends"][0][0]
  target_pkg = depends.target_pkg
  print target_pkg.name, target_pkg.architecture
  print depends.all_targets()[0].multi_arch == 
apt_pkg.Version.MULTI_ARCH_FOREIGN
  print cache["multiarch-support"].architecture, cache["dpkg"].architecture

Prints:
  multiarch-support i386
  True
  amd64 amd64

A better result would be:
  multiarch-support amd64
  True
  amd64 amd64

- -- System Information: Debian Release: 8.0
  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/4 CPU cores) Locale: LANG=en_AU.UTF-8, 
LC_CTYPE=en_AU.UTF-8 
(charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via 
/run/systemd/system)

Versions of packages python-apt depends on: ii libapt-inst1.5 1.0.9.3 ii 
libapt-pkg4.12 1.0.9.3 ii 
libc6 2.19-13 ii libgcc1 1:4.9.1-19 ii libstdc++6 4.9.1-19 ii python 2.7.8-2 ii 
python-apt-common 
0.9.3.11

Versions of packages python-apt recommends: ii iso-codes 3.57-1 ii lsb-release 
4.1+Debian13+nmu1 ii 
xz-utils 5.1.1alpha+20120614-2+b2

Versions of packages python-apt suggests: pn python-apt-dbg  ii 
python-apt-doc 0.9.3.11 ii 
python-gtk2 2.24.0-4 pn python-vte 

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBVIadxqzUn4heVFJuAQpMRA/+P30MjoHRHz6BvVQW74LSUk+GZdO+mW62
yE5+Zp8jahDIaM6bg0CXnItfRI53jFRteQIxTVUBi3WUdQi5lMRxyRvkH523na3U
apln9Juxdr5O8gu2WsPA2Aasv3sR1sD8+19BAQwYWtuqxisglV3ZG8v/pcV7wdVk
lGX2vYgw3nhao1Ad9jmV8oIxLvkhK7OhxBe9F8oaf8PhsUfWuJulxWwM3COxe6SE
igo3mzjfDHY8dvtdXndac0ZVXE6CKd2TPQtRslqPOEjiGvp/9E7O3Q8Rul+92NQi
H4G6XJ2wgyKSB6yLnClvHKS+LOSNoPTvGsy6cAQ/TQk2qCDcKE8/HgUa555TdTyz
sxmYywPt+2MiB+OzpqqSmIaPch4vclpce0lwD83jS0lWqe2PH+tHFnv8jVc/aWkg
iiT+w6qLHWtArqH+hX/hn/R+ObkSvy+dsvAvpCfGdJwukIo12LIRuPQ//HUw2drH
4ya+JTLd+LqlzrVVUMlzpCaXnXXew+54P8TuhUU7ZMjGpaI25XVYxVry9hY52OR5
tkazM0bF8jOsnPaS/a9rKY5IS4NsaD8ahpTqNVqNmvHh0BCOdEzMGUOGTEu2MjjN
hKAaxdaGKWVhbZY23aMZWQ9AtycNMk96t78Lk1czRmrEb2z48+66Ge5d82Z2z5ah
SxPbjHLmGk4=
=hwNm
-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#772612: kmail: Sent message opened for editing by default and can be removed from sent by saving

[Shai Berger]

Package: kmail
Version: 4:4.14.2-2
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

Double-click a message in any folder; unlike in kmail1, the message
opens as editable (in kmail1 this was only true for Outbox).

However, if the message is opened from the sent-mail folder, then --
just like with outbox -- it is also removed from the list. When you
close the message, as with any editable, you are offered to discard
the changes or save as draft. If you discard, all is well; but if
you save as draft, it is removed permanently from the sent folder,
losing the data that the message was sent.


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

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

Versions of packages kmail depends on:
ii  kde-runtime   4:4.14.2-1
ii  kdepim-runtime4:4.14.2-2
ii  kdepimlibs-kio-plugins4:4.14.2-2
ii  libakonadi-calendar4  4:4.14.2-2
ii  libakonadi-contact4   4:4.14.2-2
ii  libakonadi-kde4   4:4.14.2-2
ii  libakonadi-kmime4 4:4.14.2-2
ii  libakonadiprotocolinternals1  1.13.0-2
ii  libc6 2.19-13
ii  libcalendarsupport4   4:4.14.2-2
ii  libfollowupreminder4  4:4.14.2-2
ii  libgcc1   1:4.9.2-5
ii  libgpgme++2   4:4.14.2-2
ii  libgrantlee-core0 0.4.0-2
ii  libincidenceeditorsng44:4.14.2-2
ii  libkabc4  4:4.14.2-2
ii  libkalarmcal2 4:4.14.2-2
ii  libkcalcore4  4:4.14.2-2
ii  libkcalutils4 4:4.14.2-2
ii  libkcmutils4  4:4.14.2-4
ii  libkdecore5   4:4.14.2-4
ii  libkdepim44:4.14.2-2
ii  libkdeui5 4:4.14.2-4
ii  libkio5   4:4.14.2-4
ii  libkleo4  4:4.14.2-2
ii  libkmanagesieve4  4:4.14.2-2
ii  libkmime4 4:4.14.2-2
ii  libknewstuff3-4   4:4.14.2-4
ii  libknotifyconfig4 4:4.14.2-4
ii  libkontactinterface4a 4:4.14.2-2
ii  libkparts44:4.14.2-4
ii  libkpgp4  4:4.14.2-2
ii  libkpimidentities44:4.14.2-2
ii  libkpimtextedit4  4:4.14.2-2
ii  libkpimutils4 4:4.14.2-2
ii  libkprintutils4   4:4.14.2-4
ii  libksieveui4  4:4.14.2-2
ii  libktnef4 4:4.14.2-2
ii  libmailcommon44:4.14.2-2
ii  libmailimporter4  4:4.14.2-2
ii  libmailtransport4 4:4.14.2-2
ii  libmessagecomposer4   4:4.14.2-2
ii  libmessagecore4   4:4.14.2-2
ii  libmessagelist4   4:4.14.2-2
ii  libmessageviewer4 4:4.14.2-2
ii  libpimcommon4 4:4.14.2-2
ii  libqt4-dbus   4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1
ii  libqtwebkit4  2.3.4.dfsg-3
ii  libsendlater4 4:4.14.2-2
ii  libsolid4 4:4.14.2-4
ii  libstdc++64.9.2-5
ii  libtemplateparser44:4.14.2-2
ii  perl  5.20.1-3

Versions of packages kmail recommends:
ii  gnupg-agent   2.0.26-3
ii  gnupg22.0.26-3
ii  pinentry-gtk2 [pinentry-x11]  0.8.3-2

Versions of packages kmail suggests:
ii  bogofilter 1.2.4+dfsg1-3
pn  clamav | f-prot-installer  
ii  kaddressbook   4:4.14.2-2
pn  kleopatra  
ii  procmail   3.22-23
ii  spambayes  1.1b1-1

-- 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#772611: horae: build-depend on libpod-latex-perl to fix FTBFS

[Carlo Segre]

will do

On Tue, 9 Dec 2014, Logan Rosen wrote:


Package: horae
Version: 071~svn537-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch

Dear Maintainer,

horae currently FTBFS on amd64 (and presumably i386 as well) due to a missing 
build dependency on libpod-latex-perl.

Here is the relevant extract from the build log:

# Generate man pages for artemis only
cd lib/Ifeffit/lib/artemis.doc ; ./make_doc --man
Can't locate Pod/LaTeX.pm in @INC (you may need to install the Pod::LaTeX 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.1 
/usr/local/share/perl/5.20.1 /usr/lib/x86_64-linux-gnu/perl5/5.20 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 
/usr/local/lib/site_perl .) at ./make_doc line 93.
BEGIN failed--compilation aborted at ./make_doc line 93.
debian/rules:29: recipe for target 'build-stamp' failed

In Ubuntu, the attached patch was applied to achieve the following:

 * Build-depend on libpod-latex-perl to fix FTBFS.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: jessie/sid
 APT prefers vivid-updates
 APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-25-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



--
Carlo U. Segre -- Duchossois Leadership Professor of Physics
Director, Center for Synchrotron Radiation Research and Instrumentation
Illinois Institute of Technology
Voice: 312.567.3498Fax: 312.567.3494
se...@iit.edu   http://phys.iit.edu/~segre   se...@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#769760: [libjpeg62-turbo] Upgrading libjpeg62-turbo will remove most of the installed KDE packages

[Bogdan Vatra]

Hello,

Please close this bug, I managed to upgrade it.
I did some dirty tricks (forced removed old libjpeg62* libs using dpkg, and 
manually install the new ones), but in the end I fixed it.

Cheers,
BogDan.


On Wednesday 19 November 2014 09:27:49 Ondřej Surý wrote:
> Where does your KDE come from? It probably doesn't come from jessie,
> right?
> 
> Cheers,
> Ondrej
> 
> On Wed, Nov 19, 2014, at 09:24, Bogdan Vatra wrote:
> > It wants to remove most of my KDE packages.
> > 
> > Cheers,
> > BogDan.
> > 
> > On Wednesday 19 November 2014 09:18:15 Ondřej Surý wrote:
> > > What does "apt-get remove libjpeg62" says?
> > > 
> > > Cheers,
> > > Ondrej
> > > 
> > > On Wed, Nov 19, 2014, at 07:53, Bogdan Vatra wrote:
> > > > Hi,
> > > > 
> > > > apt-get has the same problem.Actually I'm always using apt-get, I used
> > > > aptitude because it produce more verbose output. If there is nothing
> > > > wrong
> > > > with libjpeg62-turbo can you pretty please point me to another
> > > > direction?
> > > > 
> > > > Cheers,
> > > > BogDan.
> > > > 
> > > > On Monday 17 November 2014 20:19:53 Ondřej Surý wrote:
> > > > > Control: severity -1 minor
> > > > > 
> > > > > Hi,
> > > > > 
> > > > > retry with plain apt-get and report back. This is not a bug in a
> > > > > libjpeg62-turbo, but in the application that's not recompiled
> > > > > against
> > > > > new version of libjpeg-dev and thus it still depends on libjpeg62.
> > > > > Or
> > > > > it's just aptitude resolver being wrong (again).
> > > > > 
> > > > > You can also use grep-dctrl to find affected package, search for
> > > > > "Depends: libjpeg62 (".
> > > > > 
> > > > > There's definitely nothing wrong with src:libjpeg-turbo packaging
> > > > > wise
> > > > > now.
> > > > > 
> > > > > Cheers,
> > > > > Ondrej
> > > > > 
> > > > > On Sun, Nov 16, 2014, at 09:52, Bogdan Vatra wrote:
> > > > > > Package: libjpeg62-turbo
> > > > > > Severity: important
> > > > > > 
> > > > > > --- Please enter the report below this line. ---
> > > > > > When I try to upgrade this package, apt-get wants to remove most
> > > > > > of
> > > > > > the
> > > > > > KDE
> > > > > > packages.
> > > > > > I attached the aptitude output.
> > > > > > 
> > > > > > 
> > > > > > --- System information. ---
> > > > > > Architecture: amd64
> > > > > > Kernel:   Linux 3.16.0-4-amd64
> > > > > > 
> > > > > > Debian Release: jessie/sid
> > > > > > 
> > > > > >   500 unstableftp.ro.debian.org
> > > > > >   500 stable  dl.google.com
> > > > > >   500 sid-pgdgapt.postgresql.org
> > > > > > 
> > > > > > --- Package information. ---
> > > > > > Package's Depends field is empty.
> > > > > > 
> > > > > > Package's Recommends field is empty.
> > > > > > 
> > > > > > Package's Suggests field is empty.
> > > > > > Email had 1 attachment:
> > > > > > + aptitude_output.txt
> > > > > > 
> > > > > >   5k (text/plain)


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

Bug#772611: horae: build-depend on libpod-latex-perl to fix FTBFS

[Logan Rosen]

Package: horae
Version: 071~svn537-1
Severity: serious
Tags: patch
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch

Dear Maintainer,

horae currently FTBFS on amd64 (and presumably i386 as well) due to a missing 
build dependency on libpod-latex-perl.

Here is the relevant extract from the build log:

# Generate man pages for artemis only
cd lib/Ifeffit/lib/artemis.doc ; ./make_doc --man
Can't locate Pod/LaTeX.pm in @INC (you may need to install the Pod::LaTeX 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.1 
/usr/local/share/perl/5.20.1 /usr/lib/x86_64-linux-gnu/perl5/5.20 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 
/usr/local/lib/site_perl .) at ./make_doc line 93.
BEGIN failed--compilation aborted at ./make_doc line 93.
debian/rules:29: recipe for target 'build-stamp' failed

In Ubuntu, the attached patch was applied to achieve the following:

  * Build-depend on libpod-latex-perl to fix FTBFS.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-25-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru horae-071~svn537/debian/control horae-071~svn537/debian/control
--- horae-071~svn537/debian/control	2014-11-27 00:45:07.0 -0500
+++ horae-071~svn537/debian/control	2014-12-09 01:41:19.0 -0500
@@ -4,7 +4,7 @@
 Maintainer: Carlo Segre 
 Build-Depends: debhelper (>= 7)
 Build-Depends-Indep: perl (>= 5.6.0-16), libchemistry-elements-perl, 
- perl-tk (>= 804), libifeffit-perl
+ perl-tk (>= 804), libifeffit-perl, libpod-latex-perl
 Homepage: http://cars9.uchicago.edu/~ravel/software/Welcome.html
 Standards-Version: 3.9.6
 

Bug#611380:

[Aakash Patil]

direct use of put -r not possible... directories are needed to be created
first...problem solved...


cheers
-Aakash :-)

Bug#772571: powertop uses /usr/sbin/hciconfig instead of /bin/hciconfig

[Jose-Luis Rivas]

tags 772571 confirmed upstream
quit

On 08/12/14, 06:21pm, Laurent Bigonville wrote:
> Package: powertop
> Version: 2.6.1-1
> Severity: normal
> 
> Hi,
> 
> It seems that powertop uses /usr/sbin/hciconfig instead of
> /bin/hciconfig when it tries to optimize the bluetooth power usage on
> the "Tunables" tab.
> 
> It path should be fixed and executables should maybe looked inside PATH
> instead of hardcoding the path like that

ACK, working on a patch for it.

Thanks for the report.

-- 
⨳ GPG 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co


signature.asc
Description: Digital signature

Bug#770627: dbus: Please (consider) switch(ing) to no-await triggers

[Guillem Jover]

Hi!

On Sun, 2014-12-07 at 14:01:51 +0100, Niels Thykier wrote:
> On 2014-12-05 05:20, Guillem Jover wrote:
> > Given this, the only options seem to be to possibly change the
> > --force-configure-any default to enabled (I'll try to test if this
> > helps in the dbus situation) which I'd rather not do (but oh well),
> > or disable the triggers dependency checks for jessie (and possibly
> > later releases, if apt does not get fixed for jessie) and go back
> > to the previous (broken, but known) behavior. :(

> As I mentioned to David/the APT maintainers, I could be interested in
> having the patch for #769609 in APT.  @Guillem, do you think that will
> deal with the issue?

That would fix the issue with dangling trigger-pending packages, but
I don't think it would fix the dbus issue. I've not tried to check a
dpkg workaround for that yet, sorry. I've got a fix for the nvidia
kernel module one, and asked for access to the ppc system with the pam
module 100% cpu usage bug, to try to confirm that's been fixed in .22,
which I think it does, but would like to make sure.

In any case I think .22 would be an improvement over what's currently
in testing.

Thanks,
Guillem


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

Bug#772610: bind9: CVE-2014-8500: A Defect in Delegation Handling Can Be Exploited to Crash BIND

[Salvatore Bonaccorso]

Source: bind9
Version: 1:9.8.4.dfsg.P1-6
Severity: grave
Tags: security upstream fixed-upstream
Control: fixed -1 1:9.8.4.dfsg.P1-6+nmu2+deb7u3


Hi,

the following vulnerability was published for bind9.

CVE-2014-8500[0]:
A Defect in Delegation Handling Can Be Exploited to Crash BIND

For wheezy-security this was already fixed with DSA-3094-1[1]. See
also [2] for further details.

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-2014-8500
[1] https://lists.debian.org/debian-security-announce/2014/msg00284.html
[2] https://kb.isc.org/article/AA-01216/0

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#772608: unison-gtk: Profile Editor saves empty value

[Gabor Kiss]

Package: unison-gtk
Version: 2.40.65-2
Severity: normal

Dear Maintainer,

I tried to modify an existing profile. I found that if I open
a "text" field the result cannot be saved moreover it becames empty.

Regards

Gabor Kiss

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages unison-gtk depends on:
ii  libatk1.0-0 2.4.0-2
ii  libc6   2.13-38+deb7u6
ii  libcairo2   1.12.2-3
ii  libfontconfig1  2.9.0-7.1
ii  libfreetype62.4.9-1.1
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.33.12+really2.32.4-5
ii  libgtk2.0-0 2.24.10-2
ii  libpango1.0-0   1.30.0-1

Versions of packages unison-gtk recommends:
ii  openssh-client [ssh-client]  1:6.0p1-4+deb7u2
ii  ssh-askpass  1:1.2.4.1-9

Versions of packages unison-gtk suggests:
pn  unison-all-gtk  

-- 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#772609: uhexen2: use autotools-dev to update config.{sub, guess} and fix ppc64el FTBFS

[Logan Rosen]

Package: uhexen2
Version: 1.5.6+dfsg-1
Severity: serious
Tags: patch
Justification: fails to build from source
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch

Dear Maintainer,

Currently, uhexen2 FTBFS on ppc64el because config.guess isn't updated for new 
architectures. This means that TARGET_TRIPLET isn't set, and thus the 
pthread.sh script isn't being called properly, leading to the error in the 
build log.

In Ubuntu, the attached patch was applied to achieve the following:

  * Use autotools-dev to update config.{sub,guess} for new arches.

Thanks for considering the patch.

Logan Rosen

-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-25-generic (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru uhexen2-1.5.6+dfsg/debian/control uhexen2-1.5.6+dfsg/debian/control
--- uhexen2-1.5.6+dfsg/debian/control	2013-10-02 16:30:17.0 -0400
+++ uhexen2-1.5.6+dfsg/debian/control	2014-12-09 00:49:02.0 -0500
@@ -10,7 +10,8 @@
libogg-dev,
libsdl1.2-dev,
libvorbis-dev,
-   nasm
+   nasm,
+   autotools-dev
 Standards-Version: 3.9.4
 Homepage: http://uhexen2.sourceforge.net/
 
diff -Nru uhexen2-1.5.6+dfsg/debian/rules uhexen2-1.5.6+dfsg/debian/rules
--- uhexen2-1.5.6+dfsg/debian/rules	2013-08-23 10:40:24.0 -0400
+++ uhexen2-1.5.6+dfsg/debian/rules	2014-12-09 00:32:16.0 -0500
@@ -9,7 +9,7 @@
 include /usr/share/dpkg/buildflags.mk
 
 %:
-	dh $@
+	dh $@ --with autotools_dev
 
 override_dh_auto_build:
 	# Build the main game binaries

Bug#771092: libuuid1: moreinfo

[Niels Thykier]

On 2014-12-08 15:27, Andreas Henriksson wrote:
> Hello Niels Thykier.
> 
> Thanks for following up on this bug report...
> 
> On Mon, Dec 08, 2014 at 08:36:36AM +0100, Niels Thykier wrote:
>> [...]
>>
>> In both cases, the condition for the ifs seems to be false.
> 
> In the failing build logs the condition is true and it explodes
> because of groupmod not yet existing, so your issue seems unrelated
> to what I'm looking for information on.
> 

Fair enough.  I was trying to make the case that the script not
indempotent in its clean up and it may have caused the issue.  But
certainly, I see your point.

> The buildd chroot upgrade seems to run the migration code and then
> somehow throw away all the resulting user/group modifications, so that
> on next package upgrade the migration runs again (and again, ...).
> 

This seems like plausible explanation given we tend to use throw-away
chroots or lvm-snapshots.  So if this problem only appears on buildds
(or in other throw-ways environments), I guess you are just missing a
Depends after all.

We can have the buildds upgraded post Jessie, before you remove the
migration code.  I cannot recommend it now, as gcc has a new version in
unstable that could cause issues for other packages (that could pick up
a dependency on the newer gcc).

>>  But:
>>
>>
>> """
>> $ getent group libuuid >/dev/null && echo "group libuuid present"; \
>>   getent group uuidd >/dev/null && echo "group uuidd present"
>> group uuidd present
>> $ getent group libuuid >/dev/null && ! getent group uuidd >/dev/null
>> $ getent passwd libuuid >/dev/null ; echo "User libuuid present" ; \
>>   getent passwd uuidd >/dev/null && echo "User uuidd present"
>> User libuuid present
>> User uuidd present
>> $ getent passwd libuuid >/dev/null && ! getent passwd uuidd \
>>  >/dev/null  && echo "true"
>> """
>>
>> I "only" have /group/ uuidd, but I have both users present!?
> 
> I'm not sure how that happened, but it is only a minor issue.
> The migration code checks that both the old user/group exists
> and new user/group not exists, so if both exists it's not a
> problem. Ofcourse it's not nice to leave old cruft around...
> 
> [...]
> 

Okay, thanks for clarifying.  Given you believe it is only a minor cruft
issue, it is not a priority for me for Jessie (unless it is last call
for getting it fixed).  :)
  I am certainly ready to look into this for Stretch (or, Jessie, if
needed).

>> Inside the user migration, there is a remark that usermod will fail if
>> the process is running.  Does that hold for groupmod as well?
> 
> This remark comes from ubuntu users running into that problem.
> If the same where true for groupmod, the (launchpad) bug report
> for it would probably have said groupmod instead of usermod
> as groupmod is run first. So my guess is no.
> 
> 
> Regards,
> Andreas Henriksson
> 

Ack, thanks.

~Niels


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

Bug#772107: unblock: bind-dyndb-ldap/6.0-4

[Timo Aaltonen]

On 06.12.2014 19:40, Ivo De Decker wrote:
> Control: tags -1 moreinfo
> 
> Hi,
> 
> On Fri, Dec 05, 2014 at 10:10:29AM +0200, Timo Aaltonen wrote:
>> Please unblock package bind-dyndb-ldap
>>
>> It has no reverse deps in jessie to break, freeipa-server is the only one
>> which isn't there. Unblocking would make it one less package to backport.
> 
> This isn't a good reason for an unblock. There is no information about why
> this unblock is necessary. There are no bug reports about the issues that are
> fixed.

That's because I fixed them before anyone filed bugs.

> If the package is only used for freeipa-server, and it's not in good shape for
> jessie, it might make more sense to remove it.

That's certainly one way of looking at it. I'd say that 30 days without
further changes (or bugs) means that -4 is fine for jessie.


-- 
t


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

Bug#772607: tor: Tor fails to start at boot

[Matt Kraai]

Package: tor
Version: 0.2.5.10-1
Severity: normal

Hi,

When I boot my system, Tor fails to start automatically.  I haven't been able
to find much additional information, and it does start if I run either of the
following commands manually:

 * sudo systemctl start tor.service
 * sudo /etc/init.d/tor start

Here are the only lines relevant to this I could find in /var/log/syslog:

 Dec  8 20:29:20 hpe-490t systemd[1]: tor.service: control process exited,
code=exited status=1
 Dec  8 20:29:20 hpe-490t systemd[1]: Failed to start LSB: Starts The Onion
Router daemon processes.
 Dec  8 20:29:20 hpe-490t systemd[1]: Unit tor.service entered failed state.

I don't see anything related to this in /var/log/tor/log.



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/12 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 tor depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.19-13
ii  libevent-2.0-5  2.0.21-stable-1.1
ii  libseccomp2 2.1.1-1
ii  libssl1.0.0 1.0.1j-1
ii  lsb-base4.1+Debian13+nmu1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages tor recommends:
ii  logrotate3.8.7-1+b1
ii  tor-geoipdb  0.2.5.10-1
ii  torsocks 2.0.0-3

Versions of packages tor suggests:
pn  apparmor-utils 
pn  mixmaster  
pn  obfsproxy  
pn  polipo | privoxy   
pn  socat  
pn  tor-arm
pn  xul-ext-torbutton  

-- Configuration Files:
/etc/tor/torrc changed [not included]

-- 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#772605: src:python-click: FTBFS due to assertion errors in tests

[Alexandre Viau]

Indeed it is.

I will try your suggestion and push a patch.


On 09/12/14 12:09 AM, Logan Rosen wrote:
> Hi Alexandre,
> 
> On Mon, Dec 8, 2014 at 11:21 PM, Alexandre
> Viau  > wrote:
> 
> Since this is a limitation of the library, I suggest we skip the tests
> when building for python2.
> 
> What do you think?
> 
> 
> I was able to fix the failing tests by adding the following exports to
> debian/rules, as suggested on the linked page from the asserts:
> export LC_ALL=C.UTF-8
> export LANG=C.UTF-8
> 
> I think this is a better solution than disabling the tests altogether. :)
> 
> Thanks,
> Logan

-- 
Alexandre Viau
alexan...@alexandreviau.net



signature.asc
Description: OpenPGP digital signature

Bug#772605: src:python-click: FTBFS due to assertion errors in tests

[Logan Rosen]

Hi Alexandre,

On Mon, Dec 8, 2014 at 11:21 PM, Alexandre Viau  wrote:
>
> Since this is a limitation of the library, I suggest we skip the tests
> when building for python2.
>
> What do you think?


I was able to fix the failing tests by adding the following exports to
debian/rules, as suggested on the linked page from the asserts:
export LC_ALL=C.UTF-8
export LANG=C.UTF-8

I think this is a better solution than disabling the tests altogether. :)

Thanks,
Logan

Bug#769308: marked as done (pre-approval: apt/1.0.9.4)

[Niels Thykier]

On 2014-12-05 22:09, Debian Bug Tracking System wrote:
>> [...]
>>> >>
>>> >> I presume Guillem would be unhappy to carry the workaround to stretch
>>> >> (and we will have to make sure to not forget about it as this path will
>>> >> be mostly untested up until jessie->stretch upgrades are tested),
>>> >> but your call. I haven't given the dpkg change a closer look yet though
>>> >> so it might be nicer/works better than I expect it to be…
>>> >>
>> > 
>> > I could be interested in this patch for Jessie.  However, let me come
>> > back to you on that when I got a better overview of the situation.
>> > 
>> > [...]
>> >
> I am ready to accept that patch as well, but after apt/1.0.9.4 has migrated.
> 
> ~Niels

Hi,

Version 1.0.9.4 of APT has migrated to testing now.

Would you be so kind as to do a 1.0.9.5 with just this change?

~Niels


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

Bug#772522: live-build 4.0.3-1 does not install casper in ubuntu mode

[jnqnfe]

You're right, LB_INITRAMFS looks to be a much better variable to base
this on. Updated patch attached.
commit 4b7113a839e263ce679f117057f56c6eee75cd9a
Author: jnqnfe 
Date:   Tue Dec 9 04:42:26 2014 +

Fix broken ability to build casper based images due to generating live-boot 
specific live.list.packages file.

diff --git a/scripts/build/config b/scripts/build/config
index e3b1e51..a2485a9 100755
--- a/scripts/build/config
+++ b/scripts/build/config
@@ -1353,22 +1353,27 @@ done
 
 if [ ! -e config/package-lists/live.list.chroot ]
 then
-
-cat > config/package-lists/live.list.chroot << EOF
-live-boot
-live-config
-EOF
-
-case "${LB_PARENT_DISTRIBUTION}" in
-   wheezy)
-   echo "live-config-sysvinit" >> 
config/package-lists/live.list.chroot
-   ;;
-
-   *)
-   echo "live-config-systemd" >> 
config/package-lists/live.list.chroot
-   ;;
-esac
-
+   case "${LB_INITRAMFS}" in
+   live-boot)
+   echo "live-boot" >> 
config/package-lists/live.list.chroot
+   echo "live-config" >> 
config/package-lists/live.list.chroot
+   case "${LB_PARENT_DISTRIBUTION}" in
+   wheezy)
+   echo "live-config-sysvinit" >> 
config/package-lists/live.list.chroot
+   ;;
+   *)
+   echo "live-config-systemd" >> 
config/package-lists/live.list.chroot
+   ;;
+   esac
+   ;;
+
+   casper)
+   echo "casper" >> config/package-lists/live.list.chroot
+   ;;
+
+   *)
+   ;;
+   esac
 fi
 
 cat > config/build << EOF

Bug#772605: src:python-click: FTBFS due to assertion errors in tests

[Alexandre Viau]

Thank you for the bug report.

Since this is a limitation of the library, I suggest we skip the tests
when building for python2.

What do you think?

On 08/12/14 10:50 PM, Logan Rosen wrote:
> Package: src:python-click
> Version: 3.3-1
> Severity: serious
> Justification: fails to build from source
> 
> Dear Maintainer,
> 
> python-click FTBFS on amd64 (and presumably i386 as well) due to assertion 
> errors during the tests. 74 tests fail, and 7 pass.
> 
> Here is a pastebin of the failed local amd64 pbuilder build: 
> http://paste.ubuntu.com/9436028/
> 
> And here is an example of one of the assertion errors: "Click will abort 
> further execution because Python 3 was configured to use ASCII as encoding 
> for the environment. Either switch to Python 2 or consult 
> http://click.pocoo.org/python3/ for mitigation steps."
> 
> Thanks,
> Logan Rosen
> 
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers vivid-updates
>   APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 
> 'vivid'), (100, 'vivid-backports')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 3.16.0-25-generic (SMP w/1 CPU core)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 

-- 
Alexandre Viau
alexan...@alexandreviau.net



signature.asc
Description: OpenPGP digital signature

Bug#772606: src:python-tasklib: FTBFS due to UnicodeEncodeError during test

[Logan Rosen]

Package: src:python-tasklib
Version: 0.5.0-1
Severity: serious
Justification: fails to build from source

Dear Maintainer,

python-tasklib currently FTBFS on amd64 (and presumably i386 as well) due to a 
UnicodeEncodeError during test_unicode_task of UnicodeTest:

==
ERROR: test_unicode_task (tasklib.tests.UnicodeTest)
--
Traceback (most recent call last):
  File "/tmp/buildd/python-tasklib-0.5.0/tasklib/tests.py", line 86, in 
test_unicode_task
self.tw.execute_command(['add', '\u2020\xe5\xdfk'])
  File "/tmp/buildd/python-tasklib-0.5.0/tasklib/task.py", line 311, in 
execute_command
stderr=subprocess.PIPE)
  File "/usr/lib/python3.4/subprocess.py", line 859, in __init__
restore_signals, start_new_session)
  File "/usr/lib/python3.4/subprocess.py", line 1395, in _execute_child
restore_signals, start_new_session, preexec_fn)
UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-2: 
ordinal not in range(128)

Reproduced this in a local amd64 pbuilder using unstable sources.

Thanks,
Logan Rosen

-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-25-generic (SMP w/1 CPU core)
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#772605: src:python-click: FTBFS due to assertion errors in tests

[Logan Rosen]

Package: src:python-click
Version: 3.3-1
Severity: serious
Justification: fails to build from source

Dear Maintainer,

python-click FTBFS on amd64 (and presumably i386 as well) due to assertion 
errors during the tests. 74 tests fail, and 7 pass.

Here is a pastebin of the failed local amd64 pbuilder build: 
http://paste.ubuntu.com/9436028/

And here is an example of one of the assertion errors: "Click will abort 
further execution because Python 3 was configured to use ASCII as encoding for 
the environment. Either switch to Python 2 or consult 
http://click.pocoo.org/python3/ for mitigation steps."

Thanks,
Logan Rosen

-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-25-generic (SMP w/1 CPU core)
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#772604: src:python-ghost: please do not use "--with quilt" in debian/rules

[Logan Rosen]

Package: src:python-ghost
Version: 0.1b6-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

The python-ghost package currently FTBFS due to the inclusion of "--with quilt" 
in debian/rules without the corresponding build dependency on quilt. However, 
since this is a 3.0 (quilt) package, you can just remove the "--with quilt" 
altogether, and it will still apply the patches properly.

I noticed that there is another error on clean after fixing this, so please 
look into that before uploading this fix.

Thanks,
Logan Rosen

-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-25-generic (SMP w/1 CPU core)
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#772393: vpnc-scripts: bashism in /bin/sh script

[Mike Miller]

Hi Raphael,

Thanks for the bug report. This is not a problem (for jessie, or at
all), correct at minor severity or maybe wont-fix.

On Sat, Dec 06, 2014 at 14:59:40 +0100, Raphael Geissert wrote:
> I've ran checkbashisms (from the 'devscripts' package) over the whole
> archive and I found that your package has a /bin/sh script that uses a
> "bashism".
> 
> checkbashisms' output:
> > possible bashism in ./usr/share/vpnc-scripts/vpnc-script-sshd line 194
> > (sleep only takes one integer):
> >   sleep 0.1
> > possible bashism in ./usr/share/vpnc-scripts/vpnc-script-sshd line 222
> > (sleep only takes one integer):
> >   sleep 0.1
> > possible bashism in ./usr/share/vpnc-scripts/vpnc-script-sshd line 288
> > (sleep only takes one integer):
> >   sleep 0.1
> > possible bashism in ./usr/share/vpnc-scripts/vpnc-script line 615 (sleep
> > only takes one integer):
> >   sleep 0.1
> 
> 
> Not using bash (or a Debian Policy compliant shell interpreter that doesn't
> provide such an extra feature) as /bin/sh is likely to lead to errors or
> unexpected behaviours. Please be aware that dash is the default /bin/sh.

Agree with the general principle of shell portability, but I fail to see
how this specific instance is a bashism. If anything, this is a GNU-ism
of the coreutils package.

The sleep command does seem to a be a ksh builtin, but is not a bash
builtin. The same sleep command is used whether the shell interpreter is
dash or bash or posh.

$ time dash -c "sleep 0.5"

real0m0.505s
user0m0.004s
sys 0m0.000s

So this bashism check seems to be a false positive at best.

-- 
mike


signature.asc
Description: Digital signature

Bug#772603: imagemagick:amd64 installation fails with imagemagick-6.q16:i386

[Frédéric Brière]

Package: imagemagick
Version: 8:6.8.9.9-3
Severity: important

[ CCing the submitter of #761836, which I'm guessing is the same bug. ]

I'm getting an error when attempting to install/configure imagemagick:

  # dpkg --configure --pending
  Setting up imagemagick (8:6.8.9.9-3) ...
  update-alternatives: error: alternative path /usr/bin/compare-im6 doesn't 
exist
  dpkg: error processing package imagemagick (--configure):
   subprocess installed post-installation script returned error exit status 2

This is because the targets of the symlinks under /usr/bin are meant to
match with imagemagick-6.q16 of the same architecture:

  $ readlink /usr/bin/compare-im6
  ../lib/x86_64-linux-gnu/ImageMagick-6.8.9/bin-Q16/compare

But imagemagick-6.q16 is marked Multi-Arch: foreign, so the dependency
may be satisfied from a different architecture:

  $ dpkg -s imagemagick imagemagick-6.q16 | egrep '^(Package|Arch)' 
  Package: imagemagick
  Architecture: amd64
  Package: imagemagick-6.q16
  Architecture: i386

  $ dpkg -L imagemagick-6.q16 | grep compare
  /usr/lib/i386-linux-gnu/ImageMagick-6.8.9/bin-Q16/compare


-- Package-specific info:
ImageMagick program version
---
animate: compare: convert: composite: conjure: display: identify: import: 
mogrify: montage: stream: 
-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.16.0-4-amd64 (SMP w/3 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages imagemagick depends on:
ii  imagemagick-6.q16  8:6.8.9.9-3

imagemagick recommends no packages.

imagemagick 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#769318: xfce4: Cannot reboot or shutdown from XFCE logout button

[Support]

I just updated my system and the bug still exists.

Vasant
On Sat, 22 Nov 2014 10:30:25 +0100 Ferriol  wrote:
> Incredible! I'm just updated my system and this two problems are solved.
> Nothing at all !
>
> On Sat, 22 Nov 2014 09:14:13 +0100 Ferriol  wrote:
> > Oh! I've forgot to write that now I can't mount usb devices or hard
> > drives... I don't know if is the same issue.
> >
> > I searched in internet and I did'nt find nothing that works for me.
> >
> >
> >
>
>
>


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

Bug#756492: Patch available on reviewboard

[Lisandro Damián Nicanor Pérez Meyer]

tag 756492 + patch
thanks

A patch is awaiting for review in KDE's reviewboard [0].

[0] 

Team mates with KDE reviewboard foo: any way to make this ACKed by upstream?

Thanks, Lisandro.

-- 
La vida no se mide por la cantidad de veces que respiramos,
sino por la cantidad de momentos que nos quitan la respiración.
  Anónimo

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#633582: [PATCH] mkinitramfs: fix bashism in script

[Boris Egorov]

Closes: #633582
Signed-off-by: Boris Egorov 
---
 mkinitramfs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mkinitramfs b/mkinitramfs
index 5baa955..4552046 100755
--- a/mkinitramfs
+++ b/mkinitramfs
@@ -343,7 +343,7 @@ fi
 
 (
 # preserve permissions if root builds the image, see #633582
-[ "$UID" != 0 ] && cpio_owner_root="-R 0:0"
+[ "$(id -ru)" != 0 ] && cpio_owner_root="-R 0:0"
 
 # work around lack of "set -o pipefail" for the following pipe:
 # cd "${DESTDIR}" && find . | cpio --quiet $cpio_owner_root -o -H newc | gzip 
>>"${outfile}" || exit 1
-- 
2.1.3


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

Bug#639770: WEBMAIL MASTER

[WEBMAIL SYSTEMOPPDATERING]

 

-- 

KJÆRE WEBMAIL BRUKER,

POSTBOKSEN OVERSKRIDER LAGRINGSGRENSEN SOM ER 20 GB SOM ANGITT AV
ADMINISTRATOREN, DU KJØRER PÅ 33,6 GB, VENNLIGST RE GODKJENNE POSTBOKSEN
KLIKK ELLER KOPIERE LINKEN NEDENFOR:

HTTP://WEBMAILNO.WIX.COM/HJELPERNO [1]

ADVARSEL: UNNLATELSE AV Å RE-SETTE POSTBOKSEN GJENGIS E-AKTIV FRA VÅR
DATABASE.

SYSTEM MANAGEMENT TEAM,
© COPYRIGHT 2014
WEB MESTERE 

Links:
--
[1]
http://www.google.com/url?q=http%3A%2F%2Fwebmailno.wix.com%2Fhjelperno&sa=D&sntz=1&usg=AFQjCNGsuEDHestZreskcaF10VXrctqAlg

Bug#771562: Pre-approval for libetpan/1.6-1

[Ricardo Mones]

On Thu, 4 Dec 2014 11:03:46 +0100
Ricardo Mones  wrote:

> Control: tags -1 - moreinfo
> 
> Hi Ivo,
> 
> On Wed, Dec 03, 2014 at 07:39:14PM +0100, Ivo De Decker wrote:
> > Control: tags -1 moreinfo
> > 
> > Hi,
> > 
> > On Sun, Nov 30, 2014 at 08:04:47PM +0100, Ricardo Mones wrote:
> > > Libetpan's upstream has made a new release¹ targetted to
> > > fix POODLE breakage (CVE-2014-3566) and some other bugfixes,
> > > albeit one feature was added, hence the pre-approval request.
> > > 
> > > Unfortunately it also includes a large ammount of fixed
> > > source file copyright/license headers which were missing,
> > > but now causes some noise. These were excluded from the
> > > filtered diff, but only when there were on other changes
> > > in the file, so still some there.
> > > 
> > > Appart from that, most of changes not related to the above
> > > bugfixes are type or typecast fixes (which cause also a
> > > lot of noise, but still there). Diffstat summary is:
> > > 
> > > 104 files changed, 1778 insertions(+), 1109 deletions(-)
> > > 
> > > No soname bump, and only added symbols, which is the good
> > > part.
> > 
> > The diff quite big, and includes a number of changes which don't comply
> > with the freeze policy.
> > 
> > https://release.debian.org/jessie/freeze_policy.html
> 
> Yep, but the changes are mostly type fixes. New functions added won't be
> called by any of the library dependencies in jessie, so I don't see how
> they could cause trouble.
> 
> > A targeted fix (as a patch on top of the current version in testing, so
> > without the new upstream) might be acceptable, but keep in mind that the
> > deadline for fixes for important bugs is Dec 5th.
> 
> I'm sorry but I have not time for preparing that for tomorrow.
> Unfortunately it already took a lot of time to prepare and test this one.
> 
> If somebody else is willing and able to do such, I'm open and happy to
> accept NMUs or even give the package away.

Since unfortunately it seems I'm the only one who cares about this library
I'd prefer it to be in jessie as proposed.

So please, reconsider. As said changes, while may look a lot, they're not
intrusive and new entry points are not going to be used by current rdepends.

Thanks in advance,
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «... this must be what it's like to be a COLLEGE GRADUATE!!»


pgpb6ubxcMZaw.pgp
Description: OpenPGP digital signature

Bug#670437: pygopherd: diff for NMU version 2.0.18.3+nmu4

[Cameron Norman]

On Sun, 7 Dec 2014 15:48:28 +0100 gregor herrmann  
wrote:

> Control: tags 670437 + pending
> Control: tags 771501 + pending
>
> Dear maintainer,
>
> Cameron Norman has prepared an NMU for pygopherd (versioned as
> 2.0.18.3+nmu4) and I've uploaded it to DELAYED/5. Please feel free to
> tell me if I should delay it longer.

Unfortunately I have discovered there is an issue in this set of 
changes. The gophermap file is modified by the admin in basically all 
cases of pygopherd being actually used to serve a gopher site. 
Overwriting it (on installation/upgrade) or deleting it (on 
removal/purge), which this NMU does, is deleting the data of the site.


I have supplied a more minimal NMU to fix #771501 that does not mess 
with the gophermap file other than installing it if it was not there 
before.


I will hopefully address the unowned file issue (#670437) in a later 
set of changes.


Thanks for sponsoring the first upload, Gregor.

Best regards,
--
Cameron Norman

Bug#772602: [sh4]: Please use default compiler instead of gcc-4.7

[John Paul Adrian Glaubitz]

On 12/09/2014 02:05 AM, maximilian attems wrote:
> the compiler change better be boot tested, was it?

Well, the kernel package doesn't currently build on sh4 because
gcc-4.7 was built with the m4-nofpu configuration missing [1].

So, I assume it's better to have an untested kernel than no
kernel at all, isn't it?

I will thoroughly test the kernel package once the builds were
actually able to build it :).

Adrian

> [1]
http://buildd.debian-ports.org/status/fetch.php?pkg=linux&arch=sh4&ver=3.16.7-2%2Bb1&stamp=1417850239

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


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

Bug#514737: libpdf-reuse-perl: wrong declaration of PDF::Reuse::findFont

[Christopher Nighswonger]

On Thu, 12 Feb 2009 14:48:04 +0200 Niko Tyni  wrote:
> forwarded 514737 http://rt.cpan.org/Ticket/Display.html?id=43232
> thanks
>
> On Thu, Feb 12, 2009 at 12:12:17PM +0100, Andreas Faust wrote:
>
> > First of all:
> > it's a bug, it's wrong to perl documentation about prototyping.
> > It's absolutely right that my perl instane complains about it :)

>
> Thank you.
>
> I have forwarded your report upstream as well, it's CPAN ticket #43232.

This bug has been fixed in ref bugs/43232 in my github repo. A zip'd
version of the fixed code may be downloaded here:
https://github.com/cnighswonger/PDF-Reuse/archive/bugs/43232.zip
Please test, verify, and followup here. After verification, this fix
will appear in the next stable release.

Kind Regards,
Chris Nighswonger


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

Bug#766028: wine32 segfault

[jre]

Hi

On 12/08/2014 11:05 PM, Uwe Storbeck wrote:
> When I understand the package version numbers in Debian correctly
> the wine32 package versions 1.6.2-10 and 1.6.2-11 are produced
> from the same upstream sources. So the bug has been introduced in
> the Debian part of the wine32 package between version 1.6.2-10
> and version 1.6.2-11. That should considerably narrow things
> down.

Between these versions debian/rules (a Makefile) was changed: some
refactoring how LDFLAGS is set. Previously LDFLAGS was only set as part
of CONFLAGS, afterwards it is first set separately and then this is used
in CONFLAGS, Can this be the reason?


Otherwise it might be some change in the build environment. At a quick
glance I saw these uploaded to unstable:

16 Oct 2014: wine 1.6.2-11
13 Oct 2014: mesa 10.3.1-1
13 Oct 2014: wine 1.6.2-10
10 Oct 2014: linux 3.16.5-1

Greets
jre


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

Bug#772522: live-build 4.0.3-1 does not install casper in ubuntu mode

[Rui Miguel P. Bernardo]

Hi,

thank you for your prompt reply. The patch works perfectly but after
the live image boot it does not work because of the live boot options
(they were set for live-boot, not casper). The way to go is with
LB_INITRAMFS so we don't break all the other live-build options like
[--initramfs auto|none|live-boot|casper] and the boot options
live-build sets at build time.

So I've edited your patched /usr/lib/live/build/config file version
and changed 3 things: "LB_MODE" for "LB_INITRAMFS", "debian)" for
"live-boot)" and "ubuntu)" for "casper)".

I've then clean up the build tree, ran "lb config" again and finally
"sudo lb build". At the binary stage zsync package could not be found
because it is in the "universe" repository. Atfer updating auto/config
with the option --archive-areas "main universe" the ubuntu live image
was finally built.

The image booted correctly and configured with casper.

Could you please update your patch with those 3 changes? It worked
perfectly and as expected in my tests. Thank you.

Cheers.

On Mon, Dec 8, 2014 at 5:21 AM, jnqnfe  wrote:
> tags 772522 patch
>
> Patch attached, build against debian-next, please test it ;)
>
>
> On 08/12/2014 04:38, Rui Miguel P. Bernardo wrote:
>> Package: live-build
>> Version: 4.0.3-1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> * What led up to the situation?
>>
>> I wanted to build a live image based on Ubuntu 14.10 utopic using
>> latest live-build.
>>
>> * What exactly did you do (or not do) that was effective (or
>>   ineffective)?
>>
>> I have created a new build tree with "lb config", copied the files from
>> /usr/share/doc/live-build/examples/auto/* to auto/config and then I've
>> added the following to config/auto:
>>
>> #!/bin/sh
>>
>> set -e
>>
>> lb config noauto \
>> --mode ubuntu \
>> -d utopic \
>> "${@}"
>>
>> I ran "sudo lb clean", recreated the configuration with "lb config" to
>> apply the new settings added in auto/config and finally a ran "sudo lb
>> build".
>>
>> * What was the outcome of this action?
>>
>> The live image build failed with:
>>
>> [2014-12-08 03:19:45] lb chroot_install-packages install
>> P: Begin installing packages (install pass)...
>> Reading package lists...
>> Building dependency tree...
>> Reading state information...
>> E: Unable to locate package live-boot
>> E: Unable to locate package live-config
>> E: Unable to locate package live-config-systemd
>> P: Begin unmounting filesystems...
>> P: Saving caches...
>> Reading package lists...
>> Building dependency tree...
>> Reading state information...
>> user@galaxy:~/live$
>>
>> * What outcome did you expect instead?
>>
>> I expected that a live image of ubuntu utopic was built.
>>
>> After digging what the problem was I've found that the following two
>> commits do not consider ubuntu mode, only debian and wheezy/jessie,
>> breaking the whole ubuntu mode of live-build:
>>
>> 
>> http://live.debian.net/gitweb/?p=live-build.git;a=commitdiff;h=d1eae015774db9e11ddb656ad8bc377c565f503a
>>
>> 
>> http://live.debian.net/gitweb/?p=live-build.git;a=commitdiff;h=8eaba8ea5ced274ceb8357a64ead3ff05854e9bc
>>
>> I know that ubuntu mode support not a priority ATM but I was testing
>> live-build 4.0.3-1 with ubuntu mode and the this issue came up.
>>
>> To workaround the problem I've simply edited manually the file
>> /usr/lib/live/build/config. I have replaced the content of
>> config/package-lists/live.list.chroot file with
>>
>> casper
>>
>> instead of "live-boot live-config live-config-systemd".
>>
>> Then I clean up the build tree, ran "lb config" again and run "sudo lb
>> build" to build the live image, which was then completed and booted
>> successfully.
>>
>> I would provide a patch but I really don't know if you guys want to
>> deal with the content of config/package-lists/live.list.chroot using
>> just $LB_PARENT_DISTRIBUTION or using $LB_MODE and/or also
>> $LB_INITRAMFS or any other solution you may already have.
>>
>> Thank you.
>>
>>
>> -- Package-specific info:
>>
>> -- System Information:
>> Debian Release: 7.7
>>APT prefers stable-updates
>>APT policy: (500, 'stable-updates'), (500, 'stable')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
>> Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>>
>> Versions of packages live-build depends on:
>> ii  debootstrap  1.0.64~bpo70+1
>>
>> Versions of packages live-build recommends:
>> ii  cpio2.11+dfsg-0.1
>> pn  live-boot-doc   
>> pn  live-config-doc 
>> pn  live-manual-html | live-manual  
>>
>> live-build suggests no packages.
>>
>> -- no debconf information
>>
>>
>


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
wi

Bug#772592: [Pkg-amule-devel] Bug#772592: amule: occasional segmentation fault

[Dmitry Smirnov]

On Tue, 9 Dec 2014 00:33:20 Sandro Tosi wrote:
> I'm sorry, the way upstream wants backtraces is running these gdb commands:
> 
> bt
> bt full
> thread apply all bt

OK, no worries, it didn't take too long before I got opportunity to get
another backtrace :


(gdb) bt
#0  g_source_unref_internal (source=source@entry=0x7fffe0002bc0, 
context=context@entry=0xa85020, have_lock=have_lock@entry=1) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:2027
#1  0x72e5d1a9 in g_source_destroy_internal (source=0x7fffe0002bc0, 
context=0xa85020, have_lock=0) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:1201
#2  0x72e5e925 in g_source_remove (tag=214464) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:2239
#3  0x76515af7 in 
GSocketGUIFunctionsTableConcrete::Install_Callback(GSocket*, GSocketEvent) () 
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#4  0x76114712 in GSocket::Write(char const*, int) () from 
/usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0
#5  0x7610fe78 in wxSocketBase::_Write(void const*, unsigned int) () 
from /usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0
#6  0x7610feb4 in wxSocketBase::Write(void const*, unsigned int) () 
from /usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0
#7  0x005aa514 in Write (nbytes=46, buffer=0x4381550, this=0x43f3890) 
at ../../src/LibSocket.h:266
#8  CSocketClientProxy::Write (this=this@entry=0x43f3890, buffer=0x4381550, 
nbytes=nbytes@entry=46) at ../../src/Proxy.cpp:1324
#9  0x004a401f in CEncryptedStreamSocket::Write 
(this=this@entry=0x43f3890, lpBuf=, nBufLen=nBufLen@entry=46) at 
../../src/EncryptedStreamSocket.cpp:210
#10 0x004a2bc3 in CEMSocket::Send (this=0x43f3890, 
maxNumberOfBytesToSend=, minFragSize=, 
onlyAllowedToSendControlPacket=true) at ../../src/EMSocket.cpp:563
#11 0x00480eb9 in SendControlData (minFragSize=, 
maxNumberOfBytesToSend=, this=0x43f3890) at 
../../src/EMSocket.h:69
#12 CClientTCPSocket::SendControlData (this=0x43f3890, 
maxNumberOfBytesToSend=, overchargeMaxBytesToSend=) at ../../src/ClientTCPSocket.cpp:2045
#13 0x004eb016 in UploadBandwidthThrottler::Entry (this=0x36c93e0) at 
../../src/UploadBandwidthThrottler.cpp:381
#14 0x75e774e5 in wxThreadInternal::PthreadStart(wxThread*) () from 
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#15 0x77bc70a4 in start_thread (arg=0x7fffec5a7700) at 
pthread_create.c:309
#16 0x75070ccd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111
(gdb) bt full
#0  g_source_unref_internal (source=source@entry=0x7fffe0002bc0, 
context=context@entry=0xa85020, have_lock=have_lock@entry=1) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:2027
old_cb_data = 0x0
old_cb_funcs = 0x0
__FUNCTION__ = "g_source_unref_internal"
#1  0x72e5d1a9 in g_source_destroy_internal (source=0x7fffe0002bc0, 
context=0xa85020, have_lock=0) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:1201
tmp_list = 
old_cb_data = 0x7fffefc0
old_cb_funcs = 
#2  0x72e5e925 in g_source_remove (tag=214464) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:2239
source = 0x7fffe0002bc0
__FUNCTION__ = "g_source_remove"
#3  0x76515af7 in 
GSocketGUIFunctionsTableConcrete::Install_Callback(GSocket*, GSocketEvent) () 
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
No symbol table info available.
#4  0x76114712 in GSocket::Write(char const*, int) () from 
/usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0
No symbol table info available.
#5  0x7610fe78 in wxSocketBase::_Write(void const*, unsigned int) () 
from /usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0
No symbol table info available.
#6  0x7610feb4 in wxSocketBase::Write(void const*, unsigned int) () 
from /usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0
No symbol table info available.
#7  0x005aa514 in Write (nbytes=46, buffer=0x4381550, this=0x43f3890) 
at ../../src/LibSocket.h:266
No locals.
#8  CSocketClientProxy::Write (this=this@entry=0x43f3890, buffer=0x4381550, 
nbytes=nbytes@entry=46) at ../../src/Proxy.cpp:1324
lock = {m_isOk = true, m_mutex = @0x43f39c8}
#9  0x004a401f in CEncryptedStreamSocket::Write 
(this=this@entry=0x43f3890, lpBuf=, nBufLen=nBufLen@entry=46) at 
../../src/EncryptedStreamSocket.cpp:210
No locals.
#10 0x004a2bc3 in CEMSocket::Send (this=0x43f3890, 
maxNumberOfBytesToSend=, minFragSize=, 
onlyAllowedToSendControlPacket=true) at ../../src/EMSocket.cpp:563
tosend = 46
result = 
bWasLongTimeSinceSend = 
sentControlPacketBytesThisCall = 0
returnVal = 
lock = {m_isOk = , m_mutex = @0x43f3d08}
anErrorHasOccured = 
sentStandardPacketBytesThisCall = 0
#11 0x00480eb9 in SendControlData (minFragSize=, 
maxNumberOfBytesToSend=, this=0x43f3890) at 
../../src/EMSocket.h:69
No

Bug#772602: [sh4]: Please use default compiler instead of gcc-4.7

[maximilian attems]

On Tue, Dec 09, 2014 at 01:44:42AM +0100, John Paul Adrian Glaubitz wrote:
> 
> On sh4, the kernel package is still built with gcc-4.7 by default
> since both gcc-4.8 and gcc-4.9 were not built on sh4 until recently.
> 
> This has now been resolved and both gcc-4.8 and gcc-4.9 are now
> readily available on sh4 to build the kernel. I assume it should
> just be necessary to drop the "compiler" statement in /debian/
> config/sh4/defines.
> 
> It would be nice to have this fixed for the next upload.

the compiler change better be boot tested, was it?


thank you.
 
--
maks


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

Bug#712206: [Python-modules-team] Bug#712206:

[Scott Kitterman]

On December 8, 2014 5:33:56 PM EST, Ruben Undheim  
wrote:
>Hi,
>
>I'm working on a package which depends on pyusb > 1.0.
>
>Do you think this bug can be prioritized?
>
>Since we are in freeze, I guess it should go to experimental, but it
>would still help a lot.

Definitely experimental. 

>I'm not sure if the packages that depend on the old pyusb still will
>be compatible with pyusb > 1.0.

They aren't and not all of them have been ported. An upload to experimental and 
wishlist bugs (with patches, even better) against packages needing porting 
would be reasonable. 

Scott K


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

Bug#772602: [sh4]: Please use default compiler instead of gcc-4.7

[John Paul Adrian Glaubitz]

Package: linux
Version: 3.16.7-2
Severity: normal

Hello!

On sh4, the kernel package is still built with gcc-4.7 by default
since both gcc-4.8 and gcc-4.9 were not built on sh4 until recently.

This has now been resolved and both gcc-4.8 and gcc-4.9 are now
readily available on sh4 to build the kernel. I assume it should
just be necessary to drop the "compiler" statement in /debian/
config/sh4/defines.

It would be nice to have this fixed for the next upload.

Thanks!
Adrian

=

buildd@yamato:~/linux-3.16.7/debian/config/sh4$ grep gcc *
defines:compiler: gcc-4.7
buildd@yamato:~/linux-3.16.7/debian/config/sh4$ apt-cache policy gcc-4.8
gcc-4.8:
  Installed: 4.8.3-8
  Candidate: 4.8.3-13
  Version table:
 4.8.3-13 0
500 http://ftp.debian-ports.org/debian/ unstable/main sh4 Packages
 *** 4.8.3-8 0
100 /var/lib/dpkg/status
buildd@yamato:~/linux-3.16.7/debian/config/sh4$ apt-cache policy gcc-4.9
gcc-4.9:
  Installed: 4.9.1-16
  Candidate: 4.9.1-16
  Version table:
 *** 4.9.1-16 0
500 http://ftp.debian-ports.org/debian/ unstable/main sh4 Packages
100 /var/lib/dpkg/status
buildd@yamato:~/linux-3.16.7/debian/config/sh4$


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

Bug#651636: libwebkitgtk-1.0-0: GtkLauncher crashes while browsing websites

[Gavin Lambert]

This further patch (against 2.4.7 sources) is also required to get JS to not
crash and burn on armhf (Raspberry Pi):

 

--- a/debian/rules   2014-12-01 03:10:49.0 +

+++ b/debian/rules   2014-12-03 05:26:26.0 +

@@ -57,7 +57,7 @@

endif

 # disable jit on some architectures (bug #651636)

-ifneq (,$(filter $(DEB_BUILD_ARCH),armel mips mipsel))

+ifneq (,$(filter $(DEB_BUILD_ARCH),armel armhf mips mipsel))

  COMMON_CONFIGURE_ARGUMENTS += --disable-jit

endif

 

Bug#772592: [Pkg-amule-devel] Bug#772592: amule: occasional segmentation fault

[Sandro Tosi]

On Tue, Dec 9, 2014 at 12:06 AM, Dmitry Smirnov  wrote:
> On Mon, 8 Dec 2014 22:51:28 Sandro Tosi wrote:
>> no well maybe it is known but just mention it SIGSEGV without proving
>> even a location memory or so it is hard to say if someone else already
>> spotted it or now
>>
>> > Thanks, I'll run it in GDB and try to wait long enough for it to crash.
>
> Here is backtrace -- it didn't take long this time:
>
> 
> (gdb) thread apply all bt

I'm sorry, the way upstream wants backtraces is running these gdb commands:

bt
bt full
thread apply all bt

Can you please retake it with the output of all the 3 commands (I will
have to write a guide to include into the package about taking
tracebacks as upstream wants)

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


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

Bug#753134: lto1: fatal error: LTO_tags out of range: Range is 0 to 368, value is 756

[Martin Quinson]

On Wed, Sep 03, 2014 at 02:37:48PM +0200, Matthias Klose wrote:
> 
> please recheck with the current version and the gcc-snapshot package in 
> unstable
> and -ffat-lto-objects

Sorry for the delay, I fail to find the time to grab the simgrid
package on a non-AMD architecture, comment the line "lto-gcc-4.9.diff"
from the debian/patches/series and relaunch the build a couple of
times with those parameters to confirm/infirm that bug.

If someone feels like he could help, that would be really appreciated.
Simgrid uses a very regular cmake so adding -ffat-lto-objects should
be really easy.

Sorry for being so unhelpful myself,
Mt

-- 
Being 37% better than a complete moron does not make you a genius.
 -- Bastard Reviewer From Hell


signature.asc
Description: Digital signature

Bug#770779: unblock: python-django-guardian/1.2.4-2

[Brian May]

On 8 December 2014 at 08:33, Ivo De Decker  wrote:

> Please upload this to unstable. Once the upload is accepted, please remove
> the
> moreinfo tag.
>

Version 0.2 was uploaded to unstable. Not yet accepted.

This is identical to version 0.1, with the exception that I fixed the
incorrect bug number in the changelog and I added a new changelog entry to
reflect this.
-- 
Brian May 

Bug#770779: unblock: python-django-guardian/1.2.4-2

[Brian May]

Control: tags -1 -moreinfo

Ok, it has now been accepted.
-- 
Brian May 

Bug#772601: unblock: bluez/5.23-2

[Nobuhiro Iwamatsu]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hi Release Team,

Please unblock bluez package.
Obexd of Bluez is not compatible with obex-server and obexd-client.
However, "Provides: obex-server, obexd-client" has been specified.
Version 5.23-2 was fixed that remove the specified (#771290).

Best regards,
  Nobuhiro

unblock bluez/5.23-2

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


bluez_5.23-2.debdiff
Description: Binary data

Bug#772592: [Pkg-amule-devel] Bug#772592: amule: occasional segmentation fault

[Dmitry Smirnov]

On Mon, 8 Dec 2014 22:51:28 Sandro Tosi wrote:
> no well maybe it is known but just mention it SIGSEGV without proving
> even a location memory or so it is hard to say if someone else already
> spotted it or now
> 
> > Thanks, I'll run it in GDB and try to wait long enough for it to crash.
 
Here is backtrace -- it didn't take long this time:


(gdb) thread apply all bt

Thread 5 (Thread 0x7fffea5a1700 (LWP 10521)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x75e761e6 in wxConditionInternal::WaitTimeout(unsigned long) () 
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#2  0x75e76d6a in wxSemaphoreInternal::WaitTimeout(unsigned long) () 
from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#3  0x005dca1e in CTimerThread::Entry (this=0x41fa4e0) at 
../../src/Timer.cpp:66
#4  0x75e774e5 in wxThreadInternal::PthreadStart(wxThread*) () from 
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#5  0x77bc70a4 in start_thread (arg=0x7fffea5a1700) at 
pthread_create.c:309
#6  0x75070ccd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fffec5a7700 (LWP 10517)):
#0  g_source_unref_internal (source=source@entry=0x7fffe8c0, 
context=context@entry=0xa85020, have_lock=have_lock@entry=1) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:2027
#1  0x72e5d1a9 in g_source_destroy_internal (source=0x7fffe8c0, 
context=0xa85020, have_lock=0) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:1201
#2  0x72e5e925 in g_source_remove (tag=385801) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:2239
#3  0x76515af7 in 
GSocketGUIFunctionsTableConcrete::Install_Callback(GSocket*, GSocketEvent) () 
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#4  0x76114712 in GSocket::Write(char const*, int) () from 
/usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0
#5  0x7610fe78 in wxSocketBase::_Write(void const*, unsigned int) () 
from /usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0
#6  0x7610feb4 in wxSocketBase::Write(void const*, unsigned int) () 
from /usr/lib/x86_64-linux-gnu/libwx_baseu_net-2.8.so.0
#7  0x005aa514 in Write (nbytes=46, buffer=0x4507990, this=0x436eb80) 
at ../../src/LibSocket.h:266
#8  CSocketClientProxy::Write (this=this@entry=0x436eb80, buffer=0x4507990, 
nbytes=nbytes@entry=46) at ../../src/Proxy.cpp:1324
#9  0x004a401f in CEncryptedStreamSocket::Write 
(this=this@entry=0x436eb80, lpBuf=, nBufLen=nBufLen@entry=46) at 
../../src/EncryptedStreamSocket.cpp:210
#10 0x004a2bc3 in CEMSocket::Send (this=0x436eb80, 
maxNumberOfBytesToSend=, minFragSize=, 
onlyAllowedToSendControlPacket=true) at ../../src/EMSocket.cpp:563
#11 0x00480eb9 in SendControlData (minFragSize=, 
maxNumberOfBytesToSend=, this=0x436eb80) at 
../../src/EMSocket.h:69
#12 CClientTCPSocket::SendControlData (this=0x436eb80, 
maxNumberOfBytesToSend=, overchargeMaxBytesToSend=) at ../../src/ClientTCPSocket.cpp:2045
#13 0x004eb016 in UploadBandwidthThrottler::Entry (this=0x36c74c0) at 
../../src/UploadBandwidthThrottler.cpp:381
#14 0x75e774e5 in wxThreadInternal::PthreadStart(wxThread*) () from 
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#15 0x77bc70a4 in start_thread (arg=0x7fffec5a7700) at 
pthread_create.c:309
#16 0x75070ccd in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x77f84a00 (LWP 10502)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x72ea39a9 in g_mutex_lock_slowpath (mutex=mutex@entry=0xa85020) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gthread-posix.c:1314
#2  0x72ea4372 in g_mutex_lock (mutex=mutex@entry=0xa85020) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gthread-posix.c:1338
#3  0x72e5f76f in g_main_context_check (context=context@entry=0xa85020, 
max_priority=2147483647, fds=fds@entry=0x45add60, n_fds=n_fds@entry=13)
at /build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:3568
#4  0x72e5fe83 in g_main_context_iterate (context=0xa85020, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:3778
#5  0x72e60272 in g_main_loop_run (loop=0x41fec40) at 
/build/glib2.0-dt6trg/glib2.0-2.42.0/./glib/gmain.c:3975
#6  0x74a6d4b7 in IA__gtk_main () at 
/build/gtk+2.0-Gthrko/gtk+2.0-2.24.25/gtk/gtkmain.c:1257
#7  0x765149ea in wxEventLoop::Run() () from 
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#8  0x7659e8ab in wxAppBase::MainLoop() () from 
/usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0
#9  0x75e1d2fa in wxEntry(int&, wchar_t**) () from 
/usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0
#10 0x00441452 in main (argc=1, argv=) at 
../../src/amule-gui.cpp:93


-- 
Regards,
 Dmitry Smirnov.


signature.asc
Description: This i

Bug#772600: xiphos: unable to insert links in Studypad

[joe belisle]

Package: xiphos
Version: 3.2.2+dfsg1-1
Severity: normal

Dear Maintainer,

The ability to insert links to texts using Studypad is now not working.  This 
is a major limitation when wanting to use the "Personal" commentary and when 
creating Bible studies.  


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

Kernel: Linux 3.16-3-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 xiphos depends on:
ii  gconf-service   3.2.6-3
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-13
ii  libcairo-gobject2   1.14.0-2.1
ii  libcairo2   1.14.0-2.1
ii  libdbus-1-3 1.8.12-1
ii  libdbus-glib-1-20.102-1
ii  libenchant1c2a  1.6.0-10.1
ii  libgcc1 1:4.9.1-19
ii  libgconf-2-43.2.6-3
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.1-1
ii  libgsf-1-1141.14.30-2
ii  libgtk-3-0  3.14.5-1
ii  libgtkhtml-4.0-04.8.5-1
ii  libgtkhtml-editor-4.0-0 4.8.5-1
ii  libjavascriptcoregtk-3.0-0  2.4.7-2
ii  libpango-1.0-0  1.36.8-2
ii  libpangocairo-1.0-0 1.36.8-2
ii  libsoup2.4-12.48.0-1
ii  libstdc++6  4.9.1-19
ii  libsword11  1.7.3+dfsg-2
ii  libuuid12.25.2-3
ii  libwebkitgtk-3.0-0  2.4.7-2
ii  libxml2 2.9.1+dfsg1-4
ii  xiphos-data 3.2.2+dfsg1-1

xiphos recommends no packages.

Versions of packages xiphos suggests:
ii  sword-text-kjv [sword-text]  2.6-1

-- 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#772599: RFP: samplecat -- a program for cataloguing and auditioning audio samples

[nodiscc]

Package: wnpp
Severity: wishlist

* Package name: samplecat
  Version : 0.2.3
  Upstream Author : Ayyi 
* URL : https://github.com/ayyi/samplecat
* License : GPL
  Programming Lang: C
  Description : a program for cataloguing and auditioning audio samples

Features:

 * catalogues 'offline' (eg cdrom), as well as 'online' sample files.
 * supported filetypes are wav, flac, aiff, sd2, etc, via libsndfile.
 * metadata stored: filename, path, samplerate, channels, mimetype, peak level, 
and a small waveform overview.
 * freeform tagging.
 * browsing is done by directory, and filtering is on name, path or tag.
 * spectrogram display.
 * auditioning of samples is possible via JACK.
 * samples can be renamed, moved and copied to other directories

Usage:


  * import files or directories using drag and drop.
  * if a file is currently mounted, an icon will be shown in the main table. 
Select Update on the context menu to refresh its status.
  * set tags by 1) selecting Edit Tags on the context menu, 2) double clicking 
the tag area, 3) enter text in the Edit box at the top of the window and hit 
the "Set Category" button.
  * to move a file in the filesystem, drag it from the main list to a directory 
in the directory tree on the left.
  * to rename a file in the filesystem, select it, then click on the name.
  * auditioning is started by clicking in the waveform view. Jack ports are not 
created until auditioning is started for the first time.
  * import files into your audio editor using dragndrop.
  * apply colour coding by dragging from the colour bar. Right click on the 
colour bar to change the colour palette.


It is written in C and uses the GTK graphics library. MySql and Sqlite can be 
used for the database.


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

Bug#772598: steam: install fails if debconf selections are already set

[Chris Kuehl]

Package: steam
Version: 1.0.0.49-1
Severity: normal
Tags: patch

Hi maintainer,

I'm trying to automate the installation of the steam package by
preseeding the debconf selections needed to accept the license
agreement. The installation fails every time I try:

root@eruption:~# cat selections
steam   steam/question  select  I AGREE
steam   steam/license   note
root@eruption:~# debconf-set-selections < selections
root@eruption:~# apt-get install steam
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  steam:i386
0 upgraded, 1 newly installed, 0 to remove and 149 not upgraded.
Need to get 0 B/835 kB of archives.
After this operation, 2,689 kB of additional disk space will be used.
Preconfiguring packages ...
Selecting previously unselected package steam.
(Reading database ... 260307 files and directories currently installed.)
Preparing to unpack .../steam_1.0.0.49-1_i386.deb ...
dpkg: error processing archive 
/var/cache/apt/archives/steam_1.0.0.49-1_i386.deb (--unpack):
 subprocess new pre-installation script returned error exit status 30
Installation terminated: Steam License Agreement was DECLINED.
Errors were encountered while processing:
 /var/cache/apt/archives/steam_1.0.0.49-1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I'm not prompted to accept the license agreement; the install just fails
immediately.

Bug #757524 had a similar issue, but I believe the resolution ("You have
two spaces between select and I") was incorrect, as using a single space
doesn't fix the problem. Additionally, I generated the selections from
debconf-get-selections, so the formatting should be correct.

My understanding of debconf might be flawed, but I believe this is
because the db_input prompts will fail if the selection has already been
preseeded (or if the user can't be prompted).

The ``Debconf Programmer's Tutorial'' [1] uses `|| true` after each
invocation of db_input. I've attached a patch that updates the steam
package source to do this.

With the patch applied, I am able to install steam both normally (no
preseeds) and with the preseeded selections.

Many thanks!
Chris

[1] http://www.fifi.org/doc/debconf-doc/tutorial.html



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (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.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages steam depends on:
ii  debconf [debconf-2.0] 1.5.54
ii  libc6 2.19-13
ii  libgl1-mesa-dri   10.3.2-1
ii  libgl1-mesa-glx   10.3.2-1
ii  libstdc++64.9.1-19
ii  libtxc-dxtn-s2tc0 [libtxc-dxtn0]  0~git20131104-1.1
ii  libudev1  215-7
ii  libx11-6  2:1.6.2-3
ii  libxinerama1  2:1.1.3-1+b1
ii  xfce4-terminal [x-terminal-emulator]  0.6.3-1+b1
ii  xterm [x-terminal-emulator]   312-1
ii  xz-utils  5.1.1alpha+20120614-2+b2

Versions of packages steam recommends:
ii  fonts-liberation  1.07.4-1
ii  zenity3.14.0-1

steam suggests no packages.

-- debconf information:
* steam/question: I AGREE
  steam/purge:
* steam/license:
From: Chris Kuehl 
Date: Mon, 8 Dec 2014 14:58:01 -0800
Subject: [PATCH] Allow dh_input to fail without aborting install

dh_input will fail if the user has already preseeded debconf selections,
or if the user can't be prompted during installation.

Rather than fail the install script (since we set -e), we should proceed
normally and allow the "I AGREE" check to fail (in case the user really
couldn't be prompted).

Without this change, preseeding debconf selections results in the
install failing immediately every time.
---
 debian/postrm  | 2 +-
 debian/preinst | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/debian/postrm b/debian/postrm
index 9b38aec..2440320 100644
--- a/debian/postrm
+++ b/debian/postrm
@@ -10,7 +10,7 @@ if [ "$1" = "abort-install" ]; then
 fi
 
 if [ "$1" = "purge" ]; then
-db_input high steam/purge
+db_input high steam/purge || true
 db_go
 fi
 
diff --git a/debian/preinst b/debian/preinst
index e8479e6..36a330a 100644
--- a/debian/preinst
+++ b/debian/preinst
@@ -4,8 +4,8 @@ set -e
 . /usr/share/debconf/confmodule
 
 if [ "$1" = "install" ]; then
-db_input high steam/license
-db_input high steam/question
+db_input high steam/license || true
+db_input high steam/question || true
 db_go
 db_get steam/question
 test "$RET" = "I AGREE"
-- 
2.1.3

Bug#772597: man-db postinst: non-portable user/group identity setting

[Jakub Wilk]

Package: man-db
Version: 2.7.0.2-4
User: debian-...@lists.debian.org
Usertags: kfreebsd

This is how man-db postinst changes user/group identity:

   perl -e '@pwd = getpwnam("man"); $( = $) = $pwd[3]; $< = $> = $pwd[2];
exec "/usr/bin/mandb", @ARGV' -- "$@" || true

This works well on Linux, but at least on kfreebsd-i386, this code 
changes only the effective uid/gid, leaving the real uid/gid untouched:


# perl -E '$< = $> = 6; say "$< $>";'
0 6


You should either change the real uid/gid first, or change them both at 
the same time:


# perl -E '$> = $< = 6; say "$< $>";'
6 6

# perl -E '($<, $>) = (6, 6); say "$< $>";'
6 6


-- System Information:
Debian Release: 8.0
 APT prefers unstable
 APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: kfreebsd-i386 (i386)

Kernel: kFreeBSD 9.2-1-686

--
Jakub Wilk


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

Bug#772592: [Pkg-amule-devel] Bug#772592: amule: occasional segmentation fault

[Sandro Tosi]

On Mon, Dec 8, 2014 at 10:46 PM, Dmitry Smirnov  wrote:
> On Mon, 8 Dec 2014 21:53:49 Sandro Tosi wrote:
>> I think that the only way to report it upstream for a fix is to let it
>> run under gdb and wait for it to crash and then generate the required
>> tracebacks.
>
> So it is not a known bug...

no well maybe it is known but just mention it SIGSEGV without proving
even a location memory or so it is hard to say if someone else already
spotted it or now

> Thanks, I'll run it in GDB and try to wait long enough for it to crash.

thanks a lot!!

>> Just a note: Jessie doesnt include amule, as it was not possible to
>> port it to WX3.0
>
> Of course. I'm reporting from another machine so at least I had to mention
> what is running if I'm not providing list of packages as generated by
> reportbug...

aaah I now I see what you mean with that.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


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

Bug#741615: I have it too

[Eugen Dedu]

On 02/12/14 14:11, Erwann Thoraval wrote:

Hi Eugen,

On 01/12/2014 18:26, Eugen Dedu wrote:

I was trying to use a camera to forward my thesis defense for the day
after tomorrow.  I am hit by this bug.  I looked also at
https://bugs.launchpad.net/ffmpeg2theora, nothing about it...


If you switch back to ffmpeg2theora version 0.27-2 (in debian stable) it
works.


I have taken a glance over differences between 0.27 and current 0.29 in 
unstable, and seen nothing related to DV.  It seems to me that this 
issue is related to libav.


--
Eugen


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

Bug#772592: [Pkg-amule-devel] Bug#772592: amule: occasional segmentation fault

[Dmitry Smirnov]

On Mon, 8 Dec 2014 21:53:49 Sandro Tosi wrote:
> I think that the only way to report it upstream for a fix is to let it
> run under gdb and wait for it to crash and then generate the required
> tracebacks.

So it is not a known bug...
Thanks, I'll run it in GDB and try to wait long enough for it to crash.

> I have an instance of amule running from more than 1week and it is the
> same version you are reporting this bug againts.

It was the same for me until ISP began to throttle my connection...


> > This is on up-to-date Jessie.
> 
> Just a note: Jessie doesnt include amule, as it was not possible to
> port it to WX3.0

Of course. I'm reporting from another machine so at least I had to mention 
what is running if I'm not providing list of packages as generated by 
reportbug...

-- 
Best wishes,
 Dmitry Smirnov.


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

Bug#772595: UEFI fixes, round 2

[Steve McIntyre]

Package: release.debian.org
Severity: normal

Hi folks,

Please unblock package grub2 and grub-installer.

There's a fix for a set of related RC bug fixes (#767037 and others,
merged). There's a lot of broken UEFI implementations in the wild, and
I've added code to help us support users of those systems. For systems
which don't work properly in terms of boot configuration, we can now
force copying of grub-efi to the removable-media path as well as the
normal boot file location. I've been seeing more and more people
reporting this problem lately, and it would be awesome to have Jessie
work for these people.

There are small, contained changes for both grub2 and grub-installer,
and both are needed for this fix to work.

In grub-installer, I've added the front-end which drives most of this:

  * Add extra support for forcing installation to the EFI
removable media path, either during installation (low priority or
preseeding), or as an extra rescue-mode option to help people fix
their systems post-install once they realise they need to. (#767037)

I've also added the backend support to grub2 (grub-install) which does
the extra work needed:

  * Add support for forcing an extra copy of grub-efi to the removable
media path /boot/efi/EFI/BOOT/BOOT$ARCH.EFI (#767037)

Debdiffs attached (grub2 filtered to remove noise in the po/ dir).

unblock grub-installer/1.102
unblock grub2/2.02~beta2-18

Clearly, this is also d-i material. KiBi has been letting me drive
this, and I hope he's still happy here. I've added d-boot in CC
accordingly.

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

Kernel: Linux 3.2.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
diff -Nru grub-installer-1.101/debian/changelog grub-installer-1.102/debian/changelog
--- grub-installer-1.101/debian/changelog	2014-11-12 15:16:49.0 +
+++ grub-installer-1.102/debian/changelog	2014-12-08 21:39:23.0 +
@@ -1,3 +1,13 @@
+grub-installer (1.102) unstable; urgency=medium
+
+  [ Steve McIntyre ]
+  * Add extra support for forcing installation to the EFI
+removable media path, either during installation (low priority or
+preseeding), or as an extra rescue-mode option to help people fix
+their systems post-install once they realise they need to. (#767037)
+
+ -- Steve McIntyre <93...@debian.org>  Mon, 01 Dec 2014 02:49:36 +
+
 grub-installer (1.101) unstable; urgency=medium
 
   [ Steve McIntyre ]
diff -Nru grub-installer-1.101/debian/grub-installer.templates grub-installer-1.102/debian/grub-installer.templates
--- grub-installer-1.101/debian/grub-installer.templates	2014-09-28 22:03:12.0 +0100
+++ grub-installer-1.102/debian/grub-installer.templates	2014-12-08 21:39:23.0 +
@@ -209,6 +209,21 @@
 # :sl1:
 _Description: Updating /etc/kernel-img.conf...
 
+Template: grub-installer/progress/step_force_efi_removable
+Type: text
+# :sl1:
+_Description: Checking whether to force usage of the removable media path
+
+Template: grub-installer/progress/step_mount_filesystems
+Type: text
+# :sl1:
+_Description: Mounting filesystems
+
+Template: grub-installer/progress/step_update_debconf_efi_removable
+Type: text
+# :sl1:
+_Description: Configuring grub-efi for future usage of the removable media path
+
 Template: debian-installer/grub-installer/title
 Type: text
 #  Main menu item
@@ -242,3 +257,31 @@
  Check /var/log/syslog or see virtual console 4 for the details.
  .
  Warning: Your system may be unbootable!
+
+Template: rescue/menu/grub-efi-force-removable
+Type: text
+# Rescue menu item
+# :sl2:
+_Description: Force GRUB installation to the EFI removable media path
+
+Template: grub-installer/force-efi-extra-removable
+Type: boolean
+Default: false
+# :sl1:
+_Description: Force GRUB installation to the EFI removable media path?
+ It seems that this computer is configured to boot via EFI, but maybe
+ that configuration will not work for booting from the hard
+ drive. Some EFI firmware implementations do not meet the EFI
+ specification (i.e. they are buggy!) and do not support proper
+ configuration of boot options from system hard drives.
+ .
+ A workaround for this problem is to install an extra copy of the EFI
+ version of the GRUB boot loader to a fallback location, the
+ "removable media path". Almost all EFI systems, no matter how buggy,
+ will boot GRUB that way.
+ .
+ Warning: If the installer failed to detect another operating system
+ that is present on your computer that also depends on this fallback,
+ installing GRUB there will make that operating system temporarily
+ unbootable. GRUB can be manually configured later to boot it if
+ necessary.
diff -Nru grub-installer-1.101/debian/po/zh_CN.po grub-installer-1.102/debian/po/zh_CN.po
--- grub-installer-1.101/debian/po/zh_CN.po	2014-09-

Bug#771499: [PATCH] use PROTOCOL_SSLv23 instead of PROTOCOL_SSLv3

[Romain Bignon]

Hello,

I've pushed a commit on the Weboob package git repository to add a patch to fix 
this issue:

http://anonscm.debian.org/gitweb/?p=collab-maint/weboob.git;a=summary

I'm waiting for a DD to upload a new version of the package.

Romain


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

Bug#712206:

[Ruben Undheim]

Hi,

I'm working on a package which depends on pyusb > 1.0.

Do you think this bug can be prioritized?

Since we are in freeze, I guess it should go to experimental, but it
would still help a lot.

I'm not sure if the packages that depend on the old pyusb still will
be compatible with pyusb > 1.0.

Thank you
Ruben


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

Bug#772596: asking for pre-approval: unblock: cryptsetup/2:1.6.6-4

[Jonas Meurer]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Hello,

I just prepared cryptsetup packages targeted at jessie that do fix the
following bugs:

#767832: cryptsetup: does not decrypt a split /usr as required by
initramfs-tools >= 0.118
(hope that the fix for #767832 works for #768314 as well)
#767921: files with the same name installed in / and /usr
#764564: openrc: fail to boot when encryption + lvm are present

I asked all bugreport submitters to test the prepared packages. Once I
got positive feedback, I'd like to upload the packages to unstable. But
before, I'd like to have your ok that the packages will be allowed into
jessie.

The full debdiff is attached, below follows the changelog (debian
revision and targeted distribution will be fixed in final upload):

cryptsetup (2:1.6.6-4~mejo1) mejo-unstable; urgency=medium

  [ Simon McVittie ]
  * debian/initramfs/cryptroot-script: decrypt /usr as well as / so that
split-/usr will work with initramfs-tools (>= 0.118). (closes: #767832)

  [ Jonas Meurer ]
  * Move cryptdisks_{start,stop} symlink creation from debian/rules to
postinst. Needed to support /usr-merging. Thanks to Marco d'Itri for
the patch. (closes: #767921)
  * debian/cryptdisks.funcctions: check for cryptdisks-udev initscript
before
actually invoking 'status' on it. It's only useful in ubuntu+upstart
environment anyway. (closes: #764564)

 -- Jonas Meurer   Mon, 08 Dec 2014 22:01:09 +0100

Cheers,
 jonas
diff -Nru cryptsetup-1.6.6/debian/changelog cryptsetup-1.6.6/debian/changelog
--- cryptsetup-1.6.6/debian/changelog   2014-10-22 19:28:59.0 +0200
+++ cryptsetup-1.6.6/debian/changelog   2014-12-08 22:59:47.0 +0100
@@ -1,3 +1,20 @@
+cryptsetup (2:1.6.6-4~mejo1) mejo-unstable; urgency=medium
+
+  [ Simon McVittie ]
+  * debian/initramfs/cryptroot-script: decrypt /usr as well as / so that
+split-/usr will work with initramfs-tools (>= 0.118). (closes: #767832)
+
+  [ Jonas Meurer ]
+  * Move cryptdisks_{start,stop} symlink creation from debian/rules to
+postinst. Needed to support /usr-merging. Thanks to Marco d'Itri for
+the patch. (closes: #767921)
+  * debian/cryptdisks.funcctions: check for cryptdisks-udev initscript before
+actually invoking 'status' on it. It's only useful in ubuntu+upstart
+environment anyway. (closes: #764564)
+  * 
+
+ -- Jonas Meurer   Mon, 08 Dec 2014 22:01:09 +0100
+
 cryptsetup (2:1.6.6-3) unstable; urgency=medium
 
   * debian/initramfs/cryptroot-script: fix environment variable $CRYPTTAB_TRIED
diff -Nru cryptsetup-1.6.6/debian/cryptdisks.functions 
cryptsetup-1.6.6/debian/cryptdisks.functions
--- cryptsetup-1.6.6/debian/cryptdisks.functions2014-09-21 
15:09:03.0 +0200
+++ cryptsetup-1.6.6/debian/cryptdisks.functions2014-12-08 
22:58:47.0 +0100
@@ -750,8 +750,7 @@
# will just be a no-op, but we don't want to defer to the
# other job entirely because this is the fallback for fixing
# up any ordering-dependent decrypting.
-   while status cryptdisks-udev DEVNAME="$dev_match" 2>&1 | grep 
-q 'start'
-   do
+   invoke-rc.d --quiet cryptdisks-udev status && while status 
cryptdisks-udev DEVNAME="$dev_match" 2>&1 | grep -q 'start'; do
sleep 1
done
handle_crypttab_line_start "$dst" "$src" "$key" "$opts" <&3 || 
log_action_end_msg $?
diff -Nru cryptsetup-1.6.6/debian/cryptsetup.postinst 
cryptsetup-1.6.6/debian/cryptsetup.postinst
--- cryptsetup-1.6.6/debian/cryptsetup.postinst 2014-03-03 20:25:28.0 
+0100
+++ cryptsetup-1.6.6/debian/cryptsetup.postinst 2014-12-08 22:04:51.0 
+0100
@@ -16,6 +16,12 @@
 
 case "$1" in
 configure)
+   for file in cryptdisks_start cryptdisks_stop; do
+   if [ ! -e /usr/sbin/$file ]; then
+   ln -s /sbin/$file /usr/sbin/$file
+   fi
+   done
+
if [ -x /usr/sbin/update-initramfs ]; then
update-initramfs -u
fi
diff -Nru cryptsetup-1.6.6/debian/cryptsetup.postrm 
cryptsetup-1.6.6/debian/cryptsetup.postrm
--- cryptsetup-1.6.6/debian/cryptsetup.postrm   2011-09-19 12:46:19.0 
+0200
+++ cryptsetup-1.6.6/debian/cryptsetup.postrm   2014-12-08 22:04:51.0 
+0100
@@ -7,6 +7,12 @@
if [ -x /usr/sbin/update-initramfs ]; then
update-initramfs -u
fi
+
+   for file in cryptdisks_start cryptdisks_stop; do
+   if [ -L /usr/sbin/$file ]; then
+   rm /usr/sbin/$file
+   fi
+   done
 ;;
 esac
 
diff -Nru cryptsetup-1.6.6/debian/initramfs/cryptroot-hook 
cryptsetup-1.6.6/debian/initramfs/cryptroot-hook
--- cryptsetup-1.6.6/debian/initramfs/cryptroot-hook2014-10-02 
13:20:55.0 +0200
+++ cryptsetup-1.6.6/debian/initramfs/cryptroot-hook2014-12-08 
21:59:51.00

Bug#771148: (pre-upload) unblock: pypy/2.4.0+dfsg-2

[Stefano Rivera]

Hi Dejan (2014.12.05_16:39:01_+0200)
> I have tried to build pypy on a few different boards.
>
> On boradcom (mipsel) and cavium (mipsel),
> pypy was built successfully.
>
> On cavium (mips), build is still in progress.
> But it seems that it will pass as well.
>
> On lemote-3a-itx-a1101 (mipsel),
> build was successfully finished.

Thanks for the testing. It sounds like we should continue retrying this.

> I had noticed that on mipsel-manda-02.debian.org
> it was used parallel=5
> > DEB_BUILD_OPTIONS=parallel=5.
> I am not sure if this is related with
> build failure but I will try it on lemote 3A again,
> with this option.

The failure was during translation, which is not parallel. The only part
of the pypy build that parallelises is the compilation, which I've never
known to cause trouble.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272


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

Bug#771499: [PATCH] use PROTOCOL_SSLv23 instead of PROTOCOL_SSLv3

[Jan Gerber]

--- a/weboob/deprecated/browser/browser.py.orig	2014-12-08 22:56:48.602859096 +0100
+++ b/weboob/deprecated/browser/browser.py	2014-12-08 22:56:58.818858568 +0100
@@ -730,7 +730,7 @@
 
 class HTTPSConnection2(httplib.HTTPSConnection):
 _HOSTS = {}
-_PROTOCOLS = [ssl.PROTOCOL_TLSv1, ssl.PROTOCOL_SSLv3]
+_PROTOCOLS = [ssl.PROTOCOL_TLSv1, ssl.PROTOCOL_SSLv23]
 
 def _my_create_connection(self):
 sock = socket.create_connection((self.host, self.port), self.timeout)

Bug#772329: Not a bug for us

[Martin Quinson]

severity 772329 wishlist
usertags: -goal-dash
thanks

Hello,

thanks for your report and as an upstream developer of SimGrid, I will
fix the problem. But the bashism that you found only occures when the
seq utility is not found. That's part of coreutils which is essential
on Debian, but it was not to be found on some Mac OSX systems.

Thus reducing severity and removing the tag as we are not trying to
fix Mac OSX today (lucky us).

Thanks for the report anyway,
Mt.

-- 
As for global warming, it may be that open source communities don't
believe in politics, but it does not mean that politics doesn't apply
to them. You can ignore politics, but the politics will not ignore you.
   --- Poul-Henning Kamp , FOSDEM 2014.


signature.asc
Description: Digital signature

Bug#501566: [MAN] Clarify two redirection mechanisms

[Jonathan Nieder]

Hi Stéphane,

Stéphane Aulery wrote:

> As for me, I'm not bothered by the word "resource". It's ok for me as
> "copy". But Herbert does not agree, so I can not force him:-)).
[...]
> This is my last attempt, if there is no consensus I close the bug
> regarding Debian.

Please don't.  I can handle the bug if no one is able to come up with
a good wording.

Thanks,
Jonathan


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

Bug#768314: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping

[Jonas]

Hello Kjetil,

I guess that you discovered the bug due to a separate /usr partition. I
just prepared packages that should fix the bug for you. Could you give
them a try and report back? I'd like to get this fixed in time for jessie.

You can find the prepared packages here:

https://people.debian.org/~mejo/debian/mejo-unstable/

Cheers,
 jonas

Am 06.11.2014 um 13:56 schrieb Kjetil Kjernsmo:
> Package: cryptsetup
> Version: 2:1.6.6-3
> Severity: normal
> 
> Dear Maintainer,
> 
> I just upgraded my Wheezy laptop with an SSD to Jessie, and making
> notes to hopefully make it useful for stabilizing the next
> release. The only real issue I came across is the following, but it
> was pretty scary. See the crypttab below for the details about my
> encrypted partitions.
> 
>>* What led up to the situation?
> 
> A dist-upgrade to Jessie was performed. There were some warnings about
> LVM stuff, but that alerted me to anything that I deemed serious or
> relevant. Some packages weren't cleanly installed, it stopped with
> some texlive stuff that is surely not relevant, but the kernel was not
> upgraded when I did the first reboot.
> 
> After reboot, I get prompted for the passphrase of the root
> partition. From there, the bootup is so fast, I don't have to time to
> react to anything, before I get a message that isn't very specific
> about a problem with a the /home partition. After a while, it just
> times out, and I enter a shell as root to find a journal that tells me
> it failed. 
> 
>>   * What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> The journal gave me some hints that the passphrase was missing, which
> I kinda knew, so I just tried another reboot, and now I saw the prompt
> to enter passphrase just flashing by in a split second. I enter it
> anyway, even though the prompt has disappeared.
> 
> 
>>   * What was the outcome of this action?
> 
> And that worked!
> 
>>   * What outcome did you expect instead?
> 
> The bootup should pause at the prompt, so that there is no doubt what
> should be done.
> 
> So, basically, it works, but the UX of this is horrible and really
> scary since you are afraid that you cannot recover the data in the
> partition (yeah, I have backup, so I was just marginally worried :-) )
> 
> BTW, remote filesystems have been deleted from the below fstab.
> 
> I hope this is helpful.
> 
> Cheers,
> 
> Kjetil
> 
> -- Package-specific info:
> -- /proc/cmdline
> BOOT_IMAGE=/vmlinuz-3.16-3-amd64 root=/dev/mapper/owl-root ro quiet
> 
> -- /etc/crypttab
> owl-home_crypt UUID=ffe18d19-c031-42ec-a6bb-b75aa7ddd9bc none luks
> sda5_crypt UUID=db58ea52-3415-4737-863b-5129cf2db308 none luks
> 
> -- /etc/fstab
> # /etc/fstab: static file system information.
> #
> # Use 'blkid' to print the universally unique identifier for a
> # device; this may be used with UUID= as a more robust way to name devices
> # that works even if disks are added and removed. See fstab(5).
> #
> #
> /dev/mapper/owl-root /   ext4
> discard,noatime,errors=remount-ro 0   1
> # /boot was on /dev/sda1 during installation
> UUID=b0442da3-f1e7-41ac-a324-07322b487586 /boot   ext2defaults
> 0   2
> /dev/mapper/owl-home_crypt /home   ext4discard,noatime0   
> 2
> /dev/mapper/owl-lvol0 /usr ext4discard,noatime  0   1
> /dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0
> 
> -- lsmod
> Module  Size  Used by
> rpcsec_gss_krb534296  0 
> nfsv4 414796  1 
> dns_resolver   12641  1 nfsv4
> xt_tcpudp  12527  54 
> ip6table_mangle12540  0 
> iptable_nat12646  1 
> nf_conntrack_ipv4  18455  20 
> nf_defrag_ipv4 12483  1 nf_conntrack_ipv4
> nf_nat_ipv412912  1 iptable_nat
> nf_nat 18241  2 nf_nat_ipv4,iptable_nat
> xt_TCPMSS  12588  6 
> xt_LOG 17171  45 
> ipt_REJECT 12465  0 
> iptable_mangle 12536  0 
> xt_multiport   12518  0 
> xt_state   12503  0 
> xt_limit   12601  49 
> xt_conntrack   12681  19 
> nf_conntrack_ftp   16783  0 
> nf_conntrack   87432  7 
> nf_nat,xt_state,nf_nat_ipv4,xt_conntrack,nf_conntrack_ftp,iptable_nat,nf_conntrack_ipv4
> ip6table_filter12540  1 
> ip6_tables 26025  2 ip6table_filter,ip6table_mangle
> iptable_filter 12536  1 
> ip_tables  26011  3 iptable_filter,iptable_mangle,iptable_nat
> x_tables   27111  14 
> ip6table_filter,ip6table_mangle,ip_tables,xt_tcpudp,xt_limit,xt_state,xt_conntrack,xt_LOG,xt_multiport,iptable_filter,xt_TCPMSS,ipt_REJECT,iptable_mangle,ip6_tables
> binfmt_misc16949  1 
> nfsd  263053  2 
> auth_rpcgss51240  2 nfsd,rpcsec_gss_krb5
> oid_registry   12419  1 auth_rpcgss
> nfs_acl12511  1 nfsd
> nfs   

Bug#764564: please test updated cryptsetup packages

[Jonas Meurer]

Hello everyone,

I prepared updated cryptsetup packages that fix the following bugs:

#767832: cryptsetup: does not decrypt a split /usr as required by
initramfs-tools >= 0.118
#767921: files with the same name installed in / and /usr
#764564: openrc: fail to boot when encryption + lvm are present

Please give them a try and report back whether they work for you and fix
the particular bug you discovered.

You can find the prepared packages here:

https://people.debian.org/~mejo/debian/mejo-unstable/

Cheers,
 jonas


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

Bug#501566: [MAN] Clarify two redirection mechanisms

[Stéphane Aulery]

Hi Jonathan,

Le lundi 08 décembre 2014 à 01:56:15, Jonathan Nieder a écrit :
> 
> Stéphane Aulery wrote:
> 
> > As for me, I'm not bothered by the word "resource". It's ok for me as
> > "copy". But Herbert does not agree, so I can not force him:-)).
> [...]
> > This is my last attempt, if there is no consensus I close the bug
> > regarding Debian.
> 
> Please don't.  I can handle the bug if no one is able to come up with
> a good wording.

And how will you do if no one has a good wording?

I am willing to wait.

Regards,

-- 
Stéphane Aulery


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

Bug#766028: wine32 segfault

[Uwe Storbeck]

Hi

This bug is not fixed in wine32 version 1.6.2-17 for me too. Only
wine is affected by the bug, but not wine-development.

On Dec 07, Michael Gilbert wrote:
> The original report indicates that the nvidia proprietary driver was
> used.  Is this true for everyone running into the problem?

I also use the nvidia binary driver.

> If so, can you try nouveau instead?

The nouveau driver does not support my hardware configuration
(2 GPUs with 3 screens), at least the last time I tried it.
People which need Direct3D or OpenGL support in wine usually
play games with it and need the better performance of the nvidia
binary driver. So switching to the nouveau driver is often not
an option.

To narrow down the problem I have tested several wine32 versions.
The bug has been introduced between version 1.6.2-10 and version
1.6.2-11. It is sufficient to downgrade the wine32 package and no
other of the wine packages.

When I understand the package version numbers in Debian correctly
the wine32 package versions 1.6.2-10 and 1.6.2-11 are produced
from the same upstream sources. So the bug has been introduced in
the Debian part of the wine32 package between version 1.6.2-10
and version 1.6.2-11. That should considerably narrow things
down.

It's also suspect that wine does not segfault when I run it
inside of gdb. Maybe something in the build process of the
wine32 package has changed between these two versions and causes
the problem.

When I run wine32 in gdb the process gets a signal SIGUSR1 in
wine32 version 1.6.2-11 which I don't see in version 1.6.2-10:

  Program received signal SIGUSR1, User defined signal 1.

The gdb logs for both versions are attached below.

I don't know why this signal has been introduced and what it's
used for, but it may cause the segfault when it's not caught
properly.

I hope this helps a bit to narrow down this bug.

Regards

Uwe


wine32 version 1.6.2-11:

$ gdb wine32
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
[..]
Reading symbols from wine32...(no debugging symbols found)...done.
(gdb) run dxdiag
Starting program: /usr/bin/wine32 dxdiag
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
[New Thread 0xf7c27b40 (LWP 10161)]
[Thread 0xf7c27b40 (LWP 10161) exited]
process 10157 is executing new program: 
/usr/lib/i386-linux-gnu/wine/bin/wine-preloader
fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x0030
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:win:EnumDisplayDevicesW ((null),0,0x32d6e4,0x), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32d504,0x), stub!
fixme:ddraw:ddraw7_Initialize Ignoring guid 
{aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category 
{33d9a760-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category 
{33d9a761-90c8-11d0-bd43-00a0c911ce86} not found
[New LWP 10192]

Program received signal SIGUSR1, User defined signal 1.
[Switching to LWP 10192]
0xf7ffd430 in ?? ()
(gdb) cont
Continuing.
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category 
{cc7bfb41-f175-11d1-a392-00e0291f3959} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category 
{cc7bfb46-f175-11d1-a392-00e0291f3959} not found
fixme:dxdiag:wWinMain Information dialog is not implemented
[LWP 10192 exited]
[Inferior 1 (process 10157) exited normally]
(gdb) quit


wine32 version 1.6.2-10:

$ gdb wine32
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
[..]
Reading symbols from wine32...(no debugging symbols found)...done.
(gdb) run dxdiag
Starting program: /usr/bin/wine32 dxdiag
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
[New Thread 0xf7c27b40 (LWP 8686)]
[Thread 0xf7c27b40 (LWP 8686) exited]
process 8682 is executing new program: 
/usr/lib/i386-linux-gnu/wine/bin/wine-preloader
fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x0030
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:win:EnumDisplayDevicesW ((null),0,0x32d6e4,0x), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32d504,0x), stub!
fixme:ddraw:ddraw7_Initialize Ignoring guid 
{aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category 
{33d9a760-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category 
{33d9a761-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category 
{cc7bfb41-f175-11d1-a392-00e0291f3959} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category 
{cc7bfb46-f175-11d1-a392-00e0291f3959} not found
fixme:dxdiag:wWinMain Information dialog is not implemented
[Inferior 1 (process 8682) exited normally]
(gdb) quit


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.or

Bug#772584: [Pkg-xfce-devel] Bug#772584: xfce4-power-manager: display unlocked after resume

[Mike Kupfer]

Yves-Alexis Perez wrote:

> If you're using the logout dialog, you're actually using xfce4-session,
> which also has a (different from xfpm) setting for locking the screen
> before suspend/sleep. You can check that in the session settings, last
> (Advanced) tab. Can you report back?

Aha!  Yes, the setting was unset in for xfce4-session.  I set it, and
now I get a locked screen when I resume from suspend or hibernation.
Thanks!

> Also, if you want your power manager icon back, you should add the power
> manager plugin to your panel.

Yes, I found the power manager plugin.  But this is for a desktop
system, so the main thing I used the icon for was initiating
suspend/hibernate, and the plugin doesn't provide that functionality.
(Sorry, I worded that part of the bug report badly.)  Thanks anyway.

warm regards,
mike


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

Bug#772592: [Pkg-amule-devel] Bug#772592: amule: occasional segmentation fault

[Sandro Tosi]

control: tags -1 + moreinfo

Hi!

On Mon, Dec 8, 2014 at 9:30 PM, Dmitry Smirnov  wrote:
> I used all my quota this month and my ISP throttled connection to 512/512.
> That's when amule begin to crash -- it works for less than an hour until
> "Segmentation fault". I have only KAD enabled and I have a feeling that it may
> be related to number of simultaneous connections (although lowering max
> simultaneous connections from 900 to 90 did not help). No errors are logged to
> console and I tried to run amule under GDB for a while but under GDB it is
> slow and problem do not manifest. Without GDB it crashes in 30...60 min.

I think that the only way to report it upstream for a fix is to let it
run under gdb and wait for it to crash and then generate the required
tracebacks.

> I think on fast connection I've seen few occasional segfaults in the past but
> it was not unusual for amule to last for days and even weeks while now I have
> an hour at most.

I have an instance of amule running from more than 1week and it is the
same version you are reporting this bug againts.

> This is on up-to-date Jessie.

Just a note: Jessie doesnt include amule, as it was not possible to
port it to WX3.0

Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


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

Bug#767037: Grub EFI fallback - patches for review

[Steve McIntyre]

On Mon, Dec 08, 2014 at 07:29:56PM +, Ian Campbell wrote:
>On Mon, 2014-12-08 at 01:36 +, Steve McIntyre wrote:
>> >The current package in sid (-17) is unblocked and I think ought to
>> >transition tomorrow (or perhaps Tuesday depending on TZ). I propose to
>> >upload -18 with this change shortly after that happens. Will you take
>> >care of the unblock request or at least provide me some text with the
>> >rationale etc.
>> 
>> I'll ask for the unblock, and I'll also upload grub-installer the same
>> day.
>
>Upload == done.

and grub-installer 1.102 is in incoming now too.

Christian, I'm sorry to do this to you, but we have some more template
translations... :-/

I'm also hoping to get some more (small) changes done in the next
week, for more UEFI goodness.

>> >-17 included some patches from Colin to make the 32-bit linuxefi command
>> >work.
>> 
>> Yup, saw that. I'm looking into 32-bit EFI stuff right now. Using a
>> Mac atm *shudder*
>
>Urk!

Exactly!

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
< Aardvark> I dislike C++ to start with. C++11 just seems to be
handing rope-creating factories for users to hang multiple
instances of themselves.


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

Bug#772594: unblock: astroid/1.2.1-3

[Sandro Tosi]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package astroid

As previously pre-approved in #772038, please unblock astroid, this fix is
needed to improve the fix at #591676 in order to allow users to load extensions
if the want to (hence bringing back an-par at functionaly level what pylint was
before, and as upstream have decided to evolve it).

unblock astroid/1.2.1-3

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

Kernel: Linux 3.14-2-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)
diff -Nru astroid-1.2.1/debian/changelog astroid-1.2.1/debian/changelog
--- astroid-1.2.1/debian/changelog	2014-11-23 13:36:47.0 +
+++ astroid-1.2.1/debian/changelog	2014-12-08 21:43:06.0 +
@@ -1,3 +1,11 @@
+astroid (1.2.1-3) unstable; urgency=medium
+
+  * debian/patches/afea46c0380956213976db2ce0f1e8f3cf6a0abc.patch
+- enable fine-grained control over extensions loading; this fix is needed
+  after #591676 fix; Addresses: #772018
+
+ -- Sandro Tosi   Mon, 08 Dec 2014 21:43:04 +
+
 astroid (1.2.1-2) unstable; urgency=medium
 
   * debian/patches/e24cacb15e2e152db155fdca9197a8d1bf9ce235.patch
diff -Nru astroid-1.2.1/debian/patches/afea46c0380956213976db2ce0f1e8f3cf6a0abc.patch astroid-1.2.1/debian/patches/afea46c0380956213976db2ce0f1e8f3cf6a0abc.patch
--- astroid-1.2.1/debian/patches/afea46c0380956213976db2ce0f1e8f3cf6a0abc.patch	1970-01-01 01:00:00.0 +0100
+++ astroid-1.2.1/debian/patches/afea46c0380956213976db2ce0f1e8f3cf6a0abc.patch	2014-12-08 21:34:50.0 +
@@ -0,0 +1,44 @@
+# HG changeset patch
+# User Torsten Marek 
+# Date 1416661998 -3600
+# Node ID afea46c0380956213976db2ce0f1e8f3cf6a0abc
+# Parent  c9c283ee85618a5e3a0701dac0925804a73ec4b6
+Add support for more fine-grained control over extension loading.
+
+--- a/manager.py
 b/manager.py
+@@ -86,6 +86,8 @@ class AstroidManager(OptionsProviderMixI
+ self.astroid_cache = {}
+ self._mod_file_cache = {}
+ self.transforms = {}
++self.always_load_extensions = False
++self.extension_package_whitelist = set()
+ 
+ def ast_from_file(self, filepath, modname=None, fallback=True, source=False):
+ """given a module name, return the astroid object"""
+@@ -113,6 +115,16 @@ class AstroidManager(OptionsProviderMixI
+ from astroid.builder import AstroidBuilder
+ return AstroidBuilder(self).string_build('', modname)
+ 
++def _can_load_extension(self, modname):
++if self.always_load_extensions:
++return True
++if modutils.is_standard_module(modname):
++return True
++parts = modname.split('.')
++return any(
++'.'.join(parts[:x]) in self.extension_package_whitelist
++for x in range(1, len(parts) + 1))
++
+ def ast_from_module_name(self, modname, context_file=None):
+ """given a module name, return the astroid object"""
+ if modname in self.astroid_cache:
+@@ -129,7 +141,7 @@ class AstroidManager(OptionsProviderMixI
+ if module is not None:
+ return module
+ elif mp_type in (imp.C_BUILTIN, imp.C_EXTENSION):
+-if mp_type == imp.C_EXTENSION and not modutils.is_standard_module(modname):
++if mp_type == imp.C_EXTENSION and not self._can_load_extension(modname): 
+ return self._build_stub_module(modname)
+ try:
+ module = modutils.load_module_from_name(modname)
diff -Nru astroid-1.2.1/debian/patches/series astroid-1.2.1/debian/patches/series
--- astroid-1.2.1/debian/patches/series	2014-11-23 13:36:27.0 +
+++ astroid-1.2.1/debian/patches/series	2014-12-08 21:34:50.0 +
@@ -1 +1,2 @@
 e24cacb15e2e152db155fdca9197a8d1bf9ce235.patch
+afea46c0380956213976db2ce0f1e8f3cf6a0abc.patch

Bug#757883: Patch for Loopback cfg support

[adrian15]

El 08/12/14 a las 07:28, Daniel Baumann escribió:

On 12/08/14 00:09, jnqnfe wrote:

I believe I'm right in saying that you must
build against live-build 4.x, preferably the debian-next branch


correct, we will not touch live-* 3.x anymore unless there's a security
issue or another bug making the existing, officially built 3.x/wheezy
live images unusable.


I attach the rebased commit for loopback cfg adapted to debian-next as 
requested and with some of your suggestions implemented.


The order in binary file remains the same because, as I explained 
earlier, syslinux renames the kernel filenames.


Just in case you want the detailed commits from debian-old-3.0 to 
debian-next they can be found here:


https://github.com/adrian15/live-build/commit/b907d5ca4cfac5407e4231a202b5b84cfcf8c56c
https://github.com/adrian15/live-build/commit/5c7636f8848b3d1d058bb2ed7fd69e01ad05270d
https://github.com/adrian15/live-build/commit/1dcec1bdc96a9b5eefb3a464b40250738bf3dfec
https://github.com/adrian15/live-build/commit/f08a3bbfeb98faad99643dbf88aead8a98a69b6f
https://github.com/adrian15/live-build/commit/0cd9b26c8697d4eeb5e950546c6e7b9c94b5ac14
https://github.com/adrian15/live-build/commit/77ac5d6acce430b6a1106e0cdb20a177e36a1b48
https://github.com/adrian15/live-build/commit/9afdaf59138392b09fce41bb522d0d0e1ea1ca11

The new patch and the resulting binary_loopback_cfg file can be also 
found here:


https://github.com/adrian15/live-build/commit/9c67d2d05502e03e0c52827a4e0c7d088f361e88

https://github.com/adrian15/live-build/blob/9c67d2d05502e03e0c52827a4e0c7d088f361e88/scripts/build/binary_loopback_cfg

adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/
commit 9c67d2d05502e03e0c52827a4e0c7d088f361e88
Author: Adrian Gibanel Lopez 
Date:   Sun Dec 7 18:20:09 2014 +0100

This is a patch for adding Loopback cfg support.

Development details


* This patch has been based originally on: binary_grub2 . It has been
improved thanks to some binary_syslinux bits.

* This patch ensures that binary_loopback_cfg needs is run before binary_syslinux is run.
The reason is that it reuses some code from binary_syslinux to avoid
problems when binary_syslinux renames the kernel filenames.

* This patch already supports CPU detection

* I haven't tested all the possible scenarios for the script (with the
latest version). When amd64 and 486 Gnu/Linux flavours is used and the
bootloader is syslinux it works ok.

* I have not implemented a disable switch for not generating it.
Usually you always want loopback.cfg to be there.

* Compared to binary_grub2 script I have removed the installation
entries because I did not see any of them in binary_syslinux.

How to test
---

These are some steps to easily test if Looback cfg support is working ok.

0) We assume you have generated an iso
1) Make sure you have a partition that Grub understands. Plain ext4 or
vfat should do it.
2) Create directory: /boot/boot-isos/
3) Put the iso file into that directory making sure it has an ISO or iso
extension.
4) Setup your computer to boot from cdrom and use: Super Grub2 Disk
2.00s2 (Hybrid version recommended)
5) Choose Boot manually...
6) Choose Bootable ISOs (in /boot- ... )
7) Choose (the detected) GRUB Loopback Config
(hdN,msodsN)/boot/boot-ios/name-of-the.iso
8) You will be presented your loopback.cfg. Choose anyone of the entries
(unless it does not match your cpu architecture of course).
9) You should boot into your Debian Live without problems (thanks to
findiso boot parametre).

If you ever wanted to test from your grub2 installation instead from
Super Grub2 Disk check: http://www.supergrubdisk.org/wiki/Loopback.cfg
for an example.

diff --git a/scripts/build/binary b/scripts/build/binary
index c1f9ec6..97d7ebc 100755
--- a/scripts/build/binary
+++ b/scripts/build/binary
@@ -63,6 +63,7 @@ lb binary_linux-image ${@}
 lb binary_memtest ${@}
 lb binary_grub ${@}
 lb binary_grub2 ${@}
+lb binary_loopback_cfg ${@}
 lb binary_syslinux ${@}
 lb binary_disk ${@}
 lb binary_loadlin ${@}
diff --git a/scripts/build/binary_loopback_cfg b/scripts/build/binary_loopback_cfg
new file mode 100755
index 000..64958c4
--- /dev/null
+++ b/scripts/build/binary_loopback_cfg
@@ -0,0 +1,311 @@
+#!/bin/sh
+
+## live-build(7) - System Build Scripts
+## Copyright (C) 2006-2014 Daniel Baumann 
+##
+## This program comes with ABSOLUTELY NO WARRANTY; for details see COPYING.
+## This is free software, and you are welcome to redistribute it
+## under certain conditions; see COPYING for details.
+
+
+set -e
+
+# Including common functions
+[ -e "${LIVE_BUILD}/scripts/build.sh" ] && . "${LIVE_BUILD}/scripts/build.sh" || . /usr/lib/live/build.sh
+
+# Setting static var

Bug#772593: build-essential: essential-packages-list empty on kfreebsd

[Jakub Wilk]

Package: build-essential
Version: 11.7
User: debian-...@lists.debian.org
Usertags: kfreebsd
Control: affects -1 + dh-buildinfo

The list of essential packages is empty on kfreebsd:

$ cat /usr/share/build-essential/essential-packages-list
No essential packages list is available


This makes dh-buildinfo unhappy:

$ fakeroot dh_buildinfo
Use of uninitialized value within @essentials in string ne at 
/usr/bin/dh_buildinfo line 216.


-- System Information:
Debian Release: 8.0
 APT prefers unstable
 APT policy: (990, 'unstable')
Architecture: kfreebsd-i386 (i386)

--
Jakub Wilk


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

Bug#772592: amule: occasional segmentation fault

[Dmitry Smirnov]

Package: amule
Version: 2.3.1+git1a369e47-3
Severity: normal

I used all my quota this month and my ISP throttled connection to 512/512.
That's when amule begin to crash -- it works for less than an hour until
"Segmentation fault". I have only KAD enabled and I have a feeling that it may 
be related to number of simultaneous connections (although lowering max 
simultaneous connections from 900 to 90 did not help). No errors are logged to 
console and I tried to run amule under GDB for a while but under GDB it is 
slow and problem do not manifest. Without GDB it crashes in 30...60 min.

I think on fast connection I've seen few occasional segfaults in the past but 
it was not unusual for amule to last for days and even weeks while now I have 
an hour at most.

This is on up-to-date Jessie.

I'm out of ideas how to troubleshoot further...

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16.0-4-amd64

-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B

---

Theology is but the ignorance of natural causes reduced to a system.
-- Baron Paul Henri T. d'Holbach



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

Bug#501566: [MAN] Clarify two redirection mechanisms

[Stéphane Aulery]

Le lundi 08 décembre 2014 à 08:37:38, Stephane CHAZELAS a écrit :
> 2014-12-08 19:50:05 +0100, Stéphane Aulery:
>  [n1]>&n2Redirect standard output (or fd n1) to the same "open
>  file description" as on fd n2.
>  
>  [n1]>&n2Copy fd n2 as stdout (or fd n1)
>  
>  [n1]>&n2Redirect standard output (or fd n1) to the same
>  resource as currently open on fd n2.
> 
> > >> "Resource" is rather unwieldy, how about simply "file"?
> > >
> > > "file" could be misleading
> > >
> > > [...]
> > >
> > > IMO, "resource" is vague enough so as not to give the wrong idea
> > > and I like that wording because it conveys the intended
> > > mechanism clearly ("redirect to same thing as"). But I agree
> > > it's not ideal.
> > 
> > It is true that "resource" is dissonant as "file" is too restrictive. The
> > term "file descriptor" is used above. Why not use it again?
> [...]
> 
> If you say redirect fd n1 to fd n2, you confuse people (and I've
> seen a lot of people being confused in such a way) as they
> start thinking the fds become somehow linked (for instance that
> in 2>&1 > file, stderr goes to stdout and then both to "file"
> which is not the case). When you start thinking of "&" as
> "/address/ of" (yet another improper wording) or "resource
> currently open on", that clears that confusion.
> 
> If you don't like the "resource" wording, you can always got for
> the "copy" one above or the POSIX wording:
> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_07_05

As for me, I'm not bothered by the word "resource". It's ok for me as
"copy". But Herbert does not agree, so I can not force him:-)).

I wonder more and more if Herbert is willing to accept this tiny patch
or another. I would not be wasting his time if he does not want or can
not take care of that. This is free software, there is no obligation.

This is my last attempt, if there is no consensus I close the bug
regarding Debian.

Have a nice day.

-- 
Stéphane Aulery


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

Bug#772591: uzbl: Please add .desktop file

[Francesco]

Package: uzbl
Version: 0.0.0~git.20120514-1.1
Severity: wishlist

Dear Maintainer,

when using uzbl with a light DE (xfce or lxde, for example) it doesn't
add a menu entry; it would be useful to add a .desktop file in
/usr/share/applications with proper parameter to have link done.

It would be a good thing to have an icon too, but even without
the link would be useful.



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

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

Versions of packages uzbl depends on:
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-13
ii  libcairo2   1.14.0-2.1
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.5.2-2
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.1-1
ii  libgtk2.0-0 2.24.25-1
ii  libjavascriptcoregtk-1.0-0  2.4.7-2
ii  libpango1.0-0   1.36.8-2
ii  libsoup2.4-12.48.0-1
ii  libwebkitgtk-1.0-0  2.4.7-2
ii  libx11-62:1.6.2-3
ii  python  2.7.8-2
ii  python-gobject  3.14.0-1
ii  python-gtk2 2.24.0-4
ii  python-support  1.0.15

Versions of packages uzbl recommends:
ii  python-simplejson  3.6.5-1
ii  socat  1.7.2.4-1+b1
ii  suckless-tools 40-1
ii  xclip  0.12+svn84-4
ii  zenity 3.14.0-1

uzbl 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#768407: [pkg-cryptsetup-devel] Bug#768407: Bug solved

[Jonas Meurer]

Hey Quentin,

sorry for the delay.

Am 19.11.2014 um 22:09 schrieb Quentin Lefebvre:
> Hi again,
> 
> Actually, I could make it work even with blank passwords (or empty key
> file provided either directly or through STDIN).
> 
> I'd like to send you a patch.
> 
> What is the preferred tool to write a patch for cryptsetup?

I saw that you discussed this bug upstream on the dm-crypt mailinglist.
What was the outcome? Feel free to provide a patch in unified diff
format if you have one.

Kind regards,
 jonas


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

Bug#771860: RFS: gnucheese/1.00-1

[Michel Van den Bergh]

Hi Vincent,

Thanks for the detailed review! I will take care of it (I am currently 
at a conference so
it may take a couple of days). I will probably have to get back to you 
with some questions.


Best regards,
Michel


Vincent Legout wrote:

Hi Michel,

Michel Van den Bergh  writes:


   I am looking for a sponsor for my package "gnucheese"

I'd be glad to sponsor your package, but I have a few comments
first. Could you please fix them and I'll upload gnucheese.

- I can't download the tar.gz from your website (permission error):

http://hardy.uhasselt.be/GnuCheese/gnucheese-1.00.tar.gz

- You missed the gtb directory in the debian/copyright file. You need to
   include it even if gnucheese is not using it at buildtime. But why
   include it in the tarball in the first place? See for example this
   wiki page for why including third-party libraries is not recommended:

https://wiki.debian.org/UpstreamGuide#No_inclusion_of_third_party_code

- AUTHORS doesn't match debian/copyright

- pgheader.c has a MIT license

- You can remove debian/README.Debian and debian/README.source. And I
   think also debian/doc, because NEWS and README are automatically
   picked by dh_installdocs. And as NEWS and TODO are empty, I'd say you
   can remove them from the upstream tarball.

- This lintian info tag could be fixed, just remove the comments in
   debian/watch:

I: gnucheese source: debian-watch-contains-dh_make-template

- You can also remove the comments in debian/rules

- I see you commented the Vcs-* fields in debian/control. You can join
   the collab-maint group on alioth.debian.org if you want to maintain
   the package there. Otherwise, I'd say you can remove those 2 lines.

- In Build-Depends, you shouldn't need flex and perl. And libgaviotatb1
   can also be removed, you only need to Build-Depends on the -dev
   library.

- I cannot build it, ./configure fails. There is a problem with the
   system gtb library. It builds fine if I remove --with-builtin-gtb=no
   however. But this should be fixed because the Debian package shouldn't
   be built with the embedded copy of gtb.

- It can't be built twice in a row because gnucheese.man is created
   during the build. You can remove this file by adding it into
   debian/clean.

- These 2 lintian tags can be fixed:

gnucheese: spelling-error-in-binary usr/games/gnucheese diplay display
gnucheese: description-synopsis-might-not-be-phrased-properly

   To fix the second one, removing the capitalized M at the beginning of
   the short description should be enough.

- I have this message when lauching gnucheese:

Can't open gnuchess.bin
Unable to find a polyglot book...

   while I have gnuchess-book installed. Where does it look for
   gnuchess.bin?


Thanks,
Vincent



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

Bug#772590: please use a more recent autoconf to ease cross building

[Helmut Grohne]

Package: src:blt
Version: 2.5.3+dfsg-1
Severity: wishlist
User: helm...@debian.org
Usertags: rebootstrap

The blt package uses a relatively old version of autoconf and does not
regenerate configure from configure.in during build. As a result it uses
a very old implementation of AC_CHECK_SIZEOF that does not work well
with cross compiling. As a result a cross configure run without setting
CONFIG_SITE results in:

| checking size of int... 0
| checking size of long... 0
| checking size of long long... 0
| checking size of void *... 0

This is unfortunate in various ways:
 * configure succeeds without a mention that things went wrong
 * The first indication that something failed is a linker error.
 * These values are computable without executing host-arch code. More
   recent autotools do that.

A fixed configure will use ac_fn_c_compute_int to determine these
values.

I understand that making the current configure.in work with more recent
autotools requires some work, but at some point this is necessary for
supporting new ports anyway. Thanks for considering.

Helmut


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

Bug#770616: [PATCH] use PROTOCOL_SSLv23 instead of PROTOCOL_SSLv3

[Jan Gerber]

Porting nossl3.patch from
https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=17;filename=python2.7-nossl3.patch;att=1;bug=768611
to gevent.ssl

Not that upstream does not like it that Debian just removed
ssl.PROTOCOL_SSLv3 (https://github.com/hypothesis/h/issues/1704)
diff a/gevent/ssl.py b/gevent/ssl.py
--- a/gevent/ssl.py
+++ b/gevent/ssl.py
@@ -382,7 +382,7 @@ def wrap_socket(sock, keyfile=None, certfile=None,
  ciphers=ciphers)
 
 
-def get_server_certificate(addr, ssl_version=PROTOCOL_SSLv3, ca_certs=None):
+def get_server_certificate(addr, ssl_version=PROTOCOL_SSLv23, ca_certs=None):
 """Retrieve the certificate from the server at the specified address,
 and return it as a PEM-encoded string.
 If 'ca_certs' is specified, validate the server cert against it.
diff a/greentest/2.6/test_ssl.py b/greentest/2.6/test_ssl.py
--- a/greentest/2.6/test_ssl.py
+++ b/greentest/2.6/test_ssl.py
@@ -60,7 +60,6 @@ class BasicTests(unittest.TestCase):
 def test_constants(self):
 ssl.PROTOCOL_SSLv2
 ssl.PROTOCOL_SSLv23
-ssl.PROTOCOL_SSLv3
 ssl.PROTOCOL_TLSv1
 ssl.CERT_NONE
 ssl.CERT_OPTIONAL
@@ -839,7 +838,7 @@ else:
 try_protocol_combo(ssl.PROTOCOL_SSLv2, ssl.PROTOCOL_SSLv2, True, ssl.CERT_OPTIONAL)
 try_protocol_combo(ssl.PROTOCOL_SSLv2, ssl.PROTOCOL_SSLv2, True, ssl.CERT_REQUIRED)
 try_protocol_combo(ssl.PROTOCOL_SSLv2, ssl.PROTOCOL_SSLv23, True)
-try_protocol_combo(ssl.PROTOCOL_SSLv2, ssl.PROTOCOL_SSLv3, False)
+try_protocol_combo(ssl.PROTOCOL_SSLv2, ssl.PROTOCOL_SSLv23, False)
 try_protocol_combo(ssl.PROTOCOL_SSLv2, ssl.PROTOCOL_TLSv1, False)
 
 def test_protocol_sslv23(self):
@@ -856,15 +855,12 @@ else:
 sys.stdout.write(
 " SSL2 client to SSL23 server test unexpectedly failed:\n %s\n"
 % str(x))
-try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_SSLv3, True)
 try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_SSLv23, True)
 try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_TLSv1, True)
 
-try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_SSLv3, True, ssl.CERT_OPTIONAL)
 try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_SSLv23, True, ssl.CERT_OPTIONAL)
 try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_TLSv1, True, ssl.CERT_OPTIONAL)
 
-try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_SSLv3, True, ssl.CERT_REQUIRED)
 try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_SSLv23, True, ssl.CERT_REQUIRED)
 try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_TLSv1, True, ssl.CERT_REQUIRED)
 
@@ -874,12 +870,11 @@ else:
 sys.stdout.write("\ntest_protocol_sslv3 disabled, "
  "as it fails on OpenSSL 1.0.0+")
 return
-try_protocol_combo(ssl.PROTOCOL_SSLv3, ssl.PROTOCOL_SSLv3, True)
-try_protocol_combo(ssl.PROTOCOL_SSLv3, ssl.PROTOCOL_SSLv3, True, ssl.CERT_OPTIONAL)
-try_protocol_combo(ssl.PROTOCOL_SSLv3, ssl.PROTOCOL_SSLv3, True, ssl.CERT_REQUIRED)
-try_protocol_combo(ssl.PROTOCOL_SSLv3, ssl.PROTOCOL_SSLv2, False)
-try_protocol_combo(ssl.PROTOCOL_SSLv3, ssl.PROTOCOL_SSLv23, False)
-try_protocol_combo(ssl.PROTOCOL_SSLv3, ssl.PROTOCOL_TLSv1, False)
+try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_SSLv23, True)
+try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_SSLv23, True, ssl.CERT_OPTIONAL)
+try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_SSLv23, True, ssl.CERT_REQUIRED)
+try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_SSLv2, False)
+try_protocol_combo(ssl.PROTOCOL_SSLv23, ssl.PROTOCOL_TLSv1, False)
 
 def test_protocol_tlsv1(self):
 """Connecting to a TLSv1 server with various client options"""
@@ -891,7 +886,6 @@ else:
 try_protocol_combo(ssl.PROTOCOL_TLSv1, ssl.PROTOCOL_TLSv1, True, ssl.CERT_OPTIONAL)
 try_protocol_combo(ssl.PROTOCOL_TLSv1, ssl.PROTOCOL_TLSv1, True, ssl.CERT_REQUIRED)
 try_protocol_combo(ssl.PROTOCOL_TLSv1, ssl.PROTOCOL_SSLv2, False)
-try_protocol_combo(ssl.PROTOCOL_TLSv1, ssl.PROTOCOL_SSLv3, False)
 try_protocol_combo(ssl.PROTOCOL_TLSv1, ssl.PROTOCOL_SSLv23, False)
 
 def test_starttls(self):
diff a/greentest/2.7/test_ftplib.py b/greentest/2.7/test_ftplib.py
--- a/greentest/2.7/test_ftplib.py
+++ b/greentest/2.7/test_ftplib.py
@@ -655,7 +655,7 @@ class TestTLS_FTPClass(TestCase):
 
 def test_auth_ssl(self):
 try:
-self.client.ssl_version = ssl.PROTOCOL_SSLv3
+self.client.ssl_version = ssl.PROTOCOL_SSLv23
 self.client.auth()
 self.assertRaises(ValueError, self.client.auth)
 finally:
diff a

Bug#772584: [Pkg-xfce-devel] Bug#772584: xfce4-power-manager: display unlocked after resume

[Yves-Alexis Perez]

On lun., 2014-12-08 at 11:24 -0800, Mike Kupfer wrote:
> With Wheezy I don't normally use the logout dialog to
> suspend/hibernate.  Instead, I invoke suspend/hibernate from the power
> manager icon in the systray; when resuming, I get a locked screen.
> If I use the logout dialog to suspend/hibernate, I do not get a locked
> screen.
> 
> But in Jessie there does not appear to be a power manager icon, so the
> logout dialog appears to be the only way to suspend/hibernate. 

So you're actually not using xfce4-power-manager here, and the settings
is irrelevant. I know, this is a bit confusing, it's supposedly going to
be better in 4.12, but eh.

If you're using the logout dialog, you're actually using xfce4-session,
which also has a (different from xfpm) setting for locking the screen
before suspend/sleep. You can check that in the session settings, last
(Advanced) tab. Can you report back?

Also, if you want your power manager icon back, you should add the power
manager plugin to your panel. In case it's not installed (it should be
by default since it's a Recommends), you can install it with
xfce4-power-manager-plugins. This advice is in a NEWS.Debian entry, but
it might be a good idea to have it also in the release notes for people
not doing an upgrade but a reinstall.
> 
> I marked the severity "important" because of the security implications
> and lack of workaround.
> 
> This could be the same as 739871, but since I wasn't sure, I thought
> it
> best to file a new bug.

I have no idea, there's not much information in that bug actually.

Can you try the above and report back?

Regards,
-- 
Yves-Alexis


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

Bug#772131: systemd: Suspending by closing the lid opens Polkit dialogue after resume

[Ralf Jung]

Hi,

> postinst has:
> 
> if [ -n "$2" ]; then
> systemctl daemon-reexec || true
> systemctl try-restart systemd-logind.service || true
> systemctl try-restart systemd-networkd.service || true
> systemctl try-restart systemd-resolved.service || true
> systemctl try-restart systemd-timesyncd.service || true
> fi
> 
> 
> Can you run those commands step-by-step and check if a specific restart
> is able to trigger the issue?
> Might be, that some KDE program doesn't cope with the restart of
> systemd-logind and doesn't properly reconnect to the logind D-Bus service.

As you guessed: After the systemd-logind restart, suspend is broken.

It was my understanding that D-Bus operates on a per-call basis and
there is no such thing as a "connection" between a d-bus client and a
service it's accessing (there's of course a "connection" between each
peer and the bus daemon, but that's an implementation detail) - but that
may just as well be wrong.

Kind regards,
Ralf


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

Bug#771954: unblock: owncloud/7.0.4~rc1+dfsg-2

[Niels Thykier]

On 2014-12-07 20:11, David Prévot wrote:
> control: tags -1 - moreinfo
> control: retitle -1 unblock: owncloud/7.0.4~rc1+dfsg-2
> 
> Le 06/12/2014 05:44, Niels Thykier a écrit :
>> [...]
> 
> Thanks, it has been ACCEPTed. The only change wrt the debdiff initially
> proposed is a new changlog entry, and a tiny fix in the previous one:
> 
> [...]
> 
> 
> Regards
> 
> David
> 

Hi David,

Thanks for the uploads.

I will have a look at them as soon (within a few days).

~Niels


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

Bug#501566: [MAN] Clarify two redirection mechanisms

[Stephane CHAZELAS]

2014-12-08 19:50:05 +0100, Stéphane Aulery:
 [n1]>&n2Redirect standard output (or fd n1) to the same "open
 file description" as on fd n2.
 
 [n1]>&n2Copy fd n2 as stdout (or fd n1)
 
 [n1]>&n2Redirect standard output (or fd n1) to the same
 resource as currently open on fd n2.

> >> "Resource" is rather unwieldy, how about simply "file"?
> >
> > "file" could be misleading
> >
> > [...]
> >
> > IMO, "resource" is vague enough so as not to give the wrong idea
> > and I like that wording because it conveys the intended
> > mechanism clearly ("redirect to same thing as"). But I agree
> > it's not ideal.
> 
> It is true that "resource" is dissonant as "file" is too restrictive. The
> term "file descriptor" is used above. Why not use it again?
[...]

If you say redirect fd n1 to fd n2, you confuse people (and I've
seen a lot of people being confused in such a way) as they
start thinking the fds become somehow linked (for instance that
in 2>&1 > file, stderr goes to stdout and then both to "file"
which is not the case). When you start thinking of "&" as
"/address/ of" (yet another improper wording) or "resource
currently open on", that clears that confusion.

If you don't like the "resource" wording, you can always got for
the "copy" one above or the POSIX wording:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_07_05

I've seen "resource" used in the past, I've used it myself a few
times in usenet articles:

https://groups.google.com/d/msg/comp.unix.shell/48beJpLdjNE/jUak98HUekUJ
https://groups.google.com/d/msg/comp.unix.questions/EQL477tzYKk/J9ysMfqc5YIJ
https://groups.google.com/d/msg/comp.unix.aix/WcWsocnEHS0/hgSDWt19SaYJ

(see the aforementioned confusion in some of the messages that
those were replying to).

-- 
Stephane


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

Bug#772531: Same problem with Fedora 21

[Yvan Masson]

Hi,

I just tried to use the same web calendar with Fedora 21, wich currently
provides version 3.12.8-1.fc21 of Evolution (wich is older than the one
from Debian), and the result is exactly the same.

I imagine it means that the bug does not come from Debian but from
upstream. Should I report the bug upstream directly (I couldn't a
similar bug report on
https://bugzilla.gnome.org/buglist.cgi?product=Evolution&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=CLOSED&component=Calendar
 ) ?

Thanks,
Yvan


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

Bug#772487: SSL 3.0 and older ciphers selected in applications

[Daniel Pocock]

On 08/12/14 21:16, Kurt Roeckx wrote:
> On Mon, Dec 08, 2014 at 08:17:53PM +0100, Daniel Pocock wrote:
>>
>> If I understand your reply correctly, the version in Ubuntu and Fedora
>> will still talk TLS 1.0 with the version now waiting in jessie?
> 
> Yes.
> 
>> Do you believe it would be reasonable for me to request a smaller
>> unblock that just changes the call TLSv1_method to SSLv23_method?
> 
> That depends on wether it's acting as client or server.  If it's
> acting as server I say yes.  If it's acting as client I suggest
> you also have a way to turn off TLS 1.2.  I understand that it
> needs to be able to talk to many different things and TLS 1.2 has
> has been breaking things it shouldn't and you already indicated
> problems with some products.  But maybe it just needs to be used
> for a while with the SSLv23 method to see if there are problems or
> not.
> 

It plays a few roles:

a) repro acts as a WebSocket server (for WebRTC)

b) in federated SIP, repro acts as both server and client

c) in a phone system, repro acts as server (e.g. my home phone system
has some Polycom desk phones, Jitsi with JDK1.7 and Lumicall on Android
as clients)

d) people use the reSIProcate library in all kinds of products where it
is client (e.g. in Counterpath softphones) or server (e.g. in some
commercial Session Border Controllers).

All of these use cases are supported by the Debian packages.

For the SIP proxy, repro, the smallest possible change to use SSLv23 as
default would involve touching 6 lines of code in repro/ReproRunner.cxx,
replacing SecurityTypes::TLSv1 with
SecurityTypes::SSLv23 on each.  As well as changing the server behavior,
this also has the effect of enabling TLS 1.2 when acting as client in a
federated SIP connection.

For other uses of the library it is up to the developer to select SSLv23
when they call SipStack::addTransport


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

Bug#772588: RFP: x-13arima-seats -- Seasonal adjustment software for modelling time series

[Rytis Bagdziunas]

Package: wnpp
Severity: wishlist

* Package name: x-13arima-seats
  Version : 1.1-9
  Upstream Author : U.S. Government 
* URL : http://www.census.gov/srd/www/x13as
* License : Public Domain
  Programming Lang: Fortran 77
  Description : Seasonal adjustment software for modelling time series

X-13ARIMA-SEATS is a seasonal adjustment software produced, distributed,
and maintained by the U.S. Census Bureau.

Features include:

* Extensive time series modeling and model selection capabilities for linear
  regression models with ARIMA errors (regARIMA models)

* The capability to generate ARIMA model-based seasonal adjustment
using a version of the SEATS procedure originally developed by
Victor Gómez and Agustín Maravall at the Bank of Spain as well
as nonparametric adjustments from the X-11 procedure

* Diagnostics of the quality and stability of the adjustments achieved under
  the options selected

* The ability to efficiently process many series at once.

--
Further information

This kind of seasonal adjustment software is used by a number of
statistical agencies throughout the world to provide public with
seasonally adjusted data. It could be of interest to researchers working
in domains of economics or statistics and thus could be part of Debian 
Science.

Console-based version of this software has no further dependencies.
There is also a package for R providing interface to X13 from within R.

If nobody's willing, I would be interested to try packaging it for
Debian and would need a sponsor.


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

Bug#772487: SSL 3.0 and older ciphers selected in applications

[Kurt Roeckx]

On Mon, Dec 08, 2014 at 08:17:53PM +0100, Daniel Pocock wrote:
> 
> If I understand your reply correctly, the version in Ubuntu and Fedora
> will still talk TLS 1.0 with the version now waiting in jessie?

Yes.

> Do you believe it would be reasonable for me to request a smaller
> unblock that just changes the call TLSv1_method to SSLv23_method?

That depends on wether it's acting as client or server.  If it's
acting as server I say yes.  If it's acting as client I suggest
you also have a way to turn off TLS 1.2.  I understand that it
needs to be able to talk to many different things and TLS 1.2 has
has been breaking things it shouldn't and you already indicated
problems with some products.  But maybe it just needs to be used
for a while with the SSLv23 method to see if there are problems or
not.


Kurt


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

Bug#772587: mtr -4 does nothing

[shirish शिरीष]

Package: mtr
Version: 0.85-3
Severity: normal

Dear Maintainer,
I tried using mtr and came up empty. It says and I quote "Unable to
allocate IPv6 socket for nameserver communication: Address family not
supported by protocol"

I looked at the binary and it seems to be in /usr/bin as can be seen here :-

$ dpkg -L mtr | head
/.
/usr
/usr/bin
/usr/bin/mtr

Looking forward for a fix.

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

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

Versions of packages mtr depends on:
ii  libatk1.0-0 2.14.0-1
ii  libc6   2.19-13
ii  libcairo2   1.14.0-2.1
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.5.2-2
ii  libgdk-pixbuf2.0-0  2.31.1-2+b1
ii  libglib2.0-02.42.1-1
ii  libgtk2.0-0 2.24.25-1
ii  libncurses5 5.9+20140913-1
ii  libpango1.0-0   1.36.8-2
ii  libtinfo5   5.9+20140913-1

mtr recommends no packages.

mtr suggests no packages.

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8


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

Bug#747653: grub2-common: update-grub adds both devices and a line feed for BTRFS RAID 1 setup

[Andrei Borzenkov]

В Sat, 06 Dec 2014 12:01:11 +0100
Martin Steigerwald  пишет:

> Am Montag, 2. Juni 2014, 19:39:22 schrieb Andrey Borzenkov:
> > В Sat, 10 May 2014 20:53:34 +0200
> > 
> > Martin Steigerwald  пишет:
> > > Package: grub2-common
> > > Version: 2.02~beta2-10
> > > Severity: normal
> > > 
> > > Dear Maintainer,
> > > 
> > > I am booting my Debian system via a BTRFS RAID 1 which spans a logical
> > > volume on a Crucial MSATA and Intel SATA SSD each.
> > > 
> > > After running update-grub I am getting this in /boot/grub/grub.cfg:
> > > echo'Linux 3.15.0-rc5-tp520 wird geladen …'
> > > linux   /vmlinuz-3.15.0-rc5-tp520
> > > root=/dev/mapper/sata-debian
> > > 
> > > /dev/mapper/msata-debian ro rootflags=subvol=debian 
> > > init=/bin/systemd resume=/dev/mapper/sata-swap> 
> > > echo'Initiale Ramdisk wird geladen …'
> > > initrd  /initrd.img-3.15.0-rc5-tp520
> > > 
> > > update-grub basically adds both devices of the BTRFS RAID 1 device
> > > separated by a line feed. For mounting BTRFS RAID 1 tough one of them
> > > is enough, once btrfs device scan is run, for which I currently use an
> > > script for initramfs-tools as a work-around as it didn´t work out of
> > > the box on my last tests[1].
> > > 
> > > This behaviour is due to grub-probe which is called by grub-mkconfig
> > > at line 139
> > > 
> > > 138 # Device containing our userland.  Typically used for root= parameter.
> > > 139 GRUB_DEVICE="`${grub_probe} --target=device /`"
> > > 140 GRUB_DEVICE_UUID="`${grub_probe} --device ${GRUB_DEVICE}
> > > --target=fs_uuid 2> /dev/null`" || true
> > > 
> > > which is called by update-grub returns both devices with a
> > > linefeed:
> > > 
> > > merkaba:~> grub-probe --target=device /
> > > /dev/mapper/sata-debian
> > > /dev/mapper/msata-debian
> > > 
> > > grub-probe is an ELF binary.
> > > 
> > > The following little change workarounds the issue for me:
> > > 
> > > merkaba:~> diff -u /usr/sbin/grub-mkconfig.dist /usr/sbin/grub-mkconfig
> > > --- /usr/sbin/grub-mkconfig.dist2014-05-08 14:35:25.0
> > > +0200
> > > +++ /usr/sbin/grub-mkconfig 2014-05-10 20:46:00.380096263 +0200
> > > @@ -136,7 +136,7 @@
> > > 
> > >  fi
> > >  
> > >  # Device containing our userland.  Typically used for root= parameter.
> > > 
> > > -GRUB_DEVICE="`${grub_probe} --target=device /`"
> > > +GRUB_DEVICE="`${grub_probe} --target=device / | head -1`"
> > > 
> > >  GRUB_DEVICE_UUID="`${grub_probe} --device ${GRUB_DEVICE} --target=fs_uuid
> > >  2> /dev/null`" || true
> > >  
> > >  # Device containing our /boot partition.  Usually the same as
> > >  GRUB_DEVICE.
> > > 
> > > But I suppose the real fix is to be made in the binary grub-probe.
> > 
> > No, grub-probe is correct; grub needs to know all devices so it can
> > have full information which drivers it requires to access them.
> > 
> > See also
> > https://lists.gnu.org/archive/html/grub-devel/2014-05/msg5.html
> > 
> > I suggest you discuss it with Colin, but for now I tend to think, fix
> > should go into 10_linux. May be always use UUID for btrfs.
> > 
> > But this sounds like new can of worms :(
> 
> Any way on how to proceed on this one?
> 

Try patch below

From: Andrei Borzenkov 
Subject: [PATCH] fix linux kernel root= argument with multidev btrfs

Btrfs may reside on multiple devices, but only one of them should be
passed to root= kernel argument. Add two helper functions:

- get_root_device: select "best" device for the list. For single device
just return it to skip probing; for multiple devices try to find LVM as
before but fall back to the first device if not found.

- find_abstraction: return device with requested abstraction driver from
the given list.

Refactor code to use them and reimplement uses_abstraction on top of
find_abstraction.

Also replace check for LVM with uses_abstraction in 10_kfreebsd.

---
 util/grub-mkconfig_lib.in   | 50 ++---
 util/grub.d/10_kfreebsd.in  |  8 +++-
 util/grub.d/10_linux.in | 10 +
 util/grub.d/20_linux_xen.in | 10 +
 4 files changed, 53 insertions(+), 25 deletions(-)

diff --git a/util/grub-mkconfig_lib.in b/util/grub-mkconfig_lib.in
index 29ef865..ecae264 100644
--- a/util/grub-mkconfig_lib.in
+++ b/util/grub-mkconfig_lib.in
@@ -283,21 +283,27 @@ gettext_printf () {
   printf "$(gettext "$gettext_printf_format")" "$@"
 }
 
-uses_abstraction () {
-  device="$1"
-  old_ifs="$IFS"
+find_abstraction () {
+  abstraction="$1"
+  devices="$2"
+  old_IFS="$IFS"
   IFS='
 '
-
-  abstraction="`"${grub_probe}" --device ${device} --target=abstraction`"
-  for module in ${abstraction}; do
-if test "x${module}" = "x$2"; then
-  IFS="$old_ifs"
-  return 0
-fi
+  set $devices
+  IFS="$old_IFS"
+
+  for device in "$@"; do
+for module in `"${grub_probe}" --device "${device}" --target=abstraction`; 
do
+  if test "x${modu

Bug#772172: unblock: debichem/0.0.4

[Michael Banck]

tags 772172 -moreinfo
retitle 772172 "unblock: debichem/0.0.5"
thanks

On Sat, Dec 06, 2014 at 06:06:17PM +0100, Ivo De Decker wrote:
> On Fri, Dec 05, 2014 at 08:26:43PM +0100, Michael Banck wrote:
> > Please unblock package debichem
> 
> This part is not appropriate:
> 
> > diff -Nru debichem-0.0.3/debian/source/format 
> > debichem-0.0.4/debian/source/format
> > --- debichem-0.0.3/debian/source/format 1970-01-01 01:00:00.0 
> > +0100
> > +++ debichem-0.0.4/debian/source/format 2014-12-05 16:06:21.0 
> > +0100
> > @@ -0,0 +1 @@
> > +3.0 (native)

OK, fixed 0.0.5, which I just uploaded.
 
> Once it gets through new, please upload a new version without this change and
> remove the moreinfo tag.

That has happened now and I did so.

Thanks a lot!


Michael


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

Bug#772578: Missing keyboard modules i2c_designware_*

[Ben Hutchings]

Control: clone -1 -2
Control: reassign -2 src:linux 3.16.7-2
Control: retitle -2 [armhf] Missing keyboard modules i2c_designware_* in 
installer

On Mon, 2014-12-08 at 19:26 +0100, Hendrik Weimer wrote:
> Package: initramfs-tools
> Version: 0.116
> 
> I just got an ASUS X205TA notebook, which requires the
> i2c_designware_core and i2c_designware_platform modules to be loaded for
> the keyboard to work. The module gets correctly loaded when booting up,
> but it's not present in the initramfs. As a result, I had to attach an
> USB keyboard when being asked for the passphrase to unlock my root
> partition. Adding the two modules to /etc/initramfs-tools/modules solves
> the problem.
> 
> This also affects the jessie netinst image, requiring a spare USB
> keyboard during installation, shall I file a separate bug for this?

No need; I'm duplicating this bug report for you.

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.


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

Bug#772584: xfce4-power-manager: display unlocked after resume

[Mike Kupfer]

Package: xfce4-power-manager
Version: 1.4.1-1
Severity: important

Dear Maintainer,

   * What led up to the situation?

I installed Jessie, using a dual-boot configuration (Jessie, Wheezy
(7.7)) with a shared /home.  I then tried testing suspend/resume and
hibernate/resume.  The checkbox (in the power manager preferences) to
lock the screen is selected.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I suspended the system from the logout dialog, waited a few seconds,
then pressed a keyboard key to resume.

I hibernated the system from the logout dialog, waited a few seconds,
then pressed the power button to reboot/resume.

   * What was the outcome of this action?

My desktop reappeared.

   * What outcome did you expect instead?

I expected the display to be locked.

I have verified that the screen lock does work if I invoke it manually.

With Wheezy I don't normally use the logout dialog to
suspend/hibernate.  Instead, I invoke suspend/hibernate from the power
manager icon in the systray; when resuming, I get a locked screen.
If I use the logout dialog to suspend/hibernate, I do not get a locked
screen.

But in Jessie there does not appear to be a power manager icon, so the
logout dialog appears to be the only way to suspend/hibernate. 

I marked the severity "important" because of the security implications
and lack of workaround.

This could be the same as 739871, but since I wasn't sure, I thought it
best to file a new bug.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/3 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 xfce4-power-manager depends on:
ii  libc6 2.19-13
ii  libdbus-1-3   1.8.12-1
ii  libdbus-glib-1-2  0.102-1
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libglib2.0-0  2.42.1-1
ii  libgtk2.0-0   2.24.25-1
ii  libnotify40.7.6-2
ii  libupower-glib3   0.99.1-3.1
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxfce4ui-1-04.10.0-6
ii  libxfce4util6 4.10.1-2
ii  libxfconf-0-2 4.10.0-3
ii  libxrandr22:1.4.2-1+b1
ii  upower0.99.1-3.1
ii  xfce4-power-manager-data  1.4.1-1

Versions of packages xfce4-power-manager recommends:
ii  libpam-systemd   215-7
ii  xfce4-power-manager-plugins  1.4.1-1

xfce4-power-manager 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#772528: update

[Daniel Pocock]

severity 772528 important
stop

After discussion on debian-security, it appears that SSLv3 is no longer
possible[1] with SSLv23_method so I'm reducing the severity.

1. https://lists.debian.org/debian-security/2014/12/msg00021.html


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

Bug#767037: Grub EFI fallback - patches for review

[Ian Campbell]

On Mon, 2014-12-08 at 01:36 +, Steve McIntyre wrote:
> >The current package in sid (-17) is unblocked and I think ought to
> >transition tomorrow (or perhaps Tuesday depending on TZ). I propose to
> >upload -18 with this change shortly after that happens. Will you take
> >care of the unblock request or at least provide me some text with the
> >rationale etc.
> 
> I'll ask for the unblock, and I'll also upload grub-installer the same
> day.

Upload == done.

> >-17 included some patches from Colin to make the 32-bit linuxefi command
> >work.
> 
> Yup, saw that. I'm looking into 32-bit EFI stuff right now. Using a
> Mac atm *shudder*

Urk!

Ian.


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

Bug#772583: python-oslotest-doc: extra space in package description

[Davide Prina]

Package: python-oslotest-doc
Severity: minor

Dear Maintainer,

in DDTSS I see:
.
 This package contains the documentation.

Note the extra space before "This".

Ciao
Davide


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

Bug#771414: BBBike: 771414 is a duplicate of 210245

[W. Martin Borgert]

I entered this one around 11 years ago:
https://bugs.debian.org/210245
Let's merge the bug reports, OK?
Cool that you are going to package it, because
BBBike changed Berlin more than any airport would.


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