Bug#710129: [Pkg-bluetooth-maintainers] Bug#732453: bluez: New upstream release 5.12

[Fabian Greffrath]

Am Mittwoch, den 08.01.2014, 21:47 +0100 schrieb Szymon Janc: 
> FYI http://www.afiestas.org/bluedevil-2-0-rc1-a-k-a-bluez5-ready/

Go for it! \o/

- Fabian


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

Bug#731283: [Openstack-devel] Bug#731283: python-pastedeploy has support for python3 now

[Thomas Goirand]

On 01/09/2014 02:07 PM, Thomas Goirand wrote:
> On 01/09/2014 12:18 AM, Barry Warsaw wrote:
>> On Dec 26, 2013, at 07:26 PM, Thomas Goirand wrote:
>>
>>> As soon as there's python3 support for webtest and there's
>>> singledispatch, I'll work on pecan again, to add support for python3 and
>>> this new upstream version.
>>
>> Python 3 support for both webtest and singledispatch are available:
>>
>> % rmadison python3-webtest
>>  python3-webtest | 2.0.10-2 | jessie | all
>>  python3-webtest | 2.0.10-2 | sid| all
>> % rmadison python3-singledispatch
>>  python3-singledispatch | 3.4.0.2-1 | jessie | all
>>  python3-singledispatch | 3.4.0.2-1 | sid| all
>>
>> Do you need anything else for Python 3 pecan?
>>
>> Cheers,
>> -Barry
> 
> Unfortunately, it seems pecan also needs logutils. I'm working on
> packaging it. Seeing how fast the NEW queue goes, it should be no
> problem to have the new version of pecan soon.
> 
> Cheers,
> 
> Thomas

FYI, python-logutils is now waiting for FTP masters approval in the NEW
queue. :)

Thomas


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

Bug#734689: XScreensaver dies regularly (glslideshow)

[Jamie Zawinski]

Weird. Running with -log may be helpful...


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

Bug#734692: adequate: minor spelling mistake in manpage in one of the examples given

[shirish शिरीष]

Package: adequate
Version: 0.10
Severity: minor

Dear Maintainer,
I was looking at the examples and one of the examples it shares is :-

adequate --tags obsolete-conffiles --all
   Check all the packages for obsolete conffiles.

If a new user were to use it just as it is, it would not work

$ adequate --tags obsolete-conffiles --all
adequate: error: unknown tag obsolete-conffiles

The actual command in the example should be :-

$ adequate --tags obsolete-conffile --all

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

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages adequate depends on:
ii  debconf  1.5.52
ii  perl 5.18.1-5

adequate recommends no packages.

adequate suggests no packages.

-- Configuration Files:
/etc/apt/apt.conf.d/20adequate changed [not included]

-- 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
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17


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

Bug#734164: console-data: should conflict with console-setup

[Christian PERRIER]

Quoting Anton Zinoviev (an...@lml.bas.bg):

> I agree.  I am not against removing c-d.  What I don't like is to abuse 
> 'Breaks' and 'Provides' inapropriately.  We must not force our way to 
> the users, they have the right to install c-d even if the package is 
> removed from the archive.  The number of the affected users may be close 
> to zero but it is definitely not zero.
> 
> BTW, on my computers I am using packages from old Debian releases that 
> are no longer available.

I'm sorry but I fail to agree here. The plan is to deprecate c-d
because it's not maintained anymore. As Debian developers, our duty is
to prevent our users from silently be left unsupported, which is what
will happen if, as c-d maintainer, I simply ask it from being removed
from the archive.

Given that it happened that c-d has been quite widely spread out, we
should do our best to avoid that situation and one of the ways to
achieve this is by having the package that is really supported to help
in this removal.

Breaks and Provides are the right way to handle a transition. And that
is a transition.

Anyway, I more and more feel quite away from what Debian is becoming
in some way, so I may finally just ask for c-d to be removed, without
caring much more than that (except checking reverse dependencies).

The alternative (particularly if we find too many reverse
dependencies) being just removing myself from Maintainers, orphaning
the package and just say "bye bye"...:-). Which, in some way, is doing
exactly what we should not be doing : leave our users in the wild.




signature.asc
Description: Digital signature

Bug#733495: [INTL:es] Spanish translation of debconf messages

[Michael Vogt]

On Sun, Dec 29, 2013 at 01:06:16PM +0100, Camaleón wrote:
> Package: squid-deb-proxy
> Severity: wishlist
> Tags: l10n patch

Thanks for your translation! I merged it into my bzr tree and it will
be part of the next upload.

Cheers,
 Michael


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

Bug#667582: [Pkg-systemd-maintainers] Bug#667582: Status of this bug?

[Michael Stapelberg]

Hi Josh,

Josh Triplett  writes:
> This bug has had a working patch available (and committed to a branch in
> the Debian packaging repository) for more than a year.  Is there
> anything preventing that patch from being merged?
I’ll take a stab at merging it once the tech-ctte decision has been
made.

-- 
Best regards,
Michael


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

Bug#729961: qemu-system-x86: rbd support

[Christian Balzer]

Hello,

Meanwhile, we're at qemu 1.7, ceph is at 0.72, both in sid and
wheezy-backports. 

I'd really, really would love to see RBD re-enabled by default for these
and when things have trickled into jessie. 

Regards,

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


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

Bug#734279: jblas: FTBFS on most architectures since tests are enabled at build time

[tony mancill]

On 01/08/2014 12:45 AM, Roland Stigge wrote:
> Hi!
> 
> On 01/08/2014 07:24 AM, tony mancill wrote:
>> I still wonder whether this package has ever been useful on 
>> non-i386/amd64 architectures.
> 
> Why should it be less useful than on other architectures? We shouldn't
> differenciate between architectures in this regard, IMO.

Sorry, imprecise wording on my part.  What I meant was, I wonder if the
package has ever been *usable* on architectures other than i386/amd64.
It compiled, to be sure, but even the simplest upstream unit-test isn't
able to execute on non-i386/amd64.

>> For the short-term, so the ruby transition can move forward, we
>> could temporarily either disable to tests or constrain the
>> architectures.  Between those 2, I prefer the latter.  Thoughts?
> 
> I'm fine with whatever you decide as maintainer.

Well, the package is team-maintained and I'm not a jblas user, just
trying to help with the bugs filed against the Java team...

The upload constraining the architectures would only need to be until
someone can demonstrate that it's working on other architectures.

The tests are working with the latest upstream release, version 1.2.3,
on s390x, so that might be the best path forward.

Cheers,
tony



signature.asc
Description: OpenPGP digital signature

Bug#734691: pcmanfm: Displays icons only when gnome-icon-theme is installed

[Paul Nijjar]

Package: pcmanfm
Version: 1.1.2-1
Severity: normal


If you install a minimal xorg system (aterm, icewm, xorg, pcmanfm) and 
lxde-icon-theme, oxygen-icon-theme, or tango-icon-theme without 
gnome-icon-theme then no icons are displayed when you launch the file manager. 
If you install gnome-icon-theme then icons are displayed.

I tried this with pcmanfm in both stable and testing. You can easily reproduce 
the problem by uninstalling gnome-icon-theme and then installing 
lxde-icon-theme. 

I do not know what causes this, but I wonder if it is because the icons for the 
lxde theme are stored in /usr/share/icons/nuoveXT2 . If I symlink this folder 
to /usr/share/icons/gnome then the icons show up (and appear to use the LXDE 
themeset). 

- Paul



-- System Information:
Debian Release: 7.3
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500, 
'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages pcmanfm depends on:
ii  libatk1.0-0  2.10.0-2
ii  libc62.17-97
ii  libcairo21.12.16-2
ii  libfm-gtk3   1.1.2.2-1
ii  libfm3   1.1.2.2-1
ii  libfontconfig1   2.11.0-2
ii  libfreetype6 2.4.9-1.1
ii  libgdk-pixbuf2.0-0   2.28.2-1+b1
ii  libglib2.0-0 2.36.4-1
ii  libgtk2.0-0  2.24.22-1
ii  libpango-1.0-0   1.36.0-1+b1
ii  libpangocairo-1.0-0  1.36.0-1+b1
ii  libpangoft2-1.0-01.36.0-1+b1
ii  libx11-6 2:1.6.2-1

Versions of packages pcmanfm recommends:
pn  gvfs-backends
ii  gvfs-fuse1.16.3-1+b2
ii  lxde-icon-theme  0.5.0-1

pcmanfm 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#734526: [Pkg-xfce-devel] Bug#734526: Bug#734526: Bug#734526: lightdm-gtk-greeter: leaking memory

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Thu, Jan 09, 2014 at 06:23:46AM +, Alistair Buxton wrote:
> Hi,
> 
> Please install debug symbols for glib and gdk and then rerun valgrind with:
> --leak-check=full --show-leak-kinds=all

In order to do that on Debian, you'll need libglib2.0-0-dbg and
libgtk-3-0-dbg.

Regards,
- -- 
Yves-Alexis Perez
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBCgAGBQJSzkXMAAoJEG3bU/KmdcClFDMIAK3HClQV0Xbaz0G5baQqi0Fj
s/BiUMHh0EQt2K3ocAmYPMbirZBKtTtSDc12YPxv97SIjoRZlTn85NXaH956qlWu
JVrt60NGzEcrxHKnuyuKfEayq1sRvxvP/lQtisk9m7Dr4tdqhBOxm5+iSc3V4nFz
F0DHP54Ork4hxbDMMCJv6bM00eRTVk9LvOdM/OMgEp/0TCl8Blw+gvAQjjppCswg
J9XdP8c7oiWqG6T2CepnF/GdDZFptI1rsQrsjyAmA9cJHayESyUXvEx3WWnbzhyy
dlW8LKtN4b3msofbUfc34X3Q0os8F0Sjqn1C1FmaYymnqxW+shxvhiMbVqHhAk4=
=CGyl
-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#734690: Language-chooser: C is not a language

[martin f krafft]

Package: debian-installer
Severity: normal

It was just pointed out in a LCA2014 presentation that it's a bit
silly to ask the user to choose the language between "C" and
"English". Maybe this could be moved to a lower priority or
rephrased?

Sorry I did not verify this or check. The network here is slow and
I just wanted to make sure that this isn't forgotten.

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

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
 .''`.   martin f. krafft   Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#734689: XScreensaver dies regularly (glslideshow)

[martin f krafft]

Package: xscreensaver
Version: 5.23-1
Severity: important

I have xscreensaver set up to run glslideshow on my laptop, locking
itself when the laptop screen is closed, on timeout, or on suspend.

Every now and then, I come back to the laptop to find it unlocked.

So far I have been unable to trace this down. Running xscreensaver
in strace causes my password not be accepted during unlock.

Also, this happens at random times, which makes it hard to
investigate.

I could certainly try to change the actual screensaver from
glslideshow, but not being able to reproduce the problem at will
doesn't really help.

Maybe you have some ideas?

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

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xscreensaver depends on:
ii  libatk1.0-0  2.10.0-2
ii  libc62.17-97
ii  libcairo21.12.16-2
ii  libfontconfig1   2.11.0-2
ii  libfreetype6 2.5.2-1
ii  libgdk-pixbuf2.0-0   2.28.2-1+b1
ii  libglade2-0  1:2.6.4-2
ii  libglib2.0-0 2.37.6-1
ii  libgtk2.0-0  2.24.22-1
ii  libice6  2:1.0.8-2
ii  libpam0g 1.1.3-10
ii  libpango-1.0-0   1.36.0-1+b1
ii  libpangocairo-1.0-0  1.36.0-1+b1
ii  libpangoft2-1.0-01.36.0-1+b1
ii  libsm6   2:1.2.1-2
ii  libx11-6 2:1.6.2-1
ii  libxext6 2:1.3.2-1
ii  libxi6   2:1.7.2-1
ii  libxinerama1 2:1.1.3-1
ii  libxml2  2.9.1+dfsg1-3
ii  libxmu6  2:1.1.1-1
ii  libxpm4  1:3.5.10-1
ii  libxrandr2   2:1.4.1-1
ii  libxrender1  1:0.9.8-1
ii  libxt6   1:1.1.4-1
ii  libxxf86vm1  1:1.1.3-1
ii  xscreensaver-data5.23-1

Versions of packages xscreensaver recommends:
ii  libjpeg-progs   8d-2
ii  perl [perl5]5.18.1-5
ii  wbritish [wordlist] 7.1-1
ii  wbritish-insane [wordlist]  7.1-1

Versions of packages xscreensaver suggests:
ii  chromium [www-browser]   31.0.1650.63-1
ii  fortune-mod [fortune]1:1.99.1-7
pn  gdm3 | kdm-gdmcompat 
ii  iceweasel [www-browser]  26.0-1
ii  lynx-cur [www-browser]   2.8.8pre2-1
pn  qcam | streamer  
ii  uzbl [www-browser]   0.0.0~git.20120514-1.1
ii  w3m [www-browser]0.5.3-15
pn  xdaliclock   
pn  xfishtank
ii  xscreensaver-gl  5.23-1

-- no debconf information


-- 
 .''`.   martin f. krafft   Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#734688: Logs are not rotated for a month

[martin f krafft]

Package: logrotate
Version: 3.8.6-1
Severity: important

I just happened to notice that /var/log/syslog had not been rotated
in almost 1 month:

  % ls -l /var/log/syslog*
  -rw-r- 1 root adm 16588618 Jan  9 14:21 /var/log/syslog
  -rw-r- 1 root adm   336215 Dec 11 15:37 /var/log/syslog.1

Indeed, when I run logrotate, nothing happens:

  % sudo logrotate -d /etc/logrotate.d/rsyslog 2>&1 | grep -A2 syslog
  reading config file /etc/logrotate.d/rsyslog

  Handling 2 logs
  --
  rotating pattern: /var/log/syslog
  after 1 days (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log does not need rotating

Here is the status file, indicating that something's wrong:

  % grep syslog /var/lib/logrotate/status
  "/var/log/syslog" 2014-1-9-10:41:57

And indeed, logrotate *thinks* it's rotating, but it actually does not:

  % sudo logrotate --force -d /etc/logrotate.d/rsyslog
  reading config file /etc/logrotate.d/rsyslog

  Handling 2 logs

  rotating pattern: /var/log/syslog
  forced from command line (7 rotations)
  empty log files are not rotated, old logs are removed
  considering log /var/log/syslog
log needs rotating
  rotating log /var/log/syslog, log->rotateCount is 7
  dateext suffix '-20140109'
  glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]'
  compressing log with: /bin/gzip
  renaming /var/log/syslog.7.gz to /var/log/syslog.8.gz (rotatecount 7, 
logstart 1, i 7), 
  renaming /var/log/syslog.6.gz to /var/log/syslog.7.gz (rotatecount 7, 
logstart 1, i 6), 
  renaming /var/log/syslog.5.gz to /var/log/syslog.6.gz (rotatecount 7, 
logstart 1, i 5), 
  renaming /var/log/syslog.4.gz to /var/log/syslog.5.gz (rotatecount 7, 
logstart 1, i 4), 
  renaming /var/log/syslog.3.gz to /var/log/syslog.4.gz (rotatecount 7, 
logstart 1, i 3), 
  renaming /var/log/syslog.2.gz to /var/log/syslog.3.gz (rotatecount 7, 
logstart 1, i 2), 
  renaming /var/log/syslog.1.gz to /var/log/syslog.2.gz (rotatecount 7, 
logstart 1, i 1), 
  renaming /var/log/syslog.0.gz to /var/log/syslog.1.gz (rotatecount 7, 
logstart 1, i 0), 
  renaming /var/log/syslog to /var/log/syslog.1
  running postrotate script
  running script with arg /var/log/syslog: "
  invoke-rc.d rsyslog rotate > /dev/null
  "
  removing old log /var/log/syslog.8.gz
  error: error opening /var/log/syslog.8.gz: No such file or directory

Nothing has actually changed.

-- Package-specific info:
Contents of /etc/logrotate.d
total 100
-rw-r--r-- 1 root root 434 Jun  8  2013 apache2
-rw-r--r-- 1 root root 173 Aug 25  2010 apt
-rw-r--r-- 1 root root  79 Mar 13  2010 aptitude
-rw-r--r-- 1 root root  69 Jun 18  2011 backupninja
-rw-r--r-- 1 root root 279 Jun 15  2012 bmc-watchdog
-rw-r--r-- 1 root root 135 May 20  2011 consolekit
-rw-r--r-- 1 root root 430 Jun  4  2013 cups-daemon
-rw-r--r-- 1 root root 112 Oct 12 23:04 cupt
-rw-r--r-- 1 root root 232 Jul 31  2010 dpkg
-rw-r--r-- 1 root root  94 Dec 20  2009 hibernate
-rw-r--r-- 1 root root 151 Sep 13  2009 iptraf
-rw-r--r-- 1 root root 135 Oct  5  2012 iptraf-ng
-rw-r--r-- 1 root root 165 Jul 24  2011 libvirtd
-rw-r--r-- 1 root root 162 Jul 24  2011 libvirtd.lxc
-rw-r--r-- 1 root root 163 Jul 24  2011 libvirtd.qemu
-rw-r--r-- 1 root root 162 Jul 24  2011 libvirtd.uml
-rw-r--r-- 1 root root 157 Mar 19  2010 pm-utils
-rw-r--r-- 1 root root 234 May 16  2013 polipo
-rw-r--r-- 1 root root 173 Dec  6  2011 postgresql-common
-rw-r--r-- 1 root root  94 Dec  1  2008 ppp
-rw-r--r-- 1 root root 515 May 31  2011 rsyslog
-rw-r--r-- 1 root root 117 Aug 18 02:48 salt-common
-rw-r--r-- 1 root root 298 Apr 20  2011 stunnel4
-rw-r--r-- 1 root root 190 Apr 13  2011 tor
-rw-r--r-- 1 root root 276 Mar 14  2010 xdm


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

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages logrotate depends on:
ii  anacron 2.3-20
ii  base-passwd 3.5.29
ii  cron [cron-daemon]  3.0pl1-124
ii  libacl1 2.2.52-1
ii  libc6   2.17-97
ii  libpopt01.16-8
ii  libselinux1 2.2.1-1

Versions of packages logrotate recommends:
ii  heirloom-mailx [mailx]  12.5-2

logrotate suggests no packages.

-- no debconf information


-- 
 .''`.   martin f. krafft   Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#734665: clusterssh: ctel does not use telnet, but ssh instead.

[tony mancill]

On 01/08/2014 04:30 PM, James Zuelow wrote:
> Package: clusterssh
> Version: 4.01.01-4
> Severity: important
> 
> Dear Maintainer,
> 
> Bug 697185 was resolved about a year ago.
> 
> However after point releases, clusterssh in stable is still broken.
> 
> Is this bug considered a "wontfix" for stable?
> 
> Thank you!
> 
> James

Hi James,

I can look into preparing an update for the next point release.

However, note that you can easily install newer versions of clusterssh
directly from the .deb in testing/unstable.  There is no recompilation
or back-porting needed.  Simply wget the .deb and use dpkg -i to install it.

Thank you,
tony



signature.asc
Description: OpenPGP digital signature

Bug#734687: ITP: python-logutils -- handlers for the Python standard library's logging package

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: python-logutils
  Version : 0.3.3
  Upstream Author : Vinay Sajip 
* URL : https://pypi.python.org/pypi/logutils
* License : BSD-3-clause
  Programming Lang: Python
  Description : handlers for the Python standard library's logging package

 The logutils package provides a set of handlers for the Python standard
 library's logging package.
 .
 Some of these handlers are out-of-scope for the standard library, and so they
 are packaged here. Others are updated versions which have appeared in recent
 Python releases, but are usable with older versions of Python and so are
 packaged here.


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

Bug#734526: [Pkg-xfce-devel] Bug#734526: Bug#734526: lightdm-gtk-greeter: leaking memory

[Alistair Buxton]

Hi,

Please install debug symbols for glib and gdk and then rerun valgrind with:
--leak-check=full --show-leak-kinds=all

Also please note lightdm-gtk-greeter is expected to leak exactly one
X11 pixmap which contains the user's wallpaper and sticks around after
the greeter exits.

-- 
Alistair Buxton
a.j.bux...@gmail.com


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

Bug#734678: Please depend on lua-sec and remove the silly warning

[martin f krafft]

also sprach Sergei Golovan  [2014-01-09 13:58 +0800]:
> prosody recommends lua-sec (through the virtual package
> lus5.1-sec, but it doesn't matter). Though I guess it's time to
> turn this soft dependency into a hard one. XMPP server without TLS
> may become useless in the future.

I am sorry I missed that. I think you should leave it as
a recommendation, but maybe update/patch the message displayed when
it's not installed.

-- 
 .''`.   martin f. krafft   Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
 
"it is easier to be a lover than a husband for the simple reason
 that it is more difficult to be witty every day
 than to say pretty things from time to time."
   -- honoré de balzac


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#734243: closure-compiler: Install a useful manpage for ‘closure-compiler’ command

[tony mancill]

On 01/06/2014 12:41 PM, Ben Finney wrote:
> package src:closure-compiler
> tags 734243 + patch
> thanks
> 
> On 05-Jan-2014, Ben Finney wrote:
>> I will work on a suitable manpage and submit it to the bug report for this.
> 
> Attached to this message are two patches for the ‘closure-compiler’ package:
> 
> * closure-compiler.r2214.add-manpage.patch
> 
>   Adds a manpage as a reStructuredText source document; I find this much
>   easier to edit than the troff format, and Debian has Docutils to render
>   reST to a manpage.
> 
>   Configures Debhelper to install the ‘closure-compiler(1)’ manpage for the
>   binary ‘closure-compiler’ package.
> 
> * closure-compiler.r2215.build-manpage.patch
> 
>   Adds the rules and auxiliary files to build the manpage in the “build”
>   target, and to clean the generated files in the “clean” target.

Hi Ben,

Thank you for providing the manpage and the patch.

I started on a new version that splits closure-compiler into a separate
binary package, but am running into some toolchain problems, I believe
with javahelper when trying to split the symlink from the jar.

I just wanted to explain the delay.
Thanks,
tony





signature.asc
Description: OpenPGP digital signature

Bug#731283: [Openstack-devel] Bug#731283: python-pastedeploy has support for python3 now

[Thomas Goirand]

On 01/09/2014 12:18 AM, Barry Warsaw wrote:
> On Dec 26, 2013, at 07:26 PM, Thomas Goirand wrote:
> 
>> As soon as there's python3 support for webtest and there's
>> singledispatch, I'll work on pecan again, to add support for python3 and
>> this new upstream version.
> 
> Python 3 support for both webtest and singledispatch are available:
> 
> % rmadison python3-webtest
>  python3-webtest | 2.0.10-2 | jessie | all
>  python3-webtest | 2.0.10-2 | sid| all
> % rmadison python3-singledispatch
>  python3-singledispatch | 3.4.0.2-1 | jessie | all
>  python3-singledispatch | 3.4.0.2-1 | sid| all
> 
> Do you need anything else for Python 3 pecan?
> 
> Cheers,
> -Barry

Unfortunately, it seems pecan also needs logutils. I'm working on
packaging it. Seeing how fast the NEW queue goes, it should be no
problem to have the new version of pecan soon.

Cheers,

Thomas


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

Bug#734678: Please depend on lua-sec and remove the silly warning

[Sergei Golovan]

Hi Martin,

On Thu, Jan 9, 2014 at 6:02 AM, martin f krafft  wrote:
>
> lua-sec is packaged, so please depend/recommend on it and remove
> this message/check.

prosody recommends lua-sec (through the virtual package lus5.1-sec,
but it doesn't matter). Though I guess it's time to turn this soft
dependency into a hard one. XMPP server without TLS may become useless
in the future.

Cheers!
-- 
Sergei Golovan


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

Bug#687564: RFS: irstlm/5.80.01-1 -- [ITP] IRST Language Modeling Toolkit

[Koichi Akabe]

Hi,

I fixed debian/ a little bit and pushed it to my personal git repository:
git://git.debian.org/users/vbkaisetsu-guest/irstlm.git
http://anonscm.debian.org/gitweb/?p=users/vbkaisetsu-guest/irstlm.git

Could you merge it if you have a time?
(Now I'm asking permission for collab-maint repository)



Iwamatsu-san,

I uploaded a package to:
http://mentors.debian.net/debian/pool/main/i/irstlm/irstlm_5.80.03-1.dsc

Could you check and upload it?

Thanks.

On Wed, 8 Jan 2014 12:03:02 +0100
Giulio Paci  wrote:

> Hi to all!
> 
> Il 08/gen/2014 09:19 "Nobuhiro Iwamatsu"  ha scritto:
> > I am a sponsor of Koichi.
> > If you need sponsor , I can sponsor this package.
> 
> We need a sponsor for this package and you are very welcome.
> Unfortunately I will have very few spare time until February.
> 
> However I think that Koichi can fix what is still needed (if anything). I
> checked what is still needed. The package is compiling with some warnings,
> but should be in a good shape. The git repository is the latest version and
> the package should be compliant with Debian policy 3.9.5. Yesterday I added
> me and Koichi as uploaders.
> 
> I never used it extensively, so I think it would be better to upload to
> experimental.
> 
> Bests,
> Giulio.
> 
> > Please feel free to contact me.
> >
> > Best regards,
> >   Nobuhiro


-- 
Koichi Akabe
 vbkaisetsu at {gmail.com, debian.or.jp}


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

Bug#734104: autoconf: uses old-style function definition, thus fails with -Werror=old-style-definition

[Ben Pfaff]

On Wed, Jan 08, 2014 at 09:44:20AM +0100, Vincent Lefevre wrote:
> On 2014-01-07 21:30:29 -0800, Ben Pfaff wrote:
> > On Fri, Jan 03, 2014 at 10:22:27PM +0100, Vincent Lefevre wrote:
> > > A developer may want to test his software with
> > > -Werror=old-style-definition (in particular because such definitions
> > > could be a real bug in the software). But configure fails because
> > > autoconf generates such a function definition. For instance:
> > 
> > In my opinion, it's a mistake to run "configure" tests with -Werror.
> 
> I don't see why.

As compilers evolve, they will inevitably come to issue new warnings,
some of which will be triggered by configure tests.  Authors of Autoconf
tests cannot possibly write them to avoid all warnings issued by future
versions of GCC.

> > I suggest adding such flags after configure tests have been run, as
> > with the --enable-Werror configure flag supported by Open vSwitch:
> > 
> > dnl OVS_ENABLE_WERROR
> > AC_DEFUN([OVS_ENABLE_WERROR],
> >   [AC_ARG_ENABLE(
> >  [Werror],
> >  [AC_HELP_STRING([--enable-Werror], [Add -Werror to CFLAGS])],
> >  [], [enable_Werror=no])
> >AC_CONFIG_COMMANDS_PRE(
> >  [if test "X$enable_Werror" = Xyes; then
> > CFLAGS="$CFLAGS -Werror"
> >   fi])])
> 
> This doesn't solve the problem at all: whether -Werror is used via
> --enable-Werror or via
> 
>   ./configure ... CFLAGS="... -Werror"
> 
> the same errors will occur.

No, configuration time errors will not occur with this macro, because
this macro adds -Werror only after all of the configuration tests have
already run.

> > I guess that -Werror=old-style-definition is somewhat more restricted,
> > but a similar solution can be used.
> 
> Actually I wasn't using -Werror=old-style-definition directly, but
> 
>   ./configure CFLAGS="-Wall -Wold-style-declaration -Wold-style-definition
> -Wmissing-parameter-type -Wmissing-prototypes -Wmissing-declarations
> -Wmissing-field-initializers -Werror"

If you did the same thing but dropped -Werror from CFLAGS and added
--enable-Werror, there would be no problem with configuration tests.

> IMHO, this is a good thing developers test that their software doesn't
> generate warnings, possibly with some exceptions; some errors can be
> avoided with -Wno-error=..., e.g. one needs -Wno-error=unused-function
> in the case of MPFR (and also gcc-snapshot). The -Werror allows one to
> do that in automatic tests without filtering the output.
> 
> Indeed if some new code generates a new warning, it may correspond to
> a bug.
> 
> In the particular case of -Werror=old-style-definition, this has
> corresponded to an obsolescent feature of C for more than 14 years,
> so that there are no reasons why programs would still use this old
> style definition.
> 
> My proposed patch concerning autoconf:
> 
>   http://lists.gnu.org/archive/html/autoconf-patches/2014-01/msg3.html

You reported this upstream?  I'm not sure why you're reporting it to
Debian also, then.


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

Bug#720143: [Pkg-tcltk-devel] Bug#720143: {tcl, tk}8.5: leaves alternatives after purge: /usr/bin/tclsh, /usr/bin/wish

[Sergei Golovan]

Hi!

On Wed, Jan 8, 2014 at 11:14 PM, Matthias Klose  wrote:
> the removal is done in tcltk-defaults from experimental.
>
> I assume this works good enough in practice, but fails when a versioned tcl8.x
> was installed without the tcl package installed. same for tk.

I think I could add the code wich will remove alternative for
/usr/bin/tclsh8.5 to tcl8.5 preinst in experimental as well.

Cheers!
-- 
Sergei Golovan


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

Bug#734559: libxc: use dh-autoreconf to fix FTBFS on ppc64el

[Logan Rosen]

Hi Daniel,

Thanks for the quick response. I agree that this is a contentious issue
without a true solution right now, which is why I am just proposing
dh-autoreconf/autotools-dev for affected packages at the moment. I am
personally not a fan of running dh-autoreconf by default, as it often
requires fixes such as disabling -Werror or fixing macro directories in
configure.ac. I am more of a fan of individual fixes where necessary. Also,
note that (from what I can tell) an autoreconf is not necessary when the
source package doesn't ship a binary specifically for a shared library,
even if it uses libtool, so it would create extra overhead when unnecessary.

Thanks again,
Logan


On Wed, Jan 8, 2014 at 5:28 AM, Daniel Leidert
wrote:

> Hello Logan,
>
> If this is a generic issue, IMO it should be fixed in a generic way as
> suggested here [1].
> Whereas there seem to be two possibilities: either run dh_autoreconf or
> patch libtool
> generated files.
>
> Touching all source packages with a libtool/autotools build system to
> introduce a new
> architecture sounds suboptimal to me (especially knowing, that updating
> the build system
> files can lead to FTBFS too - now or in the future). Can you please jump
> into the discussion
> at #733045 [1] too?
>
> JFTR: I could imagine this generic approach: enable/run dh_autoreconf by
> default and allow
> package maintainers to specificly disable it using the --without switch of
> dh.
>
> [1] *http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733045
> *
>
> Regards, Daniel
>
>  *Gesendet:* Mittwoch, 08. Januar 2014 um 07:51 Uhr
> *Von:* "Logan Rosen" 
> *An:* "Debian Bug Tracking System" 
> *Betreff:* [Debichem-devel] Bug#734559: libxc: use dh-autoreconf to fix
> FTBFS on ppc64el
> Package: libxc
> Version: 2.0.2-1
> Severity: normal
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu trusty ubuntu-patch
>
> Dear Maintainer,
>
> For the ppc64el architecture in Ubuntu, since this package uses libtool, a
> full
> autoreconf is necessary. This is because we need new libtool macros for
> ppc64el.
>
> In Ubuntu, the attached patch was applied to achieve the following:
>
> * Use dh-autoreconf to fix FTBFS on ppc64el.
>
> Thanks for considering the patch.
>
> Logan Rosen
>
>
>
> -- System Information:
> Debian Release: jessie/sid
> APT prefers trusty-updates
> APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500,
> 'trusty'), (100, 'trusty-backports')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.12.0-7-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
> ___
> Debichem-devel mailing list
> debichem-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debichem-devel
>

Bug#734686: xcb-util-cursor: use dh-autoreconf instead of autotools-dev to fix FTBFS on ppc64el

[Logan Rosen]

Package: xcb-util-cursor
Version: 0.1.1-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch

Dear Maintainer,

For the ppc64el architecture in Ubuntu, since this package uses libtool, a full
autoreconf is necessary instead of just config.{sub,guess} updates with
autotools-dev. This is because we need new libtool macros for ppc64el.

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

  * Use dh-autoreconf instead of autotools-dev to fix FTBFS on ppc64el.

Thanks for considering the patch.

Logan Rosen



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

Kernel: Linux 3.13.0-1-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 xcb-util-cursor-0.1.1/debian/control xcb-util-cursor-0.1.1/debian/control
--- xcb-util-cursor-0.1.1/debian/control	2013-12-21 03:46:49.0 -0500
+++ xcb-util-cursor-0.1.1/debian/control	2014-01-09 00:37:24.0 -0500
@@ -2,7 +2,7 @@
 Priority: extra
 Maintainer: Michael Stapelberg 
 Build-Depends: debhelper (>= 9),
-   autotools-dev,
+   dh-autoreconf,
autoconf,
automake,
pkg-config,
diff -Nru xcb-util-cursor-0.1.1/debian/rules xcb-util-cursor-0.1.1/debian/rules
--- xcb-util-cursor-0.1.1/debian/rules	2013-12-21 03:46:49.0 -0500
+++ xcb-util-cursor-0.1.1/debian/rules	2014-01-08 04:04:04.0 -0500
@@ -13,4 +13,4 @@
 	dh_auto_configure -- --disable-silent-rules
 
 %:
-	dh $@  --with autotools-dev
+	dh $@  --with autoreconf

Bug#734685: wreport: use dh-autoreconf to fix FTBFS on ppc64el

[Logan Rosen]

Package: wreport
Version: 2.9-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch

Dear Maintainer,

For the ppc64el architecture in Ubuntu, since this package uses libtool, a full
autoreconf is necessary. This is because we need new libtool macros for
ppc64el.

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

  * Use dh-autoreconf to fix FTBFS on ppc64el.

Thanks for considering the patch.

Logan Rosen



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

Kernel: Linux 3.13.0-1-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 wreport-2.9/debian/control wreport-2.9/debian/control
--- wreport-2.9/debian/control	2013-10-21 17:45:22.0 -0400
+++ wreport-2.9/debian/control	2014-01-09 00:36:24.0 -0500
@@ -6,7 +6,7 @@
   debhelper (>= 9), dh-buildinfo,
   doxygen, gperf, pkg-config,
   liblua5.1-0-dev,
-  libwibble-dev (>= 1.0), libwibble-dev (<< 2.0)
+  libwibble-dev (>= 1.0), libwibble-dev (<< 2.0), dh-autoreconf
 Standards-Version: 3.9.4.0
 Homepage: http://sourceforge.net/p/wreport
 Vcs-Svn: https://svn.smr.arpa.emr.it/dballe/wreport/trunk
diff -Nru wreport-2.9/debian/rules wreport-2.9/debian/rules
--- wreport-2.9/debian/rules	2011-06-16 09:08:11.0 -0400
+++ wreport-2.9/debian/rules	2014-01-08 04:07:22.0 -0500
@@ -5,7 +5,7 @@
 
 
 %:
-	dh $@
+	dh $@ --with autoreconf
 
 override_dh_fixperms:
 	dh_fixperms

Bug#734683: libonig: use dh-autoreconf instead of autotools-dev to fix FTBFS on ppc64el

[Logan Rosen]

Package: libonig
Version: 5.9.1-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch

Dear Maintainer,

For the ppc64el architecture in Ubuntu, since this package uses libtool, a full
autoreconf is necessary instead of just config.{sub,guess} updates with
autotools-dev. This is because we need new libtool macros for ppc64el.

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

  * Use dh-autoreconf instead of autotools-dev to also fix FTBFS on ppc64el by
getting new libtool macros (still updates config.{sub,guess}).
  * Use automake's "foreign" option to fix FTBFS while autoreconfing.

Thanks for considering the patch.

Logan Rosen



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

Kernel: Linux 3.13.0-1-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 -u libonig-5.9.1/debian/rules libonig-5.9.1/debian/rules
--- libonig-5.9.1/debian/rules
+++ libonig-5.9.1/debian/rules
@@ -18,15 +18,7 @@
 configure: debian/stamp-configure
 debian/stamp-configure:
 	dh_testdir
-
-	# update libonig's autotools files
-ifneq "$(wildcard /usr/share/misc/config.sub)" ""
-	cp -f /usr/share/misc/config.sub config.sub
-endif
-ifneq "$(wildcard /usr/share/misc/config.guess)" ""
-	cp -f /usr/share/misc/config.guess config.guess
-endif
-
+	dh_autoreconf
 	CFLAGS="$(CFLAGS)" ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
 		--disable-dependency-tracking \
 		--without-rubydir \
@@ -56,7 +48,7 @@
 	rm -f debian/stamp-*
 
 	[ ! -f Makefile ] || $(MAKE) distclean
-
+	dh_autoreconf_clean
 	dh_clean
 
 install: debian/stamp-install
diff -u libonig-5.9.1/debian/control libonig-5.9.1/debian/control
--- libonig-5.9.1/debian/control
+++ libonig-5.9.1/debian/control
@@ -4,7 +4,7 @@
 Maintainer: Max Kellermann 
 Uploaders: Alexander Wirt 
 Homepage: http://www.geocities.jp/kosako3/oniguruma/
-Build-Depends: debhelper (>= 5), autotools-dev
+Build-Depends: debhelper (>= 5), dh-autoreconf
 Standards-Version: 3.7.3
 
 Package: libonig2
only in patch2:
unchanged:
--- libonig-5.9.1.orig/configure.in
+++ libonig-5.9.1/configure.in
@@ -1,7 +1,7 @@
 dnl Process this file with autoconf to produce a configure script.
 AC_INIT(onig, 5.9.1)
 
-AM_INIT_AUTOMAKE
+AM_INIT_AUTOMAKE([foreign])
 AC_CONFIG_HEADER(config.h)
 
 

Bug#734684: libmwaw: use dh-autoreconf to fix FTBFS on ppc64el

[Logan Rosen]

Package: libmwaw
Version: 0.1.11-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch

Dear Maintainer,

For the ppc64el architecture in Ubuntu, since this package uses libtool, a full
autoreconf is necessary. This is because we need new libtool macros for
ppc64el.

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

  * Use dh-autoreconf to fix FTBFS on ppc64el.

Thanks for considering the patch.

Logan Rosen



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

Kernel: Linux 3.13.0-1-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 libmwaw-0.1.11/debian/control libmwaw-0.1.11/debian/control
--- libmwaw-0.1.11/debian/control	2013-10-08 13:49:35.0 -0400
+++ libmwaw-0.1.11/debian/control	2014-01-09 00:34:46.0 -0500
@@ -1,7 +1,7 @@
 Source: libmwaw
 Priority: optional
 Maintainer: Rene Engelhard 
-Build-Depends: autotools-dev,
+Build-Depends: dh-autoreconf,
debhelper (>= 9),
doxygen,
libboost-dev,
diff -Nru libmwaw-0.1.11/debian/rules libmwaw-0.1.11/debian/rules
--- libmwaw-0.1.11/debian/rules	2013-03-08 07:52:21.0 -0500
+++ libmwaw-0.1.11/debian/rules	2014-01-08 02:53:12.0 -0500
@@ -4,7 +4,7 @@
 #export DH_VERBOSE=1
 
 %:
-	dh $@
+	dh $@ --with autoreconf
 
 override_dh_auto_configure:
 	dh_auto_configure -- --disable-werror --docdir=/usr/share/doc/libmwaw-doc --libdir=/usr/lib \

Bug#734682: libnbio: use dh-autoreconf instead of autotools-dev to fix FTBFS on ppc64el

[Logan Rosen]

Package: libnbio
Version: 0.30-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch

Dear Maintainer,

For the ppc64el architecture in Ubuntu, since this package uses libtool, a full
autoreconf is necessary instead of just config.{sub,guess} updates with
autotools-dev. This is because we need new libtool macros for ppc64el.

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

  * Use dh-autoreconf instead of autotools-dev to also fix FTBFS on ppc64el by
getting new libtool macros (still updates config.{sub,guess}).
  * Use automake's "foreign" option to fix FTBFS while autoreconfing.

Thanks for considering the patch.

Logan Rosen



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

Kernel: Linux 3.13.0-1-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 -u libnbio-0.30/debian/rules libnbio-0.30/debian/rules
--- libnbio-0.30/debian/rules
+++ libnbio-0.30/debian/rules
@@ -35,6 +35,7 @@
 
 config.status: configure
 	dh_testdir
+	dh_autoreconf
 	# Add here commands to configure the package.
 	CFLAGS="$(CFLAGS)" ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info
 
@@ -55,13 +56,7 @@
 
 	# Add here commands to clean up after the build process.
 	[ ! -f Makefile ] || $(MAKE) distclean
-ifneq "$(wildcard /usr/share/misc/config.sub)" ""
-	cp -f /usr/share/misc/config.sub config.sub
-endif
-ifneq "$(wildcard /usr/share/misc/config.guess)" ""
-	cp -f /usr/share/misc/config.guess config.guess
-endif
-
+	dh_autoreconf_clean
 	dh_clean 
 
 install: build
diff -u libnbio-0.30/debian/control libnbio-0.30/debian/control
--- libnbio-0.30/debian/control
+++ libnbio-0.30/debian/control
@@ -2,7 +2,7 @@
 Priority: optional
 Section: net
 Maintainer: Eric Warmenhoven 
-Build-Depends: debhelper (>= 4.0.0), autotools-dev
+Build-Depends: debhelper (>= 4.0.0), dh-autoreconf
 Standards-Version: 3.7.3
 
 Package: libnbio-dev
only in patch2:
unchanged:
--- libnbio-0.30.orig/configure.ac
+++ libnbio-0.30/configure.ac
@@ -1,5 +1,6 @@
-AC_INIT(src/libnbio.c)
-AM_INIT_AUTOMAKE(libnbio, 0.30)
+AC_INIT([libnbio], [0.30])
+AC_CONFIG_SRCDIR([src/libnbio.c])
+AM_INIT_AUTOMAKE([foreign])
 AM_CONFIG_HEADER(include/config.h)
 
 AM_MAINTAINER_MODE

Bug#734681: liboggplay: use dh-autoreconf instead of autotools-dev to fix FTBFS on ppc64el

[Logan Rosen]

Package: liboggplay
Version: 0.2.1~git20091227-1.2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch

Dear Maintainer,

For the ppc64el architecture in Ubuntu, since this package uses libtool, a full
autoreconf is necessary instead of just config.{sub,guess} updates with
autotools-dev. This is because we need new libtool macros for ppc64el.

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

  * Use dh-autoreconf instead of autotools-dev to also fix FTBFS on ppc64el by
getting new libtool macros (still updates config.{sub,guess}).
  * Add AC_CONFIG_MACRO_DIR([m4]) to configure.ac to fix FTBFS while
autoreconfing.

Thanks for considering the patch.

Logan Rosen



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

Kernel: Linux 3.13.0-1-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 -u liboggplay-0.2.1~git20091227/debian/rules liboggplay-0.2.1~git20091227/debian/rules
--- liboggplay-0.2.1~git20091227/debian/rules
+++ liboggplay-0.2.1~git20091227/debian/rules
@@ -4,17 +4,4 @@
-	dh --with quilt $@
+	dh --with quilt,autoreconf $@
 
 override_dh_strip:
 	dh_strip --dbg-package=liboggplay1-dbg
-
-
-# Untill debhelper supports it
-
-override_dh_auto_configure:
-	ln -sf /usr/share/misc/config.sub .
-	ln -sf /usr/share/misc/config.guess .
-	dh_auto_configure
-
-override_dh_auto_clean:
-	dh_auto_clean
-	rm -f config.sub config.guess
-
diff -u liboggplay-0.2.1~git20091227/debian/control liboggplay-0.2.1~git20091227/debian/control
--- liboggplay-0.2.1~git20091227/debian/control
+++ liboggplay-0.2.1~git20091227/debian/control
@@ -1,7 +1,7 @@
 Source: liboggplay
 Priority: extra
 Maintainer: John Francesco Ferlito 
-Build-Depends: debhelper (>= 7.0.50~), quilt (>= 0.46-7~), autotools-dev, pkg-config, liboggz-dev, libfishsound-dev, libtheora-dev, libkate-dev, libsndfile-dev
+Build-Depends: debhelper (>= 7.0.50~), quilt (>= 0.46-7~), dh-autoreconf, pkg-config, liboggz-dev, libfishsound-dev, libtheora-dev, libkate-dev, libsndfile-dev
 Standards-Version: 3.8.3
 Section: libs
 
diff -u liboggplay-0.2.1~git20091227/debian/patches/series liboggplay-0.2.1~git20091227/debian/patches/series
--- liboggplay-0.2.1~git20091227/debian/patches/series
+++ liboggplay-0.2.1~git20091227/debian/patches/series
@@ -1,2 +1,3 @@
+macro-directory
 CVE-2009-3388
 CVE-2009-3378
only in patch2:
unchanged:
--- liboggplay-0.2.1~git20091227.orig/debian/patches/macro-directory
+++ liboggplay-0.2.1~git20091227/debian/patches/macro-directory
@@ -0,0 +1,11 @@
+--- a/configure.ac
 b/configure.ac
+@@ -12,6 +12,8 @@
+ SHARED_VERSION_INFO="2:0:1"
+ SHLIB_VERSION_ARG=""
+ 
++AC_CONFIG_MACRO_DIR([m4])
++
+ # Checks for programs
+ AC_PROG_CC
+ AC_PROG_LIBTOOL

Bug#727353: daq: update config.{sub,guess} for the AArch64 port

[Logan Rosen]

Package: daq
Version: 0.6.2-2
Followup-For: Bug #727353
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch

Dear Maintainer,

For the ppc64el architecture in Ubuntu, since this package uses libtool, a full
autoreconf is necessary instead of just config.{sub,guess} updates with
autotools-dev. This is because we need new libtool macros for ppc64el.

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

  * Use dh-autoreconf to get new libtool macros for ppc64el and update
config.{sub,guess} for new arches.

Thanks for considering the patch.

Logan Rosen



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

Kernel: Linux 3.13.0-1-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 daq-0.6.2/debian/control daq-0.6.2/debian/control
--- daq-0.6.2/debian/control	2011-01-12 19:34:06.0 -0500
+++ daq-0.6.2/debian/control	2014-01-09 00:30:53.0 -0500
@@ -1,7 +1,7 @@
 Source: daq
 Priority: extra
 Maintainer: Javier Fernandez-Sanguino Pen~a 
-Build-Depends: debhelper (>= 7.0.50~), autotools-dev, libpcap0.8-dev, flex, bison
+Build-Depends: debhelper (>= 7.0.50~), dh-autoreconf, libpcap0.8-dev, flex, bison
 Standards-Version: 3.8.4
 Section: libs
 Homepage: http://www.snort.org/snort-downloads
diff -Nru daq-0.6.2/debian/rules daq-0.6.2/debian/rules
--- daq-0.6.2/debian/rules	2010-11-10 19:50:34.0 -0500
+++ daq-0.6.2/debian/rules	2014-01-08 03:22:36.0 -0500
@@ -11,5 +11,5 @@
 #export DH_VERBOSE=1
 
 %:
-	dh $@ 
+	dh $@ --with autoreconf 
 #	dh $@  --with quilt

Bug#734680: npth: use dh-autoreconf instead of autotools-dev to fix FTBFS on ppc64el

[Logan Rosen]

Package: npth
Version: 0.91-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu trusty ubuntu-patch

Dear Maintainer,

For the ppc64el architecture in Ubuntu, since this package uses libtool, a full
autoreconf is necessary instead of just config.{sub,guess} updates with
autotools-dev. This is because we need new libtool macros for ppc64el.

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

  * Use dh-autoreconf instead of autotools-dev to fix FTBFS on ppc64el.

Thanks for considering the patch.

Logan Rosen



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

Kernel: Linux 3.13.0-1-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 npth-0.91/debian/control npth-0.91/debian/control
--- npth-0.91/debian/control	2013-05-06 12:56:46.0 -0400
+++ npth-0.91/debian/control	2014-01-09 00:27:45.0 -0500
@@ -2,7 +2,7 @@
 Section: libdevel
 Priority: optional
 Maintainer: Eric Dorland 
-Build-Depends: debhelper (>= 9), autotools-dev
+Build-Depends: debhelper (>= 9), dh-autoreconf
 Standards-Version: 3.9.3.1
 Vcs-Git: git://git.debian.org/git/users/npth.git
 Vcs-Browser: http://git.debian.org/?p=users/eric/npth.git;a=summary
diff -Nru npth-0.91/debian/rules npth-0.91/debian/rules
--- npth-0.91/debian/rules	2013-05-06 12:56:46.0 -0400
+++ npth-0.91/debian/rules	2014-01-08 02:42:13.0 -0500
@@ -1,7 +1,7 @@
 #!/usr/bin/make -f
 
 %:
-	dh $@ --with autotools_dev
+	dh $@ --with autoreconf
 
 override_dh_auto_configure:
 	dh_auto_configure -- --enable-static

Bug#728068: please enable TLS 1.2 by default

[Fabián Rodríguez]

This appears to be fixed upstream for Firefox 27/28. See:
https://bugzilla.mozilla.org/show_bug.cgi?id=861266

As a workaround, you can enable TLS 1.2 in Firefox/Iceweasel 25 and 26 
by setting the preference security.tls.version.max=3 in about:config.

See:
https://bugzilla.mozilla.org/show_bug.cgi?id=861266#c27


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

Bug#734679: ITP: python-docker -- docker-py are python bindings to docker.io's socket voodoo

[Paul Tagliamonte]

Package: wnpp
Severity: wishlist
Owner: Paul Tagliamonte 

* Package name: python-docker
  Version : 0.2.3
  Upstream Author : Docker, Inc
* URL : https://github.com/dotcloud/docker-py
* License : apache2
  Programming Lang: Python
  Description : docker-py are python bindings to docker.io's socket voodoo

An API client for docker written in Python


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

Bug#667582: Status of this bug?

[Josh Triplett]

This bug has had a working patch available (and committed to a branch in
the Debian packaging repository) for more than a year.  Is there
anything preventing that patch from being merged?

- Josh Triplett


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

Bug#734678: Please depend on lua-sec and remove the silly warning

[martin f krafft]

Package: prosody
Version: 0.9.1-1
Severity: normal

[] Starting Prosody XMPP Server: prosody
**
Prosody was unable to find LuaSec
This package can be obtained in the following ways:

  Source:   http://www.inf.puc-rio.br/~brunoos/luasec/
  Debian/Ubuntu:http://prosody.im/download/start#debian_and_ubuntu
  luarocks: luarocks install luasec

SSL/TLS support will not be available
More help can be found on our website, at http://prosody.im/doc/depends
**

. ok 


lua-sec is packaged, so please depend/recommend on it and remove
this message/check.

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

Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


-- 
 .''`.   martin f. krafft   Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#734677: src:qtbase-opensource-src: qt5 packages aren't multi-arch ready

[Dima Kogan]

Package: src:qtbase-opensource-src
Severity: normal
In Debian, QT5 packages have no multi-arch tags. Ubuntu has supposedly
resolved this:

 https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1209239


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

Bug#734676: gnugk: does not create pid file

[Naoto SONE]

Package: gnugk
Version: 2:3.4-2-1
Severity: minor

Dear Maintainer,

I can not stop gnugk with following command "/etc/init.d/gnugk stop". 
pid file was not created in our system.
I created a patch of gnugk init script.

@@ -41,6 +41,7 @@
 case "$1" in
   start)
echo -n "Starting $DESC: "
+   [ -d /var/run/$NAME ] || install -d -o$NAME -g$NAME -m755 /var/run/$NAME
start-stop-daemon --start --quiet \
--chuid $NAME --pidfile /var/run/$NAME/$NAME.pid \
--background --exec $DAEMON -- $ARGS

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

Kernel: Linux 3.12-1-amd64 (SMP w/2 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 gnugk depends on:
ii  adduser  3.113+nmu3
ii  libc62.17-97
ii  libexpat12.1.0-4
ii  libgcc1  1:4.8.2-10
ii  libh323-1.24.0   1.24.0~dfsg2-1+b1
ii  libldap-2.4-22.4.31-1+nmu2+b1
ii  libodbc1 2.3.1-1
ii  libpt2.10.10 2.10.10~dfsg-2.1
ii  libsasl2-2   2.1.25.dfsg1-17
ii  libsdl1.2debian  1.2.15-8
ii  libssh-4 0.5.4-1
ii  libssl1.0.0  1.0.1e-6
ii  libstdc++6   4.8.2-10

gnugk recommends no packages.

Versions of packages gnugk suggests:
pn  ekiga  
pn  ohphone
pn  ohphone-basic  
pn  simph323   

-- Configuration Files:
/etc/gatekeeper.ini changed [not included]
/etc/init.d/gnugk 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#734675: fftw3: Fix configury for neon support on arm64 (armv8)

[Wookey]

Source: fftw3
Version: 3.3.3-7
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertag: arm64

In version 3.3.3-6 arm64 was added to the --enable-neon arch list. This
is correct in principle but doesn't work because both the enabling
compiler option and the compiler define have changed between the 32-bit
armv7 (for which this code was written) and armv8 (the 64-bit arch,
called 'arm64' in debian and 'aarch64' by ARM and GNU triplets).

neon is always enabled on armv8/arm64 unless explictly disabled so the
-mfpu=neon option is not understood by the arm64/aarch64 compiler. Also
__ARM_NEON__ is not defined by the compiler. So this needs changes in
configure.ac and simd-neon.h

However, applying this doesn't in fact get a working build as it exposes
a compiler ICE in the gcc4.8 we are currently using in unstable. But
that should get fixed soon.

Note that full support for arm64 will include enabling double-precision,
as that is available in armv8 neon, and writing code to support it.

Also note that armv8 has fused multiply-accumulate by default, which
apparently needs to be recorded for this package. I failed to understand
exactly what was going on with that so have not changed anything in this
patch, not least because doing so prduced another failure to build, as
have_fma and --enable-neon are deemed incompatible.

-- System Information:
Debian Release: 7.3
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-kvm-i386-20110111 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -Nru fftw3-3.3.3/debian/changelog fftw3-3.3.3/debian/changelog
--- fftw3-3.3.3/debian/changelog	2013-10-27 13:32:57.0 +
+++ fftw3-3.3.3/debian/changelog	2014-01-07 18:04:54.0 +
@@ -1,3 +1,9 @@
+fftw3 (3.3.3-7arm641) unstable; urgency=low
+
+  * Correct neon arm64 support in configurey
+
+ --Tue, 07 Jan 2014 18:03:45 +
+
 fftw3 (3.3.3-7) unstable; urgency=low
 
   * restrict architectures of long dependency of libfftw3-3 (Closes: #710890)
diff -Nru fftw3-3.3.3/debian/patches/arm64-neon-config.patch fftw3-3.3.3/debian/patches/arm64-neon-config.patch
--- fftw3-3.3.3/debian/patches/arm64-neon-config.patch	1970-01-01 00:00:00.0 +
+++ fftw3-3.3.3/debian/patches/arm64-neon-config.patch	2014-01-07 18:43:56.0 +
@@ -0,0 +1,27 @@
+Index: fftw3-3.3.3/configure.ac
+===
+--- fftw3-3.3.3.orig/configure.ac	2012-11-25 12:33:44.0 +
 fftw3-3.3.3/configure.ac	2014-01-07 18:25:34.89000 +
+@@ -273,7 +273,8 @@
+ 			[AC_MSG_ERROR([Need a version of gcc with -maltivec])])])])
+ 	fi
+ 
+-	if test "$have_neon" = "yes" -a "x$NEON_CFLAGS" = x; then
++	# armhf (no flag needed on arm64)
++	if test "$host_cpu" = "arm" -a "$have_neon" = "yes" -a "x$NEON_CFLAGS" = x; then
+ 	AX_CHECK_COMPILER_FLAGS(-mfpu=neon, [NEON_CFLAGS="-mfpu=neon"],
+ 		[AC_MSG_ERROR([Need a version of gcc with -mfpu=neon])])
+ 	fi
+Index: fftw3-3.3.3/simd-support/simd-neon.h
+===
+--- fftw3-3.3.3.orig/simd-support/simd-neon.h	2012-11-25 12:33:44.0 +
 fftw3-3.3.3/simd-support/simd-neon.h	2014-01-07 18:43:48.5 +
+@@ -29,7 +29,7 @@
+ #define SIMD_VSTRIDE_OKA(x) ((x) == 2)
+ #define SIMD_STRIDE_OKPAIR SIMD_STRIDE_OK
+ 
+-#if defined(__GNUC__) && !defined(__ARM_NEON__)
++#if defined(__GNUC__) && !defined(__ARM_NEON__) && !defined (__aarch64__) 
+ #error "compiling simd-neon.h requires -mfpu=neon or equivalent"
+ #endif
+ 
diff -Nru fftw3-3.3.3/debian/patches/series fftw3-3.3.3/debian/patches/series
--- fftw3-3.3.3/debian/patches/series	2013-10-27 13:32:57.0 +
+++ fftw3-3.3.3/debian/patches/series	2014-01-07 17:38:41.0 +
@@ -5,3 +5,4 @@
 texinfo5-compat.patch
 wisdom-manpage.patch
 fix-fftw-wisdom-to-conf.patch
+arm64-neon-config.patch

Bug#734674: eclipse: Frequently segfaults under some circumstances

[Rogério Brito]

Package: eclipse
Version: 3.8.1-4
Severity: important

Hi, I have been trying to use eclipse for homework for an Android
application and I keep getting crashes with an insane frequency.

Upon inspecting the segfaults, I saw messages in my dmesg log pointing to
libsoup and I found:

http://bugs.debian.org/705420

There, some workarounds are offered, but the final conclusion seems to be
that the bug is not with libsoup, with with eclipse itself:

https://bugzilla.gnome.org/show_bug.cgi?id=710242#c5

The bug in eclipse is filed at:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=404776

And a small patch is available at:


http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=b22a7d19afbe2a3811a0f8aa54c1e85d92c62a2c


Can we have eclipse rebuilt with this patch, please?

This would make eclipse conform to the libsoup API of not passing a null
pointer when one is not expected (a correctness argument) and would probably
make these insanely frequent crashes that I'm seeing disappear (a usability
argument).


Thanks in advance,

Rogério.

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

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf-8, LC_CTYPE=pt_BR.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages eclipse depends on:
pn  eclipse-jdt  
pn  eclipse-pde  

eclipse recommends no packages.

eclipse suggests no packages.

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br


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

Bug#671110: python-lzma: FTBFS if built twice in a row: aborting due to unexpected upstream changes

[Jordan Metzmeier]

Adding pyliblzma.egg-info/PKG-INFO to debian/clean appears to resolve the 
issue. It is 
regenerated each build. I am not sure if actually removing it on clean is the 
correct 
thing to do though.

Regards,
Jordan Metzmeier


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

Bug#734673: libsamplerate: Use autotools-dev to keep config.{sub, guess} up to date for portability

[Wookey]

Source: libsamplerate
Version: 0.1.8
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertag: arm64

This package fails to build on new architectures (noted on arm64)
because the config.sub and config.guess files shipped with the package
are out of date. This patch uses the debhelper helpers to update this
files (and clean them properly so it builds twice). This fixes the issue
for future new ports too.

-- System Information:
Debian Release: 7.3
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-kvm-i386-20110111 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -Nru libsamplerate-0.1.8/debian/changelog libsamplerate-0.1.8/debian/changelog
--- libsamplerate-0.1.8/debian/changelog	2012-06-18 09:54:12.0 +
+++ libsamplerate-0.1.8/debian/changelog	2014-01-08 16:30:12.0 +
@@ -1,3 +1,9 @@
+libsamplerate (0.1.8-5arm64) unstable; urgency=low
+
+  * Ensure config.{sub,guess} up to date for new ports
+
+ --Wed, 08 Jan 2014 16:29:34 +
+
 libsamplerate (0.1.8-5) unstable; urgency=low
 
   * debian/rules: Purge *.la files after install.
diff -Nru libsamplerate-0.1.8/debian/control libsamplerate-0.1.8/debian/control
--- libsamplerate-0.1.8/debian/control	2012-06-18 09:54:12.0 +
+++ libsamplerate-0.1.8/debian/control	2014-01-08 16:30:45.0 +
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Erik de Castro Lopo 
 DM-Upload-Allowed: yes
-Build-Depends: debhelper (>> 8.1.3), fftw3-dev, libsndfile1-dev
+Build-Depends: debhelper (>> 8.1.3), autotools-dev, fftw3-dev, libsndfile1-dev
 Standards-Version: 3.9.3
 Homepage: http://www.mega-nerd.com/SRC/
 
diff -Nru libsamplerate-0.1.8/debian/rules libsamplerate-0.1.8/debian/rules
--- libsamplerate-0.1.8/debian/rules	2012-06-18 09:54:12.0 +
+++ libsamplerate-0.1.8/debian/rules	2014-01-08 16:29:10.0 +
@@ -17,6 +17,7 @@
 
 config.status: configure
 	dh_testdir
+	dh_autotools-dev_updateconfig
 	./configure  $(shell dpkg-buildflags --export=configure) \
 		--host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
 		--prefix=/usr --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
@@ -39,6 +40,7 @@
 
 	[ ! -f Makefile ] || $(MAKE) distclean
 
+	dh_autotools-dev_restoreconfig
 	dh_clean -a
 
 install: build

Bug#734655: terminator fail to honor x-terminal-emulator -e syntax

[Dominique Michel]

Le Wed, 8 Jan 2014 17:22:44 -0500,
Julián Moreno Patiño  a écrit :

Hi again Julián,

To be sure it is no misunderstanding, this issue is not about
terminator itself, but about terminator used a x-terminal-emulator.

When it is the case, no quoting must be necessary to get a command like

x-terminal-emulator -e mc /home/dom

to work.

And I get the exact same error than when calling it directly.

Thanks,
Dominique

> severity 734655 normal
> tags 734655 + moreinfo
> thanks
> 
> Hello Dominnique,
> 
> Do you try it : terminator -e 'mc /home/dom' ?

Yes I did and it work. But it must work without it when terminator is
called via x-terminal-emulator, and I get the same error in both cases.

It look like it is a patch for that in Ubuntu.


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

Bug#725778: libasyncns:config.guess/config.sub out of date for arm64

[Wookey]

The automatic autoreconf in the above patch is generally best, but if
you baulk at that I can confim that the attached more conservative
dh-autotools-dev patch also fixes the ftbfs for arm64.


Wookey
-- 
Principal hats:  Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
diff -Nru libasyncns-0.8/debian/control libasyncns-0.8/debian/control
diff -Nru libasyncns-0.8/debian/rules libasyncns-0.8/debian/rules
--- libasyncns-0.8/debian/rules	2011-07-30 20:23:25.0 +0100
+++ libasyncns-0.8/debian/rules	2013-10-08 09:53:00.0 +0100
@@ -7,7 +7,7 @@
 export LDFLAGS=-Wl,--as-needed
 
 %:
-	dh  $@
+	dh $@ --with autotools-dev
 
 override_dh_auto_configure:
 	dh_auto_configure -- --docdir=/usr/share/doc/libasyncns-dev

Bug#734672: pu: package subversion/1.6.17dfsg-4+deb7u5

[James McCoy]

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

Subversion's transition to the non-versioned ruby-svn package didn't
make it into Wheezy.  Since ruby1.8 is planning on being removed for
Jessie, the libsvn-ruby1.8 → ruby-svn transition should be backported to
Wheezy so there's an upgrade path to what will be Jessie's ruby-svn
(built with something other than ruby1.8) package.

In addition, libsvn-dev contains a broken /usr/lib/$arch/libsvnjavahl-1.so
symlink (#711911) which is trivial to fix.

The attached debdiff contains both of these changes.  Does this seem
reasonable?

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 
diffstat for subversion_1.6.17dfsg-4+deb7u4 subversion_1.6.17dfsg-4+deb7u5

 debian/libsvn-ruby1.8.install   |2 --
 debian/libsvn-ruby1.8.links |1 +
 debian/libsvn-ruby1.8.lintian-overrides |2 --
 debian/libsvn-ruby1.8.postinst  |   12 
 debian/ruby-svn.install |2 ++
 debian/ruby-svn.lintian-overrides   |2 ++
 subversion-1.6.17dfsg/debian/changelog  |9 +
 subversion-1.6.17dfsg/debian/control|   13 -
 subversion-1.6.17dfsg/debian/rules  |5 +++--
 9 files changed, 37 insertions(+), 11 deletions(-)

diff -u subversion-1.6.17dfsg/debian/control subversion-1.6.17dfsg/debian/control
--- subversion-1.6.17dfsg/debian/control
+++ subversion-1.6.17dfsg/debian/control
@@ -100,7 +100,7 @@
 Recommends: python-subversion (>= 1.5), libsvn-perl (>= 1.5),
 libconfig-inifiles-perl, liburi-perl,
 exim4 | mail-transport-agent, xsltproc, rsync
-Suggests: libsvn-ruby1.8
+Suggests: ruby-svn
 Description: Assorted tools related to Subversion
  This package includes miscellaneous tools for use with Subversion
  clients and servers:
@@ -144,22 +144,25 @@
  manipulates a Subversion repository or working copy.  See the
  'subversion' package for more information.
 
-Package: libsvn-ruby1.8
+Package: ruby-svn
 Section: ruby
 Architecture: any
 Multi-Arch: same
 Pre-Depends: multiarch-support
+Breaks: libsvn-ruby1.8 (<< 1.6.17dfsg-4+deb7u5)
 Depends: ruby1.8, ${shlibs:Depends}, ${misc:Depends}
+Replaces: libsvn-ruby1.8 (<< 1.6.17dfsg-4+deb7u5)
 Description: Ruby bindings for Subversion
  This is a set of Ruby interfaces to libsvn, the Subversion libraries.
  It is useful if you want to, for example, write a Ruby script that
  manipulates a Subversion repository or working copy.  See the
  'subversion' package for more information.
 
-Package: libsvn-ruby
-Section: ruby
+Package: libsvn-ruby1.8
+Section: oldlibs
+Priority: extra
 Architecture: all
-Depends: libsvn-ruby1.8, ${misc:Depends}
+Depends: ruby-svn, ${misc:Depends}
 Description: Ruby bindings for Subversion (dummy package)
  This is a dummy package to install the Subversion library bindings for
  the default version of Ruby.
reverted:
--- subversion-1.6.17dfsg/debian/libsvn-ruby1.8.lintian-overrides
+++ subversion-1.6.17dfsg.orig/debian/libsvn-ruby1.8.lintian-overrides
@@ -1,2 +0,0 @@
-# nobody but us will ever link to this, so we don't ship a shlibs file
-no-shlibs-control-file usr/lib/*/libsvn_swig_ruby-1.so.*
diff -u subversion-1.6.17dfsg/debian/rules subversion-1.6.17dfsg/debian/rules
--- subversion-1.6.17dfsg/debian/rules
+++ subversion-1.6.17dfsg/debian/rules
@@ -118,7 +118,7 @@
   rb_defs := SWIG_RB_SITE_LIB_DIR=$(shell $(RUBY) -rrbconfig -e "print RbConfig::CONFIG['vendordir']")
   rb_defs += SWIG_RB_SITE_ARCH_DIR=$(shell $(RUBY) -rrbconfig -e "print RbConfig::CONFIG['vendorarchdir']")
 else
-  DH_OPTIONS += -Nlibsvn-ruby -Nlibsvn-$(RUBY)
+  DH_OPTIONS += -Nruby-svn -Nlibsvn-$(RUBY)
   RUBY := fooby
 endif
 
@@ -346,13 +346,14 @@
 	cd debian/tmp/$(libdir); for lib in ra fs auth swig; do \
 	$(RM) libsvn_$${lib}_*.so libsvn_$${lib}_*.la; \
 	done
-	cd debian/tmp/$(libdir); $(RM) libsvn_swig*.a libsvnjavahl.a libsvnjavahl.la
+	cd debian/tmp/$(libdir); $(RM) libsvn_swig*.a libsvnjavahl-1.a libsvnjavahl-1.la
 	# Intermediate hack, until we can remove the rest of the .la files.
 	sed -i  "/dependency_libs/s/=.*/=''/" debian/tmp/$(libdir)/*.la
 	dh_install -s
 ifdef DEB_OPT_WITH_JAVAHL
 	mkdir -p debian/libsvn-java/$(libdir)
 	mv debian/libsvn-java/usr/lib/jni debian/libsvn-java/$(libdir)/
+	$(RM) debian/libsvn-dev/$(libdir)/libsvnjavahl-1.so
 endif
 	ln -s libsvn_ra_neon-1.so.1 debian/libsvn1/$(libdir)/libsvn_ra_dav-1.so.1
 
reverted:
--- subversion-1.6.17dfsg/debian/libsvn-ruby1.8.install
+++ subversion-1.6.17dfsg.orig/debian/libsvn-ruby1.8.install
@@ -1,2 +0,0 @@
-debian/tmp/usr/lib/*/libsvn_swig_ruby*.so.*
-debian/tmp/usr/lib/ruby
diff -u subversion-1.6.17dfsg/debian/changelog subversion-1.6.17dfsg/debian/changelog
--- subversion-1.6.17dfsg/debian/changelog
+++ subversion-1.6.17dfsg/debian/changelog
@@ -1,3 +1,12 @@
+subversion (1.6.17dfsg-4+deb7u5) UNRELEASED; urgency=low
+
+  * rules: Fix removal of libsvnjavahl-1.a/.la/.so from libsvn-dev.

Bug#734671: enable pam_keyinit by default

[Russ Allbery]

Package: libpam-runtime
Version: 1.1.3-10
Severity: wishlist

It would be better for any application that uses the kernel keyring
if pam_keyinit were run by default in the PAM session stack.  Without
this module, users are placed in a default UID-based user session,
which doesn't isolate each session's keys.

Worse, currently (although this is a separate bug that's been
separately reported and may be fixed in the future), the kernel uses
the UID session for reading, but when writing creates a new session
keyring that's limited to children of the writing process.  This
basically makes use of keyring Kerberos caches impossible unless one
does the equivalent of what pam_keyinit does first.  It's rather
inobvious that this is necessary.

The problem with this, which will make it more complex, is that one
generally does not want to create a new session keyring when running
commands like su or sudo, just for login sessions, since you normally
want to preserve the user's existing credentials.  I'm not sure what
this means for how to achieve this configuration.

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

Kernel: Linux 3.11-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

Versions of packages libpam-runtime depends on:
ii  debconf [debconf-2.0]  1.5.52
ii  libpam-modules 1.1.3-10

libpam-runtime recommends no packages.

libpam-runtime suggests no packages.

-- debconf information:
  libpam-runtime/profiles: unix, systemd, consolekit
  libpam-runtime/no_profiles_chosen:
  libpam-runtime/conflicts:
  libpam-runtime/title:
  libpam-runtime/override: false


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

Bug#734403: linux-image-3.12-1-amd64: "shutdown -h now" makes computer restart

[Jose R R]

Niltze, all!



On Mon, Jan 6, 2014 at 6:50 PM, Ben Hutchings  wrote:
> Control: tag -1 moreinfo
>
> On Mon, 2014-01-06 at 22:19 +, Robert Lemmen wrote:
>> Package: src:linux
>> Version: 3.12.6-2
>> Severity: normal
>>
>> hi there,
>>
>> the last aptitude upgrade my kernel got updated to 3.12-1-amd64, since
>> then something very strange happens: when i do a "shutdown -h now", thge
>> computer shuts down as expected, and all lights and fans go off. but
>> after a few more seconds, the whole thing restarts itself, a bit of a
>> zombie moment. I originally expected this to be some bizarre hardware
>> thing, but then I found a report [0] linking this to the kernel
>> (different version in their case). I still had linux-image-3.11-2-amd64
>> installed, so I rebooted into that and retried (a couple of times to
>> make sure), and i'll be damned but that kernel does the shutdown fine!
>>
>> I have no clue how all that ACPI or whatever works, bbut something there
>> isn't ideal.
>
> Many devices can generate a wake-up signal after the computer is shut
> down (wake on LAN, wake on key, etc.) and this is evidently happening
> when it should not.  So it is hardware-related but probably caused by a
> change in the way a driver prepares the hardware for shutdown.
>
>> happy to try a few things if you point me in the right
>> direction
> [...]
>
> Please try to work out which driver is doing this, by removing a driver
> with the 'rmmod' command and then shutting down.  I think it is probably
> one of:
>
> e1000e
> igb
> xhci_hcd
> ehci-pci
>
> Ben.
>
> --
> Ben Hutchings
> Any smoothly functioning technology is indistinguishable from a rigged demo.

As an experiment before upgrading to a newer kernel in this laptop,
which runs 64-bit Debian with my kernel 3.12.2 built from
https://www.kernel.org/ , yesterday evening I entered the directive:
shutdown -h now ... it did *and* it did not wake up, restart, etc.
until today that I turned it on from its power switch.

Thus, I agree taht it is possible that a driver may be causing the
issue in the hardware from the person that originated this topic.


Best Professional Regards.

-- 
Jose R R
http://www.metztli-it.com
-
IBM Lotus Symphony supported on GNU/Linux, Mac OS, and Windows.
-
Daylight Saving Time in USA & Canada starts: Sunday 08 March 2010
-


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

Bug#734670: cups: Honour DEB_BUILD_OPTIONS=nocheck to allow bootstrapping

[Wookey]

Source: cups
Version: 1.6.4
Severity: normal
Tags: patch

cups build-depends on libcupsfilters-dev (from cups-filters) and
cups-filters build-depends on libcups2-dev (from cups). This means that
in a port bootstrap neither of these package can be built first.

This patch allows the untangling of this curcular build-dependency by
allowing cups to honour the 'nocheck' build-option which skips tests.
(recommended in
http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules-options
)

Because cups only need cups-filters for the test, this is all that is needed.

A later patch will supply annotations to the Build-Depends, allowing
full automation, but that is not yet suitable for the archive. Having
the mechanism present in the rules file is still very useful to porters.
(I just used it for the arm64 bootstrap).

See https://wiki.debian.org/DebianBootstrap for more info on this general 
subject.

-- System Information:
Debian Release: 7.3
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-kvm-i386-20110111 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Description: Honour DEB_BUILD_OPTIONS=nocheck
This allows bootstraping because cups-filters and libcupsfilters-dev 
dependencies are only needed for tests. Ideally DEB_BUILD_PROFILES 
annotations of the build-deps to record this would accompany this patch, 
but they are not yet suitable for the archive, so that will come later.

Author: wookey   Sat, 04 Jan 2014 00:24:54 +


diff -Nru cups-1.6.4/debian/rules cups-1.6.4/debian/rules
--- cups-1.6.4/debian/rules	2013-10-02 08:36:50.0 +
+++ cups-1.6.4/debian/rules	2014-01-04 00:23:58.0 +
@@ -135,7 +135,9 @@
 	dh_fixperms -Xusr/lib/cups/backend-available
 
 override_dh_auto_test:
+ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
 	make check
+endif
 
 ifeq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
 override_dh_makeshlibs:

Bug#734669: avahi: Add DEB_BUILD_PROFILES stage1 support for bootstraping

[Wookey]

Source: avahi
Version: 0.6.31-4
Severity: normal
Tags: patch

avahi needs gtk2, gtk3 and QT to build, but is also needed to build
packages which gtk3 and QT build-depend on, thus it is involved in one of
the many circular build-deps in Debian.

We are working to make Debian bootstrappable by adding 'profile'
information to packages to untangle these circular dependencies, and
make the dependency relations into an actual tree.

This patch contains the necessary debian/rules changes to build a basic
libavahi without all the GUI tools. It is generally nice and clean,
except for the need to fake up a man page file to stop the build barfing
due to one being missing. This could also be done using dh_exec to make
the .install file conditional, or take that file out of the .install file
and copy it in the rules file. Use whichever of these solutions seems
nicest to you.

A later patch will provide the Build-Depends profile annotations to the
control file, but these cannot yet go into the main archive so I'm not
sending those in yet. Having the build mechanism in in the meantime is
still very useful to porters.

See https://wiki.debian.org/DebianBootstrap for more info 

-- System Information:
Debian Release: 7.3
  APT prefers stable
  APT policy: (990, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-kvm-i386-20110111 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -Nru avahi-0.6.31/debian/changelog avahi-0.6.31/debian/changelog
--- avahi-0.6.31/debian/changelog	2013-12-26 17:36:01.0 +
+++ avahi-0.6.31/debian/changelog	2014-01-03 18:29:30.0 +
@@ -1,3 +1,10 @@
+avahi (0.6.31-4profile1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * Add stage1 DEB_BUILD_PROFILE avoiding gtk and qt build-deps 
+
+ -- wookey   Fri, 03 Jan 2014 18:28:40 +
+
 avahi (0.6.31-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru avahi-0.6.31/debian/rules avahi-0.6.31/debian/rules
--- avahi-0.6.31/debian/rules	2013-11-26 19:22:52.0 +
+++ avahi-0.6.31/debian/rules	2014-01-03 19:00:52.0 +
@@ -9,6 +9,14 @@
 	CONFFLAGS += --disable-autoipd
 endif
 
+#disable gtk and qt parts of build for bootstrap
+ifeq ($(words $(sort $(filter stage1,$(DEB_BUILD_PROFILES,1)
+DH_OPTIONS += -Nlibavahi-qt4-1 -Nlibavahi-qt4-dev -Navahi-discover
+DH_OPTIONS += -Nlibavahi-ui0 -Nlibavahi-ui-dev -Navahi-ui-utils
+DH_OPTIONS += -Nlibavahi-ui-gtk3-0 -Nlibavahi-ui-gtk3-dev
+CONFIGURE_SWITCHES += --disable-gtk --disable-gtk3 --disable-qt4 --disable-pygtk
+endif
+
 # Ensure at build time that the library has no dependencies on undefined
 # symbols, and speed up loading.
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,-z,defs -Wl,-O1 -Wl,--as-needed
@@ -20,7 +28,8 @@
 		--disable-monodoc \
 		--disable-qt3 \
 		--enable-gtk3 \
-		--with-systemdsystemunitdir=/lib/systemd/system
+		--with-systemdsystemunitdir=/lib/systemd/system \
+		$(CONFIGURE_SWITCHES)
 
 override_dh_auto_build:
 	dh_auto_build
@@ -44,13 +53,17 @@
 
 # List any files which are not installed
 override_dh_install:
-	dh_install --list-missing
+	dh_install --list-missing $(DH_OPTIONS)
 
 override_dh_installinit:
 	dh_installinit -pavahi-daemon -- start 14 2 3 4 5 . stop 86 0 1 6 .
 	dh_installinit -pavahi-dnsconfd -- start 16 2 3 4 5 . stop 84 0 1 6 .
 
 override_dh_installdocs:
+#bodge missing manpage
+	ifeq ($(words $(sort $(filter stage1,$(DEB_BUILD_PROFILES,1)
+	  debian/tmp/usr/share/man/man1/avahi-discover.1
+	endif
 	dh_installdocs --all docs/NEWS docs/README
 
 override_dh_strip:

Bug#733831: wiggle: FTBFS on big endian (mips, powerpc, s390x sparc) but built previously

[NeilBrown]

On Mon, 6 Jan 2014 04:11:10 + Dimitri John Ledkov  wrote:

> Control: tag -1 patch
> 
> 
> On 6 January 2014 03:28, NeilBrown  wrote:
> >
> > On Wed, 1 Jan 2014 04:06:44 + Dimitri John Ledkov  
> > wrote:
> >
> > > On 1 January 2014 03:55, NeilBrown  wrote:
> > > > On Wed, 01 Jan 2014 02:49:26 + Dimitri John Ledkov 
> > > > wrote:
> > > >
> > > >> I'm also CC'ing upstream author of wiggle, to look into big-endian
> > > >> test-failures. Maybe it's something obvious for Neil =)
> > > >
> > > > There have been a lot of fixes since the 0.9.1 version currently in 
> > > > Debian
> > > > and v1.0 has been released.
> > > > I would suggest trying v1.0 and see if the test failures are fixed 
> > > > there or
> > > > not.
> > > >
> > > > I don't have access to a big-endian so I cannot easily perform the 
> > > > tests and
> > > > find the cause directly.
> > >
> > >
> > > I have access to a debian porter-box big-endian (powerpc) and the
> > > latest git clone also fails in similar fashion. I'll try to get the
> > > logs over. I'm not sure what's the procedure for non-debian-developers
> > > to gain access to those machines. But I guess I can act as a proxy.
> > >
> >
> > I suspect the problem is in "config.h":
> >
> >
> > /* Includes and defines for ccan files */
> >
> > #if !defined(LITTLE_ENDIAN) && !defined(BIG_ENDIAN)
> >  #if defined(__APPLE__) || defined(__FreeBSD__) || defined(__NetBSD__) || 
> > defined(__OpenBSD__)
> >   #include 
> >  #else
> >   #include 
> >  #endif
> > #endif
> > #ifdef LITTLE_ENDIAN
> >  #define HAVE_LITTLE_ENDIAN 1
> >  #define HAVE_BIG_ENDIAN 0
> > #elif defined(BIG_ENDIAN)
> >  #define HAVE_LITTLE_ENDIAN 0
> >  #define HAVE_BIG_ENDIAN 1
> > #else
> >  #error Unknown endian
> > #endif
> >
> >
> >
> >  seems to define both LITTLE_ENDIAN and BIG_ENDIAN, so the above
> > code doesn't work.
> > Can you just hack it to select the 'BIG_ENDIAN' branch and see if that makes
> > it work?
> 
> But of course it defines both LITTLE & BIG endian macros, as the byte
> order is defined in BYTE_ORDER to the value of either LITTLE or BIG
> endian (and thankfully we don't need to care about "universal" -
> simultaneously big & little endian Mac OS X builds anymore...).
> 
> I've tested the attached patch and the test-suite passes on both
> x86_64 (little) and powerpc (big) endian.
> 
> Would you apply this patch upstream?
> 

Thanks.  I've applied the patch.

NeilBrown


signature.asc
Description: PGP signature

Bug#734668: RM: agda [sparc], hbro [sparc], libghc-happstack-authenticate-dev [sparc], libghc-happstack-authenticate-prof [sparc], libghc-hbro-contrib-dev [sparc], libghc-hbro-contrib-prof [sparc], li

[Clint Adams]

Package: ftp.debian.org
Severity: normal

dak rm --architecture=sparc -p -R -b libghc-happstack-authenticate-dev 
libghc-happstack-authenticate-prof libghc-hbro-dev libghc-hbro-prof 
libghc-hbro-contrib-dev libghc-hbro-contrib-prof libghc-web-routes-dev 
libghc-web-routes-prof libghc-web-routes-boomerang-dev 
libghc-web-routes-boomerang-prof libghc-web-routes-happstack-dev 
libghc-web-routes-happstack-prof libghc-web-routes-hsp-dev 
libghc-web-routes-hsp-prof libghc-web-routes-th-dev libghc-web-routes-th-prof 
agda hbro


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

Bug#508274: Quilt is not the right package to get that fixed

[Martin Quinson]

package: quilt
tag 508274 wontfix
Thanks

Hello,

as we said several times, we are not the CDBS maintainers, so there is
nothing we can do for this bug. Sorry about it, I hope that the actual
CDBS maintainer will accept to reintegrate this file and fix it.

Bye, Mt.

-- 
Alvin: Sinon, le polymorphisme en C, c'est trop bô. :)
Emptty: Ca, c'est clair. Le C, j'aime ca. C'est un peu de l'art primitif,
   mais ca te secoue les tripes...


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

Bug#508162: this should not be in quilt

[Martin Quinson]

package: cdbs
retitle 508162 Please reintegrate the patchsys-quilt.mk from quilt into the 
CDBS package
thanks

As I said one year ago, I am not a CDBS hacker, and I cannot fix the
bugs on this snipet. It would be really better if that file could be
reintegrated near the rest of the CDBS package, please.

Thanks, Mt.

-- 
Most people have a higher than average number of legs. 


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

Bug#734667: Please integrate the patchsys-quilt.mk file from the quilt package

[Martin Quinson]

package: cdbs
version: 0.4.122
severity: wishlist

Follow up for: #508274

As noted one year ago, none of the current quilt maintainer know the
cdbs internals. We have an issue with maintaining the cdbs chunk that
allows to integrate quilt into that build system. We would be very
much in flavor of passing over that file to the CDBS maintainers so
that it gets betterly maintained.

Of course, we'd have to setup some conflicts dependencies between the
packages so that it works, but that's very doable I think.

Would you please accept to integrate that file directly into your
package, please? From my POV, you can rename this file or change it in
any way, I am not really concerned.

Thanks in advance, 
Mt.

-- 
VI VI VI The editor of the beast.


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

Bug#734666: di: problems reporting space in NFS mount point

[Rogério Brito]

Package: di
Version: 4.34-2
Severity: normal

Hi there.

First of all, thank you for maintaining di. It is so really useful that it
is one of the first things that I install on each and every system that I
use.

I have noticed a problem with di when trying to see the amount of space of
an NFS mounted filesystem. In particular, I want to see the amount of space
of my root (local) system and of my NFS mounted filsystem.

When I issue `di -m /`, I get the expected output:

,[ di -m / ]
| Filesystem MountMebis   Used  Avail %Used  fs 
Type
| /dev/sdc1  / 462186.2   237931.0   224239.2   51%  
ext4   
`

When I issue `di -m /media/lattes`, I also get the expected output:

,[ di -m /media/lattes/ ]
| Filesystem MountMebis   Used  Avail %Used  fs 
Type
| 192.168.1.100:/hom /media/lattes 714450.7   657506.156928.5   92%  
nfs4   
`

Unfortunately, when I issue `di -m / /media/lattes` to show the space of
both filesystems, I only get one entry back (the local filesystem, excluding
the NFS-mounted filesystem):

,[ di -m / /media/lattes ]
| Filesystem MountMebis   Used  Avail %Used  fs 
Type
| /dev/sdc1  / 462186.2   237931.0   224239.2   51%  
ext4   
`

Just for the record, GNU coreutil's df doesn't have this bug, but its output
is horrendous:

,[ df -m / /media/lattes ]
| Filesystem 1M-blocks   Used 
Available Use% Mounted on
| /dev/disk/by-uuid/c1b72bf3-c292-411d-832a-0b92510b158f462187 237932
224240  52% /
| 192.168.1.100:/home/rbrito714451 657507 
56929  93% /media/lattes
`

I would have expected di to show me an output like (this is edited):

,
| Filesystem MountMebis   Used  Avail %Used  fs 
Type
| /dev/sdc1  / 462186.2   237931.0   224239.2   51%  
ext4   
| 192.168.1.100:/hom /media/lattes 714450.7   657506.156928.5   92%  
nfs4   
`


Thanks once again,

Rogério Brito.

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

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf-8, LC_CTYPE=pt_BR.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages di depends on:
ii  libc6  2.17-97

di recommends no packages.

di suggests no packages.

-- no debconf information

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br


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

Bug#734665: clusterssh: ctel does not use telnet, but ssh instead.

[James Zuelow]

Package: clusterssh
Version: 4.01.01-4
Severity: important

Dear Maintainer,

Bug 697185 was resolved about a year ago.

However after point releases, clusterssh in stable is still broken.

Is this bug considered a "wontfix" for stable?

Thank you!

James


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

Kernel: Linux 3.2.51 (SMP w/2 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 clusterssh depends on:
ii  libexception-class-perl  1.32-1
ii  libtry-tiny-perl 0.11-1
ii  libx11-protocol-perl 0.56-4
ii  openssh-client   1:6.0p1-4
ii  perl 5.14.2-21+deb7u1
ii  perl-tk  1:804.030-1
ii  xterm278-4

clusterssh recommends no packages.

clusterssh 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#734664: RFP: mate-screensaver -- MATE screen saver and locker

[Vangelis Mouhtsis]

Package: wnpp
Severity: wishlist

* Package name: mate-screensaver
  Version : 1.6.1
  Upstream Author : Stefano Karapetsas 
* URL : http://www.mate-desktop.org/
* License : GPL, LGPL
  Programming Lang: C
  Description : MATE screen saver and locker

 mate-screensaver is a screen saver and locker that aims to have simple,
 sane and secure defaults, and be well integrated with the MATE desktop.
 .
 It is designed to support, among other things:
 .
 * the ability to lock down configuration settings
 * translation into other languages
 * user switching
 .
 This package will be maintained by the Debian MATE Packaging Team.


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

Bug#720092: Please package ocl

[Nobuhiro Iwamatsu]

Hi,

Thanks for your comment.

2014/1/8 Andrey Gursky :
> Hi,
>
> oh, your reply on 24. Sep. 2013 was addressed only to
> 720...@bugs.debian.org and wasn't being cc'ed, so I have not received
> a copy of it.
>
> On Christmas holidays I've tried to build opencv with opencl support
> on Debian Jessie without(!) proprietary OpenCL SDK. It is enough to
> install just 2 additional packages: ocl-icd-dev and ocl-icd-opencl-dev
> in make opencv automatically discover a presence of OpenCL support and
> enable building the ocl module. So you could for now just extend
> build-depends on these 2 packages from main.

Yes, I know about these.
I have debian / control that are additionally matters you pointed out.
  
http://anonscm.debian.org/gitweb/?p=debian-science/packages/opencv.git;a=shortlog;h=refs/heads/ocl-support

But please see
  http://www.debian.org/doc/debian-policy/ch-archive.html#s-contrib
and following line in this section.
  "free packages which require contrib, non-free packages or packages
  which are not in our archive at all for compilation or execution, and..".

^^^

As in this section, restrictions contrib will also affect the Debian
package other than.

If we always necessary SDK of Intel and Nvidia when using opencv-ocl,
opencv will
set handling of contrib. We can choose the Free If you're available
the Gallium with OpenCL.
Therefore, this is the treatment of main.

I dont know why ocl-icd-opencl-dev was installed into main section. If
this have same problem,
(If the library of DFSG incompatible there is only) this should set to contrib.
I will ask about this to maintainer.

>
> There will be no proprietary/contrib dependencies for installing the
> future package libopencv-ocl. Once one needs to use it, then only
> these users will have to install some non-free OpenCL ICD from
> amd/intel/nvidia. Or(!) one can install locally some free (though not
> 100% functioning) OpenCL ICD and use it. I can't see no impacts on the
> opencv ocl module itself. This was the idea of OpenCL ICD: one can
> link to the loader (e.g. libOpenCL.so from ocl-icd-libopencl1) but
> then use a proprietary one.

Is libOpenCL.so DFSG compatible? if this is DFSG incompatible,
ocl-icd should set to contrib.
Or If there is libOpenCL.so (or ICD) of DFSG compatible, there is no problem.
If you know  libOpenCL.so (or ICD) of DFSG compatible, could you tell me?

>
> If it works out with Gallium - it would be great! But the main thing
> for now is to have the ocl module packaged and then one can experiment
> with the either OpenCL implementation.
>

Yes, I think too.

> Regards,
> Andrey
>
>
> 2014/1/8, Nobuhiro Iwamatsu :
>> Hi,
>>
>> I looked again this problem. We can use the Mesa (Gallium) of X.org to
>> non-free except for libraries.
>>   http://www.x.org/wiki/GalliumStatus/
>>   http://www.x.org/wiki/XorgEVoC/GalliumCompute/
>>
>> Is this right?
>>
>> Best regards,
>>   Nobuhiro
>>
>> 2013/9/24 Nobuhiro Iwamatsu :
>>> Hi,
>>>
 Source: opencv
 Version: 2.4.5+dfsg-0exp1
 Severity: normal

 Hi,

 there is a "new" module in opencv: ocl, allowing using OpenCL. It is
 introduced almost a year ago [1]:

 2.4.3 (November 2012):
 Technology-preview version of ocl - OpenCL-accelerated computer vision
 algorithms, contributed by the Chinese Academy of Science

 and it has been improved in consecutive releases:

 2.4.4 (March 2013):
 The openCL-based hardware acceleration (ocl) module is now mature,
 and, with numerous bug fixes, it is largely bug-free.

 2.4.5 (April 2013):
 there are further improvements and extensions in ocl module:...

 2.4.6 (July 2013):
 Binary compatiblility with both OpenCL 1.1/1.2 platforms. Now the
 binaries compiled with any of AMD/Intel/Nvidia's SDK can run on all
 other platforms.

 Please, consider packaging this module.
>>>
>>> I support the ocl module in opencv is difficult in Debian.
>>> Because OCL SDK is in non-free section.
>>> When opencv is dependent on the OCL SDK if, opencv is in contrib section.
>>> Because I want to distribute opencv in the main section, I will not
>>> support ocl module.
>>>
>>> Does this work for you?
>>>
>>> Best regards,
>>>   Nobuhiro
>>>
>>> --
>>> Nobuhiro Iwamatsu
>>>iwamatsu at {nigauri.org / debian.org}
>>>GPG ID: 40AD1FA6
>>
>>
>>
>> --
>> Nobuhiro Iwamatsu
>>iwamatsu at {nigauri.org / debian.org}
>>GPG ID: 40AD1FA6
>>



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


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

Bug#734663: RFP: mate-control-center -- utilities to configure the MATE desktop

[Vangelis Mouhtsis]

Package: wnpp
Severity: wishlist

* Package name: mate-control-center
  Version : 1.6.2
  Upstream Author : Stefano Karapetsas 
* URL : http://www.mate-desktop.org/
* License : GPL, LGPL
  Programming Lang: C
  Description : utilities to configure the MATE desktop

 This package contains configuration applets for the MATE desktop,
 allowing to set accessibility configuration, desktop fonts, keyboard
 and mouse properties, sound setup, desktop theme and background,
 user interface properties, screen resolution, and other MATE parameters.
 .
 It also contains a front end to these applets, which can also be
 accessed with the MATE panel or the Caja file manager.
 .
 This package will be maintained by the Debian MATE Packaging Team.


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

Bug#734662: Please add an example of arch-specific dependency with more than one architecture

[Martin Quinson]

package: debian-policy
version: 3.9.5.0
severity: wishlist

Hello, an example of architecture-restricted dependency with more than
one arch should probably be added to the section 7.1 "Syntax of
relationship fields" of the policy. The document already specify that
the list is space-separated, but an example would still be welcome (at
least to me).

I propose the following chunk:

->8-

If the architecture-restricted dependency should apply to more than
one architecture, simply list all architectures between braces,
separated with spaces. Example:

Build-Depends:
 libluajit5.1-dev [i386 amd64 kfreebsd-i386 armel armhf powerpc mips mipsel],
 liblua5.1-dev [hurd-i386 ia64 kfreebsd-amd64 s390x sparc],
  
8<---

Thanks for the fish,
Mt.

-- 
Autrefois, c'était l'excellence qui faisait la notoriété.
Maintenant, c'est la notoriété qui fait l'excellence.
  --- Alain Finkielkraut


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

Bug#663577: shall 663577 be closed ?

[Holger Levsen]

Hi,

663577 was opened almost 2 years ago, asking for help maintaining irssi-
scripts, as it seems with success, (last upload 3 months ago, 1 open bug), so 
I wonder whether 663577 should be closed...

I stumbled on it while looking at wnpp output and think that others shouldnt 
"waste" their time like this :) (It wasnt much time, but still..)


cheers,
Holger


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

Bug#698765: dh-autoreconf: document handling of packages that only use Autoconf plus config.{guess,sub}

[Wookey]

Colin wrote:
> but no doubt more sensible examples exist

zsh appears to be one such package

just doing 
configure:
dh_autoreconf
dh_autotools-dev_updateconfig

clean:
dh_autotools-dev_restoreconfig
dh_autoreconf_clean

works fine for that package.

I'd expect that to usually work if the build isn't too fancy.

BTW I think you typoed your example above:
cp -f /usr/share/misc/config.guess /usr/share/misc/config.guess ./
should be:
cp -f /usr/share/misc/config.sub /usr/share/misc/config.guess ./


Wookey
-- 
Principal hats:  Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/


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

Bug#734661: ddclient: Please update to 3.8.2

[Reuben Thomas]

Package: ddclient
Version: 3.8.1-1ubuntu2
Severity: wishlist

There was a new release recently. Since it's the first for a while, no
doubt it has lots of good things; specifically, though, it fixes
#690658!

-- System Information:
Debian Release: wheezy/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'saucy-updates'), (500, 
'saucy-security'), (500, 'saucy'), (90, 'trusty')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11.0-14-generic (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

Versions of packages ddclient depends on:
ii  debconf [debconf-2.0]  1.5.50ubuntu1
ii  initscripts2.88dsf-41ubuntu3
ii  lsb-base   4.1+Debian11ubuntu4
ii  perl [perl5]   5.14.2-21build1

Versions of packages ddclient recommends:
ii  libio-socket-ssl-perl  1.76-2ubuntu1

ddclient suggests no packages.

-- debconf information excluded

-- debsums errors found:
debsums: changed file /usr/sbin/ddclient (from ddclient package)


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

Bug#734659: ITP: scannotation - A Java annotation scanner

[Timo Aaltonen]

Package: wnpp
Severity: wishlist

Package name: scannotation
Version : 1.0.3
Upstream Author : Bill Burke
URL : http://scannotation.sourceforge.net/
License : Apache-2.0
Programming Lang: java
Description : A Java annotation scanner

Scannotation is a Java library that creates an annotation database from
a set of .class files.


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

Bug#734571: mc: [copy&] paste adds extra characters

[Drew Parsons]

On Thu, 2014-01-09 at 01:36 +1100, Dmitry Smirnov wrote:

> 
> I don't see how it could be bug in MC. Certainly this is not happening
> in `konsole` in KDE. Feel free to reassign to Gnome Terminal,
> otherwise I'll close this bug few weeks later.

There's no sense just closing the bug, that won't make it go away.

Obviously it's got something to do with the interaction between Gnome
and mc, but which one's responsible, I don't know.  

Copy&paste works fine in Gnome Terminal without mc.

Drew


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

Bug#711489: AWX Web-Interface is a third-party addon, not part of XBMC

[Bálint Réczey]

tags 711489 wontfix
notforwarded 711489
tags 712371 wontfix
notforwarded 712371
thanks

Hi Martin,

Sorry, but AWXi is just an addon which can be installed from XBMC's
repository but they (and thus me in "XBMC from Debian") don't maintain
it.
I would have been happy to forward you to the right people maintaining
it, but the only information I found was that they are "MKay, Mizaki
et al".

I asked for contact info at upstream's bugtracker, they may be able to help:
http://trac.xbmc.org/ticket/14818#comment:2

Thanks,
Balint


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

Bug#734525: apt-listbugs: breaks when /usr/bin/ruby is ruby1.8

[Francesco Poli]

Control: reassign -1 ruby1.8 1.8.7.358-10

On Wed, 08 Jan 2014 03:51:26 +0100 Felix C. Stegerman wrote:

[...]
> > On 2014-01-08 00:06, Francesco Poli wrote:
[...]
> >> This seems to be exactly the same issue that has already been 
> >> reported as bug #734233: http://bugs.debian.org/734233
> > 
> >> I am therefore merging the two reports.
[...]
> It seems to be fixed in ruby1.8 now (http://bugs.debian.org/734319).

Thanks for the heads up, Felix.
Yes, it seems the upgrade of ruby1.8 fixes the issue.

Mmmh, no wait, ruby1.8 no longer provides ruby-interpreter (and this is
good, since now packages depending on "ruby | ruby-interpreter" will
pull in ruby1.9.1), but /usr/bin/ruby1.8 still seems to be a
possible alternative for /usr/bin/ruby ...

I am under the impression that this means it's still possible to find
oneself with a broken ruby-debian: if root manually installed ruby1.8
and ruby1.9.1 and manually set /usr/bin/ruby1.8 as the alternative
for /usr/bin/ruby, I think the upgrade
  ruby1.8 1.8.7.358-9 → 1.8.7.358-10
won't alter the alternatives and apt-listbugs will fail to run.

Antonio, please correct me if I am wrong.
Is there a way to declare that /usr/bin/ruby1.8 is no longer a valid
alternative for /usr/bin/ruby ?
Should the ruby1.8.postinst run
  update-alternatives --remove ruby /usr/bin/ruby1.8
or something like that?

I am reassigning this bug report to ruby1.8, but I am not yet closing or
merging it, since there is this last doubt to be clarified.

Antonio, please let me know.
Thanks for your time!

-- 
 http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
 New GnuPG key, see the transition document!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpAnVWrtMPR9.pgp
Description: PGP signature

Bug#734657: apvlv: APT Virtual Package pdf-viewer does not include apvlv

[Ricardo Peliquero]

Package: apvlv
Version: 0.1.1-1.2+b1
Severity: wishlist

Dear Maintainer,

Please consider adding apvlv in Debian APT as a pdf-viewer virtual package.

Thank you,

Ricardo Peliquero

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

Kernel: Linux 3.13-rc6-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages apvlv depends on:
ii  libatk1.0-0 2.10.0-2
ii  libc6   2.17-97
ii  libcairo2   1.12.16-2
ii  libdjvulibre21  3.5.25.4-2
ii  libfontconfig1  2.11.0-2
ii  libfreetype62.5.2-1
ii  libgcc1 1:4.8.2-12
ii  libgdk-pixbuf2.0-0  2.28.2-1+b1
ii  libglib2.0-02.36.4-1
ii  libgtk2.0-0 2.24.22-1
ii  libpango1.0-0   1.36.0-1+b1
ii  libpoppler-glib80.18.4-10
ii  libstdc++6  4.8.2-12

apvlv recommends no packages.

Versions of packages apvlv suggests:
ii  poppler-data  0.4.6-4

-- 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#734650: transition: perl 5.18.2

[gregor herrmann]

On Wed, 08 Jan 2014 22:52:00 +0200, Niko Tyni wrote:

> Affected packages that we know of are (hope I got this right)
> 
>  is_affected: ".depends ~ /perl \(<< 5\.18/"
>  bad:  ".depends ~ /perl \(<< 5\.18\.2/"
>  good: ".depends ~ /perl \(<< 5\.18\.3/"
> 
> which would currently yield
> 
>  nmu libpar-packer-perl_1.017-1 . ALL . -m 'rebuild for Perl 5.18.2'
>  nmu libdevel-cover-perl_1.08-1 . ALL . -m 'rebuild for Perl 5.18.2'
>  nmu libclass-xsaccessor-perl_1.19-1 . ALL . -m 'rebuild for Perl 5.18.2'
>  nmu libcommon-sense-perl_3.72-2 . ALL . -m 'rebuild for Perl 5.18.2'

Please note that these binNMUs will need an additional
'extra-depends' on perl 5.18.2 (no idea how to express this).

Cf. #632467 (msg #20).
 
> Additionally, libmodule-corelist-perl will need a source upload
> to upgrade to at least 3.03.

Already done by carnil :)

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
   `-   NP: Rolling Stones: Allwrong


signature.asc
Description: Digital signature

Bug#734597: [Pkg-bitcoin-devel] Bug#734597: litecoin: Litecoin still builds with system LevelDB

[Scott Howard]

On Wed, Jan 8, 2014 at 9:31 AM, Dmitry Smirnov  wrote:
> On Wed, 8 Jan 2014 23:22:37 Micha wrote:
>> It would be better to change Litecoin to use the bundled LevelDB,
>> for the same reason as that is already being done with Bitcoin.
>
> Actually I disagree that it would be better to use bundled LevelDB.

See:
https://docs.google.com/document/d/1naenR6N6fMWSpHM0f4jpQhYBEkCEQDbLBs8AXC19Y-o/edit#heading=h.i7tz3gqh65mi
and
http://sourceforge.net/mailarchive/message.php?msg_id=31207353
for detailed discussion and justification from upstream.

If you disagree, I'd be interested in hearing why.
Cheers,
Scott


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

Bug#733029: dpkg-buildpackage: disable signing by default (-us -uc should be the default)

[Benjamin Drung]

Am Sonntag, den 05.01.2014, 15:09 +0100 schrieb Guillem Jover:
> On Thu, 2014-01-02 at 17:22:33 +, Jonathan Dowland wrote:
> > You raise some very valid points and §I appreciate your concerns and
> > perhaps should rephrase my request so that I'm suggesting subsuming the
> > most common used features of debsign and perhaps as part of a staged
> > migration (compat symlink to debsign binary name in the phase 1, real
> > name dpkg-sign or whatever), to try and avoid further complicating the
> > debian package development universe.
> 
> > On Thu, Jan 02, 2014 at 11:03:04AM +0100, Guillem Jover wrote:
> > > IMO having debsign become a thiner wrapper around this new tool would
> > > be the goal, as it would simplify its code,
> 
> (Obviously, assuming devscripts maintainers would agree, I was just
> inferring from previous interactions regarding debuild for example; in
> any case what happens with debsign would be their decision entirely.)

I agree with this proposal. It can become a thin wrapper around the new
tool (assuming someone does the work). Then it can either fade away (if
the new tool can replace it completely) or stay forever (like debuild)
if it provides additional features.

-- 
Benjamin Drung
Debian & Ubuntu Developer


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

Bug#734495: mingw-w64: Fails to compile Tcl and Tk, please apply workaround patch

[Stephen Kitt]

On Wed, 08 Jan 2014 09:21:23 +0100, Manuel Bilderbeek
 wrote:
> On 07-01-14 23:14, Stephen Kitt wrote:
> > The patch you link to actually applies to Tcl, not to MinGW-w64; the bug
> > is
> 
> Oops!
> Sorry for that! I totally missed that...

No problem!

> I also see that it was fixed upstream in the mean time: 
> http://core.tcl.tk/tcl/info/7488de4f4b203a7f - now to find out in which 
> release this landed...

There hasn't been a release since then, but it seems to me that it's in line
for the next release, 8.6.2 I suppose, whenever that happens.

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#734656: [Pkg-javascript-devel] Bug#734656: nodejs: standard node shebang #!/usr/bin/env node fails in Debian as there is no binary/symlink named 'node' in $PATH

[Paul Tagliamonte]

Tags 734656 - d-i
thanks


On Wed, Jan 08, 2014 at 10:25:05PM +, luke wrote:
> Package: nodejs
> Version: 0.10.24~dfsg1-1
> Severity: grave
> Tags: d-i

Why d-i?

> Dear Maintainer,
> 
> Attempting to use many programs installed with `npm install` fails before
> execution because the Node.js interpreter installed by dpkg/synaptic is not at
> the expected path.  The node binary is named 'nodejs' on Debian, but the node
> community expects the de-facto standard of '#!/usr/bin/env node'.

Please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614907 for
background on the node / node.js naming issue.

> I understand this is a tricky issue, as Javascript was never really designed 
> to
> be run like a shell script, and does not have the heritage of many other Linux
> shell languages.  Additionally, it is unclear from the Node.js project what 
> the
> official name of the binary should be. That said, here are the accepted
> shebangs for some other interpreters:
> 
> #!/usr/bin/env python
> #!/usr/bin/env/ lua
^ that's not right :)

> #!/usr/bin/env perl
> 
> All references to node shebangs I can find on the internet converge on
> #!/usr/bin/env node which is why this issue prevents many npm packages to fail
> to run.
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> Creating a symlink as root: /usr/bin/node -> /usr/bin/nodejs solves the issue
> as far as I can tell.

Sounds like a perfect workaround.

> ln -s -T /usr/bin/nodejs /usr/bin/node && chmod 755 /usr/bin/node
> 
> A quick search of the Sid repositories doesn't show any conflicts with files
> installing to the path /usr/bin/node

Try the package: `node'. It's  not in /usr/bin, but it's on ${PATH}. In
fact, since you're using `env', it's double not clear.

> so doing the simple symlink within the
> Debian installer may be sufficient.

No way. There's a node-legacy package which does this. No need to
involve the installer.

>* What was the outcome of this action?
> Standard node scripts run correctly as the de-facto node shebang(
> #!/usr/bin/env node) now resolves to 'node' in the user's $PATH
> 
> I'm not very well clued on how this may affect other Debian packages, but 
> works
> in my little world, and this may extend further.
> 
>* What outcome did you expect instead?
> The expected behaviour is for the Debian package to install nodejs with a
> binary resolvable by the name supported by the node community and existing
> software, rather than with a name that refelects Node.js confusing
> project/binary naming schemes.  Potentially even better would be to support
> 'nodejs' and 'node', but plan to converge on '/usr/bin/node' for the future.
> 

As much as I disagree with ctte on this, I'm afraid that this won't
change. I'd close this, but I'll leave that for the maintainers of node
to do.

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature

Bug#734655: terminator fail to honor x-terminal-emulator -e syntax

[Julián Moreno Patiño]

severity 734655 normal
tags 734655 + moreinfo
thanks

Hello Dominnique,

Do you try it : terminator -e 'mc /home/dom' ?

Kind regards,

2014/1/8 Dominnique Michel :
> Package: terminator
> Version: 0.97-2
> Severity: serious
> Tags: upstream
> Justification: Policy 11.8.3
>
> # /usr/bin/terminator -e mc /home/dom
> Usage: terminator [options]
>
> terminator: error: Additional unexpected arguments found: ['/home/dom']
>
> That command should work as terminator claim to be a x-terminal-emulator.
>
>
>
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.12-1-amd64 (SMP w/1 CPU core)
> Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages terminator depends on:
> ii  gconf2  3.2.6-1
> ii  python-dbus 1.2.0-2+b1
> ii  python-gobject  3.10.2-1
> ii  python-gtk2 2.24.0-3+b1
> ii  python-vte  1:0.28.2-5
> pn  python:any  
>
> Versions of packages terminator recommends:
> ii  python-gnome2 2.28.1+dfsg-1
> ii  python-keybinder  0.3.0-2
> ii  python-notify 0.1.1-3
> ii  xdg-utils 1.1.0~rc1+git20111210-7
>
> terminator suggests no packages.
>
> -- no debconf information
>



-- 
Julián Moreno Patiño
Debian Developer
 .''`. Debian GNU/{Linux,KfreeBSD}
: :' : Free Operating Systems
`. `'  http://debian.org/
  `-   GPG Fingerprint:
C2C8 904E 314C D8FA 041D 9B00 D5FD FC15 6168 BF60
Registered GNU Linux User ID 488513


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

Bug#734656: nodejs: standard node shebang #!/usr/bin/env node fails in Debian as there is no binary/symlink named 'node' in $PATH

[luke]

Package: nodejs
Version: 0.10.24~dfsg1-1
Severity: grave
Tags: d-i
Justification: renders package unusable

Dear Maintainer,

Attempting to use many programs installed with `npm install` fails before
execution because the Node.js interpreter installed by dpkg/synaptic is not at
the expected path.  The node binary is named 'nodejs' on Debian, but the node
community expects the de-facto standard of '#!/usr/bin/env node'.

I understand this is a tricky issue, as Javascript was never really designed to
be run like a shell script, and does not have the heritage of many other Linux
shell languages.  Additionally, it is unclear from the Node.js project what the
official name of the binary should be. That said, here are the accepted
shebangs for some other interpreters:

#!/usr/bin/env python
#!/usr/bin/env/ lua
#!/usr/bin/env perl

All references to node shebangs I can find on the internet converge on
#!/usr/bin/env node which is why this issue prevents many npm packages to fail
to run.

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

Creating a symlink as root: /usr/bin/node -> /usr/bin/nodejs solves the issue
as far as I can tell.
ln -s -T /usr/bin/nodejs /usr/bin/node && chmod 755 /usr/bin/node

A quick search of the Sid repositories doesn't show any conflicts with files
installing to the path /usr/bin/node so doing the simple symlink within the
Debian installer may be sufficient.

   * What was the outcome of this action?
Standard node scripts run correctly as the de-facto node shebang(
#!/usr/bin/env node) now resolves to 'node' in the user's $PATH

I'm not very well clued on how this may affect other Debian packages, but works
in my little world, and this may extend further.

   * What outcome did you expect instead?
The expected behaviour is for the Debian package to install nodejs with a
binary resolvable by the name supported by the node community and existing
software, rather than with a name that refelects Node.js confusing
project/binary naming schemes.  Potentially even better would be to support
'nodejs' and 'node', but plan to converge on '/usr/bin/node' for the future.

FYI, I'm by no means a JavaScript guy, but I'm very happy to



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

Kernel: Linux 3.12-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nodejs depends on:
ii  libc-ares21.10.0-2
ii  libc6 2.17-97
ii  libgcc1   1:4.8.2-12
ii  libssl1.0.0   1.0.1f-1
ii  libstdc++64.8.2-12
ii  libv8-3.14.5  3.14.5.8-5
ii  zlib1g1:1.2.8.dfsg-1

nodejs recommends no packages.

nodejs 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#734565: mapserver: CVE-2013-7262

[Sebastiaan Couwenberg]

Hi Salvatore,

On 01/08/2014 10:09 AM, Salvatore Bonaccorso wrote:
> On Wed, Jan 08, 2014 at 08:40:35AM +0100, Sebastiaan Couwenberg wrote:
>> On 01/08/2014 08:25 AM, Salvatore Bonaccorso wrote:
>>> If you fix the vulnerability please also make sure to include the
>>> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
>>
>> The new mapserver packages were prepared before the CVE was available.

I've prepared new mapserver packages for squeeze and wheezy with only
the fix for this CVE, the new stable upstream release route I initially
took is not proper to fix this issue.

mapserver (6.0.1-3.2+deb7u2) for wheezy:

http://mentors.debian.net/debian/pool/main/m/mapserver/mapserver_6.0.1-3.2+deb7u2.dsc

mapserver (5.6.5-2+squeeze3) for squeeze:

http://mentors.debian.net/debian/pool/main/m/mapserver/mapserver_5.6.5-2+squeeze3.dsc

The squeeze package contained debhelper.log files in the debian/
directory, which caused problems for clean pbuilder builds so they were
removed. And dpatch insisted in changing the permissions. I've included
these changes in the squeeze package too.

>>> Please adjust the affected versions in the BTS as needed, at least
>>> unstable from looking at source seems affected.
>>
>> Unstable is no longer affect with the upload of mapserver 6.4.1, wheezy
>> and squeeze still are, but the proposed updates for both are waiting for
>> feedback from the release team:
> 
> Could you clarify if second commit referenced in
> 
> https://github.com/mapserver/mapserver/issues/4834
> (WFS-2 specific fixes for postgis time sql injections (#4834,#4815))
> 
> is also needed? Is this relevant for Debian?

No, the WFS-2 specific commit shouldn't be relevant for Debian yet.

The vulnerability was discovered during the implementation of WFS 2.0
support in MapServer. That support only lives in the master branch for
now and will be included in the next major upstream release.

> Thanks for your work, and regards,
> Salvatore

If the security-team approves the package changes, shall I ask my
sponsor to upload the packages?

Kind Regards,

Bas

-- 
GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old)


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

Bug#733521: Similar symptom on System76 Lemur Ultra

[Johan Gronqvist]

I see similar visual symptoms. On my laptop the hibernation procedure 
appears to write the image to disk for some (very reasonable amount of) 
time, and then freezes while still showing the desktop.


For me it also appeared with the upgrade from kernel 3.11 to 3.12, and I 
am using Jessie for almost all of my packages. Hibernation (by calling 
pm-hibernate) works fine if I boot the 3.11 kernel.


Both my swap and system partitions are luks-encrypted, and I also have a 
system76 laptop. I do not know what similarities or differences exist in 
hardware between my lemur ultra and the gazelle pro, but I can of course 
provide logs and other pieces of information if that would be helpful (I 
am not attaching any now, as I am unsure which ones might provide any 
additional value over those already provided by Russ).


I also see the problem with pm-suspend as described at 
, 
where it was reported for arch and ubuntu, and the solution proposed 
there was also a kernel downgrade.


Regards

Johan


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

Bug#733434: maven-plugin-testing: FTBFS: Missing required artifact: org.apache.maven.plugin-testing:maven-test-tools:jar:debian

[Roddy Shuler]

The problem is in 0002-fix-dependency-on-maven-test-tools.patch...

The version for maven-test-tools needs to be updated from 1.2 to 1.3 to
match what is being generated by the package.

Bug#734655: terminator fail to honor x-terminal-emulator -e syntax

[Dominnique Michel]

Package: terminator
Version: 0.97-2
Severity: serious
Tags: upstream
Justification: Policy 11.8.3

# /usr/bin/terminator -e mc /home/dom
Usage: terminator [options]

terminator: error: Additional unexpected arguments found: ['/home/dom']

That command should work as terminator claim to be a x-terminal-emulator.



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.12-1-amd64 (SMP w/1 CPU core)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages terminator depends on:
ii  gconf2  3.2.6-1
ii  python-dbus 1.2.0-2+b1
ii  python-gobject  3.10.2-1
ii  python-gtk2 2.24.0-3+b1
ii  python-vte  1:0.28.2-5
pn  python:any  

Versions of packages terminator recommends:
ii  python-gnome2 2.28.1+dfsg-1
ii  python-keybinder  0.3.0-2
ii  python-notify 0.1.1-3
ii  xdg-utils 1.1.0~rc1+git20111210-7

terminator 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#711604: Hash randomization test failures

[Dominic Hargreaves]

On Sun, Jan 05, 2014 at 06:15:20PM +, Dominic Hargreaves wrote:
> On Sun, Jan 05, 2014 at 06:03:45PM +, Dominic Hargreaves wrote:
> > On Sun, Jan 05, 2014 at 07:10:46PM +0200, Niko Tyni wrote:
> > > Also, at the risk of stating the obvious: I don't think we can tell
> > > whether a build failure is caused by functional breakage or just test
> > > suite fragility without looking at the code, right? The code could
> > > actually be relying on the old hash behaviour, and that could cause very
> > > similar sporadic test suite failures.
> > 
> > Yes, absolutely. From the packages I've looked at it's generally fairly
> > obvious if the breakage is caused by assumptions in the test suite, though,
> > as opposed to in the functional code.
> > 
> > > > #711428 libcgi-application-plugin-authentication-perl
> > > > #711436 libdbix-abstract-perl
> > > > #711444 libgraph-readwrite-perl
> > > > #711446 libgraph-writer-graphviz-perl
> > > > #711604 libmime-lite-html-perl
> > > > #711614 libscriptalicious-perl
> > > > #711615 libsearch-estraier-perl
> > > > #720018 libhtml-wikiconverter-moinmoin-perl
> > > > #720271 libnet-jabber-perl
> 
> So this package needs to be checked to see whether the test failures
> are definitely random, and that the random breakage is purely in the test
> suite. If so, the severity of this bug can be downgraded to important.

This doesn't seem to be the case here; this package fails to build
for me 12 times in a row. Updating the package to 1.24 (which looks
like it would be a worthwhile update anyway) doesn't change anything.
And I've just re-verified that the package does build on wheezy.

This is currenly keeping sympa out of testing.

Cheers,
Dominic.


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

Bug#692460: TIFFAppendToStrip: Maximum TIFF file size exceeded

[Jay Berkenbilt]

Mathieu Malaterre  wrote:

> Package: libtiff-tools
> Version: 4.0.2-4
> Severity: important

Your bug report says 4.0.2-4, but later, you have

> -- System Information:
> Debian Release: 6.0.6
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable'), (200,
> testing'), (100, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.2.0-0.bpo.3-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages libtiff-tools depends on:
> ii  libc6   2.11.3-4 Embedded GNU C Library: Shared 
> lib
> ii  libjpeg62   6b1-1The Independent JPEG Group's 
> JPEG 
> ii  libtiff43.9.4-5+squeeze5 Tag Image File Format (TIFF) 
> libra
> ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime
>
> libtiff-tools recommends no packages.
>
> Versions of packages libtiff-tools suggests:
> pn  libtiff-opengl (no description available)
>
> -- no debconf information

Are you sure this is still true with the latest tiff2rgba?  The version
that reportbug thinks you have predates bigtiff support.

-- 
Jay Berkenbilt 


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

Bug#734654: loook: fails to run with LANG=C

[Matthias Ferdinand]

Package: loook
Version: 0.7.2-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

 any invocation, even "loook -h"

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

 using with LANG=C (or empty LANG)

   * What was the outcome of this action?

Traceback (most recent call last):
  File "/usr/bin/loook", line 472, in 
g = TranslationIntegration(loookversion)
  File "/usr/bin/loook", line 397, in __init__
_result = self.look4mo(_localepath)
  File "/usr/bin/loook", line 424, in look4mo
_lpath = localepath + self.language + "/LC_MESSAGES/" + self.moname
TypeError: Can't convert 'NoneType' object to str implicitly



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.11-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages loook depends on:
ii  python3 3.3.2-17
ii  python3-tk  3.3.3-2

Versions of packages loook recommends:
ii  libreoffice  1:4.1.4-2

loook suggests no packages.

-- debconf-show failed


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

Bug#734614: [Debian-med-packaging] Bug#734614: [gwyddion] impossible execute gwyddion

[Jan Beyer]

Dear Marco,

thank you for the bug report. It is actually already reported and known
upstream (see
http://sourceforge.net/mailarchive/message.php?msg_id=31756867) and a quick
fix is to start gwyddion with english language. Upstream has already
released a patch, but I did not yet find the time to release an updated
Debian revision. I will try to give this higher priority on my todo-list.
I'm sorry for the delay.

Best regards,
Jan

Und es begab sich am 08.01.2014 16:33, dass Marco Righi schrieb:
> Package: gwyddion
> Version: 2.34-1
> Severity: grave
> 
> --- Please enter the report below this line. ---
> the "gwyddion" execution provide the following output:
> 
> 
> gwyddion:17274): GwyApp-CRITICAL **: gwy_app_menu_resolve_translations:
> assertion `p' failed
> Errore di segmentazione
> 
> where "Errore di segmentazione" is a segmentation error.
> 
> --- System information. ---
> Architecture: amd64
> Kernel:   Linux 3.11-2-amd64
> 
> Debian Release: jessie/sid
>   500 testing www.deb-multimedia.org
>   500 testing security.debian.org
>   500 testing http.us.debian.org
>   500 testing ftp2.de.debian.org
>   500 testing ftp.it.debian.org
>   500 testing ftp.deb-multimedia.org
>   500 testing apt.jenslody.de
>   500 stable  repo.wuala.com
>   500 stable  apt.spideroak.com
>   500 oneiric ppa.launchpad.net
>   500 debian  packages.linuxmint.com
> 
> --- Package information. ---
> Depends   (Version) | Installed
> ===-+-==
> libatk1.0-0 (>= 1.12.4) |
> libc6 (>= 2.14) |
> libcairo2(>= 1.2.4) |
> libfftw3-double3|
> libfontconfig1(>= 2.11) |
> libfreetype6 (>= 2.2.1) |
> libgcc1(>= 1:4.1.1) |
> libgdk-pixbuf2.0-0  (>= 2.22.0) |
> libgl1-mesa-glx |
>  OR libgl1  |
> libglib2.0-0(>= 2.24.0) |
> libglu1-mesa|
>  OR libglu1 |
> libgtk2.0-0 (>= 2.24.0) |
> libgtkglext1|
> libgtksourceview2.0-0   (>= 2.10.0) |
> libgwyddion2-0  (>= 2.34-1) |
> libice6(>= 1:1.0.0) |
> libpango-1.0-0  (>= 1.14.0) |
> libpangocairo-1.0-0 (>= 1.14.0) |
> libpangoft2-1.0-0   (>= 1.14.0) |
> libpangox-1.0-0  (>= 0.0.2) |
> libpng12-0(>= 1.2.13-4) |
> libpython2.7   (>= 2.7) |
> libsm6  |
> libstdc++6   (>= 4.1.1) |
> libx11-6|
> libxml2  (>= 2.7.4) |
> libxmu6 |
> libxt6  |
> zlib1g (>= 1:1.1.4) |
> gwyddion-common  (= 2.34-1) |
> 
> 
> Package's Recommends field is empty.
> 
> Suggests  (Version) | Installed
> ===-+-===
> gwyddion-plugins| 2.34-1
> 
> 
> 
> 
> 
> 


-- 
Jan Beyer   happy Debian Maintainer ;-) 

mailj...@beathovn.deGPG key ID 0x0CA6B4AA
jabber  beath...@jabber.org
web http://www.beathovn.de/


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

Bug#734653: RFP: lighttable -- Cross-platform interactive IDE with real time feedback

[Jérémy Lal]

Package: wnpp
Severity: wishlist

* Package name: lighttable
  Version : 0.6.0
  Upstream Author : Chris Granger 
* URL : http://www.lighttable.com/
* License : GPL-3
  Programming Lang: Clojure
  Description : Cross-platform interactive IDE with real time feedback

Light Table is a new kind of IDE with a unique user interface,
a reactive work surface for the creation and exploration of our
programs. Highlighted features are:
 * Documentation everywhere
 * Real-time code evaluation and visualization
 * Organize code around functions
 * Automatic refactorisation while typing
 * Plugins support
It supports Clojure and Javascript languages, and is meant to
support more languages in the future.


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

Bug#731345: Kirkwood Kernel 3.12-1

[Ian Campbell]

On Wed, 2014-01-08 at 09:23 +, Ian Campbell wrote:
> Yes, thinking about it "DTB-After: version" probably makes more
> logical sense. 

Hi Marc,

Please can you try this flash-kernel patch on your SheevaPlug?

I've tried it on a ts-419 with Andrew Lunn's DTB patches for that
platform and in some basic tests it seems fine but the Sheevaplug
specific runes need validating.

I'm going to run a more complete set of combinations too, so where for
me 3.13 needs DTB appended and 3.12 I intend to test:

Installing 3.12 while running 3.12 (reran flash-kernel manually)
Installing 3.13 while running 3.13 (reran flash-kernel manually)
Installing 3.12 while running 3.13 (dpkg --purge linux-image-3.13...)
Installing 3.13 while running 3.12 (dpkg -i linux-image-3.13...)

If you could do something similar for the Sheeva case that would be
awesome.

Ian.


8<-

>From c0543194c1fae562fa4c8042aa7ff4e37a49e970 Mon Sep 17 00:00:00 2001
From: Ian Campbell 
Date: Thu, 2 Jan 2014 14:40:39 +
Subject: [PATCH] Support requirement to append a DTB on Sheevaplug from kernel
 v3.12 onwards

We want to support both flashing a new (DT based) kernel while running an old
(board file based) kernel as well as flashing an old kernel while running a new
(which normally corresponds to removing a new kernel package).

Therefore add two db entries, one which matches the old board file based
platform and one wich matches the new DT based platform.

We also need to know which kernels need the DTB. We cannot just append the DTB
and rely on the old kernels ignoring it because at least some older kernels
will malfunction if given an appended DTB while they would function fine with
their built in board support. Therefore introduce a new db field
"DTB-Append-From" which is compared against the kernel we are flashing to
determine if the DTB should be appended.

DTB-Append and DTB-Append-From now override/mask Machine-ID since DTB based
systems do not use Machine-ID.

Closes: #731345.
---
 README   |  8 +++-
 db/all.db| 15 +++
 debian/changelog |  7 +++
 functions| 23 ---
 test_db  |  2 +-
 test_functions   | 17 +
 6 files changed, 63 insertions(+), 9 deletions(-)

diff --git a/README b/README
index 674a88a..6093d78 100644
--- a/README
+++ b/README
@@ -92,13 +92,19 @@ The supported fields are:
   suffix, installation is aborted
 
 * Machine-Id: (optional) linux mach-type to set before starting vmlinuz;
-  will be set by a small piece of ARM code prepended to the kernel image
+  will be set by a small piece of ARM code prepended to the kernel image.
+  This option is ignored if a DTB is to be appended, via either DTB-Append or
+  DTB-Append-From.
 
 * DTB-Id: (optional) specifies the name of the DTB file for this device
 
 * DTB-Append: (optional) when yes the DTB specified by DTB-Id will be appended
   to the kernel image.
 
+* DTB-Append-From: (optional): Can be used instead of DTB-Append. The argument
+  is a kernel version, if the kernel to be installed is at least this version
+  then the DTB specified named by DTB-Id will be appended to the kernel image.
+
 * U-Boot-Kernel-Address, U-Boot-Kernel-Entry-Point, U-Boot-Initrd-Address:
   (optional) address where to load in (physical) RAM the kernel, entry point
   and initrd, respectively; this also indicates that U-Boot images should be
diff --git a/db/all.db b/db/all.db
index 76e99fd..b62f821 100644
--- a/db/all.db
+++ b/db/all.db
@@ -250,10 +250,25 @@ Bootloader-Sets-Root: no
 
 Machine: Marvell SheevaPlug Reference Board
 Kernel-Flavors: kirkwood
+DTB-Id: kirkwood-sheevaplug.dtb
+DTB-Append-From: 3.12
 U-Boot-Kernel-Address: 0x8000
 U-Boot-Initrd-Address: 0x0
 Boot-Kernel-Path: /boot/uImage
 Boot-Initrd-Path: /boot/uInitrd
+Boot-DTB-Path: dtb
+Required-Packages: u-boot-tools
+Bootloader-Sets-Root: no
+
+Machine: Globalscale Technologies SheevaPlug
+Kernel-Flavors: kirkwood
+DTB-Id: kirkwood-sheevaplug.dtb
+DTB-Append-From: 3.12
+U-Boot-Kernel-Address: 0x8000
+U-Boot-Initrd-Address: 0x0
+Boot-Kernel-Path: /boot/uImage
+Boot-Initrd-Path: /boot/uInitrd
+Boot-DTB-Path: dtb
 Required-Packages: u-boot-tools
 Bootloader-Sets-Root: no
 
diff --git a/debian/changelog b/debian/changelog
index f9654c1..716606d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+flash-kernel (3.12) UNRELEASED; urgency=low
+
+  * Append a DTB on Sheevaplug from kernel version 3.12 onwards. Based on a
+patch by Marc Kleine-Budde. (Closes: #731345).
+
+ -- Ian Campbell   Wed, 08 Jan 2014 19:55:43 +
+
 flash-kernel (3.11) unstable; urgency=low
 
   [ Updated translations ]
diff --git a/functions b/functions
index 66e9738..d75f139 100644
--- a/functions
+++ b/functions
@@ -319,6 +319,10 @@ abootimg_get_image_size() {
echo "$abootimg" | sed -rn 's/^\* image size = ([0-9]+) bytes.*/\1/p'
 }
 
+dtb_append_required() {
+   linux-version compare "$kvers" ge "$dtb_appe

Bug#720143: {tcl,tk}8.5: leaves alternatives after purge: /usr/bin/tclsh, /usr/bin/wish

[Matthias Klose]

the removal is done in tcltk-defaults from experimental.

$ cat tcl.preinst
#!/bin/sh

set -e

case "$1" in
install|upgrade)
# Currently the alternatives mechanism is not used
if dpkg --compare-versions "$2" lt-nl "8.6.0+2"; then
update-alternatives --remove-all tclsh || true
fi
;;
[...]

I assume this works good enough in practice, but fails when a versioned tcl8.x
was installed without the tcl package installed. same for tk.

  Matthias


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

Bug#734650: transition: perl 5.18.2

[Niko Tyni]

On Wed, Jan 08, 2014 at 10:52:00PM +0200, Niko Tyni wrote:

> Perl 5.18.2 was released on Monday. This is an ABI-compatible maintenance
> release, see the upstream policy at
>  
> http://search.cpan.org/~jesse/perl-5.14.0/pod/perlpolicy.pod#MAINTENANCE_BRANCHES

Sorry, that should of course have been
 
http://search.cpan.org/~rjbs/perl-5.18.2/pod/perlpolicy.pod#MAINTENANCE_BRANCHES

The only change in this section since 5.14.0 is:

+Patches that fix regressions in perl's behavior relative to previous
+releases are acceptable.

-- 
Niko Tyni   nt...@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#734392: Error: Can't connect to unix socket

[Paul Gevers]

Slight progress:

paul@wollumbin ~ $
SPEECHD_ADDRESS=unix_socket:/home/paul/.cache/speech-dispatcher/speechd.sock
spd-say hello
works. Also the following python works out of the box:

paul@wollumbin ~ $ python3
Python 3.2.3 (default, Feb 20 2013, 14:44:27)
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import speechd
>>> client = speechd.SSIPClient('test')
>>> client.speak("Hello World!")
# pause here
>>> client.close()

I don't understand yet, but it seems that the files of speech-dispatcher
on my system are scattered over:
~/.cache/speech-dispatcher
~/.config/speech-dispatcher
and
~/.speech-dispatcher
and they don't work together.

@ Jarek, please confirm that the .cache folder contains the logging you
were searching

Paul



signature.asc
Description: OpenPGP digital signature

Bug#734164: console-data: should conflict with console-setup

[Anton Zinoviev]

reassign 734164 console-data
retitle 734164 The package doesn't make obvious to the users that it is 
deprecated in favour of console-setup
thanks

On Sun, Jan 05, 2014 at 08:38:32AM +0100, Christian PERRIER wrote:
>
> Well, that's long overdue. A way to really get rid of c-d is probably
> to have c-s add Breaks and Provides so that it can smoothly replace
> c-d...but that's a job for console-setup, not console-data, indeed.

I don't agree.  C-s doesn't break console-data, nor does it provide all 
of the functionality of c-d.  C-s can be configured to omit the font 
and/or keymap configuration in which case c-d can do this or c-s can be 
configured to use the fonts and/or keymaps of c-d.

> Some may argue that c-d provides a few very exotic (or obsolete)
> keymaps and maybe console fonts, that console-setup doesn't
> provide.but the number of affected users is probably very very
> close to zero nowadays.

I agree.  I am not against removing c-d.  What I don't like is to abuse 
'Breaks' and 'Provides' inapropriately.  We must not force our way to 
the users, they have the right to install c-d even if the package is 
removed from the archive.  The number of the affected users may be close 
to zero but it is definitely not zero.

BTW, on my computers I am using packages from old Debian releases that 
are no longer available.

Anton Zinoviev


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

Bug#636568: uploading xerces-c with PATH_MAX patch

[Jay Berkenbilt]

Sorry, this fell off my radar for six months.  I was reviewing open bugs
on my packages and realized this one was trivial, so I uploaded a fix.

-- 
Jay Berkenbilt 


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

Bug#733271: missing test files

[Alexandre Gramfort]

hi,

do you have any idea why this happens? these files are excluded from
the manifest to avoid
a huge upload to pypi but could be shipped on debian. Any idea how to fix this?

thanks
Alex


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

Bug#734651: libmodule-corelist-perl: new upstream version needed for Perl 5.18.2

[Niko Tyni]

Package: libmodule-corelist-perl
Version: 3.02-1
Severity: important
x-debbugs-cc: p...@packages.debian.org

I've just uploaded perl_5.18.2-1 to experimental, Breaking
libmodule-corelist-perl (<< 3.03). So this package needs to be updated,
otherwise it becomes uninstallable when 5.18.2 enters sid.
-- 
Niko Tyni   nt...@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#733270: mne python doc package

[Alexandre Gramfort]

I'll try to add it soon. Any help welcome though :)

cheers,
Alex


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

Bug#733865: [Pkg-xen-devel] Bug#733865: Bug#733865: xen-utils-4.3: qemu-dm is not executable: No such file or directory

[Ian Campbell]

On Mon, 2014-01-06 at 05:29 -0600, Marc F. Clemente wrote:
> On 01/02/2014 11:56 AM, Ian Campbell wrote:
> > You can select a non-default model use by using the
> > "device_model_version" directive in your config.
> 
>  From what I gather, for now, you MUST select a non-default model, using 
> something like:
> 
> device_model_version="qemu-xen"
> device_model_override="/usr/bin/qemu-system-x86_64"

Yes, I think so. Not sure what the default path is, but it probably
isn't correct so the override is appropriate.

> > In the context of Debian the Debian Xen maintainer has been trying to
> > move away from the traditional fork for several releases. Historically
> > the traditional qemu was shipped with the Xen utils in but in some
> > release (Wheezy? Maybe Squeeze?) it was removed and ended up packaged
> > separately as a separate xen-qemu-dm-4.0 package in order to keep things
> > working. In Jessie even that is gone. Luckily however the upstream qemu
> > package in Jessie already supports Xen so you should be able to simply
> > select that in your configuration.
> 
> So "traditional" disappeared when Debian's xen went from 4.1 to 4.2.

IIRC it was removed from the package when Debian's xen went to 4.0, but
re-added as a separate source package. Then when Debian's Xen went to
4.1 it was reenabled in the main Xen package and the separate source
package was obsoleted. Then it went away again with the 4.2 packages.

> > So, things are a bit in flux right now but will be sorted by the time
> > Jessie is actually released. The fact that the Xen tools in 4.3 still
> > default to qemu-traditional which is not present is a bit unfortunate
> > but with Xen 4.4 due to be released in the next 4-6 weeks with a default
> > of qemu-upstream this will take care of itself sooner rather than later.
> > Xen 4.4 also includes support for compiling without qemu-traditional
> > support which will improve the error message should you try to use it
> > (either inadvertently as you have done here or deliberately).
> 
> Is it, or will it be possible for me to build xen 4.3 or 4.4 WITH 
> "traditional"?

It ought to be possible, the upstream release still includes it so you
could download it and give it a try, I've never done it myself.

You might find the Squeeze era xen-qemu-dm-4.0 source package
illustrative.

> 
> >> Is it possible to do HVM with Debian?
> >
> > It should be, although as I say it may be in flux a bit.
> 
> My problem is that I was doing HVM with xen 4.1.  I had MS Windows XP, 7 
> and 8 virtual machines.  I had VGA and PCI passthrough working just 
> fine.  I tried using xen 4.2, but I was unable to do VGA passthrough. 
> With 4.3, I can't even do PCI passthrough.  It says that my Intel 5500 
> chipset is buggy (Intel errata #53), and disables IOMMU.  Maybe my 
> chipset is buggy...  But it is rock-solid stable when I do HVMs with VGA 
> passthrough using xen 4.1.

There have been various IOMMU issues relating to buggy hardware where
"buggy" is not stability but rather security related. The one I can
think of immediately was XSA-36 but that was an AMD thing IIRC, and you
are using Intel. I'm pretty sure there were Intel ones too.

Check the list of XSAs (Xen Security Announcements) if one of them
appears related then the text will describe what the security issue was
you can make a determination if it is an issue which affects you -- and
from there I think it will also explain how to turn it back on if you
think you are safe (or you could check the Xen command line option
docs).

> I wonder if anybody else shares my experience...

WTR the IOMMU disabling due to security issue, loads, I'm sure google
will find them.

Ian.


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

Bug#713877: udev: cd drive does not generate events

[Christoph Pfister]

udev on my up-to-date debian testing system does not generate any
event when I open the drive tray, insert a media and close the tray
again:

> lxuser@debian:~$ udevadm monitor
> monitor will print the received events for:
> UDEV - the event which udev sends out after rule processing
> KERNEL - the kernel uevent
>

which is pretty annoying. Adding the rule from comment #25 avoids the problem:

> lxuser@debian:~$ udevadm monitor
> monitor will print the received events for:
> UDEV - the event which udev sends out after rule processing
> KERNEL - the kernel uevent
>
> KERNEL[37.344854] change   
> /devices/pci:00/:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 
> (block)
> UDEV  [40.918624] change   
> /devices/pci:00/:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 
> (block)
> KERNEL[49.120679] change   
> /devices/pci:00/:00:11.0/ata2/host1/target1:0:0/1:0:0:0> /block/sr0 
> (block)
> KERNEL[52.632667] change   
> /devices/pci:00/:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 
> (block)
> UDEV  [52.639049] change   
> /devices/pci:00/:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 
> (block)
> UDEV  [52.689831] change   
> /devices/pci:00/:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sr0 
> (block)

Thanks,

Christoph


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

Bug#734650: transition: perl 5.18.2

[Niko Tyni]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: p...@packages.debian.org

Perl 5.18.2 was released on Monday. This is an ABI-compatible maintenance
release, see the upstream policy at
 
http://search.cpan.org/~jesse/perl-5.14.0/pod/perlpolicy.pod#MAINTENANCE_BRANCHES

I've just uploaded perl_5.18.2-1 to experimental. Dominic is going to
run a test rebuild of at least the perl related packages next, but we
don't expect regressions.

Affected packages that we know of are (hope I got this right)

 is_affected: ".depends ~ /perl \(<< 5\.18/"
 bad:  ".depends ~ /perl \(<< 5\.18\.2/"
 good: ".depends ~ /perl \(<< 5\.18\.3/"

which would currently yield

 nmu libpar-packer-perl_1.017-1 . ALL . -m 'rebuild for Perl 5.18.2'
 nmu libdevel-cover-perl_1.08-1 . ALL . -m 'rebuild for Perl 5.18.2'
 nmu libclass-xsaccessor-perl_1.19-1 . ALL . -m 'rebuild for Perl 5.18.2'
 nmu libcommon-sense-perl_3.72-2 . ALL . -m 'rebuild for Perl 5.18.2'

Additionally, libmodule-corelist-perl will need a source upload
to upgrade to at least 3.03.

Thanks for your work,
-- 
Niko Tyni   nt...@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#733162: mirror submission for mirror.trueinter.net

[Roberto Saavedra - [ inAsset Networks ]]

Hello Simon,Should we do anything else on our part to complete the registration of our Mirror server?Thanks.  Regards,
Roberto Saavedra - [ inAsset Networks ]P : +34 683 422 390F : +34 911 701 242E-mail : 		r...@inasset.es / r...@trueinter.netWe deliver True InternetFacebook :	https://facebook.com/inassetTwitter :		https://twitter.com/inassetnetworks

El 26/12/2013, a las 17:12, Roberto Saavedra - [ inAsset Networks ]  escribió:Hello Simon,Role contact could be either ad...@inasset.es or n...@inasset.es
Could you please indicate how to proceed for push-mirroring with ftp.de.mirror.org?  We have been reading the documentation, and would like to know if we should open an account at the mirror server for ftp.de.mirror.org, or initiate communication with them for the setup.Thanks.  Regards,Roberto Saavedra - [ inAsset Networks ]P : +34 683 422 390F : +34 911 701 242E-mail : 		r...@inasset.es / r...@trueinter.netWe deliver True InternetFacebook :	https://facebook.com/inassetTwitter :		https://twitter.com/inassetnetworks

El 26/12/2013, a las 11:37, Simon Paillard  escribió:Hi there,On Thu, Dec 26, 2013 at 03:43:31PM +, Roberto Saavedra wrote:Package: mirrorsSeverity: wishlistSubmission-Type: newSite: mirror.trueinter.netType: leafArchive-architecture: ALL amd64 armel armhf hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390x sparc Archive-ftp: /debian/Archive-http: /debian/Archive-rsync: debian/CDImage-ftp: /debian-cd/CDImage-http: /debian-cd/CDImage-rsync: debian-cd/IPv6: yesArchive-upstream: ftp.de.debian.orgCDImage-upstream: ftp.de.debian.orgUpdates: twiceMaintainer: Roberto Saavedra Can you provide us a role contact like ad...@inasset.es so that we can reachsomebody when you're away ?Country: ES SpainLocation: MadridSponsor: inAsset Networks http://www.inasset.esBest regards.-- Simon Paillard

signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#710129: [Pkg-bluetooth-maintainers] Bug#732453: bluez: New upstream release 5.12

[Szymon Janc]

Hi,

On Wednesday 08 January 2014 12:20:11 Fabian Greffrath wrote:
> Am Mittwoch, den 08.01.2014, 15:14 +0900 schrieb Nobuhiro Iwamatsu:
> > Because KDE (bluedevil) does not support Bluez5 yet.
> > Arch has been distributed in the separate package to bluez5 and bluez4
> > the Bluez solve this problem, but this is not possible with Debian.
> 
> I see. The corresponding bug report in Debian #710129 has not been
> answered since May 2013, but according to the Fedora Wiki [1] there is a
> GIT branch of bluedevil that supports Bluez5. Maybe that could be
> packaged in Debian or uploaded via NMU if nothing else happens?

FYI http://www.afiestas.org/bluedevil-2-0-rc1-a-k-a-bluez5-ready/

-- 
Szymon K. Janc
szymon.j...@gmail.com


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

Bug#733489: python-apt: Improve 'Dependency' and 'BaseDependency' to get target package versions that satisfy dependencies

[Michael Schaller]

Julian, another question regarding this change...
Do you have any problems with changing the constructor of 
apt.package.BaseDependency?


I would like it to change it so that it only takes a apt_pkg.Dependency 
object as argument. As far as I see it the constructor is not documented 
and so I would assume that the constructor is not part of the public 
API. Am I correct?



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