Bug#822932: golang-golang-x-net-dev: please update to latest upstream snapshot

[Potter, Tim (HPE Linux Support)]

Package: golang-golang-x-net-dev
Severity: wishlist
X-Debbugs-CC: pkg-go 

Please upload the latest release of the golang-golang-x-net-dev package,
1:0.0+git20160413.0.fb93926.  I've already packaged this in the repo on alioth.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#822945: dbconfig-common: enable calling packages to know the error state, e.g. by declaring _dbc_on_error_option external

[Paul Gevers]

Package: dbconfig-common
Version: 2.0.4~bpo8+1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Packages that depend on dbconfig may want to know what the exit state
is. E.g. cacti is running code that requires the correct setup via
dbconfig. However, if the admin asked dbconfig to ignore installation errors or
in noninteractive fail mode, also the package calling dbconfig could respect
that wish from the admin. A package could use _dbc_on_error_option for that,
but as can be seen by the underscore, that variable is considered internal.

Once implemented, this should also be documented.

- -- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (60, 'unstable'), (50, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-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
Init: systemd (via /run/systemd/system)

Versions of packages dbconfig-common depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  ucf3.0030

dbconfig-common recommends no packages.

Versions of packages dbconfig-common suggests:
ii  dbconfig-mysql  2.0.4~bpo8+1

- -- debconf information excluded

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJXIySnAAoJEJxcmesFvXUKvYcIAKUaDmr7nFAHrA2tduvguTS3
Lb0dAQgwReArIuwAya2gqAbK5JHqHM7R+ZgAMJ2S0RTdaZGqUnvr82M1rWhqwkn0
IuSDgjJnFo6QZFADI0huoEUKqsK64q5qx0p9yPfXuQsJZrGKhT0Lfz+KfURyNb3F
XkSLO3wrGqWtgw9UMImpjk0Y2dRRv9SulzWCG/9DGfL1B2gvPOPhFez5fWPAcZYM
vLN//eU9eJE9CzO+gMdAlWV45QWn5zkd1pFqmilwpm+bbcr1s+S7/4mDqh9tEa02
pmicWs3bxWv+6rqEStjaIexAF1ktiQyG6N+z+5xQpPzrezqT1oJieT/HuuqrLfA=
=G2HG
-END PGP SIGNATURE-

Bug#822948: shotwell: please make the build reproducible (timestamps, umask)

[Alexis Bienvenüe]

Source: shotwell
Version: 0.22.0-4
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps umask
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

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

The attached patch fixes date handling (tar needs an English date in
--mtime) and fixes files mode in the temp-source archive. Once
applied, shotwell can be built reproducibly in our current experimental
framework.

Regards,
Alexis Bienvenüe.

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




diff -Nru shotwell-0.22.0/debian/changelog shotwell-0.22.0/debian/changelog
--- shotwell-0.22.0/debian/changelog	2016-03-21 13:15:42.0 +0100
+++ shotwell-0.22.0/debian/changelog	2016-04-29 11:10:27.0 +0200
@@ -1,3 +1,10 @@
+shotwell (0.22.0-4.0~reproducible1) UNRELEASED; urgency=medium
+
+  * Fix date handling for non-English locales
+  * Fix files mode in temp-source tarball
+
+ -- Alexis Bienvenüe   Fri, 29 Apr 2016 08:57:37 +0200
+
 shotwell (0.22.0-4) unstable; urgency=medium
 
   * New debian/patches/0100-ios8.patch (Closes: #792016):
diff -Nru shotwell-0.22.0/debian/rules shotwell-0.22.0/debian/rules
--- shotwell-0.22.0/debian/rules	2015-11-03 11:57:14.0 +0100
+++ shotwell-0.22.0/debian/rules	2016-04-29 11:10:09.0 +0200
@@ -5,7 +5,7 @@
 export VALAFLAGS:=$(foreach w,$(CPPFLAGS) $(CFLAGS) $(LDFLAGS),-X $(w))
 
 CHDATE:=$(shell dpkg-parsechangelog --show-field=Date)
-B_DATE:=$(shell date -d "$(CHDATE)")
+B_DATE:=$(shell LC_ALL=C date --utc -d "$(CHDATE)")
 
 %:
 	dh $@
@@ -21,8 +21,7 @@
 	mkdir -p debian/shotwell-dbg/usr/share/doc/shotwell-dbg/temp-source
 	find -type f -name '*.c' -exec cp --parent '{}' debian/shotwell-dbg/usr/share/doc/shotwell-dbg/temp-source/ ';'
 	cd debian/shotwell-dbg/usr/share/doc/shotwell-dbg && \
-	find . -newermt '$(B_DATE)' -print0 | xargs -0r touch --no-dereference --date='$(B_DATE)' && \
-	tar --mtime="$(B_DATE)" -cJf temp-source.tar.xz temp-source
+	tar --mode=go=rX,u+rw,a-s --mtime="$(B_DATE)" -cJf temp-source.tar.xz temp-source
 	rm -fr debian/shotwell-dbg/usr/share/doc/shotwell-dbg/temp-source
 
 override_dh_installchangelogs:

Bug#822416: Install LVM with Free PE, partman-?????

[Philip Hands]

Philipp Kern  writes:

> On 2016-04-24 09:18, Geert Stappers wrote:
>> | Install a starting point.
>> | More complicated configuration can be done on the installed system.
>> | KISS
>
>> Keep It Simple
>
> There is also the inverse direction here: The user will be confused as 
> to why so much of the drive's capacity is missing and needs to resort to 
> not so simple and potentially destructive tooling to rectify the 
> situation. That's not really simple either, right?
>
> Not really arguing for one way or another, but one sysadmin's KISS is 
> another user's WTF. :)

Yes, but a vast /home is pretty-much never what anyone wants.

People that are confused by the lack of allocated LVM space will also be
confused when /var fills on their 5TB disk whether there's LVM involved
or not -- at least there's some chance of them being able to make the
filled FS bigger if we've not already eaten all the spare capacity for them.

We could always point at the release notes in the installer, and explain
that the disk will not be fully pre-allocated for LVM installs.

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#822942: felix-main: FTBFS: the artifact org.apache.felix:org.apache.felix.bundlerepository:jar:2.0.6 has not been downloaded

[Chris Lamb]

Source: felix-main
Version: 5.0.0-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

felix-main fails to build from source in unstable/amd64:

  [..]

  Adding debian:COMODO_RSA_Certification_Authority.pem
  Adding debian:Camerfirma_Chambers_of_Commerce_Root.pem
  Adding debian:Camerfirma_Global_Chambersign_Root.pem
  Adding debian:Certification_Authority_of_WoSign_G2.pem
  Adding debian:Certigna.pem
  Adding debian:Certinomis_-_Autorité_Racine.pem
  Adding debian:Certinomis_-_Root_CA.pem
  Adding debian:Certplus_Class_2_Primary_CA.pem
  Adding debian:Certum_Root_CA.pem
  Adding debian:Certum_Trusted_Network_CA.pem
  Adding debian:Chambers_of_Commerce_Root_-_2008.pem
  Adding 
debian:China_Internet_Network_Information_Center_EV_Certificates_Root.pem
  Adding debian:ComSign_CA.pem
  Adding debian:Comodo_AAA_Services_root.pem
  Adding debian:Comodo_Secure_Services_root.pem
  Adding debian:Comodo_Trusted_Services_root.pem
  Adding debian:Cybertrust_Global_Root.pem
  Adding debian:D-TRUST_Root_Class_3_CA_2_2009.pem
  Adding debian:D-TRUST_Root_Class_3_CA_2_EV_2009.pem
  Adding debian:DST_ACES_CA_X6.pem
  Adding debian:DST_Root_CA_X3.pem
  Adding debian:Deutsche_Telekom_Root_CA_2.pem
  Adding debian:DigiCert_Assured_ID_Root_CA.pem
  Adding debian:DigiCert_Assured_ID_Root_G2.pem
  Adding debian:DigiCert_Assured_ID_Root_G3.pem
  Adding debian:DigiCert_Global_Root_CA.pem
  Adding debian:DigiCert_Global_Root_G2.pem
  Adding debian:DigiCert_Global_Root_G3.pem
  Adding debian:DigiCert_High_Assurance_EV_Root_CA.pem
  Adding debian:DigiCert_Trusted_Root_G4.pem
  Adding debian:E-Tugra_Certification_Authority.pem
  Adding debian:EBG_Elektronik_Sertifika_Hizmet_Sağlayıcısı.pem
  Adding debian:EC-ACC.pem
  Adding debian:EE_Certification_Centre_Root_CA.pem
  Adding debian:Entrust.net_Premium_2048_Secure_Server_CA.pem
  Adding debian:Entrust_Root_Certification_Authority.pem
  Adding debian:Entrust_Root_Certification_Authority_-_EC1.pem
  Adding debian:Entrust_Root_Certification_Authority_-_G2.pem
  Adding debian:Equifax_Secure_CA.pem
  Adding debian:Equifax_Secure_Global_eBusiness_CA.pem
  Adding debian:Equifax_Secure_eBusiness_CA_1.pem
  Adding debian:GeoTrust_Global_CA.pem
  Adding debian:GeoTrust_Global_CA_2.pem
  Adding debian:GeoTrust_Primary_Certification_Authority.pem
  Adding debian:GeoTrust_Primary_Certification_Authority_-_G2.pem
  Adding debian:GeoTrust_Primary_Certification_Authority_-_G3.pem
  Adding debian:GeoTrust_Universal_CA.pem
  Adding debian:GeoTrust_Universal_CA_2.pem
  Adding debian:GlobalSign_ECC_Root_CA_-_R4.pem
  Adding debian:GlobalSign_ECC_Root_CA_-_R5.pem
  Adding debian:GlobalSign_Root_CA.pem
  Adding debian:GlobalSign_Root_CA_-_R2.pem
  Adding debian:GlobalSign_Root_CA_-_R3.pem
  Adding debian:Global_Chambersign_Root_-_2008.pem
  Adding debian:Go_Daddy_Class_2_CA.pem
  Adding debian:Go_Daddy_Root_Certificate_Authority_-_G2.pem
  Adding debian:Hellenic_Academic_and_Research_Institutions_RootCA_2011.pem
  Adding debian:Hongkong_Post_Root_CA_1.pem
  Adding debian:IGC_A.pem
  Adding debian:IdenTrust_Commercial_Root_CA_1.pem
  Adding debian:IdenTrust_Public_Sector_Root_CA_1.pem
  Adding debian:Izenpe.com.pem
  Adding debian:Juur-SK.pem
  Adding debian:Microsec_e-Szigno_Root_CA.pem
  Adding debian:Microsec_e-Szigno_Root_CA_2009.pem
  Adding debian:NetLock_Arany_=Class_Gold=_Főtanúsítvány.pem
  Adding debian:NetLock_Business_=Class_B=_Root.pem
  Adding debian:NetLock_Express_=Class_C=_Root.pem
  Adding debian:NetLock_Notary_=Class_A=_Root.pem
  Adding debian:NetLock_Qualified_=Class_QA=_Root.pem
  Adding debian:Network_Solutions_Certificate_Authority.pem
  Adding debian:OISTE_WISeKey_Global_Root_GA_CA.pem
  Adding debian:OISTE_WISeKey_Global_Root_GB_CA.pem
  Adding debian:PSCProcert.pem
  Adding debian:QuoVadis_Root_CA.pem
  Adding debian:QuoVadis_Root_CA_1_G3.pem
  Adding debian:QuoVadis_Root_CA_2.pem
  Adding debian:QuoVadis_Root_CA_2_G3.pem
  Adding debian:QuoVadis_Root_CA_3.pem
  Adding debian:QuoVadis_Root_CA_3_G3.pem
  Adding debian:RSA_Security_2048_v3.pem
  Adding debian:Root_CA_Generalitat_Valenciana.pem
  Adding debian:S-TRUST_Authentication_and_Encryption_Root_CA_2005_PN.pem
  Adding debian:S-TRUST_Universal_Root_CA.pem
  Adding debian:SecureSign_RootCA11.pem
  Adding debian:SecureTrust_CA.pem
  Adding debian:Secure_Global_CA.pem
  Adding debian:Security_Communication_EV_RootCA1.pem
  Adding debian:Security_Communication_RootCA2.pem
  Adding debian:Security_Communication_Root_CA.pem
  Adding debian:Sonera_Class_1_Root_CA.pem
  Adding debian:Sonera_Class_2_Root_CA.pem
  Adding debian:Staat_der_Nederlanden_EV_Root_CA.pem
  Adding debian:Staat_der_Nederlanden_Root_CA.pem
  Adding debian:Staat_der_Nederlanden_Root_CA_-_G2.pem
  Adding debian:Staat_der_Nederlanden_Root_CA_-_G3.pem
  Adding debian:Starfield_Class_2_CA.pem
  Adding 

Bug#822943: tuskar-ui: FTBFS: ImportError: cannot import name unittest

[Chris Lamb]

Source: tuskar-ui
Version: 0.4.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

tuskar-ui fails to build from source in unstable/amd64:

  [..]

  ERROR: Failure: ImportError (No module named v1_1)
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
  addr.filename, addr.module)
File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
  return self.importFromDir(dir_path, fqname)
File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
  mod = load_module(part_fqname, fh, filename, desc)
File 
"/home/lamby/temp/cdt.20160429094108.GsO2cfy2qm.tuskar-ui/tuskar-ui-0.4.0/tuskar_ui/infrastructure/overview/tests.py",
 line 22, in 
  from tuskar_ui.infrastructure.overview import forms
File 
"/home/lamby/temp/cdt.20160429094108.GsO2cfy2qm.tuskar-ui/tuskar-ui-0.4.0/tuskar_ui/infrastructure/overview/forms.py",
 line 25, in 
  from os_cloud_config import keystone as keystone_config
File "/usr/lib/python2.7/dist-packages/os_cloud_config/keystone.py", line 
26, in 
  from os_cloud_config.utils import clients
File "/usr/lib/python2.7/dist-packages/os_cloud_config/utils/clients.py", 
line 26, in 
  from novaclient.v1_1 import client as novav11client
  ImportError: No module named v1_1
  
  ==
  ERROR: Failure: ImportError (cannot import name SortedDict)
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
  addr.filename, addr.module)
File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
  return self.importFromDir(dir_path, fqname)
File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
  mod = load_module(part_fqname, fh, filename, desc)
File 
"/home/lamby/temp/cdt.20160429094108.GsO2cfy2qm.tuskar-ui/tuskar-ui-0.4.0/tuskar_ui/infrastructure/parameters/forms.py",
 line 19, in 
  from django.utils.datastructures import SortedDict
  ImportError: cannot import name SortedDict
  
  ==
  ERROR: Failure: ImportError (cannot import name SortedDict)
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
  addr.filename, addr.module)
File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
  return self.importFromDir(dir_path, fqname)
File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
  mod = load_module(part_fqname, fh, filename, desc)
File 
"/home/lamby/temp/cdt.20160429094108.GsO2cfy2qm.tuskar-ui/tuskar-ui-0.4.0/tuskar_ui/infrastructure/parameters/urls.py",
 line 17, in 
  from tuskar_ui.infrastructure.parameters import views
File 
"/home/lamby/temp/cdt.20160429094108.GsO2cfy2qm.tuskar-ui/tuskar-ui-0.4.0/tuskar_ui/infrastructure/parameters/views.py",
 line 22, in 
  from tuskar_ui.infrastructure.parameters import forms
File 
"/home/lamby/temp/cdt.20160429094108.GsO2cfy2qm.tuskar-ui/tuskar-ui-0.4.0/tuskar_ui/infrastructure/parameters/forms.py",
 line 19, in 
  from django.utils.datastructures import SortedDict
  ImportError: cannot import name SortedDict
  
  ==
  ERROR: Failure: ImportError (cannot import name SortedDict)
  --
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
  addr.filename, addr.module)
File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
  return self.importFromDir(dir_path, fqname)
File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
  mod = load_module(part_fqname, fh, filename, desc)
File 
"/home/lamby/temp/cdt.20160429094108.GsO2cfy2qm.tuskar-ui/tuskar-ui-0.4.0/tuskar_ui/infrastructure/parameters/views.py",
 line 22, in 
  from tuskar_ui.infrastructure.parameters import forms
File 
"/home/lamby/temp/cdt.20160429094108.GsO2cfy2qm.tuskar-ui/tuskar-ui-0.4.0/tuskar_ui/infrastructure/parameters/forms.py",
 line 19, in 
  from django.utils.datastructures import SortedDict
  ImportError: cannot import name SortedDict
  
  

Bug#822934: golang-github-imdario-mergo: please update to latest upstream release

[Potter, Tim (HPE Linux Support)]

Package: golang-github-imdario-mergo
Severity: wishlist
X-Debbugs-CC: pkg-go 

Please upload the latest release of the golang-github-imdario-mergo,
0.2.2.  I've already packaged this in the repo on alioth.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#822935: postgresql-9.4-asn1oid: Plugin crashes when trying to use syntax '.1.2.3'::asn1oid

[Herwin Weststrate]

Package: postgresql-9.4-asn1oid
Version: 0.0.20100818-3.1
Severity: normal

Dear Maintainer,

  template1=# SELECT '.1.2.3'::asn1oid;
  server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
  The connection to the server was lost. Attempting reset: Failed.

Attached is a very simple patch that fixes this problem.


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

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

Versions of packages postgresql-9.4-asn1oid depends on:
ii  libc6   2.19-18+deb8u4
ii  postgresql-9.4  9.4.7-1.pgdg80+1

postgresql-9.4-asn1oid recommends no packages.

postgresql-9.4-asn1oid suggests no packages.

-- no debconf information

--- asn1oid.c.orig	2016-04-29 08:05:46.202000167 +0200
+++ asn1oid.c	2016-04-29 08:01:32.605836190 +0200
@@ -101,8 +101,12 @@
 tmp[i] += 9;
 break;
 case '.':
-if(c == str)
+if(c == str) {
+if (c[1]) {
+break;
+}
 PG_RETURN_POINTER(0);
+}
 ++i;
 if(i >= 64)
 PG_RETURN_POINTER(0);

Bug#822939: Bug#822767: libgtk-3-0: firefox scrollbar unusable

[Rene Engelhard]

severity 822939 important
forcemerge 822807 822939 
thanks

Hi,

oh, I am sorry, I missed 822807 since I didn't expect it under "important"
only.

Regards,

Rene

Bug#822667: ITP: gcc-6-doc -- documentation for the GNU compilers (gcc, gobjc, g++)

[郭溢譞]

Package: wnpp
Followup-For: Bug #822667
Owner: "Guo Yixuan (郭溢譞)" 

Hello,

The packaging work is just pushed to the git repository, branch
debian/6:

  https://anonscm.debian.org/gitweb/?p=users/yixuan-guest/gcc-doc.git

It should be buildable now, but I'll have some check on the patches
before uploading.

Cheers,
Yixuan

Bug#822938: [erlang-inets] inets_regexp module missing from package

[Sergei Golovan]

tags 822938 upstream
thanks

Hi, Jean,

On Fri, Apr 29, 2016 at 10:41 AM, Jean Parpaillon
 wrote:
> Package: erlang-inets
> Version: 1:18.3-dfsg-1
> Severity: important
>
> --- Please enter the report below this line. ---
> The inets_regexp module is missing from erlang-inets package, making
> applications depending on it unusable (cowboy 1.x.x for instance)

There's no inets_regexp source file in Erlang 18.3 anymore, so the
module is obviously missing from the binary package as well.

I'll ask upstream if this change was intentional, and if it was then we'll
have to live with it.

Cheers!
-- 
Sergei Golovan

Bug#822944: libgtk-3-0: emacs icons and scrollbar arrows disappeared

[Jörg-Volker Peetz]

Package: emacs24
Version: 24.5+1-6+b2
Severity: normal

Dear Maintainer(s),

version 3.20 of libgtk-3-0 changes the emacs24 appearance. The icons in the
menu bar vanish and in the scrollbar the up and down arrows
("-GtkScrollbar-has-backward-stepper") disappear.

Are changes in gtk.css needed or additional packages?

Regards,
jvp.


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

Kernel: Linux 4.5.2 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages emacs24 depends on:
ii  emacs24-bin-common 24.5+1-6+b2
ii  gconf-service  3.2.6-3
ii  libacl12.2.52-3
ii  libasound2 1.1.0-1
ii  libatk1.0-02.20.0-1
ii  libc6  2.22-6
ii  libcairo-gobject2  1.14.6-1+b1
ii  libcairo2  1.14.6-1+b1
ii  libdbus-1-31.10.8-1
ii  libfontconfig1 2.11.0-6.4
ii  libfreetype6   2.6.3-3
ii  libgconf-2-4   3.2.6-3
ii  libgdk-pixbuf2.0-0 2.34.0-1
ii  libgif75.1.4-0.1
ii  libglib2.0-0   2.48.0-1
ii  libgnutls303.4.11-4
ii  libgomp1   6.0.1-2
ii  libgpm21.20.4-6.2
ii  libgtk-3-0 3.18.9-1
ii  libice62:1.0.9-1+b1
ii  libjpeg62-turbo1:1.4.2-2
ii  libm17n-0  1.7.0-3+b1
ii  libmagickcore-6.q16-2  8:6.8.9.9-7+b1
ii  libmagickwand-6.q16-2  8:6.8.9.9-7+b1
ii  libotf00.9.13-3
ii  libpango-1.0-0 1.40.1-1
ii  libpangocairo-1.0-01.40.1-1
ii  libpng16-161.6.21-4
ii  librsvg2-2 2.40.15-1
ii  libselinux12.5-1
ii  libsm6 2:1.2.2-1+b1
ii  libtiff5   4.0.6-1
ii  libtinfo5  6.0+20160319-1
ii  libx11-6   2:1.6.3-1
ii  libxft22.3.2-1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxml22.9.3+dfsg1-1
ii  libxpm41:3.5.11-1+b1
ii  libxrandr2 2:1.5.0-1
ii  libxrender11:0.9.9-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

emacs24 recommends no packages.

Versions of packages emacs24 suggests:
ii  emacs24-common-non-dfsg  24.5+1-1

-- no debconf information

Bug#822940: Acknowledgement (/pci@f400000/ata-6@d/@0:3,/boot/vmlinux: Unknown or corrupt filesystem)

[Mathieu Malaterre]

If I type `halt` from the yaboot prompt, I return to Open Firmware.

>From there,

0 > dir hd:,\

seems to be working ok

where

devalias hd /pci@f400/ata-6@d/disk@0

Bug#820407: RFS: smartmontools/6.4+svn4214-1~bpo8+1

[Jonathan Dowland]

On Thu, Apr 28, 2016 at 05:11:26PM +, Gianfranco Costamagna wrote:
> oops sorry!
> 
> thanks for understanding,

Hey no problem, thanks for sponsoring it!

Bug#780665: closed by Debian FTP Masters <ftpmas...@ftp-master.debian.org> (Bug#820703: Removed package(s) from unstable)

[Jonathan Dowland]

reopen 780665
found 780665 7u91-2.6.3-1~deb8u1
thanks

On Fri, Apr 15, 2016 at 07:41:13PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the openjdk-7-jre-headless package:
> 
> #780665: openjdk-7-jre-headless: stable-security update to 
> openjdk-7-jre-headless introduced pulseaudio dependency
> 
> It has been closed by Debian FTP Masters .

I think there's a bit of a procedural problem here, when bugs against stable
packages are closed when a package is RoM'd from sid. OpenJDK 7 is still the
only OpenJDK version in Jessie.  I've just checked and confirmed this bug is
still present in the latest updated version in Jessie. I haven't checked all
the other closed bugs to see if they are still relevant, but I bet more than
just this one is.


-- 
Jonathan Dowland

Bug#822947: dh-haskell: breaks when dpkg-buildflags returns multiple flags in LDFLAGS

[Colin Watson]

Package: dh-haskell
Version: 0.1
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch

On Ubuntu, "dpkg-buildflags --get LDFLAGS" defaults to
"-Wl,-Bsymbolic-functions -Wl,-z,relro".  dh-haskell's handling of the
output of LDFLAGS is buggy in that it only works correctly when a single
flag is returned (I think it probably even breaks if LDFLAGS is empty).
This results in errors such as:

  [1 of 5] Compiling Data.These   ( Data/These.hs, 
dist-ghc/build/Data/These.p_o )
  /usr/bin/ld: unrecognized option '-Bsymbolic-functions -Wl'
  /usr/bin/ld: use the --help option for usage information
  collect2: error: ld returned 1 exit status

Patch follows.

diff --git a/lib/Debian/Debhelper/Buildsystem/haskell.pm 
b/lib/Debian/Debhelper/Buildsystem/haskell.pm
index aabed89..4bc85fa 100644
--- a/lib/Debian/Debhelper/Buildsystem/haskell.pm
+++ b/lib/Debian/Debhelper/Buildsystem/haskell.pm
@@ -321,7 +321,9 @@ ghc, that harden generated binaries and fix corresponding 
lintian warning.
 =cut
 
 sub ghc_linker_flags {
-my @link_flags = `dpkg-buildflags --get LDFLAGS` or die $!;
+my $link_flags = `dpkg-buildflags --get LDFLAGS` or die $!;
+chomp $link_flags;
+my @link_flags = split " ", $link_flags;
 return map "--ghc-option=-optl$_", @link_flags;
 }
 

Thanks,

-- 
Colin Watson   [cjwat...@ubuntu.com]

Bug#822924: libsdl2-2.0-0: ibus support is disabled

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending
Control: severity -1 wishlist


Hi,

2016-04-29 04:43 ookawa michiaki:

Package: libsdl2-2.0-0
Version: 2.0.4+dfsg1-2+b1
Severity: normal

Dear Maintainer,
Since 2.0.4, SDL can use ibus for input method.
Currently, libsdl2-2.0-0 doesn't support it.
Please add depends for libibus-1.0 and rebuild with it.


Support enabled now, will be present in the next release.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#821445: [Pkg-postgresql-public] Bug#821445: postgresql-common: [INTL:nl] Dutch translation of debconf messages

[Christoph Berg]

Control: tags -1 pending

Re: Frans Spiesschaert 2016-04-18 <1461003580.5627.6.ca...@yucom.be>
> Package: postgresql-common 
> Severity: wishlist 
> Tags: l10n patch 
>  
> 
> Dear Maintainer, 
>  
> == 
> Please find attached the updated Dutch translation of postgresql-common 
> debconf messages. 

Hi Frans,

thanks for the update. However, the only change is the translation of
the last chunk which is 100% shell code - I'd prefer to have that bit
left untranslated so it doesn't get fuzzy if we change the original.

I've updated debian/po/templates.pot not to contain that chunk anymore
so translators won't be seeing an untranslated chunk anymore.

Cheers,
Christoph

Bug#822949: liblablgtk2-ocaml-dev: lablgtk2 2.18 has wrong version in META file (reports as 2.16)

[Felix Ruess]

Package: liblablgtk2-ocaml-dev
Version: 2.16.0+dfsg-1
Severity: important

Dear Maintainer,

liblablgtk2 2.18.3+dfsg-1 reports the version wrongly as 2.16:

$ apt-cache madison liblablgtk2-ocaml
liblablgtk2-ocaml | 2.18.3+dfsg-1 | http://httpredir.debian.org/debian sid/main
amd64 Packages
$ ocamlfind query -format '%v' lablgtk2
2.16.0

expected would be that it correctly reports 2.18

It seems that the META file in the orig sources has
version = "2.18.0"
but is overwritten by the META, META.lablgtk2-gnome and META.lablgtk2-gl files
in the debian packaging info to
version="2.16.0"

Bug#822933: golang-github-graylog2-go-gelf: please update to latest upstream snapshot

[Potter, Tim (HPE Linux Support)]

Package: golang-github-graylog2-go-gelf
Severity: wishlist
X-Debbugs-CC: pkg-go 

Please upload the latest release of the golang-github-graylog2-go-gelf package,
0.0~git20160329.0.76d60fc.  I've already packaged this in the repo on alioth.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#822936: INFO: rcu_sched self-detected stall on CPU

[Jiann-Ming Su]

Package: linux-image-3.16.0-4-686-pae
Version: 3.16.7-ckt25-1

The netbook doesn't crash, but the entire networking stack freezes up.
When I press a key on the keyboard, the backlight comes on, and
everything is functional again.

Apr 27 21:53:20 ranfan kernel: INFO: rcu_sched self-detected stall on
CPU { 0}  (t=6590 jiffies g=23325 c=23324 q=2)
Apr 27 21:53:20 ranfan kernel: sending NMI to all CPUs:
Apr 27 21:53:20 ranfan kernel: NMI backtrace for cpu 0
Apr 27 21:53:20 ranfan kernel: CPU: 0 PID: 0 Comm: swapper/0 Not
tainted 3.16.0-4-686-pae #1 Debian 3.16.7-ckt25-1
Apr 27 21:53:20 ranfan kernel: Hardware name: Acer AO751h
 /JV11-ML  , BIOS V0.3212 02/26/2010
Apr 27 21:53:20 ranfan kernel: task: c15fca00 ti: c15ee000 task.ti: c15ee000
Apr 27 21:53:20 ranfan kernel: EIP: 0060:[] EFLAGS: 0026 CPU: 0
Apr 27 21:53:20 ranfan kernel: EIP is at
arch_trigger_all_cpu_backtrace+0x95/0xd0
Apr 27 21:53:20 ranfan kernel: EAX: 00418958 EBX: 2710 ECX:
f000 EDX: f000
Apr 27 21:53:20 ranfan kernel: ESI: c1614f80 EDI: f75d9620 EBP:
f5007e40 ESP: f5007e34
Apr 27 21:53:20 ranfan kernel:  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Apr 27 21:53:20 ranfan kernel: CR0: 8005003b CR2: b7765000 CR3:
0171e000 CR4: 07f0
Apr 27 21:53:20 ranfan kernel: Stack:
Apr 27 21:53:20 ranfan kernel:  c1548401 c157a0ce c1614f80 f5007e88
c10ac95d c1557924 19be 5b1d
Apr 27 21:53:20 ranfan kernel:  5b1c 0002  f5007e88
c1084790 0001 c166a5ec c1614f80
Apr 27 21:53:20 ranfan kernel:  f75d9620  c15fca00 
 f5007e9c c1062dac f5009f7c
Apr 27 21:53:20 ranfan kernel: Call Trace:
Apr 27 21:53:20 ranfan kernel:  [] ? rcu_check_callbacks+0x38d/0x5b0
Apr 27 21:53:20 ranfan kernel:  [] ? account_process_tick+0x60/0x130
Apr 27 21:53:20 ranfan kernel:  [] ? update_process_times+0x3c/0x60
Apr 27 21:53:20 ranfan kernel:  [] ?
tick_sched_handle.isra.13+0x26/0x60
Apr 27 21:53:20 ranfan kernel:  [] ? tick_sched_timer+0x37/0x70
Apr 27 21:53:20 ranfan kernel:  [] ? __remove_hrtimer+0x38/0x90
Apr 27 21:53:20 ranfan kernel:  [] ? __run_hrtimer+0x6d/0x190
Apr 27 21:53:20 ranfan kernel:  [] ?
tick_sched_handle.isra.13+0x60/0x60
Apr 27 21:53:20 ranfan kernel:  [] ? hrtimer_interrupt+0x1e8/0x2a0
Apr 27 21:53:20 ranfan kernel:  [] ?
tick_do_broadcast.constprop.7+0x6b/0x70
Apr 27 21:53:20 ranfan kernel:  [] ?
tick_handle_oneshot_broadcast+0x105/0x180
Apr 27 21:53:20 ranfan kernel:  [] ?
add_interrupt_randomness+0x15a/0x1a0
Apr 27 21:53:20 ranfan kernel:  [] ? timer_interrupt+0x12/0x20
Apr 27 21:53:20 ranfan kernel:  [] ?
handle_irq_event_percpu+0x35/0x180
Apr 27 21:53:20 ranfan kernel:  [] ? handle_irq_event+0x2a/0x50
Apr 27 21:53:20 ranfan kernel:  [] ? handle_simple_irq+0x70/0x70
Apr 27 21:53:20 ranfan kernel:  [] ? handle_edge_irq+0x66/0x100
Apr 27 21:53:20 ranfan kernel:  [] ? handle_irq+0x71/0x90
Apr 27 21:53:20 ranfan kernel:  
Apr 27 21:53:20 ranfan kernel:
Apr 27 21:53:20 ranfan kernel:  [] ? do_IRQ+0x3c/0xd0
Apr 27 21:53:20 ranfan kernel:  [] ? rebalance_domains+0x14e/0x250
Apr 27 21:53:20 ranfan kernel:  [] ? common_interrupt+0x33/0x38
Apr 27 21:53:20 ranfan kernel:  [] ?
psb_intel_sdvo_read_response+0xcb/0x200 [gma500_gfx]
Apr 27 21:53:20 ranfan kernel:  [] ? __do_softirq+0x6d/0x230
Apr 27 21:53:20 ranfan kernel:  [] ? cpu_callback+0x160/0x160
Apr 27 21:53:20 ranfan kernel:  [] ? do_softirq_own_stack+0x22/0x30
Apr 27 21:53:20 ranfan kernel:  
Apr 27 21:53:20 ranfan kernel:
Apr 27 21:53:20 ranfan kernel:  [] ? irq_exit+0x8d/0xa0
Apr 27 21:53:20 ranfan kernel:  [] ? do_IRQ+0x45/0xd0
Apr 27 21:53:20 ranfan kernel:  [] ?
tick_broadcast_oneshot_control+0x7b/0x210
Apr 27 21:53:20 ranfan kernel:  [] ? common_interrupt+0x33/0x38
Apr 27 21:53:20 ranfan kernel:  [] ? cpuidle_enter_state+0x3e/0xd0
Apr 27 21:53:20 ranfan kernel:  [] ? cpu_startup_entry+0x2be/0x3b0
Apr 27 21:53:20 ranfan kernel:  [] ? start_kernel+0x3dd/0x3e2
Apr 27 21:53:20 ranfan kernel:  [] ? set_init_arg+0x45/0x45
Apr 27 21:53:20 ranfan kernel: Code: 08 5b 5d c3 66 90 f0 0f b3 15 a8
a4 66 c1 a1 a8 a4 66 c1 85 c0 75 3a 31 c0 bb 10 27 00 00 eb 1f 8d b6
00 00 00 00 b8 58 89 41 00  36 aa 21 00 e8 91 ca 09 00 83 eb 01 74
09 a1 a8 a4 66 c1 85
Apr 27 21:52:54 ranfan kernel: NMI backtrace for cpu 1
Apr 27 21:52:54 ranfan kernel: CPU: 1 PID: 0 Comm: swapper/1 Not
tainted 3.16.0-4-686-pae #1 Debian 3.16.7-ckt25-1
Apr 27 21:52:54 ranfan kernel: Hardware name: Acer AO751h
 /JV11-ML  , BIOS V0.3212 02/26/2010
Apr 27 21:52:54 ranfan kernel: task: f50b9560 ti: f50d task.ti: f50d
Apr 27 21:52:54 ranfan kernel: EIP: 0060:[] EFLAGS: 00200246 CPU: 1
Apr 27 21:52:54 ranfan kernel: EIP is at cpu_startup_entry+0xf2/0x3b0
Apr 27 21:52:54 ranfan kernel: EAX: 0020 EBX: f50d ECX:
0001 EDX: f50d1fec
Apr 27 21:52:54 ranfan kernel: ESI: 0004 EDI: 0001 EBP:
f50d1f90 ESP: f50d1f60
Apr 27 21:52:54 ranfan kernel:  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Apr 27 21:52:54 ranfan 

Bug#822767: libgtk-3-0: firefox scrollbar unusable

[Rene Engelhard]

clone 822767 -1
reassign -1 firefox
retitle -1 needs CSS Node support support for Gtk 3.20
tag -1 upstream
forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1234158
severity -1 grave
thanks

Hi,

On Thu, Apr 28, 2016 at 11:47:12PM +0200, Jörg-Volker Peetz wrote:
> On Wed, 27 Apr 2016 11:47:58 +0200 =?UTF-8?Q?J=c3=b6rg-Volker_Peetz?=
>  wrote:
> > Package: libgtk-3-0
> > Version: 3.20.3-1
> > Severity: normal
> >
> > Dear Maintainer(s),
> >
> > this version changes the emacs24 (24.5+1-6) appearance. The icons in the
> > menu bar vanish and in the scrollbar the up and down arrows
> > ("-GtkScrollbar-has-backward-stepper") disappear.
> >
> > Are changes in gtk.css needed or additional packages?
> 
> On Wed, 27 Apr 2016 23:31:17 +0200 Michael Biebl  wrote:
> > Am 27.04.2016 um 20:45 schrieb Jörg-Volker Peetz:
> > > Package: libgtk-3-0
> > > Version: 3.20.3-1
> > > Severity: normal
> > > 
> > > Dear Maintainer(s),
> > > 
> > > also for the new firefox version in sid (46.0-1) the scrollbars are 
> > > unusable.
> > > Going back to version 3.18.9-1 of the libgtk-3 packages makes the 
> > > scrollbars
> > > work again.
> > 
> > That's something which needs to be fixed in Firefox
> > 
> > See https://bugzilla.mozilla.org/show_bug.cgi?id=1234158

Cloning a bug there.

> Then a bug report should also be filed for emacs24?

Maybe. Don't know what emacs does, it it wouldn't do harm, would it? Maybe
this bug even should just be reassigned there since the Gtk 3.20 changes
- as incompatible they are apparently - were intended..

(With google I see a thread/bug about Gtk 3.20 on the emacs ml but I am not able
to access it: 
https://lists.gnu.org/archive/html/bug-gnu-emacs/2016-04/msg00048.html)

Regards,

Rene

Bug#822937: samba: throws error on atempt to connect

[Walsh, Nicholas]

Package: samba
Version: 2:3.6.6-6+deb7u9
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after update to version 2:3.6.6-6+deb7u9 all attempts at smb connection to a AD 
share result in the error

"ntlmssp3_handle_neg_flags: Got challenge flags[0x60898201] - possible 
downgrade detected!
missing_flags[0x0010] - NT_STATUS_RPC_SEC_PKG_ERROR session setup failed: 
NT_STATUS_MORE_PROCESSING_REQUIRED *** Please consider answering these 
questions, where appropriate ***
did you forget to run kinit?"

The kinit did throw me off, but I realised that kerberos was not at issue since 
nothing changed with it and it's not used for authentication.

My primary use for smbclient is with the icinga2 monitoring platform for space 
checks, something that was the first to indicate a problem.

Commandline, both from icinga2 and in separate tests by myself has been
smbclient //[server]/[share] -U [domain]/[user]



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

Kernel: Linux 3.2.0-4-amd64 (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

Versions of packages samba depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.49
ii  dpkg   1.16.17
ii  libacl12.2.51-8
ii  libattr1   1:2.4.46-8
ii  libc6  2.13-38+deb7u10
ii  libcap21:2.22-1.2
ii  libcomerr2 1.42.5-1.1+deb7u1
ii  libcups2   1.5.3-5+deb7u6
ii  libgssapi-krb5-2   1.10.1+dfsg-5+deb7u7
ii  libk5crypto3   1.10.1+dfsg-5+deb7u7
ii  libkrb5-3  1.10.1+dfsg-5+deb7u7
ii  libldap-2.4-2  2.4.31-2+deb7u1
ii  libpam-modules 1.1.3-7.1
ii  libpam-runtime 1.1.3-7.1
ii  libpam0g   1.1.3-7.1
ii  libpopt0   1.16-7
ii  libtalloc2 2.0.7+git20120207-1
ii  libtdb11.2.10-2
ii  libwbclient0   2:3.6.6-6+deb7u9
ii  lsb-base   4.1+Debian8+deb7u1
ii  procps 1:3.3.3-3
ii  samba-common   2:3.6.6-6+deb7u9
ii  update-inetd   4.43
ii  zlib1g 1:1.2.7.dfsg-13

Versions of packages samba recommends:
ii  logrotate  3.8.1-4
ii  tdb-tools  1.2.10-2

Versions of packages samba suggests:
pn  ctdb  
pn  ldb-tools 
pn  openbsd-inetd | inet-superserver  
pn  smbldap-tools 

-- debconf information:
  samba/run_mode: daemons
  samba-common/title:

Bug#822672: RFS: freecell-solver/4.2.0-0.1 [NMU]

[Shlomi Fish]

Hi Paul and everybody,

On Fri, 29 Apr 2016 10:36:23 +0800
Paul Wise  wrote:

> On Thu, Apr 28, 2016 at 8:41 PM, Shlomi Fish wrote:
> 
> > I fixed most pep8 warnings there, except for some in the TAP library which
> > was copied from https://github.com/rjbs/pytap .  
> 
> Embedded code copies are discouraged in Debian, could you remove it
> from upstream VCS and tarballs and make it a dependency instead?
> 
> https://wiki.debian.org/EmbeddedCodeCopies
> 

Well, I think the problem I ran into was that there's a lot of other things
called "pyTAP" or something to the effect - see
https://duckduckgo.com/?q=pytap=about and it's hard to know that the one I'm
using is what I need. Perhaps there should be a name/identifier change and a
proper package should be put on PyPI.

Regards,

Shlomi Fish 

-- 
-
Shlomi Fish   http://www.shlomifish.org/
What Makes Software Apps High Quality -  http://shlom.in/sw-quality

An idealist is one who, on noticing that a rose smells better than a cabbage,
concludes that it is also more nourishing.
— http://en.wikiquote.org/wiki/H._L._Mencken

Please reply to list if it's a mailing list post - http://shlom.in/reply .

Bug#822938: [erlang-inets] inets_regexp module missing from package

[Jean Parpaillon]

Package: erlang-inets
Version: 1:18.3-dfsg-1
Severity: important

--- Please enter the report below this line. ---
The inets_regexp module is missing from erlang-inets package, making
applications depending on it unusable (cowboy 1.x.x for instance)

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.5.2

Debian Release: stretch/sid
  500 trusty  ppa.launchpad.net 
  500 testing security.debian.org 
  500 testing repository.spotify.com 
  500 testing cdn.debian.net 
  500 stable  dl.google.com 
  400 testing www.deb-multimedia.org 
  200 unstablecdn.debian.net 
1 experimentalcdn.debian.net 

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.



-- 
Jean Parpaillon

Bug#822935: postgresql-9.4-asn1oid: Plugin crashes when trying to use syntax '.1.2.3'::asn1oid

[Herwin Weststrate]

Attached is a better patch, basicly every occurence of
PG_RETURN_POINTER(0) resulted in a segfault, text input like '1.2.3',
'.' or '' would still fail with the first patch.
The behavior here is comparable to what happens when you use
"'foo'::integer"

-- 
Herwin Weststrate
Quarantainenet BV
--- pgsql-asn1oid-0.0.20100818/asn1oid.c	2010-08-18 17:24:28.0 +0200
+++ pgsql-asn1oid-0.0.20100818.patched/asn1oid.c	2016-04-29 08:55:12.952143426 +0200
@@ -101,21 +101,36 @@
 tmp[i] += 9;
 break;
 case '.':
-if(c == str)
-PG_RETURN_POINTER(0);
+if(c == str) {
+if (c[1]) {
+/* Skip over first dot */
+break;
+}
+ereport(ERROR,
+  (errcode(ERRCODE_INVALID_TEXT_REPRESENTATION),
+  errmsg("invalid input syntax for type asn1oid: \"%s\"",
+str)));
+}
 ++i;
 if(i >= 64)
-PG_RETURN_POINTER(0);
+ereport(ERROR,
+  (errcode(ERRCODE_INVALID_TEXT_REPRESENTATION),
+  errmsg("invalid input syntax for type asn1oid: \"%s\"",
+str)));
 tmp[i] = 0;
 break;
 default:
-PG_RETURN_POINTER(0);
+ereport(ERROR,
+  (errcode(ERRCODE_INVALID_TEXT_REPRESENTATION),
+  errmsg("invalid input syntax for type asn1oid: \"%s\"",
+str)));
 }
 }
-if(c == str)
-PG_RETURN_POINTER(0);
-if(c[-1] == '.')
-PG_RETURN_POINTER(0);
+if(c == str || c[-1] == '.')
+ereport(ERROR,
+  (errcode(ERRCODE_INVALID_TEXT_REPRESENTATION),
+  errmsg("invalid input syntax for type asn1oid: \"%s\"",
+str)));
 
 ++i;
 

Bug#822940: /pci@f400000/ata-6@d/@0:3,/boot/vmlinux: Unknown or corrupt filesystem

[Mathieu Malaterre]

Package: installation-reports

Boot method: yaboot
Image version: 
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd/debian-testing-powerpc-netinst.iso
Date: Fri Apr 29 10:21:50 CEST 2016

Machine: Mac Mini G4
Processor: G4
Memory: 512M
Partitions: default setup (whole disk) upon `install32`

Résultat de lspci -knn (ou lspci -nn) : ?

Installation du système de base : O

Initial boot:   [E ]
Detect network card:[O ]
Configure network:  [ O]
Detect CD:  [ O]
Load installer modules: [O ]
Detect hard drives: [ O]
Partition hard drives:  [ O]
Install base system:[ O]
Clock/timezone setup:   [O ]
User/password setup:[ O]
Install tasks:  [ O]
Install boot loader:[ O]
Overall install:[ O]

Comments/Problems:

Technically I do need some firmware: ATI/R200 and b43. The ATI should
not be required, but the b43 would be nice if I want to do install
over wifi. hw-detect did not seems to see the wifi card and did not
ask for non-free external thingy.

Bug#822941: debian-installer: cannot boot installed on VirtualBox with EFI-enabled

[Hideki Yamane]

Package: debian-installer
Severity: important

Dear Maintainer,

 I found user notes Debian on VBox with EFI enabled environment cannot
 boot, see http://qiita.com/zakuro9715/items/45e82473ce39914e04ed (in Japanese)

 I've confirmed it with d-i9 alpha5.
 And, it doesn't happen with Fedora 24 alpha and Ubuntu 16.04.


Step to reproduce:

 1. setup Virtualbox VM with EFI enabled
 2. install Debian
 3. after installation, turn of VM
 4. turn on VM again
 5. not bootable, startup EFI shell



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

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

Bug#822946: Don't set console setting over logout/login

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: console-setup
Version: 1.142
Severity: important

When using console-setup to setup proper console char set (latin1), it
does not preserve it over logout/login or reboot. After logout, the
console is again set to UTF-8 what makes it difficult to handle
passwords with umlauts or even usernames with German umlauts (even if
the last usecase is not supported).

When logging in as root and do dpkg-reconfigure console-setup with all
settings as before (or running cached_setup_font.sh), it works for all
presently consoles (until logout).

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (700, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.5.0 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages console-setup depends on:
ii  console-setup-linux 1.142
ii  debconf 1.5.59
ii  keyboard-configuration  1.142
ii  xkb-data2.17-1

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales   2.22-7
ii  lsb-base  9.20160110

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.59
ii  liblocale-gettext-perl  1.07-1+b1

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.31
ii  initscripts 2.88dsf-59.3
ii  kbd 2.0.3-2
ii  keyboard-configuration  1.142

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
ii  console-common0.7.89
ii  console-data  2:1.12-5
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.0.3-2
pn  systemd   

- -- debconf information:
* console-setup/fontface47: Terminus
* console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic 
languages
  console-setup/framebuffer_only:
  console-setup/store_defaults_in_debconf_db: true
* console-setup/fontsize-fb47: 6x12 (nur Framebuffer)
  keyboard-configuration/switch: No temporary switch
  keyboard-configuration/store_defaults_in_debconf_db: true
* keyboard-configuration/variant: Deutsch - Deutsch (ohne Akzenttasten)
  keyboard-configuration/variantcode: nodeadkeys
  keyboard-configuration/unsupported_config_options: true
  debian-installer/console-setup-udeb/title:
* keyboard-configuration/model: IBM ThinkPad 560Z/600/600E/A22E
  keyboard-configuration/altgr: The default for the keyboard layout
  keyboard-configuration/unsupported_options: true
  console-setup/guess_font:
  keyboard-configuration/other:
  keyboard-configuration/toggle: No toggling
  keyboard-configuration/layout:
* console-setup/charmap47: ISO-8859-1
  keyboard-configuration/unsupported_layout: true
  keyboard-configuration/modelcode: thinkpad
  keyboard-configuration/ctrl_alt_bksp: true
  console-setup/fontsize: 6x12
  keyboard-configuration/compose: No compose key
  keyboard-configuration/layoutcode: de
  console-setup/use_system_font:
  keyboard-configuration/unsupported_config_layout: true
  keyboard-configuration/optionscode: 
lv3:ralt_switch_multikey,terminate:ctrl_alt_bksp,shift:breaks_caps
  console-setup/fontsize-text47: 6x12 (nur Framebuffer)
  keyboard-configuration/xkb-keymap: de(nodeadkeys)
  console-setup/codesetcode: Lat15

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

iQGcBAEBCgAGBQJXIyYoAAoJEKZ8CrGAGfasCJkL/0SoINg1GtCfp1ytPPZwHCf6
YSteUB1sRfrfT3mXH1+bEk6ra4HfKFSC6PvAPe0AucxEvpbuC6iFeJosTA63/y3O
gI9i6ie9HDZWhM8OPltCiY4vTESHwhAbBWexQtro7AWuFYlANmYmV4R5YM3DmPTy
MkG4uZX+axhY0ED92BtEaPTzeuhiD2NVp0KWIfQ9U7cG2ONTbbb7vfEfbCLSV1En
HnsqvlgPQdVXxxcSxbzus7TZNvvG7rkQl6gNQKBHR3hst7N4a2JPEhR9vuj61eK3
fUzB2R1mdvF3zGzWP4ZUFK6AXNGx1s31maEGwpziuHAbWv1iJbOy8R9f9ET8g4xq
AZ1WAiVUVUuMI+v6VwX5IwiZs0M21ksVjNLz3k5jE7RDAxYVXs4ldtTAkU3sJIM7
DcQ60Udz4+wfer7rDtEds5vN828fb/C4bOJKmahHT0PwvnlW8+PuU/mqLfx1woHe
+0tw7j3RYA0EyLKfkTxm4dBnDfXPDJ8N5i6gUuG1Ew==
=aBsv
-END PGP SIGNATURE-

Bug#820798: devscripts: [licensecheck] please add support for MAME's license/copyright info

[Dominique Dumont]

On Tuesday 12 April 2016 15:14:56 Jordi Mallach wrote:
> // license:BSD-3-Clause
> // copyright-holders:Miodrag Milanovic
> 
> Would it be possible to add support for something like this?

I think so. I'll handle this.

All the best

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Bug#746005: guile-2.0 migration

[Emilio Pozuelo Monfort]

Control: severity -1 serious

Hi,

We talked about this on the RT meeting yesterday and agreed to bump this to RC
again. We wouldn't like to release Stretch with guile-1.8 just for lilypond's
sake, and it is better to act now that there's plenty of time before the freeze
so that a new version can be uploaded (possibly to experimental for the time
being) and fixes can be applied.

We can discuss this again later in the cycle if necessary, though hopefully
lilypond can get in shape and we won't need to do that :)

On 09/12/15 21:02, Don Armstrong wrote:
> On Wed, 09 Dec 2015, Emilio Pozuelo Monfort wrote:
>> On 06/05/15 16:41, Don Armstrong wrote:
>>> Control: severity -1 important
>>>
>>> On Tue, 05 May 2015, Rob Browning wrote:
 Don Armstrong  writes:

> At this juncture, I'm OK with expending the effort myself to keep
> guile-1.8 working with lilypond as the sole reverse dependency if that's
> what is required. [Unfortunately, I don't have enough time or expertise
> to actually solve the issues with the newer versions of guile, though.]

 For the record, I'm fine with letting 1.8 stay for now.  I imagine Don
 and I can handle any serious problems, and hopefully we won't need it
 too much longer.
>>>
>>> Thanks. I'm going to downgrade this for the time being. I'm going to try
>>> to keep on top of this as the development of squeeze progresses; feel
>>> free to re-ping whenever.
>>
>> Squeeze? Did you mean Stretch? :)
> 
> Yes, sorry.
> 
>> How is this looking? I saw some commits on the upstream git repo
>> mentioning guile 2.0. If you're unsure about this, maybe we could have
>> the unstable 2.19.x series uploaded to experimental, built against
>> guile-2.0, to make some progress, get some feedback, etc?
> 
> I haven't re-pinged them recently, but they were making some progress
> last time I checked.
> 
> Rebuilding for experimental makes some sense to keep on top of this,
> though as I remember, it built, but then didn't always work properly.
> 
> [I'm running chronically short on time though, so I've sort of just been
> letting this sit until a new release comes out.]

There have been plenty of 'unstable' releases (last one was 2.19.40 just a few
days ago) and those have a --with-guile2 configure switch. It may be a good idea
to upload that to experimental with guile 2.0 support?

Cheers,
Emilio

Bug#801476: backported patch from 3.6.0-1

[Piotr Ożarowski]

tags 801476 +patch
fixed 801476 3.6.0-1
thanks

I backported patch from 3.6.0-1 that fixes this bug. Please consider
updating package in stable.
--- /usr/lib/python3/dist-packages/lxml/html/soupparser.py.orig	2016-04-29 10:50:38.407542936 +0200
+++ /usr/lib/python3/dist-packages/lxml/html/soupparser.py	2016-04-29 10:56:35.038214263 +0200
@@ -3,9 +3,19 @@
 
 __all__ = ["fromstring", "parse", "convert_tree"]
 
+import re
 from lxml import etree, html
-from BeautifulSoup import \
- BeautifulSoup, Tag, Comment, ProcessingInstruction, NavigableString
+
+try:
+from bs4 import (
+BeautifulSoup, Tag, Comment, ProcessingInstruction, NavigableString,
+Declaration, CData, Doctype)
+_DECLARATION_OR_DOCTYPE = (Declaration, Doctype)
+except ImportError:
+from BeautifulSoup import (
+BeautifulSoup, Tag, Comment, ProcessingInstruction, NavigableString,
+Declaration, CData)
+_DECLARATION_OR_DOCTYPE = Declaration
 
 
 def fromstring(data, beautifulsoup=None, makeelement=None, **bsargs):
@@ -45,8 +55,6 @@
 You can pass a different Element factory through the `makeelement`
 keyword.
 """
-if makeelement is None:
-makeelement = html.html_parser.makeelement
 root = _convert_tree(beautiful_soup_tree, makeelement)
 children = root.getchildren()
 for child in children:
@@ -59,10 +67,12 @@
 def _parse(source, beautifulsoup, makeelement, **bsargs):
 if beautifulsoup is None:
 beautifulsoup = BeautifulSoup
-if makeelement is None:
-makeelement = html.html_parser.makeelement
-if 'convertEntities' not in bsargs:
-bsargs['convertEntities'] = 'html'
+if hasattr(beautifulsoup, "HTML_ENTITIES"):  # bs3
+if 'convertEntities' not in bsargs:
+bsargs['convertEntities'] = 'html'
+if hasattr(beautifulsoup, "DEFAULT_BUILDER_FEATURES"):  # bs4
+if 'features' not in bsargs:
+bsargs['features'] = ['html.parser']  # use Python html parser
 tree = beautifulsoup(source, **bsargs)
 root = _convert_tree(tree, makeelement)
 # from ET: wrap the document in a html root element, if necessary
@@ -71,36 +81,201 @@
 root.tag = "html"
 return root
 
+
+_parse_doctype_declaration = re.compile(
+r'(?:\s|[ element. However, the document
+# may be a soup like 'HelloHi
+# all<\p>'. In this example roots is a list containing meta, head
+# and body elements.
+pre_root = beautiful_soup_tree.contents[:first_element_idx]
+roots = beautiful_soup_tree.contents[first_element_idx:last_element_idx+1]
+post_root = beautiful_soup_tree.contents[last_element_idx+1:]
+
+# Reorganize so that there is one  root...
+if html_root is not None:
+# ... use existing one if possible, ...
+i = roots.index(html_root)
+html_root.contents = roots[:i] + html_root.contents + roots[i+1:]
 else:
-element.tail = (element.tail or '') + text
+# ... otherwise create a new one.
+html_root = _PseudoTag(roots)
+
+convert_node = _init_node_converters(makeelement)
+
+# Process pre_root
+res_root = convert_node(html_root)
+prev = res_root
+for e in reversed(pre_root):
+converted = convert_node(e)
+if converted is not None:
+prev.addprevious(converted)
+prev = converted
+
+# ditto for post_root
+prev = res_root
+for e in post_root:
+converted = convert_node(e)
+if converted is not None:
+prev.addnext(converted)
+prev = converted
+
+if declaration is not None:
+try:
+# bs4 provides full Doctype string
+doctype_string = declaration.output_ready()
+except AttributeError:
+doctype_string = declaration.string
+
+match = _parse_doctype_declaration(doctype_string)
+if not match:
+# Something is wrong if we end up in here. Since soupparser should
+# tolerate errors, do not raise Exception, just let it pass.
+pass
+else:
+external_id, sys_uri = match.groups()
+docinfo = res_root.getroottree().docinfo
+# strip quotes and update DOCTYPE values (any of None, '', '...')
+docinfo.public_id = external_id and external_id[1:-1]
+docinfo.system_url = sys_uri and sys_uri[1:-1]
+
+return res_root
+
+
+def _init_node_converters(makeelement):
+converters = {}
+ordered_node_types = []
+
+def converter(*types):
+def add(handler):
+for t in types:
+converters[t] = handler
+ordered_node_types.append(t)
+return handler
+return add
+
+def find_best_converter(node):
+for t in ordered_node_types:
+if isinstance(node, t):
+return converters[t]
+return None
+
+def convert_node(bs_node, parent=None):
+# duplicated in convert_tag() below
+ 

Bug#803195: RFA: spark -- SPARK programming language toolset

[Florian Schanda]

On Wed, 28 Oct 2015 21:48:46 +0100 Eugeniy Meshcheryakov  
wrote:
> I know about the new version, I also tried to compile it for Debian, but
> it was alsways failing either because of internal compiler error or
> other reasons. And now I just have no time for packaing it.

Ok, so might be able to take over maintenance of this package and update to 
SPARK 2014 but I might require some help since I have not done this before.

I think the situation now should be better than in the past: we had a number 
of tool requirements (alt-ergo, cvc4) that already exist in debian. Now, these 
tools live under the a libexec dir for spark so they should no longer conflict 
with the debian packages.

We still require a recent gprbuild but this should be less of an issue. The 
main issue I see is that building from source is somewhat involved (requires a 
checkout of the gnat sources for a start).

Florian

Bug#822416: Install LVM with Free PE, partman-?????

[Holger Levsen]

On Fri, Apr 29, 2016 at 10:14:17AM +0200, Philip Hands wrote:
> Yes, but a vast /home is pretty-much never what anyone wants.

actually I want that all the time on laptops and desktops :-)
With disks bigger than 500gb I usually want a 20gb root filesystem, 
10gb swap, and 470gb /home on LVM. Sometimes I'd prefer 30 or 40gb
root filesystems in that situation.
Having /var (and/or /var/log) on seperate partitions is something I
nowadays only do on servers (but then, on virtualized server sometimes
also not anymore…)

IOW: one size doesnt fit all.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#821686: [pkg-kolab] Bug#821686: src:libkolab: PHP 7.0 Transition

[Sandro Knauß]

Control: block -1 821687

Before adding php7 support to libkolab, we need to fix libkolabxml.
--
Am Montag, 18. April 2016, 23:02:28 CEST schrieb Ondřej Surý:
> Package: src:libkolab
> Severity: important
> User: pkg-php-ma...@lists.alioth.debian.org
> Usertags: php7.0-transition
> 
> Dear maintainer(s),
> 
> this bug is a part of ongoing php7.0 transition.  It is filled as
> important, but the severity will be bumped to serious within quite short
> (~month) timeframe as the transition was announced almost 3 months ago.
> 
> The libkolab package currently build-depends on php5 php5-cli php5-dev .
> 
> PHP 7.0 has landed in unstable with substantial changes to the packaging:
> 
>   1. Every package built from src:phpMAJOR.MINOR now include
>  phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.
> 
>   2. Accompanying src:php-defaults builds 1:1 mapping to a default
>  MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
>  specify a dependency, please use the generic name, unless you
>  absolutely know that won't work for you.
> 
>   3. Every path in the system has been changed to a versioned, e.g.
>  /etc/php5/cli is now /etc/php/7.0/cli
> 
>   4. dh_php5 is now dh_php
> 
>   5. php-pear is not built from independent source package.
> 
>   6. master-7.0 branches of several extensions (php-apcu, xdebug,
>  php-apcu-bc) can be used as a template how to change the PHP
>  extension packaging.  It's mostly cut since the d/rules tries
>  to figure-out most of the variables from debian/ directory.
> 
>   7. pkg-php-tools package now supports PHP 7.0 packaging and if your
>  package uses pkg-php-tools a simple binNMU is all it might need
> 
>   8. PHP 7.0 has changed extension API, so most-if-not-all extensions
>  need work from upstream to be compatible with PHP 7.0.
> 
>   9. We expect to ship next Debian release (stretch) only with PHP
>  7.0, that means that all packages needs to be made compatible with
>  PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
>  maintained software.  However some extensions has been deprecated
>  (f.e. mysql) and thus old unmaintained software will stop working
>  and it will have to be either patched or removed from stable Debian.
> 
> So what you need to do:
> 
> Replace every occurence of php5 with just php, e.g. if you depend on
> 'php5' then you just need to depend on 'php'.  Also if you package a web
> application and depend on specific SAPI, I would recommend depending just
> on 'php' package and let the user decide whether he will install php-fpm,
> libapache2-mod-php or php-cgi.
> 
> The script that was used to get the list of packages for MBF was not a
> particular smart one (so it doesn't detect alternatives, etc.), so if
> there's a false positive, please excuse me and just close the bug with
> short explanation.
> 
> The other options that might be used with packages that don't and won't
> support PHP 7.0 is to remove the software from Debian by changing the
> title of this bugreport to:
> 
> RM: libkolab -- ROM; doesn't support PHP 7.0
> 
> reassigning it to ftp.debian.org pseudo-package and changing severity to
> 'normal'.
> 
> Also feel free to contact the maintainers at one of the lists:
> 
> pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
> pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
> pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all
> 
> Cheers, Ondrej
> 
> -- System Information:
> Debian Release: 8.4
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
> 'stable') Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
> Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> 
> ___
> pkg-kolab-devel mailing list
> pkg-kolab-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kolab-devel



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

Bug#814489: [Pkg-privacy-maintainers] Bug#814489: tails-installer: fails with "Could not find the 'ifcpu64.c32' COM32 module"

[ge...@riseup.net]

On 16-04-29 14:01:07, ge...@riseup.net wrote:
> @intrigeri: Do you need support / help with this? Just in case you're
> missing the time: Would you be happy to get a patch?

Sorry, just overlooked the fact that it's already fixed in git.
Sorry for the noise then.. :(


signature.asc
Description: PGP signature

Bug#822951: openuniverse: FTBFS when built with dpkg-buildpackage -A (can't cd to [...]/debian/openuniverse/usr/share/openuniverse/conf)

[Santiago Vila]

Package: src:openuniverse
Version: 1.0beta3.1+dfsg-4
User: sanv...@debian.org
Usertags: binary-indep
Severity: important
Tags: patch

Hello Javier.

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found

[... snipped ...]

   debian/rules override_dh_install
make[1]: Entering directory '/<>/openuniverse-1.0beta3.1+dfsg'
dh_install
[ ! -L debian/openuniverse/usr/share/openuniverse/conf/ou.conf ] && \
cd `pwd`/debian/openuniverse/usr/share/openuniverse/conf && \
ln -s /etc/openuniverse.conf ou.conf
/bin/sh: 2: cd: can't cd to 
/<>/openuniverse-1.0beta3.1+dfsg/debian/openuniverse/usr/share/openuniverse/conf
debian/rules:28: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 2
make[1]: Leaving directory '/<>/openuniverse-1.0beta3.1+dfsg'
debian/rules:14: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Explanation: We are creating arch-independent packages only, so the cd command 
fails
because debian/openuniverse/[...] does not exist (as openuniverse is 
arch-dependent).

The trivial fix is to override dh_install only when creating arch-dependent 
packages.

While we are at it, it would be more elegant to do the chgrp and chmod thing
just after dh_fixperms.

[ Another possible improvement would be to create symlinks with dh_link, or 
even better,
  using debian/openuniverse.links, but this is up to you ].

The following patch (warning: untested) might fix this.

BTW: Glad that you finally decided to use UTF-8 for your own name :-)

Thanks.


--- a/debian/rules
+++ b/debian/rules
@@ -24,7 +24,7 @@ override_dh_auto_build:
$(MAKE)
 
 
-override_dh_install:
+override_dh_install-arch:
dh_install
[ ! -L debian/openuniverse/usr/share/openuniverse/conf/ou.conf ] && \
cd `pwd`/debian/openuniverse/usr/share/openuniverse/conf && \
@@ -32,7 +32,8 @@ override_dh_install:
[ ! -L debian/openuniverse/usr/share/doc/openuniverse/manual ] && \
cd debian/openuniverse/usr/share/doc/openuniverse && \
ln -s ../../openuniverse/docs manual 
+
+override_dh_fixperms-arch:
+   dh_fixperms
chgrp games `pwd`/debian/openuniverse/var/games/openuniverse/scrshots
chmod g+ws  `pwd`/debian/openuniverse/var/games/openuniverse/scrshots
-
-

Bug#822953: refcard: [INTL:sk] Slovak po-debconf translation

[helix84]

Package: refcard
Severity: wishlist
Tags: l10n patch
Version: 5.0.9

.po attached

~~helix84
# Slovak translation of the Debian reference card
# Copyright (C) 2008 Free Software Foundation, Inc.
# This file is distributed under the same license as the refcard package.
# Peter Mann , 2005, 2008.
# Ivan Masár , 2010, 2016.
msgid ""
msgstr ""
"Project-Id-Version: refcard 9.0\n"
"POT-Creation-Date: 2016-04-21 19:43+0200\n"
"PO-Revision-Date: 2016-04-29 12:09+0200\n"
"Last-Translator: ctenar \n"
"Language-Team: x\n"
"Language: sk\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n"
"X-Generator: Virtaal 0.7.1\n"

#. type: Attribute 'lang' of: 
#: entries.dbk:4
msgid "en-GB"
msgstr "sk"

#. type: Content of: 
#: entries.dbk:7
msgid "DebianGNU/Linux Reference Card"
msgstr "Referenčná karta DebianGNU/Linux"

#. type: Content of: 
#: entries.dbk:10
msgid "The 101 most important things when using Debian GNU/Linux"
msgstr "101 najdôležitejších vecí pri používaní Debian GNU/Linuxu"

#. type: Content of: 
#: entries.dbk:13
msgid ""
" 2004 2010 W. Martin Borgert   2016 Holger Wansing   2004 2010 "
"Your Name (\"Language\") "
msgstr ""
" 2004 2010 W. Martin Borgert   2016 Holger Wansing   2004 2010 "
"Peter Mann (slovenský preklad) "

#. type: Content of: 
#: entries.dbk:28
#| msgid ""
#| "This document may be used under the terms of the GNU General Public "
#| "License version 3 or higher. Conditions for copying and translations can "
#| "be found at http://www.debian.org/doc/manuals/refcard/\;> "
#| "http://www.debian.org/doc/manuals/refcard/, "
#| "where you can always get the latest version of the reference card."
msgid ""
"This document may be used under the terms of the GNU General Public License "
"version 3 or higher. The license text can be found at http://;
"www.gnu.org/copyleft/gpl.html\">http://www.gnu.org/copyleft/gpl.html "
"and /usr/share/common-licenses/GPL-3."
msgstr ""
"Tento dokument sa smie používať v súlade s podmienkami GNU General Public "
"License verzie 3 alebo vyššej. Text licencie nájdete na adrese http://www.gnu.org/copyleft/gpl.html\";
">http://www.gnu.org/copyleft/gpl.html a v súbore /usr/share"
"/common-licenses/GPL-3."

#. type: Content of: 
#: entries.dbk:35 entries.dbk:370
msgid "APT"
msgstr "APT"

#. type: Content of: 
#: entries.dbk:36
msgid "Debian"
msgstr "Debian"

#. type: Content of: 
#: entries.dbk:37
msgid "dpkg"
msgstr "dpkg"

#. type: Content of: 
#: entries.dbk:38
msgid "reference card"
msgstr "referenčná karta"

#. type: Content of: 
#: entries.dbk:39
msgid "basic commands"
msgstr "základné príkazy"

#. type: Content of: 
#: entries.dbk:40
msgid "Version"
msgstr "Verzia"

#. type: Content of: 
#: entries.dbk:41
msgid "Made by"
msgstr "Made by"

#. type: Content of: 
#: entries.dbk:45
msgid "Getting Help"
msgstr "Získanie pomoci"

#. type: Content of: 
#: entries.dbk:48
msgid "man page or man bash"
msgstr "man stránka alebo man bash"

#. type: Content of: 
#: entries.dbk:50
msgid "Read online help for every command and many configuration files."
msgstr "Okamžitá pomoc ku každému príkazu a k množstvu konfiguračných súborov."

#. type: Content of: 
#: entries.dbk:54
msgid ""
"command   --"
"help, -h"
msgstr ""
"príkaz   --"
"help, -h"

#. type: Content of: 
#: entries.dbk:57
msgid "Brief help for most commands."
msgstr "Stručná pomoc k väčšine príkazov."

#. type: Content of: 
#: entries.dbk:61
msgid ""
"/usr/share/doc/package-name/"
msgstr ""
"/usr/share/doc/názov-balíka/"

#. type: Content of: 
#: entries.dbk:62
msgid ""
"Find all documentation here, optional file README.Debian contains specifics."
msgstr ""
"Tu nájdete kompletnú dokumentáciu, nepovinný súbor README.Debian obsahuje špecifické poznámky."

#. type: Content of: 
#: entries.dbk:67
msgid "http://www.debian.org/doc/\;>Web documentation"
msgstr "http://www.debian.org/doc/\;>Dokumentácia na webe"

#. type: Content of: 
#: entries.dbk:69
msgid ""
"Reference, manuals, FAQs, HOWTOs, etc. at http://www.debian.org/doc/;
""
msgstr ""
"Príručky, návody, FAQ, HOWTO, atď. na http://www.debian.org/doc/"

#. type: Content of: 
#: entries.dbk:73
msgid ""
"http://lists.debian.org/\;>Mailing lists at "
"http://lists.debian.org/"
msgstr ""
"http://lists.debian.org/\;>Poštové konferencie na "
"http://lists.debian.org/"

#. type: Content of: 
#: entries.dbk:76
msgid "The community is always helpful, search for users."
msgstr "Komunita sa snaží pomáhať, hľadajte skupinu users."

#. type: Content of: 
#: entries.dbk:80
msgid ""
"http://wiki.debian.org/\;>The Wiki at http://;
"wiki.debian.org/"
msgstr ""
"http://wiki.debian.org/\;>Wiki na http://wiki.;
"debian.org/"

#. type: Content of: 
#: entries.dbk:82
msgid "Contains all kind of useful information."
msgstr "Obsahuje všetky druhy užitočných informácií."

#. type: Content of: 
#: entries.dbk:88
msgid "Installation"

Bug#822937: Acknowledgement (samba: throws error on atempt to connect)

[Walsh, Nicholas]

Further information:
smbclient //[host]/[share] -U\[domain]nwalsh%[password] -d10
INFO: Current debug levels:
  all: 10
  tdb: 10
  printdrivers: 10
  lanman: 10
  smb: 10
  rpc_parse: 10
  rpc_srv: 10
  rpc_cli: 10
  passdb: 10
  sam: 10
  auth: 10
  winbind: 10
  vfs: 10
  idmap: 10
  quota: 10
  acls: 10
  locking: 10
  msdfs: 10
  dmapi: 10
  registry: 10
lp_load_ex: refreshing parameters
Initialising global parameters
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
INFO: Current debug levels:
  all: 10
  tdb: 10
  printdrivers: 10
  lanman: 10
  smb: 10
  rpc_parse: 10
  rpc_srv: 10
  rpc_cli: 10
  passdb: 10
  sam: 10
  auth: 10
  winbind: 10
  vfs: 10
  idmap: 10
  quota: 10
  acls: 10
  locking: 10
  msdfs: 10
  dmapi: 10
  registry: 10
params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf"
Processing section "[global]"
doing parameter workgroup = [domain]
doing parameter server string = %h server
doing parameter dns proxy = no
doing parameter log file = /var/log/samba/log.%m
doing parameter max log size = 1000
doing parameter syslog = 0
doing parameter panic action = /usr/share/samba/panic-action %d
doing parameter passdb backend = tdbsam
doing parameter obey pam restrictions = yes
doing parameter unix password sync = yes
doing parameter passwd program = /usr/bin/passwd %u
doing parameter passwd chat = *Enter\snew\s*\spassword:* %n\n 
*Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
doing parameter pam password change = yes
doing parameter domain master = no
doing parameter local master = no
doing parameter preferred master = no
doing parameter usershare allow guests = yes
pm_process() returned Yes
lp_servicenumber: couldn't find homes
set_server_role: role = ROLE_STANDALONE
Substituting charset 'UTF-8' for LOCALE
added interface eth0 ip=fe80::250:56ff:fe8a:3a0e%eth0 
bcast=fe80:::::%eth0 netmask=:::::
added interface eth0 ip=10.120.38.255 bcast=10.120.39.255 netmask=255.255.254.0
Netbios name list:-
my_netbios_names[0]="GOTSVL2142"
Client started (version 3.6.6).
Opening cache file at /var/run/samba/gencache.tdb
Opening cache file at /var/run/samba/gencache_notrans.tdb
sitename_fetch: No stored sitename for
internal_resolve_name: looking up [host]#20 (sitename (null))
name [host]#20 found.
remove_duplicate_addrs2: looking for duplicate address/port pairs
Running timed event "tevent_req_timedout" 0x7ff64b2e33e0
Connecting to 10.255.0.210 at port 445
Socket options:
SO_KEEPALIVE = 0
SO_REUSEADDR = 0
SO_BROADCAST = 0
TCP_NODELAY = 1
TCP_KEEPCNT = 9
TCP_KEEPIDLE = 7200
TCP_KEEPINTVL = 75
IPTOS_LOWDELAY = 0
IPTOS_THROUGHPUT = 0
SO_SNDBUF = 24040
SO_RCVBUF = 87380
SO_SNDLOWAT = 1
SO_RCVLOWAT = 1
SO_SNDTIMEO = 0
SO_RCVTIMEO = 0
TCP_QUICKACK = 1
session request ok
Substituting charset 'UTF-8' for LOCALE
Doing spnego session setup (blob length=108)
got OID=1.2.840.48018.1.2.2
got OID=1.2.840.113554.1.2.2
got OID=1.3.6.1.4.1.311.2.2.10
got principal=[host]$@[domain]
 negotiate: struct NEGOTIATE_MESSAGE
Signature: 'NTLMSSP'
MessageType  : NtLmNegotiate (1)
NegotiateFlags   : 0x60088215 (1611170325)
   1: NTLMSSP_NEGOTIATE_UNICODE
   0: NTLMSSP_NEGOTIATE_OEM
   1: NTLMSSP_REQUEST_TARGET
   1: NTLMSSP_NEGOTIATE_SIGN
   0: NTLMSSP_NEGOTIATE_SEAL
   0: NTLMSSP_NEGOTIATE_DATAGRAM
   0: NTLMSSP_NEGOTIATE_LM_KEY
   0: NTLMSSP_NEGOTIATE_NETWARE
   1: NTLMSSP_NEGOTIATE_NTLM
   0: NTLMSSP_NEGOTIATE_NT_ONLY
   0: NTLMSSP_ANONYMOUS
   0: NTLMSSP_NEGOTIATE_OEM_DOMAIN_SUPPLIED
   0: NTLMSSP_NEGOTIATE_OEM_WORKSTATION_SUPPLIED
   0: NTLMSSP_NEGOTIATE_THIS_IS_LOCAL_CALL
   1: NTLMSSP_NEGOTIATE_ALWAYS_SIGN
   0: NTLMSSP_TARGET_TYPE_DOMAIN
   0: NTLMSSP_TARGET_TYPE_SERVER
   0: NTLMSSP_TARGET_TYPE_SHARE
   1: NTLMSSP_NEGOTIATE_EXTENDED_SESSIONSECURITY
   0: NTLMSSP_NEGOTIATE_IDENTIFY
   0: NTLMSSP_REQUEST_NON_NT_SESSION_KEY
   0: NTLMSSP_NEGOTIATE_TARGET_INFO
   0: NTLMSSP_NEGOTIATE_VERSION
   1: NTLMSSP_NEGOTIATE_128
   1: NTLMSSP_NEGOTIATE_KEY_EXCH
   0: NTLMSSP_NEGOTIATE_56
DomainNameLen: 0x0006 (6)
DomainNameMaxLen : 0x0006 (6)
DomainName   : *
DomainName   : '[domain]'
WorkstationLen   : 0x000a (10)
WorkstationMaxLen: 0x000a (10)
Workstation  : *
Workstation  : 'GOTSVL2142'
Got challenge flags:
Got NTLMSSP neg_flags=0x60898201
  NTLMSSP_NEGOTIATE_UNICODE
  

Bug#822666: closed by Ben Hutchings <b...@decadent.org.uk> (Bug#822666: fixed in linux 4.5.2-1)

[Ben Hutchings]

On Fri, 2016-04-29 at 13:07 +0200, Thierry Herbelot wrote:
> On 04/29/2016 12:09 PM, Debian Bug Tracking System wrote:
> > 
> > This is an automatic notification regarding your Bug report
> > which was filed against the src:linux package:
> > 
> > #822666: linux-headers-3.16.0-4-amd64: deprecated syntax in linux-headers 
> > Makefile
> > 
> > It has been closed by Ben Hutchings .
> > 
> > Their explanation is attached below along with your original report.
> > If this explanation is unsatisfactory and you have not received a
> > better one in a separate message then please contact Ben Hutchings 
> >  by
> > replying to this email.
> > 
> > 
> Dear Maintainer,
> 
> The problem cannot be solved by importing a more recent version of the 
> Linux kernel: the problem comes from a specific Makefile, which is only 
> present in Debian
[...]
> Then I do not think the initial problem is solved by switching to a more 
> recent version of the kernel (indeed the problem is also present in an 
> even more recent of the kernel).

Please read the changelog that was included in the previous message.

Ben.

-- 
Ben Hutchings
Tomorrow will be cancelled due to lack of interest.

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

Bug#822956: www.debian.org: releases/wheezy note on LTS

[José Gatica]

Cool



Enviado con MailTrack




*José Gatica A.*
Web Developer
Coordinador Enlaces
56 9 74899270
Valdivia - Chile



2016-04-29 7:29 GMT-03:00 Santiago Ruano Rincón :

> Package: www.debian.org
> Severity: normal
> Tags: patch
>
> Hi,
>
> Now that Wheezy has been handed over to the LTS team, a note could be
> added in the release pages. Patch attached. Also attached a Spanish
> translation to be forwarded to l10n-spanish.
>
> Cheers,
>
> Santiago
>

Bug#822957:

[Yash Paupiah]

Package: monit
Version: 5.9-1;

Disables sslv3 if the system's openssl is compiled without it. (Jessie)


I am using Debian GNU/Linux 8 (Jessie), kernel 3.16.0-4-686-pae
and GLIBC 2.19-18+deb8u4
diff -Nru monit-5.9/debian/changelog monit-5.9/debian/changelog
--- monit-5.9/debian/changelog	2015-09-12 19:34:24.0 +0400
+++ monit-5.9/debian/changelog	2016-04-28 17:08:16.0 +0400
@@ -1,3 +1,10 @@
+monit (1:5.9-1+deb8u1.1) UNRELEASED; urgency=medium
+
+  * Remove support for sslv3 when system doesn't support it.
+  * 
+
+ -- Yash Paupiah    Thu, 28 Apr 2016 17:06:49 +0400
+
 monit (1:5.9-1+deb8u1) jessie; urgency=medium
 
   * Fix umask-related regression between 5.8.1 and 5.9 (Closes: #796989)
diff -Nru monit-5.9/debian/patches/OPENSSL_NO_SSLv3.patch monit-5.9/debian/patches/OPENSSL_NO_SSLv3.patch
--- monit-5.9/debian/patches/OPENSSL_NO_SSLv3.patch	1970-01-01 04:00:00.0 +0400
+++ monit-5.9/debian/patches/OPENSSL_NO_SSLv3.patch	2016-04-28 17:00:27.0 +0400
@@ -0,0 +1,19 @@
+Index: monit-5.9/src/ssl.c
+===
+--- monit-5.9.orig/src/ssl.c
 monit-5.9/src/ssl.c
+@@ -624,6 +624,14 @@ ssl_connection *new_ssl_connection(char
+ break;
+ 
+ case SSL_VERSION_SSLV3:
++
++#ifdef OPENSSL_NO_SSL3
++LogError("SSL: SSLv3 not supported - use TLSv1\n");
++goto sslerror;
++#else
++  ssl->method = SSLv3_client_method();
++#endif
++   break;
+ #ifdef OPENSSL_FIPS
+ if (FIPS_mode()) {
+ LogError("SSLv3 is not allowed in FIPS mode - use TLSv1\n");
diff -Nru monit-5.9/debian/patches/series monit-5.9/debian/patches/series
--- monit-5.9/debian/patches/series	2015-09-12 19:34:24.0 +0400
+++ monit-5.9/debian/patches/series	2016-04-28 16:54:56.0 +0400
@@ -3,3 +3,4 @@
  11_enable_hurd.patch
 12_FTBFS_on_kfreebsd.patch
 13_umask_fix.patch
+OPENSSL_NO_SSLv3.patch

Bug#806108: singular: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

severity 806108 important
thanks

Hi. I *really* appreciate that you consider this has a greater severity
than "important", but I prefer to keep it important for two reasons:

* I don't have the "blessing" (so to speak) from the release managers
  to make these bugs RC yet.

* If this is serious, all the other similar bugs should be serious too.
  Here is the complete list of similar bugs:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=binary-indep;users=sanv...@debian.org


Well, those are my reasons, but of course if you insist that this must
be serious, go ahead. I promise that I will not downgrade it again,
otherwise it would be a very odd severity war indeed: Maintainer
raises severity and reporter downgrades it :-)

Thanks.

Bug#822950: kio: Missing DBUS registration in kioexec, leading to Dolphin freezes when opening remote files

[Gregor Riepl]

Package: kio
Version: 5.16.0-1
Severity: important
Tags: newcomer

Dear Maintainer,

kioexec from kio 5.16 has a bug that causes Dolphin to freeze when opening
remote files in an external editor.

The bug was fixed in kio 5.17, according to the upstream bug report:
https://bugs.kde.org/show_bug.cgi?id=353037

Please update KDE in testing to 5.17 or backport the patch that fixes the
problem:
https://quickgit.kde.org/?p=kio.git=commit=1b4289ca0e00bf7ba59b19837ea2b2519f42a984

Thank you!



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

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

Versions of packages kio depends on:
ii  libacl1   2.2.52-3
ii  libc6 2.22-7
ii  libgcc1   1:5.3.1-14
ii  libgssapi-krb5-2  1.13.2+dfsg-5
ii  libkf5archive55.16.0-1
ii  libkf5codecs5 5.16.0-1
ii  libkf5completion5 5.16.0-1
ii  libkf5configcore5 5.16.0-1
ii  libkf5configwidgets5  5.16.0-1
ii  libkf5coreaddons5 5.16.0-1
ii  libkf5dbusaddons5 5.16.0-1
ii  libkf5i18n5   5.16.0-1
ii  libkf5itemviews5  5.16.0-1
ii  libkf5kiocore55.16.0-1
ii  libkf5kiontlm55.16.0-1
ii  libkf5kiowidgets5 5.16.0-1
ii  libkf5notifications5  5.16.0-1
ii  libkf5service-bin 5.16.0-1
ii  libkf5service55.16.0-1
ii  libkf5solid5  5.16.0-1
ii  libkf5textwidgets55.16.0-1
ii  libkf5wallet-bin  5.16.0-1
ii  libkf5wallet5 5.16.0-1
ii  libkf5widgetsaddons5  5.16.0-1
ii  libkf5windowsystem5   5.16.0-1
ii  libqt5core5a  5.5.1+dfsg-16+b1
ii  libqt5dbus5   5.5.1+dfsg-16+b1
ii  libqt5gui55.5.1+dfsg-16+b1
ii  libqt5network55.5.1+dfsg-16+b1
ii  libqt5script5 5.5.1+dfsg-2
ii  libqt5widgets55.5.1+dfsg-16+b1
ii  libqt5x11extras5  5.5.1-3
ii  libqt5xml55.5.1+dfsg-16+b1
ii  libstdc++65.3.1-14
ii  libxml2   2.9.3+dfsg1-1
ii  libxslt1.11.1.28-2.1

kio recommends no packages.

kio suggests no packages.

-- no debconf information

Bug#822949: patch

[Felix Ruess]

Added a patch to update the META files to the version of the upstream
package.

P.S. Sorry, I ran reportbug on a different machine so it says "Version:
2.16.0+dfsg-1", but it's really about 2.18.3+dfsg-1
From cd1c49d61c1f75c9b283439dfb41c2a07add4995 Mon Sep 17 00:00:00 2001
From: Felix Ruess 
Date: Fri, 29 Apr 2016 11:56:30 +0200
Subject: [PATCH] update version in META files to 2.18.0

should fix bug #822949
---
 debian/META| 2 +-
 debian/META.lablgtk2-gl| 2 +-
 debian/META.lablgtk2-gnome | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/debian/META b/debian/META
index cdf9c0b..ebb0cb0 100644
--- a/debian/META
+++ b/debian/META
@@ -1,4 +1,4 @@
-version="2.16.0"
+version="2.18.0"
 requires(mt) = "threads"
 requires(mt,mt_vm) = "threads.vm"
 requires(mt,mt_posix) = "threads.posix"
diff --git a/debian/META.lablgtk2-gl b/debian/META.lablgtk2-gl
index 1712640..e4c814b 100644
--- a/debian/META.lablgtk2-gl
+++ b/debian/META.lablgtk2-gl
@@ -1,4 +1,4 @@
-version="2.16.0"
+version="2.18.0"
 directory="+lablgtk2"
 requires = "lablgtk2"
 
diff --git a/debian/META.lablgtk2-gnome b/debian/META.lablgtk2-gnome
index d9ed436..c808c69 100644
--- a/debian/META.lablgtk2-gnome
+++ b/debian/META.lablgtk2-gnome
@@ -1,4 +1,4 @@
-version="2.16.0"
+version="2.18.0"
 directory="+lablgtk2"
 requires = "lablgtk2"
 
-- 
1.9.1

Bug#795019: Bug#822879: cableswig: switch to castxml

[Steve M. Robbins]

On April 28, 2016 05:54:57 PM you wrote:
> Source: cableswig
> Version: 0.1.0+git20150808-2
> Severity: serious
> Control: block 818848 by -1
> 
> Dear maintainer,
> 
> gccxml is scheduled for removal, but cableswig build-depends on it.
> Please port your package to castxml.

Actually, cableswig should also be removed.  It was only in the archive to 
support the old insighttoolkit builds; but insighttoolkit is to be removed 
c.f. #795019.  Nothing else depends on cableswig -- see dak output, below.

What's your preferred workflow here?  Shall I close this bug and open a removal 
for cableswig?  Or will you just go ahead and remove cableswig and gccxml now?  
GCC-XML is dead upstream and my attempt at a wrapper around CastXML was not a 
success so IMHO it's better to remove it sooner than later.  Its other 
dependencies have already switched to CastXML (e.g. pygccxml) or they will 
soon or they are also dead.

Cheers,
-Steve


dak rm -Rn cableswig" 
Will remove the following packages from unstable: 

cableswig | 0.1.0+git20150808-2 | source, amd64, arm64, armel, armhf, hurd-
i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, 
ppc64el, s390x 
libcableswig-dev | 0.1.0+git20150808-2 | amd64, arm64, armel, armhf, hurd-
i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mips64el, mipsel, powerpc, 
ppc64el, s390x 

Maintainer: Steve M. Robbins  

--- Reason --- 

-- 

Checking reverse dependencies... 
# Broken Build-Depends: 
insighttoolkit: cableswig (>= 0.1.0+cvs20110226) 

Dependency problem found.



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

Bug#822954: haproxy-1.5.8 Disable SSLv3

[Anoop Seburuth]

Package: haproxy
Version: 1.5.8


As Described the problem: https://www.rfc-editor.org/rfc/rfc7568.txt
According to rfc7568, sslv3 is no longer considered secure. This patch
disables sslv3 if the system's openssl is compiled without it. (Jessie)

Below is a transcript:

--- haproxy-1.5.8.orig/src/ssl_sock.c
+++ haproxy-1.5.8/src/ssl_sock.c
@@ -1506,8 +1506,14 @@ int ssl_sock_prepare_ctx(struct bind_con
ssloptions |= SSL_OP_NO_TLSv1_2;
if (bind_conf->ssl_options & BC_SSL_O_NO_TLS_TICKETS)
ssloptions |= SSL_OP_NO_TICKET;
-   if (bind_conf->ssl_options & BC_SSL_O_USE_SSLV3)
+   if (bind_conf->ssl_options & BC_SSL_O_USE_SSLV3) {
+#ifndef OPENSSL_NO_SSL3
SSL_CTX_set_ssl_version(ctx, SSLv3_server_method());
+#else
+   Alert("SSLv3 support requested but unavailable.\n");
+   cfgerr++;
+#endif
+   }
if (bind_conf->ssl_options & BC_SSL_O_USE_TLSV10)
SSL_CTX_set_ssl_version(ctx, TLSv1_server_method());
 #if SSL_OP_NO_TLSv1_1
@@ -1853,8 +1859,14 @@ int ssl_sock_prepare_srv_ctx(struct serv
options |= SSL_OP_NO_TLSv1_2;
if (srv->ssl_ctx.options & SRV_SSL_O_NO_TLS_TICKETS)
options |= SSL_OP_NO_TICKET;
-   if (srv->ssl_ctx.options & SRV_SSL_O_USE_SSLV3)
+   if (srv->ssl_ctx.options & SRV_SSL_O_USE_SSLV3) {
+#ifndef OPENSSL_NO_SSL3
SSL_CTX_set_ssl_version(srv->ssl_ctx.ctx, 
SSLv3_client_method());
+#else
+   Alert("SSLv3 support requested but unavailable.");
+   cfgerr++;
+#endif
+   }
if (srv->ssl_ctx.options & SRV_SSL_O_USE_TLSV10)
SSL_CTX_set_ssl_version(srv->ssl_ctx.ctx, 
TLSv1_client_method());
 #if SSL_OP_NO_TLSv1_1


I am using Debian GNU/Linux 8 (Jessie) , Kernel 3.16.7-ckt25-1 and GLIBC
2.19-18+deb8u4

Bug#814489: [Pkg-privacy-maintainers] Bug#814489: tails-installer: fails with "Could not find the 'ifcpu64.c32' COM32 module"

[ge...@riseup.net]

(Sorry for missing In-Reply-To: and References:)

@intrigeri: Do you need support / help with this? Just in case you're
missing the time: Would you be happy to get a patch?


signature.asc
Description: PGP signature

Bug#822961: ntp logging (?again?) in a way to be catched by logcheck

[Christian Ehrhardt]

Package: ntp
Version: 1:4.2.8p4+dfsg-3+b1

Hi,
debugging a rather old issue I realized that the changes made back when
uploading 4.2.6+dfsg-1 might no more completely apply.

I quote from the changelog in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498992:
"* Remove ntp.logcheck.ignore.server, none of those messages are send to
syslog now.  (Closes: #498992)"

But I had to find that this today still (?again?) happens.
So much could have been changed on how the log data flows.

But testing is rather easy:
apt-get install logcheck
apt-get install ntp
service ntp restart

Then logcheck will report about everything from ntp:
sudo -u logcheck logcheck -s -o -t | grep ntp | wc -l
41

Is the solution "just" to bring back the old logcheck ignore file - I don't
know?

Note: tested on sid.

Bug#822960: openssh: please consider to apply/backport upstream commit 4fb726f0fdcb155ad419913cea10dc4afd409d24

[Christoph Anton Mitterer]

Source: openssh
Version: 1:7.2p2-5
Severity: wishlist


Hi Colin.

Could you please consider to apply and idealy have upstream
commit 4fb726f0fdcb155ad419913cea10dc4afd409d24 backported to
jessie?

It should fix a long standing issue that cause hanging processes
when using ssh with control channel multiplexing.
E.g. as described here:
https://dev.icinga.org/issues/2546
http://tracker.nagios.org/view.php?id=321


Cheers,
Chris

Bug#822952: squid3-3.4.8-6

[Yash Paupiah]

Package: squid3
Version: 3.4.8-6;

Disables sslv3 if the system's openssl is compiled without it. (Jessie)


I am using Debian GNU/Linux 8 (Jessie), kernel 3.16.0-4-686-pae
and GLIBC 2.19-18+deb8u4
diff -Nru squid3-3.4.8/debian/changelog squid3-3.4.8/debian/changelog
--- squid3-3.4.8/debian/changelog	2016-03-20 17:14:27.0 +0400
+++ squid3-3.4.8/debian/changelog	2016-04-29 13:23:52.0 +0400
@@ -1,3 +1,10 @@
+squid3 (3.4.8-6+deb8u2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove support for SSLv3 when it is unsupported.
+
+ -- Yash Paupiah   Fri, 29 Apr 2016 13:22:33 +0400
+
 squid3 (3.4.8-6+deb8u2) jessie-security; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff -Nru squid3-3.4.8/debian/patches/OPENSSL_NO_SSL3.patch squid3-3.4.8/debian/patches/OPENSSL_NO_SSL3.patch
--- squid3-3.4.8/debian/patches/OPENSSL_NO_SSL3.patch	1970-01-01 04:00:00.0 +0400
+++ squid3-3.4.8/debian/patches/OPENSSL_NO_SSL3.patch	2016-04-29 13:21:58.0 +0400
@@ -0,0 +1,34 @@
+Index: squid3-3.4.8/src/ssl/support.cc
+===
+--- squid3-3.4.8.orig/src/ssl/support.cc
 squid3-3.4.8/src/ssl/support.cc
+@@ -1020,8 +1020,13 @@ sslCreateClientContext(const char *certf
+ break;
+ 
+ case 3:
++#ifndef OPENSSL_NO_SSL3
+ debugs(83, 5, "Using SSLv3.");
+ method = SSLv3_client_method();
++#else
++	debugs(83, DBG_IMPORTANT, "SSLv3 is not available in this Proxy.");
++	return NULL;
++#endif
+ break;
+ 
+ case 4:
+@@ -1405,9 +1410,14 @@ Ssl::contextMethod(int version)
+ break;
+ 
+ case 3:
++#ifndef OPENSSL_NO_SSL3
+ debugs(83, 5, "Using SSLv3.");
+ method = SSLv3_server_method();
+-break;
++#else
++debugs(83, DBG_IMPORTANT, "SSLv3 is not available in this Proxy.");
++return NULL;
++#endif
++	 break;
+ 
+ case 4:
+ debugs(83, 5, "Using TLSv1.");
diff -Nru squid3-3.4.8/debian/patches/series squid3-3.4.8/debian/patches/series
--- squid3-3.4.8/debian/patches/series	2016-03-20 17:14:27.0 +0400
+++ squid3-3.4.8/debian/patches/series	2016-04-29 12:01:13.0 +0400
@@ -11,3 +11,4 @@
 35-squid-3.4-13203.patch 
 36-squid-3.4-13225.patch
 37-squid-3.5-13990.patch
+OPENSSL_NO_SSL3.patch

Bug#822210: sdl2-config.cmake: extra leading / trailing whitespace

[Manuel A. Fernandez Montecelo]

Control: forwarded -1 https://bugzilla.libsdl.org/show_bug.cgi?id=3295


2016-04-27 22:41 GMT+01:00 Manuel A. Fernandez Montecelo
:
> Hi,
>
> 2016-04-27 14:08 GMT+01:00 Gianfranco Costamagna :
>> Hi Manuel and libsdl2 developers!
>>
>>
>> How do you feel about the patch below?
>> I think we should apply it, to avoid cmake breakages in linux systems.
>
> It looks a bit odd to have to play with whitespace in this way.
>
> I'm fine with it in general, though; but since this is not Debian
> specific I prefer if it's applied (or at least blessed) by upstream
> first.  If it's failing for Jason, it should affect more people using
> other distros or the code directly from SDL repos.

This has been reported in upstream's bugzilla already (by somebody
else), with no fixes so far -- setting "forwarded" accordingly to
track the evolution upstream.


At a first glance, it looks very odd for cmake to be so fussy about
whitespace, but I guess that they have a good reason.

I've been looking into it and a more definitive/robust fix could be to
trim the strings coming from configure, so the same problem is avoided
in other systems or in future changes to other variables.  (Patch
attached).

Since "string(STRIP input output)" does not return the stripped
string, instead of using the string() function in the same spot where
the original variable is used, one has to use an "output variable" and
then use the variable as substitute in the original command.

So the result looks a bit ugly and duplicates the number of lines, and
everything is a bit cumbersome, but I think that it works.

Jason, if you want to test it to see if it works fine, then I can
submit both to upstream's bug report for them to decide.

(If anybody wants to use the attached patch as a basis for better
patches, feel free to do it.  Also anybody feel free to submit the
patches upstream, but better if tested first).


Cheers.
-- 
Manuel A. Fernandez Montecelo 


sdl2-config.cmake.in
Description: Binary data

Bug#822956: www.debian.org: releases/wheezy note on LTS

[Santiago Ruano Rincón]

Package: www.debian.org
Severity: normal
Tags: patch

Hi,

Now that Wheezy has been handed over to the LTS team, a note could be
added in the release pages. Patch attached. Also attached a Spanish
translation to be forwarded to l10n-spanish.

Cheers,

Santiago
>From d3d3cf8548fbc011e81a9365fcf25ef9461729e7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Santiago=20Ruano=20Rinc=C3=B3n?= 
Date: Fri, 29 Apr 2016 12:19:30 +0200
Subject: [PATCH] releases/wheezy/index.wml: wheezy benefits from LTS

---
 english/releases/wheezy/index.wml | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/english/releases/wheezy/index.wml b/english/releases/wheezy/index.wml
index 01ac7d5..452073f 100644
--- a/english/releases/wheezy/index.wml
+++ b/english/releases/wheezy/index.wml
@@ -20,6 +20,12 @@ the Release Notes.
 # Security updates have been discontinued as of <:=spokendate('XXX'):>.
 
 
+Wheezy benefits from Long Term Support (LTS) from 26 April 2016
+until 31 May 2018. The LTS is limited to i386, amd64, armel and armhf. For more
+information, please refer to the https://wiki.debian.org/LTS;>LTS section of Debian Wiki.
+
+
 To obtain and install Debian, see
 the installation information page and the
 Installation Guide. To upgrade from an older
-- 
2.8.1

>From c2b54a08623d8f20646bcd7d0fa5b167df83e6a9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Santiago=20Ruano=20Rinc=C3=B3n?= 
Date: Fri, 29 Apr 2016 12:21:19 +0200
Subject: [PATCH] spanish/releases/wheezy/index.wml: wheezy benefits from LTS

---
 spanish/releases/wheezy/index.wml | 8 +++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/spanish/releases/wheezy/index.wml b/spanish/releases/wheezy/index.wml
index 9a3fd3b..ca95a50 100644
--- a/spanish/releases/wheezy/index.wml
+++ b/spanish/releases/wheezy/index.wml
@@ -20,7 +20,13 @@ en las Notas de Publicación.
 Debian 8.0 (jessie).
 # Las actualizaciones de seguridad han dejado de proporcionarse el <:=spokendate('XXX'):>.
 
- 
+
+Wheezy beneficia de soporte a largo plazo («Long Term Support», LTS)
+desde el 26 de abril de 2016 hasta el 31 de mayo de 2018. Wheezy LTS está
+limitado a i386, amd64, armel y armhf. Para más información visite la https://wiki.debian.org/LTS;>sección LTS de la wiki de Debian.
+
+
 Para obtener e instalar Debian, consulte la página de la información de instalación y la
 Guía de Instalación. Para actualizar desde una 
-- 
2.8.1

Bug#822955: monitoring-plugins (2.1.1-1) Disable SSLv3

[Anoop Seburuth]

Package: monitoring-plugins
Version: 2.1.1


As Described the problem: https://www.rfc-editor.org/rfc/rfc7568.txt
According to rfc7568, sslv3 is no longer considered secure. This patch
disables sslv3 if the system's openssl is compiled without it. (Jessie)

Below is a transcript:


--- monitoring-plugins-2.1.1.orig/plugins/sslutils.c
+++ monitoring-plugins-2.1.1/plugins/sslutils.c
@@ -66,7 +66,12 @@ int np_net_ssl_init_with_hostname_versio
 #endif
 break;
 case 3: /* SSLv3 protocol */
+#if defined(OPENSSL_NO_SSL3)
+printf(("%s\n", _("CRITICAL - SSL protocol version 3 is
not supported by your SSL library.")));
+return STATE_CRITICAL;
+#else
 method = SSLv3_client_method();
+#endif
 break;
 default: /* Unsupported */
 printf("%s\n", _("CRITICAL - Unsupported SSL protocol
version."));



I am using Debian GNU/Linux 8 (Jessie) , Kernel 3.16.7-ckt25-1 and GLIBC
2.19-18+deb8u4


Regard,

Anoop Seburuth

Bug#773554: new upstream

[Iain R. Learmonth]

tags 773554 + pending
kthxbye

Hi,

I have uploaded version 2.3.2 to DELAYED/3 as an NMU.

If I don't receive any communication, this will enter unstable in 3
days. For future uploads I will also adopt this package under the
Internet Measurement Packaging Team.

Thanks,
Iain.

Bug#822958: lynx: bidi text rendering is broken

[Vincent Lefevre]

Package: lynx
Version: 2.8.9dev9-1
Severity: normal

Bi-directional text rendering is broken. See

  https://en.wikipedia.org/wiki/Right-to-left_mark

as an example in mlterm. I've attached 2 screenshots:

* lynx289-84.png with lynx 2.8.9dev8-4 (testing)

* lynx289-91.png with lynx 2.8.9dev9-1 (unstable)

With lynx 2.8.9dev9-1, the exclamation mark is no longer at the
correct place. With lynx 2.8.9dev8-4, there was also an issue: the
replacement characters after "the order of the Hebrew characters is".

Note: in the same mlterm, the w3m browser is OK.

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

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

Versions of packages lynx depends on:
ii  libbsd0   0.8.3-1
ii  libbz2-1.01.0.6-8
ii  libc6 2.22-7
ii  libgnutls30   3.4.11-4
ii  libidn11  1.32-3
ii  libncursesw5  6.0+20160319-1
ii  libtinfo5 6.0+20160319-1
ii  lynx-common   2.8.9dev9-1
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages lynx recommends:
ii  mime-support  3.59

lynx suggests no packages.

-- no debconf information

Bug#822666: closed by Ben Hutchings <b...@decadent.org.uk> (Bug#822666: fixed in linux 4.5.2-1)

[Thierry Herbelot]

On 04/29/2016 12:09 PM, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the src:linux package:

#822666: linux-headers-3.16.0-4-amd64: deprecated syntax in linux-headers 
Makefile

It has been closed by Ben Hutchings .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Ben Hutchings 
 by
replying to this email.




Dear Maintainer,

The problem cannot be solved by importing a more recent version of the 
Linux kernel: the problem comes from a specific Makefile, which is only 
present in Debian


For example, the linux-headers-4.6.0-rc3-amd64_4.6~rc3-1~exp1_amd64.deb 
package, which is quite recent contains a Makefile with the same error:


/usr/src/linux-headers-4.6.0-rc3-amd64/Makefile:

%
 1  VERSION = 2
 2  PATCHLEVEL = 6
 3	MAKEARGS := -C /usr/src/linux-headers-4.6.0-rc3-common 
O=/usr/src/linux-headers-4.6.0-rc3-amd64

 4  MAKEFLAGS += --no-print-directory
 5  .PHONY: all $(MAKECMDGOALS)
 6  cmd := $(filter-out all Makefile,$(MAKECMDGOALS))
 7  all:
 8  @$(MAKE) $(MAKEARGS) $(cmd)
 9  Makefile:;
10  $(cmd) %/: all <===
11  @:
%

The problem comes from line 10 which contains two types of targets.

Then I do not think the initial problem is solved by switching to a more 
recent version of the kernel (indeed the problem is also present in an 
even more recent of the kernel).


Best regards

Thierry

--
Thierry Herbelot
6WIND
Software Engineer

Bug#822959: Upgrade to new version: 6.1 stable

[Lampshade]

Source: gcc-6
Version: 6.0.1-2
Severity: wishlist

New stable version of GNU Compiler Collection is available: 6.1
Please upgrade package to new stable version.

Bug#822914: dpkg: Please add support for new architecture "riscv64" (RISC-V 64 bits little-endian)

[Guillem Jover]

Hi!

On Thu, 2016-04-28 at 22:30:13 +0100, Manuel A. Fernandez Montecelo wrote:
> Package: dpkg
> Version: 1.18.4
> Severity: wishlist
> Tags: patch
> Control: user debian-ri...@lists.debian.org
> Control: usertag -1 + riscv64

> What ${subject} says.  Patch attached with the line that needs to be
> added to cputable.
> 
> I think that it's all what's needed, if not please tell me what else
> is missing.

Does the new arch satisfy:

  


?

Thanks,
Guillem

Bug#822916: lives: crashes on startup

[Sebastian Ramacher]

Control: tags -1 + moreinfo

HHii

On 2016-04-28 14:52:55, koanhead wrote:
> Package: lives
> Version: 2.2.6~ds0-1
> Severity: important
> 
> Dear Maintainer,
> 
> Attempting to start LiVES (aka 'lives'), both from menu and from terminal,
> results in a crash with the following message:
> 
> "
> LiVES 2.2.6
> Copyright 2002-2014 Gabriel Finch (salsa...@gmail.com) and others.
> LiVES comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details.
> 
> LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found
> in compound effect image_stabilizer, line 4
> 
> LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found
> in compound effect motion_analyser, line 4
> 
> **
> Gtk:ERROR:/tmp/buildd/gtk+3.0-3.14.5/./gtk/gtkprogressbar.c:604:tick_cb:
> assertion failed: (priv->pulse2 > priv->pulse1)
> 
> Unfortunately LiVES crashed.
> Please report this bug at
> http://sourceforge.net/tracker/?group_id=64341=507139
> "
> 
> 
> 
> Invoking `lives -debug` from terminal results in the following:
> 
> "
> LiVES 2.2.6
> Copyright 2002-2014 Gabriel Finch (salsa...@gmail.com) and others.
> LiVES comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details.
> 
> LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found
> in compound effect image_stabilizer, line 4
> 
> LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found
> in compound effect motion_analyser, line 4
> 
> **
> Gtk:ERROR:/tmp/buildd/gtk+3.0-3.14.5/./gtk/gtkprogressbar.c:604:tick_cb:
> assertion failed: (priv->pulse2 > priv->pulse1)
> 
> Unfortunately LiVES crashed.
> Please report this bug at
> http://sourceforge.net/tracker/?group_id=64341=507139
> Thanks. Recovery should be possible if you restart LiVES.
> 
> 
> When reporting crashes, please include details of your operating system,
> distribution, and the LiVES version (2.2.6)
> and any information shown below:
> 
> #0  0x7f36ada074c9 in __libc_waitpid (pid=26891, stat_loc=0x7fff7edb87cc,
> #1  0x7f36b0657613 in g_on_error_stack_trace ()
> #2  0x0041cdb8 in ?? ()
> #3  
> #4  0x7f36ad67d067 in __GI_raise (sig=sig@entry=6)
> #5  0x7f36ad67e448 in __GI_abort () at abort.c:89
> #6  0x7f36b06a7a45 in g_assertion_message ()
> #7  0x7f36b06a7ada in g_assertion_message_expr ()
> #8  0x7f36b21ff20e in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #9  0x7f36b22e9684 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> #10 0x7f36b0958474 in ?? ()
> #11 0x7f36b0972087 in g_signal_emit_valist ()
> #12 0x7f36b0972f2a in g_signal_emit_by_name ()
> #13 0x7f36b1d2e79c in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
> #14 0x7f36b1d20e78 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
> #15 0x7f36b0682613 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #16 0x7f36b0681b6d in g_main_context_dispatch ()
> #17 0x7f36b0681f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #18 0x7f36b0681ffc in g_main_context_iteration ()
> #19 0x00418259 in ?? ()
> #20 0x004b45a4 in ?? ()
> #21 0x00421be8 in ?? ()
> #22 0x00422b6f in ?? ()
> #23 0x7f36b0681b6d in g_main_context_dispatch ()
> #24 0x7f36b0681f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> #25 0x7f36b0682272 in g_main_loop_run ()
> #26 0x7f36b21abc25 in gtk_main ()
> #27 0x00417361 in ?? ()
> #28 0x7f36ad669b45 in __libc_start_main (main=0x416c70, argc=2,
> #29 0x004180ca in ?? ()
> "
> 
> I'll be happy to report this upstream (as instructed in the crash message) if
> the maintainers desire, but won't do so unless instructed. Please let me know
> if I can provide any further information.

I think this crash should be fixed in the version testing / unstable. Could you
please test with a version from there?

Regards
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#822477: qgis: FTBFS: error: request for member 'insert' in 'qm', which is of pointer type 'QMap

[Gianfranco Costamagna]

control: tags -1 patch

Hi, I just successfully applied the upstream fix on Ubuntu and seems the 
package now builds fine.

https://github.com/qgis/QGIS/commit/fc6559aa053317cda8ced657c3013a0d4c6549e9

please consider adding this to the debian package too.

cheers,

Gianfranco



signature.asc
Description: OpenPGP digital signature

Bug#822954: [Pkg-haproxy-maintainers] Bug#822954: haproxy-1.5.8 Disable SSLv3

[Vincent Bernat]

 ❦ 29 avril 2016 14:23 +0400, "Anoop Seburuth"  :

> As Described the problem: https://www.rfc-editor.org/rfc/rfc7568.txt
> According to rfc7568, sslv3 is no longer considered secure. This patch
> disables sslv3 if the system's openssl is compiled without
> it. (Jessie)

This patch is applied in more recent versions of HAProxy. So, this fix
would be only for Jessie. I highly doubt that we could push such a patch
to a stable release. Isn't SSLv3 already not usable due to the fact it
is disabled in OpenSSL?
-- 
What I tell you three times is true.
-- Lewis Carroll


signature.asc
Description: PGP signature

Bug#821811: samba: badlock patch breaks trust relationship

[Santiago Ruano Rincón]

Dear Samba maintainers,

Any updates about this bug?

LTS Team, anyone could help to handle it?

According to comment#17 in
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1572122
Andreas Schneider prepared a fix for 3.6.25.

Cheers,

Santiago


signature.asc
Description: PGP signature

Bug#795019: Bug#822879: cableswig: switch to castxml

[Mattia Rizzolo]

[ not sure why you CCed the itk removal bug ]

On Fri, Apr 29, 2016 at 06:41:33AM -0500, Steve M. Robbins wrote:
> Actually, cableswig should also be removed.  It was only in the archive to 
> support the old insighttoolkit builds; but insighttoolkit is to be removed 
> c.f. #795019.  Nothing else depends on cableswig -- see dak output, below.

Cool, would have been helpful you have filed such RM...

FTR, itk is going to be removed pretty soon, as we managed to clear the
rdeps, as you read :)

> What's your preferred workflow here?  Shall I close this bug and open a 
> removal 
> for cableswig?

don't close this bug until it's fixed, it'll be closed by the RM once
processed.
If you think this package needs to be removed file a RM.  Since the only
rdep is insighttoolkit, that is also clear to be removed now, it's going
to be removed at the same time.

> Or will you just go ahead and remove cableswig and gccxml now?

you can't remove gccxml.
You filed a RM, but that's really not enough.  A FTP master followed up
on the bug report, but you apparently ignored the email.  All rdeps
needs to be cleared before the RM can proceed.  That means that all the
bugs I filed (you can see the blocker on your RM) need to be closed.

> GCC-XML is dead upstream and my attempt at a wrapper around CastXML was not a 
> success so IMHO it's better to remove it sooner than later.
> Its other 
> dependencies have already switched to CastXML (e.g. pygccxml) or they will 
> soon or they are also dead.

Yes, but that only happened because I filed those bugs and I'm working
on them, I'd have actually expected you do that (at least the bug
filing, not the fixing them).  I'm saying so, becuase that's true also
for other RMs of the past (like itk, indeed, where the bugs "itk is
going to be rmed, switch to itk4" have been filed by others).


For what concerns cableswig, please just ask the removal of the package,
then :)
Ahah, so easy fix :>

Thanks!
-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#822477: qgis: FTBFS: error: request for member 'insert' in 'qm', which is of pointer type 'QMap

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Gianfranco,

On 04/29/2016 02:49 PM, Gianfranco Costamagna wrote:
> Hi, I just successfully applied the upstream fix on Ubuntu and seems the 
> package now builds fine.
> 
> https://github.com/qgis/QGIS/commit/fc6559aa053317cda8ced657c3013a0d4c6549e9
> 
> please consider adding this to the debian package too.

Thanks for the patch, I'll include it in the package along with the
changes for todays 2.14.2 release.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature

Bug#822963: htop: please make the build reproducible (timestamps)

[Alexis Bienvenüe]

Source: htop
Version: 2.0.1-1
Severity: wishlist
Tags: patch upstream
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

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

The attached patch honours the SOURCE_DATE_EPOCH environment
variable [2] to get a reproducible copyright year.
Once applied, htop can be built reproducibly in our current
experimental framework.

Regards,
Alexis Bienvenüe.

 [1]: https://wiki.debian.org/ReproducibleBuilds
 [2]: https://reproducible-builds.org/specs/source-date-epoch/

diff -Nru htop-2.0.1/debian/changelog htop-2.0.1/debian/changelog
--- htop-2.0.1/debian/changelog	2016-04-14 10:26:00.0 +0200
+++ htop-2.0.1/debian/changelog	2016-04-29 14:59:30.0 +0200
@@ -1,3 +1,9 @@
+htop (2.0.1-1.0~reproducible1) UNRELEASED; urgency=medium
+
+  * Honour SOURCE_DATE_EPOCH for copyright year
+
+ -- Alexis Bienvenüe   Fri, 29 Apr 2016 14:46:35 +0200
+
 htop (2.0.1-1) unstable; urgency=medium
 
   * New upstream release 2.0.1. (Closes: #814401, #783893, #774930)
diff -Nru htop-2.0.1/debian/patches/003-honour-source-date-epoch.patch htop-2.0.1/debian/patches/003-honour-source-date-epoch.patch
--- htop-2.0.1/debian/patches/003-honour-source-date-epoch.patch	1970-01-01 01:00:00.0 +0100
+++ htop-2.0.1/debian/patches/003-honour-source-date-epoch.patch	2016-04-29 14:55:47.0 +0200
@@ -0,0 +1,18 @@
+Description: Hounour SOURCE_DATE_EPOCH
+ Honour the SOURCE_DATE_EPOCH environment variable for copyright year.
+Author: Alexis Bienvenüe 
+
+Index: htop-2.0.1/configure.ac
+===
+--- htop-2.0.1.orig/configure.ac
 htop-2.0.1/configure.ac
+@@ -4,7 +4,8 @@
+ AC_PREREQ(2.65)
+ AC_INIT([htop],[2.0.1],[his...@gobolinux.org])
+ 
+-year=$(date +%Y)
++SOURCE_DATE_EPOCH="${SOURCE_DATE_EPOCH:-$(date +%s)}"
++year=$(date -u -d "@$SOURCE_DATE_EPOCH" "+%Y" 2>/dev/null || date -u -r "$SOURCE_DATE_EPOCH" "+%Y" 2>/dev/null || date -u "+%Y")
+ 
+ # The following two lines are required by hwloc scripts
+ AC_USE_SYSTEM_EXTENSIONS
diff -Nru htop-2.0.1/debian/patches/series htop-2.0.1/debian/patches/series
--- htop-2.0.1/debian/patches/series	2016-04-14 10:22:00.0 +0200
+++ htop-2.0.1/debian/patches/series	2016-04-29 14:45:00.0 +0200
@@ -1,3 +1,4 @@
 001-lintian-warning-fix-man-typo.patch
 002-lintian-warning-fix-desktop-keywords.patch
 601-openvz-new-ctid-vpid.patch
+003-honour-source-date-epoch.patch

Bug#822964: Have to click connect twice before login dialogue opens

[Brent S. Elmer]

Package: network-manager-openconnect-gnome
Version: 1.2.0-1
Severity: normal

I just upgraded network-manager-openconnect and network-manager-openconnect-
gnome with version 1.2.0-1 that just hit stretch on 4-28-2016 from version
1.0.2-1 that was in stretch.  This was the only upgrade that I did at the time.
What I see after the upgrade is that the first time I click on connect to vpn,
the login dialogue does not appear.  I waited for a while.  When I click on it
a second time, it does appear and I can log in and connect to the vpn as usual.
I have rebooted my machine twice I tried connecting to the vpn and the same
behavior happens(i.e. the login dialogue does not open until after the 2nd time
clicked)
This behavior never happened until I upgraded to 1.2.0-1.



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

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

Versions of packages network-manager-openconnect-gnome depends on:
ii  libatk1.0-0  2.20.0-1
ii  libc62.22-7
ii  libcairo-gobject21.14.6-1+b1
ii  libcairo21.14.6-1+b1
ii  libdbus-1-3  1.10.8-1
ii  libdbus-glib-1-2 0.106-1
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.0-1
ii  libgtk-3-0   3.18.9-1
ii  libnm-glib-vpn1  1.1.94-1
ii  libnm-glib4  1.1.94-1
ii  libnm-util2  1.1.94-1
ii  libnm0   1.1.94-1
ii  libopenconnect5  7.06-2+b2
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libsecret-1-00.18.3-1
ii  libxml2  2.9.3+dfsg1-1
ii  network-manager-openconnect  1.2.0-1

network-manager-openconnect-gnome recommends no packages.

network-manager-openconnect-gnome suggests no packages.

-- no debconf information

Bug#822968: designate: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 

Package: designate 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch translation of designate debconf 
messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#822967: cinder: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 

Package: cinder 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch translation of cinder debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#822963: htop: please make the build reproducible (timestamps)

[Daniel Lange]

Control: tags -1 +pending

Hi Alexis,

that patch is from Graham (CC) and we have it both already in
https://anonscm.debian.org/cgit/collab-maint/htop.git/commit/?id=cef9e7933e5c9704eaa5a6330067967f32e52798
and sent upstream (https://github.com/hishamhm/htop/pull/476).

Were waiting for upstream to apply the patch and will make it available in 
Debian on the next release of the package.

Kind regards,
Daniel


Am 29.04.2016 um 15:05 schrieb Alexis Bienvenüe:
> Source: htop
> Version: 2.0.1-1
> Severity: wishlist
> Tags: patch upstream
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: timestamps
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> While working on the “reproducible builds” effort [1], we have noticed
> that 'htop' could not be built reproducibly.
> 
> The attached patch honours the SOURCE_DATE_EPOCH environment
> variable [2] to get a reproducible copyright year.
> Once applied, htop can be built reproducibly in our current
> experimental framework.
> 
> Regards,
> Alexis Bienvenüe.
> 
>   [1]: https://wiki.debian.org/ReproducibleBuilds
>   [2]: https://reproducible-builds.org/specs/source-date-epoch/
> 

Bug#822953: refcard: [INTL:sk] Slovak po-debconf translation

[Holger Wansing]

Hi,

helix84  wrote:
> Package: refcard
> Severity: wishlist
> Tags: l10n patch
> Version: 5.0.9
> 
> .po attached

I have built the pdf with your translation file, attached.
Please take a look, if everything is fine. 
thanks


Holger

-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/



refcard-sk-a4.pdf
Description: Adobe PDF document

Bug#822969: heat: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 

Package: heat 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch translation of heat debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#818815: oolite: FTBFS with libc 2.23: non-floating-point argument in call to function '__builtin_isfinite'

[Gianfranco Costamagna]

control: tags -1 patch

the following patch (stolen from adios similar patch) should fix the issue:
--- oolite-1.82.orig/src/Core/Scripting/OOJSPlayerShip.m
+++ oolite-1.82/src/Core/Scripting/OOJSPlayerShip.m
@@ -1496,7 +1496,7 @@ static BOOL ValidateContracts(JSContext

if (!isCargo)
{
-   if (argc > offset+5 && JS_ValueToECMAUint32(context, 
OOJS_ARGV[offset + 5], ) && isfinite(uValue))
+   if (argc > offset+5 && JS_ValueToECMAUint32(context, 
OOJS_ARGV[offset + 5], ) && isfinite((double)uValue))
{
*risk = uValue;
}


thanks for considering it,


Gianfranco
Description: fix glib-2.23 build failure

Author: Gianfranco Costamagna 

--- oolite-1.82.orig/src/Core/Scripting/OOJSPlayerShip.m
+++ oolite-1.82/src/Core/Scripting/OOJSPlayerShip.m
@@ -1496,7 +1496,7 @@ static BOOL ValidateContracts(JSContext
 
 	if (!isCargo)
 	{
-		if (argc > offset+5 && JS_ValueToECMAUint32(context, OOJS_ARGV[offset + 5], ) && isfinite(uValue))
+		if (argc > offset+5 && JS_ValueToECMAUint32(context, OOJS_ARGV[offset + 5], ) && isfinite((double)uValue))
 		{
 			*risk = uValue;
 		}


signature.asc
Description: OpenPGP digital signature

Bug#822971: dolfin: FTBFS on kfreebsd

[Mattia Rizzolo]

Source: dolfin
Version: 1.6.0-4
Control: block 822321 by -1

Since this version, with the switch to vtk6 and whatnot, dolfin FTBFS on
kfreebsd.

This unfortunately jeopardize our quest to remove vtk5 from the archive,
as the old binaries there still depends on it.

Please try to see what causes such failure and fix it.
I'm sorry I can't provide more insight.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#820977: [buildd-tools-devel] Bug#820977: sbuild: please log the dpkg-buildpackage command line options

[Ferenc Wágner]

Johannes Schauer  writes:

> Quoting Ferenc Wágner (2016-04-28 07:58:35)
>
>> While working on enabling source-only uploads for some packages, several
>> times I found myself wondering what type of (failed) build (arch-any/
>> arch-all/mixed) a given build log corresponds to.  The dpkg-buildpackage
>> options are important (and hopefully not too many), thus I find --debug too
>> heavy-handed for this.
>
> aha. So if I understand your situation correctly, you have a directory
> of build logs and you now want to figure out which build log
> corresponds to which arch-all/arch-any/whatever build?

That is a good approximation, yes.

> If that is the case, then this could be fixed by showing the values of
>
> BUILD_ARCH_ALL
> BUILD_ARCH_ANY
> BUILD_SOURCE
>
> in the log.

Yes.

> This would be more readable than printing the dpkg-buildpackage
> invocation.

I'm not sure about this one.  Maybe more readable and also less useful...

> Alternatively, this problem could also be fixed by printing the exact sbuild
> invocation into the log. Though that might not be enough because your sbuildrc
> might overwrite values.

That's exactly why I didn't propose logging the sbuild invocation.
Sbuild has too many knobs, which are also often tweaked, but are also
fairly obvious from the build log.
-- 
Regards,
Feri

Bug#822117: Update solved issue

[Jakob Wiedner]

Hi,

after the update to Linux 4.5.0-0.bpo.1-amd64 #1 SMP Debian 
4.5.1-1~bpo8+1 (2016-04-20) x86_64 the bug does not occur any longer.


Regards,
Jakob Wiedner

Bug#822953: refcard: [INTL:sk] Slovak po-debconf translation

[Holger Wansing]

Control: tags -1 + pending


helix84  wrote:
> Package: refcard
> Severity: wishlist
> Tags: l10n patch
> Version: 5.0.9
> 
> .po attached

Just committed.


-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

Bug#822966: ceilometer: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 

Package: ceilometer 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch translation of ceilometer debconf 
messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#818813: torcs: FTBFS with libc 2.23: non-floating-point argument in call to function '__builtin_isnan'

[Gianfranco Costamagna]

control: tags -1 patch

the following patch (stolen from adios similar patch) should fix the issue:
--- torcs-1.3.3+dfsg.orig/src/modules/simu/simuv2/simu.cpp
+++ torcs-1.3.3+dfsg/src/modules/simu/simuv2/simu.cpp
@@ -67,7 +67,7 @@ ctrlCheck(tCar *car)
 if (isnan(car->ctrl->brakeCmd) || isinf(car->ctrl->brakeCmd)) 
car->ctrl->brakeCmd = 0;
 if (isnan(car->ctrl->clutchCmd) || isinf(car->ctrl->clutchCmd)) 
car->ctrl->clutchCmd = 0;
 if (isnan(car->ctrl->steer) || isinf(car->ctrl->steer)) car->ctrl->steer = 
0;
-if (isnan(car->ctrl->gear) || isinf(car->ctrl->gear)) car->ctrl->gear = 0;
+if (isnan((double)car->ctrl->gear) || isinf((double)car->ctrl->gear)) 
car->ctrl->gear = 0;
 #endif

 /* When the car is broken try to send it on the track side */

cheers,

G-
Description: fix build failure with glib 2.23

Author: Gianfranco Costamagna

--- torcs-1.3.3+dfsg.orig/src/modules/simu/simuv2/simu.cpp
+++ torcs-1.3.3+dfsg/src/modules/simu/simuv2/simu.cpp
@@ -67,7 +67,7 @@ ctrlCheck(tCar *car)
 if (isnan(car->ctrl->brakeCmd) || isinf(car->ctrl->brakeCmd)) car->ctrl->brakeCmd = 0;
 if (isnan(car->ctrl->clutchCmd) || isinf(car->ctrl->clutchCmd)) car->ctrl->clutchCmd = 0;
 if (isnan(car->ctrl->steer) || isinf(car->ctrl->steer)) car->ctrl->steer = 0;
-if (isnan(car->ctrl->gear) || isinf(car->ctrl->gear)) car->ctrl->gear = 0;
+if (isnan((double)car->ctrl->gear) || isinf((double)car->ctrl->gear)) car->ctrl->gear = 0;
 #endif
 
 /* When the car is broken try to send it on the track side */


signature.asc
Description: OpenPGP digital signature

Bug#791765: Seems to be fixed in version 0.9.9

[Lars Cebulla]

Hi,

I would suggest to upgrade to version 0.9.9.

This bug seems to be fixed there. I compiled the latest version on
Jessie without any problems, it's working really nice!

Bug#822973: idjc displays "something bad happened" and doesn't start (undefined symbol: avcodec_alloc_frame)

[Frederic Peters]

Package: idjc
Version: 0.8.15-1+b1
Severity: important

Hi,

 $ idjc
jack client ID: idjc_default
something bad happened

I altered part of main.py to get a proper trace and got this:

Traceback (most recent call last):
  File "/usr/bin/idjc", line 32, in 
exit(idjc.main())
  File "/usr/lib/idjc/site-packages/idjc/__init__.py", line 119, in main
return maingui.main()
  File "/usr/lib/idjc/site-packages/idjc/maingui.py", line 3995, in main
run_instance = MainWindow()
  File "/usr/lib/idjc/site-packages/idjc/maingui.py", line 3047, in __init__
self.backend = ctypes.CDLL(FGlobs.backend)
  File "/usr/lib/python2.7/ctypes/__init__.py", line 365, in __init__
self._handle = _dlopen(self._name, mode)
OSError: /usr/lib/idjc/idjc.so: undefined symbol: avcodec_alloc_frame

The symbol was apparently marked avcodec_alloc_frame, I guess if finally
got removed in a recent ffmpeg upload.


thanks,
Fred

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

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

Versions of packages idjc depends on:
ii  jackd 5
ii  libavcodec57  7:3.0.1-3
ii  libavformat57 7:3.0.1-3
ii  libavutil55   7:3.0.1-3
ii  libc6 2.22-7
ii  libflac8  1.3.1-4
ii  libglib2.0-0  2.48.0-1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-1
ii  libmp3lame0   3.99.5+repack1-9+b1
ii  libmpg123-0   1.22.4-1
ii  libogg0   1.3.2-1
ii  libopus0  1.1.2-1
ii  libsamplerate00.1.8-8
ii  libshout-idjc32.3.1-2
ii  libsndfile1   1.0.25-10
ii  libspeex1 1.2~rc1.2-1
ii  libswresample27:3.0.1-3
ii  libvorbis0a   1.3.5-3
ii  libvorbisenc2 1.3.5-3
ii  python2.7.11-1
ii  python-dbus   1.2.4-1
ii  python-gobject3.20.0-2
ii  python-gtk2   2.24.0-4
ii  python-irc8.5.3+dfsg-2
ii  python-mutagen1.31-1
ii  python2.7 2.7.11-8
pn  python:any

Versions of packages idjc recommends:
ii  python-eyed3  0.6.18-1

idjc suggests no packages.

-- no debconf information

Bug#821687: [pkg-kolab] Bug#821687: src:libkolabxml: PHP 7.0 Transition

[Ondřej Surý]

Control: severity -1 serious

Hi Sandro,

ok then. I am setting severity to serious, so the swig related packages
doesn't block PHP 7.0 transition.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

On Fri, Apr 29, 2016, at 14:01, Sandro Knauß wrote:
> Control: block -1 821715
> 
> We need to wait till swig supports php7. See error log.
> 
> Regards,
> 
> sandro
> 
> --
> Am Montag, 18. April 2016, 23:02:29 CEST schrieb Ondřej Surý:
> > Package: src:libkolabxml
> > Severity: important
> > User: pkg-php-ma...@lists.alioth.debian.org
> > Usertags: php7.0-transition
> > 
> > Dear maintainer(s),
> > 
> > this bug is a part of ongoing php7.0 transition.  It is filled as
> > important, but the severity will be bumped to serious within quite short
> > (~month) timeframe as the transition was announced almost 3 months ago.
> > 
> > The libkolabxml package currently build-depends on php5 php5-cli
> > php5-dev .
> > 
> > PHP 7.0 has landed in unstable with substantial changes to the packaging:
> > 
> >   1. Every package built from src:phpMAJOR.MINOR now include
> >  phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.
> > 
> >   2. Accompanying src:php-defaults builds 1:1 mapping to a default
> >  MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
> >  specify a dependency, please use the generic name, unless you
> >  absolutely know that won't work for you.
> > 
> >   3. Every path in the system has been changed to a versioned, e.g.
> >  /etc/php5/cli is now /etc/php/7.0/cli
> > 
> >   4. dh_php5 is now dh_php
> > 
> >   5. php-pear is not built from independent source package.
> > 
> >   6. master-7.0 branches of several extensions (php-apcu, xdebug,
> >  php-apcu-bc) can be used as a template how to change the PHP
> >  extension packaging.  It's mostly cut since the d/rules tries
> >  to figure-out most of the variables from debian/ directory.
> > 
> >   7. pkg-php-tools package now supports PHP 7.0 packaging and if your
> >  package uses pkg-php-tools a simple binNMU is all it might need
> > 
> >   8. PHP 7.0 has changed extension API, so most-if-not-all extensions
> >  need work from upstream to be compatible with PHP 7.0.
> > 
> >   9. We expect to ship next Debian release (stretch) only with PHP
> >  7.0, that means that all packages needs to be made compatible with
> >  PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
> >  maintained software.  However some extensions has been deprecated
> >  (f.e. mysql) and thus old unmaintained software will stop working
> >  and it will have to be either patched or removed from stable Debian.
> > 
> > So what you need to do:
> > 
> > Replace every occurence of php5 with just php, e.g. if you depend on
> > 'php5' then you just need to depend on 'php'.  Also if you package a web
> > application and depend on specific SAPI, I would recommend depending just
> > on 'php' package and let the user decide whether he will install php-fpm,
> > libapache2-mod-php or php-cgi.
> > 
> > The script that was used to get the list of packages for MBF was not a
> > particular smart one (so it doesn't detect alternatives, etc.), so if
> > there's a false positive, please excuse me and just close the bug with
> > short explanation.
> > 
> > The other options that might be used with packages that don't and won't
> > support PHP 7.0 is to remove the software from Debian by changing the
> > title of this bugreport to:
> > 
> > RM: libkolabxml -- ROM; doesn't support PHP 7.0
> > 
> > reassigning it to ftp.debian.org pseudo-package and changing severity to
> > 'normal'.
> > 
> > Also feel free to contact the maintainers at one of the lists:
> > 
> > pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
> > pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
> > pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all
> > 
> > Cheers, Ondrej
> > 
> > -- System Information:
> > Debian Release: 8.4
> >   APT prefers stable-updates
> >   APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
> > 'stable') Architecture: amd64 (x86_64)
> > 
> > Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
> > Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> > 
> > 
> > ___
> > pkg-kolab-devel mailing list
> > pkg-kolab-de...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kolab-devel
> 
> Email had 2 attachments:
> + libkolabxml_1.1.2-2~_amd64.build
>   2.6M (text/plain)
> + signature.asc
>   1k (application/pgp-signature)

Bug#821686: [pkg-kolab] Bug#821686: Bug#821686: src:libkolab: PHP 7.0 Transition

[Sandro Knauß]

Control: severity -1 serious
Control: block -1 by 821687

Hi Ondřej,

also libkolab is using swig and it is blocked by libkolabxml. So setting 
severity to serious, so the swig related packages doesn't block PHP 7.0 
transition.

In both packages, all php code is translated via swig.

what is the correct way to create php modules nowadays?

debian/rules:
PHPAPI := $(shell php-config --phpapi)
[...]
override_dh_gencontrol:
echo "php:Depends=phpapi-${PHPAPI}" >> debian/php-kolab.substvars
dh_gencontrol
[...]

debian/php-kolab.install:
usr/lib/php5/*/kolabcalendaring.php usr/share/php/
usr/lib/php5/*/kolabicalendar.php usr/share/php/
usr/lib/php5/*/kolabobject.php usr/share/php/
usr/lib/php5/*/kolabshared.php usr/share/php/

I can image that, we should not move the modules to /usr/share/php/ anymore, 
to have a clear versionbased path?

Regards,

--
Am Freitag, 29. April 2016, 13:57:02 CEST schrieb Sandro Knauß:
> Control: block -1 821687
> 
> Before adding php7 support to libkolab, we need to fix libkolabxml.
> --
> 
> Am Montag, 18. April 2016, 23:02:28 CEST schrieb Ondřej Surý:
> > Package: src:libkolab
> > Severity: important
> > User: pkg-php-ma...@lists.alioth.debian.org
> > Usertags: php7.0-transition
> > 
> > Dear maintainer(s),
> > 
> > this bug is a part of ongoing php7.0 transition.  It is filled as
> > important, but the severity will be bumped to serious within quite short
> > (~month) timeframe as the transition was announced almost 3 months ago.
> > 
> > The libkolab package currently build-depends on php5 php5-cli php5-dev .
> > 
> > PHP 7.0 has landed in unstable with substantial changes to the packaging:
> >   1. Every package built from src:phpMAJOR.MINOR now include
> >   
> >  phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.
> >   
> >   2. Accompanying src:php-defaults builds 1:1 mapping to a default
> >   
> >  MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
> >  specify a dependency, please use the generic name, unless you
> >  absolutely know that won't work for you.
> >   
> >   3. Every path in the system has been changed to a versioned, e.g.
> >   
> >  /etc/php5/cli is now /etc/php/7.0/cli
> >   
> >   4. dh_php5 is now dh_php
> >   
> >   5. php-pear is not built from independent source package.
> >   
> >   6. master-7.0 branches of several extensions (php-apcu, xdebug,
> >   
> >  php-apcu-bc) can be used as a template how to change the PHP
> >  extension packaging.  It's mostly cut since the d/rules tries
> >  to figure-out most of the variables from debian/ directory.
> >   
> >   7. pkg-php-tools package now supports PHP 7.0 packaging and if your
> >   
> >  package uses pkg-php-tools a simple binNMU is all it might need
> >   
> >   8. PHP 7.0 has changed extension API, so most-if-not-all extensions
> >   
> >  need work from upstream to be compatible with PHP 7.0.
> >   
> >   9. We expect to ship next Debian release (stretch) only with PHP
> >   
> >  7.0, that means that all packages needs to be made compatible with
> >  PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
> >  maintained software.  However some extensions has been deprecated
> >  (f.e. mysql) and thus old unmaintained software will stop working
> >  and it will have to be either patched or removed from stable Debian.
> > 
> > So what you need to do:
> > 
> > Replace every occurence of php5 with just php, e.g. if you depend on
> > 'php5' then you just need to depend on 'php'.  Also if you package a web
> > application and depend on specific SAPI, I would recommend depending just
> > on 'php' package and let the user decide whether he will install php-fpm,
> > libapache2-mod-php or php-cgi.
> > 
> > The script that was used to get the list of packages for MBF was not a
> > particular smart one (so it doesn't detect alternatives, etc.), so if
> > there's a false positive, please excuse me and just close the bug with
> > short explanation.
> > 
> > The other options that might be used with packages that don't and won't
> > support PHP 7.0 is to remove the software from Debian by changing the
> > 
> > title of this bugreport to:
> > RM: libkolab -- ROM; doesn't support PHP 7.0
> > 
> > reassigning it to ftp.debian.org pseudo-package and changing severity to
> > 'normal'.
> > 
> > Also feel free to contact the maintainers at one of the lists:
> > 
> > pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
> > pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
> > pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all
> > 
> > Cheers, Ondrej
> > 
> > -- System Information:
> > Debian Release: 8.4
> > 
> >   APT prefers stable-updates
> >   APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
> > 
> > 'stable') Architecture: amd64 (x86_64)
> > 
> > Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
> > Locale: 

Bug#617296: Status of ITP: libjs-ace -- standalone code editor for the web ?

[Andreas Tille]

Hi,

since besides the existing code copies of ace in

  graphite-web
  libswagger2-perl
  owncloud
  ruby-ace-rails-ap

there is another candidate rstudio (#617296) which has a minimised copy
of ace.  So I wonder what might be the status of the ace ITP and whether
there is some packaging repository to look at.  If you ask me using

   git://anonscm.debian.org/pkg-javascript

would be a good idea.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#822965: neutron: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 

Package: neutron 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch translation of neutron debconf messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#822970: openstack-trove: [INTL:nl] Dutch translation of debconf messages

[Frans Spiesschaert]

 

Package: openstack-trove 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch translation of openstack-trove debconf 
messages. 
It has been submitted for review to the debian-l10n-dutch mailing list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
=== 

-- 
Cheers,
Frans

===
http://home.base.be/vt6362833/



nl.po.gz
Description: application/gzip


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

Bug#822972: audioread: version bump

[Nico Schlömer]

Package: python-audioread
Version: version bump (2.1.2)
Severity: wishlist

The audioread version shipped with Debian is rather old now (1.0.2). The latest
release (from Jan 2016) is 2.1.2. Please bump.



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

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

Bug#686653: HP Deskjet broken in Wheezy

[Brian Potkin]

found 686653 cups/2.1.3-5
thanks



Established a queue with f300_series-hpijs on Jessie. Ugpraded the machine
to unstable. The PPD changed to f300 Series, hpcups 3.16.3

Regards,
 
Brian.

Bug#822974: backport for jessie

[Robert Lange]

I have made such a backport in my personal Jessie backports repo. I used the 
source packages from testing (and maybe unstable, if a package was not in 
testing, but I think all relevant packages are in testing now). The process was 
complicated b/c I needed to backport dpkg and debhelpers and a bunch of others 
in order to satisfy the dependency chain and build dependency chain. However, 
after compiling around 10ish source packages, everything worked. I've been 
tracking and keeping up w/ changes, and so far I have not had any problems, 
with the following caveats.

One major issue with an official backport is that GnuPG 2.1 breaks backward 
compatibility with the key format of previous versions. This is not a problem 
if you can use gpg2 for everything, but if you still need gpg1 for some things, 
then you will have to manually keep 2 copies of your keychain in sync; the old 
1.x format and the 2.1 format. Every time you import or sign a new key, you 
will have to remember to do the operation with both gpg and gpg2. For me, I 
have been able to live with 2.1 only, but others may not be able to.

This is made somewhat more complicated by the fact that many Debian admin and 
build scripts currently still default to invoke gpg instead of gpg2. I had to 
set some environment variables to get some scripts to use gpg2, and I think I 
had to set up a diversion for some other scripts that are currently hard-coded 
to use gpg instead of gpg2. (I am not at home currently, so I can't be more 
exact.) There were some warnings about gpg2 having possibly incompatible 
command line arguments and maybe some scripts breaking as a result of this, but 
so far I have not noticed any problems from this.

Anyway, upgrading my personal machines to GnuPG 2.1 was interesting and 
rewarding, but given the above, I would say that doing this in the official 
backports repo would cause a lot of problems, especially with that special 
breed of user who upgrades first and reads the notes later.

--Robert Lange


On 16-04-29, Daniel Pocock   wrote:
> Package: gnupg2
> Version: 2.1.11-7
> Severity: wishlist
> 
> Please consider providing a gnupg2 2.1.x backport in jessie-backports or
> comment if it is not feasible.
> 
> I came across some comments about it here:
> 
> https://lists.gnupg.org/pipermail/gnupg-users/2015-June/053772.html
> 
> 
> 

Bug#821686: [pkg-kolab] Bug#821686: Bug#821686: src:libkolab: PHP 7.0 Transition

[Ondřej Surý]

Hi Sandro,

I recently rewrote the packaging of external PECL module to a single
makefile snippet[1], but I guess this is probably usable only for pure
PECL modules.

Generally speaking:

echo 'extension=kolab.so' > debian/kolab.ini
echo 'mod debian/kolab.ini' > debian/php-kolab.php

install the kolab.so module to the correct place /usr/lib/php//

Using /usr/share/php/ for PHP code is fine.

and then have something like this in d/rules:

%:
dh $@ --with php

override_dh_php:
dh_php -p php-kolab

and build-depend on dh-php.

I can help you with that if you want after swig supports PHP 7.0, just
ping me.

1. http://anonscm.debian.org/cgit/pkg-php/dh-php.git/tree/pkg-pecl.mk

^^^ This is more complicated than Debian really needs because I need
support for multiple PHP versions as I maintain PHP 5.5, 5.6 and 7.0 in
external-Debian and PPA repositories.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

On Fri, Apr 29, 2016, at 14:51, Sandro Knauß wrote:
> Control: severity -1 serious
> Control: block -1 by 821687
> 
> Hi Ondřej,
> 
> also libkolab is using swig and it is blocked by libkolabxml. So setting 
> severity to serious, so the swig related packages doesn't block PHP 7.0 
> transition.
> 
> In both packages, all php code is translated via swig.
> 
> what is the correct way to create php modules nowadays?
> 
> debian/rules:
> PHPAPI := $(shell php-config --phpapi)
> [...]
> override_dh_gencontrol:
> echo "php:Depends=phpapi-${PHPAPI}" >> debian/php-kolab.substvars
> dh_gencontrol
> [...]
> 
> debian/php-kolab.install:
> usr/lib/php5/*/kolabcalendaring.php usr/share/php/
> usr/lib/php5/*/kolabicalendar.php usr/share/php/
> usr/lib/php5/*/kolabobject.php usr/share/php/
> usr/lib/php5/*/kolabshared.php usr/share/php/
> 
> I can image that, we should not move the modules to /usr/share/php/
> anymore, 
> to have a clear versionbased path?
> 
> Regards,
> 
> --
> Am Freitag, 29. April 2016, 13:57:02 CEST schrieb Sandro Knauß:
> > Control: block -1 821687
> > 
> > Before adding php7 support to libkolab, we need to fix libkolabxml.
> > --
> > 
> > Am Montag, 18. April 2016, 23:02:28 CEST schrieb Ondřej Surý:
> > > Package: src:libkolab
> > > Severity: important
> > > User: pkg-php-ma...@lists.alioth.debian.org
> > > Usertags: php7.0-transition
> > > 
> > > Dear maintainer(s),
> > > 
> > > this bug is a part of ongoing php7.0 transition.  It is filled as
> > > important, but the severity will be bumped to serious within quite short
> > > (~month) timeframe as the transition was announced almost 3 months ago.
> > > 
> > > The libkolab package currently build-depends on php5 php5-cli php5-dev .
> > > 
> > > PHP 7.0 has landed in unstable with substantial changes to the packaging:
> > >   1. Every package built from src:phpMAJOR.MINOR now include
> > >   
> > >  phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.
> > >   
> > >   2. Accompanying src:php-defaults builds 1:1 mapping to a default
> > >   
> > >  MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
> > >  specify a dependency, please use the generic name, unless you
> > >  absolutely know that won't work for you.
> > >   
> > >   3. Every path in the system has been changed to a versioned, e.g.
> > >   
> > >  /etc/php5/cli is now /etc/php/7.0/cli
> > >   
> > >   4. dh_php5 is now dh_php
> > >   
> > >   5. php-pear is not built from independent source package.
> > >   
> > >   6. master-7.0 branches of several extensions (php-apcu, xdebug,
> > >   
> > >  php-apcu-bc) can be used as a template how to change the PHP
> > >  extension packaging.  It's mostly cut since the d/rules tries
> > >  to figure-out most of the variables from debian/ directory.
> > >   
> > >   7. pkg-php-tools package now supports PHP 7.0 packaging and if your
> > >   
> > >  package uses pkg-php-tools a simple binNMU is all it might need
> > >   
> > >   8. PHP 7.0 has changed extension API, so most-if-not-all extensions
> > >   
> > >  need work from upstream to be compatible with PHP 7.0.
> > >   
> > >   9. We expect to ship next Debian release (stretch) only with PHP
> > >   
> > >  7.0, that means that all packages needs to be made compatible with
> > >  PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
> > >  maintained software.  However some extensions has been deprecated
> > >  (f.e. mysql) and thus old unmaintained software will stop working
> > >  and it will have to be either patched or removed from stable Debian.
> > > 
> > > So what you need to do:
> > > 
> > > Replace every occurence of php5 with just php, e.g. if you depend on
> > > 'php5' then you just need to depend on 'php'.  Also if you package a web
> > > application and depend on specific SAPI, I would recommend depending just
> > > on 'php' package and let the user decide whether he will 

Bug#796633: nbd-client: Has init script in runlevel S but no matching service file

[Wouter Verhelst]

On Thu, Apr 28, 2016 at 10:13:52AM -0300, Felipe Sateler wrote:
> On 28 April 2016 at 09:26, Alkis Georgopoulos  wrote:
> Wouter wrote:
> > The reason nbd is in runlevel S is because it needs to run before
> > mountnfs.sh, otherwise filesystems won't be mounted properly.
> 
> What does this mean? Will nfs filesystems not be mounted, or
> nbd-backed filesystems not be mounted properly?

It means nbd-backed filesystems won't be mounted when not using systemd
and not using the proper dependency headers, because insserv places the
init script either too early (when there is no network) or too late
(when the mountnfs.sh init script has already tried and failed to mount
nbd-backed filesystems, which are marked with _netdev in fstab).

> > The init
> > script has a line "X-Start-Before: mountnfs" to enforce that. It could
> > work if either Ubuntu doesn't support non-systemd installs anymore, or
> > if mountnfs (or its systemd equivalent) has been moved out of S as well.
> 
> Systemd provides a symlink from mountnfs to /dev/null, thus it no
> longer exists. So this invariant is broken anyway. However, systemd
> mounts asynchronously as devices appear, so maybe the broken invariant
> is not problematic when running under systemd.

Possibly, but the dependency on $network is still required, and the
X-Start-Before line and (thus) the S runlevel specification is still
required for non-systemd installs, too.

If ubuntu no longer supports non-systemd installs (I don't know whether
that's the case), then given all the above, dropping the S runlevel and
removing the X-Start-Before header *should* work. However, the
dependency on $network must remain (otherwise the script will be started
before the server is accessible).

Ideally, the patches that are referred to in Debian #812485 and #812487
are applied to ubuntu's udev and kernel, although this is not crucial
(udev already manages to discover when an nbd device is connected, so
boot will work, it's just that discovery of disconnects is broken).

With these changes, booting the system *should* work (although I haven't
tested any of the above, so please do). Shutdown might be a different
matter.

Doing all this *will* break non-systemd installs, however. If that's
okay as a tradeoff, then you could do that.

Also, I don't know what the policy is on updates to a just-released LTS
Ubuntu, so maybe that's a blocker? If not, it's my hope to get a
properly working systemd boot by the end of debcamp at the latest, so
maybe you can fix it by updating to the then-current version of nbd in
Debian unstable if no issues are found in Debian after a while.

-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
   people in the world who think they really understand all of its rules,
   and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12

Bug#806108: singular: FTBFS due to indep build failure

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,

I upgraded (again) because the then last package (4.0.3-p1+ds-1) was non-usable:
working on this issue was then my highest priority. I thought that I could
postpone this issue, but I was wrong (obviously).

Whatever, I fixed by forcing a complete build.
I am on my way to submit the new package *4.0.3-p1+ds-2).

Cheers,
Jerome

On 29/04/16 10:36, Santiago Vila wrote:
> severity 806108 important
> thanks
>
> Hi. I *really* appreciate that you consider this has a greater severity
> than "important", but I prefer to keep it important for two reasons:
>
> * I don't have the "blessing" (so to speak) from the release managers
>   to make these bugs RC yet.
>
> * If this is serious, all the other similar bugs should be serious too.
>   Here is the complete list of similar bugs:
>
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=binary-indep;users=sanv...@debian.org
>
>
> Well, those are my reasons, but of course if you insist that this must
> be serious, go ahead. I promise that I will not downgrade it again,
> otherwise it would be a very odd severity war indeed: Maintainer
> raises severity and reporter downgrades it :-)
>
> Thanks.
>
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJXI3s2AAoJEIC/w4IMSybj4FEIALt14ADF/mlQyyBashkqeRi+
DANq2IiGX98MkbXpZiZI6EJG1GBZJcifx+1Pqfk8ht8Vk+ZYqreCCymzR4ukw2dY
4Mia1+CqtrhgnQ3z3nbm5kmTXN13jDwinK9mawycvWYVOW6hlbaYw1XHqWO4WAfr
a42bhLhqXVrIVN2OBe3NZfl/QImzRb1+H3B3ydyr71V1A7O0VLUC74qA4kvr81d2
+EJfkaHvzSgk7RYPqjuba5YgQzWMW7zMafOy1DMOqpWECcjoSwr8mXMkk1Q2qmno
uAPriagKIpV+M2zBJN9XxReQlnTqjjP0Ni2Emdwk0PK2w2bTHKVVER9au5/x0Gc=
=rWFS
-END PGP SIGNATURE-

Bug#822974: backport for jessie

[Daniel Pocock]

Package: gnupg2
Version: 2.1.11-7
Severity: wishlist

Please consider providing a gnupg2 2.1.x backport in jessie-backports or
comment if it is not feasible.

I came across some comments about it here:

https://lists.gnupg.org/pipermail/gnupg-users/2015-June/053772.html

Bug#822973: idjc displays "something bad happened" and doesn't start (undefined symbol: avcodec_alloc_frame)

[Sebastian Ramacher]

Control: tags -1 + confirmed upstream
Control: severity -1 + grave

On 2016-04-29 15:51:52, Frederic Peters wrote:
> Package: idjc
> Version: 0.8.15-1+b1
> Severity: important
> 
> Hi,
> 
>  $ idjc
> jack client ID: idjc_default
> something bad happened
> 
> I altered part of main.py to get a proper trace and got this:
> 
> Traceback (most recent call last):
>   File "/usr/bin/idjc", line 32, in 
> exit(idjc.main())
>   File "/usr/lib/idjc/site-packages/idjc/__init__.py", line 119, in main
> return maingui.main()
>   File "/usr/lib/idjc/site-packages/idjc/maingui.py", line 3995, in main
> run_instance = MainWindow()
>   File "/usr/lib/idjc/site-packages/idjc/maingui.py", line 3047, in __init__
> self.backend = ctypes.CDLL(FGlobs.backend)
>   File "/usr/lib/python2.7/ctypes/__init__.py", line 365, in __init__
> self._handle = _dlopen(self._name, mode)
> OSError: /usr/lib/idjc/idjc.so: undefined symbol: avcodec_alloc_frame
> 
> The symbol was apparently marked avcodec_alloc_frame, I guess if finally
> got removed in a recent ffmpeg upload.

From the build log:

avcodec_encoder.c: In function 'live_avcodec_encoder_main':
avcodec_encoder.c:145:42: warning: implicit declaration of function 
'avcodec_alloc_frame' [-Wimplicit-function-declaration]

And later:

dpkg-shlibdeps: warning: debian/idjc/usr/lib/idjc/idjc.so contains an 
unresolvable reference to symbol avcodec_alloc_frame: it's probably a plugin

Well, it's not. Raising the severity accordingly.

Regards
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#822941: debian-installer: cannot boot installed on VirtualBox with EFI-enabled

[Roger Shimizu]

Dear Yamane-san,

Thanks for your report!

On Fri, Apr 29, 2016 at 5:33 PM, Hideki Yamane  wrote:
> Package: debian-installer
> Severity: important
>
> Dear Maintainer,
>
>  I found user notes Debian on VBox with EFI enabled environment cannot
>  boot, see http://qiita.com/zakuro9715/items/45e82473ce39914e04ed (in 
> Japanese)
>
>  I've confirmed it with d-i9 alpha5.
>  And, it doesn't happen with Fedora 24 alpha and Ubuntu 16.04.
>
>
> Step to reproduce:
>
>  1. setup Virtualbox VM with EFI enabled
>  2. install Debian
>  3. after installation, turn of VM
>  4. turn on VM again
>  5. not bootable, startup EFI shell

It's very like bug#821341 [0]
Please double confirm whether you use GPT partition.
Thank you!

[0] https://bugs.debian.org/821341

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 17B3ACB1

Bug#681726: eclipse: Upgrade Eclipse to Juno 4.2

[Peter Spiess-Knafl]

Hi!

I would also like to know what is exactly the problem that prevents
upgrading to a more recent version of Eclipse?

I think it would be really worth putting effort into getting the latest
version (or at least a more recent version form 4.x) of eclipse into the
next release of Debian.

I could not find an RFH bug for Eclipse but I think one should be filed,
because the current version, even in unstable, is almost four years old.

Greetings
Peter

Bug#822893: mutt-patched: nntp no longer working

[James McCoy]

Control: tag -1 patch

On Thu, Apr 28, 2016 at 09:13:08PM +0200, Reiner Herrmann wrote:
> But I also just saw in git that it has been disabled, because it
> doesn't build. :(
> It would be awesome if you could get it running again! :)

Agreed.  I took a quick look and the attached patch fixes the build.  I
haven't had a chance to do any testing yet, but thought I'd send this in
case it helps.

Cheers,
James
diff --git a/debian/patches/mutt-patched/nntp.patch b/debian/patches/mutt-patched/nntp.patch
index 8dc1de0..fc0ca34 100644
--- a/debian/patches/mutt-patched/nntp.patch
+++ b/debian/patches/mutt-patched/nntp.patch
@@ -1471,7 +1471,19 @@ diff --git a/compose.c b/compose.c
 index 42bdb46..01c79ce 100644
 --- a/compose.c
 +++ b/compose.c
-@@ -84,6 +84,16 @@ static const char * const Prompts[] =
+@@ -38,6 +38,11 @@
+ #include "remailer.h"
+ #endif
+ 
++#ifdef USE_NNTP
++#include "mx.h"
++#include "nntp.h"
++#endif
++
+ #include 
+ #include 
+ #include 
+@@ -84,6 +89,16 @@ static const char * const Prompts[] =
"Subject: ",
"Reply-To: ",
"Fcc: "

Bug#822977: RM: pyplusplus -- RoQA; orphaned; dead upstream; marginal popcon; RC buggy

[Mattia Rizzolo]

package: ftp.debian.org

please remove pyplusplus from the archive.
The maintainer lost insterest in the package pretty much right after the
first upload, and later orphaned it.

Upstream is dead, and even if a fork seems to exist, I'd say there is no
point in keeping this package.  Also, it's blocking gccxml removal.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#822978: ITP: puppet-module-puppetlabs-concat -- construct files from multiple ordered fragments of text

[Thomas Goirand]

Package: wnpp
Severity: wishlist
Owner: Thomas Goirand 

* Package name: puppet-module-puppetlabs-concat
  Version : 2.1.0
  Upstream Author : Morgan Haskel 
* URL : https://github.com/puppetlabs/puppetlabs-concat
* License : Apache-2.0
  Programming Lang: Ruby, Perl
  Description : construct files from multiple ordered fragments of text

 Puppet lets you centrally manage every important aspect of your system using a
 cross-platform specification language that manages all the separate elements
 normally aggregated in different files, like users, cron jobs, and hosts,
 along with obviously discrete elements like packages, services, and files.
 .
 This module gathers concat::fragment resources from other modules and order
 them into a coherent file through a single concat resource.

Bug#822666: linux-headers-3.16.0-4-amd64: deprecated syntax in linux-headers Makefile

[Thierry Herbelot]

Dear maintainer,

We would like that the fix applied to the 4.5.2-1 package is also 
applied to the stable jessie version of debian:


When we are building our out-of-tree kernel modules, the error due to 
the Debian Makefile is generating false alarms (the Makefile error is 
essentially noise in our build logs, which would be great if it were 
removed).


Best regards

Thierry

--
Thierry Herbelot
6WIND
Software Engineer