Bug#780178: armagetronad: several security vulnerabilities and network packets can terminate the connection

[Markus Koschany]

Source: armagetronad
Version: 0.2.8.3.2-1
Severity: serious
Tags: security

A new version of ArmagetronAD was released a few days ago which fixes
primarily possible security vulnerabilities and crashes.

>From the release notes:

"The practically exploitable bug that was fixed was an error in the
network error handling. In client mode, any received packet that
causes an exception during processing would terminate the connection
to the server. Regular game clients are usually well protected by a
NAT router that would not let such packets from attackers through.
Game servers are only vulnerable during the brief period while they
are communicating with the master servers, and the effect then is that
the server will not advertise itself.

Another theoretically exploitable bug was that very short UDP packets
would cause a read beyond the input buffer. The same buffer as last
time, embarrasingly, but this time off the other end and with maximum
offset 2."

I have talked to upstream who provided a minimal patch which I intend
to apply. I think it should be fixed for Jessie and Wheezy since the
vulnerability is remotely exploitable.

Regards,

Markus


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

Bug#780177: emacs24: Possible FTBFS due to bug in patch-to-news script

[Adam Porter]

Package: emacs24
Version: 24.4+1
Severity: minor

I am trying to build the Debian package of emacs24-24.4+1-5 on an
Ubuntu Trusty system.  I realize this is unsupported, but I have
encountered a confusing bug.  The build log shows this:


   debian/rules override_dh_auto_install
make[1]: Entering directory `/home/me/Temp/src/emacs/emacs24-24.4+1'
perl -p -e "s|\@PKG_NAME\@|emacs24-bin-common|go;" -e
"s|\@MAJOR_VERSION\@|24|go;" -e "s|\@MINOR_VERSION\@|4|go;" -e
"s|\@FULL_VERSION\@|24.4|go;" -e "s|\@PACKAGE_VERSION\@|24.4+1-5|go;"
-e "s|\@DEBIAN_REV\@||go;" -e "s|\@UPSTREAM_VERSION\@|24.4|go;" -e
"s|\@DEBSRC_VERSION\@|24.4+1|go;" -e "s|\@DEB_FLAVOR\@|emacs24|go;" -e
"s|\@MENU_VERSION\@|24|go;" -e "s|\@INFO_FILES\@|efaq.info|go;" -e
"s|\@INFO_SUBDIR\@|emacs-24|go;" -e "s|\@X_SUPPORT\@||go;" -e
"s|\@BIN_PRIORITY\@|27|go;" -e
"s|\@MOVEMAIL_BIN\@|usr/lib/emacs/24.4/x86_64-linux-gnu/movemail|go;"
< debian/emacsVER-bin-common.lintian-overrides >
debian/emacs24-bin-common.lintian-overrides
perl -p -e "s|\@PKG_NAME\@|emacs24-bin-common|go;" -e
"s|\@MAJOR_VERSION\@|24|go;" -e "s|\@MINOR_VERSION\@|4|go;" -e
"s|\@FULL_VERSION\@|24.4|go;" -e "s|\@PACKAGE_VERSION\@|24.4+1-5|go;"
-e "s|\@DEBIAN_REV\@||go;" -e "s|\@UPSTREAM_VERSION\@|24.4|go;" -e
"s|\@DEBSRC_VERSION\@|24.4+1|go;" -e "s|\@DEB_FLAVOR\@|emacs24|go;" -e
"s|\@MENU_VERSION\@|24|go;" -e "s|\@INFO_FILES\@|efaq.info|go;" -e
"s|\@INFO_SUBDIR\@|emacs-24|go;" -e "s|\@X_SUPPORT\@||go;" -e
"s|\@BIN_PRIORITY\@|27|go;" -e
"s|\@MOVEMAIL_BIN\@|usr/lib/emacs/24.4/x86_64-linux-gnu/movemail|go;"
< debian/emacsVER-bin-common.postinst >
debian/emacs24-bin-common.postinst
perl -p -e "s|\@PKG_NAME\@|emacs24-bin-common|go;" -e
"s|\@MAJOR_VERSION\@|24|go;" -e "s|\@MINOR_VERSION\@|4|go;" -e
"s|\@FULL_VERSION\@|24.4|go;" -e "s|\@PACKAGE_VERSION\@|24.4+1-5|go;"
-e "s|\@DEBIAN_REV\@||go;" -e "s|\@UPSTREAM_VERSION\@|24.4|go;" -e
"s|\@DEBSRC_VERSION\@|24.4+1|go;" -e "s|\@DEB_FLAVOR\@|emacs24|go;" -e
"s|\@MENU_VERSION\@|24|go;" -e "s|\@INFO_FILES\@|efaq.info|go;" -e
"s|\@INFO_SUBDIR\@|emacs-24|go;" -e "s|\@X_SUPPORT\@||go;" -e
"s|\@BIN_PRIORITY\@|27|go;" -e
"s|\@MOVEMAIL_BIN\@|usr/lib/emacs/24.4/x86_64-linux-gnu/movemail|go;"
< debian/emacsVER-bin-common.prerm > debian/emacs24-bin-common.prerm
cd debian && \
  csplit -s -f emacsVER-common.README. \
  emacsVER-common.README '/@@PATCH_LIST_HERE@@/'
cp debian/emacsVER-common.README.00 debian/emacsVER-common.README.tmp
for p in $(QUILT_PATCHES=debian/patches quilt series); do \
  debian/patch-to-news "$p" >> debian/emacsVER-common.README.tmp \
  && echo >> debian/emacsVER-common.README.tmp; \
done
debian/patch-to-news: line 9:
0001-Prefer-usr-share-info-emacs-24-over-usr-share-info.patch: No such
file or directory
debian/patch-to-news: line 9:
0002-Run-debian-startup-and-set-debian-emacs-flavor.patch: No such
file or directory
debian/patch-to-news: line 9:
0003-Remove-files-that-appear-to-be-incompatible-with-the.patch: No
such file or directory
debian/patch-to-news: line 9:
0004-Adjust-documentation-references-for-Debian.patch: No such file or
directory
debian/patch-to-news: line 9:
0005-Modify-the-output-of-version-to-indicate-Debian-modi.patch: No
such file or directory
debian/patch-to-news: line 9:
0006-Look-for-NEWS-in-order-to-find-etc-rather-than-GNU.patch: No such
file or directory
debian/patch-to-news: line 9:
0007-Don-t-try-to-build-src-macuvs.h-via-IVD_Sequences.tx.patch: No
such file or directory
debian/patch-to-news: line 9:
0008-A-race-to-create-info-has-been-eliminated.patch: No such file or
directory
debian/patch-to-news: line 9:
0009-Nil-load-path-elements-shouldn-t-crash-Emacs.patch: No such file
or directory
make[1]: *** [debian/emacs24-common.README.Debian] Error 1


What's happening is, the patch-to-news script is getting just the
filename of each patch, not "debian/patches/filename.patch".

Now, there are entries in both the Ubuntu and Debian changelogs for
emacs24 packages that mention the bug being fixed (in different
versions), and it appears that the debian/rules file was edited to
change the argument to "debian/patches/$$p".  However, my download of
emacs24_24.4+1-5 from Debian does not have the corrected rules script,
so the build fails on my system.

In the process of investigating this, I found on Google a git repo
that fixes the patch-to-news script itself:

http://git.willhughes.name/emacs/commit/37eb31c8134e099a209f497512e7de8772b47105/

I don't know why the build works for Debian but doesn't work here.  Is
there a difference in quilt that causes the relative path to be
printed instead of just the filename?  Anyway, maybe it would be good
to consider patching patch-to-news itself.  It's a shame that the only
reason the build failed on my system is due to this little problem.

Thanks.

-- System Information:
Debian Release: jessie/sid
  APT prefers trusty-updates
  APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500,
'trusty'), (100, 'trusty-backpo

Bug#773443: [PATCH] host.conf.5: keywords and env. var. nospoof, spoofalert, spoof and RESOLV_SPOOF_CHECK were added to glibc 2.0.7 but never implemented

[Michael Kerrisk (man-pages)]

On 03/10/2015 12:27 AM, Stéphane Aulery wrote:
> Move descriptions to historical section and reorder it for clarity

Thanks, Stéphane.

Applied. But please make patch titles shorter (<72 chars) --move text 
to the body of the commit message as needed.

Thanks,

Michael


> Debian Bug #773443 reported by yg...@ygrex.ru
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773443
> Signed-off-by: Stéphane Aulery 
> ---
>  man5/host.conf.5 | 125 
> ---
>  1 file changed, 63 insertions(+), 62 deletions(-)
> 
> diff --git a/man5/host.conf.5 b/man5/host.conf.5
> index 9ff2ed3..08da435 100644
> --- a/man5/host.conf.5
> +++ b/man5/host.conf.5
> @@ -66,52 +66,6 @@ This is
>  by default, as it may cause a substantial performance loss at sites
>  with large hosts files.
>  .TP
> -.I nospoof
> -Valid values are
> -.IR on " and " off .
> -If set to
> -.IR on ,
> -the resolv+ library will attempt to prevent hostname spoofing to
> -enhance the security of
> -.BR rlogin " and " rsh .
> -It works as follows: after performing a host address lookup, resolv+
> -will perform a hostname lookup for that address.
> -If the two hostnames
> -do not match, the query will fail.
> -The default value is
> -.IR off .
> -.TP
> -.I spoofalert
> -Valid values are
> -.IR on " and " off .
> -If this option is set to
> -.I on
> -and the
> -.I nospoof
> -option is also set, resolv+ will log a warning of the error via the
> -syslog facility.
> -The default value is
> -.IR off .
> -.TP
> -.I spoof
> -Valid values are
> -.IR off ", " nowarn " and " warn .
> -If this option is set to
> -.IR off ,
> -spoofed addresses are permitted and no warnings will be emitted
> -via the syslog facility.
> -If this option is set to
> -.IR warn ,
> -resolv+ will attempt to prevent hostname spoofing to
> -enhance the security and log a warning of the error via the syslog
> -facility.
> -If this option is set to
> -.IR nowarn ,
> -the resolv+ library will attempt to prevent hostname spoofing to
> -enhance the security but not emit warnings via the syslog facility.
> -Setting this option to anything else is equal to setting it to
> -.IR nowarn .
> -.TP
>  .I reorder
>  Valid values are
>  .IR on " and " off .
> @@ -133,15 +87,6 @@ override the behavior which is configured in
>  If set, this variable points to a file that should be read instead of
>  .IR /etc/host.conf .
>  .TP
> -.B RESOLV_SPOOF_CHECK
> -Overrides the
> -.IR nospoof ", " spoofalert " and " spoof
> -commands in the same way as the
> -.I spoof
> -command is parsed.
> -Valid values are
> -.IR off ", " nowarn " and " warn .
> -.TP
>  .B RESOLV_MULTI
>  Overrides the
>  .I multi
> @@ -184,6 +129,10 @@ can take arguments like
>  .IR off ", " nowarn " and " warn .
>  Line comments can appear anywhere and not only at the beginning of a line.
>  .SS Historical
> +The
> +.BR nsswitch.conf (5)
> +file is the modern way of controlling the order of host lookups.
> +.PP
>  In glibc 2.4 and earlier, the following keyword is recognized:
>  .TP
>  .I order
> @@ -191,15 +140,67 @@ This keyword specifies how host lookups are to be 
> performed.
>  It should be followed by one or more lookup methods, separated by commas.
>  Valid methods are
>  .IR bind ", " hosts ", and " nis .
> -The
> +.TP
>  .B RESOLV_SERV_ORDER
> -environment variable could be used to override the
> -.I order
> -command.
> +Overrides the order command.
>  .PP
> -The
> -.BR nsswitch.conf (5)
> -file is the modern way of controlling the order of host lookups.
> +Since glibc 2.0.7, the following keywords and environment variable have
> +been recognized but never implemented:
> +.TP
> +.I nospoof
> +Valid values are
> +.IR on " and " off .
> +If set to
> +.IR on ,
> +the resolv+ library will attempt to prevent hostname spoofing to
> +enhance the security of
> +.BR rlogin " and " rsh .
> +It works as follows: after performing a host address lookup, resolv+
> +will perform a hostname lookup for that address.
> +If the two hostnames
> +do not match, the query will fail.
> +The default value is
> +.IR off .
> +.TP
> +.I spoofalert
> +Valid values are
> +.IR on " and " off .
> +If this option is set to
> +.I on
> +and the
> +.I nospoof
> +option is also set, resolv+ will log a warning of the error via the
> +syslog facility.
> +The default value is
> +.IR off .
> +.TP
> +.I spoof
> +Valid values are
> +.IR off ", " nowarn " and " warn .
> +If this option is set to
> +.IR off ,
> +spoofed addresses are permitted and no warnings will be emitted
> +via the syslog facility.
> +If this option is set to
> +.IR warn ,
> +resolv+ will attempt to prevent hostname spoofing to
> +enhance the security and log a warning of the error via the syslog
> +facility.
> +If this option is set to
> +.IR nowarn ,
> +the resolv+ library will attempt to prevent hostname spoofing to
> +enhance the security but not emit warnings via the syslog facility.
> +Setting this option to anything else is equal to setting it to
> +.IR nowar

Bug#780176: [xterm] XTerm and UXTerm appear in Xfce 4.10 main menu twice

[bullgard]

Package: xterm
Version: 312-1
Severity: wishlist

--- Please enter the report below this line. ---
XTerm and UXTerm appear in Xfce 4.10 main menu twice. Please decide if 
they should appear in the System or the Accessories menu item and remove 
two menu item entries accordingly. The present solution leads to 
ambiguity and misunderstandings among users.

--- System information. ---
Architecture: i386
Kernel: Linux 3.16.0-4-686-pae

Debian Release: 8.0
500 testing security.debian.org
500 testing ftp2.de.debian.org

--- Package information. ---
Depends (Version) | Installed
===-+-=
xbitmaps | 1.1.1-2
libc6 (>= 2.11) | 2.19-15
libfontconfig1 (>= 2.9.0) | 2.11.0-6.3
libice6 (>= 1:1.0.0) | 2:1.0.9-1+b1
libtinfo5 | 5.9+20140913-1+b1
libutempter0 (>= 1.1.5) | 1.1.5-4
libx11-6 | 2:1.6.2-3
libxaw7 | 2:1.0.12-2+b1
libxft2 (>> 2.1.1) | 2.3.2-1
libxmu6 | 2:1.1.2-1
libxt6 | 1:1.1.4-1+b1


Recommends (Version) | Installed
=-+-===
x11-utils | 7.7+2


Suggests (Version) | Installed
==-+-===
xfonts-cyrillic |


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

Bug#780175: linux-image-3.16.0-4-686-pae: flags mismatch irq 6 00000080 (sata_sil) vs 00000000 (floppy)

[Dan Brown]

Package: src:linux
Version: 3.16.7-ckt7-1
Severity: important

Dear Maintainer,


I have an old Dell (Dimension XPS B766r) which was previously running Debian 6 
on it serving as a fileserver with 8 sata HDDs, 2 IDE HDDs, and an SD to IDE 
adapter running the OS. It has two PCI RAID cards running in jBOD to facilitate 
the numerous drives.  The MegaRAID PCI card is detected and it's drives all 
show up. The Silicon Image SiI 3114 RAID card is detected but has a conflict 
with the IRQ for the floppy drive (which is disabled in BIOS).  The Silicon 
Image card detects all drives, and the kernel detects the card and loads the 
sata_sil module for it, but once the OS is booted none of the drives appear.

As a workaround, in rc.local I have the following for the time being:

# rc.local
rmmod sata_sil
modprobe -v sata_sil 

mount /opt/mnt/driveA
mount /opt/mnt/driveB
mount /opt/mnt/driveC
mount /opt/mnt/driveD

I have fstab entries for these mounts setup with the noauto option so the 
system doesn't fail on boot.
lsmod shows the sata_sil module in the system modules after boot but it seems 
to not recognize the card and/or the drives attached to it.


-- Package-specific info:
** Version:
Linux version 3.16.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-686-pae 
root=UUID=35edd3a8-224b-4aba-a58e-85c4e341d54d ro quiet 
init=/lib/systemd/systemd

** Not tainted

** Kernel log:
[5.348426] EXT4-fs (sdc1): mounted filesystem with ordered data mode. Opts: 
(null)
[6.569549] systemd[1]: Cannot add dependency job for unit 
display-manager.service, ignoring: Unit display-manager.service failed to load: 
No such file or directory.
[6.914491] fuse init (API version 7.23)
[7.419642] systemd-udevd[151]: starting version 215
[7.992617] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[7.992642] ACPI: Power Button [PWRF]
[8.239366] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[8.246524] intel_rng: Firmware space is locked read-only. If you can't or
intel_rng: don't want to disable this in firmware setup, and if
intel_rng: you are certain that your system has a functional
intel_rng: RNG, try using the 'no_fwh_detect' option.
[8.334653] MPU-401 device not found or device busy
[8.670179] [drm] Initialized drm 1.1.0 20060810
[8.853367] wmi: Mapper loaded
[9.087456] input: PC Speaker as /devices/platform/pcspkr/input/input4
[9.315527] dcdbas dcdbas: Dell Systems Management Base Driver (version 
5.6.0-3.2)
[9.325094] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
[9.325111] PCI: setting IRQ 11 as level-triggered
[9.332493] nouveau  [  DEVICE][:01:00.0] BOOT0  : 0x20154000
[9.332512] nouveau  [  DEVICE][:01:00.0] Chipset: NV05 (NV05)
[9.332520] nouveau  [  DEVICE][:01:00.0] Family : NV04
[9.332798] nouveau  [   VBIOS][:01:00.0] checking PRAMIN for image...
[9.353128] nouveau  [   VBIOS][:01:00.0] ... appears to be valid
[9.353141] nouveau  [   VBIOS][:01:00.0] using image from PRAMIN
[9.353152] nouveau  [   VBIOS][:01:00.0] BMP version 2.1
[9.353538] nouveau  [   VBIOS][:01:00.0] version 02.05.13.03.00
[9.414468] nouveau W[   VBIOS][:01:00.0] DCB table not found
[9.414871] nouveau W[   VBIOS][:01:00.0] DCB table not found
[9.415015] nouveau W[   VBIOS][:01:00.0] DCB table not found
[9.415026] nouveau W[   VBIOS][:01:00.0] DCB table not found
[9.415114] nouveau W[  PTIMER][:01:00.0] unknown input clock freq
[9.415134] nouveau  [ PFB][:01:00.0] RAM type: SDRAM
[9.415143] nouveau  [ PFB][:01:00.0] RAM size: 32 MiB
[9.415151] nouveau  [ PFB][:01:00.0]ZCOMP: 0 tags
[9.442538] nouveau  [ CLK][:01:00.0] --:   
[9.442586] nouveau W[   VBIOS][:01:00.0] DCB table not found
[9.442645] agpgart-intel :00:00.0: AGP 2.0 bridge
[9.442674] agpgart-intel :00:00.0: putting AGP V2 device into 4x mode
[9.442703] nouveau :01:00.0: putting AGP V2 device into 4x mode
[9.449890] [TTM] Zone  kernel: Available graphics memory: 255938 kiB
[9.449905] [TTM] Initializing pool allocator
[9.449941] [TTM] Initializing DMA pool allocator
[9.450421] nouveau  [ DRM] VRAM: 31 MiB
[9.450437] nouveau  [ DRM] GART: 64 MiB
[9.450449] nouveau  [ DRM] BMP version 2.1
[9.450459] nouveau W[ DRM] No DCB data found in VBIOS
[9.475999] nouveau  [ DRM] Saving VGA fonts
[9.532472] nouveau W[ DRM] No DCB data found in VBIOS
[9.533239] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[9.533248] [drm] Driver supports precise vblank timestamp query.
[9.598779] nouveau  [ DRM] MM: using M2MF for buffer copies
[9.668823] nouveau  [ DRM] allocated 1280x1024 fb: 0x4000, bo ddb58000
[9.

Bug#780133: [debhelper-devel] Bug#780133: DH_VERBOSE under dh command

[Niels Thykier]

On 2015-03-10 00:23, Tianon Gravi wrote:
> [...]
> 
> Ok, here's my initial stab at improving this section to make the point
> more clear:
> 
> | diff --git a/debhelper.pod b/debhelper.pod
> | index 9415d78..f5d27f6 100644
> | --- a/debhelper.pod
> | +++ b/debhelper.pod
> | @@ -660,6 +660,12 @@ F, F, F, and F 
> scripts, etc.
> |  
> |  =head1 ENVIRONMENT
> |  
> | +The following environment variables can influence the behavior of 
> debhelper.
> | +It is important to note that these must be actual environment variables in
> | +order to function properly (not simply F variables). To specify
> | +them properly in F, be sure to prefix their assignment with
> | +"B". For example, "B".
> | +
> |  =over 4
> |  
> |  =item B
> 
> Would appreciate some prose review before I commit, though. :)
> 
> ♥,
> - Tianon
>   4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
> 
> [...]

Looks good to me.  The only thing I can think of is that it probably
also valid to do:

DH_VERBOSE := 1
export DH_VERBOSE

So maybe it should simply say that people should remember to "export"
them and not necessary require it to be exported during the assignment.

~Niels


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

Bug#779898: [ITR] templates://diaspora-installer/{templates}

[Christian PERRIER]

Dear Debian maintainer,

The Debian internationalisation team and the Debian English
localisation team will soon begin the review of the debconf
templates used in diaspora-installer.

This review takes place for all packages that use debconf to interact with
users and its aims are:
- to improve the use of English in all debconf templates;
- to make the wording of debconf templates more consistent;
- to encourage more translations of templates.

Even if your first language is English, this process is likely to help
track down typos or errors, and improve consistency between the
debconf templates of your package and that of other packages in the
distribution.

The process involves both debian-l10n-english contributors and
Debian translators.

The details of the process are given in
http://wiki.debian.org/I18n/SmithDebconfReviewProcess.

I will act as the coordinator of this activity for diaspora-installer.

The first step of the process is to review the debconf source
template file(s) of diaspora-installer. This review will start on Friday, March 
13, 2015, or
as soon as you acknowledge this mail with an agreement for us to
carry out this process.

All parts of the process will be carried out in close collaboration
with you, and, unless you explicitly ask for it, no upload nor NMU
will happen for diaspora-installer.

If you approve this process, please let us know by replying to this
mail. If some work in progress on your side would conflict with such a
rewrite (such as adding or removing debconf templates), please say so,
and we will defer the review to later in the development cycle.

Thank you for your attention.

-- 




signature.asc
Description: Digital signature

Bug#780174: memtest86: new upstream version (V6.0.0)

[Paul Wise]

Package: memtest86
Severity: wishlist

Please update memtest86 to the new upstream version (V6.0.0), which
checks for the DRAM rowhammer weakness. You may want to also ask
upstream to adjust their download page to fix your watch file.

http://www.memtest86.com/download.htm
http://www.memtest86.com/support/ver_history.htm
http://googleprojectzero.blogspot.com/2015/03/exploiting-dram-rowhammer-bug-to-gain.html

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#780173: valgrind: ignores compressed debug sections (default for -dbg built by debhelper in compat v9)

[Niels Thykier]

Package: valgrind
Version: 1:3.10.0-4
Severity: normal



Hi,

We have received a bug against debhelper because valgrind allegedly
does not support compressed debug sections.  In debhelper compat 9, it
is currently the default to compress these sections.

Please consider have upstream support compressed debug sections.

I am not sure where the upstream bug tracker is, though I did find
https://bugs.kde.org/show_bug.cgi?id=303877, which seems to be
related.

Thanks,
~Niels


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

Bug#773443: host.conf.5: spoof deprecated ?

[Michael Kerrisk (man-pages)]

Hello Stéphane,

On 10 March 2015 at 00:26, Stéphane Aulery  wrote:
> Hello Michael,
>
> Le lundi 09 mars 2015 à 10:03:09, Michael Kerrisk (man-pages) a écrit :
>> On 03/09/2015 08:59 AM, Stéphane Aulery wrote:
>> > Le lundi 09 mars 2015 à 08:22:01, Michael Kerrisk (man-pages) a écrit :
>> >>
>> >> On 03/08/2015 02:05 PM, Stéphane Aulery wrote:
>> >>>
>> >>> A Debian user reported that [1]:
>> >>>
>>  spoof* keywords (nospoof, spoofalert, spoof) are here from 1996,
>>  they are still valid keywords but do not have any effect apparently,
>>  no libraries or tools use them
>> 
>>  it is misleading to see references to resolv+ and rlogin, the keywords
>>  are just ignored these days; the only meaning they have is that they
>>  are
>>  allowed by host.conf syntax
>> >>>
>> >>> The glibc source code seems to confirm that the keywords nospoof,
>> >>> spoofalert and spoof are accepted but without effects. I could find
>> >>> nothing in the changelog. Could you please confirm that they are
>> >>> obsolete? I could correct the man page accordingly.
>> >>
>> >> I had a quick grep in the glibc source code.
>> >>
>> >> It appears that you (and the reporter) are correct. (Even back in
>> >> glibc 2.1, things look the same).
>> >>
>> >> A patch would be appreciated!
>
> I dug a little further comparing versions 2.0.6 [1], 2.0.7 [2]
> and trunk [3] of glibc and I come to a different conclusion.
>
> The keywords nospoof, spoofalert, spoof and RESOLV_SPOOF_CHECK were
> added to glibc 2.0.7 but never implemented and documented in the
> changelog.

Perfect -- that's exactly the sort of detail it's great to have in man-pages!

Cheers,

Michael


> [1] http://ftp.gnu.org/gnu/glibc/glibc-2.0.6.tar.gz
> [2] 
> http://archive.debian.org/debian/dists/hamm/main/source/libs/glibc_2.0.7t.orig.tar.gz
> [3] 
> https://sourceware.org/git/?p=glibc.git&a=search&h=HEAD&st=grep&s=spoof&sr=1
>
> Regards,
>
> --
> Stéphane Aulery



-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/


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

Bug#779559: dpkg-source: Add test dependencies to .dsc

[Martin Pitt]

Hey Guillem,

Guillem Jover [2015-03-10  5:39 +0100]:
> So given all the above, I'd say:
> 
>   Testsuite-Triggers: foo, bar, baz
> 
> from the union of all testsuites test depends, minus @ and @builddeps@,
> without versions, and with alternatives split (i.e. a simple comma
> separated package list). If the field is present then it overrides the
> automatically extracted value.
> 
> Does this seem fine?

+1 for me, that's simple and clean.

Thanks!

Martin
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


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

Bug#778729: Try 2: Bug#778729: RFS: git-tools/1.0.0-1 [ITP]

[Stephen Kitt]

On Tue, 10 Mar 2015 00:38:29 +0100, Adam Borowski  wrote:
> Should be ready now.  However, mentors.d.n seems to not allow uploading the
> same binary package with a different source more than once per day (there's
> some cronjob AFAIK), so I had to use my own repository:
> 
> http://angband.pl/debian/pool/main/g/git-mestrelion-tools/git-mestrelion-tools_1.0.0-1.dsc

Thanks, I've uploaded that to the archive. For your next upload you might
want to add a watch file ;-).

Regards,

Stephen


pgp7s3VBDsw_D.pgp
Description: OpenPGP digital signature

Bug#728347: On packaging Mediawiki 1.23 for Debian jessie

[Yongmin Hong]

MediaWiki 1.19's LTS support will end at May 2015, according to the mw.org [1].

[1]: https://www.mediawiki.org/wiki/MediaWiki_1.19
--
Yongmin Hong [Revi]
[[mw:User:-revi]]
GPG fingerprint: 72595467101410C3DBF2899FCFAB84B9E7BBAB4A
Sent from Android


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

Bug#760445: [mate-control-center] mate-display-properties segment fault with VirtualBox VNC Desktop

[张敬强]

> 
> I assume that the above bug is fixed since gtk+2.0 (v2.24.25-3)  
> appeared in Debian jessie.
> 
> Can you please check if the bug is still there or if it is gone now?
> 
The bug has gone now for sid with VirtualBox 4.3.24.

Need I to check it with jessie ?

Thanks

Bug#779559: dpkg-source: Add test dependencies to .dsc

[Guillem Jover]

Hi!

On Wed, 2015-03-04 at 11:00:08 +0100, Martin Pitt wrote:
> Guillem Jover [2015-03-04 10:42 +0100]:
> > Ah, indeed, making it clear that this is strictly not for "dependency"
> > purposes, seems better. It just crossed my mind that it might make sense
> > to strip the version information from those dependencies, and only list
> > package names, but given that those dependencies can have alternatives
> > «foo (>= 1.0) | bar», they should probably be preserved?
> 
> Stripping versions sounds good to me. For alternatives I'd either
> split them out as separate triggers (if we want to trigger tests on
> alternative changes too), or just ignore them completely (if we don't
> want the extra test runs).

Ok, if we just want a list of packages that should trigger test reruns
then yes, splitting alternatives and stripping versions would be best,
because having thought about it, I think it does make sense to trigger
on changes for the alternatives too (and ideally the test runner would
then use, if satisfiable, the alternatives that have changed!).

> > > It's even conceivable that package maintainers want to maintain this
> > > field manually, like "run the tests for the nvidia graphics driver
> > > whenever the kernel changes". But auto-generating it in the described
> > > manner would still be an useful default IMHO.
> > 
> > Right. So then we either need to replace it with the information
> > from the testsuite, or extend it in a similar way as how the Testsuite
> > field is currently being handled. I'd tend to think the latter.
> 
> I'd say, if debian/control already has that field, dpkg-source
> shouldn't touch it at all. That way you can avoid unnecessary reverse
> dependency runs if the maintainer decides so?

Ok, this gives more control, as it allows to reset the field. If the
maintainer wants to extend it, those can always be added to some of
the specific test dependencies instead.

On Thu, 2015-03-05 at 06:34:31 -0700, Adam Conrad wrote:
> On Wed, Mar 04, 2015 at 10:42:15AM +0100, Guillem Jover wrote:
> > When I said coalesce any other dependencies I was thinking about the
> > following situation. Say we have a package with an "autopkgtest"
> > testsuite with dependencies «foo (>= 1.0), bar», and another "newchecks"
> > testsuite with dependencies «quux, frob, bar». And then the
> > Testsuite-Triggers ends up being «foo (>= 1.0), bar, quux, frob».
> 
> I'm not convinced this is actuall a problem.  What we're trying to
> approximate here with auto-filling Testsuite-Triggers (rather than
> someone specifying it manually in debian/control) is a set of packages
> that we feel it would be reasonable to force a retest for.
> 
> Sure, maybe it wastes a few cycles if TestA doesn't actually depend
> on or use DepB, but we run it when DepB changes anyway, but I'm not
> sure optimising for that is worth having ${test}-Triggers instead of
> just one concatenated field.

Ok, that makes sense. Also considering it an approximation doesn't
disallow the test runner to skip the package by checking the more
fine-grained dependencies from the test metadata, even for different
testsuite implementations.

On Wed, 2015-03-04 at 11:00:08 +0100, Martin Pitt wrote:
> On Wed, Mar 04, 2015 at 10:42:15AM +0100, Guillem Jover wrote:
> > If I'm only interested in running either autopkgtest or newchecks for
> > the whole archive, I might get triggered for packages that I'm not
> > interested in, which would be wasteful. And to get accurate
> > information we are back to having to unpack the source packages. This
> > might get worse the more testsuites we get.
> 
> OK, agreed. So putting that together, how about:
> 
>   XS-Autopkgtest-Triggers: foo, bar, baz
> 
> which gets the union of all test depends, minus @, without versions,
> and with alternatives either expanded or ignored?

So given all the above, I'd say:

  Testsuite-Triggers: foo, bar, baz

from the union of all testsuites test depends, minus @ and @builddeps@,
without versions, and with alternatives split (i.e. a simple comma
separated package list). If the field is present then it overrides the
automatically extracted value.

Does this seem fine?

Thanks,
Guillem


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

Bug#776746: gnome-session: GNOME crashes during a remote desktop access

[GGaotx]

> * gnome-session should put different text on the "oh no!" message
>   if the problem is really "your X server is not sufficiently capable to
>   run GNOME"

> * xrdp should allow session-selection, so remote users can select
>   a non-compositing environment like LXDE or XFCE even if GNOME is
>   the default

> * xrdp, or whatever Xserver it uses behind the scenes (Xvnc?), should
>   support the Composite extension

If this is considered as xrdp's bug, the 3rd option should be best way to 
fully fix this issue. But if it's considered as GNOME's bug, probably it 
should be patched to make GNOME 3 support non-compositing 
environment and this may better then modifying xrdp because this is 
a GNOME 3 ONLY issue and not xrdp's fault. Xrdp works well with other
desktop environments.

Gaotx 

Bug#780172: installation-reports: Installed Debian Jessie sucessfully on a Compaq Presario F700 laptop

[Robert Stryk]

Package: installation-reports
Severity: wishlist

Dear Maintainer,

   * What led up to the situation? Some update to Jessie made the file system
(ext3) unmountable.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Trying Rescue mode made a system with no user accounts and
no root account.
   * What was the outcome of this action? Normal installation worked nicely.
   * What outcome did you expect instead?



-- Package-specific info:

Boot method: CD
Image version: debian-jessie-DI-rc1-amd64-netinst
Date: 

Machine: Compaq Presario F700
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

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

Comments/Problems:




-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20150107"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux Judy-PC 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) 
x86_64 GNU/Linux
lspci -knn: 00:00.0 RAM memory [0500]: NVIDIA Corporation MCP67 Memory 
Controller [10de:0547] (rev a2)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: 00:01.0 ISA bridge [0601]: NVIDIA Corporation MCP67 ISA Bridge 
[10de:0548] (rev a2)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: 00:01.1 SMBus [0c05]: NVIDIA Corporation MCP67 SMBus [10de:0542] 
(rev a2)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: 00:01.2 RAM memory [0500]: NVIDIA Corporation MCP67 Memory 
Controller [10de:0541] (rev a2)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: 00:01.3 Co-processor [0b40]: NVIDIA Corporation MCP67 Co-processor 
[10de:0543] (rev a2)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: 00:02.0 USB controller [0c03]: NVIDIA Corporation MCP67 OHCI USB 
1.1 Controller [10de:055e] (rev a2)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: Kernel driver in use: ohci-pci
lspci -knn: 00:02.1 USB controller [0c03]: NVIDIA Corporation MCP67 EHCI USB 
2.0 Controller [10de:055f] (rev a2)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:04.0 USB controller [0c03]: NVIDIA Corporation MCP67 OHCI USB 
1.1 Controller [10de:055e] (rev a2)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: Kernel driver in use: ohci-pci
lspci -knn: 00:04.1 USB controller [0c03]: NVIDIA Corporation MCP67 EHCI USB 
2.0 Controller [10de:055f] (rev a2)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: Kernel driver in use: ehci-pci
lspci -knn: 00:06.0 IDE interface [0101]: NVIDIA Corporation MCP67 IDE 
Controller [10de:0560] (rev a1)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: Kernel driver in use: pata_amd
lspci -knn: 00:07.0 Audio device [0403]: NVIDIA Corporation MCP67 High 
Definition Audio [10de:055c] (rev a1)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:08.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Bridge 
[10de:0561] (rev a2)
lspci -knn: 00:09.0 IDE interface [0101]: NVIDIA Corporation MCP67 AHCI 
Controller [10de:0550] (rev a2)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: Kernel driver in use: ahci
lspci -knn: 00:0a.0 Ethernet controller [0200]: NVIDIA Corporation MCP67 
Ethernet [10de:054c] (rev a2)
lspci -knn: Subsystem: Hewlett-Packard Company Device [103c:30ea]
lspci -knn: Kernel driver in use: forcedeth
lspci -knn: 00:0c.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express 
Bridge [10de:0563] (rev a2)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0d.0 PCI bridge [0604]: NVIDIA Corporation MCP67 PCI Express 
Bridge [10de:0563] (rev a2)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:12.0 VGA compatible controller [0300]: NVIDIA Corporation C67 
[GeForce 7000M / nFo

Bug#780159: qemu-kvm: exit status is 0 if process is killed

[Benjamin Moody]

On 3/9/15, Michael Tokarev  wrote:
> Indeed it does.  What exit code do you suggest to use in this case?

Really, anything nonzero would be fine; it's not as if qemu exit codes
have any particular significance currently.  I think 128+(signal
number) is somewhat standard.

> Note this has been this way since the Day One, qemu _always_ did that,
> for many years.  So lowering the severity.

Yeah, I know this bug has been around for a long time.  It's just that
only today did it annoy me sufficiently to be worth the effort of
filing a bug report.

Benjamin


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

Bug#779784: git-extras: fresh-branch deletes everything without asking

[Andrew Starr-Bochicchio]

On Mon, 9 Mar 2015 22:20:39 -0400 Andrew Starr-Bochicchio
 wrote:
> I submitted a pull request for this upstream:
>
> https://github.com/tj/git-extras/pull/322

And it was very quickly merged. Proposed NMU debdiff attached.

Thanks,

-- Andrew Starr-Bochicchio

   Ubuntu Developer 
   Debian Developer 
   PGP/GPG Key ID: D53FDCB1


bts779784.debdiff
Description: Binary data

Bug#780089: wireshark: "On gnome wireshark has not title bar. Does not correctly get focus on click events"

[Paul Wise]

On Tue, Mar 10, 2015 at 3:51 AM, Bálint Réczey wrote:

> I'm unable to reproduce the issue with a fully updated Jessie/Sid
> system. I suspect this issue is not related to wireshark, but to
> GNOME/window decorations.
> I'm copying Debian GNOME Team, maybe they have seen similar problems
> with other programs.
>
> Please try to debug this further and if you find logs please attach
> them because Wireshark starts fine on my system with titlebar and it
> works normally.

I'm able to reproduce this, here are the steps:

Disconnect external monitor.

Start and close wireshark.

Reconnect external monitor.

Start wireshark, it will appear on the primary display even if you
have the mouse in the secondary display. Most other apps start on the
display where the mouse is.

Move the wireshark window to the secondary display and maximise it.

Close wireshark.

Start wireshark, it will appear on the secondary display without any titlebar.

There are no logs about this as far as I can tell.

This doesn't happen with other GTK+3 apps like liferea.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#780171: nautilus-sendto: FTBFS on x32: -Werror on printf("%li", time_t)

[Adam Borowski]

Package: nautilus-sendto
Version: 3.8.2-1
Severity: wishlist
Tags: patch
User: debian-...@lists.debian.org
Usertags: ftbfs-x32 port-x32

Hi!
I'm afraid your package fails to build on x32.  This is because it assumes
time_t is the same type as long, which is not the case on x32, and, per
Linus' decree, on all new 32-bit architectures.

Fix attached.


-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (600, 'unstable'), (500, 'unreleased'), (50, 'experimental')
Architecture: x32 (x86_64)

Kernel: Linux 3.19.0-x32 (SMP w/6 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)
diff -urd nautilus-sendto-3.8.2.orig/src/nautilus-sendto.c nautilus-sendto-3.8.2/src/nautilus-sendto.c
--- nautilus-sendto-3.8.2.orig/src/nautilus-sendto.c	2014-05-12 13:55:07.0 +0200
+++ nautilus-sendto-3.8.2/src/nautilus-sendto.c	2015-03-10 03:50:15.977114441 +0100
@@ -266,7 +266,7 @@
 	g_mkdir (tmp_dir, 0700);
 	tmp_work_dir = g_strdup_printf ("%s/nautilus-sendto-%s/%li",
 	g_get_tmp_dir (), g_get_user_name (),
-	time (NULL));
+	(long) time (NULL));
 	g_mkdir (tmp_work_dir, 0700);
 	g_free (tmp_dir);
 

Bug#779784: git-extras: fresh-branch deletes everything without asking

[Andrew Starr-Bochicchio]

tag patch
thanks

Hi,

I submitted a pull request for this upstream:

https://github.com/tj/git-extras/pull/322

Thanks,

-- Andrew Starr-Bochicchio

   Ubuntu Developer 
   Debian Developer 
   PGP/GPG Key ID: D53FDCB1


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

Bug#685575: Build dep

[Antoine Beaupré]

On 2015-02-06 09:39:15, Geoff wrote:
> Hi,
>
> I've been playing around with opentracker packaging on Linux only.
>
> I made some improvements to Roman's packaging work.

Where?

> I believe the Makefile has to be patched to support DESTDIR convention.

Understood.

> The package also need to build depends on the following packages:
>
>  * libowfat-dev
>  * zlib1g-dev
>  * freebsd-glue: needed to find srandomdev on linux build
>
> What is the current status on opentracker packaging?

It's pretty much stalled, as you can see from the bug tracker.

> I'm willing to help if needed (I'm not a DD though).

Then please push a git repo with this somewhere! :)

a.

-- 
The flesh you so fancifully fry
Is not succulent, tasty or kind
It's death for no reason
And death for no reason is murder
- Morrissey


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

Bug#780170: Please, update compatibility.js symlink

[David Prévot]

Package: pdf2htmlex
Version: 0.12+ds-1
Severity: wishlist

Hi Johannes,

I’d like to get rid of the compatibility symlinks introduced in pdf.js
1.0.21+dfsg-1, and thus encourage you to change the
/usr/share/pdf2htmlEX/compatibility.js symlink so it points to
/usr/share/javascript/pdf/web/compatibility.js instead of
/usr/share/javascript/pdf/compatibility.js as it currently does.

You may use a simple debian/links file containing the following line and
drop the current override_dh_auto_install from debian/rules:

usr/share/javascript/pdf/web/compatibility.js   
usr/share/pdf2htmlEX/compatibility.js

Thanks in advance

Regards

David


signature.asc
Description: Digital signature

Bug#778483: closed by Yves-Alexis Perez (Re: [Pkg-xfce-devel] Bug#778483: xfce4: Screen tearing in XFCE)

[john k]

I can confirm that in three different machines (two laptop and one 
desktop) with different graphic cards (nVidia and Intel), this problem 
still exists.


On 08/03/2015 10:15 μμ, Debian Bug Tracking System wrote:

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

#778483: xfce4: Screen tearing in XFCE

It has been closed by Yves-Alexis Perez .

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





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

Bug#778085: qt4-x11: ftbfs with GCC-5

[Matthias Klose]

On 03/09/2015 02:04 PM, Lisandro Damián Nicanor Pérez Meyer wrote:
> Upstream's patch is available at https://codereview.qt-project.org/#/c/106514/
> 
> It's still failing to integrate due to tests failing, so we still need
> to fix stuff before this is fixed.

yes, that's what I took:
http://launchpadlibrarian.net/199520528/qt4-x11_4%3A4.8.6%2Bgit64-g5dc8b2b%2Bdfsg-3~ubuntu5_4%3A4.8.6%2Bgit64-g5dc8b2b%2Bdfsg-3~ubuntu6.diff.gz

could you elaborate which tests are failing?


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

Bug#749355: parallel: /usr/bin/parallel conflicts with moreutils' parallel

[Antoine Beaupré]

On 2015-02-15 12:46:15, Filippo Giunchedi wrote:
> On Sat, Sep 27, 2014 at 07:45:14PM -0400, Antoine Beaupré wrote:
>> So I doubt we can coninve Joey to fix this problem the way we are
>> proposing now, but it's possible.
>> 
>> If someone wants to go forward here, there would need to be a set of
>> patches that would create conflicting binary packages for both that will
>> divert /usr/bin/parallel. A patch on ikiwiki-hosting to depend on
>> moreutils-parallel would also then be necessary.
>
> Is dpkg-divert a strict requirement? Would alternatives suffices (e.g. like
> netcat does)?

No, because the commandline interface is different and would break
packages.

>> Then we send this to the moreutils and gnu parallel maintainers to see
>> if they would accept the fix, and we can simply NMU it.
>> 
>> But the main problem, to restate what Joey has said here, is time: it
>> takes time to do that work and unless someone steps up to help the
>> maintainers patiently to clear things up, things will stay as they
>> currently are.
>
> true, I am willing to give it a shot but we're probably far too late in the
> release cycle to get this into jessie (won't be wasted work anyway tho!)

Indeed.

A>

-- 
You Are What You Is
- Frank Zappa


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

Bug#780141: libdbus-glib-1-2: Mark as deprecated

[Simon McVittie]

Control: tags 780141 + confirmed

On 09/03/15 17:15, Samuel Bronson wrote:
> it would seem to make sense to move dbus-glib to the
> oldlibs section

The package maintainer can't actually do that; we'd have to ask the
archive administrators ("ftpmasters") to change it. I'll probably do
that after Debian 8 is released (it's currently in freeze, so I can't
make non-critical changes in testing/unstable right now).

> and mention that it's been deprecated in favor of the
> functionality added to glib in 2.26 in the description.

I already did this in experimental, in fact. Again, this won't reach
testing/unstable until after Debian 8 is out.

> (Yes, I know it wasn't marked as deprecated yet in 0.100, but it seems
> to have been effectively deprecated at least as far back as 2011-04-04
> .)

As both the Debian maintainer and the upstream unmaintainer (as in "it
is unmaintained, and I am the unmaintainer") I am well aware of its
status, and glad to see its users are getting the message :-)

S


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

Bug#780169: jessie-pu: package youtube-dl/2014.08.05-1jessie0.1

[Stefano Rivera]

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

youtube-dl 2014.08.05-1 requires SSLv3 in https requests, and doesn't use
protocol negotiation. See #780059. This, besides being bad, and not very
future-proof has caused complete incompatibility with Python 2.7.9,
which dropped the PROTOCOL_SSLv3 attribute from the ssl module.

This bug has been fixed, by the upstream, in unstable. But at this point
in the freeze, I doubt you'd consider letting the latest upstream
version migrate to testing.

So, please consider this t-p-u upload:

diff -Nru youtube-dl-2014.08.05/debian/changelog 
youtube-dl-2014.08.05/debian/changelog
--- youtube-dl-2014.08.05/debian/changelog  2014-08-06 11:43:31.0 
-0700
+++ youtube-dl-2014.08.05/debian/changelog  2015-03-09 17:15:30.0 
-0700
@@ -1,3 +1,11 @@
+youtube-dl (2014.08.05-1jessie0.1) testing; urgency=medium
+
+  * Non-maintainer upload.
+  * Use SSL protocol negotiation, rather than requiring SSLv3 (which is no
+longer supported in python 2.7.9). Closes: #780059.
+
+ -- Stefano Rivera   Mon, 09 Mar 2015 17:14:45 -0700
+
 youtube-dl (2014.08.05-1) unstable; urgency=medium
 
   * Imported Upstream version 2014.08.05.
diff -Nru youtube-dl-2014.08.05/debian/patches/no-sslv3 
youtube-dl-2014.08.05/debian/patches/no-sslv3
--- youtube-dl-2014.08.05/debian/patches/no-sslv3   1969-12-31 
16:00:00.0 -0800
+++ youtube-dl-2014.08.05/debian/patches/no-sslv3   2015-03-09 
17:09:54.0 -0700
@@ -0,0 +1,34 @@
+Description: Support Python 2.7.9, which removed PROTOCOL_SSLv3
+ In fact, don't try to force an SSL version at all. Debian OpenSSL doesn't
+ support insecure versions.
+ Upstream use Python's default SSL handshake since
+ 
https://github.com/rg3/youtube-dl/commit/0db261ba567cb5370455d67c4398e11e5e2119f8
+ And switches to TLSv1 in legacy paths in
+ 
https://github.com/rg3/youtube-dl/commit/d79323136fabc2cd72afc7c124e17797e32df514
+Author: Stefano Rivera 
+Bug-Debian: https://bugs.debian.org/780059
+Forwarded: not-needed
+Last-Update: 2015-03-08
+
+--- a/youtube_dl/utils.py
 b/youtube_dl/utils.py
+@@ -588,17 +588,14 @@
+ if getattr(self, '_tunnel_host', False):
+ self.sock = sock
+ self._tunnel()
+-try:
+-self.sock = ssl.wrap_socket(sock, self.key_file, 
self.cert_file, ssl_version=ssl.PROTOCOL_SSLv3)
+-except ssl.SSLError:
+-self.sock = ssl.wrap_socket(sock, self.key_file, 
self.cert_file, ssl_version=ssl.PROTOCOL_SSLv23)
++self.sock = ssl.wrap_socket(sock, self.key_file, 
self.cert_file, ssl_version=ssl.PROTOCOL_SSLv23)
+ 
+ class HTTPSHandlerV3(compat_urllib_request.HTTPSHandler):
+ def https_open(self, req):
+ return self.do_open(HTTPSConnectionV3, req)
+ return HTTPSHandlerV3(**kwargs)
+ else:
+-context = ssl.SSLContext(ssl.PROTOCOL_SSLv3)
++context = ssl.SSLContext(ssl.PROTOCOL_SSLv23)
+ context.verify_mode = (ssl.CERT_NONE
+if opts_no_check_certificate
+else ssl.CERT_REQUIRED)
diff -Nru youtube-dl-2014.08.05/debian/patches/series 
youtube-dl-2014.08.05/debian/patches/series
--- youtube-dl-2014.08.05/debian/patches/series 1969-12-31 16:00:00.0 
-0800
+++ youtube-dl-2014.08.05/debian/patches/series 2015-03-08 13:43:36.0 
-0700
@@ -0,0 +1 @@
+no-sslv3


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

Bug#767960: gitweb: no longer works: Undefined subroutine CGI::startform

[Carl Worth]

On Wed, 5 Nov 2014 00:10:28 +0100, gregor herrmann wrote:
> On Tue, 04 Nov 2014 14:29:18 -0800, Jonathan Nieder wrote:
> 
> > > Just shout as soon as we should upload.
> > 1:2.1.3-1 which is now in sid has the fix, so it should be safe to
> > upload.
> 
> Great, thanks.
> 
> I've uploaded libcgi-pm-perl 4.09-2 right now.

I'm still having trouble with this.

I currently have the following installed:

gitweb 1:2.1.4-2.1
libcgi-pm-perl 4.03-1

and gitweb is working fine.

But if I run "apt-get upgrade" on sid, it installs libcgi-pm-perl 4.09-2
and gitweb no longer works, (it hits the "Undefined subroutine
CGI::startform" error described above).

I don't know what the expected fix in git/gitweb 1:2.1.3-1 was, but it
seems that given the current state of gitweb that the current Breaks in
libcgi-pm-perl is not adequate:

Breaks: git (<< 1:2.1.3)

-Carl


pgpAZX3PHyy3U.pgp
Description: PGP signature

Bug#775877: gnome-session: No mouse pointer after login

[Simon McVittie]

On 09/03/15 23:41, Podrigal, Aron wrote:
> The missing mouse
> pointer however perhaps is not a bug in gnome-session. Its probably
> somewhere in gnome-settings-daemon

As I said already:
> Searching the gnome-settings-daemon source code, the only obvious
> possibility is in the power plugin. Aron, please try this and see
> whether it works better for you:
> 
> 
> https://people.debian.org/~smcv/gnome-settings-daemon_3.14.2-2+smcv1_amd64.deb

If you can still reproduce this problem with your current version of
g-s-d, please try that one, which I think might fix it.

If you can't reproduce this issue, then it probably shouldn't be
considered "grave" severity.

Thanks,
S


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

Bug#780074: [wishlist]: Add support for pre/post start/stop scripts

[Simon Deziel]

Unfortunately, the previous patch contained an error. Here is a
corrected version.
commit 69ab1dcd862ad8ca4df784ef75ee2b5c8545dba2
Author: Simon Deziel 
Date:   Sun Mar 8 21:27:42 2015 -0400

Add support for pre/post start/stop scripts (v2)

diff --git a/debian/openvpn.init.d b/debian/openvpn.init.d
index 8507ace..32299d8 100644
--- a/debian/openvpn.init.d
+++ b/debian/openvpn.init.d
@@ -38,7 +38,21 @@ if test -e /etc/default/openvpn ; then
   . /etc/default/openvpn
 fi
 
+exec_script () {
+  local rc=0
+  local script_path="$CONFIG_DIR/$NAME.$1"
+  [ -x "$script_path" ] || return $rc
+
+  export script_type="$1" config="$CONFIG_DIR/$NAME.conf"
+  "$script_path"; rc=$?
+  unset script_type config
+  return $rc
+}
+
 start_vpn () {
+# pre-start script
+exec_script "pre-start"
+
 if grep -q '^[	 ]*daemon' $CONFIG_DIR/$NAME.conf ; then
   # daemon already given in config file
   DAEMONARG=
@@ -93,8 +107,14 @@ start_vpn () {
 if [ "$SAVED_DEFAULT_SEND_REDIRECTS" -ne 0 ]; then
   sysctl -w net.ipv4.conf.default.send_redirects=$SAVED_DEFAULT_SEND_REDIRECTS > /dev/null
 fi
+
+# post-start script
+exec_script "post-start"
 }
 stop_vpn () {
+  # pre-stop script
+  exec_script "pre-stop"
+
   start-stop-daemon --stop --quiet --oknodo \
   --pidfile $PIDFILE --exec $DAEMON --retry 5
   if [ "$?" -eq 0 ]; then
@@ -102,6 +122,9 @@ stop_vpn () {
 [ "$OMIT_SENDSIGS" -ne 1 ] || rm -f /run/sendsigs.omit.d/openvpn.$NAME.pid
 rm -f /run/openvpn/$NAME.status 2> /dev/null
   fi
+
+  # post-stop script
+  exec_script "post-stop"
 }
 
 case "$1" in



openvpn-pre-post-start-stop-v2.patch.sig
Description: PGP signature

Bug#749090: minidlna: allow M-SEARCH from clients on other subnets

[Alexander Gerasiov]

Hello Eric,

There is more complex analysis of this issue in upstream's bugtracker:
 http://sourceforge.net/p/minidlna/patches/77/

Could you please test this patch. I've updated it according current 
minidlna's version:

http://anonscm.debian.org/cgit/collab-maint/minidlna.git/plain/debian/patches/08_fix_multicast_from_other_subnet.patch?id=02e74952c8714809c43c9aa7ed80ff07a0d7d82e

--
Alexander.


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

Bug#496832: bakefile Debian package

[Aleš Křivák]

Hi,
I am interested in packaging bakefile. I already have it here:

https://bitbucket.org/aleskrivak/bakefile/
branch: debian-1.2.5.1
upstream tarball: https://github.com/vslavik/bakefile/archive/v1.2.5.1.tar.gz

I can submit ITP for this package but I am not sure wheter I should
use this bugreport - previous discussion was about bakefile 0.2.x,
legacy version of bakefile with different syntax and incompatible with
current version...

Also, current version of bakefile is only a python module with single
executable script - should I rename the package to python-bakefile?

Thanks,
AK


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

Bug#780168: outdated constitution at www.debian.org/devel/constitution , should be version 1.5

[Stefano Zacchiroli]

Package: www.debian.org
Severity: normal

Heya, as per https://www.debian.org/vote/2014/vote_004 , the version of the
Debian Constitution published at https://www.debian.org/vote/2014/vote_004
should be updated to version 1.5 --- it is currently at version 1.4.

Version 1.5 of the Constitution is already shipped by doc-base; see my patch
implementing it as part of #777350.

I'm not sure if the online version of the Constitution is generated from
doc-base (and hence a simple rebuild is needed), or if a separate patch is
needed.

TIA,
Cheers.

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

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


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

Bug#780023: xbmc: XBMC crash at startup

[Bálint Réczey]

Control: reassign -1 libgl1-mesa-glx 10.3.2-1
Control: tags -1 - moreinfo unreproducible
Control: affects -1 xbmc

Hi Jeremy,

2015-03-09 23:25 GMT+01:00 Jeremy Guitton :
> Hi Balint,
>
> Are you sure hat is a sqlite issue ? From the log I see a segmentation fault
> on line 30 :
>
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  brw_meta_fast_clear (brw=brw@entry=0x27d8b68, fb=fb@entry=0x2839b60,
> buffers=buffers@entry=2, partial_clear=partial_clear@entry=false) at
> ../../../../../../../src/mesa/drivers/dri/i965/brw_meta_fast_clear.c:447

You are correct, it looks like a mesa crash, not an SQLite3 one:

Thread 1 (Thread 0x7ffd3af5c840 (LWP 17572)):
#0  brw_meta_fast_clear (brw=brw@entry=0x27d8b68,
fb=fb@entry=0x2839b60, buffers=buffers@entry=2,
partial_clear=partial_clear@entry=false) at
../../../../../../../src/mesa/drivers/dri/i965/brw_meta_fast_clear.c:447
#1  0x7ffd18303a48 in brw_clear (ctx=0x27d8b68, mask=2) at
../../../../../../../src/mesa/drivers/dri/i965/brw_clear.c:246
#2  0x012e7877 in CRenderSystemGL::ClearBuffers(unsigned int) ()
#3  0x00805180 in CGUIWindowManager::RenderPass() const ()
#4  0x00805388 in CGUIWindowManager::Render() ()
#5  0x00ccef77 in CApplication::RenderNoPresent() ()
#6  0x00ccf951 in CApplication::Render() ()
#7  0x00d87b51 in CXBApplicationEx::Run() ()
#8  0x00d8e43b in XBMC_Run ()
#9  0x006903a8 in main ()

I have not looked at the beginning of the file just started looking
for the first thread which was not in a blocking call - thus I missed
the real problem.

>
> To reproduce the bug just install a jessie with defaults options, add xbmc
> and lanch it with double-click on the icon. Like that xbmc segfault 2/3 of
> the time. No add-ons installed and fresh install, .xbmc in home deleted.
>
> I join to this mail, a log with mesa-dbg and  libsqlite3-0-dbg packages
> installed.
>
> A friend have the same issue, with also an intel graphic cards. Perhaps a
> bug in mesa ?
I'm reassigning the bug to mesa, in the hope that Mesa maintainers can
help in debugging and fixing the issue.

I started XBMC three times with no crash. My Intel card used for testing is:
$ lspci
...
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core
processor Graphics Controller (rev 09)
...

Cheers,
Balint

>
> Cheers.
> Jérémy
>
> 2015-03-09 21:06 GMT+01:00 Bálint Réczey :
>>
>> Control: tags -1 unreproducible moreinfo
>>
>> Hi Jeremy,
>>
>> 2015-03-08 11:57 GMT+01:00 Jeremy Guitton :
>> > Package: xbmc
>> > Version: 2:13.2+dfsg1-4
>> > Severity: important
>> >
>> > Dear Maintainer,
>> >
>> > On fresh install of jessie with Gnome Desktop, XBMC crash at startup. I
>> > join
>> > the log file.
>> From the logs it looks like the crash happens in SQLite 3.
>>
>> Thread 11 (Thread 0x7f6f7daaf700 (LWP 4072)):
>> #0  0x7f6fb0dd4860 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
>> #1  0x7f6fb0de003b in ?? () from
>> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
>> #2  0x7f6fb0df142c in ?? () from
>> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
>> #3  0x7f6fb0e0c659 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
>> #4  0x7f6fb0e0c85f in ?? () from
>> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
>> #5  0x7f6fb0e0cfc5 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
>> #6  0x7f6fb0e3ef21 in ?? () from
>> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
>> #7  0x7f6fb0e3ff27 in sqlite3_step () from
>> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
>> #8  0x00a10062 in dbiplus::SqliteDataset::query
>> (this=0x7f6f680863d0, query=0x7f6f6801d4f8 "SELECT sum(watchedcount)
>> FROM tvshowview LIMIT 1") at sqlitedataset.cpp:662
>> #9  0x009ee8f1 in CDatabase::GetSingleValue
>> (this=this@entry=0x7f6f7daaeb60, que
>>
>> If you can reproduce the issue please install libsqlite3-0-dbg to have
>> a better stack trace and attach it.
>>
>> I tried reproducing the crash, but with no luck. Could you please list
>> the steps I need to take?
>> Do you have any add-ons installed?
>>
>> Cheers,
>> Balint
>>
>> >
>> >
>> >
>> > -- System Information:
>> > Debian Release: 8.0
>> >   APT prefers testing-updates
>> >   APT policy: (500, 'testing-updates'), (500, 'testing')
>> > Architecture: amd64 (x86_64)
>> > Foreign Architectures: i386
>> >
>> > Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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: systemd (via /run/systemd/system)
>> >
>> > Versions of packages xbmc depends on:
>> > ii  fonts-dejavu-core  2.34-1
>> > ii  fonts-roboto   1:4.4.4r2-6
>> > ii  libjs-iscroll  5.1.2+dfsg1-1
>> > ii  libjs-jquery   1.7.2+dfsg-3.2
>> > ii  mesa-utils 8.2.0-1
>> > ii  python-imaging 2.6.1-1
>> > pn  python:any 
>> > ii  ttf-dejavu-core2.34-1
>> > ii  x11-utils  7.7+2
>> > ii  xbmc-bin   2:13.2+dfsg1-4
>> >
>> > xbmc re

Bug#775877: gnome-session: No mouse pointer after login

[Podrigal, Aron]

Hi Simon, sorry for my late response, That issue seems like its gone
already for a while, I did not notice when exactly. It has been some time
and I've had some updates to some other packages. The missing mouse pointer
however perhaps is not a bug in gnome-session. Its probably somewhere in
gnome-settings-daemon, however I tried running it with --debug but did not
notice any special log entries leading to this.
If you can advise where and how to look for, I will definitely try to find
the problem.

Thanks

On Mon, Mar 9, 2015 at 4:50 PM, Simon McVittie  wrote:

> On 06/03/15 10:00, Simon McVittie wrote:
> > On Tue, 20 Jan 2015 at 21:43:09 -0500, Aron Podrigal wrote:
> >>  Jan 20 16:46:18 jessie gnome-session[1888]:
> >>
> GLib-GIO:ERROR:/tmp/buildd/glib2.0-2.42.1/./gio/gdbusconnection.c:4231:invoke_set_property_in_idle_cb:
> >>  assertion failed: (error != NULL)
> >
> > This seems likely to be the problem: gnome-settings-daemon crashed with
> > an assertion failure.
>
> gdbusconnection.c:4231 is the last of the lines I've quoted here:
>
>   if (!data->vtable->set_property (data->connection,
>g_dbus_message_get_sender
> (data->message),
>g_dbus_message_get_path (data->message),
>data->interface_info->name,
>data->property_name,
>value,
>&error,
>data->user_data))
> {
>   gchar *dbus_error_name;
>   g_assert (error != NULL);
>
> So the bug here is that something, somewhere in the
> gnome-settings-daemon process, has a set_property() callback
> that fails without correctly setting the error.
>
> Searching the gnome-settings-daemon source code, the only obvious
> possibility is in the power plugin. Aron, please try this and see
> whether it works better for you:
>
>
> https://people.debian.org/~smcv/gnome-settings-daemon_3.14.2-2+smcv1_amd64.deb
>
> Regards,
> S
>
>

Bug#778729: Try 2: Bug#778729: RFS: git-tools/1.0.0-1 [ITP]

[Adam Borowski]

On Mon, Mar 09, 2015 at 11:49:08PM +0100, Stephen Kitt wrote:
> > Thus, it would feel odd to have a package named "git-tools" that contains
> > only two tools of some note.
> 
> OK, stick with git-restore-mtime as the binary package then. I'm wondering if
> it would be better to call the source package git-mestrelion-tools...

Good idea, I've just done so.

> > > While I'm at it, given that you're shipping extra manpages, wouldn't it be
> > > worth it to ship the help2man-generated manpage as well, instead of
> > > rebuilding it every time?
> > 
> > I build it from source to make sure new upstream changes are incorporated.
> 
> That's what I reckoned, although you'd still need to tweak the version number
> in debian/rules every time.

The version number is just something help2man wants, man works fine without.

> > On the other hand, this makes it near impossible to adjust the output, and
> > is inconsistent with the other three manpages, all of which are
> > hand-crafted.  Thus, you're probably right, it would be better to ship
> > the manpage instead of building it from source.

Done.

> Shall I wait for that then before uploading?

Should be ready now.  However, mentors.d.n seems to not allow uploading the
same binary package with a different source more than once per day (there's
some cronjob AFAIK), so I had to use my own repository:

http://angband.pl/debian/pool/main/g/git-mestrelion-tools/git-mestrelion-tools_1.0.0-1.dsc


-- 
// If you believe in so-called "intellectual property", please immediately
// cease using counterfeit alphabets.  Instead, contact the nearest temple
// of Amon, whose priests will provide you with scribal services for all
// your writing needs, for Reasonable and Non-Discriminatory prices.


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

Bug#773443: [PATCH] host.conf.5: keywords and env. var. nospoof, spoofalert, spoof and RESOLV_SPOOF_CHECK were added to glibc 2.0.7 but never implemented

[Stéphane Aulery]

Move descriptions to historical section and reorder it for clarity

Debian Bug #773443 reported by yg...@ygrex.ru

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773443
Signed-off-by: Stéphane Aulery 
---
 man5/host.conf.5 | 125 ---
 1 file changed, 63 insertions(+), 62 deletions(-)

diff --git a/man5/host.conf.5 b/man5/host.conf.5
index 9ff2ed3..08da435 100644
--- a/man5/host.conf.5
+++ b/man5/host.conf.5
@@ -66,52 +66,6 @@ This is
 by default, as it may cause a substantial performance loss at sites
 with large hosts files.
 .TP
-.I nospoof
-Valid values are
-.IR on " and " off .
-If set to
-.IR on ,
-the resolv+ library will attempt to prevent hostname spoofing to
-enhance the security of
-.BR rlogin " and " rsh .
-It works as follows: after performing a host address lookup, resolv+
-will perform a hostname lookup for that address.
-If the two hostnames
-do not match, the query will fail.
-The default value is
-.IR off .
-.TP
-.I spoofalert
-Valid values are
-.IR on " and " off .
-If this option is set to
-.I on
-and the
-.I nospoof
-option is also set, resolv+ will log a warning of the error via the
-syslog facility.
-The default value is
-.IR off .
-.TP
-.I spoof
-Valid values are
-.IR off ", " nowarn " and " warn .
-If this option is set to
-.IR off ,
-spoofed addresses are permitted and no warnings will be emitted
-via the syslog facility.
-If this option is set to
-.IR warn ,
-resolv+ will attempt to prevent hostname spoofing to
-enhance the security and log a warning of the error via the syslog
-facility.
-If this option is set to
-.IR nowarn ,
-the resolv+ library will attempt to prevent hostname spoofing to
-enhance the security but not emit warnings via the syslog facility.
-Setting this option to anything else is equal to setting it to
-.IR nowarn .
-.TP
 .I reorder
 Valid values are
 .IR on " and " off .
@@ -133,15 +87,6 @@ override the behavior which is configured in
 If set, this variable points to a file that should be read instead of
 .IR /etc/host.conf .
 .TP
-.B RESOLV_SPOOF_CHECK
-Overrides the
-.IR nospoof ", " spoofalert " and " spoof
-commands in the same way as the
-.I spoof
-command is parsed.
-Valid values are
-.IR off ", " nowarn " and " warn .
-.TP
 .B RESOLV_MULTI
 Overrides the
 .I multi
@@ -184,6 +129,10 @@ can take arguments like
 .IR off ", " nowarn " and " warn .
 Line comments can appear anywhere and not only at the beginning of a line.
 .SS Historical
+The
+.BR nsswitch.conf (5)
+file is the modern way of controlling the order of host lookups.
+.PP
 In glibc 2.4 and earlier, the following keyword is recognized:
 .TP
 .I order
@@ -191,15 +140,67 @@ This keyword specifies how host lookups are to be 
performed.
 It should be followed by one or more lookup methods, separated by commas.
 Valid methods are
 .IR bind ", " hosts ", and " nis .
-The
+.TP
 .B RESOLV_SERV_ORDER
-environment variable could be used to override the
-.I order
-command.
+Overrides the order command.
 .PP
-The
-.BR nsswitch.conf (5)
-file is the modern way of controlling the order of host lookups.
+Since glibc 2.0.7, the following keywords and environment variable have
+been recognized but never implemented:
+.TP
+.I nospoof
+Valid values are
+.IR on " and " off .
+If set to
+.IR on ,
+the resolv+ library will attempt to prevent hostname spoofing to
+enhance the security of
+.BR rlogin " and " rsh .
+It works as follows: after performing a host address lookup, resolv+
+will perform a hostname lookup for that address.
+If the two hostnames
+do not match, the query will fail.
+The default value is
+.IR off .
+.TP
+.I spoofalert
+Valid values are
+.IR on " and " off .
+If this option is set to
+.I on
+and the
+.I nospoof
+option is also set, resolv+ will log a warning of the error via the
+syslog facility.
+The default value is
+.IR off .
+.TP
+.I spoof
+Valid values are
+.IR off ", " nowarn " and " warn .
+If this option is set to
+.IR off ,
+spoofed addresses are permitted and no warnings will be emitted
+via the syslog facility.
+If this option is set to
+.IR warn ,
+resolv+ will attempt to prevent hostname spoofing to
+enhance the security and log a warning of the error via the syslog
+facility.
+If this option is set to
+.IR nowarn ,
+the resolv+ library will attempt to prevent hostname spoofing to
+enhance the security but not emit warnings via the syslog facility.
+Setting this option to anything else is equal to setting it to
+.IR nowarn .
+.TP
+.B RESOLV_SPOOF_CHECK
+Overrides the
+.IR nospoof ", " spoofalert " and " spoof
+commands in the same way as the
+.I spoof
+command is parsed.
+Valid values are
+.IR off ", " nowarn " and " warn .
 .SH SEE ALSO
 .BR gethostbyname (3),
 .BR hosts (5),
-- 
2.1.4


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

Bug#773443: host.conf.5: spoof deprecated ?

[Stéphane Aulery]

Hello Michael,

Le lundi 09 mars 2015 à 10:03:09, Michael Kerrisk (man-pages) a écrit :
> On 03/09/2015 08:59 AM, Stéphane Aulery wrote:
> > Le lundi 09 mars 2015 à 08:22:01, Michael Kerrisk (man-pages) a écrit :
> >>
> >> On 03/08/2015 02:05 PM, Stéphane Aulery wrote:
> >>>
> >>> A Debian user reported that [1]:
> >>>
>  spoof* keywords (nospoof, spoofalert, spoof) are here from 1996,
>  they are still valid keywords but do not have any effect apparently,
>  no libraries or tools use them
> 
>  it is misleading to see references to resolv+ and rlogin, the keywords
>  are just ignored these days; the only meaning they have is that they
>  are
>  allowed by host.conf syntax
> >>>
> >>> The glibc source code seems to confirm that the keywords nospoof,
> >>> spoofalert and spoof are accepted but without effects. I could find
> >>> nothing in the changelog. Could you please confirm that they are
> >>> obsolete? I could correct the man page accordingly.
> >>
> >> I had a quick grep in the glibc source code.
> >>
> >> It appears that you (and the reporter) are correct. (Even back in 
> >> glibc 2.1, things look the same).
> >>
> >> A patch would be appreciated!

I dug a little further comparing versions 2.0.6 [1], 2.0.7 [2]
and trunk [3] of glibc and I come to a different conclusion.

The keywords nospoof, spoofalert, spoof and RESOLV_SPOOF_CHECK were
added to glibc 2.0.7 but never implemented and documented in the
changelog.

[1] http://ftp.gnu.org/gnu/glibc/glibc-2.0.6.tar.gz
[2] 
http://archive.debian.org/debian/dists/hamm/main/source/libs/glibc_2.0.7t.orig.tar.gz
[3] https://sourceware.org/git/?p=glibc.git&a=search&h=HEAD&st=grep&s=spoof&sr=1

Regards,

-- 
Stéphane Aulery


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

Bug#780167: /usr/bin/rmadison: Deal with arch when querying package:arch

[Nelson A. de Oliveira]

Package: devscripts
Version: 2.15.1
Severity: wishlist
File: /usr/bin/rmadison

Suppose we have an user (I won't say it was me) trying to understand this:

=
$ rmadison openjdk-7-jre:amd64
debian:
new:
=

Could rmadison ignore the arch or maybe threat it like "rmadison
openjdk-7-jre -a amd64", please?

Thank you!

Best regards,
Nelson


-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
Not present

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

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

Versions of packages devscripts depends on:
ii  dpkg-dev 1.17.24
ii  libc62.19-15
ii  perl 5.20.2-2
ii  python3  3.4.2-2
pn  python3:any  

Versions of packages devscripts recommends:
ii  at  3.1.16-1
ii  curl7.38.0-4
ii  dctrl-tools 2.23
ii  debian-keyring  2015.03.04
ii  dput0.9.6.4
pn  equivs  
ii  fakeroot1.20.2-1
ii  file1:5.22+15-1
ii  gnupg   1.4.18-7
pn  libdistro-info-perl 
ii  libencode-locale-perl   1.03-1
pn  libjson-perl
ii  liblwp-protocol-https-perl  6.06-2
pn  libparse-debcontrol-perl
ii  libsoap-lite-perl   1.11-1
ii  liburi-perl 1.64-1
ii  libwww-perl 6.08-1
ii  lintian 2.5.30+deb8u3
ii  man-db  2.7.0.2-5
ii  patch   2.7.5-1
ii  patchutils  0.3.3-1
ii  python3-debian  0.1.25
pn  python3-magic   
ii  sensible-utils  0.0.9
ii  strace  4.9-2
ii  unzip   6.0-16
ii  wdiff   1.2.2-1
ii  wget1.16.2-2
ii  xz-utils5.1.1alpha+20120614-2+b3

Versions of packages devscripts suggests:
ii  bsd-mailx [mailx]8.1.2-0.20141216cvs-1
ii  build-essential  12
pn  cvs-buildpackage 
pn  debbindiff   
pn  devscripts-el
pn  gnuplot  
ii  gpgv 1.4.18-7
pn  libauthen-sasl-perl  
pn  libfile-desktopentry-perl
ii  libnet-smtp-ssl-perl 1.01-3
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
pn  libyaml-syck-perl
ii  mutt 1.5.23-3
ii  openssh-client [ssh-client]  1:6.7p1-3
ii  svn-buildpackage 0.8.5+nmu1
ii  w3m  0.5.3-19

-- no debconf information


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

Bug#780093: [Pkg-libvirt-maintainers] Bug#780093: libvirt: error: unsupported configuration: QEMU 2.1.2 is too new for help parsing

[Thorsten Glaser]

On Mon, 9 Mar 2015, Guido Günther wrote:

> wrapping qemu/kvm by a skript or something?

Yes, necessarily:

tglase@tglase:~ $ virsh -c qemu:///system dumpxml MirBSD | fgrep emul   
 
/usr/local/bin/qemu-in-chroot
tglase@tglase:~ $ cat /usr/local/bin/qemu-in-chroot
#!/bin/sh
exec schroot -c sid-amd64 -u root -- qemu-system-x86_64 -enable-kvm "$@"

Otherwise I cannot assign more than 2047 MiB RAM.

*But*:

tglase@tglase:~ $ virsh -c qemu:///system dumpxml SuSE_Linux_1.0 | fgrep emul
/usr/bin/kvm
tglase@tglase:~ $ virsh -c qemu:///system start SuSE_Linux_1.0
error: Failed to start domain SuSE_Linux_1.0
error: unsupported configuration: QEMU 2.1.2 is too new for help parsing

So this also happens for VMs created by virt-manager and
then untouched.

> Does
> 
> virsh capabilities
> 
> show the same error?

No, it shows a bunch of XML things (capabilities/{host,guest}/…).

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg


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

Bug#779285: tudu: Tudu crashes with segmentation fault when deleting main task whithout subtasks

[Ruben Pollan]

Hello Sébastien,

Quoting Sébastien POHER (2015-02-26 16:16:20)
>* What led up to the situation?
> 
> I tried to delete a main task, first of all whithout deleting its subtasks. 
> This leads to seg fault.
> Then I deleted, one by one, all subtasks, then tried to delete the main task. 
> This leads to seg fault as well.
> 
>* What outcome did you expect instead?
> 
> Normally, deleting ("dd" keyboard input) should delete the task

I'm not able to reproduce the issue. Can you start from a clean file with 
something like:
$ tudu -f /tmp/tudu.xml

And describe to me step by step what to do to reproduce the issue.

Thank you for your report.

-- 
Ruben Pollan  | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: http://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.


signature.asc
Description: signature

Bug#780133: DH_VERBOSE under dh command

[Tianon Gravi]

On Mon, Mar 09, 2015 at 09:12:30PM +, Tianon Gravi wrote:
> On Mon, Mar 09, 2015 at 05:40:50PM +0100, Niels Thykier wrote:
> > I suppose we can stress the fact a bit harder.
> 
> I'd like to take a stab at this one, if you don't mind. :)

Ok, here's my initial stab at improving this section to make the point
more clear:

| diff --git a/debhelper.pod b/debhelper.pod
| index 9415d78..f5d27f6 100644
| --- a/debhelper.pod
| +++ b/debhelper.pod
| @@ -660,6 +660,12 @@ F, F, F, and F scripts, 
etc.
|  
|  =head1 ENVIRONMENT
|  
| +The following environment variables can influence the behavior of debhelper.
| +It is important to note that these must be actual environment variables in
| +order to function properly (not simply F variables). To specify
| +them properly in F, be sure to prefix their assignment with
| +"B". For example, "B".
| +
|  =over 4
|  
|  =item B

Would appreciate some prose review before I commit, though. :)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


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

Bug#780166: openjdk-7-jre: XML parser returns corrupt attribute value (fixed in 7u76)

[Nelson A. de Oliveira]

Package: openjdk-7-jre
Version: 7u75-2.5.4-2
Severity: normal

Can we have something updated/backported/patched to fix this
https://bugs.openjdk.java.net/browse/JDK-8059327 please?

I hit it while trying to use JOSM and open a bziped2 file.

Thank you!

Best regards,
Nelson

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

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

Versions of packages openjdk-7-jre depends on:
ii  libasound21.0.28-1
ii  libatk-wrapper-java-jni   0.30.5-1
ii  libatk1.0-0   2.14.0-1
ii  libc6 2.19-15
ii  libcairo2 1.14.0-2.1
ii  libcups2  1.7.5-11
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-3
ii  libgdk-pixbuf2.0-02.31.1-2+b1
ii  libgif4   4.1.6-11
ii  libgl1-mesa-glx [libgl1]  10.4.2-2
ii  libglib2.0-0  2.42.1-1
ii  libgtk2.0-0   2.24.25-3
ii  libjpeg62-turbo   1:1.3.1-12
ii  libpango-1.0-01.36.8-3
ii  libpangocairo-1.0-0   1.36.8-3
ii  libpangoft2-1.0-0 1.36.8-3
ii  libpng12-01.2.50-2+b2
ii  libx11-6  2:1.6.2-3
ii  libxext6  2:1.3.3-1
ii  libxi62:1.7.4-1+b2
ii  libxinerama1  2:1.1.3-1+b1
ii  libxrandr22:1.4.2-1+b1
ii  libxrender1   1:0.9.8-1+b1
ii  libxtst6  2:1.2.2-1+b1
ii  openjdk-7-jre-headless7u75-2.5.4-2
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages openjdk-7-jre recommends:
pn  fonts-dejavu-extra  
ii  libgconf2-4 3.2.6-3
pn  libgnome2-0 
ii  libgnomevfs2-0  1:2.24.4-6+b1

Versions of packages openjdk-7-jre suggests:
ii  icedtea-7-plugin  1.5.2-1

-- no debconf information


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

Bug#780154: unblock: oss4/4.2-build2010-2

[Samuel Thibault]

Hello,

Ivo De Decker, le Mon 09 Mar 2015 23:53:11 +0100, a écrit :
> Once kfreebsd is removed from jessie, I'll reinstate the removal hint.

Why so?  The oss4 package maintainers had added the Linux drivers part
of it for some reason I guess (and it's not kfreebsd).

Samuel


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

Bug#780154: unblock: oss4/4.2-build2010-2

[Julien Cristau]

Control: tag -1 moreinfo

On Mon, Mar  9, 2015 at 22:22:21 +0100, Samuel Thibault wrote:

> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Please unblock package oss4
> 
> A security issue was filed against the usb drivers contained in the oss4
> package, and was pung again late January as #775662, but maintainers of
> that part of the package didn't seem to have discussed with upstream
> about it.  Considering how many issues there are in there, I tend not to
> trust the module at all.  In upload oss4/4.2-build2010-2, I have thus
> just disabled the usb module, see attached debdiff.
> 
This should probably be reconciled with #778332 somehow.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#780155: ITP: baculum -- Baculum WebGUI tool for Bacula Community program

[Marcin Haba]

On 09.03.2015 22:57, Cameron Norman wrote:
> On Mon, Mar 9, 2015 at 2:13 PM, gani  wrote:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Marcin Haba 
>>
>> * Package name: baculum
>>   Version : 7.0+git20150208
>>   Upstream Author : Marcin Haba 
>> * URL : http://www.bacula.org/
>> * License : AGPLv3
>>   Programming Lang: PHP
>>   Description : Baculum WebGUI tool for Bacula Community program
> 
> I see you linked to the bacula.org homepage for this package. Am I
> correct in saying that what you are packaging can be found here:
> 
> http://www.bacula.org/git/cgit.cgi/bacula/tree/gui
> 
> if so there seems to already be packaging (outside of Debian) that
> uses the bweb name for the package.
> If not, would you mind clarifying which GUI tool for Bacula this is
> with a link to a homepage and / or git repo?

Hello,

Bweb tool in Bacula Community has been removed from bacula-gui release
archive from version 7.0.x. From the same version 7.0 has introduced
Baculum tool to bacula-gui archive.

Here is Baculum in Bacula Git repository:

http://www.bacula.org/git/cgit.cgi/bacula/tree/gui/baculum?h=Branch-7.0

>>  - is it a dependency for another package?
>>
>> Yes, it is. Baculum uses external toolset - PRADO Framework.
>> Additionally Baculum uses external JavaScript libraries.
> 
> Actually those are the dependencies of this project. The question is
> if this package is a dependency of another package (in the same way
> PRADO is a dependency of this package).

OK. Thank you for clarification. I was thinking that question is about
general packages/projects. In Debian I have not seen PRADO Framework in
packages, similar as Opentip JavaScript library and Flotr2 library. They
are Baculum dependencies that I wrote up in debian/copyright in Baculum
deb metadata file.

I have seen libjs-flotr, but probably it is older version of Flotr2
project. I need to check it.

>>  - how do you plan to maintain it?
>> After each Bacula and Baculum release I plan to build Baculum deb and rpm
>> packages for community. From deb packages I am going to build also for 
>> Debian.
>>
>>  - inside a packaging team?
>> I am not sure about packaging team. I have never been packages maintainer.
> 
> You should probably maintain it inside the Debian Bacula Team. This
> will make it easier to find a sponsor (which I will get to) and help
> if need be.

OK. It is fine for me.

>>  - do you need a sponsor?
>> No. I do not.
> 
> You mentioned that you have never made Debian packages before. Thus,
> you are not a Debian developer and need a debian developer to review
> and then upload the packages for you. This is what a sponsor is. You
> need a sponsor.

I did not say that I have never made Debian packages before. I just have
never been packages maintainer. Anyway, from that what I read and
understood, sponsor is person that prepares build packages instead of
me. If I am wrong, I am sorry, Lately I read a lot of different texts in
Internet.

I prepared Baculum project on Launchpad for Ubuntu as PPA project.

Best regards.
Marcin Haba

> 
> --
> Cameron Norman
> 


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

Bug#779600: linux-image-3.16.0-4-686-pae: Linux console does not render the bold attribute correctly

[Samuel Bronson]

Source: linux
Version: 3.16.7-ckt7-1
Control: retitle -1 linux-image-3.16.0-4-686-pae: i915: does not render console 
bold correctly on HDMI

In particular, (170,170,170) is indistinguishable from (255,255,255) on
my HDMI-connected TV, but a VGA-connected monitor does fine.

I'm attaching the entire dmesg output I get when I pass "debug=0xe" to
the drm module and boot with just the TV connected, on the theory that
the debugging output from i915 might be useful.

Of course, it could easily still be a problem with my TV or its default
configuration...
Linux devbox 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01) i686 
GNU/Linux
-
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!

Bug#778729: Try 2: Bug#778729: RFS: git-tools/1.0.0-1 [ITP]

[Stephen Kitt]

On Mon, 9 Mar 2015 10:57:02 +0100, Adam Borowski  wrote:
> On Sun, Mar 08, 2015 at 04:20:08PM +0100, Stephen Kitt wrote:
> > Could you fix up debian/patches/debian-changes? It's just got
> > auto-generated template headers... Or is that because you're using
> > single-debian-patch in debian/source/options?
> 
> The latter.  I guess, dpkg-source shouldn't insert that template if
> single-debian-patch is set.  It's pointless to duplicate the work if all
> changes are already tracked and documented in a proper VCS.

OK, that's fine by me. (I guess you could file a bug if one isn't already
filed!)

> > Also, I know this has been debated before, but it seems rather
> > restrictive to call the binary package git-restore-mtime, given that
> > there are other useful git tools in the package.
> 
> Actually, it was the source name that was discussed.
> 
> As for binary, my reason is that "git restore-mtime" is the main point of
> interest here, the other tools being just thrown in.  Their usefulness is
> quite marginal.  In fact, I dropped two altogether: git-branches-rename and
> git-rebase-theirs as both can be reproduced by an one-liner.
> 
> As for three tools that I left in, git-find-uncommited-repos probably should
> be axed too -- it's just "find -name .git -execdir 'git status'" with some
> output massaging.  git-strip-merge is both situational and trivial to
> reproduce.  The only other tool with some real use is git-clone-subset.
> 
> Thus, it would feel odd to have a package named "git-tools" that contains
> only two tools of some note.

OK, stick with git-restore-mtime as the binary package then. I'm wondering if
it would be better to call the source package git-mestrelion-tools...

> > While I'm at it, given that you're shipping extra manpages, wouldn't it be
> > worth it to ship the help2man-generated manpage as well, instead of
> > rebuilding it every time?
> 
> I build it from source to make sure new upstream changes are incorporated.

That's what I reckoned, although you'd still need to tweak the version number
in debian/rules every time.

> On the other hand, this makes it near impossible to adjust the output, and
> is inconsistent with the other three manpages, all of which are
> hand-crafted.  Thus, you're probably right, it would be better to ship
> the manpage instead of building it from source.

Shall I wait for that then before uploading?

Regards,

Stephen


pgpkiwIQCtWVA.pgp
Description: OpenPGP digital signature

Bug#779832: needrestart: Use of uninitialized value in chdir

[Thomas Liske]

Hi,


On 03/05/2015 11:45 AM, wforumw wrote:
> Always when I run needrestart I get
> Use of uninitialized value in chdir at 
> /usr/share/perl5/NeedRestart/Interp/Python.pm line 119.
> Use of chdir('') or chdir(undef) as chdir() is deprecated at 
> /usr/share/perl5/NeedRestart/Interp/Python.pm line 119.
> Use of uninitialized value in chdir at 
> /usr/share/perl5/NeedRestart/Interp/Python.pm line 119.
> Use of chdir('') or chdir(undef) as chdir() is deprecated at 
> /usr/share/perl5/NeedRestart/Interp/Python.pm line 119.
> Running kernel seems to be up-to-date.
> No services need to be restarted.
> 
> I habe purged and re-installed the package but the issue still occurs.
> 
> Why I get these warnings?

the Python interpreter backend seems to be unable to retrieve the
current working directory of one of the python processes. This sounds
interesting... could you please provide the output of:

needrestart -v -n -r l


HTH & TIA,
Thomas

> Thanks
> 
> 
> 
> -- Package-specific info:
> needrestart output:
> Running kernel seems to be up-to-date.
> No services need to be restarted.
> 
> 
> -- System Information:
> Debian Release: 8.0
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages needrestart depends on:
> ii  dpkg   1.17.24
> ii  libmodule-find-perl0.12-1
> ii  libmodule-scandeps-perl1.16-1
> ii  libproc-processtable-perl  0.51-1
> ii  libsort-naturally-perl 1.03-1
> ii  libterm-readkey-perl   2.32-1+b1
> ii  perl   5.20.1-5
> 
> needrestart recommends no packages.
> 
> needrestart suggests no packages.
> 
> -- no debconf information
> 


-- 

::  WWW: http://fiasko-nw.net/~thomas/  ::
   :::  Jabber:   xmpp:tho...@jabber.fiasko-nw.net  :::
::  flickr:  http://www.flickr.com/photos/laugufe/  ::


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

Bug#779329: linux-image-3.16.0-4-amd64: atl1 issue seems to be fixed in 3.16.7-ckt7-1

[Szymon Łapiński]

Package: src:linux
Followup-For: Bug #779329



-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt7-1 (2015-03-01)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=3404940f-c1f8-484d-8e46-b7f7f4677349 ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[   19.555494] atl1 :01:00.0: irq 44 for MSI/MSI-X
[   19.88] atl1 :01:00.0: eth1 link is up 1000 Mbps full duplex

01:00.0 Ethernet controller [0200]: Qualcomm Atheros Attansic L1 Gigabit 
Ethernet [1969:1048] (rev b0)
Subsystem: ASUSTeK Computer Inc. P5KPL-VM Motherboard [1043:8226]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: atl1


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

Bug#780165: macchanger: $ENABLE_INTERFACES in /etc/default/macchanger ignored

[Maximilian Stein]

Package: macchanger
Version: 1.7.0-5.3
Severity: important
Tags: patch

Dear Maintainer,

unfortunately setting ENABLE_INTERFACES in /etc/default/macchanger has
no effect, so even the MACs of my virtual interfaces had been set
randomly which made them stop working in turn.

Reading /etc/macchanger/ifupdown.sh I recognized that this variable is
ignored completely. I will attach a patch for
/etc/macchanger/ifupdown.sh checking if the devices occurs in
ENABLE_INTERFACES when it is set, however I need to use bash instead of
sh.

Furthermore, observing the log file (/var/log/macchanger) I noticed that
somebody tries to call the script with the option --all which is neither
supported by ifupdown.sh nor by macchanger itself.

Thank you!

Yours sincerely,
Maximilian Stein

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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 macchanger depends on:
ii  debconf [debconf-2.0]  1.5.55
ii  dpkg   1.17.24
ii  install-info   5.2.0.dfsg.1-6
ii  libc6  2.19-15

macchanger recommends no packages.

macchanger suggests no packages.

-- Configuration Files:
/etc/default/macchanger changed:
ENABLE_ON_POST_UP_DOWN=true
ENABLE_INTERFACES="wlan0 eth0"

/etc/macchanger/ifupdown.sh changed:
package=macchanger
. /etc/default/${package}
LOGFILE=/var/log/${package}.log
if [ "$ENABLE_ON_POST_UP_DOWN" != "true" ]; then
echo "disabled in /etc/default/${package}" >> $LOGFILE
exit
fi
echo "IFACE = $IFACE" >> $LOGFILE
if [ "$IFACE" = lo ]; then
echo "ignoring loopback" >> $LOGFILE
exit 0
fi
if [ ! -z "$ENABLE_INTERFACES" ]; then
if [[ ! "$ENABLE_INTERFACES" =~ "$IFACE" ]]; then
echo "ignoring $IFACE" >> $LOGFILE
exit 0
fi
fi
/usr/bin/${package} -a $IFACE >> $LOGFILE 2>&1


-- debconf information:
* macchanger/automatically_run: true

--- /etc/macchanger/ifupdown.sh.bak	2015-03-09 22:53:07.066707847 +0100
+++ /etc/macchanger/ifupdown.sh	2015-03-09 23:03:32.241482116 +0100
@@ -1,4 +1,4 @@
-#!/bin/sh
+#!/bin/bash
 #
 # randomize MAC address before connecting to wifi or ethernet
 #
@@ -29,4 +29,12 @@
 exit 0
 fi
 
+# if ENABLE_INTERFACES is set, quit if IFACE not in that list
+if [ ! -z "$ENABLE_INTERFACES" ]; then
+if [[ ! "$ENABLE_INTERFACES" =~ "$IFACE" ]]; then
+echo "ignoring $IFACE" >> $LOGFILE
+exit 0
+fi
+fi
+
 /usr/bin/${package} -a $IFACE >> $LOGFILE 2>&1



signature.asc
Description: OpenPGP digital signature

Bug#780155: ITP: baculum -- Baculum WebGUI tool for Bacula Community program

[Marcin Haba]

On 09.03.2015 23:25, Marcin Haba wrote:
> On 09.03.2015 22:57, Cameron Norman wrote:
>> On Mon, Mar 9, 2015 at 2:13 PM, gani  wrote:
>>> Package: wnpp
>>> Severity: wishlist
>>> Owner: Marcin Haba 
>>>
>>> * Package name: baculum
>>>   Version : 7.0+git20150208
>>>   Upstream Author : Marcin Haba 
>>> * URL : http://www.bacula.org/
>>> * License : AGPLv3
>>>   Programming Lang: PHP
>>>   Description : Baculum WebGUI tool for Bacula Community program
>>
>> I see you linked to the bacula.org homepage for this package. Am I
>> correct in saying that what you are packaging can be found here:
>>
>> http://www.bacula.org/git/cgit.cgi/bacula/tree/gui
>>
>> if so there seems to already be packaging (outside of Debian) that
>> uses the bweb name for the package.
>> If not, would you mind clarifying which GUI tool for Bacula this is
>> with a link to a homepage and / or git repo?
> 
> Hello,
> 
> Bweb tool in Bacula Community has been removed from bacula-gui release
> archive from version 7.0.x. From the same version 7.0 has introduced
> Baculum tool to bacula-gui archive.
> 
> Here is Baculum in Bacula Git repository:
> 
> http://www.bacula.org/git/cgit.cgi/bacula/tree/gui/baculum?h=Branch-7.0
> 
>>>  - is it a dependency for another package?
>>>
>>> Yes, it is. Baculum uses external toolset - PRADO Framework.
>>> Additionally Baculum uses external JavaScript libraries.
>>
>> Actually those are the dependencies of this project. The question is
>> if this package is a dependency of another package (in the same way
>> PRADO is a dependency of this package).
> 
> OK. Thank you for clarification. I was thinking that question is about
> general packages/projects. In Debian I have not seen PRADO Framework in
> packages, similar as Opentip JavaScript library and Flotr2 library. They
> are Baculum dependencies that I wrote up in debian/copyright in Baculum
> deb metadata file.

One more thing to clarify. Mentioned debian/copyright file I published
on Launchpad, but it is not in Git repository on bacula.org yet. I
prepared it short time ago.

Best regards.
Marcin Haba

> 
> I have seen libjs-flotr, but probably it is older version of Flotr2
> project. I need to check it.
> 
>>>  - how do you plan to maintain it?
>>> After each Bacula and Baculum release I plan to build Baculum deb and rpm
>>> packages for community. From deb packages I am going to build also for 
>>> Debian.
>>>
>>>  - inside a packaging team?
>>> I am not sure about packaging team. I have never been packages maintainer.
>>
>> You should probably maintain it inside the Debian Bacula Team. This
>> will make it easier to find a sponsor (which I will get to) and help
>> if need be.
> 
> OK. It is fine for me.
> 
>>>  - do you need a sponsor?
>>> No. I do not.
>>
>> You mentioned that you have never made Debian packages before. Thus,
>> you are not a Debian developer and need a debian developer to review
>> and then upload the packages for you. This is what a sponsor is. You
>> need a sponsor.
> 
> I did not say that I have never made Debian packages before. I just have
> never been packages maintainer. Anyway, from that what I read and
> understood, sponsor is person that prepares build packages instead of
> me. If I am wrong, I am sorry, Lately I read a lot of different texts in
> Internet.
> 
> I prepared Baculum project on Launchpad for Ubuntu as PPA project.
> 
> Best regards.
> Marcin Haba
> 
>>
>> --
>> Cameron Norman
>>


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

Bug#780163: gftp: please reintegrate gftp in testing

[gpe92]

Package: gftp
Version: 2.0.19-4
Severity: wishlist

Dear Maintainer,

gftp works fine in testing now.
Why is it always removed from testing ?

Regards.

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

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

Versions of packages gftp depends on:
ii  gftp-gtk   2.0.19-4
ii  gftp-text  2.0.19-4

gftp recommends no packages.

gftp suggests no packages.

-- no debconf information


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

Bug#780159: qemu-kvm: exit status is 0 if process is killed

[Michael Tokarev]

Control: reassign -1 qemu-system
Control: tag -1 + confirmed upstream
Control: found -1 1:2.1+dfsg-11
Control: found -1 1:2.2+dfsg-5exp
Control: severity -1 minor

10.03.2015 01:07, Benjamin Moody wrote:
> Package: qemu-kvm
> Version: 1.1.2+dfsg-6+deb7u6
> Severity: normal
> 
> Dear Maintainer,
> 
> As the subject line says, if a qemu process (kvm or qemu-system-*) is
> interrupted by a signal (say, by pressing ^C), it still exits with a
> status of 0.

Indeed it does.  What exit code do you suggest to use in this case?

Note this has been this way since the Day One, qemu _always_ did that,
for many years.  So lowering the severity.

Thanks,

/mjt


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

Bug#780023: xbmc: XBMC crash at startup

[Jeremy Guitton]

Hi Balint,

Are you sure hat is a sqlite issue ? From the log I see a segmentation
fault on line 30 :

Program terminated with signal SIGSEGV, Segmentation fault.
#0  brw_meta_fast_clear (brw=brw@entry=0x27d8b68, fb=fb@entry=0x2839b60,
buffers=buffers@entry=2, partial_clear=partial_clear@entry=false) at
../../../../../../../src/mesa/drivers/dri/i965/brw_meta_fast_clear.c:447

To reproduce the bug just install a jessie with defaults options, add xbmc
and lanch it with double-click on the icon. Like that xbmc segfault 2/3 of
the time. No add-ons installed and fresh install, .xbmc in home deleted.

I join to this mail, a log with mesa-dbg and  libsqlite3-0-dbg packages
installed.

A friend have the same issue, with also an intel graphic cards. Perhaps a
bug in mesa ?

Cheers.
Jérémy

2015-03-09 21:06 GMT+01:00 Bálint Réczey :

> Control: tags -1 unreproducible moreinfo
>
> Hi Jeremy,
>
> 2015-03-08 11:57 GMT+01:00 Jeremy Guitton :
> > Package: xbmc
> > Version: 2:13.2+dfsg1-4
> > Severity: important
> >
> > Dear Maintainer,
> >
> > On fresh install of jessie with Gnome Desktop, XBMC crash at startup. I
> join
> > the log file.
> From the logs it looks like the crash happens in SQLite 3.
>
> Thread 11 (Thread 0x7f6f7daaf700 (LWP 4072)):
> #0  0x7f6fb0dd4860 in ?? () from
> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> #1  0x7f6fb0de003b in ?? () from
> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> #2  0x7f6fb0df142c in ?? () from
> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> #3  0x7f6fb0e0c659 in ?? () from
> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> #4  0x7f6fb0e0c85f in ?? () from
> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> #5  0x7f6fb0e0cfc5 in ?? () from
> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> #6  0x7f6fb0e3ef21 in ?? () from
> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> #7  0x7f6fb0e3ff27 in sqlite3_step () from
> /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
> #8  0x00a10062 in dbiplus::SqliteDataset::query
> (this=0x7f6f680863d0, query=0x7f6f6801d4f8 "SELECT sum(watchedcount)
> FROM tvshowview LIMIT 1") at sqlitedataset.cpp:662
> #9  0x009ee8f1 in CDatabase::GetSingleValue
> (this=this@entry=0x7f6f7daaeb60, que
>
> If you can reproduce the issue please install libsqlite3-0-dbg to have
> a better stack trace and attach it.
>
> I tried reproducing the crash, but with no luck. Could you please list
> the steps I need to take?
> Do you have any add-ons installed?
>
> Cheers,
> Balint
>
> >
> >
> >
> > -- System Information:
> > Debian Release: 8.0
> >   APT prefers testing-updates
> >   APT policy: (500, 'testing-updates'), (500, 'testing')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> >
> > Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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: systemd (via /run/systemd/system)
> >
> > Versions of packages xbmc depends on:
> > ii  fonts-dejavu-core  2.34-1
> > ii  fonts-roboto   1:4.4.4r2-6
> > ii  libjs-iscroll  5.1.2+dfsg1-1
> > ii  libjs-jquery   1.7.2+dfsg-3.2
> > ii  mesa-utils 8.2.0-1
> > ii  python-imaging 2.6.1-1
> > pn  python:any 
> > ii  ttf-dejavu-core2.34-1
> > ii  x11-utils  7.7+2
> > ii  xbmc-bin   2:13.2+dfsg1-4
> >
> > xbmc recommends no packages.
> >
> > xbmc suggests no packages.
> >
> > -- no debconf information
>
## XBMC CRASH LOG ###

 SYSTEM INFO 
 Date: lundi 9 mars 2015, 22:08:06 (UTC+0100)
 XBMC Options: 
 Arch: x86_64
 Kernel: Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt4-3 (2015-02-03)
 Release: Debian GNU/Linux 8 (jessie)
## END SYSTEM INFO ##

### STACK TRACE #
=>  Core file: /home/debotux/core (2015-03-09 22:08:06.068501859 +0100)
=
[New LWP 17572]
[New LWP 17583]
[New LWP 17582]
[New LWP 17581]
[New LWP 17588]
[New LWP 17587]
[New LWP 17589]
[New LWP 17580]
[New LWP 17584]
[New LWP 17590]
[New LWP 17591]
[New LWP 17592]
[New LWP 17593]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/xbmc/xbmc.bin'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  brw_meta_fast_clear (brw=brw@entry=0x27d8b68, fb=fb@entry=0x2839b60, buffers=buffers@entry=2, partial_clear=partial_clear@entry=false) at ../../../../../../../src/mesa/drivers/dri/i965/brw_meta_fast_clear.c:447

Thread 13 (Thread 0x7ffcdb7fe700 (LWP 17593)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x00f5feb2 in CJobManager::GetNextJob(CJobWorker const*) ()
#2  0x00f6081a in CJobWorker::Process() ()
#3  0x0132d35f in CThread::Action() ()
#4  0x0132d619 in CThread::staticThread(void*) ()
#5  0x7ffd37e2e0a4 in start_thr

Bug#772890: Jessie will ship with broken livestreamer

[Stefan Breunig]

Hi Onur,

I don't plan to bring an updated version of livestreamer to Debian
stable (jessie) or to provide backports.

Among other reasons, the non-latest version of livestreamer will always
be broken for some service or another. This roots in the nature of how
livestreamer interacts with the various services. Most likely every
livestreamer update would have to be made available in jessie. I don’t
think this is feasible.

Instead, please install livestreamer from testing (unstable), as long as
the other dependencies can be satisfied from stable.

Cheers,
Stefan


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

Bug#780160: CVE-2014-9639

[Moritz Muehlenhoff]

Package: opus-tools
Version: 0.1.9-1
Severity: important
Tags: security

Hi,
CVE-2014-9638 and CVE-2014-9639 for vorbis-tools also affect opus-tools,
please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776086
for details and reproducers.

Cheers,
Moritz


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

Bug#780159: qemu-kvm: exit status is 0 if process is killed

[Benjamin Moody]

Package: qemu-kvm
Version: 1.1.2+dfsg-6+deb7u6
Severity: normal

Dear Maintainer,

As the subject line says, if a qemu process (kvm or qemu-system-*) is
interrupted by a signal (say, by pressing ^C), it still exits with a
status of 0.

Example:

  $ kvm
  ^Cqemu: terminating on signal 2
  $ echo $?
  0

This is extremely annoying when trying to write robust scripts that
invoke qemu - there is no way for the script to know whether the guest
system powered off successfully, or the process was interrupted for some
reason.

Benjamin


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

Bug#780158: base: Fixed width 6x13 font does not display correctly

[Kingsley Tart]

Package: base
Severity: normal

Dear Maintainer,

Fixed [Misc] and Fixed [Trad] font Medium Semi-Condensed displays as the wrong
font when selecting font size 10.

I've re-installed Debian several times and each time this bug crops up. How I
reproduced it this time:

* install base system, with default debian desktop environment
* install xfonts-traditional-1.6 package
* make appropriate symlink changes to enable bitmap fonts
* logout then back in to restart X

then:
* go into gedit / Edit / Preferences / Fonts & Colours
* select editir font Fixed Medium Semi-Condensed size 10
* save changes
* font is all wrong in editor (shows a completely different font - see links to
Kate screenshots lower in this message)

A similar thing happens in Kate and Kwrite (which I use all of the time),
except that it appears to work at first, but if I then close Kate and re-open,
it's all messed up again.

After freshly setting it in Kate, this is how it looks (all OK):
http://quitebig.com/debian-font-problem/kate-nice.png

But if I close Kate and re-open it, it looks like this:
http://quitebig.com/debian-font-problem/kate-nasty.png

With Terminal (this is minor):
* open terminal and go to preferences for editing default profile, tab
"General"
* select Fixed Medium Semi-Condensed 10 point then click "Select" in dialog
bottom right
* font shows incorrectly in the "Font" select box but works OK in the terminal
itself

I also tried James Knoble's xfonts-jmk-3.0.19 package, but hit upon the same
problem.

I tried setting up the fonts before adding the Nvidia driver on a fresh OS
installation, after adding the Nvidia driver, adding KDE4, adding XFCE, but
whatever I did, nothing fixed it.

The problem doesn't seem to happen for other sizes of Fixed Medium Semi-
Condensed, or does it happen with the bold version of the font (even at 10pt).

Every time the font displays incorrectly, it shows the same incorrect font.

This might only seem like a minor bug, but for me it's a deal-breaker. I use
terminal windows, Kate and Kwrite all day every day, and I'm still using an old
setup running KDE 3.5 so that I can keep this font, as it's the best
combination I've found of compactness and readability. I'd much prefer to use
my Debian installation but until I can get this font to display correctly,
that's not an option.

I'm keeping my fingers crossed that this is a quick and easy fix :)



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

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


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

Bug#780093: [Pkg-libvirt-maintainers] Bug#780093: libvirt: error: unsupported configuration: QEMU 2.1.2 is too new for help parsing

[Guido Günther]

On Mon, Mar 09, 2015 at 10:05:02AM +0100, Thorsten Glaser wrote:
> Package: libvirt-clients
> Version: 1.2.9-9
> Severity: grave
> Justification: renders package unusable
> 
> tglase@tglase:~ $ virsh -c qemu:///system start MirBSD
> error: Failed to start domain MirBSD
> error: unsupported configuration: QEMU 2.1.2 is too new for help parsing

That is because it should use the more reliable QMP probing. Are you
wrapping qemu/kvm by a skript or something?

Does

virsh capabilities

show the same error? Anything in the daemon logs (if not please try
increasing the debug level).
Cheers,
 -- Guido


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

Bug#780157: ITP: baculum -- Baculum WebGUI tool for Bacula Community program

[Marcin Haba]

Package: wnpp
Severity: wishlist
Owner: Marcin Haba 

* Package name: baculum
  Version : 7.0+git20150208
  Upstream Author : Marcin Haba 
* URL : http://www.bacula.org/
* License : AGPLv3
  Programming Lang: PHP
  Description : Baculum WebGUI tool for Bacula Community program

Baculum is web based tool to manage, administrate and monitor Bacula
services.From server side Baculum is written in PHP and works basing on
PRADO Framework. Baculum interface enables e.g. to run Bacula backup and
restore actions, take access to Bacula console via web, watch backup
graphs and others.

 - why is this package useful/relevant?

This package allows access to Bacula basic administrative tasks via web
intreface.

 - is it a dependency for another package?

Yes, it is. Baculum uses external toolset - PRADO Framework.
Additionally Baculum uses external JavaScript libraries.

 - do you use it?
Yes, I do.

 - if there are other packages providing similar functionality, how does
it compare?

Yes, there are other packages. I do not know how to compare them because
I do not use these tools and in most part I have not installed them.

 - how do you plan to maintain it?
After each Bacula and Baculum release I plan to build Baculum deb and
rpm packages for community. From deb packages I am going to build also
for Debian.

 - inside a packaging team?
I am not sure about packaging team. I have never been packages maintainer.

 - are you looking for co-maintainers?
No, I am not.

 - do you need a sponsor?
No. I do not.


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

Bug#780155: ITP: baculum -- Baculum WebGUI tool for Bacula Community program

[Cameron Norman]

On Mon, Mar 9, 2015 at 2:13 PM, gani  wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Marcin Haba 
>
> * Package name: baculum
>   Version : 7.0+git20150208
>   Upstream Author : Marcin Haba 
> * URL : http://www.bacula.org/
> * License : AGPLv3
>   Programming Lang: PHP
>   Description : Baculum WebGUI tool for Bacula Community program

I see you linked to the bacula.org homepage for this package. Am I
correct in saying that what you are packaging can be found here:

http://www.bacula.org/git/cgit.cgi/bacula/tree/gui

if so there seems to already be packaging (outside of Debian) that
uses the bweb name for the package.
If not, would you mind clarifying which GUI tool for Bacula this is
with a link to a homepage and / or git repo?

>  - is it a dependency for another package?
>
> Yes, it is. Baculum uses external toolset - PRADO Framework.
> Additionally Baculum uses external JavaScript libraries.

Actually those are the dependencies of this project. The question is
if this package is a dependency of another package (in the same way
PRADO is a dependency of this package).

>  - how do you plan to maintain it?
> After each Bacula and Baculum release I plan to build Baculum deb and rpm
> packages for community. From deb packages I am going to build also for Debian.
>
>  - inside a packaging team?
> I am not sure about packaging team. I have never been packages maintainer.

You should probably maintain it inside the Debian Bacula Team. This
will make it easier to find a sponsor (which I will get to) and help
if need be.

>  - do you need a sponsor?
> No. I do not.

You mentioned that you have never made Debian packages before. Thus,
you are not a Debian developer and need a debian developer to review
and then upload the packages for you. This is what a sponsor is. You
need a sponsor.

--
Cameron Norman


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

Bug#780156: tinyxml2: FTBFS with noopt: DEBIAN/symbols doesn't match completely debian/libtinyxml2-2.symbols

[Jakub Wilk]

Source: tinyxml2
Version: 2.2.0-1

I wanted to rebuild tinyxml2 with DEB_BUILD_OPTIONS=noopt, but the 
package failed to build:

| dh_makeshlibs -- -c4
| dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
| dpkg-gensymbols: warning: debian/libtinyxml2-2/DEBIAN/symbols doesn't match 
completely debian/libtinyxml2-2.symbols
| --- debian/libtinyxml2-2.symbols (libtinyxml2-2_2.2.0-1_i386)
| +++ dpkg-gensymbolsjXw4_X 2015-03-09 21:36:55.563797001 +
| @@ -1,4 +1,29 @@
|  libtinyxml2.so.2 libtinyxml2-2 #MINVER#
| + _ZN8tinyxml210XMLElement12SetAttributeEPKcS2_@Base 2.2.0-1
| + _ZN8tinyxml210XMLElement7SetNameEPKcb@Base 2.2.0-1
| + _ZN8tinyxml210XMLVisitorC1Ev@Base 2.2.0-1
| + _ZN8tinyxml210XMLVisitorC2Ev@Base 2.2.0-1
| + _ZN8tinyxml212XMLAttributeC1Ev@Base 2.2.0-1
| + _ZN8tinyxml212XMLAttributeC2Ev@Base 2.2.0-1
| + _ZN8tinyxml27XMLNode10FirstChildEv@Base 2.2.0-1
| + _ZN8tinyxml27XMLNode11GetDocumentEv@Base 2.2.0-1
| + _ZN8tinyxml27XMLText8SetCDataEb@Base 2.2.0-1
| + _ZN8tinyxml27XMLTextC1EPNS_11XMLDocumentE@Base 2.2.0-1
| + _ZN8tinyxml27XMLTextC2EPNS_11XMLDocumentE@Base 2.2.0-1
| + _ZNK8tinyxml210XMLElement11ClosingTypeEv@Base 2.2.0-1
| + _ZNK8tinyxml210XMLElement14FirstAttributeEv@Base 2.2.0-1
| + _ZNK8tinyxml210XMLElement4NameEv@Base 2.2.0-1
| + _ZNK8tinyxml211XMLDocument14WhitespaceModeEv@Base 2.2.0-1
| + _ZNK8tinyxml211XMLDocument15ProcessEntitiesEv@Base 2.2.0-1
| + _ZNK8tinyxml211XMLDocument5ErrorEv@Base 2.2.0-1
| + _ZNK8tinyxml211XMLDocument6HasBOMEv@Base 2.2.0-1
| + _ZNK8tinyxml212XMLAttribute4NextEv@Base 2.2.0-1
| + _ZNK8tinyxml27XMLNode10FirstChildEv@Base 2.2.0-1
| + _ZNK8tinyxml27XMLNode11NextSiblingEv@Base 2.2.0-1
| + _ZNK8tinyxml27XMLNode6ParentEv@Base 2.2.0-1
| + _ZNK8tinyxml27XMLText5CDataEv@Base 2.2.0-1
| + _ZdlPvS_@Base 2.2.0-1
| + _ZnwjPv@Base 2.2.0-1
|   (c++)"tinyxml2::XMLAttribute::Name() const@Base" 2.0.2
|   (c++)"tinyxml2::XMLAttribute::ParseDeep(char*, bool)@Base" 2.0.2
|   (c++)"tinyxml2::XMLAttribute::QueryBoolValue(bool*) const@Base" 2.0.2
| dh_makeshlibs: failing due to earlier errors
| make[1]: *** [override_dh_makeshlibs] Error 2
| debian/rules:21: recipe for target 'override_dh_makeshlibs' failed

--
Jakub Wilk


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

Bug#780154: unblock: oss4/4.2-build2010-2

[Samuel Thibault]

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

Please unblock package oss4

A security issue was filed against the usb drivers contained in the oss4
package, and was pung again late January as #775662, but maintainers of
that part of the package didn't seem to have discussed with upstream
about it.  Considering how many issues there are in there, I tend not to
trust the module at all.  In upload oss4/4.2-build2010-2, I have thus
just disabled the usb module, see attached debdiff.

unblock oss4/4.2-build2010-2

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

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

-- 
Samuel
  mr  -  remove the home of correct users who accidentally enter mr
instead of rm
diff -Nru oss4-4.2-build2010/debian/changelog 
oss4-4.2-build2010/debian/changelog
--- oss4-4.2-build2010/debian/changelog 2014-11-22 16:22:36.0 +0100
+++ oss4-4.2-build2010/debian/changelog 2015-03-09 20:27:33.0 +0100
@@ -1,3 +1,10 @@
+oss4 (4.2-build2010-2) unstable; urgency=medium
+
+  * Disable USB drivers, which insufficiently validate USB device descriptors.
+(Closes: #775662)
+
+ -- Samuel Thibault   Mon, 09 Mar 2015 20:16:31 +0100
+
 oss4 (4.2-build2010-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru oss4-4.2-build2010/debian/oss4-dkms.dkms.in 
oss4-4.2-build2010/debian/oss4-dkms.dkms.in
--- oss4-4.2-build2010/debian/oss4-dkms.dkms.in 2014-10-23 22:47:36.0 
+0200
+++ oss4-4.2-build2010/debian/oss4-dkms.dkms.in 2015-03-09 20:07:55.0 
+0100
@@ -1,7 +1,7 @@
 PACKAGE_NAME="oss4"
 PACKAGE_VERSION="_VERSION_"
 BUILT_MODULE_NAME[0]="osscore"
-BUILT_MODULE_NAME[1]="oss_usb"
+BUILT_MODULE_NAME[1]="oss_sbpci"
 BUILT_MODULE_NAME[2]="oss_sbxfi"
 BUILT_MODULE_NAME[3]="oss_via823x"
 BUILT_MODULE_NAME[4]="oss_geode"
@@ -31,7 +31,8 @@
 BUILT_MODULE_NAME[28]="oss_audiopci"
 BUILT_MODULE_NAME[29]="oss_ymf7xx"
 BUILT_MODULE_NAME[30]="oss_cmpci"
-BUILT_MODULE_NAME[31]="oss_sbpci"
+# This module insufficiently validates USB device descriptors, thus disabled.
+#BUILT_MODULE_NAME[31]="oss_usb"
 BUILT_MODULE_LOCATION[0]="core/"
 BUILT_MODULE_LOCATION[1]="drivers/"
 BUILT_MODULE_LOCATION[2]="drivers/"
@@ -63,7 +64,7 @@
 BUILT_MODULE_LOCATION[28]="drivers/"
 BUILT_MODULE_LOCATION[29]="drivers/"
 BUILT_MODULE_LOCATION[30]="drivers/"
-BUILT_MODULE_LOCATION[31]="drivers/"
+#BUILT_MODULE_LOCATION[31]="drivers/"
 DEST_MODULE_LOCATION[0]="/updates/dkms/"
 DEST_MODULE_LOCATION[1]="/updates/dkms/"
 DEST_MODULE_LOCATION[2]="/updates/dkms/"
@@ -95,7 +96,7 @@
 DEST_MODULE_LOCATION[28]="/updates/dkms/"
 DEST_MODULE_LOCATION[29]="/updates/dkms/"
 DEST_MODULE_LOCATION[30]="/updates/dkms/"
-DEST_MODULE_LOCATION[31]="/updates/dkms/"
+#DEST_MODULE_LOCATION[31]="/updates/dkms/"
 AUTOINSTALL=yes
 MAKE[0]="make -C ${kernel_source_dir} 
SUBDIRS=${dkms_tree}/${PACKAGE_NAME}/${PACKAGE_VERSION}/build/core modules && \
  make -C ${dkms_tree}/${PACKAGE_NAME}/${PACKAGE_VERSION}/build/drivers 
osscore_symbols.inc && \

Bug#779656:

[Chris Bainbridge]

0020-Fix-Savannah-bug-43547.-CVE-2014-9671.patch is buggy, see bug #780143

Bug#737370: mkdir: directories created with weird mode when -p is used [FIXED in 8.22]

[Frank Lin PIAT]

On 2 Feb 2014, Bob Proulx said
> I cannot recreate the above behavior.
> [..]
> If I set umask to a more restrictive umask then I can.
> 
>   $ umask 022
>   $ rm -rf /tmp/a
>   $ mkdir /tmp/a
>   $ cd /tmp/a
>   $ setfacl -m d:g::rwx .
>   $ mkdir b 
>   $ mkdir -p c
>   $ ls -log
>   total 0
>   drwxrwxr-x+ 2 40 Feb  2 11:31 b
>   drwxr-xr-x+ 2 40 Feb  2 11:31 c

On Jessie, the result is:
drwxrwxr-x+ 2 4096 Mar  9 22:17 b
drwxrwxr-x+ 2 4096 Mar  9 22:17 c

The bug was fixed upstream by Paul Eggert, in version 8.22
http://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=e7198a67b8dd7f23925dfa40b7a90342e185f729
 

Regards

Thanks

Frank lin Piat


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

Bug#780155: ITP: baculum -- Baculum WebGUI tool for Bacula Community program

[gani]

Package: wnpp
Severity: wishlist
Owner: Marcin Haba 

* Package name: baculum
  Version : 7.0+git20150208
  Upstream Author : Marcin Haba 
* URL : http://www.bacula.org/
* License : AGPLv3
  Programming Lang: PHP
  Description : Baculum WebGUI tool for Bacula Community program

Baculum is web based tool to manage, administrate and monitor Bacula services.
>From server side Baculum is written in PHP and works basing on PRADO Framework.
Baculum interface enables e.g. to run Bacula backup and restore actions, take
access to Bacula console via web, watch backup graphs and others.

 - why is this package useful/relevant?

This package allows access to Bacula basic administrative tasks via web 
intreface.

 - is it a dependency for another package?

Yes, it is. Baculum uses external toolset - PRADO Framework.
Additionally Baculum uses external JavaScript libraries.

 - do you use it?
Yes, I do.

 - if there are other packages providing similar functionality, how does it 
compare?

Yes, there are other packages. I do not know how to compare them because I do 
not
use these tools and in most part I have not installed them.

 - how do you plan to maintain it?
After each Bacula and Baculum release I plan to build Baculum deb and rpm
packages for community. From deb packages I am going to build also for Debian.

 - inside a packaging team?
I am not sure about packaging team. I have never been packages maintainer.

 - are you looking for co-maintainers?
No, I am not.

 - do you need a sponsor?
No. I do not.


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

Bug#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5

[Simon McVittie]

On 09/03/15 20:57, Julien Cristau wrote:
> On Thu, Feb 26, 2015 at 08:54:10 +, Simon McVittie wrote:
>> Context for Mesa maintainers: #775235 is that gnome-shell crashes in
>> an i386 VM with its default choice of emulated CPU, with
>> "LLVM ERROR: Do not know how to split the result of this operator!".
...
>> The merged bug #770130 is that gnome-shell crashes on an unknown i386
>> [...] with
>> "Cogl-ERROR **: Failed to create texture 2d due to size/format constraints".
>>
>> The other merged bug #776911 is that gnome-shell crashes on an
>> unknown i386 with "Cogl-ERROR **: Failed to create texture 2d due to
>> size/format constraints"; that looks like the same thing as #770130.
>
> Sounds like there are at least two different issues that should be
> split...

Perhaps. Michael, could you elaborate on your reasoning for believing
that #775235 (reproducible, in a VM, presumably with llvmpipe) is the
same bug as #770130 (on real hardware, seems to be with i915-family
graphics)?

#776911 (on real hardware, appears to be with i915-family graphics)
looks quite a lot like #770130: both involve Intel graphics chips
encountering a "pipe A underrun", and GNOME Shell crashing with
"Cogl-ERROR **: Failed to create texture 2d due to size/format constraints".

S


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

Bug#780143:

[Chris Bainbridge]

Upstream: "The problem you are describing in this bug report has already
been fixed in version 2.5.5"

Bug#780133: DH_VERBOSE under dh command

[Tianon Gravi]

On Mon, Mar 09, 2015 at 05:40:50PM +0100, Niels Thykier wrote:
> It seems to be documented under "ENVIRONMENT", which I thought would
> imply that it is an environment variable and not a Makefile variable?
> 
> I suppose we can stress the fact a bit harder.

I'd like to take a stab at this one, if you don't mind. :)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4


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

Bug#780153: libtinyxml2-2: null pointer dereference

[Jakub Wilk]

Package: libtinyxml2-2
Version: 2.2.0-1
Usertags: afl

TinyXML-2 crashes when parsing the attached file:

$ make prettyprintxml CXXFLAGS="-g -O2 -Wall" LDFLAGS=-ltinyxml2
g++ -g -O2 -Wall  -ltinyxml2  prettyprintxml.cc   -o prettyprintxml
$ ./prettyprintxml crash.xml
Segmentation fault


Valgrind says it's a null pointer dereference:

==2570== Invalid read of size 1
==2570==at 0x4056C53: tinyxml2::StrPair::GetStr() (tinyxml2.cpp:175)
==2570==by 0x405C5AD: tinyxml2::XMLPrinter::Visit(tinyxml2::XMLText const&) 
(tinyxml2.cpp:2219)
==2570==by 0x4056450: tinyxml2::XMLText::Accept(tinyxml2::XMLVisitor*) 
const (tinyxml2.cpp:920)
==2570==by 0x4056418: tinyxml2::XMLDocument::Accept(tinyxml2::XMLVisitor*) 
const (tinyxml2.cpp:554)
==2570==by 0x405BAB6: tinyxml2::XMLDocument::Print(tinyxml2::XMLPrinter*) 
const (tinyxml2.cpp:1830)
==2570==by 0x8048C6C: main (prettyprintxml.cc:19)
==2570==  Address 0x0 is not stack'd, malloc'd or (recently) free'd


This bug was found using American fuzzy lop:
http://lcamtuf.coredump.cx/afl/
(available in Debian experimental)

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

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

Versions of packages libtinyxml2-2 depends on:
ii  libc6  2.19-15
ii  libgcc11:5-20150307-1
ii  libstdc++6 5-20150307-1
ii  multiarch-support  2.19-15

--
Jakub Wilk


crash.xml
Description: XML document
#include 


#include 


using namespace tinyxml2;


int main(int argc, char ** argv)
{
	if (argc != 2) {
		fprintf(stderr, "Usage: %s \n", argv[0]);
		return 1;
	}
	XMLDocument* doc = new XMLDocument();
	if (doc->LoadFile(argv[1]) != XML_NO_ERROR) {
		doc->PrintError();
		return 1;
	}
	XMLPrinter printer;
	doc->Print(&printer);
	puts(printer.CStr());
	return 0;
}

Bug#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5

[Simon McVittie]

On 09/03/15 19:09, kytv wrote:
> The host system has an AMD FX-6100 CPU.
...
> These did not work without the patch and they're still not working.
> 
> * SandyBridge
> * Broadwell
> * Haswell
> * Westmere
> * Nehalem
> * Penryn

Those are all rather modern Intel CPUs. It would not surprise me at all
if they had CPU features that are not supported by your host system: AMD
CPUs usually support the latest version of AMD-originated features and a
somewhat older version of Intel-originated features, and vice versa.

You can check via /proc/cpuinfo on the host and the VM. For instance,
here's the Sandy Bridge CPU on my laptop:

flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology nonstop_tsc
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2
ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer
aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow
vnmi flexpriority ept vpid

If your host CPU is missing any of those features, then emulating a
SandyBridge CPU in your VM is probably an invalid configuration.

S


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

Bug#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5

[Julien Cristau]

On Thu, Feb 26, 2015 at 08:54:10 +, Simon McVittie wrote:

> Adding mesa@packages to Cc since I suspect #775235 needs reassigning
> to Mesa, perhaps along with its merged bugs #770130, #776911.
> 
> Context for Mesa maintainers: #775235 is that gnome-shell crashes in
> an i386 VM with its default choice of emulated CPU, with
> "LLVM ERROR: Do not know how to split the result of this operator!".
> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775235#10 for full
> backtrace.
> 
> The merged bug #770130 is that gnome-shell crashes on an unknown i386
> (probably relatively old, since it has 82830M/MG integrated graphics,
> which Wikipedia says is a Pentium III-M chipset) with
> "Cogl-ERROR **: Failed to create texture 2d due to size/format constraints".
> Oddly, this only happens for non-power-of-two textures in the gnome-shell
> run by the actual user, not by the gnome-shell used for the gdm login
> prompt (even though both use non-power-of-two textures). Michael Gilbert
> merged this with #775235 and #776911 without comment; I'm not sure of
> the reasoning for believing that #775235 and #770130 is the same thing.
> 
> The other merged bug #776911 is that gnome-shell crashes on an
> unknown i386 with "Cogl-ERROR **: Failed to create texture 2d due to
> size/format constraints"; that looks like the same thing as #770130.
> 
Sounds like there are at least two different issues that should be
split...

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5

[kytv]

On Sun,  8 Mar 2015 20:02:00 + (UTC)
intrigeri  wrote:

> I've rebuilt the mesa package with the patch from
> https://freedesktop.org/patch/34445/, and it fixes things for me, at
> least with `-cpu qemu32'. I've asked the other Tails developer (Cc'd),
> who is also experiencing this bug, to try and reproduce my results.

The patch to mesa is definitely an improvement but some qemu CPU
types still fail. The host system has an AMD FX-6100 CPU.
.
---

These did not work without the patch and they're still not working.

* SandyBridge
* Broadwell
* Haswell
* Westmere
* Nehalem
* Penryn


These worked previously and still work after the patch.
* host
* kvm64
* Opteron_G1
* Opteron_G2
* Opteron_G3
* Opteron_G4
* Opteron_G5
* phenom

These failed previously but they work with the patched mesa.
* core2duo
* coreduo
* Conroe
* n270
* qemu32

I'll attach logs later.


pgp1_pxlMk_3U.pgp
Description: OpenPGP digital signature

Bug#779813: installation-reports: KMS results in blank screen after installation on Acer eM350

[Michael Fincham]

On Thu, 5 Mar 2015 04:18:50 +0100, Cyril Brulebois wrote:
> I'd recommend filing a bug report against the linux kernel.

No need, I updated to 3.16.7-ckt7-1 today and the workaround is no longer 
required :)

Cheers,
-- 
Michael


pgp2GRGPVvPWg.pgp
Description: PGP signature

Bug#780151: debian-installer: Buggy Built-Using generation on an arch-dep manner

[Cyril Brulebois]

Source: debian-installer
Severity: important

Built-Using was missing some items, see #696418 & #700026, so a patch
was pushed to try and deal with it:

commit b4411bfb56601cf6a7366a1bec065b56b91f1a42
Author: Cyril Brulebois 
Date:   Mon Mar 3 00:00:46 2014 +0100

Extend write-built-using to also generate the ${extra:Built-Using} 
substvar.

This makes it possible to track packages mentioned in the EXTRA_PACKAGES
variable (currently set to "bf-utf-source syslinux"). Thanks to Ansgar
Burchardt for the reports (Closes: #696418, #700026).

Note: Unknown packages are ignored, so architecture-specific packages
shouldn't be a problem.

Acked-by: Ian Campbell 
Signed-off-by: Cyril Brulebois 

I lost track of Karsten's objection here:
  https://lists.debian.org/debian-boot/2015/02/msg00012.html

so here's a bug report to try and get that fixed instead of just
reverting the said commit. (Funny how things that shouldn't be an issue
turn out to be one…)

It's indeed sad that I only tested the case of an entirely inexistent
package and didn't think about the funny not-available-on-all-archs
packages…

Maybe we could iterate over the packages mentioned there, calling
dpkg-checkbuilddeps with its -d flag to see if the relevant packages are
relevant? Another idea might be to use Dpkg::Deps to figure out whether
some package is relevant for the current architecture? Any other ideas?

I'd happily take patches here, as I'm busy with other bugs.

Mraw,
KiBi.


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

Bug#776744: [Pkg-utopia-maintainers] Bug#776744: Bug#776744: policykit-1: use current libmozjs-24.0-dev | libmozjs185-dev

[Michael Biebl]

Am 09.03.2015 um 21:43 schrieb Michael Biebl:
> Am 09.03.2015 um 21:35 schrieb Alf Gaida:

>> - libmozjs-17.0-dev,
>> + libmozjs-24.0-dev|libmozjs185-dev,
> 
> Changing the build-depends is not sufficient.
> Someone will actually need to port the source code to mozjs 24.

That aside, the correct Build-Depends would be libmozjs-24-dev



-- 
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#775877: gnome-session: No mouse pointer after login

[Simon McVittie]

On 06/03/15 10:00, Simon McVittie wrote:
> On Tue, 20 Jan 2015 at 21:43:09 -0500, Aron Podrigal wrote:
>>  Jan 20 16:46:18 jessie gnome-session[1888]:
>>  
>> GLib-GIO:ERROR:/tmp/buildd/glib2.0-2.42.1/./gio/gdbusconnection.c:4231:invoke_set_property_in_idle_cb:
>>  assertion failed: (error != NULL)
> 
> This seems likely to be the problem: gnome-settings-daemon crashed with
> an assertion failure.

gdbusconnection.c:4231 is the last of the lines I've quoted here:

  if (!data->vtable->set_property (data->connection,
   g_dbus_message_get_sender (data->message),
   g_dbus_message_get_path (data->message),
   data->interface_info->name,
   data->property_name,
   value,
   &error,
   data->user_data))
{
  gchar *dbus_error_name;
  g_assert (error != NULL);

So the bug here is that something, somewhere in the
gnome-settings-daemon process, has a set_property() callback
that fails without correctly setting the error.

Searching the gnome-settings-daemon source code, the only obvious
possibility is in the power plugin. Aron, please try this and see
whether it works better for you:

https://people.debian.org/~smcv/gnome-settings-daemon_3.14.2-2+smcv1_amd64.deb

Regards,
S


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

Bug#776744: [Pkg-utopia-maintainers] Bug#776744: policykit-1: use current libmozjs-24.0-dev | libmozjs185-dev

[Michael Biebl]

Am 09.03.2015 um 21:35 schrieb Alf Gaida:
> Package: policykit-1
> Followup-For: Bug #776744
> 
> Dear Maintainer,
> 
> please use currend build dependencies - maybe the fallback to libmozjs185-dev 
> might be a good idea.
> 
> diff --git a/debian/control b/debian/control
> index 482f3a4..89ba49f 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -10,7 +10,7 @@ Build-Depends: debhelper (>= 9),
>   libexpat1-dev,
>   libpam0g-dev,
>   libselinux1-dev [linux-any],
> - libmozjs-17.0-dev,
> + libmozjs-24.0-dev|libmozjs185-dev,

Changing the build-depends is not sufficient.
Someone will actually need to port the source code to mozjs 24.


-- 
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#780022: x11-xkb-utils: xkbcomp - BUG: triggered 'if (axnum >= dev->valuator->numAxes)'

[Julien Cristau]

On Mon, Mar  9, 2015 at 08:50:12 +0100, Niels Thykier wrote:

> On 2015-03-09 08:01, Julien Cristau wrote:
> > On Sun, Mar  8, 2015 at 21:42:25 +0100, Niels Thykier wrote:
> > 
> >> [...]
> >>
> > Please provide the full X log, not xdm :)
> > 
> > Cheers,
> > Julien
> > 
> 
> Attached.
> 
> Just before the "BUG" appears (twice), X seems to be configuring the
> devices called "Jabra LINK 360" and "Jabra EVOLVE 65".  In both cases,
> it seems to conclude these devices have "mouse-like" features (e.g.
> mouse buttons and x/y-axes).
>   However, the "Jabra EVOLVE 65" is a wireless set of headphones.  I am
> guessing the "Jabra LINK 360" is the small USB dongle for said headphones.
> 
Thanks.  Can you build the evdev driver from
git://anongit.freedesktop.org/xorg/driver/xf86-input-evdev and, if the
BUG still happens, file a report upstream at
https://bugs.freedesktop.org/enter_bug.cgi?product=xorg&component=Input/evdev&version=git

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#776744: policykit-1: use current libmozjs-24.0-dev | libmozjs185-dev

[Alf Gaida]

Package: policykit-1
Followup-For: Bug #776744

Dear Maintainer,

please use currend build dependencies - maybe the fallback to libmozjs185-dev 
might be a good idea.

diff --git a/debian/control b/debian/control
index 482f3a4..89ba49f 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,7 @@ Build-Depends: debhelper (>= 9),
  libexpat1-dev,
  libpam0g-dev,
  libselinux1-dev [linux-any],
- libmozjs-17.0-dev,
+ libmozjs-24.0-dev|libmozjs185-dev,
  gtk-doc-tools,
  xsltproc,
  libgirepository1.0-dev (>= 0.9.12),

cheers Alf


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

Kernel: Linux 3.18-3-ck-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages policykit-1 depends on:
ii  adduser3.113+nmu3
ii  dbus   1.8.16-1
ii  libc6  2.19-15
ii  libexpat1  2.1.0-6+b3
ii  libglib2.0-0   2.42.1-1
ii  libmozjs185-1.01.8.5-1.0.0+dfsg-4.3
ii  libnspr4   2:4.10.7-1
ii  libnspr4-0d2:4.10.7-1
ii  libpam-systemd 219-4
ii  libpam0g   1.1.8-3.1
ii  libpolkit-agent-1-00.112-4.1
ii  libpolkit-gobject-1-0  0.112-4.1
ii  libsystemd0219-4

policykit-1 recommends no packages.

policykit-1 suggests no packages.

-- Configuration Files:
/etc/polkit-1/rules.d/40-debian-sudo.rules [Errno 13] Keine Berechtigung: 
u'/etc/polkit-1/rules.d/40-debian-sudo.rules'
/etc/polkit-1/rules.d/50-default.rules [Errno 13] Keine Berechtigung: 
u'/etc/polkit-1/rules.d/50-default.rules'

-- no debconf information


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

Bug#780150: RM: python-cream/0.5.3-1

[Mike Gabriel]

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

Please remove python-cream from Debian jessie, it is weakly maintained
upstream and not appropriate for jessie.

light+love,
Mike

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

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


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

Bug#780149: libtinyxml2.6.2: hangs forever

[Jakub Wilk]

Package: libtinyxml2.6.2
Version: 2.6.2-2
Usertags: afl

TinyXML hangs forever (or at least for one minute :-P) when trying to 
load the attached file:


$ make prettyprintxml CXXFLAGS="-g -O2 -Wall" LDFLAGS=-ltinyxml
g++ -g -O2 -Wall  -ltinyxml  prettyprintxml.cc   -o prettyprintxml
$ ./prettyprintxml hang.xml
[nothing happens...]


This bug was found using American fuzzy lop:
http://lcamtuf.coredump.cx/afl/
(available in Debian experimental)

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

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

Versions of packages libtinyxml2.6.2:i386 depends on:
ii  libc6  2.19-15
ii  libgcc11:5-20150307-1
ii  libstdc++6 5-20150307-1
ii  multiarch-support  2.19-15

--
Jakub Wilk
#include 

#define TIXML_USE_STL 1
#include 

int main(int argc, char ** argv)
{
	if (argc != 2) {
		fprintf(stderr, "Usage: %s \n", argv[0]);
		return 1;
	}
	TiXmlDocument doc(argv[1]);
	if (!doc.LoadFile()) {
		fprintf(stderr, "invalid XML\n");
		return 1;
	}
	TiXmlPrinter printer;
	doc.Accept(&printer);
	puts(printer.CStr());
	return 0;
}


hang.xml
Description: XML document

Bug#778332: RM: oss4/4.2-build2010-1.1

[Julien Cristau]

On Mon, Mar  9, 2015 at 20:29:43 +0100, Moritz Mühlenhoff wrote:

> On Wed, Mar 04, 2015 at 09:46:20AM +0100, Ivo De Decker wrote:
> > Hi,
> > 
> > On Fri, Feb 13, 2015 at 05:52:36PM +0100, Moritz Muehlenhoff wrote:
> > > please remove oss4 from jessie. There's been no maintainer
> > > followup since a month (plus no action back then we Ben
> > > initially reported it to the maintainers privately).
> > 
> > Removal hint added.
> 
> I tried to check why this hasn't been removed, but I don't
> understand why. The simulated removal "dak rm -s testing"
> run show many dependencies on ALSA, e.g.
> 
As long as britney takes kfreebsd into account, the removal hint won't
work.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#779254: please confirm this bug with zoneminder from Debian

[Holger Levsen]

Hi John,

On Montag, 9. März 2015, John Crout wrote:
> It's in the current Debian Mint.
> This help?

not really, no.


cheers,
Holger


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

Bug#780148: RM: cream-melange/0.5.2-2

[Mike Gabriel]

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

Please remove cream-melange from Debian jessie, it is weakly maintained
upstream and the cream-melange-widgets package has not yet been package
for Debian, thus Cream Melange is still incomplete.

Thus, cream-melange is not appropriate for Debian jessie.


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

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


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

Bug#780146: not appropriate for jessie

[Mike Gabriel]

Package: cream-melange
Version: 0.5.2-2
Severity: serious


The cream-melange package from the Cream Melange project is currently  
not suitable for Debian jessie, thus marking it with a RC bug.


No further action has to be taken for now, except waiting for its  
automatic removal from jessie.


Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgpZQZBVRawcK.pgp
Description: Digitale PGP-Signatur

Bug#780145: not appropriate for jessie

[Mike Gabriel]

Package: python-cream
Severity: serious
Version: 0.5.3-1

The python-cream package from the Cream Melange project is currently  
not suitable for Debian jessie, thus marking it with a RC bug.


No further action has to be taken for now, except waiting for its  
automatic removal from jessie.


Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgpkxWcNc9w18.pgp
Description: Digitale PGP-Signatur

Bug#780147: tinyxmlparser.cpp:543: static bool TiXmlBase::StringEqual(const char*, const char*, bool, TiXmlEncoding): Assertion `0' failed.

[Jakub Wilk]

Package: libtinyxml2.6.2
Version: 2.6.2-2
Usertags: afl

TinyXml crashes with failed assertion while trying to parse the attached 
file:


$ make prettyprintxml CXXFLAGS="-g -O2 -Wall" LDFLAGS=-ltinyxml
g++ -g -O2 -Wall  -ltinyxml  prettyprintxml.cc   -o prettyprintxml
$ ./prettyprintxml badxml.xml
prettyprintxml: tinyxmlparser.cpp:543: static bool TiXmlBase::StringEqual(const 
char*, const char*, bool, TiXmlEncoding): Assertion `0' failed.
Aborted


Backtrace:

#0  0xf7fdc425 in __kernel_vsyscall ()
#1  0xf7c5d307 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#2  0xf7c5e9c3 in __GI_abort () at abort.c:89
#3  0xf7c56687 in __assert_fail_base (fmt=0xf7d90794 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", 
assertion=assertion@entry=0xf7fb8751 "0", file=file@entry=0xf7fb8d76 "tinyxmlparser.cpp", 
line=line@entry=543, function=function@entry=0xf7fb93c0  "static bool TiXmlBase::StringEqual(const char*, const char*, bool, 
TiXmlEncoding)") at assert.c:92
#4  0xf7c56737 in __GI___assert_fail (assertion=0xf7fb8751 "0", file=0xf7fb8d76 
"tinyxmlparser.cpp", line=543, function=0xf7fb93c0  "static bool TiXmlBase::StringEqual(const char*, const char*, 
bool, TiXmlEncoding)") at assert.c:101
#5  0xf7fb5674 in TiXmlBase::StringEqual (p=p@entry=0x804fbbf "", 
tag=tag@entry=0xf7fb8e08 "version", ignoreCase=ignoreCase@entry=true, 
encoding=encoding@entry=TIXML_ENCODING_UNKNOWN) at tinyxmlparser.cpp:543
#6  0xf7fb7862 in TiXmlDeclaration::Parse (this=0x804fbc8, p=0x804fbbf "", 
data=0xd620, _encoding=TIXML_ENCODING_UNKNOWN) at tinyxmlparser.cpp:1603
#7  0xf7fb625b in TiXmlDocument::Parse (this=0xd748, p=0x804fbb8 
"http://lcamtuf.coredump.cx/afl/
(available in Debian experimental)

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

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

Versions of packages libtinyxml2.6.2 depends on:
ii  libc6  2.19-15
ii  libgcc11:5-20150307-1
ii  libstdc++6 5-20150307-1
ii  multiarch-support  2.19-15

--
Jakub Wilk
#include 

#define TIXML_USE_STL 1
#include 

int main(int argc, char ** argv)
{
	if (argc != 2) {
		fprintf(stderr, "Usage: %s \n", argv[0]);
		return 1;
	}
	TiXmlDocument doc(argv[1]);
	if (!doc.LoadFile()) {
		fprintf(stderr, "invalid XML\n");
		return 1;
	}
	TiXmlPrinter printer;
	doc.Accept(&printer);
	puts(printer.CStr());
	return 0;
}


badxml.xml
Description: XML document

Bug#780023: xbmc: XBMC crash at startup

[Bálint Réczey]

Control: tags -1 unreproducible moreinfo

Hi Jeremy,

2015-03-08 11:57 GMT+01:00 Jeremy Guitton :
> Package: xbmc
> Version: 2:13.2+dfsg1-4
> Severity: important
>
> Dear Maintainer,
>
> On fresh install of jessie with Gnome Desktop, XBMC crash at startup. I join
> the log file.
>From the logs it looks like the crash happens in SQLite 3.

Thread 11 (Thread 0x7f6f7daaf700 (LWP 4072)):
#0  0x7f6fb0dd4860 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#1  0x7f6fb0de003b in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#2  0x7f6fb0df142c in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#3  0x7f6fb0e0c659 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#4  0x7f6fb0e0c85f in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#5  0x7f6fb0e0cfc5 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#6  0x7f6fb0e3ef21 in ?? () from /usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#7  0x7f6fb0e3ff27 in sqlite3_step () from
/usr/lib/x86_64-linux-gnu/libsqlite3.so.0
#8  0x00a10062 in dbiplus::SqliteDataset::query
(this=0x7f6f680863d0, query=0x7f6f6801d4f8 "SELECT sum(watchedcount)
FROM tvshowview LIMIT 1") at sqlitedataset.cpp:662
#9  0x009ee8f1 in CDatabase::GetSingleValue
(this=this@entry=0x7f6f7daaeb60, que

If you can reproduce the issue please install libsqlite3-0-dbg to have
a better stack trace and attach it.

I tried reproducing the crash, but with no luck. Could you please list
the steps I need to take?
Do you have any add-ons installed?

Cheers,
Balint

>
>
>
> -- System Information:
> Debian Release: 8.0
>   APT prefers testing-updates
>   APT policy: (500, 'testing-updates'), (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/8 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: systemd (via /run/systemd/system)
>
> Versions of packages xbmc depends on:
> ii  fonts-dejavu-core  2.34-1
> ii  fonts-roboto   1:4.4.4r2-6
> ii  libjs-iscroll  5.1.2+dfsg1-1
> ii  libjs-jquery   1.7.2+dfsg-3.2
> ii  mesa-utils 8.2.0-1
> ii  python-imaging 2.6.1-1
> pn  python:any 
> ii  ttf-dejavu-core2.34-1
> ii  x11-utils  7.7+2
> ii  xbmc-bin   2:13.2+dfsg1-4
>
> xbmc recommends no packages.
>
> xbmc suggests no packages.
>
> -- no debconf information


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

Bug#760445: [mate-control-center] mate-display-properties segment fault with VirtualBox VNC Desktop

[Mike Gabriel]

Control: tag -1 moreinfo

Hi,

On  Do 04 Sep 2014 09:19:24 CEST, 张敬强 wrote:


Package: mate-control-center
Version: 1.8.2+dfsg1-1
Severity: normal

Dear Maintainers,

I install Jessie in VirtualBox with VNC remote desktop enabled.
And I have installed mate-desktop-environment and virtualbox-guest-x11.
When change screen resolution, segment fault will occur with the  
following step:


0. Make sure no ~/.config/monitors.xml file exist
1. run mate-display-properties, select a different resolution R-A  
and click apply
	result: setting applied but segment fault displayed on terminal, a  
window appeared to ask whether accept

2. run mate-display-properties
result: segment fault displayed on terminal and no resolution change
3. run mate-display-properties, select a different resolution R-B  
and click apply
	result: setting applied but segment fault displayed on terminal, a  
window appeared to ask whether accept

4. run mate-display-properties
result: segment fault dispalyed on terminal and resolution become R-A
x. run mate-display-properties
	result: segment fault dispalyed on terminal and resolution change  
between R-A and R-B

x+1. rm ~/.config/monitors.xml and run mate-display-properties
result: segment fault displayed on terminal and no resolution change


I assume that the above bug is fixed since gtk+2.0 (v2.24.25-3)  
appeared in Debian jessie.


Can you please check if the bug is still there or if it is gone now?

Thanks,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgpYd7BigZYbP.pgp
Description: Digitale PGP-Signatur

Bug#780089: wireshark: "On gnome wireshark has not title bar. Does not correctly get focus on click events"

[Bálint Réczey]

Control: tags -1 unreproducible moreinfo

Hi Bart,

2015-03-09 8:59 GMT+01:00 Bart Mariën :
> Package: wireshark
> Version: 1.12.1+g01b65bf-3
> Severity: important
>
> Dear Maintainer,
>
> When starting wireshark gui from commandline or gnome shortcut. The 
> application starts
> with no gnome 'integration'. There is no tilte bar. It's not posible to 
> resize or move the
> gui.
> When the app loses focues(switch to other application). When clicking on the 
> Wireshark
> gui/window, you will give focus to the application that is hidden behind the 
> wireshark
> window, which will be brougth to front. Only if there are no other 
> application positioned
> behind wireshark, it is possible to select/interact with the wireshark gui.
>
> When running the app as sudo/root, the integration is correct. This howerver 
> is discoraged
> by the package maintainer.
>
> Wireshark was installed form the jessie repo, and is at the latest version
I'm unable to reproduce the issue with a fully updated Jessie/Sid
system. I suspect this issue is not related to wireshark, but to
GNOME/window decorations.
I'm copying Debian GNOME Team, maybe they have seen similar problems
with other programs.

Please try to debug this further and if you find logs please attach
them because Wireshark starts fine on my system with titlebar and it
works normally.

Cheers,
Balint


>
>
> -- System Information:
> Debian Release: 8.0
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=nl_BE.UTF-8, LC_CTYPE=nl_BE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages wireshark depends on:
> ii  libc62.19-15
> ii  libcairo21.14.0-2.1
> ii  libgdk-pixbuf2.0-0   2.31.1-2+b1
> ii  libglib2.0-0 2.42.1-1
> ii  libgtk-3-0   3.14.5-1
> ii  libnl-3-200  3.2.24-2
> ii  libnl-genl-3-200 3.2.24-2
> ii  libnl-route-3-2003.2.24-2
> ii  libpango-1.0-0   1.36.8-3
> ii  libpangocairo-1.0-0  1.36.8-3
> ii  libpcap0.8   1.6.2-2
> ii  libportaudio219+svn20140130-1
> ii  libwireshark51.12.1+g01b65bf-3
> ii  libwiretap4  1.12.1+g01b65bf-3
> ii  libwsutil4   1.12.1+g01b65bf-3
> ii  wireshark-common 1.12.1+g01b65bf-3
> ii  xdg-utils1.1.0~rc1+git20111210-7.4
> ii  zlib1g   1:1.2.8.dfsg-2+b1
>
> wireshark recommends no packages.
>
> wireshark suggests no packages.
>
> -- no debconf information
>


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

Bug#779254: please confirm this bug with zoneminder from Debian

[John Crout]

It's in the current Debian Mint.
This help?
- John Crout, MPH, BSEE, CISSP
(720) 476-9140
Skype: jcrout1


On 3/9/15, Holger Levsen  wrote:
> control: tags -1 moreinfo
> control: severity -1 important
>
> Hi John,
>
> you submitted this bug against a zoneminder version which is not in Debian.
>
> Can you please confirm that this bug also applies with versions of
> zoneminder
> from Debian? Downgrading the severity until then...
>
>
> cheers,
>   Holger
>


--


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

Bug#779937: GDP shouldn't process all yaml files all the time

[Alexandre Detiste]

Hi,

> To be fair, judging by your shell prompt

And that's the new souped-up version (see uname's 4 cores output),
on the old one a plain "./run" almost nears two minutes
while GDP v37 ran in 0.2 seconds.

On an Amd Duron from 2005 that is still perfect for most
GDP games & Youtube; I get 10 seconds.

> the video core is the main purpose of the RPi's SoC
...and I know many people that use it to watch movies
or play some old games. (Doom has RetroPie plugins)
It's their _only_ Linux computer in their household;
so they would have run GDP on it;
or beg someone to illegaly share generated .debs

> Perhaps if we profiled what takes all the time, we'd be able to avoid it
> - e.g. by "compiling" the parts of the YAML files that are actually
> needed for the argument parser into a pickle file or something, and
> loading the rest lazily.

I did something similar for bash autocompletion, --package option
now knows about about all the packages avaible for each game;
this was a lower-hanging fruit.

Do you mean compiling it during the package build or by postinst script
like the .pyc files ? I guess this pickle format is arch-independant.

> parts of the YAML files that are actually needed
That's only the package name, aliases, longname & demo_for tags.

Cheers,

Alexandre


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

Bug#778332: RM: oss4/4.2-build2010-1.1

[Moritz Mühlenhoff]

On Wed, Mar 04, 2015 at 09:46:20AM +0100, Ivo De Decker wrote:
> Hi,
> 
> On Fri, Feb 13, 2015 at 05:52:36PM +0100, Moritz Muehlenhoff wrote:
> > please remove oss4 from jessie. There's been no maintainer
> > followup since a month (plus no action back then we Ben
> > initially reported it to the maintainers privately).
> 
> Removal hint added.

I tried to check why this hasn't been removed, but I don't
understand why. The simulated removal "dak rm -s testing"
run show many dependencies on ALSA, e.g.

Checking reverse dependencies...
# Broken Depends:
a2jmidid: a2jmidid [amd64 armel armhf i386 mips mipsel powerpc s390x]
abx: abx [amd64 arm64 armel armhf i386 mips mipsel powerpc ppc64el s390x]
aconnectgui: aconnectgui [amd64 arm64 armel armhf i386 mips mipsel powerpc 
ppc64el s390x]
adplay: adplay [amd64 armel armhf i386 mips mipsel powerpc ppc64el s390x]
aegisub: aegisub [amd64 armhf i386 mips mipsel powerpc ppc64el s390x]
aeolus: aeolus [amd64 arm64 armel armhf i386 mips mipsel powerpc ppc64el s390x]
(..)

Cheers,
Moritz


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

Bug#780091: unblock (pre-approval): atril/1.8.1+dfsg1-4

[Mike Gabriel]

Control: tags -1 - moreinfo

On  Mo 09 Mär 2015 18:41:45 CET, Niels Thykier wrote:


Control: tags -1 confirmed moreinfo

On 2015-03-09 09:41, Mike Gabriel wrote:

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

Please consider unblocking planned upload of package atril.

+  * debian/patches:
++ Add 0002_forgotten-mutex-unlock.patch. Don't forget to unlock the
+  trylock'ed mutex. Prevents from unpredictable behaviour after that
+  mutex unlocking has been forgotten. (Closes: #779848).

-> Prevent from unpredictable behaviour because of forgotten unlock call in
atril's job handling code.

ligh+love,
Mike


unblock atril/1.8.1+dfsg1-4

[...]


Ack, please upload this to unstable and remove the moreinfo tag once it
has been accepted.

Thanks,
~Niels


uploaded and accepted in unstable.

light+love+thanks,
Mike
--

mike gabriel aka sunweaver (Debian Developer)
fon: +49 (1520) 1976 148

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpMwTuEXi7aJ.pgp
Description: Digitale PGP-Signatur

Bug#780130: unblock (pre-approval): python-x2go/0.5.0.1-3

[Mike Gabriel]

Control: tags -1 - moreinfo

On  Mo 09 Mär 2015 18:45:24 CET, Niels Thykier wrote:


Control: tags -1 confirmed moreinfo

On 2015-03-09 16:11, Mike Gabriel wrote:

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

Please consider unblocking planned upload of package python-x2go.

I skimmed through python-x2go upstream Git and considered the below
patches important enough to attempt for an unblock request.

+  * debian/patches:
++ Add 0003_use-correct-loglevel-WARN.patch. Use the proper
+  log.loglevel_WARN expression (instead of undefined
+  log.loglevel_WARNING). Upstream patch needed
+  rebasing and a modification to apply correctly. (Closes: #780128).

-> Cherry-picked from upstream. Prevent python-x2go from throwing
exceptions due to flaw in log message calls.



NB: There is a typo in the patch description s/logolevel/loglevel/


++ Update 0001_catch-connection-exception-during-session-startup.patch.
+  Fix expression errors in two Python exceptions. (Closes: #780125).

-> I should have paid more attention here, in the first place. The issue
got fixed upstream way back already, but I forgot to provide the fix in
Debian (until today).

++ Add 0005_fix-password-auth-if-keys-have-passphrase.patch.  
Fix password
+  authentication in pyhoca-cli if people have default SSH keys  
locked with

+  a passphrase. (Closes: #780127).

-> Nasty issue if people use pyhoca-cli (X2Go command line client) and
have locked SSH private keys. PyHoca-CLI won't stop trying to unlock the
SSH key instead of using the interactively provide password for normal
username/password SSH authentication.


light+love,
Mike


(include/attach the debdiff against the package in testing)

unblock python-x2go/0.5.0.1-3

[...]


Ack, please upload this to unstable and remove the moreinfo tag once it
has been accepted.

~Niels


uploaded and accepted in unstable.

light+love,
Mike
--

mike gabriel aka sunweaver (Debian Developer)
fon: +49 (1520) 1976 148

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpfoB92VbPZS.pgp
Description: Digitale PGP-Signatur

Bug#780092: unblock (pre-approval): mate-utils/1.8.1+dfsg1-2

[Mike Gabriel]

Control: tags -1 - moreinfo

On  Mo 09 Mär 2015 18:40:38 CET, Niels Thykier wrote:


Control: tags -1 confirmed moreinfo

On 2015-03-09 09:32, Mike Gabriel wrote:

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

Please consider unblocking planned upload of package mate-utils

+  * debian/patches:
++ Add 0001_mate-dictionary-fix-double-free-error.patch. Avoid  
crashes of

+  mate-dictionary due to double-free error. (Closes: #779856).

-> Prevent crashes of mate-dictionary after error dialog box showed up.

light+love,
Mike


unblock mate-utils/1.8.1+dfsg1-2

[...]


Ack, please upload this to unstable and remove the moreinfo tag when it
has been accepted.

~Niels


uploaded and accepted in unstable.

light+love+thanks,
Mike
--

mike gabriel aka sunweaver (Debian Developer)
fon: +49 (1520) 1976 148

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgp3viFDlONEx.pgp
Description: Digitale PGP-Signatur