Bug#823995: game-data-packager: new version of Pyflakes3 complains when checking command_line.py

[Alexandre Detiste]

Package: game-data-packager
Version: 44
Severity: normal


Is this a bug in GDP or Pyflakes3 ?

---

$for f in game_data_packager/*.py; do echo $f; pyflakes3 $f; done

game_data_packager/command_line.py
Traceback (most recent call last):
  File "/usr/bin/pyflakes3", line 9, in 
load_entry_point('pyflakes==1.2.2', 'console_scripts', 'pyflakes')()
  File "/usr/lib/python3/dist-packages/pyflakes/api.py", line 184, in main
warnings = checkRecursive(args, reporter)
  File "/usr/lib/python3/dist-packages/pyflakes/api.py", line 141, in
checkRecursive
warnings += checkPath(sourcePath, reporter)
  File "/usr/lib/python3/dist-packages/pyflakes/api.py", line 108, in checkPath
return check(codestr, filename, reporter)
  File "/usr/lib/python3/dist-packages/pyflakes/api.py", line 69, in check
w = checker.Checker(tree, filename)
  File "/usr/lib/python3/dist-packages/pyflakes/checker.py", line 416, in
__init__
self.handleChildren(tree)
  File "/usr/lib/python3/dist-packages/pyflakes/checker.py", line 738, in
handleChildren
self.handleNode(node, tree)
  File "/usr/lib/python3/dist-packages/pyflakes/checker.py", line 785, in
handleNode
handler(node)
  File "/usr/lib/python3/dist-packages/pyflakes/checker.py", line 1164, in
IMPORTFROM
node.module, alias.name)
  File "/usr/lib/python3/dist-packages/pyflakes/checker.py", line 212, in
__init__
full_name = module + '.' + self.real_name
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'



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

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

Versions of packages game-data-packager depends on:
ii  fakeroot1.20.2-1
ii  python3 3.5.1-3
ii  python3-debian  0.1.27
ii  python3-yaml3.11-3+b1
pn  python3:any 

game-data-packager recommends no packages.

Versions of packages game-data-packager suggests:
ii  arj   3.10.22-14
ii  binutils  2.26-8
ii  cabextract1.6-1
ii  cdparanoia3.10.2+debian-11
ii  dynamite  0.1.1-2
ii  gcc   4:5.3.1-1
pn  gdebi | gdebi-kde 
ii  gir1.2-gdkpixbuf-2.0  2.34.0-1
ii  gir1.2-gtk-3.03.20.3-2
ii  gir1.2-pango-1.0  1.40.1-1
ii  innoextract   1.6-1
ii  lgc-pg1.3.1-1
ii  lgogdownloader2.28-1
ii  lhasa [lzh-archiver]  0.3.1-1
ii  make  4.1-9
ii  p7zip-full15.14.1+dfsg-1
ii  python3-gi3.20.1-1
ii  steam 1.0.0.52-1
ii  steamcmd  0~20130205-1
ii  unace-nonfree 2.5-8
ii  unar  1.9.1-1
ii  unrar 1:5.3.2-1
ii  unshield  1.0-1
ii  unzip 6.0-20
ii  vorbis-tools  1.4.0-8
ii  xdelta1.1.3-9.1

-- debconf-show failed

Bug#823993: [buildd-tools-devel] Bug#823993: sbuild: bad foreach when reading the list of foreign architectures

[Johannes Schauer]

Hi,

Quoting Adam Borowski (2016-05-11 05:32:57)
> When there's actually a foreign arch configured, I get:
> 
> [~]# sbuild-update -udcar unstable-arm64
> Use of uninitialized value $_ in scalar chomp at 
> /usr/share/perl5/Sbuild/ResolverBase.pm line 192.
> unstable-arm64: Performing update.
> (..., all ok, exit status 0)
> [~]# chroot /srv/sbuild/unstable-arm64/
> (unstable-arm64-sbuild)root@umbar:/# dpkg --print-foreign-architectures
> amd64
> (unstable-arm64-sbuild)root@umbar:/#
> 
> And the code in question is:
> foreach my $arch (split /\s+/, $foreignarchs) {
> chomp;
> next unless $_;
> $set{$_} = 1;
> }
> 
> Note "my $arch" vs "$_".

thanks for finding this!

Indeed I did not test on chroots which already have foreign architectures from
the start as sbuild will be adding the required architectures itself.

I'm planning to upload a new Debian revision today with some patches from the
git master branch.  I assume you'd like me to make the fix for this part of
that upload because it otherwise pollutes stderr?

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#823968: squid3: CVE-2016-4553 CVE-2016-4554 CVE-2016-4555 CVE-2016-4556

[Salvatore Bonaccorso]

Hi Amos,

On Wed, May 11, 2016 at 03:12:14PM +1200, Amos Jeffries wrote:
> 
> CVE-2016-4553:
>  Patch for 3.4 and older is now available at
> .
> 
> CVE-2016-4554:
>  Additional changes are needed than those initially linked to. see the
> advisory URL for updated patch links.
> 
> CVE-2016-4555:
>  Squid-3.1 in wheezy is not affected.
> 
> CVE-2016-4556:
>  Patch for 3.4 should also apply fairly easily to 3.1, but has not been
> tested.
>  Also, the severity of this issue is much reduced for Debian since SSL
> is not enabled.
>  Though it still remains an issue for CDN and reverse-proxy installations.
> 
> 
> HTH

Yes, thanks for your feedback.

Regards,
Salvatore

Bug#823897: [buildd-tools-devel] Bug#823897: sbuild-createchroot: Failed to set root: ownership on /.../usr/sbin/policy-rc.d

[Johannes Schauer]

Control: tag -1 + pending

Hi Tianon,

Quoting Tianon Gravi (2016-05-10 08:15:05)
> Running "sbuild-createchroot unstable" fails setting permissions:

thanks a lot for your very detailed bug report and investigating the problem
already!

You are indeed right and the problem is now fixed in git and will be fixed in
unstable with the upload of the next Debian revision.

Thank you!

cheers, josch


signature.asc
Description: signature

Bug#823984: libarchive13/unstable is older than libarchive13/stable

[Salvatore Bonaccorso]

Hi,

On Wed, May 11, 2016 at 02:52:08AM +0200, Vincent Lefevre wrote:
> Package: libarchive13
> Version: 3.1.2-11+b1
> Severity: grave
> Justification: renders package unusable
> 
> libarchive13 from unstable is now older than the version from stable
> (due to a security update). Thus it is no longer installable, because
> the version from stable (which is selected by default) cannot be
> installed in unstable:
> 
> libarchive13 : Depends: libnettle4 (>= 2.3) but it is not going to be 
> installed

Please see #823893 for why this has not yet seen as well an update in
unstable.

Regards,
Salvatore

Bug#823977: cmake-fedora: Typo in package description

[陳昌倬]

Control: tags -1 newcomer

On Tue, May 10, 2016 at 11:13:36PM +0200, Thomas Vincent wrote:
> Package: cmake-fedora
> Severity: minor
> 
> Dear Maintainer,
> 
> I believe I spotted a typo while translating the description of cmake-fedora.
> Indeed, in the short description, "that simply the release process" should be 
> corrected into "that simplify the release process".

Thanks for the report. I think it is suitable for a new contributor.

-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D
  BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#823994: libwacom2-udeb: uninstallable, depends on non-udeb libgudev-1.0-0

[Cyril Brulebois]

Package: libwacom2-udeb
Version: 0.19-1
Severity: important

[ X-D-Cc: debian-b...@lists.debian.org, please keep it in copy
  when replying. ]

Hi,

As a follow-up to the just-closed #815717, where libinput10-udeb should
become installable once rebuilt against newest libwacom (which now has
an udeb), well, this won't work yet. :)

libwacom2-udeb depends on libgudev-1.0-0, which isn't an udeb, so
neither of libinput10-udeb, libwacom2-udeb, or x-x-i-libinput-udeb are
going to be installable.

(See e.g.: https://d-i.debian.org/dose/graph-unstable-amd64.png)

Thanks for your time.


KiBi.

Bug#823881: dosfstools: mmd fails right after mkfs.msdos (sectors/tracks mismatch)

[Cyril Brulebois]

[ Poke Steve. ]

Andreas Bombe  (2016-05-11):
> On Tue, May 10, 2016 at 02:15:42PM +0200, Andreas Bombe wrote:
> > Since 416 blocks is a rather odd value, the default is used and that has
> > changed. I think mtools is overzealous in checking those values and
> > refusing to work. Still, it probably makes sense to use 64/32 as the
> > default for smaller filesystem sizes (up to 512 MB possibly) and I'll
> > prepare a version that implements this.
> 
> Uploading this now.
> 
> As far as I'm concerned, I consider this an aesthetic change. There is
> still no guarantee that the total number of sectors is a multiple of
> sectors per track. It just happens to work with the current values.

Steve → we probably don't want to be hardcoding such things in so many
places right? 3 calls in src:debian-installer, plus debian-cd, and maybe
others?

> If you want to make this robust, you'll either have to explicitly
> specify matched size/sectors/heads on the command line to mkfs.msdos or
> disable the bogus mtools check like everyone else does when encountering
> that error.

Thanks for your input and the proposed change.

I think Steven mentioned (when we first diagnosed this) a possibly
bogus/overzealous check on mtools side as well. You seem to agree. So,
if this check is bogus, why not fix it/remove it upstream then?

> Seriously, searching for that error message in your favorite search
> engine will give you pages upon pages of hits, all of them describing
> how to turn it off.

Seriously, I read the man^Winfo page and implemented a workaround in
src:debian-installer already.

I filed this against dosfstools anyway to make sure our findings /
intuitions were correct.

Thanks for the swift replies.


KiBi.


signature.asc
Description: Digital signature

Bug#823993: sbuild: bad foreach when reading the list of foreign architectures

[Adam Borowski]

Package: sbuild
Version: 0.69.0-1
Severity: normal

When there's actually a foreign arch configured, I get:

[~]# sbuild-update -udcar unstable-arm64
Use of uninitialized value $_ in scalar chomp at 
/usr/share/perl5/Sbuild/ResolverBase.pm line 192.
unstable-arm64: Performing update.
(..., all ok, exit status 0)
[~]# chroot /srv/sbuild/unstable-arm64/
(unstable-arm64-sbuild)root@umbar:/# dpkg --print-foreign-architectures
amd64
(unstable-arm64-sbuild)root@umbar:/#

And the code in question is:
foreach my $arch (split /\s+/, $foreignarchs) {
chomp;
next unless $_;
$set{$_} = 1;
}

Note "my $arch" vs "$_".


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

Kernel: Linux 4.6.0-rc7-debug+ (SMP w/6 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 sbuild depends on:
ii  adduser 3.114
ii  apt-utils   1.2.11
ii  libsbuild-perl  0.69.0-1
ii  perl5.22.2-1

Versions of packages sbuild recommends:
ii  debootstrap  1.0.81
ii  fakeroot 1.20.2-1

Versions of packages sbuild suggests:
pn  deborphan  
ii  wget   1.17.1-2

-- no debconf information

Bug#823968: squid3: CVE-2016-4553 CVE-2016-4554 CVE-2016-4555 CVE-2016-4556

[Amos Jeffries]

CVE-2016-4553:
 Patch for 3.4 and older is now available at
.

CVE-2016-4554:
 Additional changes are needed than those initially linked to. see the
advisory URL for updated patch links.

CVE-2016-4555:
 Squid-3.1 in wheezy is not affected.

CVE-2016-4556:
 Patch for 3.4 should also apply fairly easily to 3.1, but has not been
tested.
 Also, the severity of this issue is much reduced for Debian since SSL
is not enabled.
 Though it still remains an issue for CDN and reverse-proxy installations.


HTH
Amos

Bug#823552: endless "supply vcc not found, using dummy regulator"

[Ben Hutchings]

On Wed, 2016-05-11 at 01:49 +0200, Steinar H. Gunderson wrote:
> On Thu, May 05, 2016 at 11:29:18PM +0200, Steinar H. Gunderson wrote:
> > 
> > I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid 
> > and
> > installing 4.5.0-2-armmp-lpae (and generating the uInitrd myself, and 
> > updating
> > boot.ini -- I'm not entirely sure if this can be done more automatically), 
> > the
> > serial console shows tens of thousands of these messages on boot:
> > 
> > [   47.161428] exynos-dwc3 usb@1200: no suspend clk specified   
> > 
> > [   47.162811] usb_phy_generic.49646.auto supply vcc not found, using dummy 
> > regulator 
> > [   47.163532] usb_phy_generic.49647.auto supply vcc not found, using dummy 
> > regulator
> I've reproduced this on 4.6.0-rc7. Should I take it upstream, or are there
> still worries that this might be Debian-specific?

It might well be a bug in our configuration, but then you can easily
provide that to upstream.

Ben.

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

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

Bug#823986: installation-reports: "hardware" errors on virtualbox

[Jose R R]

"02:29 < kilobyte> reproduced in virtualbox: lots of I/O errors: ata1.00:
  failed command: WRITE FPDMA QUEUED"

As I frequently test Reiser4-enabled unstable Debian-Installers on
VirtuaBox 5.0.16 (my latest version), on a frequent basis I come
across similar I/O errors: ata related as well as some other
idiosyncrasies related to unstable nature of my d-i builds. Wait a few
days for the debian-installer component UDEBs to stabilize and work
better together --in harmony-- then try your installation again.


On Tue, May 10, 2016 at 6:27 PM, Adam Borowski  wrote:
> Package: installation-reports
> Severity: normal
>
>
> 00:37 < calops> hi, is there any known issue about the testing installer
> (netinst and CD) failing around the "selecting packages"
> step?
> 00:39 < calops> it happens to me both natively on my machine, and as a
> virtualbox guest
> 01:35 < Sledge> calops: anything in syslog?
> 02:29 < kilobyte> reproduced in virtualbox: lots of I/O errors: ata1.00:
>   failed command: WRITE FPDMA QUEUED
>
> Syslog attached.  The failed step was "Select and install software", no
> error message was given other than "installation step failed".
>
> No hardware or software errors on the host, other VMs work fine, so this is
> not a fault of the new version of virtualbox (current unstable --
> 5.0.20-dfsg-1).  And that calops guy reports it's failing on bare metal too.
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (150, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.6.0-rc6-debug2+ (SMP w/6 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)



-- 
Jose R R
http://metztli.it
-
Try at no charge http://b2evolution.net for http://OpenShift.com PaaS
-
from our GitHub http://Nepohualtzintzin.com repository. Cloud the easy way!
-

Bug#823881: dosfstools: mmd fails right after mkfs.msdos (sectors/tracks mismatch)

[Andreas Bombe]

On Tue, May 10, 2016 at 02:15:42PM +0200, Andreas Bombe wrote:
> Since 416 blocks is a rather odd value, the default is used and that has
> changed. I think mtools is overzealous in checking those values and
> refusing to work. Still, it probably makes sense to use 64/32 as the
> default for smaller filesystem sizes (up to 512 MB possibly) and I'll
> prepare a version that implements this.

Uploading this now.

As far as I'm concerned, I consider this an aesthetic change. There is
still no guarantee that the total number of sectors is a multiple of
sectors per track. It just happens to work with the current values.

If you want to make this robust, you'll either have to explicitly
specify matched size/sectors/heads on the command line to mkfs.msdos or
disable the bogus mtools check like everyone else does when encountering
that error.

Seriously, searching for that error message in your favorite search
engine will give you pages upon pages of hits, all of them describing
how to turn it off.


Andreas

Bug#823992: ITP: python-scruffy -- framework for taking care of a bunch of boilerplate in Python apps

[陳昌倬]

Package: wnpp
Severity: wishlist
Owner: "ChangZhuo Chen (陳昌倬)" 

* Package name: python-scruffy
  Version : 0.3.3
  Upstream Author : snare
* URL : https://github.com/snare/scruffy
* License : Expat
  Programming Lang: Python
  Description : framework for taking care of a bunch of boilerplate in 
Python apps

 Scruffy is a framework for taking care of a bunch of boilerplate in
 Python apps. It handles the loading of configuration files, the loading
 and management of plugins, and the management of other filesystem
 resources such as temporary files and directories, log files, etc.
 .
 A typical use case for Scruffy is a command-line Python tool with some
 or all of the following requirements:
 .
  * Read a set of configuration defaults
  * Read a local configuration file and apply it on top of the defaults
  * Allow overriding some configuration options with command line flags
or at runtime
  * Load a core set of Python-based plugins
  * Load a set of user-defined Python-based plugins
  * Generate log files whose name, location and other logging settings
are based on configuration
  * Store application state between runs in a file or database

-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D
  BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#823991: libpng16-16: generates a ton of noisy warnings

[Daniel Kahn Gillmor]

Package: libpng16-16
Version: 1.6.21-4
Control: affects -1 wine32 wine64

wine32 and wine64 are super noisy, even when the command they run does
nothing; they complain repeatedly to stderr about a modified version of
libpng.  this probably affects other programs that were built against
libpng12 and are now running against libpng16, too.

0 dkg@alice:~/tmp$ wine32 dir
Executing wine (wineserver64) 1.8.1 on Debian stretch/sid (amd64).
If something goes wrong, please rerun with "WINEDEBUG=err+all wine"
for more detailed debugging output.
fixme:service:scmdatabase_autostart_services Auto-start service L"MountMgr" 
failed to start: 2
wine: cannot find L"C:\\windows\\system32\\dir.exe"
2 dkg@alice:~/tmp$ libpng warning: Application built with libpng-1.2.54 but 
running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 0x80004005 initializing encoder
libpng warning: Application built with libpng-1.2.54 but running with 1.6.21
err:menubuilder:convert_to_native_icon error 

Bug#823990: dh_gconf no longer needs to add gconf2 dependency to misc:Depends?

[Ari Pollak]

Package: debhelper
Version: 9.20160403
Severity: wishlist

dh_gconf still adds gconf2 to ${misc:Depends}, but AFAICT that's a legacy
holdout and is no longer needed anymore. The gconf2 package uses triggers to
update its database with new schemas; if you install gconf2, it will
rebuild the database from scratch anyway. So for something like pidgin, which
adds URL handlers to gconf (not used by GNOME 3 anyway) but doesn't need gconf
for normal operation, that's just an extraneous dependency that just seems to
irritate certain users.


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

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

Versions of packages debhelper depends on:
ii  autotools-dev20160430.1
ii  binutils 2.26-8
ii  dh-autoreconf12
ii  dh-strip-nondeterminism  0.016-1
ii  dpkg 1.18.4
ii  dpkg-dev 1.18.4
ii  file 1:5.25-2
ii  libdpkg-perl 1.18.4
ii  man-db   2.7.5-1
ii  perl 5.22.2-1
ii  po-debconf   1.0.19

debhelper recommends no packages.

Versions of packages debhelper suggests:
ii  dh-make  2.201605

-- no debconf information

Bug#823989: gnome-software: ignores packages that are on hold

[Paul Wise]

Package: gnome-software
Version: 3.20.2-2
Severity: normal

I put a package on hold but the Updates tab says there is one update
and the OS Updates dialog lists the package that has been held.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (860, 'testing-proposed-updates'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-software depends on:
ii  appstream0.9.5-1
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-1
ii  gnome-software-common3.20.2-2
ii  gsettings-desktop-schemas3.20.0-3
ii  libappstream-glib8   0.5.14-3
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  libenchant1c2a   1.6.0-11
ii  libfwupd10.7.0-1
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.0-1
ii  libgnome-desktop-3-123.20.1-1
ii  libgtk-3-0   3.20.3-2
ii  libgtkspell3-3-0 3.0.8-1
ii  libjson-glib-1.0-0   1.2.0-1
ii  liblimba00.5.6-1
ii  libpackagekit-glib2-18   1.1.0-2
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpolkit-gobject-1-00.105-15
ii  libsoup2.4-1 2.54.1-1
ii  libsqlite3-0 3.12.2-1
ii  packagekit   1.1.0-2

gnome-software recommends no packages.

Versions of packages gnome-software suggests:
ii  fwupd  0.7.0-1
pn  limba  

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#712841: A bit late, but still an issue...

[Martin Michlmayr]

* Christian Mueller  [2016-05-10 18:57]:
> That would be great. You mean customise.conf, correct? Anything I can do to
> help?

No, I meant uLinux.conf.  There should be a [System] stanza with
information such as

Model = TS-219
Internal Model = TS-219

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#797942: sentinella: build-depends on obsolete kdebase-workspace-dev

[Eriberto Mota]

Hi all,

We will wait for a new upstream version up to October 2016. After
this, will be needed ask for a removal from Debian.

Thanks!

Regards,

Eriberto

Bug#823988: ITP: gitsome -- Supercharged Git/Shell Autocompleter with GitHub Integration

[陳昌倬]

Package: wnpp
Severity: wishlist
Owner: "ChangZhuo Chen (陳昌倬)" 

* Package name: gitsome
  Version : 0.4.0
  Upstream Author : Donne Martin
* URL : https://github.com/donnemartin/gitsome
* License : Apache
  Programming Lang: Python
  Description : Supercharged Git/Shell Autocompleter with GitHub Integration

 gitsome aims to supercharge the standard git/shell interface by
 focusing on:
 .
  * Improving ease-of-use
  * Increasing productivity
 .
 Also, gitsome provides direct integration with GitHub.

-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D
  BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#823987: systemd: after upgrading some libs, login takes much longer until systemd-logind is restarted

[Christoph Anton Mitterer]

Something that happened before sometimes (but not always), just
happened again.

I tried to restart systemd-logind, which sometimes just worked and
fixed the issue:
# systemctl restart systemd-logind.service 
Job for systemd-logind.service failed because a timeout was exceeded. See 
"systemctl status systemd-logind.service" and "journalctl -xe" for details.
~# systemctl status systemd-logind.service
● systemd-logind.service - Login Service
   Loaded: loaded (/lib/systemd/system/systemd-logind.service; static; vendor 
preset: enabled)
   Active: activating (start) since Wed 2016-05-11 03:30:14 CEST; 1min 20s ago
 Docs: man:systemd-logind.service(8)
   man:logind.conf(5)
   http://www.freedesktop.org/wiki/Software/systemd/logind
   http://www.freedesktop.org/wiki/Software/systemd/multiseat
 Main PID: 3611 (systemd-logind)
   Status: "Processing requests..."
Tasks: 1 (limit: 512)
   CGroup: /system.slice/systemd-logind.service
   └─3611 /lib/systemd/systemd-logind

May 11 03:30:14 kronecker systemd[1]: Starting Login Service...
May 11 03:30:14 kronecker systemd-logind[3611]: New seat seat0.
May 11 03:30:14 kronecker systemd-logind[3611]: New session 385 of user root.
May 11 03:30:14 kronecker systemd-logind[3611]: New session 393 of user root.
May 11 03:30:14 kronecker systemd-logind[3611]: New session 388 of user root.
May 11 03:30:14 kronecker systemd-logind[3611]: New session 391 of user root.
May 11 03:30:14 kronecker systemd-logind[3611]: New session 386 of user root.


journalctl spits out this, when doing the restart:
May 11 03:28:43 kronecker systemd[1]: Stopped Login Service.
May 11 03:28:43 kronecker systemd[1]: Starting Login Service...
May 11 03:28:43 kronecker systemd-logind[3594]: New seat seat0.
May 11 03:28:43 kronecker systemd[1]: Started User Manager for UID 0.
May 11 03:28:43 kronecker systemd-logind[3594]: New session 386 of user root.
May 11 03:28:43 kronecker systemd-logind[3594]: New session 393 of user root.
May 11 03:28:43 kronecker systemd-logind[3594]: New session 385 of user root.
May 11 03:28:43 kronecker systemd-logind[3594]: New session 391 of user root.
May 11 03:28:43 kronecker systemd-logind[3594]: New session 388 of user root.
May 11 03:28:46 kronecker systemd[1]: Time has been changed
May 11 03:28:46 kronecker systemd[22063]: Time has been changed
May 11 03:28:46 kronecker systemd[1]: apt-daily.timer: Adding 9h 38min 
56.244716s random time.

smime.p7s
Description: S/MIME cryptographic signature

Bug#823987: systemd: after upgrading some libs, login takes much longer until systemd-logind is restarted

[Christoph Anton Mitterer]

Package: systemd
Version: 229-5
Severity: normal


Hi.

This issue happens since quote a while (> 1 year?).

When "some" packages are upgraded, logins, at least via ssh, are considerably
delayed.

journalctl output when trying to log in via ssh:
May 11 03:03:43 kronecker sshd[3051]: Postponed publickey for root from 
2001:[snipsnap] port 44890 ssh2 [preauth]
May 11 03:03:43 kronecker sshd[3051]: Accepted publickey for root from 
2001:[snipsnap] port 44890 ssh2: ED25519 SHA256:[snipsnap]
May 11 03:03:43 kronecker sshd[3051]: pam_unix(sshd:session): session opened 
for user root by (uid=0)
May 11 03:03:43 kronecker systemd-logind[2552]: New session 386 of user root.
May 11 03:04:04 kronecker systemd[1]: systemd-logind.service: Start operation 
timed out. Terminating.
May 11 03:04:04 kronecker systemd[1]: Failed to start Login Service.
May 11 03:04:04 kronecker sshd[3051]: pam_systemd(sshd:session): Failed to 
create session: Message recipient disconnected from message bus without replying
May 11 03:04:04 kronecker systemd[1]: systemd-logind.service: Unit entered 
failed state.
May 11 03:04:04 kronecker systemd[1]: systemd-logind.service: Failed with 
result 'timeout'.
May 11 03:04:04 kronecker systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
May 11 03:04:04 kronecker systemd[1]: Stopped Login Service.
May 11 03:04:04 kronecker systemd[1]: Starting Login Service...
May 11 03:04:04 kronecker systemd-logind[3054]: New seat seat0.
May 11 03:04:04 kronecker systemd[1]: Started User Manager for UID 0.
May 11 03:04:04 kronecker systemd-logind[3054]: New session 331 of user root.
May 11 03:04:04 kronecker systemd-logind[3054]: New session 386 of user root.
May 11 03:04:04 kronecker systemd-logind[3054]: New session 385 of user root.


I think to remeber that it also happened on local logins, but I couldn't
reproduce this anymore right now.

In the current case I've had these packages upgraded:
[UPGRADE] gcc-6-base:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] lib32atomic1:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] lib32cilkrts5:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] lib32gcc1:amd64 1:6.1.1-1 -> 1:6.1.1-2
[UPGRADE] lib32gomp1:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] lib32itm1:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] lib32quadmath0:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] lib32stdc++6:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] lib32ubsan0:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libatomic1:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libcc1-0:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libcilkrts5:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libgcc1:amd64 1:6.1.1-1 -> 1:6.1.1-2
[UPGRADE] libgfortran3:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libgomp1:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libgpg-error0:amd64 1.22-1 -> 1.22-2
[UPGRADE] libitm1:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] liblsan0:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libobjc4:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libquadmath0:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libsctp1:amd64 1.0.16+dfsg-3 -> 1.0.17+dfsg-1
[UPGRADE] libstdc++6:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libtsan0:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libubsan0:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libwacom-common:amd64 0.18-1 -> 0.19-1
[UPGRADE] libwacom2:amd64 0.18-1 -> 0.19-1
[UPGRADE] libx32atomic1:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libx32cilkrts5:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libx32gcc1:amd64 1:6.1.1-1 -> 1:6.1.1-2
[UPGRADE] libx32gomp1:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libx32itm1:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libx32quadmath0:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libx32stdc++6:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] libx32ubsan0:amd64 6.1.1-1 -> 6.1.1-2
[UPGRADE] lksctp-tools:amd64 1.0.16+dfsg-3 -> 1.0.17+dfsg-1

... before, logins worked without delay.


After upgrading, needrestart proposed a number of services
to be restarted, which yield in this:
May 11 03:02:33 kronecker systemd[1]: Stopping LSB: Start/stop apache2 web 
server...
May 11 03:02:33 kronecker systemd[1]: Stopping BIND Domain Name Server...
May 11 03:02:33 kronecker systemd[1]: Stopping D-Bus System Message Bus...
May 11 03:02:33 kronecker systemd[1]: Stopping Fail2Ban Service...
May 11 03:02:33 kronecker systemd[1]: Stopping A distributed, fault-tolerant 
Jabber/XMPP server...
May 11 03:02:33 kronecker systemd[1]: Stopped D-Bus System Message Bus.
May 11 03:02:33 kronecker systemd[1]: Stopping LSB: Start NTP daemon...
May 11 03:02:33 kronecker systemd[1]: Started D-Bus System Message Bus.
May 11 03:02:33 kronecker systemd[1]: Failed to subscribe to NameOwnerChanged 
signal for 'org.freedesktop.login1': Device or resource busy
May 11 03:02:33 kronecker systemd[1]: systemd-logind.service: Service has no 
hold-off time, scheduling restart.
May 11 03:02:33 kronecker systemd[1]: Stopped BIND Domain Name Server.
May 11 03:02:33 kronecker systemd[1]: Stopping OpenBSD Secure Shell server...
May 11 03:02:33 kronecker systemd[1]: Stopping Self Monitoring and Reporting 
Technology (SMART) Daemon...
May 11 03:02:33 kronecker systemd[1]: Stopping LSB: lm-sensors daemon...
May 11 03:02:33 kronecker systemd[1]: 

Bug#804944: dtach seems broken on arm64

[Ned T. Crigler]

On Wed, May 04, 2016 at 09:01:35PM +0200, Stefan Völkel wrote:
> I can reproduce the problem inside a chroot without /dev/pts mounted. Once I
> mount /dev/pts the error is gone.
> 
> I'd say lets go with the patch.

Thanks. I've applied the patch and released dtach version 0.9.

-- 
Ned T. Crigler

Bug#823985: ITP: quasselc -- C Library for connecting to Quassel cores

[Jelmer Vernooij]

Package: wnpp
Severity: wishlist
Owner: "Jelmer Vernooij" 

* Package name: quasselc
  Version : 0.0.0
  Upstream Author : Pierre-Hugues Husson 
* URL : https://github.com/phhusson/quasselc
* License : GPLv3
  Programming Lang: C
  Description : Library for connecting to Quassel cores

This library provides an API for connecting to Quassel servers (cores).

It is used by the Quassel plugin for irssi.
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745371)

Bug#823984: libarchive13/unstable is older than libarchive13/stable

[Vincent Lefevre]

Package: libarchive13
Version: 3.1.2-11+b1
Severity: grave
Justification: renders package unusable

libarchive13 from unstable is now older than the version from stable
(due to a security update). Thus it is no longer installable, because
the version from stable (which is selected by default) cannot be
installed in unstable:

libarchive13 : Depends: libnettle4 (>= 2.3) but it is not going to be installed

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/8 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 libarchive13 depends on:
ii  libacl1 2.2.52-3
ii  libattr11:2.4.47-2
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.22-7
ii  liblzma55.1.1alpha+20120614-2.1
ii  liblzo2-2   2.08-1.2
ii  libnettle6  3.2-1
ii  libxml2 2.9.3+dfsg1-1
ii  zlib1g  1:1.2.8.dfsg-2+b1

libarchive13 recommends no packages.

Versions of packages libarchive13 suggests:
pn  lrzip  

-- no debconf information

Bug#823978: [pkg-boost-devel] Bug#823978: libboost-regex1.58.0: Boost somehow mixes up c_regex_traits and cpp_regex_traits

[Dimitri John Ledkov]

On 10 May 2016 at 22:27, Gert Wollny  wrote:
> Package: libboost-regex1.58.0
> Version: 1.58.0+dfsg-5+b1
> Severity: important
>
> Dear maintainer,
>
> when compiling src:mrs with g++-6 I get unresolved symbols
>
> /usr/bin/c++ -o mrs -I. obj/M6Server.o [...] -lboost_regex [...]
>
> obj/M6Server.o: In function
> `boost::cpp_regex_traits::transform_primary[abi:cxx11](char const*, char
> const*) const':
> /usr/include/boost/regex/v4/cpp_regex_traits.hpp:965: undefined reference to
> `boost::re_detail::cpp_regex_traits_implementation::transform_primary[abi:cxx11](char
> const*, char const*) const'
> obj/M6Server.o: In function
> `boost::cpp_regex_traits::transform[abi:cxx11](char const*, char const*)
> const':
> /usr/include/boost/regex/v4/cpp_regex_traits.hpp:961: undefined reference to
> `boost::re_detail::cpp_regex_traits_implementation::transform[abi:cxx11](char
> const*, char const*) const'
> ...
>
> now in the symbol table I get
> objdump --dynamic-syms libboost_regex.so.1.58.0 \
>  | c++filt \
>  | sed -e "s/^[0-9a-f]* *\([A-Za-z]\) *D[A-Z] \.[a-z]*/\1/" \
>  | sed -e "s/[0-9a-f]*  Base *//" | grep "transform_primary"
>
> g boost::c_regex_traits::transform_primary[abi:cxx11](wchar_t const*,
> wchar_t const*)
> w
> boost::re_detail::cpp_regex_traits_implementation::transform_primary(wchar_t
> const*, wchar_t const*) const
> w
> boost::re_detail::cpp_regex_traits_implementation::transform_primary(char
> const*, char const*) const
> g boost::c_regex_traits::transform_primary[abi:cxx11](char const*, char
> const*)
>
> i.e. the symbols are not available.
>
> Given
> http://www.boost.org/doc/libs/1_58_0/libs/regex/doc/html/boost_regex/ref/regex_traits.html
>
> I thought compiling with -DBOOST_REGEX_USE_C_LOCALE would get me somewhere, 
> but
> then I get a lot more missing symbols, and they are all without the 
> [abi:cxx11]
> tag.
>
>
> src:mrs requires -std=c++11, but I assume for the boost package the g++ 
> default
> was used, and with g++-5 this is -std=c++03, therefore, final guess is that
> there is a problem with compiling boost with -std=c++11 and then linking
> against a boost library that was compiled with -std=c++03.
>

g++-5 defaults are "funny" - it's using c++11 ABI for libstdc++ yet 98
standards for the code.
With gcc++-6 everything is bumped - "The default mode for C++ is now
-std=gnu++14 instead of -std=gnu++98."

With gcc++-6 i think we will need to compile boost with gcc++-6 and
then recompile the world with against the new libraries. Have you
tried that?

Regards,

Dimitri.

>
> Best,
> Gert
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
> (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages libboost-regex1.58.0 depends on:
> ii  libc6   2.22-7
> ii  libgcc1 1:6-20160117-1
> ii  libicu5555.1-7
> ii  libstdc++6  6-20160117-1
>
> libboost-regex1.58.0 recommends no packages.
>
> libboost-regex1.58.0 suggests no packages.
>
> -- no debconf information
>
> ___
> pkg-boost-devel mailing list
> pkg-boost-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boost-devel



-- 
Regards,

Dimitri.

Bug#783250: /sbin/btrfs: btrfs check consumes too much memory

[Nicholas D Steeves]

Hi Chris,

I'm not sure when it will be ready, but it looks like Qu Wenruo is
working on this upstream:

[PATCH RFC 00/16] Introduce low memory usage btrfsck mode
https://www.spinics.net/lists/linux-btrfs/msg54480.html

Cheers,
Nicholas

Bug#823639: Bump lshw version to B.02.18

[Bob Bib]

control: notfound -1 B.02.18
control: found -1 02.17-1.1

JFR:
http://www.ezix.org/project/wiki/HardwareLiSter#Download
http://www.ezix.org/download/?package=lshw.ezix.org

--
Best wishes,
Bob

Bug#823953: inkscape: PDF+Latex export completely broken

[Mattia Rizzolo]

control: tag -1 upstream
control: notfound -1 0.91-5~bpo8+1
control: found -1 0.91-5
control: forwarded -1 https://qbugs.launchpad.net/inkscape/+bug/1417470

On Tue, May 10, 2016 at 11:05:43AM -0600, Daniel Blaschke wrote:
> Package: inkscape
> Version: 0.91-5~bpo8+1

bpo bugs are not to be sent to the Debian BTS.
But given that this issue actually affects also the regular release,
tweaking the version.

> see also the according launchbad bug report:
> https://bugs.launchpad.net/ubuntu/+bug/1417470

So this is an upstream bug.
Marking as so (but using the /inkscape/ part of the bug, instead of the
ubuntu one.  Also I added a Debian task to the LP bug, pointing to this
very bug.

-- 
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#823983: kfreebsd-10.3: hangs at boot mounting root ZFS pool

[Steven Chamberlain]

Package: src:kfreebsd-10
Version: 10.3~svn297264-1~debug1
Severity: important
Tags: experimental

I have a few systems running this kernel, amd64 arch, having a ZFS
root filesystem.  Most are working fine, but one in particular
hangs at boot, right after kernel message "Mounting root/root..." or
similar.

The boot partition is plain UFS.  GRUB doesn't need to access the
ZFS pool during boot, although it is able to.  d-i can mount the pool
and that way I was able to revert back to 10.1 kernel, which is fine.

The pool is comprised of only one device, which is an msdos primary
partition.  System has only 1GiB RAM which may be relevant, though
with 10.1 it had been stable for months.

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

Kernel: kFreeBSD 10.3-0-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#823978: [pkg-boost-devel] Processed: re: mrs: FTBFS with GCC 6: was not declared in this scope

[Steve M. Robbins]

Hi Gert,

Boost 1.58 (and 1.60) is compiled with the default gcc (currently 5) and 
default gcc flags.  For gcc 5, this means the C++03 api.

So if mrs requires -std=c++11, I think you're out of luck with Debian's boost, 
until it is built with -std=c++11.  At least, this is my understanding.  
Appreciate confirmation or refutation from more knowledgeable folks!

-Steve


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

Bug#823552: endless "supply vcc not found, using dummy regulator"

[Steinar H. Gunderson]

On Thu, May 05, 2016 at 11:29:18PM +0200, Steinar H. Gunderson wrote:
> I'm installing an ODROID XU4 (Exynos 5422-based). After upgrading it to sid 
> and
> installing 4.5.0-2-armmp-lpae (and generating the uInitrd myself, and updating
> boot.ini -- I'm not entirely sure if this can be done more automatically), the
> serial console shows tens of thousands of these messages on boot:
> 
> [   47.161428] exynos-dwc3 usb@1200: no suspend clk specified 
>   
> [   47.162811] usb_phy_generic.49646.auto supply vcc not found, using dummy 
> regulator 
> [   47.163532] usb_phy_generic.49647.auto supply vcc not found, using dummy 
> regulator

I've reproduced this on 4.6.0-rc7. Should I take it upstream, or are there
still worries that this might be Debian-specific?

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#733467: libglib2.0-0: Multi-arch: can't install armel package on an amd64 box

[Michael Biebl]

Control: tags -1 + moreinfo

On Sat, 28 Dec 2013 18:25:09 -0800 Dima Kogan  wrote:
> Package: libglib2.0-0
> Severity: normal
> 
> Hi. This may be a qemu bug intead of a libglib2.0-0 bug; I can't tell
> without digging.
> 
> I have an amd64 Debian/sid box with armel architecture support (via
> multi-arch). I am unable to install the armel libglib2.0-0 package; the
> postinst script runs out of memory on my machine; I have 4GB of RAM, so
> this really shouldn't happen.
> 
> The specific command in the postinst that eats the RAM is
> 
>  /usr/lib/arm-linux-gnueabi/glib-2.0/glib-compile-schemas 
> /usr/share/glib-2.0/schemas

Sounds like a qemu issue to me. I haven't heard of such a bug report on
a native armel system.
Is this bug still reproducible?


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



signature.asc
Description: OpenPGP digital signature

Bug#726078: libglib2.0-bin: conffiles not removed

[Michael Biebl]

Control: tags -1 + moreinfo

On Sat, 12 Oct 2013 10:35:25 +0800 Paul Wise  wrote:
> Package: libglib2.0-bin
> Version: 2.38.0-1
> Severity: normal
> User: debian...@lists.debian.org
> Usertags: obsolete-conffile adequate
> 
> The recent upgrade did not deal with obsolete conffiles properly.


> $ pkg=libglib2.0-bin ; adequate $pkg ; dpkg-query -W -f='${Conffiles}\n' $pkg 
> | grep obsolete
> libglib2.0-bin: obsolete-conffile 
> /etc/bash_completion.d/gsettings-bash-completion.sh
> libglib2.0-bin: obsolete-conffile 
> /etc/bash_completion.d/gresource-bash-completion.sh
> libglib2.0-bin: obsolete-conffile 
> /etc/bash_completion.d/gdbus-bash-completion.sh
>  /etc/bash_completion.d/gsettings-bash-completion.sh 
> 912020ee60c5011d69c46fdefbbc1ef5 obsolete
>  /etc/bash_completion.d/gresource-bash-completion.sh 
> 305f04df5006e28bbee350d1f9f7f973 obsolete
>  /etc/bash_completion.d/gdbus-bash-completion.sh 
> 3c6022ac0bf85f2f374358a52456e803 obsolete

We do ship this code in debian/libglib2.0-bin.maintscript

rm_conffile /etc/bash_completion.d/gsettings-bash-completion.sh 2.33.3-1~
rm_conffile /etc/bash_completion.d/gresource-bash-completion.sh 2.33.3-1~
rm_conffile /etc/bash_completion.d/gdbus-bash-completion.sh 2.33.3-1~

Those were added in

glib2.0 (2.33.3-1) experimental; urgency=low

  * New upstream release.
  * debian/libglib2.0-0.symbols: Add new symbols from this release.
  * debian/libglib2.0-bin.install: bash completion is now installed into
/usr/share/bash-completion/completions/ by upstream.
  * Add debian/libglib2.0-bin.maintscript: Clean up old bash completion
…

So I'm curious why those conffiles were not removed in your case.
From which version to which version did you upgrade?

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



signature.asc
Description: OpenPGP digital signature

Bug#823982: debootstrap: --variant=fakechroot fails when host system does not have dbus installed

[Daniel Kahn Gillmor]

Package: debootstrap
Version: 1.0.81
Severity: wishlist
Control: affects -1 fakechroot dbus debirf

On a very minimal/lean system running debian sid, i tried to do the
following as a non-privileged user:

  fakechroot fakeroot /usr/sbin/debootstrap --variant=fakechroot --include=dbus 
sid ~/target

the result was a failed install:

 [...]
W: Failure while configuring base packages.  This will be re-attempted up to 
five times.
W: See /home/dkg/target/debootstrap/debootstrap.log for details (possibly the 
package dbus is at fault)
1 dkg@demo:~$ 


looking in ~/target/debootstrap/debootstrap.log shows the following
error message repeated five times:

1 dkg@demo:~$ tail -n 6 ~/target/debootstrap/debootstrap.log 
Setting up dbus (1.10.8-1) ...
dbus-uuidgen: error while loading shared libraries: libdbus-1.so.3: cannot open 
shared object file: No such file or directory
dpkg: error processing package dbus (--configure):
 subprocess installed post-installation script returned error exit status 127
Errors were encountered while processing:
 dbus
0 dkg@demo:~$ 



weirdly, dbus-uuidgen works fine under fakeroot and fakechroot, which is
what makes me suspect debootstrap being the cause of the problem:


0 dkg@demo:~$ fakechroot fakeroot chroot ~/target dbus-uuidgen
c53d40afb5e8a5a5788f7c4e573267bf
0 dkg@demo:~$ 


This also has an effect on debirf, since debirf depends on debootstrap's
fakechroot functionality to build an iso as a non-privileged user.


This is reproducible from an amd64 host system with the following packages:

0 dkg@demo:~$ dpkg -l fakeroot fakechroot debootstrap libdbus-1-3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  debootstrap1.0.81   all  Bootstrap a basic Debian system
ii  fakechroot 2.18-1   all  gives a fake chroot environment -
ii  fakeroot   1.20.2-1 amd64tool for simulating superuser pri
dpkg-query: no packages found matching libdbus-1-3
1 dkg@demo:~$ 

   --dkg


signature.asc
Description: PGP signature

Bug#823981: RFS: aiksaurus/1.2.1+dev-0.12-6.3 [RC] [NMU] -- an English-language thesaurus

[Fabian Wolff]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for an update of the aiksaurus package.

The aiksaurus package currently has one RC bug because its
debian/rules file is still using dh_desktop, which has been obsolete
since 2009. I rewrote the rules file so that it now uses a more modern
"dh" style.

I also updated debian/copyright to follow the machine-readable format
and applied a variety of other changes to fix all 4 errors and 70
warnings that Lintian reported.

Here is the build log for amd64:

  https://bitbucket.org/snippets/f-w/eKxrB

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

  https://mentors.debian.net/package/aiksaurus

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

  dget -x 
https://mentors.debian.net/debian/pool/main/a/aiksaurus/aiksaurus_1.2.1+dev-0.12-6.3.dsc

Changes since the last upload:

  * Rewrite and clean up debian/rules (Closes: #817290 #821961).
  * Fix all Lintian warnings and errors.
  * Install libAiksaurus[GTK]-1.2.so instead of libAiksaurus[GTK].so.
  * Upgrade to source format 3.0 (quilt) and Standards version 3.9.8.

The change listed as the third bullet point was necessary to fix a
certain Lintian warning. This did indeed change the soname, but since
aiksaurus currently has no reverse dependencies, I do not think that
this is a problem.

Regards,
Fabian Wolff

Bug#823980: udev: setting udev_log="debug" in /etc/udev/udev.conf == 90 second hang during boot

[Daniel Kahn Gillmor]

Package: udev
Version: 229-5
Severity: normal

I put udev_log="debug" into /etc/udev/udev.conf to try to understand
part of what udev is doing.  Then i needed to reboot my computer (for
other reasons).

Normal bootup is quite fast.  But right when the transition from the
initramfs to the regular system would normally happen, i see something
like this:

[***   ] (1 of 4) A start job is running for dev-sda1.device (16s / 1min 30s)

And it cycles through multiple "start jobs", each of them a .device
job.  after the designated timeout elapses, i'm given a chance to
enter into the emergency mode.  (even more problematically, on systems
where the keyboard is only available via USB, i can't enter the root
password or hit ^D to get past the emergency mode prompt).

From emergency mode, "systemctl default" brings up the system as
usual, with no problems.  If i remove udev_log="debug" from
/etc/udev/udev.conf and reboot, i don't have this hang on boot.

the systems i've tested this on all tend to use lvm, fwiw.  some of
them use encrypted volumes, some do not.  I haven't tested it on
systems without lvm yet.

My initramfs is built with dracut 044+38-1, using the standard debian
kernel hooks, in case it matters.  I see the issue when the system
udev.conf has the debug line in it -- it doesn't seem to matter
whether the udev.conf in the initramfs has the debug line or not.

not sure how to better understand or debug this (let alone fix it),
but i'm open to suggestions.

--dkg

-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages udev depends on:
ii  adduser  3.114
ii  dpkg 1.18.4
ii  libacl1  2.2.52-3
ii  libblkid12.28-1
ii  libc62.22-7
ii  libkmod2 22-1.1
ii  libselinux1  2.5-2
ii  libudev1 229-5
ii  lsb-base 9.20160110
ii  procps   2:3.3.11-3
ii  util-linux   2.28-1

udev recommends no packages.

udev suggests no packages.

Versions of packages udev is related to:
ii  systemd  229-5


signature.asc
Description: PGP signature

Bug#823906: apt-cudf: unable to find a solution with an out-of-date chroot

[Aurelien Jarno]

On 2016-05-10 20:48, Ralf Treinen wrote:
> Hi,
> 
> On Tue, May 10, 2016 at 11:18:56AM +0200, Aurelien Jarno wrote:
> 
> > We use sbuild wit the cudf resolver on the build daemons, with the
> > following optimization criteria:
> > 
> >   $aspcud_criteria = 
> > '-removed,-changed,-new,-count(solution,APT-Release:=/experimental/)';
> > 
> > Unfortunately this doesn't work when the available packages are newer
> > than the one installed in the chroots.
> 
> That is very strange. As a first remark, the optimisation criterion should
> not be at stake here. The optimisation criterion cannot make the search for
> a solution fail in case there is a solution, the criterion only
> serves to decide which solution to select in case there are several
> solutions.

Confirmed, I am able to reproduce the problem with only 'apt-get
--solver aspcud build-dep qgis'. Note that 'apt-get build-dep qgis'
succeed.

> > This can also be reproduced using the following command:
> > 
> > | apt-get --solver aspcud -o 'APT::Solver::Strict-Pinning=false' -o 
> > 'APT::Solver::aspcud::Preferences=-removed,-changed,-new,-count(solution,APT-Release:=/experimental/)'
> >  build-dep qgis
> 
> A quick test on my home machine does not reproduce the error. Anyway, I guess
> you have to specify that you want to satisfy the build-dependencies of
> qgis/experimental, I guess ?

I have been able to reproduce the problem on mips, but we have seen the
problem on various architectures, though for different packages, so
probably with different conditions. I am able to reproduce the problem
even with only unstable in the sources.list.

Unfortunately it seems that qgis build dependencies are currently not
available on amd64. I'll try to see if I see a similar issue on amd64 or
i386, try to reproduce it and report it here.

Thanks,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#804531: eagle: cannot be rebuilt against libssl1.0.2

[Scott Howard]

Thank you Sebastian,

On Mon, May 9, 2016 at 6:14 PM, Sebastian Andrzej Siewior
 wrote:
> On 2016-04-22 00:19:58 [+0200], Andreas Beckmann wrote:
>> Since the only API/ABI difference between libssl1.0.0 and libssl1.0.2 is
>> the removal of some symbols, you could try the following:
> …
>
> | $ readelf -a bin/eagle|grep -i SSLv3
> |09aa3640  00019607 R_386_JUMP_SLOT      SSLv3_client_method
> |09aa36ec  0001c207 R_386_JUMP_SLOT      SSLv3_server_method
> |   406:  0 FUNCGLOBAL DEFAULT  UND SSLv3_client_method
> |   450:  0 FUNCGLOBAL DEFAULT  UND SSLv3_server_method
>
> Haven't tried it but it seems that the binary uses the removed symbols.
>
> Besides I looked at the license [0]:
> - 2.1.b says "not to … vary or modify the Software" so I think the
>   change of libssl1.0.0 -> .2 is not permitted.

I agree with this assessment. I'll raise the issue upstream. It's
non-free, so not too high on my priority list (and not much I can do
on my own anyways...)

Thanks, everyone.
~Scott

Bug#823518: wwwconfig-common: Apache 2 conf.d Fails - Not Configured on Jessie

[Rob McAninch]

Sorry, I'm just learning about some of these things. I think the wiki
document is here:
https://wiki.debian.org/Apache/PackagingFor24

But basically what used to go in the conf.d/ now goes in
/etc/apache2/conf-available/ and then gets enabled with a symlink in
conf-enabled/

There is a2enconf new.conf that will create that symlink but I am not sure
if the package is meant to call that command or not.



On Tue, May 10, 2016 at 5:51 PM, Ola Lundqvist  wrote:

> Hi Rob
>
> Thanks for the information. Do you have any reference to how it works now?
> Is the new directory this conf-available and conf-enabled?
>
> // Ola
>
> On Thu, May 5, 2016 at 4:52 PM, Rob  wrote:
>
>> Package: wwwconfig-common
>> Version: 0.2.2
>> Severity: important
>>
>> Dear Maintainer,
>>
>> The Apache confd-link.sh fails on Jessie as the Apache 2.4 configuration
>> has changed.
>> The conf.d is not used now.
>>
>> Expected the package's apache.conf file to get linked at /conf-available
>> and enabled.
>>
>>
>> -- System Information:
>> Debian Release: 8.4
>>   APT prefers stable-updates
>>   APT policy: (500, 'stable-updates'), (500, 'stable')
>> Architecture: amd64 (x86_64)
>>
>> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> wwwconfig-common depends on no packages.
>>
>> wwwconfig-common recommends no packages.
>>
>> Versions of packages wwwconfig-common suggests:
>> ii  apache22.4.10-10+deb8u4
>> pn  mysql-client   
>> pn  postgresql-client  
>>
>> -- no debconf information
>>
>
>

-- 
Rob McAninch
http://robmcaninch.com (Photography)
http://rock13.com

Bug#822209: udiskie: Mention something about policykit, possibly in README.Debian

[Faheem Mitha]

Hi Gianfranco,

Thanks for the commit.

Regards, Faheem Mitha

On Tue, 10 May 2016, Gianfranco Costamagna wrote:


control: tags -1 pending

Hi, I committed and uploaded this new file a few seconds ago.

I don't think the end user should have privileges to mount/unmount disks, so I 
gave up
in making a polkit file for everybody.

I thought about configuring it, but I don't see how I can do that.

Thanks for now for the README.Debian file, and let me know if you have another 
solution,
I'll happily review it again!

(and sorry for the long wait)

Gianfranco




Il Martedì 26 Aprile 2016 14:09, Faheem Mitha  ha scritto:

On Fri, 22 Apr 2016, Gianfranco Costamagna wrote:


Hi, can you please provide a patch for this?


I can also install a policykit file if needed, just please send a patch

thanks

G.


Hi Gianfranco,

This is the same patch as I posted earlier in
https://github.com/coldfix/udiskie/issues/111

Consider creating a README.Debian with this content. Please feel free to
make modifications as you think appropriate. Or I can make modifications
if you want.

 Regards, Faheem



Note that by default not all udiskie actions may be allowed. You may see
an error like:

GDBus.Error:org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not
authorized to perform operation

That error means you need to give udiskie addition permissions to perform
whatever actions are necessary. These permissions are governed by
policykit (package `policykit-1` in Debian),

Here is an example. If you run `udiskie-mount` and/or `udiskie-umount`
inside a user cron job, you will need to grant your user additional
permissions for the policykit actions as follows:

1) `org.freedesktop.udisks2.filesystem-mount-other-seat` for when nobody
is logged in and

2) `org.freedesktop.udisks2.filesystem-mount` when somebody is logged into
the system in an active session.

To grant these permissions, you can (for example) create a file called
`/etc/polkit-1/localauthority/50-local.d/10-udiskie.pkla` containing the
following:

```
[udisks2]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.filesystem-mount-other-seat;org.freedesktop.udisks2.filesystem-mount
ResultAny=yes

```
This gives the necessary permissions to all users in the `plugdev` group.
If you wish to only give permissions to a single user, you can replace the
first line with
```
Identity=unix-group:plugdev
```
Note additionally that the policykit version in Debian (for jessie and
later) is 105. The Javascript syntax you will see for Policykit is for
versions 106 and later. The `*.pkla` suffix and the corresponding syntax
is only used for policykit 105 and earlier.

Bug#823979: autodep8: Support for ELPA testsuites

[Sean Whitton]

Package: autodep8
Version: 0.5.1
Severity: wishlist
Tags: patch

Dear maintainers,

Please consider applying the following patch which adds support for the
testsuites of Emacs Lisp addon packages.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: i386 (i686)

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

Versions of packages autodep8 depends on:
ii  dctrl-tools  2.24-2
ii  python3  3.5.1-3

autodep8 recommends no packages.

autodep8 suggests no packages.

-- no debconf information

-- 
Sean Whitton
From 2bee7dc0e3f008312774acc04a94df167e804fa1 Mon Sep 17 00:00:00 2001
From: Sean Whitton 
Date: Tue, 10 May 2016 13:10:27 -0700
Subject: [PATCH] ELPA testsuite detection & update copyright years

---
 debian/changelog  |  8 
 debian/control|  1 +
 debian/copyright  |  2 +-
 support/elpa/detect   | 18 +
 support/elpa/generate | 19 ++
 test/elpa_test.sh | 55 +++
 6 files changed, 102 insertions(+), 1 deletion(-)
 create mode 100755 support/elpa/detect
 create mode 100755 support/elpa/generate
 create mode 100644 test/elpa_test.sh

diff --git a/debian/changelog b/debian/changelog
index 20fc757..faeb535 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+autodep8 (0.6) UNRELEASED; urgency=medium
+
+  * Add support for ELPA package testsuites run by dh_elpa_test.
+  * Add test suite for ELPA package testsuite detection.
+  * Bump copyright years in d/copyright.
+
+ -- Sean Whitton   Tue, 10 May 2016 11:51:14 -0700
+
 autodep8 (0.5.1) unstable; urgency=medium
 
   * test/helper.sh: include extra information on failed tests to help
diff --git a/debian/control b/debian/control
index 6a44ec8..9d0b81b 100644
--- a/debian/control
+++ b/debian/control
@@ -24,3 +24,4 @@ Description: DEP-8 test control file generator
   - NodeJS packages
   - Kernel module packages using DKMS
   - R packages
+  - Emacs Lisp ELPA packages
diff --git a/debian/copyright b/debian/copyright
index 99b3620..dabe791 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -3,7 +3,7 @@ Upstream-Name: autodep8
 Source: http://git.debian.org/?p=collab-maint/autodep8.git;a=summary
 
 Files: *
-Copyright: 2014 the contributing authors. See `git log` for details.
+Copyright: 2014-2016 the contributing authors. See `git log` for details.
 License: GPL-3.0+
 
 License: GPL-3.0+
diff --git a/support/elpa/detect b/support/elpa/detect
new file mode 100755
index 000..7fd6287
--- /dev/null
+++ b/support/elpa/detect
@@ -0,0 +1,18 @@
+#!/bin/sh
+
+# Maintainer: Sean Whitton 
+
+# We check that: this package uses dh_elpa, debhelper compat level is
+# at least 10 (see dh_elpa_test(1)), and the user hasn't disabled
+# dh_elpa_test, and that there is actually a testsuite to run
+
+set -e
+
+# check that the file exists first, so that if it doesn't cat doesn't
+# produce stderr output which disrupts other test/*_test.sh
+test -e debian/compat
+test "$(cat debian/compat)" -ge 10
+(! grep -q ".*DH_ELPA_TEST_DISABLE.*" debian/rules)
+grep-dctrl -q -F Build-Depends dh-elpa debian/control
+( grep -q -r ".*(ert-deftest.*" . || \
+grep-dctrl -q -F Build-Depends elpa-buttercup debian/control )
diff --git a/support/elpa/generate b/support/elpa/generate
new file mode 100755
index 000..3d89bc7
--- /dev/null
+++ b/support/elpa/generate
@@ -0,0 +1,19 @@
+#!/bin/sh
+
+# Maintainer: Sean Whitton 
+
+# Remarks:
+
+# 1. Many ELPA test suites write to the build tree, so we need that
+#restriction in the general case.
+
+# 2. We invoke `debian/rules build' rather than simply `dh_elpa_test'
+#because that ensures that any DH_ELPA_TEST_* environment
+#variables the user has specifies in debian/rules are exported
+#such that dh_elpa_test can see them.  See dh_elpa_test(1).
+
+cat <

signature.asc
Description: PGP signature

Bug#823518: wwwconfig-common: Apache 2 conf.d Fails - Not Configured on Jessie

[Ola Lundqvist]

Hi Rob

Thanks for the information. Do you have any reference to how it works now?
Is the new directory this conf-available and conf-enabled?

// Ola

On Thu, May 5, 2016 at 4:52 PM, Rob  wrote:

> Package: wwwconfig-common
> Version: 0.2.2
> Severity: important
>
> Dear Maintainer,
>
> The Apache confd-link.sh fails on Jessie as the Apache 2.4 configuration
> has changed.
> The conf.d is not used now.
>
> Expected the package's apache.conf file to get linked at /conf-available
> and enabled.
>
>
> -- System Information:
> Debian Release: 8.4
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> wwwconfig-common depends on no packages.
>
> wwwconfig-common recommends no packages.
>
> Versions of packages wwwconfig-common suggests:
> ii  apache22.4.10-10+deb8u4
> pn  mysql-client   
> pn  postgresql-client  
>
> -- no debconf information
>



-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comFolkebogatan 26\
|  o...@debian.org   654 68 KARLSTAD|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---

Bug#816569: mrs: FTBFS with GCC 6: was not declared in this scope

[Gert Wollny]

Control: block -1 by  823978

Hi, 

I've added a patch to the packaging svn that fixes the problem, but
building with g++-6 still doesn't work because of some boost-regex
linking problem (see block request),

Best, 
Gert 

Bug#807006: qemu: FTBFS on sparc64 due to incompatible linker parameters

[James Clarke]

Control: tags -1 patch
Control: forwarded -1 
http://lists.nongnu.org/archive/html/qemu-devel/2016-05/msg01566.html

Hi,
On Fri, 04 Dec 2015 01:58:14 +0100 John Paul Adrian Glaubitz 
 wrote:
> qemu currently fails to build from source on sparc64 because it sets
> both the linker parameters "-r" and "--relax":
>
> cc -nostdlib -Wl,-r -o block/iscsi.mo block/iscsi.o
> /usr/bin/ld: --relax and -r may not be used together
> collect2: error: ld returned 1 exit status
> make[1]: *** [block/iscsi.mo] Error 1
> /«BUILDDIR»/qemu-2.4+dfsg/rules.mak:117: recipe for target 'block/iscsi.mo' 
> failed
>
> This happens because gcc is called with "-Wl,-r" which does not gcc's
> internal mechanism to disable "--relax" at the same time (for whatever
> reason).
>
> Thus, on sparc*, gcc should be either called with just "-Wl" but not with "-r"
> or the option "-no-relax" should be passed in order to fix this problem.
>
> ghc upstream had the same problem and fixed the issue by setting "-no-relax"
> for sparc [1].
>
> Please apply a similar fix for qemu.

I have submitted a patch upstream, and attached a backported version.

Regards,
James
--- a/configure
+++ b/configure
@@ -4505,6 +4505,18 @@
   fi
 fi
 
+#
+# Sparc implicitly links with --relax, which is
+# incompatible with -r. It does no harm to give
+# it on other platforms too.
+
+cat > $TMPC << EOF
+int foo(void) { return 0; }
+EOF
+if compile_prog "" "-nostdlib -Wl,-r -Wl,--no-relax"; then
+  LD_REL_FLAGS="-Wl,--no-relax"
+fi
+
 ##
 # End of CC checks
 # After here, no more $cc or $ld runs
@@ -5471,6 +5483,7 @@
 fi
 echo "LDFLAGS=$LDFLAGS" >> $config_host_mak
 echo "LDFLAGS_NOPIE=$LDFLAGS_NOPIE" >> $config_host_mak
+echo "LD_REL_FLAGS=$LD_REL_FLAGS" >> $config_host_mak
 echo "LIBTOOLFLAGS=$LIBTOOLFLAGS" >> $config_host_mak
 echo "LIBS+=$LIBS" >> $config_host_mak
 echo "LIBS_TOOLS+=$libs_tools" >> $config_host_mak
--- a/rules.mak
+++ b/rules.mak
@@ -111,7 +111,7 @@
$(if $(findstring /,$@),$(call quiet-command,cp $@ $(subst /,-,$@), "  
CP$(subst /,-,$@)"))
 
 
-LD_REL := $(CC) -nostdlib -Wl,-r
+LD_REL := $(CC) -nostdlib -Wl,-r $(LD_REL_FLAGS)
 
 %.mo:
$(call quiet-command,$(LD_REL) -o $@ $^,"  LD -r $(TARGET_DIR)$@")


signature.asc
Description: PGP signature

Bug#787279: d-i screen blanking (more info)

[Philipp Kern]

On 2016-05-09 23:28, Philip Hands wrote:

In order to make the dpms stuff work again in future versions I'd think
that screen-blanking is really not helpful during install, so would set
DPMS="-s 0" or perhaps DPMS="-s 0 -dpms", by default, and also make it
so that is what's set when dpms=false is specified.


While completely true for automated installs, people might end up with 
idling installers on some machines, no? But I guess the alternative of 
not blanking when it's actively doing something is not very compelling 
either…


Kind regards
Philipp Kern

Bug#823978: libboost-regex1.58.0: Boost somehow mixes up c_regex_traits and cpp_regex_traits

[Gert Wollny]

Package: libboost-regex1.58.0
Version: 1.58.0+dfsg-5+b1
Severity: important

Dear maintainer,

when compiling src:mrs with g++-6 I get unresolved symbols

/usr/bin/c++ -o mrs -I. obj/M6Server.o [...] -lboost_regex [...]

obj/M6Server.o: In function
`boost::cpp_regex_traits::transform_primary[abi:cxx11](char const*, char
const*) const':
/usr/include/boost/regex/v4/cpp_regex_traits.hpp:965: undefined reference to
`boost::re_detail::cpp_regex_traits_implementation::transform_primary[abi:cxx11](char
const*, char const*) const'
obj/M6Server.o: In function
`boost::cpp_regex_traits::transform[abi:cxx11](char const*, char const*)
const':
/usr/include/boost/regex/v4/cpp_regex_traits.hpp:961: undefined reference to
`boost::re_detail::cpp_regex_traits_implementation::transform[abi:cxx11](char
const*, char const*) const'
...

now in the symbol table I get
objdump --dynamic-syms libboost_regex.so.1.58.0 \
 | c++filt \
 | sed -e "s/^[0-9a-f]* *\([A-Za-z]\) *D[A-Z] \.[a-z]*/\1/" \
 | sed -e "s/[0-9a-f]*  Base *//" | grep "transform_primary"

g boost::c_regex_traits::transform_primary[abi:cxx11](wchar_t const*,
wchar_t const*)
w
boost::re_detail::cpp_regex_traits_implementation::transform_primary(wchar_t
const*, wchar_t const*) const
w
boost::re_detail::cpp_regex_traits_implementation::transform_primary(char
const*, char const*) const
g boost::c_regex_traits::transform_primary[abi:cxx11](char const*, char
const*)

i.e. the symbols are not available.

Given
http://www.boost.org/doc/libs/1_58_0/libs/regex/doc/html/boost_regex/ref/regex_traits.html

I thought compiling with -DBOOST_REGEX_USE_C_LOCALE would get me somewhere, but
then I get a lot more missing symbols, and they are all without the [abi:cxx11]
tag.


src:mrs requires -std=c++11, but I assume for the boost package the g++ default
was used, and with g++-5 this is -std=c++03, therefore, final guess is that
there is a problem with compiling boost with -std=c++11 and then linking
against a boost library that was compiled with -std=c++03.


Best,
Gert



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

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

Versions of packages libboost-regex1.58.0 depends on:
ii  libc6   2.22-7
ii  libgcc1 1:6-20160117-1
ii  libicu5555.1-7
ii  libstdc++6  6-20160117-1

libboost-regex1.58.0 recommends no packages.

libboost-regex1.58.0 suggests no packages.

-- no debconf information

Bug#818566: Root cause fixed

[Ruben Undheim]

The root cause for this has been fixed in libosmocore. With a binNMU on 
openbsc, the bug will be fixed.

Bug#823977: cmake-fedora: Typo in package description

[Thomas Vincent]

Package: cmake-fedora
Severity: minor

Dear Maintainer,

I believe I spotted a typo while translating the description of cmake-fedora.
Indeed, in the short description, "that simply the release process" should be 
corrected into "that simplify the release process".

Thanks for your work on cmake-fedora,
Thomas


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

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

Bug#823976: apt: [INTL:nl] Dutch po file for the apt package

[Frans Spiesschaert]

 

Package: apt 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch po file for the apt package. 
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 "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#823975: unattended-upgrades: [INTL:nl] Dutch po file for the unattended-upgrades package

[Frans Spiesschaert]

 

Package: unattended-upgrades 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the Dutch po file for the unattended-upgrades package. 
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 "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#823974: apt-listchanges: [INTL:nl] Dutch po file for the apt-listchanges package

[Frans Spiesschaert]

 

Package: apt-listchanges 
Severity: wishlist 
Tags: l10n patch 
 

Dear Maintainer, 
 
== 
Please find attached the updated Dutch po file for the apt-listchanges package. 
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 "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#823973: php7.0-fpm: add more systemd features to the unit file

[Jonas Genannt]

Package: php7.0-fpm
Severity: wishlist
Tags: patch

Dear Maintainer,

please see attached patch. It will add some systemd features for a
more secure environment.

Greets,
Jonasdiff --git a/php-fpm.service b/php-fpm.service
index 5621b29..130cc7e 100644
--- a/php-fpm.service
+++ b/php-fpm.service
@@ -10,6 +10,9 @@ ExecStartPre=/usr/lib/php/php@PHP_VERSION@-fpm-checkconf
 ExecStart=/usr/sbin/php-fpm@PHP_VERSION@ --nodaemonize --fpm-config /etc/php/@PHP_VERSION@/fpm/php-fpm.conf
 ExecReload=/usr/lib/php/php@PHP_VERSION@-fpm-checkconf
 ExecReload=/bin/kill -USR2 $MAINPID
+ProtectSystem=full
+PrivateTmp=true
+PrivateDevices=true
 
 [Install]
 WantedBy=multi-user.target

Bug#777791: [PATCH] ball: ftbfs with GCC-5

[Danny Edel]

On 05/10/2016 07:13 PM, Andreas Tille wrote:
> Thanks a lot.  Your work is really appreciated.  Please also be bold and
> commit to master.  I have no time to look the next 2-3 days - but I'd
> like to see the changes in master since I see no point in deriving for
> this package what we are doing anywhere else.

Hi Andreas,

I have backported a fix for the Python issue and ball now builds in a
fresh sid cowbuilder.  I also un-deleted the 0001-missingSigned.patch,
since I realized it is needed on ARM, where "char" is "unsigned char" by
default, causing FTBFS when assigning -1 to a "const char".  This may be
a candidate for a pullrequest to the newly moved upstream github repository.

All patches are uploaded to "master", the work-in-progress branch is
deleted.  To me the resulting package (now without any weird hacks and
old packages from snapshot.d.o) seems usable:  I started BALLView and
loaded random projects from /usr/share/BALL-1.4/data/projects, and I get
molecule renderings on my screen -- but I have no idea if these are the
right ones : )

Cheers,

- Danny



signature.asc
Description: OpenPGP digital signature

Bug#823972: denemo: Soundfont path needs to be changed

[Dhionel Díaz]

Package: denemo
Version: 2.0.6-1
Severity: normal
Tags: patch

Dear Maintainer,

A fresh install of denemo was not playing sounds because it was
expecting the soundfonts to be located in /usr/share/denemo/soundfonts.
With the attached patch the problem is solved changing the soundfont
path to /usr/share/sounds/sf2. I hope it can be useful.

Regards,


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages denemo depends on:
ii  denemo-data 2.0.6-1
ii  guile-2.0-libs  2.0.11+1-10+b1
ii  libasound2  1.1.0-1
ii  libatk1.0-0 2.20.0-1
ii  libaubio4   0.4.1-2.1+b1
ii  libc6   2.22-7
ii  libcairo-gobject2   1.14.6-1+b1
ii  libcairo2   1.14.6-1+b1
ii  libevdocument3-43.20.0-3
ii  libevview3-33.20.0-3
ii  libfftw3-double33.3.4-2+b1
ii  libfluidsynth1  1.1.6-3
ii  libfontconfig1  2.11.0-6.4
ii  libfreetype62.6.3-3+b1
ii  libgc1c21:7.4.2-7.4
ii  libgdk-pixbuf2.0-0  2.34.0-1
ii  libglib2.0-02.48.0-1
ii  libgtk-3-0  3.20.3-2
ii  libgtksourceview-3.0-1  3.20.2-1
ii  libpango-1.0-0  1.40.1-1
ii  libpangocairo-1.0-0 1.40.1-1
ii  libportaudio2   19+svn20140130-1
ii  libportmidi01:184-2.2
ii  librsvg2-2  2.40.15-1
ii  librubberband2  1.8.1-6+b1
ii  libsmf0 1.3-2+b1
ii  libsndfile1 1.0.25-10
ii  libxml2 2.9.3+dfsg1-1
ii  ttf-denemo  2.0.6-1

Versions of packages denemo recommends:
pn  alsa
ii  denemo-doc  2.0.6-1
ii  lilypond2.18.2-4.1

denemo suggests no packages.

-- no debconf information

-- 
Dhionel Díaz
Centro Nacional de Desarrollo e Investigación en Tecnologías Libres
Ministerio del Poder Popular para
Educación Universitaria, Ciencia y Tecnología
diff -Nru denemo-2.0.6/debian/patches/0008-Change-soundfont-path.patch denemo-2.0.6/debian/patches/0008-Change-soundfont-path.patch
--- denemo-2.0.6/debian/patches/0008-Change-soundfont-path.patch	1969-12-31 20:00:00.0 -0400
+++ denemo-2.0.6/debian/patches/0008-Change-soundfont-path.patch	2016-05-10 09:30:55.0 -0400
@@ -0,0 +1,32 @@
+Description: Change soundfonts path
+Change the path where denemo looks for the soundfonts to
+the typical location in Debian.
+Author: Dhionel Díaz 
+Last-Update: 2016-05-10
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/include/denemo/denemo.h
 b/include/denemo/denemo.h
+@@ -132,7 +132,7 @@
+ 
+ #define COMMANDS_DIR   "actions"
+ #define UI_DIR "ui"
+-#define SOUNDFONTS_DIR "soundfonts"
++#define SOUNDFONTS_DIR "sf2"
+ #define PIXMAPS_DIR"pixmaps"
+ #define FONTS_DIR  "denemo"
+ #define LOCALE_DIR "po"
+--- a/src/core/utils.c
 b/src/core/utils.c
+@@ -2815,9 +2815,10 @@
+   {
+ case DENEMO_DIR_FONTS:
+   return g_build_filename("/usr/share/fonts/truetype/", get_local_dir(dir), NULL);
++case DENEMO_DIR_SOUNDFONTS:
++  return g_build_filename("/usr/share/sounds/", get_local_dir(dir), NULL);
+ case DENEMO_DIR_COMMANDS:
+ case DENEMO_DIR_UI:
+-case DENEMO_DIR_SOUNDFONTS:
+ case DENEMO_DIR_LILYPOND_INCLUDE:
+   return g_build_filename(get_system_data_dir (), get_local_dir(dir), NULL);
+ case DENEMO_DIR_PIXMAPS:
diff -Nru denemo-2.0.6/debian/patches/series denemo-2.0.6/debian/patches/series
--- denemo-2.0.6/debian/patches/series	2016-04-15 14:42:53.0 -0430
+++ denemo-2.0.6/debian/patches/series	2016-05-10 09:30:55.0 -0400
@@ -5,3 +5,4 @@
 0005-Change-zoom-for-testing-to-100.patch
 0006-Fix-italian-translation.patch
 0007-Install-soundfont-into-correct-directory.patch
+0008-Change-soundfont-path.patch



signature.asc
Description: OpenPGP digital signature

Bug#823971: mutt: Ignores /etc/mailcap and ~/.mailcap files

[Bob Proulx]

Package: mutt
Version: 1.6.0-1
Severity: normal

The recent version 1.6.0-1 ignores both ~/.mailcap and /etc/mailcap
files.  At least for text/html entries.

cat >> ~/.mailcap <.
To report a bug, please visit http://bugs.mutt.org/.

misc/am-maintainer-mode.patch
features/ifdef.patch
features/trash-folder.patch
features/purge-message.patch
features/imap_fast_trash.patch
features/sensible_browser_position.patch
features/compressed-folders.patch
features/compressed-folders.debian.patch
debian-specific/Muttrc.patch
debian-specific/Md.etc_mailname_gethostbyname.patch
debian-specific/use_usr_bin_editor.patch
debian-specific/correct_docdir_in_man_page.patch
debian-specific/dont_document_not_present_features.patch
debian-specific/document_debian_defaults.patch
debian-specific/assumed_charset-compat.patch
debian-specific/467432-write_bcc.patch
debian-specific/566076-build_doc_adjustments.patch
misc/define-pgp_getkeys_command.patch
misc/gpg.rc-paths.patch
misc/smime.rc.patch
upstream/528233-readonly-open.patch
upstream/228671-pipe-mime.patch
upstream/383769-score-match.patch
upstream/771125-CVE-2014-9116-jessie.patch
upstream/path_max.patch
upstream/809802_timeout_hook.patch
__separator__mutt.org.patch

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

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

Versions of packages mutt depends on:
ii  libassuan02.4.2-3
ii  libc6 2.22-7
ii  libcomerr21.43~WIP.2016.03.15-2
ii  libgnutls30   3.4.11-4
ii  libgpg-error0 1.22-1
ii  libgpgme111.6.0-3
ii  libgssapi-krb5-2  1.13.2+dfsg-5
ii  libidn11  1.32-3
ii  libk5crypto3  1.13.2+dfsg-5
ii  libkrb5-3 1.13.2+dfsg-5
ii  libncursesw5  6.0+20160319-1
ii  libsasl2-22.1.26.dfsg1-15
ii  libtinfo5 6.0+20160319-1
ii  libtokyocabinet9  1.4.48-10

Versions of packages mutt recommends:
ii  libsasl2-modules   2.1.26.dfsg1-15
ii  locales2.22-7
ii  locales-all [locales]  2.22-7
ii  mime-support   3.60

Versions of packages mutt suggests:
ii  aspell  0.60.7~20110707-3+b1
ii  ca-certificates 20160104
pn  default-mta | mail-transport-agent  
ii  gnupg   1.4.20-6
ii  ispell  3.4.00-5
pn  mixmaster   
ii  openssl 1.0.2h-1
ii  urlview 0.9-20

Versions of packages mutt is related to:
ii  mutt  1.6.0-1
pn  mutt-dbg  
pn  mutt-patched  

-- no debconf information

Bug#823195: evince-common: Mouse Inverted Reversed Scrolling Does not Function

[Jason Crain]

On Sat, May 07, 2016 at 03:08:13PM -0400, Carl Nikolov wrote:
> It is a bluetooth mouse can you test this ? 
> 
> It's probably different in this case

I do not have a bluetooth mouse to test with.

I did get around to putting an Xubuntu live image on my USB keychain so
I could test with something better than a virtual machine.  The result
was the same.  Xfce's reverse scroll does not work with GTK3 apps.
Instead of this being unique to Evince, I strongly suspect that the
problem you've experienced is that Xfce's reverse scrolling does not
work with *any* GTK3 app.

Please try this.  Install the gtk-3-examples package and run the
following program:

  gtk3-demo --run flowbox

And see if the reverse scrolling works correctly.  From my testing,
gtk3-demo does not follow Xfce's reverse scroll setting, demonstrating
that this problem is not specific to Evince.

If that's the case, that it's all GTK3 apps and not just Evince, the
solution is going to be that Xfce needs to set some libinput properties
when enabeling reverse scrolling.  For a workaround, on my system (in a
virtual machine) running this command and not using Xfce's reverse
scroll option fixes it:

  xinput --set-int-prop 12 "libinput Natural Scrolling Enabled" 8 1

You'll need to replace "12" with whatever your device ID is, which you
can find with "xinput --list".  There are other recommendations for
xinput settings at (https://bbs.archlinux.org/viewtopic.php?id=179667)
if that doesn't work.

Bug#823970: override: gnome-user-guide:doc/optional

[Michael Biebl]

Package: ftp.debian.org
Severity: normal

Hi,

please move gnome-user-guide from section gnome into section doc.
I've already made the according change in debian/control [1]

Thanks,
Michael

[1] https://anonscm.debian.org/viewvc/pkg-gnome?view=revision=48550

Bug#817005: RFS: aseqjoy/0.0.1-1 [ITP]

[Gianfranco Costamagna]

Hi,

>https://mentors.debian.net/debian/pool/main/a/aseqjoy/aseqjoy_0.0.2-1.dsc


>I just upload to mentors.


wonderful!
>If use Files: * (for the upstream) and Files: debian/* (for mantainer)
>and both have same license this raise the lintian warning.


You shouldn't have any issue by doing
Files: *
Copyright: upstream
License: foo

Files: debian/*
Copyright: you
License: foo

License: foo


common errors are:
- you put debian before the "*" one
(the order *matters* here, from the most common to the particular license)
- you put the license text twice, just put it at the end and mention it on the 
specific
sections.

can you please fix the copyright?
(I can also look at a "lintian-problematic" file and tell you what is wrong in 
that case,
otherwise my answer is too generic I admit)

thanks!

Gianfranco

Bug#823969: RFS: clblas/2.10-3

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: clblas
  Version : 2.10-3
  Upstream Author : Advanced Micro Devices, Inc.
* URL : https://github.com/clMathLibraries/clFFT
* License : Apache version 2
  Section : science

It builds those binary packages:

  libclblas-bin - OpenCL BLAS library (executables)
  libclblas-dev - OpenCL BLAS library (development files)
  libclblas-doc - OpenCL BLAS library (documentation)
  libclblas2 - OpenCL BLAS library (shared library)

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


  https://mentors.debian.net/package/clblas

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

  dget -x 
https://mentors.debian.net/debian/pool/main/c/clblas/clblas_2.10-3.dsc


Changes since the last upload:

  * d/gbp.conf: no patch numbering with gbp-pq.
  * Cherry-pick upstream patch enabling altivec on ppc64. (Closes: #819091)
  * d/rules: drop usage of -mno-altivec compile flag with ppc64.
  * Drop debug package in favour autogenerated dbgsym packages.
  * Bump standards version to 3.9.8, no changes required.

Regards,
Ghislain Vaillant

Bug#822828: gedit 3.20 segfaulting

[Michael Biebl]

Hi Marc

On Wed, 27 Apr 2016 20:24:33 -0700 "Marc J. Driftmeyer"
 wrote:
> Package: gedit
> Version: 3.20.1-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I'm having only Gedit 3.20 running into issues/showstoppers on my Debian Sid 
> configuration. Included is the strace output from the command line.
> 
> I hope you can find what is throwing this exception and cause a segfault. 
> Great application in my workflow.
> 

Is this a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823770
i.e., should we reassign and merge the two bug reports?

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#823968: squid3: CVE-2016-4553 CVE-2016-4554 CVE-2016-4555 CVE-2016-4556

[Salvatore Bonaccorso]

Source: squid3
Version: 3.5.17-1
Severity: important
Tags: security upstream fixed-upstream

Hi

There is a new upstream version of squid3 to address CVE-2016-4553
CVE-2016-4554 CVE-2016-4555 CVE-2016-4556. But more information is
provided via the security-tracker:

 [1] https://security-tracker.debian.org/CVE-2016-4553
 [2] https://security-tracker.debian.org/CVE-2016-4554
 [3] https://security-tracker.debian.org/CVE-2016-4555
 [4] https://security-tracker.debian.org/CVE-2016-4556
 [5] http://www.squid-cache.org/Advisories/SQUID-2016_7.txt
 [6] http://www.squid-cache.org/Advisories/SQUID-2016_8.txt
 [7] http://www.squid-cache.org/Advisories/SQUID-2016_9.txt

Please include CVE identifiers when fixing the issue, and could you
check the older versions and update affected version? Santiago Ruano
Rincón has as well already done some research.

Regards,
Salvatore

Bug#815360: Bug#795428: OpenSLP 1.2 should not be part of stretch

[Moritz Mühlenhoff]

On Sun, Feb 21, 2016 at 12:20:52AM +, Julien Cristau wrote:
> Control: clone -1 -2 -3 -4 -5 -6 -7 -8
> Control: reassign -2 cups 2.1.3-1
> Control: retitle -2 cups: build-depends on libslp-dev
> Control: reassign -3 kde-runtime 4:15.08.3-1
> Control: retitle -3 kde-runtime: build-depends on libslp-dev
> Control: reassign -4 kio-extras 4:15.08.3-1
> Control: retitle -4 kio-extras: build-depends on libslp-dev
> Control: reassign -5 nis 3.17-34
> Control: retitle -5 nis: build-depends on libslp-dev
> Control: reassign -6 ola 0.9.8-1
> Control: retitle -6 ola: build-depends on libslp-dev
> Control: reassign -7 openldap 2.4.42+dfsg-2
> Control: retitle -7 openldap: build-depends on libslp-dev
> Control: reassign -8 roaraudio 1.0~beta11-5
> Control: retitle -8 roaraudio: build-depends on libslp-dev
> 
> On Thu, Aug 13, 2015 at 23:55:59 +0200, Moritz Muehlenhoff wrote:
> 
> > Source: openslp-dfsg
> > Severity: serious
> > 
> > The last maintainer upload of openslp happened in 2007
> > and it's orphaned for 5.5 years now. The 1.2 branch is
> > completely abandoned upstream.
> > 
> > At the minimum the package should be upgraded to 2.0,
> > but the comment at
> > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-5177
> > suggests it's completely abandoned upstream.
> > 
> Cloning the bug against the reverse dependencies.

Dear KDE maintainers,
this seems to be a forgotten/unused build dep? While kde-runtime build depends
on libslp-dev, none of the binary packages actually link against it.

Cheers,
Moritz

Bug#823693: ITP: asciiquarium

[Ben Finney]

On 10-May-2016, Niklas Sombert wrote:
> Ben Finney wrote:
> > That synopsis you've written still is not a noun phrase :-)
> 
> Oh. :-)
> 
> "simulation of an aquarium using ASCII art"

That's great! Thank you for re-wording it.

-- 
 \ “Here is a test to see if your mission on earth is finished. If |
  `\  you are alive, it isn't.” —Francis Bacon |
_o__)  |
Ben Finney 


signature.asc
Description: PGP signature

Bug#822209: udiskie: Mention something about policykit, possibly in README.Debian

[Gianfranco Costamagna]

control: tags -1 pending

Hi, I committed and uploaded this new file a few seconds ago.

I don't think the end user should have privileges to mount/unmount disks, so I 
gave up
in making a polkit file for everybody.

I thought about configuring it, but I don't see how I can do that.

Thanks for now for the README.Debian file, and let me know if you have another 
solution,
I'll happily review it again!

(and sorry for the long wait)

Gianfranco




Il Martedì 26 Aprile 2016 14:09, Faheem Mitha  ha scritto:

On Fri, 22 Apr 2016, Gianfranco Costamagna wrote:

> Hi, can you please provide a patch for this?
>
>
> I can also install a policykit file if needed, just please send a patch
>
> thanks
>
> G.

Hi Gianfranco,

This is the same patch as I posted earlier in 
https://github.com/coldfix/udiskie/issues/111

Consider creating a README.Debian with this content. Please feel free to 
make modifications as you think appropriate. Or I can make modifications 
if you want.

  Regards, Faheem



Note that by default not all udiskie actions may be allowed. You may see 
an error like:

 GDBus.Error:org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not
authorized to perform operation

That error means you need to give udiskie addition permissions to perform 
whatever actions are necessary. These permissions are governed by 
policykit (package `policykit-1` in Debian),

Here is an example. If you run `udiskie-mount` and/or `udiskie-umount` 
inside a user cron job, you will need to grant your user additional 
permissions for the policykit actions as follows:

1) `org.freedesktop.udisks2.filesystem-mount-other-seat` for when nobody 
is logged in and

2) `org.freedesktop.udisks2.filesystem-mount` when somebody is logged into 
the system in an active session.

To grant these permissions, you can (for example) create a file called 
`/etc/polkit-1/localauthority/50-local.d/10-udiskie.pkla` containing the 
following:

```
[udisks2]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.filesystem-mount-other-seat;org.freedesktop.udisks2.filesystem-mount
ResultAny=yes

```
This gives the necessary permissions to all users in the `plugdev` group. 
If you wish to only give permissions to a single user, you can replace the 
first line with
```
Identity=unix-group:plugdev
```
Note additionally that the policykit version in Debian (for jessie and 
later) is 105. The Javascript syntax you will see for Policykit is for 
versions 106 and later. The `*.pkla` suffix and the corresponding syntax 
is only used for policykit 105 and earlier.

Bug#822613: RFS: dynamic-graph/3.0.0-1

[Gianfranco Costamagna]

control: owner -1 !

Hi, please fix the Pedantic lintian issues
https://mentors.debian.net/package/dynamic-graph
(e.g. no dep5 copyright, old compat level, typos, missing harderning flags)

and then I'll have a look at the package.




Il Lunedì 25 Aprile 2016 18:42, Rohan Budhiraja  ha 
scritto:
Package: sponsorship-requests
   Severity: wishlist [important for RC bugs, wishlist for new packages]

   Dear mentors,

   I am looking for a sponsor for my package "dynamic-graph"

  * Package name: dynamic-graph
Version : 3.0.0-1
Upstream Author : Thomas Moulard
 François Bleibel
 François Keith
   Nicolas Mansard
  Olivier Stasse

  * URL : https://github.com/proyan/dynamic-graph
  * License : LGPL-3
Section : libs

   It builds those binary packages:

 libdynamic-graph-dev - Dynamic graph C++ library development package
  libdynamic-graph-doc - documentation for the dynamic graph C++ library
  libdynamic-graph3.0.0 - Dynamic graph C++ library

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

  http://stack-of-tasks.github.io/


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

 dget -x 
http://mentors.debian.net/debian/pool/main/d/dynamic-graph/dynamic-graph_3.0.0-1.dsc

   Regards,
Rohan Budhiraja

Bug#823896: vim-dbg package no longer built

[Niels Thykier]

fREW Schmidt:
> Oh thanks!
> 
> Sorry, I didn't realize that debug symbols are now hosted elsewhere.
> Do you know why that is?  Seems sketchy since they have to be the same
> version and whatnot...
> 

Hi,

Ubuntu has had ddebs.ubuntu.com for a while plus the infrastructure to
build dbg packages for package that did not have any.
  What changed is that Debian got a similar setup now, so Debian
maintainers are now dropping their manual -dbg packages.

Three of the key reasons for moving the (automatic) dbg packages in
Debian to a separate archive were:

 * We expected quite a lot of them and expected them to be quite large.
   - As such the burden on mirrors might suddenly "explode"

 * The mirror metadata would also increase significantly
   - There were regular complains about the metadata being too "heavy"
 already now

 * We expected that very few people (relative to all of users of Debian)
   would want dbgsym packages.

I presume Ubuntu made came to a similar conclusion back when they made
their ddeb solution.


As for the technical parts, the dbgsym packages are built along with the
regular packages (which is why they have the same version).  When they
are uploaded to Debian, the infrastructure separates the "original" debs
and the "dbgsym" packages into separate archives.

> On Tue, May 10, 2016 at 06:30:25PM +, Niels Thykier wrote:
>> Hi,
>>
>> Forgot to CC you own the mail below.
>>
>>
>> [...]



signature.asc
Description: OpenPGP digital signature

Bug#767884: Not fixed in 1.45-0-1

[Logan Rosen]

Hi,

I don't believe that this was fixed in the 1.45-0-1 upload. The
autopkgtest is still failing in Ubuntu:
http://autopkgtest.ubuntu.com/packages/r/r-cran-spatstat/yakkety/amd64/

Should this be reopened? I can't verify that it's still happening in
Debian because the package is on the blacklist:
https://ci.debian.net/status/blacklist/

Thanks,
Logan

Bug#330695: [Pkg-openldap-devel] Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Ryan Tandy]

On Tue, May 10, 2016 at 09:21:56PM +0200, Helmut Grohne wrote:

Control: severity -1 serious
Control: tags -1 + patch


Thanks for the update and patch. I'm dropping Russ from CC because he is 
no longer actively involved in maintaining openldap. I will try to get 
this uploaded ASAP.

Bug#822098: python3-gear: depends on python3.4

[Jean-Michel Vourgère]

Control: retitle -1 python3-gear: depends on python3.4
Control: reassign -1 python3-gear 0.5.8-2
Control: severity -1 serious

Ouch, actualy this is a arch:all package, so that a bin-nmu is impossible.
A sourceful upload is needed. (Thanks Emilio for the tip).

Reassigning back to python-gear.

Bug#823967: libapache2-mod-perl2: hardening-no-relro mod_perl.so

[Niko Tyni]

Package: libapache2-mod-perl2
Version: 2.0.9-4

As noticed by lintian, mod_perl.so is not linked with
-Wl,-z,relro.

W: libapache2-mod-perl2: hardening-no-relro usr/lib/apache2/modules/mod_perl.so

It looks like we're currently using the debhelper default behaviour where
linker flags are passed to Makefile.PL in an LD=[...] argument. This
normally works with ExtUtils::MakeMaker, but apparently not with the
libapache2-mod-perl2 build system.

I see Apache2::Build::ldopts uses

my $ld = $self->perl_config('ld');

so that part probably needs some work. Filing this to track
the issue, but I'm not promising a patch any time soon...
-- 
Niko Tyni   nt...@debian.org

Bug#823966: override: gnome-devel-docs:doc/optional

[Michael Biebl]

Package: ftp.debian.org
Severity: normal

Hi,

please move gnome-devel-docs from section gnome into section doc.
I've already made the according change in debian/control [1]

Thanks,
Michael

[1] https://anonscm.debian.org/viewvc/pkg-gnome?view=revision=48173

Bug#820824: libapache2-mod-perl2: FTBFS: t/protocol/pseudo_http.t failure

[Niko Tyni]

On Mon, May 09, 2016 at 09:49:13PM +0300, Niko Tyni wrote:

> I intend to disable the test in libapache2-mod-perl2 for now until
> a better solution is found. 

Done in 2.0.9-5 which I just uploaded.

> Do you want to track the apache2 crash
> with this bug, or should we reassign it back?

In the latter case feel free to reassign and close,
or let me know and I'll do that.
-- 
Niko

Bug#823965: O: fbset -- framebuffer device maintenance program

[Heliogabalo]

Package: wnpp
Severity: normal

I intend to orphan the fbset package.

The package description is:
 Program to modify settings for the framebuffer devices (/dev/fb[0-9]*
 or /dev/fb/[0-9]*) on Linux, like depth, virtual resolution, timing
 parameters etc.

I'm just taking control of the bug-trac reports. Any help will be apreciated.
I will translate de docs, providing the references to the project as much
acurated as i can.

This work need an update. It have some 'cross' references in other pkgs like
DirectFB wich is maintained in Debian as version 1.2.10(outdated).

The app work fine, i was testing it on Debian & Ubuntu without problem.

severity: normal

"Guillem Jover  (2014-03-03):
> This package has a lethargic upstream, and needs to be synced from 
time
> to time with the latest Linux framebuffer header, accelerators, docs 
and
> modes, from «linux/include/linux/fb.h» and «linux/Documentation/fb/»
> respectively, which I've not done since linux-3.0.0-rc1, as I can't be
> bothered any longer. It also produces a udeb, so people interested in
> the installer might want to take a look.

I only quickly looked, but I didn't find anything obvious making use of
the binaries the udeb contains, or a reference to the udeb itself; so I
might be OK for it to go away entirely. Cc-ing -boot@ so that someone
can yell if I missed something."

Bug#823964: xapers: Show context of syntax error when parsing the BibTeX file

[Rafael Laboissière]

Package: xapers
Version: 0.6-1
Severity: wishlist
Tags: patch upstream

When there is a parsing error in the BibTeX file scanned by Xapers, no 
indication is given about is location in the file.  Would it be possible 
to implement something along the lines of the patch attached to this bug 
report?


Thanks.

Rafael

-- System Information: 
Debian Release: stretch/sid 
 APT prefers testing 
 APT policy: (650, 'testing'), (600, 'unstable'), (550, 'stable'), (500, 'experimental') 
Architecture: i386 (i686)


Kernel: Linux 4.3.0-trunk-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xapers depends on: 
ii  poppler-utils 0.38.0-2+b1 
ii  pybtex0.19-2 
ii  python2.7.11-1 
ii  python-pkg-resources  18.8-1 
ii  python-xapian 1.2.23-1


Versions of packages xapers recommends: 
ii  python-pycurl  7.43.0-1 
ii  python-urwid   1.3.1-2+b1 
ii  xclip  0.12+svn84-4 
ii  xdg-utils  1.1.1-1


xapers suggests no packages.

-- no debconf information
>From 4ce8e43b7022091ffb3a65cb371df18cda7c42f9 Mon Sep 17 00:00:00 2001
From: Rafael Laboissiere 
Date: Tue, 10 May 2016 17:01:12 +0200
Subject: [PATCH] Print context of syntax error found in the BibTeX file

---
 lib/xapers/bibtex.py | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/lib/xapers/bibtex.py b/lib/xapers/bibtex.py
index 45d908b..f9e2cbb 100644
--- a/lib/xapers/bibtex.py
+++ b/lib/xapers/bibtex.py
@@ -35,7 +35,11 @@ class Bibtex():
 parser = inparser.Parser(encoding='utf-8')
 
 if os.path.exists(bibtex):
-bibdata = parser.parse_file(bibtex)
+try:
+bibdata = parser.parse_file(bibtex)
+except TokenRequired as e:
+print e.get_context()
+raise e
 else:
 # StringIO requires unicode input
 # http://nedbatchelder.com/text/unipain.html
-- 
2.8.0.rc3

Bug#816430: cups: 'Find New Printers' in the web interface does not work

[Brian Potkin]

On Tue 01 Mar 2016 at 19:44:50 +, Brian Potkin wrote:

> Going to 'Administration/Find New Printers' from the web interface gets
> the outcome
> 
>   List Available Printers
>   Available Printers
>   No printers found
> 
> An error_log is attached.
> 
> 'Administration/Add Printer' requests authorisation and lists printers.
> 
> On returning to Administration/Find New Printers it now comes up with a 
> list of available printers.
> 
> With cups 1.7.5 (Debian 8) 'Find New Printers' works immediately.

This behaviour is replicated exactly as described above with
Fedora-Workstation-Live-x86_64-24_Beta-1.6.iso, which has cups 2.1.3.

openSUSE-Tumbleweed-GNOME-Live-i686-Current.iso has the same CUPS
version and behaves in a slightly different way (no network printers
are displayed with either "Find Available Printers" or "Add Printer"),
but I'd say the behaviour is again identical to Debian and Fedora.

(I never saw Mike Sweet's responses in cups-devel; maybe due to the
change to Git. Something for me to sort out sometime).

Cheers,

Brian.

Bug#823800: transition: glpk-4.60

[Sébastien Villemot]

Le mardi 10 mai 2016 à 14:03 +0200, Emilio Pozuelo Monfort a écrit :
> On 09/05/16 10:13, Sébastien Villemot wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > Control: forwarded -1 
> > https://release.debian.org/transitions/html/auto-glpk.html
> > 
> > Dear Release Team,
> > 
> > Please schedule a transition for glpk, whose new version (4.60-1) stands
> > in experimental.
> > 
> > All reverse deps seems to build fine with the new version.
> 
> Go ahead.

Thanks, uploaded.

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594

Bug#823963: ardour: Incorrect balance behaviour for stereo bus sends

[Nis Sandor]

Package: ardour
Version: 1:4.7~dfsg-1
Severity: normal

Dear Maintainer,

It is possible to set invalid balance values for stereo bus sends in ardour4.
How to reproduce: add a stereo bus and an audio track to your project. Add a 
"New aux send" to your audio track, open mixer window.
Click the 'Aux' button on you bus to show aux send's volume and balance 
parameters on the audio track. On the audio track grab
either the (L) or (R) signs to set stereo with or the center indicator and move 
it out of the channel strip.
You can set stereo width over 100% and L/R values below 0 and above 100  (eg: 
L: -70 R: 170 Width: 145%).
It will cause false stereo image rendering.

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

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

Versions of packages ardour depends on:
ii  ardour-data   1:4.7~dfsg-1
pn  jackd 
ii  libasound21.1.0-1
ii  libatk1.0-0   2.20.0-1
ii  libatkmm-1.6-1v5  2.24.2-1
ii  libaubio4 0.4.1-2.1+b1
ii  libbluetooth3 5.36-1
ii  libc6 2.22-7
ii  libcairo2 1.14.6-1+b1
ii  libcairomm-1.0-1v51.12.0-1+b1
ii  libcurl3-gnutls   7.47.0-1
ii  libcwiid1 0.6.00+svn201-3.2
ii  libfftw3-single3  3.3.4-2+b1
ii  libflac8  1.3.1-4
ii  libfontconfig12.11.0-6.4
ii  libfreetype6  2.6.3-3+b1
ii  libgcc1   1:6.1.1-1
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.48.0-1
ii  libglibmm-2.4-1v5 2.48.1-1
ii  libgtk2.0-0   2.24.30-1.1
ii  libgtkmm-2.4-1v5  1:2.24.4-2+b1
ii  libjack-jackd2-0 [libjack-0.116]  1.9.10+20150825git1ed50c92~dfsg-1
ii  liblilv-0-0   0.22.0~dfsg0-1
ii  liblo70.28-5
ii  liblrdf0  0.4.0-7
ii  libltc11  1.2.0-1
ii  libogg0   1.3.2-1
ii  libpango-1.0-01.40.1-1
ii  libpangocairo-1.0-0   1.40.1-1
ii  libpangoft2-1.0-0 1.40.1-1
ii  libpangomm-1.4-1v52.40.0-1
ii  librubberband21.8.1-6+b1
ii  libsamplerate00.1.8-8
ii  libserd-0-0   0.22.0~dfsg0-2
ii  libsigc++-2.0-0v5 2.8.0-1
ii  libsndfile1   1.0.25-10
ii  libsord-0-0   0.14.0~dfsg0-1
ii  libsratom-0-0 0.4.6~dfsg0-1
ii  libstdc++66.1.1-1
ii  libsuil-0-0   1:0.8.2-dmo1
ii  libtag1v5 1.9.1-2.4
ii  libvamp-hostsdk3v51:2.6-dmo3
ii  libvamp-sdk2v51:2.6-dmo3
ii  libx11-6  2:1.6.3-1
ii  libxml2   2.9.3+dfsg1-1

Versions of packages ardour recommends:
ii  chromium [www-browser] 50.0.2661.94-1
ii  firefox-esr [www-browser]  45.1.0esr-1
ii  links [www-browser]2.12-1+b2
ii  lynx [www-browser] 2.8.9dev9-1
ii  opera [www-browser]12.16.1860

ardour suggests no packages.

-- no debconf information

Bug#330695: libldap2: /etc/ldap/ldap.conf breaks multiarch and on soname change

[Helmut Grohne]

Control: severity -1 serious
Control: tags -1 + patch

On Sun, Jul 13, 2008 at 07:47:31PM -0700, Russ Allbery wrote:
> I see that we're indeed still shipping /etc/ldap/ldap.conf in the library
> package.  This is a Policy violation (8.2); we really should do something
> about it.

I confirm that this is indeed a policy violation and raise the severity
accordingly.

> All values are commented-out in the default version and the library seems
> to run fine if the file is missing entirely.  I propose we just move the
> file into /usr/share/doc/libldap-2.4-2/examples and mention it in
> README.Debian.  Any objections?

In your later mail, you proposed to move it to libldap-common. I
implemented the move of the config file and the manual page in the
attached patch and verified it using piuparts.

Helmut
--- openldap-2.4.42+dfsg/debian/changelog
+++ openldap-2.4.42+dfsg/debian/changelog
@@ -1,3 +1,11 @@
+openldap (2.4.42+dfsg-2.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * Fix policy 8.2 violation (Closes: #330695)
++ Move /etc/ldap/ldap.conf and manpage to new package libldap-common.
+
+ -- Helmut Grohne   Tue, 10 May 2016 17:41:23 +0200
+
 openldap (2.4.42+dfsg-2) unstable; urgency=medium
 
   [ Ryan Tandy ]
--- openldap-2.4.42+dfsg/debian/control
+++ openldap-2.4.42+dfsg/debian/control
@@ -86,12 +86,22 @@
 Multi-Arch: same
 Conflicts: ldap-utils (<= 2.1.23-1)
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, libldap-common (= 
${source:Version})
 Replaces: libldap2, libldap-2.3-0
 Description: OpenLDAP libraries 
  These are the run-time libraries for the OpenLDAP (Lightweight Directory
  Access Protocol) servers and clients.
 
+Package: libldap-common
+Section: libs
+Priority: standard
+Architecture: all
+Multi-Arch: foreign
+Replaces: libldap-2.4-2 (<< 2.4.42+dfsg-2.1)
+Description: OpenLDAP common files for libraries
+ These are common files for the run-time libraries for the OpenLDAP
+ (Lightweight Directory Access Protocol) servers and clients.
+
 Package: libldap-2.4-2-dbg
 Section: debug
 Priority: extra
--- openldap-2.4.42+dfsg/debian/libldap-2.4-2.install
+++ openldap-2.4.42+dfsg/debian/libldap-2.4-2.install
@@ -2,4 +2,3 @@
 usr/lib/*/liblber-2.4.so.2.*.*
 usr/lib/*/libldap_r-2.4.so.2
 usr/lib/*/libldap_r-2.4.so.2.*.*
-etc/ldap/ldap.conf
--- openldap-2.4.42+dfsg/debian/libldap-2.4-2.manpages
+++ openldap-2.4.42+dfsg/debian/libldap-2.4-2.manpages
@@ -1 +0,0 @@
-debian/tmp/usr/share/man/man5/ldap.conf.5
--- openldap-2.4.42+dfsg/debian/libldap-common.install
+++ openldap-2.4.42+dfsg/debian/libldap-common.install
@@ -0,0 +1 @@
+etc/ldap/ldap.conf
--- openldap-2.4.42+dfsg/debian/libldap-common.manpages
+++ openldap-2.4.42+dfsg/debian/libldap-common.manpages
@@ -0,0 +1 @@
+debian/tmp/usr/share/man/man5/ldap.conf.5

Bug#823962: parl-desktop-strict: not installable in sid

[Ralf Treinen]

Package: parl-desktop-strict
Version: 1.9.2 
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

parl-desktop-strict is not installable in sid since it conflicts with
libreoffice-style-galaxy. But it also depends on this package, via the
following dependency chain: 

parl-desktop-strict (1.9.2)
   ↓ parl-desktop
parl-desktop (1.9.2)
   ↓ libreoffice-style-tango
libreoffice-style-tango (1:5.1.3~rc2-3)
   ↓ libreoffice-style-default
libreoffice-style-galaxy (1:5.1.3~rc2-3)

In fact this was already with version 1.0.9 of parl-desktop-strict. The
package isnot installable in sid since 2015-06-02.

-Ralf.

Bug#823898: libconfig-model-systemd-perl: Minor error in package description (a spurious "OK"?)

[Dominique Dumont]

On Tue, 10 May 2016 15:49:06 +0100 Justin B Rye  
wrote:
> Well, for a start "systemd" is canonically lowercase.  Also, this is a
> capitalised verb phrase (saying what the package does) instead of an
> uncapitalised noun phrase (saying what it is); for enhanced DevRef
> compliance you could make it:
> 
>  Description: editor and validator for systemd configuration files
> or
>  Description: systemd configuration file editor and validator

ok. I also have to fix upstream.

> #  Config::Model::Systemd provides a configuration editor for the
> #  configuration file of Systemd, i.e. all files in
> #  ~/.config/systemd/user/ or all files in /etc/systemd/system/ Ok.
> 
> This appears to be saying that systemd has only one configuration
> file, which consists of all the files in one of two places.

Good point. Fixed.

> Upstream has "Ok. I simplified".  It seems a bit pointless to phrase
> things in an oversimplified way when that just means you're going to
> have to explain it twice.  If I'm correctly understanding this, why
> not just say:
> 
>  Description: systemd configuration file editor and validator
>   Config::Model::Systemd provides configuration models for systemd
>   configuration files (that is, all files in /etc/systemd/system/ and
>   ~/.config/systemd/user/). Config::Model, Config::Model::TkUI, and cme
>   can use these models for configuration editing and validation.

I'd rather keep the 2 explanations which answer 2 different questions.

The first question is, why should a user install this package ? I hope that the
first explanation answers that in the simplest possible way.

Then other user may wonder what is the content of this package, I.e. how does 
it compare to libconfig-model-perl. Hence the 2nd explanation.

I've also forgotten to add a recommend field for cme and libconfig-model-tkui-
perl. Without these packages, libconfig-model-systemd-perl is pretty useless.

Thanks for the suggestions

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#823956: [Pkg-php-pecl] Bug#823956: php-json dependency and build-dependency issues.

[Ondřej Surý]

Hmmph, I wanted php5.6-json to go, but I might keep it a bit longer
since we are keeping php5 a bit longer in unstable.

I'll take care of this.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Vše pro chleba (https://vseprochleba.cz) – Potřeby pro pečení chleba
všeho druhu

On Tue, May 10, 2016, at 19:40, peter green wrote:
> Package: php5-json
> Severity: serious
> Version: 1.3.7-1
> 
> php5-json depends on the cruft package libjson-c2 which is no longer 
> built from the json-c source package.
> 
> The release team attempted to schedule a binnmu but it was blocked due 
> to the removal of dh-php5.
> 
> Furthermore even in an environment where dh-php5 is available the binnmu 
> succeeds but doesn't fix the problem because the dependency is 
> hardcoded. A debdiff changing the dependency is available at 
> http://debdiffs.raspbian.org/main/p/php-json/php-json_1.3.7-1%2brpi1.debdiff
> 
> ___
> Pkg-php-pecl mailing list
> pkg-php-p...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-pecl

Bug#823706: Lazarus 1.6 source files are missing

[Paul Gevers]

Hi Denis,

On 10-05-16 11:11, Denis Kozlov wrote:
> Is there a reference (e.g. discussion on a mailing list, etc) which
> identifies the quality requirements that Lazarus source files don't
> meet? There is a chance that they could get addressed upstream.

Well, the general reference for all Debian packages is the Debian
policy¹. However, that is a rather lengthy document, so I expect you to
refer here to what is specific in Lazarus source that is NOK from Debian
perspective. The main reason for not including all upstream sources is
that Debian doesn't consider all of them to be free. The best source for
that is (the history of) debian/orig-tar.sh² and the changelog³, e.g.:
 - AggPas: removed to honor free licencing. (Closes: Bug#708695)

Another major reason why we need to reorder stuff is that we want to
build from source. This means we recreate all Makefiles that are created
from Makefile.fpc files, we will not use shipped binary files, so we
recreate them from source, e.g. for icons. You can all find that back in
the debian/rules file [4].

Do you need more info?

Paul

¹ https://www.debian.org/doc/debian-policy/
²
https://anonscm.debian.org/cgit/pkg-pascal/lazarus.git/log/debian/orig-tar.sh
³
https://anonscm.debian.org/cgit/pkg-pascal/lazarus.git/tree/debian/changelog
[4] https://anonscm.debian.org/cgit/pkg-pascal/lazarus.git/tree/debian/rules



signature.asc
Description: OpenPGP digital signature

Bug#823961: herbstluftwm: please make the build reproducible (timestamps)

[Fabian Wolff]

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

Hi!

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

The attached patch attempts to make the build reproducible by
referring to the SOURCE_DATE_EPOCH environment variable [2] for
deterministic timestamps instead of using the current system time.
However, a fallback is also provided in case SOURCE_DATE_EPOCH is not
set.

Regards,
Fabian Wolff

[1] https://wiki.debian.org/ReproducibleBuilds
[2] https://reproducible-builds.org/specs/source-date-epoch/
--- a/Makefile
+++ b/Makefile
@@ -18,6 +18,15 @@
 HERBSTLUFTWMDOC = doc/herbstluftwm.txt
 TUTORIAL = doc/herbstluftwm-tutorial.txt
 
+DATE_FMT = %Y-%m-%d
+ifdef SOURCE_DATE_EPOCH
+BUILD_DATE ?= $(shell date -u -d "@$(SOURCE_DATE_EPOCH)" "+$(DATE_FMT)"  2>/dev/null || date -u -r "$(SOURCE_DATE_EPOCH)" "+$(DATE_FMT)" 2>/dev/null || date -u "+$(DATE_FMT)")
+else
+BUILD_DATE ?= $(shell date "+$(DATE_FMT)")
+endif
+
+export CPPFLAGS += -DBUILD_DATE="\"$(BUILD_DATE)\""
+
 .PHONY: depend all all-nodoc doc install install-nodoc info www
 .PHONY: cleandoc cleanwww cleandeps clean
 
@@ -93,7 +102,7 @@
 
 doc/%.1 doc/%.7: doc/%.txt version.mk
 	$(call colorecho,DOC,$@)
-	$(VERBOSE) $(A2X) -f manpage -a "herbstluftwmversion=herbstluftwm $(VERSION)" -a "date=`date +%Y-%m-%d`" $<
+	$(VERBOSE) $(A2X) -f manpage -a "herbstluftwmversion=herbstluftwm $(VERSION)" -a "date=$(BUILD_DATE)" $<
 
 doc/%.html: doc/%.txt version.mk
 	$(call colorecho,DOC,$@)
--- a/ipc-client/main.c
+++ b/ipc-client/main.c
@@ -17,7 +17,7 @@
 #include "client-utils.h"
 
 #define HERBSTCLIENT_VERSION_STRING \
-"herbstclient " HERBSTLUFT_VERSION " (built on " __DATE__ ")\n"
+"herbstclient " HERBSTLUFT_VERSION " (built on " BUILD_DATE ")\n"
 
 void print_help(char* command, FILE* file);
 void init_hook_regex(int argc, char* argv[]);
--- a/src/globals.h
+++ b/src/globals.h
@@ -12,7 +12,7 @@
 #define HERBSTLUFT_AUTOSTART "herbstluftwm/autostart"
 #define WINDOW_MANAGER_NAME "herbstluftwm"
 #define HERBSTLUFT_VERSION_STRING \
-WINDOW_MANAGER_NAME " " HERBSTLUFT_VERSION " (built on " __DATE__ ")"
+WINDOW_MANAGER_NAME " " HERBSTLUFT_VERSION " (built on " BUILD_DATE ")"
 
 #define HERBST_FRAME_CLASS "_HERBST_FRAME"
 #define HERBST_DECORATION_CLASS "_HERBST_DECORATION"

Bug#823960: php7.0: "Arch: all" packages do not need the whole build process to be created

[Santiago Vila]

Package: src:php7.0
Version: 7.0.6-1

Dear maintainer:

As in Bug #823954, the architecture-independent binary packages
generated by this source package do not really need any C source
compiling to be created.

The attached patch works for me, but it may need some tweaking.
I've only tested the "dpkg-buildpackage -A" part, but I'm confident
that either it will work with "dpkg-buildpackage -B" or it will be
very easy to fix.

This time the patch is a lot smaller because debian/rules is using dh.

On my i3 at home, "dpkg-buildpackage -A" takes 38 minutes to finish.
With this patch, only 20 seconds.

Note: The rationale for doing this is that source only uploads (which
are currently optional but will hopefully be the norm some day) are
handled by different autobuilders. There is one autobuilder which only
creates "Arch: all" packages, so this is not just a theoretical time
saving but a real one.


Thanks.--- a/debian/rules
+++ b/debian/rules
@@ -306,12 +306,16 @@ override_dh_auto_clean: unprepared
# remove shared config.cache
rm -f $(CURDIR)/config.cache
 
-override_dh_auto_configure: prepared
+override_dh_auto_configure-indep:
+
+override_dh_auto_configure-arch: prepared
for target in $(TARGETS); do \
  dh_auto_configure --builddirectory $${target}-build $(PARALLEL) -- 
$$(eval echo \$${$${target}_config}); \
done
 
-override_dh_auto_build:
+override_dh_auto_build-indep:
+
+override_dh_auto_build-arch:
for target in $(TARGETS); do \
  dh_auto_build --builddirectory $${target}-build $(PARALLEL); \
done

Bug#821874: RM: faumachine [amd64 i386] -- RoQA, unmaintained, RC-Buggy, Depends on to be removed packages

[Stefan Potyra]

Hi Tobi,

thanks again for your comments and suggestions!

There is good news: We've got a building and working upstream version with the
current gcc in unstable :).

I'm preparing a new debian package now. I hope to get it done and uploaded
soonish (new DM-key not yet in archive, but Fuddl will upload the new package).

I'll give a short update tomorrow.

Cheers,
  Stefan.

Bug#823906: apt-cudf: unable to find a solution with an out-of-date chroot

[Ralf Treinen]

Hi,

On Tue, May 10, 2016 at 11:18:56AM +0200, Aurelien Jarno wrote:

> We use sbuild wit the cudf resolver on the build daemons, with the
> following optimization criteria:
> 
>   $aspcud_criteria = 
> '-removed,-changed,-new,-count(solution,APT-Release:=/experimental/)';
> 
> Unfortunately this doesn't work when the available packages are newer
> than the one installed in the chroots.

That is very strange. As a first remark, the optimisation criterion should
not be at stake here. The optimisation criterion cannot make the search for
a solution fail in case there is a solution, the criterion only
serves to decide which solution to select in case there are several
solutions.

> This can also be reproduced using the following command:
> 
> | apt-get --solver aspcud -o 'APT::Solver::Strict-Pinning=false' -o 
> 'APT::Solver::aspcud::Preferences=-removed,-changed,-new,-count(solution,APT-Release:=/experimental/)'
>  build-dep qgis

A quick test on my home machine does not reproduce the error. Anyway, I guess
you have to specify that you want to satisfy the build-dependencies of
qgis/experimental, I guess ?

I'll ask on the dose developers list.

Thanks for your bug report -Ralf.

Bug#823959: RFS: rainbow-delimiters/2.1.3-1 [ITP] -- Emacs mode to colour-code delimiters according to their depth

[Sean Whitton]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package rainbow-delimiters.

Upstream's blurb:

> rainbow-delimiters is a "rainbow parentheses"-like mode which
> highlights delimiters such as parentheses, brackets or braces
> according to their depth. Each successive level is highlighted in a
> different color. This makes it easy to spot matching delimiters,
> orient yourself in the code, and tell which statements are at a given
> depth.

I intend to maintain this as part of the pkg-emacsen team.

* Package name: rainbow-delimiters
  Version : 2.1.3-1
  Upstream Author : Fanael Linithien 
* URL : http://github.com/Fanael/rainbow-delimiters
* License : GPL-3+
  Section : lisp

Download with dget:

dget -x 
http://mentors.debian.net/debian/pool/main/r/rainbow-delimiters/rainbow-delimiters_2.1.3-1.dsc

Or build it with gbp:

gbp clone --pristine-tar 
https://anonscm.debian.org/git/pkg-emacsen/pkg/rainbow-delimiters.git
cd zenburn-emacs
gbp buildpackage

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#823589: mplayer: Please create dummy package for upgrades from jessie

[Adam Conrad]

Package: mplayer
Version: 2:1.3.0-1
Followup-For: Bug #823589
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch



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

  * Add mplayer2 transitional package to fix upgrades (LP: #1580268)

So, I noticed after fixing this in Ubuntu that you fixed it in Debian
git 48 hours ago.  Your fix is, however, incomplete (notice the extra
parts of my diff that aren't included in your commit, where I version
the Replaces, and change the Conflict to a versioned Breaks).

It would be lovely if you swapped in my fix for yours (at least the
missing bits).

... Adam

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

Kernel: Linux 4.4.0-21-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru mplayer-1.3.0/debian/control mplayer-1.3.0/debian/control
--- mplayer-1.3.0/debian/control	2016-04-17 13:14:24.0 -0600
+++ mplayer-1.3.0/debian/control	2016-05-10 11:57:44.0 -0600
@@ -147,6 +147,16 @@
  (1 or 2 passes), libavcodec, PCM/MP3/VBRMP3 audio. Also has stream
  copying and video resizing capabilities.
 
+# This can be dropped after yakkety/stretch release, whichever is later:
+Package: mplayer2
+Section: oldlibs
+Architecture: all
+Multi-Arch: foreign
+Depends: mplayer (>= 2:1.2)
+Description: transitional package from mplayer2 to mplayer
+ This package exists to upgrade mplayer2 users to mplayer; it can be safely
+ removed once the upgrade has been performed.
+
 Package: mplayer
 Architecture: any
 Multi-Arch: foreign
@@ -163,9 +173,9 @@
  mencoder (<< 2:1.0~rc3+svn20090426-2),
  mplayer-doc (<< 2:1.0~rc3+svn20090426-2),
  mplayer-nogui (<< 2:1.0~rc3+svn20090426-2),
- mplayer2
-Conflicts:
- mplayer2
+ mplayer2 (<< 2:1.2)
+Breaks:
+ mplayer2 (<< 2:1.2)
 Description: movie player for Unix-like systems
  MPlayer plays most MPEG, VOB, AVI, Ogg/OGM, VIVO,
  ASF/WMA/WMV, QT/MOV/MP4, FLI, RM, NuppelVideo, yuv4mpeg, FILM, RoQ, PVA files,

Bug#798780: release.debian.org: Please let playonlinux migrate to testing

[Jens Reyer]

On 05/08/2016 06:16 PM, Bertrand Marc wrote:
> Le 10/04/2016 13:52, Andreas Beckmann a écrit :
>> On Sun, 21 Feb 2016 11:00:14 +0100 Bertrand Marc 
>> wrote:
>>> Do you think we could find a solution to restore the dependency and let
>>> playonlinux migrate to testing ?
>>
>> What about
>>
>> * split a playonlinux-data package from playonlinux containing
>>   /usr/share/playonlinux/*
>>   /usr/share/locale/*
>>   mark as Multi-Arch: foreign
>>   document in the description that a foreign architecture may be needed
>>   to install playonlinux on amd64 (dpkg --add-architecture i386)
>>
>> * make playonlinux arch:any
>>   Depends: playonlinux-data (= ${source:Version})
>>
>> * add Build-Depends: wine32 | wine32-development
>>   (instead of enumerating the architectures in the playonlinux package)

I assume both packages are part of src:playonlinux, and playonlinux-data
is arch:all?
But why "Multi-Arch: foreign" for playonlinux-data then?

Otherwise (playonlinux-data arch:any, and src:playonlinux build-depends
on wine32) no playonlinux* package at all would be on e.g. amd64. So
users would see no playonlinux* package, and thus they wouldn't see the
documentation to install the foreign arch.

But even if playonlinux-data is available on amd64, I doubt that the
documentation in the long package description is enough. Remember that
POL is intended to give a quick and easy start. A part of its target
audience might not even know that long package descriptions exist.

So this solution makes sure that POL works *once* it's been installed.
But it doesn't help greatly to install it.


Alternatively you could make something similar to what we have in the
wine packaging.

There wine (arch:all) depends on wine32|wine64 (which are arch specific,
and only available on archs with the correct 32-/64 bitness).
Installations without wine32 are considered broken generally, but there
are some use cases that work without wine32. I think the same is true
for POL: you generally want wine32, but you don't need it in *every* case.

So:

* Keep a dependency from playonlinux on "wine|wine-development".
  Nowadays these packages provide the /usr/bin/wine(-development)
  and /usr/bin/wineserver(-development) wrappers/links, it's not an
  empty package as stated elsewhere.

* Make playonlinux (arch:all) *recommend* wine32|wine32-development.
  This /should/ solve the release migration issue.

* Change /usr/bin/playonlinux to be a wrapper script that checks
  if wine32 is installed (test if the executables /usr/lib/wine/wine
  or /usr/lib/wine-development/wine exist).
  If yes, execute the real playonlinux.
  If no, give the user instructions how to install wine32. If you
  think wine32 is needed in any case, you'd have to abort now.
  Otherwise just continue after displaying the warning.
  Wine shows the warning only in the terminal. I think POL would
  have to use something like zenity (we had that in Wine once, but
  it was removed for reasons unknown to me).

* Additionally you might add the same test/warning to the postinst
  as suggested in https://bugs.debian.org/783875#44.

* Also additionally you might add the instructions to install wine32
  from i386 in the description (as Andreas suggested). I don't know
  why we don't have that in Wine.

You  probably need some versioning for the wine dependencies. I can help
with them (and the other changes) if you want to pick this route.

For reference the /usr/bin/wine(-development) wrapper script:
http://anonscm.debian.org/cgit/pkg-wine/wine.git/tree/debian/scripts/wine

Greets
jre

Bug#674514: eog-plugins: Missing dbg package

[Michael Biebl]

Hi Frederik

On Fri, 25 May 2012 09:20:06 +0200 Frederik Himpe  wrote:
> Package: eog-plugins
> Version: 3.4.0-1
> Severity: normal
> 
> eog-plugins is missing a dbg package containing the debugging symbols. It 
> makes
> debugging bugs like https://bugzilla.gnome.org/show_bug.cgi?id=676735 harder.

We have automatic dbgsym package now [1], so this bug report can be closed.

Regards,
Michael

[1] https://lists.debian.org/debian-devel/2015/12/msg00262.html

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



signature.asc
Description: OpenPGP digital signature

Bug#811076: eog-plugins: Python related depends too tight: Causes problems during transitions

[Michael Biebl]

Hi Scott

On Fri, 15 Jan 2016 08:44:07 -0500 Scott Kitterman
 wrote:
> Package: eog-plugins
> Version: 3.16.3-1
> Severity: important
> Tags: patch
> 
> Currently, eog-plugins gets python3 interpreter depends like this (when
> built with python3.4 as default python3):
> 
> python3 (<< 3.5), python3 (>= 3.4~), python3.4
> 
> As a result, eog-plugins became uninstallable once the default was updated
> to python3.5.  While a binNMU corrected this, it's entirely unnecessary. I
> looked and there's no compiled python extensions in the plugins, it's all
> arch all python that does not need rebuilding when the version changes.
> 
> Ths problem is that because dh_python3 was being called for all plugins, some
> of which are compiled, dh_python treated them as python3 extensions for
> dependency calculation.
> 
> Please see the attached patch that addresses this issue.  With it the python3
> interpreter depend is:
> 
> python3:any (>= 3.3.2-2~)
> 
> No more trouble during transitions, the package is always installable.

That patch looks like it could easily get out-of-date once new py files
are added as it can be easily forgotten to update the list.
I'm therefore a bit worried to apply the patch as is.

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#823958: RM: libtest2-perl -- ROM; obsolete

[gregor herrmann]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please remove libtest2-perl from the archive.

Test2 has been merged into Test-Simple/libtest-simple-perl.

No rdeps or real world installations.


Cheers,
gregor


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJXMh95XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG2j4P/0EikK6lWK4qRM7LBVbWpY/J
dgSniYWeErwmJHF1WoTjUWi77ul+ToHAmTKqcPXHv8UipG1RZc6K2IAc0UG8Qn0F
Y+axJ1BlUUbuOOG+pDxVEGF3mssQ2upILPDpwxy1rTveD6dIVe0AUw4iiLxHXNsy
EngFpBY5FyBmbQK2IcdSkdMcL6vVvUfWgOh1Kwq6uG34PLQJq6ybf+XhYJCbKpjH
iiJ5zaxcLtpPayLfmoxeZmeiGfXiYhPRvUYHyyXO+XE0qtanJQpROcwh3SLiKXWi
KEx/2lV0cFWwJedISBibL1EmekwOC49RhobSw39B8/q3g7gSqbsTM1O1gEjRt3+b
R+j/21lfWxAybP+OKTd9x6hdTGSp1hG/yqDCOudYTSOiVN4CsgSGgQYYJmc75COV
aaNPiptIeoEgUi1b1PLU14MojSkEKtj3t639Bky5+aglcuJz+2kbcHX9SzQBqaBU
6AQPiLjiweN28lD4COh8/mlIGCqRRYYK9qxNfHbx54CLAjgFtEK54gYq6xtMjQLq
hSwP4in1j1hF9nyZQJNPDeBrgOsBwq7iKe8sTva85DboPeE4M4uIWQhC8nRrvgiU
hL9///fJP1U80VINkykJIY6Yl1tw+sUctreUeDJXdqPBwBtP30GWMHSJ2fsd8zUa
RXGYWEHSUTr0OSLygier
=CIux
-END PGP SIGNATURE-

Bug#823957: ITP: rainbow-delimiters -- Emacs mode to colour-code delimiters according to their depth

[Sean Whitton]

Package: wnpp
Severity: wishlist
Owner: Sean Whitton 

* Package name: rainbow-delimiters
  Version : 2.1.3
  Upstream Author : Fanael Linithien 
* URL : https://github.com/Fanael/rainbow-delimiters
* License : GPL-3+
  Programming Lang: Emacs Lisp
  Description : Emacs mode to colour-code delimiters according to their 
depth

A useful Emacs mode for working with languages with lots of delimiters,
e.g. Lisp.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#822613: RFS: dynamic-graph/3.0.0-1

[Andrey Rahmatullin]

On Tue, May 10, 2016 at 03:19:41PM +, Gianfranco Costamagna wrote:
> >Your package has several lintian-detected problems of various severiuty,
> >but the one about embedded jQuery is a blocker one. You will need to fix
> >it before having a chance for the package to be uploaded. Please look into
> >other issues as well.
> 
> 
> Not embedding it might result in a broken documentation
> https://lists.debian.org/debian-devel/2014/10/msg00795.html
> 
> So, I'm not sure if that tag is worth a fix...
Yeah, in that case I would investigate the case further.

> (BTW you commented on traitets, fed, dynamic-graph, but you didn't set 
> yourself
> as owner, do you plan to also sponsor the packages?)
No, I was doing some triaging.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#823956: php-json dependency and build-dependency issues.

[peter green]

Package: php5-json
Severity: serious
Version: 1.3.7-1

php5-json depends on the cruft package libjson-c2 which is no longer 
built from the json-c source package.


The release team attempted to schedule a binnmu but it was blocked due 
to the removal of dh-php5.


Furthermore even in an environment where dh-php5 is available the binnmu 
succeeds but doesn't fix the problem because the dependency is 
hardcoded. A debdiff changing the dependency is available at 
http://debdiffs.raspbian.org/main/p/php-json/php-json_1.3.7-1%2brpi1.debdiff

Bug#823955: grub-uboot: crashed during load from U-Boot (Exynos 5422)

[Steinar H. Gunderson]

Package: grub-uboot
Version: 2.02~beta2-36
Severity: important

Hi,

I have an ODROID XU4 (Exynos 5422-based), and I want to run GRUB
(chainloaded from U-Boot). I've been generally following the
instructions on

  https://wiki.linaro.org/LEG/Engineering/Kernel/GRUBonUBOOT

In particular, I've run grub-install --boot-directory=/fatboot
(which is a small FAT partition at the start of the eMMC flash
on the device), which created a core.img, although it warned
about no hints for my target platform.

I try to boot it from U-Boot manually like this:

  Exynos5422 # setenv grub_bootdev hd0,msdos1
  Exynos5422 # setenv loadaddr 0x40008000
  Exynos5422 # fatload mmc 0:1 $loadaddr /grub/arm-uboot/core.img
  reading /grub/arm-uboot/core.img
  
  48540 bytes read
  Exynos5422 # bootm
  ## Booting kernel from Legacy Image at 40008000 ...
 Image Name:
 Image Type:   ARM Linux Kernel Image (uncompressed)
 Data Size:48476 Bytes = 47.3 KiB
 Load Address: 0800
 Entry Point:  0800
 Verifying Checksum ... OK
 Loading Kernel Image ... OK
  OK
  
  Starting kernel ...
  
  prefetch abort
  pc : []  lr : [<001a>]
  sp : be766f38  ip :  fp : be87119c
  r10: be8ac824  r9 :  r8 : be766f30
  r7 :   r6 :  r5 : 0800  r4 : be8ad000
  r3 : be766fa8  r2 : 4100 r1 : 1f43  r0 : 
  Flags: nZCv  IRQs off  FIQs off  Mode HYP_32
  Resetting CPU ...
  
  emmc resetting ...
  resetting ...

At this point, it resets and goes back to U-Boot.

This bug is one out of two, I guess: Either something is broken
in grub-uboot itself, or some documentation would be appreciated,
since there's not even a README in the current grub-uboot or
grub-uboot-bin packages. :-)

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/mmcblk0p2 / ext4 rw,noatime,errors=remount-ro,data=ordered 0 0
/dev/mmcblk0p1 /fatboot vfat 
rw,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro
 0 0
*** END /proc/mounts

*** BEGIN /proc/mdstat
cat: /proc/mdstat: No such file or directory
*** END /proc/mdstat

*** BEGIN LVM
*** END LVM

*** BEGIN /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root 13 Feb 11 17:28 mmc-064GE2_0x8f583699 -> ../../mmcblk0
lrwxrwxrwx 1 root root 15 Feb 11 17:28 mmc-064GE2_0x8f583699-part1 -> 
../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Feb 11 17:28 mmc-064GE2_0x8f583699-part2 -> 
../../mmcblk0p2
*** END /dev/disk/by-id

*** BEGIN /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 15 Feb 11 17:28 96C3-9298 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Feb 11 17:28 e139ce78-9841-40fe-8823-96a304a09859 -> 
../../mmcblk0p2
*** END /dev/disk/by-uuid

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

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

Versions of packages grub-uboot depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  dpkg   1.18.7
ii  grub-common2.02~beta2-36
ii  grub-uboot-bin 2.02~beta2-36
ii  grub2-common   2.02~beta2-36
ii  ucf3.0036

grub-uboot recommends no packages.

grub-uboot suggests no packages.

-- debconf information:
  grub2/kfreebsd_cmdline_default: quiet
  grub2/kfreebsd_cmdline:
  grub2/linux_cmdline_default: quiet
  grub2/force_efi_extra_removable: false
  grub2/device_map_regenerated:
  grub2/linux_cmdline:

Bug#823918: apt-get --solver dump doesn't add Preferences field to edsp file

[David Kalnischkies]

On Tue, May 10, 2016 at 04:25:23PM +0200, Pietro Abate wrote:
> On 10/05/16 15:09, David Kalnischkies wrote:
> > > 'APT::Solver::aspcud::Preferences=-removed,-changed,-new,-count(solution,APT-Release:=/experimental/)'
> > ^^
> > 
> > The preferences string is missing as it isn't sent – and it isn't sent 
> > because it
> > doesn't apply to the specified solver: You requested 'dump' to resolve it, 
> > but
> > the preferences string is for 'aspcud'.
> > 
> > So, seems to work as intended, doesn't it – or did I miss anything?
> 
> I see. YEs, it respect the spec. But as it is the this option
> (APT::Solver::aspcud::Preferences) is actually useless because aspcud
> will never receive this information, correct ? 

You answered that yourself in your next mail, I notice through that the
spec is disagreeing with itself: The configuration section mentions this
solver specific option, while later it only mentions the all-solver
option. It is all-solver for the strict-pinning only option.

That seems rather inconsistent and is also not really consistent with
how apt usually is configured ala value = config("apt::specific::foo",
config("apt::foo", default_value));

So, I will take that bugreport as a wish to implement & document that
consistently for both – lets just hope we never have a solver called
'preferences' or 'strict-pinning'. ;)

[apt would actually support that just fine, it would just be confusing
as hell for a human to look at]


> This make me think that maybe it would be worth adding the solver to
> be called to the edsp file as well. Something like :
> 
> Solver: aspcud
> Preferences: ...
> 
> This will make the edsp fully contained.

As you wish :)


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#823954: php5: Binary package "php5" does not need the whole build process to be created

[Santiago Vila]

Package: src:php5
Version: 5.6.21+dfsg-1

Dear maintainer:

The "php5" binary package is "Architecture: all" and it does not
really contain any file which is generated by compiling C source code.

So, it would make sense if "dpkg-buildpackage -A" generated this
package directly without "building" anything.

Briefly, the attached patch does this:

* The old "build" target is renamed to "build-arch".

* The old "install" target is renamed to "install-arch".

* A new "build-indep" target is created which does nothing
  (because there is really nothing to build).

* A new "install-indep" target is created which just puts
  /usr/share/bug/php5/control in place. This is removed from
  the old install target.

* The /usr/share/bug/php5/script symlink is handled by dh_link
  and "debian/php5.links".


I've checked that "dpkg-buildpackage -A" generates exactly the same
"php5" package as before. I believe "dpkg-buildpackage -B" should also
work, but in either case, I am confindent that it would be easy to
fix if it does not.

In my i3 at home, the patch reduces build time for "dpkg-buildpackage -A"
from 85 minutes to a few seconds.

Thanks.--- /dev/null
+++ b/debian/php5.links
@@ -0,0 +1 @@
+usr/share/bug/php5-common/script usr/share/bug/php5/script
--- a/debian/rules
+++ b/debian/rules
@@ -212,7 +212,9 @@ else
echo 'nocheck found in DEB_BUILD_OPTIONS or unsupported architecture' | 
tee test-results.txt
 endif
 
-build: build-apache2-stamp build-apache2filter-stamp build-cgi-stamp 
build-cli-stamp build-phpdbg-stamp build-embed-stamp build-fpm-stamp 
test-results.txt
+build-indep:
+
+build-arch: build-apache2-stamp build-apache2filter-stamp build-cgi-stamp 
build-cli-stamp build-phpdbg-stamp build-embed-stamp build-fpm-stamp 
test-results.txt
 
 build-apache2-stamp: configure-apache2-stamp
dh_testdir
@@ -500,8 +502,14 @@ clean: unprepared
 
 PCNTL_FUNCTIONS := $(shell < ext/pcntl/php_pcntl.h sed -ne "/^PHP_FUNCTION/ 
s/PHP_FUNCTION(\(.*\));/\1/;t end;d;:end p" | tr '\n' ',')
 
-install: DH_OPTIONS=
-install: build
+install-indep:
+   # Install reportbug for php5 package
+   mkdir -p debian/php5/usr/share/bug/php5
+   install -m644 debian/php5.bug.control 
debian/php5/usr/share/bug/php5/control
+
+install-arch: DH_OPTIONS=-a
+install-arch: install-arch-stamp
+install-arch-stamp: build-arch
dh_testdir
dh_testroot
dh_prep
@@ -533,11 +541,6 @@ ifeq (yes,$(RUN_TESTS))
cp test-results.txt debian/php5-common/usr/share/doc/php5-common/
 endif
 
-   # Install reportbug for php5 package
-   mkdir -p debian/php5/usr/share/bug/php5
-   install -m644 debian/php5.bug.control 
debian/php5/usr/share/bug/php5/control
-   ln -s ../php5-common/script debian/php5/usr/share/bug/php5/script
-
# Install helper shell fragment
install -m644 debian/php5-helper 
$(CURDIR)/debian/php5-common/usr/share/php5/
install -m644 debian/debhelper/php5-maintscript-helper 
$(CURDIR)/debian/php5-common/usr/share/php5/
@@ -672,12 +675,12 @@ endif
# directories cleanup:
-rmdir -p debian/libapache2-mod-php5/usr/share/man/man1
 
-   touch install-stamp
+   touch install-arch-stamp
 
 # Build architecture-independent files here.
 # Pass -i to all debhelper commands in this target to reduce clutter.
 binary-indep: DH_OPTIONS=-i
-binary-indep: build install
+binary-indep: install-indep
# Need this version of debhelper for DH_OPTIONS to work.
dh_testdir
dh_testroot
@@ -698,7 +701,8 @@ binary-indep: build install
dh_builddeb
 
 # Build architecture-dependent files here.
-binary-arch: build install
+binary-arch: DH_OPTIONS=-a
+binary-arch: build-arch install-arch
# Need this version of debhelper for DH_OPTIONS to work.
dh_testdir
dh_testroot
@@ -855,7 +859,5 @@ binary-arch: build install
dh_builddeb -s
 
 binary: binary-arch binary-indep
-build-arch: build
-build-indep: build
 
 .PHONY: build build-arch build-indep clean binary-indep binary-arch binary 
install configure

Bug#821239: jessie-pu: package ledgersmb/1.3.47-1~deb8u1

[Robert James Clay]

Jonathan,

 I have not seen  a response to this since I sent it.  Should I have removed 
the 'moreinfo' tag when I originally responded?

On Monday, April 25, 2016 09:10:44 AM Robert James Clay wrote:
> On Friday, April 22, 2016 06:32:15 PM Jonathan Wiltshire wrote:
> > Control: tag -1 moreinfo
> > 
> > On Sat, Apr 16, 2016 at 06:52:45PM -0400, Robert James Clay wrote:
> > > Please accept ledgersmb_1.3.47-1~deb8u1 for the next Jessie point
> > > release.
> > > It resolves the issues with the current version of ledgersmb in 'jessie'
> > > (1.3.40-1) of the package failing to complete an install without errors.
> > 
> > Could you expand on the details please? The proposed patch is 139K and:
> >  97 files changed, 1286 insertions(+), 623 deletions(-)
> > 
> > Quite a lot, and the changelog includes words like "New upstream release"
> > which immediately rings alarm bells.
> 
> Admittedly, the upstream changes come to about 70% of the diff but all
> of those changes between LedgerSMB v1.3.40 and v1.3.47 were bug fixes, not
> feature changes (which didn't happen until the now released but not yet
> uploaded to Debian v1.4.x series), and were unrelated to the issues with
> the package installation errors. And of the upstream versions between those
> two, only v1.3.46-1 was uploaded to Debian and that also turned out to have
> an package installation error, albeit not one as serious as with the
> 1.3.40-1 package. The only way I can see to avoid all that is by creating a
> 1.3.40-2 package for jessie-pu, and backporting the packaging changes as
> necessary but newer upstream versions have already been uploaded so such a
> package version would not be able to go through the usual sequence of
> unstable -> testing -> jessie- pu.
> 
> A long standing installation related issue had been that the package
> installation process failed to configure the Ledgersmb DB admin user with
> the necessary credentials when the non-default option to do so was
> selected.  With 1.3.40-1 when the debconf option was selected, there was
> also a "syntax error" that came up during the package installation (Debian
> bug #698298).  That could be aborted and one could then run the
> install/upgrade again, not doing the package configuration;  but one would
> then have to set the user name & password for the LedgerSMB Database Admin
> manually in any case and there were also then apache2 related errors that
> come up resulting from the LedgerSMB Apache configuration, which ones
> depending on if the apache2 package is already installed and what modules
> might already be configured.
> 
> With 1.3.46-1, the issue with configuring the LedgerSMB database admin
> user was resolved by dropping the use of dbconfig-common and adding a
> script installed by the package that would directly set user name and
> password for it.  It was also intended to resolve the issues with the
> LedgerSMB Apache configuration but it turned out there was still such an
> issue, related to enabling the Apache rewrite module as necessary with the
> ledgersmb package install.  That in turn was resolved with the 1.3.47-1
> package version.
> 
> There were other package related changes between 1.3.40-1 and 1.3.47-1
> but the above summarizes the ones related to the package installation
> errors, which is what I feel is needed to resolve the issue with such
> errors being seen with the current version of LedgerSMB in the current
> Debian Stable ('Jessie'). If you have any other questions, please let me
> know.
> 
> 
> 
> Regards,
>Robert James Clay
>j...@rocasa.us


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