Bug#762073: libc6: libc6 declares 'Multi-Arch: same' but is not coinstallable on some arches

[Ben Longbons]

Package: libc6
Version: 2.19-11
Severity: normal

Dear Maintainer,

While testing cross toolchains [1], dpkg bailed out when trying to
overwrite a shared file with different contents.

Particularly, /lib/ld.so.1 is different on powerpc, mips, and mipsel.
I only checked arches listed under 'Foreign Architectures' below;
upstream has list at https://sourceware.org/glibc/wiki/ABIList

Since ld.so is the single most important file on a system, it is hard-coded
in all existing binaries, but at least the conflict needs to be declared.

(Theoretically, Debian doesn't officially need to support binaries that
don't come from .deb packages or Debian-provided gcc, so it might be
possible to remove the conflict in the long term. Practically, it would
be dangerous to change it on native arches, but sufficient packaging magic
can ensure that users who don't opt in never see the difference.)


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
armel
powerpc
arm64
armhf
mips
mipsel

Kernel: Linux 3.14-2-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

Versions of packages libc6 depends on:
ii  libgcc1  1:4.9.1-14

libc6 recommends no packages.

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.53
pn  glibc-doc  
ii  locales2.19-11

-- debconf information excluded


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

Bug#761931: reportbug: bogus "not fully qualified" with ssmtp

[Eduard Bloch]

Hallo,
* Sandro Tosi [Tue, Sep 16 2014, 11:18:48PM]:
> > sendmail: RCPT TO: (554 5.7.1 domain idefix of  is 
> > not fully qualified.)
> 
> domains in email addresses have to be fully qualified to be routed, so
> that means you may want to change the address you're using with
> reportbug with something fully qualified.

Yesh, that's what the message says.

However, as said, if I pipe the same message that reportbug stored as
backup to sendmail, it just works. And it should work, ssmtp was
configured to rewrite the sender address. Therefore I must assume that
reportbug does something evil to it if rewritting suddenly breaks.

Regards,
Eduard.


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

Bug#753643: munge: diff for NMU version 0.5.11-1.1

[gennaro . oliva]

Dear Ana and Remi,

On Wed, Sep 17, 2014 at 11:26:30PM +0200, Ana Guerrero Lopez wrote:
> I've prepared an NMU for munge (versioned as 0.5.11-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

this patch is perfect for me.
Thanks for your help
-- 
Gennaro Oliva


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

Bug#762072: Overwrittes volk-config-info from gnuradio

[Eduard Bloch]

Package: libvolk-bin
Version: 3.7.5-3
Severity: important

Upgrade from previous jessie/sid state failed once with the following
messages. As usual, the installation order is not guaranteed, I guess
you have to set Overrides as needed.

Vorbereitung zum Entpacken von .../libvolk-bin_3.7.5-3_amd64.deb ...
Entpacken von libvolk-bin (3.7.5-3) ...
dpkg: Fehler beim Bearbeiten des Archivs 
/var/cache/apt/archives/libvolk-bin_3.7.5-3_amd64.deb (--unpack):
 Versuch, »/usr/bin/volk-config-info« zu überschreiben, welches auch in Paket 
gnuradio 3.7.3-9+b1 ist
dpkg-deb: Fehler: Unterprozess einfügen wurde durch Signal (Datenübergabe 
unterbrochen (broken pipe)) getötet
Vorbereitung zum Entpacken von .../gnuradio_3.7.5-3_amd64.deb ...
Begin freedesktop uninstall...
Begin freedesktop uninstall...
Uninstall icon: 32x32
Uninstall icon: 48x48
Uninstall icon: 64x64
Uninstall icon: 128x128
Uninstall icon: 256x256
Uninstall mime type

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

Kernel: Linux 3.16.2+ (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libvolk-bin depends on:
ii  libboost-filesystem1.55.0   1.55.0+dfsg-2
ii  libboost-program-options1.55.0  1.55.0+dfsg-2
ii  libboost-system1.55.0   1.55.0+dfsg-2
ii  libboost-test1.55.0 1.55.0+dfsg-2
ii  libc6   2.19-11
ii  libgcc1 1:4.9.1-14
ii  liborc-0.4-01:0.4.22-1
ii  libstdc++6  4.9.1-14
ii  libvolk0.0.03.7.5-3
ii  multiarch-support   2.19-7

libvolk-bin recommends no packages.

libvolk-bin suggests no packages.

-- no debconf information

-- 
Es gibt Menschen, die, wenn sie das Licht am Ende des Tunnels sehen,
ein neues Stück Tunnel kaufen.
-- Johannes Rau 
(vor Schülern über die Zukunftsängste der Gesellschaft)


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

Bug#762027: libircclient: libircclient segmentation fault on using ipv6 (possible security issue?)

[Dariusz Dwornikowski]

> Dear Maintainer,
> 
> current upstream versions and down to 1.3 (possibly even older) versions
> of libircclient have an issue with ipv6 handling. When connecting to a
> ipv6 address it segfaults on receiving the first message from the server.
> 
> It's caused by writing a sockaddr6_in into a sockaddr_in which overwrites
> some callback function pointers.
> 
> The bug is reported upstream but since it's possibly a security issue
> and libircclients' upstream is very slow you might want to consider
> applying this small patch.

Thanks you I will apply it and make a point release. Can you point
point me to the URL where the patch was reported? 


> 
> -- System Information:
> Debian Release: 7.6
>   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_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages libircclient1 depends on:
> ii  libc6  2.13-38+deb7u4
> 
> libircclient1 recommends no packages.
> 
> libircclient1 suggests no packages.
> 
> -- no debconf information

> Index: libircclient.c
> ===
> --- libircclient.c(revision 125)
> +++ libircclient.c(working copy)
> @@ -817,7 +817,7 @@
>   if (saddr.ss_family == AF_INET)
>   memcpy (&session->local_addr, &((struct sockaddr_in 
> *)&laddr)->sin_addr, sizeof(struct in_addr));
>   else
> - memcpy (&session->local_addr, &((struct sockaddr_in6 
> *)&laddr)->sin6_addr, sizeof(struct in6_addr));
> + memcpy (&session->local_addr6, &((struct sockaddr_in6 
> *)&laddr)->sin6_addr, sizeof(struct in6_addr));
>  
>  #if defined (ENABLE_DEBUG)
>   if ( IS_DEBUG_ENABLED(session) )


-- 
Dariusz Dwornikowski, 
  Institute of Computing Science, Poznań University of Technology
  www.cs.put.poznan.pl/ddwornikowski/  
  room 2.7.2 BTiCW | tel. +48 61 665 29 41


signature.asc
Description: Digital signature

Bug#762071: am-utils: now amd segfault at 8 ... error 4 in libc-2.19.so (kernels 3.14+)

[ptizoom]

Package: am-utils
Version: 6.2+rc20130922-1
Severity: important

Dear Maintainer,
just wanted to report
after upgrade of libc6 to 2.19-11,
amd is crashing frequently ...on kernels 3.14, 3.16 alike.

with errors...
[  489.075564] amd[4369]: segfault at 8 ip 7f3f6f50121a sp 7fff92516318 
error 4 in libc-2.19.so[7f3f6f471000+19f000]
[  917.201125] amd[9567]: segfault at 8 ip 7f0fe885821a sp 7ce3e0e8 
error 4 in libc-2.19.so[7f0fe87c8000+19f000]
...

this am-utils version is a made up from, 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727770

has anyone experienced similare issues?

thanks,

Christian Montanari.

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

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

Versions of packages am-utils depends on:
ii  debconf1.5.53
ii  debianutils4.4
ii  libamu46.2+rc20130922-1
ii  libc6  2.19-11
ii  libgdbm3   1.8.3-13
ii  libhesiod0 3.2.1-3
ii  libldap-2.4-2  2.4.39-1.1+b1
ii  libwrap0   7.6.q-25
ii  rpcbind [portmap]  0.2.1-6
ii  ucf3.0030

am-utils recommends no packages.

Versions of packages am-utils suggests:
ii  am-utils-doc  6.2+rc20110530-3.2
ii  nis   3.17-33

-- Configuration Files:
/etc/am-utils/amd.conf changed:
[global] 
  auto_dir = /amd
  log_file = syslog
  restart_mounts = yes
  selectors_in_defaults = yes
  unmount_on_exit = yes
  vendor = Debian
  nfs_vers = 3
  log_options   = fatal,error,warn
  debug_options = amq
[/homes/k]
  map_type = file
  map_name = /etc/am-utils/amd.homes
[/home]
  map_name = amd.home
  map_type = nis

/etc/init.d/am-utils changed:
PATH=/usr/sbin:/sbin:/usr/bin:/bin
export PATH
CONF=/etc/default/am-utils
test -x /usr/sbin/amd || exit 0
get_amd_args() {
if [ ! -f "$CONF" ]
then
echo "$0: not configured yet (try running \"dpkg-reconfigure 
am-utils\")." 1>&2
exit 1
fi
. "$CONF"
if test "$AM_UTILS_USE_NIS" = true
then
map="$AM_UTILS_NIS_MASTER_MAP"
case "$AM_UTILS_NIS_MASTER_MAP_KEY_STYLE" in
config)
key="$AM_UTILS_NIS_KEY"
AMDARGS="`ypmatch \"$key\" \"$map\"`"
;;
onekey)
AMDARGS="`ypcat \"$map\"`"
;;
mountpoint)
AMDARGS="`ypcat -k \"$map\"`"
;;
custom)
AMDARGS="`sh -c \"$AM_UTILS_NIS_CUSTOM\"`"
;;
*)
echo "$0: bad key style"
exit 1
;;
esac
if [ -z "$AMDARGS" ]
then
echo "$0: cannot find master map" 1>&2
exit 1
fi
else
AMDARGS=""
if [ "$AM_UTILS_MAP_NET" = true ]
then
AMDARGS="$AMDARGS /net /usr/share/am-utils/amd.net"
fi
if [ "$AM_UTILS_MAP_HOME" = true ]
then
AMDARGS="$AMDARGS /home /etc/passwd"
fi
AMDARGS="$AMDARGS $AM_UTILS_MAP_OTHERS"
fi
if  [ "$AM_UTILS_CLUSTERNAME" != "" ]; then
AMDARGS="-C \"$AM_UTILS_CLUSTERNAME\" $AMDARGS"
fi
}
start_amd() {
pid="`amq -p 2>/dev/null`"
if [ -n "$pid" ]; then
echo "Starting automounter: amd is already running" 1>&2
exit 0
fi
# If the hostname is not a FQHN, add the -d command line switch,
# so that hostnames in the maps are stripped correctly.
case `hostname` in
*.*)dnsdomain=''
;;
*)  if test "$AM_UTILS_USE_NIS" = true; then
  dnsdomainname=`dnsdomainname`
  if [ "$dnsdomainname" ] ; then
dnsdomain="-d $dnsdomainname"
  else
echo "$0: please setup your domainname" 1>&2
exit 1
  fi
else
  dnsdomain=''
fi
;;
esac
get_amd_args
echo -n "Starting automounter: amd"

/usr/sbin/amd -F /etc/am-utils/amd.conf $dnsdomain $AMDARGS
echo "."
}
raze_amd() {
  # This function tries to kill an amd which hasn't exited nicely.
  # This happens really easily, especially if using mount_type autofs
  # Get the currently mounted filesystems
  filesystems=`/bin/tempfile -s .amd`
  if [ $? -ne 0 ]; then
return 1
  fi
  amq | awk '$2 !~ "root" {print $1}' > $filesystems
  # Kill the daemon
  kill -9 "$pid"
  sleep 10
  if kill -s 0 $pid; then
rm -f $filesystems
return 1
  fi
  # Attempt to forcibly unmount the remaining filesystems
  returncode=0
  tac $filesystems | while read fs; do
umount -l -f "$fs" || returncode=1
sleep 1
  done
  rm -f $filesystems
  return $returncode
}
sto

Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC

[Michel Dänzer]

On 18.09.2014 13:23, Bill Chatfield wrote:

[0.997986] radeonfb :00:10.0: enabling device (0006 -> 0007)
[1.193788] radeonfb :00:10.0: Invalid ROM contents
[1.193813] radeonfb (:00:10.0): Invalid ROM signature 303 should be 
0xaa55
[1.193823] radeonfb: Retrieved PLL infos from Open Firmware
[1.193842] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=203.00 Mhz, 
System=392.00 MHz
[1.193864] radeonfb: PLL min 12000 max 35000
[1.289994] i2c i2c-2: unable to read EDID block.
[1.441986] i2c i2c-2: unable to read EDID block.
[1.593986] i2c i2c-2: unable to read EDID block.
[1.949865] radeonfb: Monitor 1 type LCD found
[1.949881] radeonfb: EDID probed
[1.949893] radeonfb: Monitor 2 type no found
[1.949915] radeonfb: Using Firmware dividers 0x0002008e from PPLL 0
[1.949981] radeonfb: Dynamic Clock Power Management enabled
[1.982573] Console: switching to colour frame buffer device 160x53
[2.004457] radeonfb: Backlight initialized (radeonbl0)
[2.004635] radeonfb (:00:10.0): ATI Radeon 4e50 "NP"


This shows that radeonfb is still enabled, so it doesn't provide the 
information corresponding to the bug.



--
Earthling Michel Dänzer|  http://www.amd.com
Libre software enthusiast  |Mesa and X developer


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

Bug#762070: devscripts: [licensecheck] should check also javascript files by default

[Dominique Dumont]

Package: devscripts
Version: 2.14.6
Severity: wishlist

Dear Maintainer,

For better or for worse, javascript is becoming a widely used language and
more debian package are about packaging javascript. Packaging javascript
requires an analysis of the javacript files to check their license and
copyright. 

Unfortunately, by default, licensecheck does not parse javascript files.
One has to use the -c option to check for licenses in copyright files.

This small patch add js in the default language list.

All the best

--- /usr/bin/licensecheck~  2014-08-05 16:40:16.0 +0200
+++ /usr/bin/licensecheck   2014-09-17 20:24:07.021840282 +0200
@@ -160,7 +160,7 @@
 $default_ignore_regex =~ s/^#.*$//mg;
 $default_ignore_regex =~ s/\n//sg;
 
-my $default_check_regex = 
'\.(c(c|pp|xx)?|h(h|pp|xx)?|f(77|90)?|go|p(l|m)|xs|sh|php|py(|x)|rb|java|vala|el|sc(i|e)|cs|pas|inc|dtd|xsl|mod|m|tex|mli?|(c|l)?hs)$';
+my $default_check_regex = 
'\.(c(c|pp|xx)?|h(h|pp|xx)?|f(77|90)?|go|p(l|m)|xs|sh|php|py(|x)|rb|js|java|vala|el|sc(i|e)|cs|pas|inc|dtd|xsl|mod|m|tex|mli?|(c|l)?hs)$';
 
 my $modified_conf_msg;


*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- Package-specific info:

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

--- ~/.devscripts ---
DEBCHANGE_RELEASE_HEURISTIC=changelog
DEBSIGN_KEYID="49AB2B6C"
DEBUILD_LINTIAN=yes
DEBUILD_LINTIAN_OPTS="-i -I --show-overrides"
USCAN_DESTDIR=../tarballs
DEBRELEASE_DEBS_DIR=../build-area

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

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

Versions of packages devscripts depends on:
ii  dpkg-dev 1.17.13
ii  libc62.19-11
ii  perl 5.20.0-6
ii  python3  3.4.1-1
pn  python3:any  

Versions of packages devscripts recommends:
ii  at  3.1.15-1
ii  curl7.38.0-1
ii  dctrl-tools 2.23
ii  debian-keyring  2014.08.31
ii  dput-ng [dput]  1.8
ii  dupload 2.7.0
ii  equivs  2.0.9
ii  fakeroot1.20.1-1.1
ii  file1:5.19-2
ii  gnupg   1.4.18-4
ii  libdistro-info-perl 0.13
ii  libencode-locale-perl   1.03-1
ii  libjson-perl2.61-1
ii  liblwp-protocol-https-perl  6.06-2
ii  libparse-debcontrol-perl2.005-4
ii  libsoap-lite-perl   1.11-1
ii  liburi-perl 1.64-1
ii  libwww-perl 6.08-1
ii  lintian 2.5.27
ii  man-db  2.6.7.1-1
ii  patch   2.7.1-6
ii  patchutils  0.3.3-1
ii  python3-debian  0.1.23
pn  python3-magic   
ii  sensible-utils  0.0.9
ii  strace  4.9-2
ii  unzip   6.0-12
ii  wdiff   1.2.2-1
ii  wget1.15-1+b1
ii  xz-utils5.1.1alpha+20120614-2

Versions of packages devscripts suggests:
ii  bsd-mailx [mailx]8.1.2-0.20140825cvs-1
ii  build-essential  11.7
pn  cvs-buildpackage 
pn  devscripts-el
pn  gnuplot  
ii  gpgv 1.4.18-4
pn  libauthen-sasl-perl  
ii  libfile-desktopentry-perl0.07-1
ii  libnet-smtp-ssl-perl 1.01-3
ii  libterm-size-perl0.207-1+b2
ii  libtimedate-perl 2.3000-2
ii  libyaml-syck-perl1.27-2+b2
ii  mutt 1.5.23-1.1
ii  openssh-client [ssh-client]  1:6.6p1-7
pn  svn-buildpackage 
ii  w3m  0.5.3-17

-- 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#749275: License for PGObject::Util::PseudoCSV?

[RJ Clay]

Chris,
On 06/04/2014 02:40 PM, RJ Clay wrote:


   I knew that module was BSD licensed when I started packaging it, but not which one;  and 
for the debian/copyright file, I need to be more specific.  But I also only ask because the 
rest of the PGObject*  modules that I've packaged so far have been, IIRC, bsd-2-clause;  while 
this one appears to bsd-3-clause, being listed that way in both the README and PseudoCSV.pm.


   And with the recent v1.1.0 release, I'm afraid it's still not clear to me...   The LICENSE 
file itself is for a 2 clause BSD license, like the rest of the PGObject* modules have I've 
looked at so far; while the README file and the module itself currently have the 3 clause BSD 
license (including this as the third clause: "Neither the name of Chris Travers's Organization 
nor the names of its contributors may be used to endorse or promote products derived from this 
software without specific prior written permission.").








Robert James Clay
j...@rocasa.us


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

Bug#754586: [jitsi-dev] debcheckout jitsi

[Damian Minkov]

Hi,

On Wed, Sep 17, 2014 at 11:51 PM, Damian Minkov  wrote:
> Hi,
>
>
>
> On Wed, Sep 17, 2014 at 11:40 PM, Kurt Roeckx  wrote:
>> On Wed, Sep 17, 2014 at 11:21:06PM +0300, Damian Minkov wrote:
>>> Hi,
>>>
>>> it is the upstream which contains the debian packaging. We commit
>>> everything in resources/install/debian.
>>> What's the point of this field if its not the upstream? What should we
>>> put there?
>>> I saw there is a bug report about missing vcs fields and I've added
>>> them with values pointing to the repository containing the sources we
>>> are currently packaging.
>>
>> It seems to contain instruction on how to generate the source
>> package from that repository, including having to do a few git
>> clone / svn checkouts.  The Vcs-* fields should point to the
>> sources like it's in Debian so that people working on
>> Debian can make changes to it.  This means among other things
>> that there is a "debian" directory, instead of a
>> resources/install/debian.  The full sources shouldn't even be
>> there, it could be that the upstream sources are gotten from
>> the .orig.tar.gz file.  Or it might have the upstream sources
>> too, but most likely not contain the full upstream history, just
>> those things that are uploaded to Debian.
>>
>> Typically the "debian" dir is not maintained upstream, but in it's
>> own repository like the one in collab-maint.  You seem to have a
>> different workflow.  And the Vcs-* fields you added will not result
>> in people getting what they expect to find.
>>
>> (I don't know if I explained myself good, but I hope you
>> understand what I mean.)
>
> Thanks for clearing it. Are these values correct:
>
> +Vcs-Git: git://anonscm.debian.org/collab-maint/jitsi.git
> +Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/jitsi.git
>
> Should we commit there or it is automatically imported? Do we have
> access there? How can we update with current version or it is updated
> after the package is accepted into Debian repo?

I see that you need to be Debian developer to have write access. Also
external developers can be granted access by the developer.
But what I see is that the repository is out of sync, it is missing
the changes for 2.4.4997-1.2. As long as we have our packaging folder,
we need some sort of notifications for changes in the package so we
can merge the changes. Not sure how good is to have one more
repository to sync. Still there is a source package that can be
downloaded with apt-get source and for sure it is in sync, and people
can make changes to it.

Regards
damencho

>
> Thanks
> damencho
>
>>
>>
>> Kurt
>>


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

Bug#761947: systemd: Upgrade fails due to conflict with systemd-shim 8-1

[Martin Pitt]

Paul Menzel [2014-09-17 23:08 +0200]:
> That is great, but it does not fix the error of broken upgrade path to
> my knowledge. Users might experience that bug when systemd 215-4
> migrates to testing before systemd-shim 8-2.

Well yes, then systemd would be held back for upgrading until
systemd-shim 8-2 lands. Isn't that pretty much what we are looking
for?

But can this happen in the first place? The newer systemd in unstable
makes systemd-shim uninstallable in testing, so britney ought to hold
back the systemd migration until systemd and systemd-shim can enter
testing in lockstep.

> In my opinion, unfortunately systemd needs to have a line similar to:
> 
> Breaks: systemd-shim (<< 8-2)

Now that we stopped having the "API gap" between unstable and
experimental we could indeed do that. I'm a bit surprised that we need
that in the first place though (see above).

> Are you going to reassign to systemd or should I do it?

If we need it, please go ahead. (I might have misunderstood how
britney works)

Martin

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


signature.asc
Description: Digital signature

Bug#752692: [Pkg-xfce-devel] Processed: lxde-metapackages bugs cleanup (pass #1)

[Yves-Alexis Perez]

control: tag -1 moreinfo , severity -1 normal

On jeu., 2014-09-18 at 00:54 +, Debian Bug Tracking System wrote:
> > retitle 752692 DM exits and re-tries several times, without letting login 
> > (memory low?)
> Bug #752692 [lightdm] lxde exits and re-tries several times, without letting 
> me login
> Changed Bug title to 'DM exits and re-tries several times, without letting 
> login (memory low?)' from 'lxde exits and re-tries several times, without 
> letting me login'
> > severity 752692 important
> Bug #752692 [lightdm] DM exits and re-tries several times, without letting 
> login (memory low?)
> Severity set to 'important' from 'normal'

Bob, please don't reassign bugs without explaining things for the new
maintainer.

Richard: there's not enough information provided here to be able to
debug. Please provide logs from Xorg and lightdm (you or someone else,
interested in a low-memory setup, provided that's actually the problem).

Regards,
-- 
Yves-Alexis


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

Bug#762066: CONFIG_OCTEON_USB=y

[Heinrich Schuchardt]

At least the following also have to be changed:

CONFIG_USB=y
CONFIG_USB_STORAGE=y

Best regards

Heinrich Schuchardt


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

Bug#762069: security-tracker does not update NVD information anymore

[Salvatore Bonaccorso]

Package: security-tracker
Severity: normal
Tags: confirmed

Hi,

I'm looking into this problem, but would like to have documented the
problem in the BTS. Currently since we switched to fetch information
trough https updates of NVD information for the security-tracker does
not work anymore.

Makefile contains a update-nvd target, which fetches the nvde-$year
information via https:

wget -q -Odata/nvd/$$name https://nvd.nist.gov/download/$$name

ERROR: The certificate of `nvd.nist.gov' is not trusted.
ERROR: The certificate of `nvd.nist.gov' hasn't got a known issuer.

Solution: We need (as for example also needed for qa's vcs-watch) our
own CA store for the security-tracker which is used on soler.

Regards,
Salvatore


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

Bug#758716: tgt: init script not LSB compliant

[Apollon Oikonomopoulos]

Control: clone -1 -2
Control: retitle -2 tgt: init script stop action should always stop tgtd
Control: reopen -2
Control: found -2 1:1.0.50-1

On 19:17 Wed 17 Sep , Patrick Matthäi wrote:
> Am 16.09.2014 um 11:55 schrieb Apollon Oikonomopoulos:
> >> a) stop vs. forcedstop
> >> stop does not work if there are still open sessions:
> >># /etc/init.d/tgt stop ; echo $?
> >>[FAIL] Stopping target framework daemon: tgtd failed!
> >>Some initiators are still connected - could not stop tgtd
> >>2
> >> I had to change the use of stop() to forcedstop(), so that tgt works with 
> >> HeartBeat.
> > 
> > This is intentional and I am a bit reluctant to change the behavior at 
> > this point (although under systemd we default to forcedstop, having no 
> > ability to define custom actions). I'll think a bit more about 
> > defaulting to a hard behavior before the next release. Note that failing 
> > in this case does not seem to be an LSB violation.
> 
> Think about stopping a SQL or Webservice, where are still (and any time)
> users. Not stopping on stop is buggy :(

You're right. However HTTP or MySQL clients might be able to deal with 
this in a graceful manner, whereas a system whose root fs resides on an 
iSCSI disks will probably not be excited if you pull the root fs under 
its feet.

Note that I don't like stop vs forcedstop either and as I said we 
already force-stop under systemd by default, so I'll probably change it.  
For the time being I'm cloning this as a different bug report and 
leaving it open.

Thanks again,
Apollon


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

Bug#755610: Changes now being reviewed upstream

[Brian May]

It looks like these patches have been revised and merged upstream.
-- 
Brian May 

Bug#757966: RFS: lutris/0.3.4-1 [ITP]

[Andrey Rahmatullin]

On Wed, Sep 17, 2014 at 05:12:54PM -0300, Eriberto wrote:
> > 6. I have added a generic README.source about quilt. Is this OK?
> No. My idea was talk about the original debian directory removed from
> upstream code.
The original debian/ is removed by dpkg-source when unpacking 3.0 (quilt)
packages, please read dpkg-source(1), "Format: 3.0 (quilt)".
You should document in README.source only things required to be done
manually after unpacking the package, see
https://www.debian.org/doc/debian-policy/ch-source.html#s-readmesource

-- 
WBR, wRAR


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

Bug#762067: wireshark crashes immediately

[Giorgos Pallas]

Package: wireshark
Version: 1.12.0+git+4fab41a1-1+b1
Severity: important

Dear Maintainer,

When I start wireshark it gives the following messages and crashes:

(wireshark:3095): GdkPixbuf-WARNING **: Error loading XPM image loader: Image 
type 'xpm' is not supported
**
ERROR:/build/wireshark-VQ_DcW/wireshark-1.12.0+git+4fab41a1/ui/gtk/stock_icons.c:401:stock_icons_init:
 assertion failed: (pixbuf)
Aborted

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

Kernel: Linux 3.14-2-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

Versions of packages wireshark depends on:
ii  libc62.19-11
ii  libcairo21.12.16-5
ii  libgdk-pixbuf2.0-0   2.30.8-1
ii  libglib2.0-0 2.40.0-5
ii  libgtk-3-0   3.12.2-3+b1
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.7-1
ii  libpangocairo-1.0-0  1.36.7-1
ii  libpcap0.8   1.6.2-1
ii  libportaudio219+svn20140130-1
ii  libwireshark51.12.0+git+4fab41a1-1+b1
ii  libwiretap4  1.12.0+git+4fab41a1-1+b1
ii  libwsutil4   1.12.0+git+4fab41a1-1+b1
ii  wireshark-common 1.12.0+git+4fab41a1-1+b1
ii  xdg-utils1.1.0~rc1+git20111210-7.1
ii  zlib1g   1:1.2.8.dfsg-2

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#762066: CONFIG_OCTEON_USB=y

[Heinrich Schuchardt]

Package: linux-image-octeon
Version: 3.16+60
Severity: important

Booting from the internal USB drive of an Ubiquity EdgeRouter Lite requires
CONFIG_OCTEON_USB=y

Please, add this to the kernel config file of Octeon Linux images.

At least as of Kernel 3.17-rc4 the driver works without problems.

Best regards

Heinrich Schuchardt


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

Bug#761406: debconf notice or NEWS.Debian entry?

[Lesley Longhurst]

How about a brief debconf notice with a pointer to "further info" which would 
be an expanded version in NEWS.Debian?

Those same users are also way less likely to understand the issue, so a "words 
of one syllable approach" would seem sensible to me.

-Original Message-
From: Ryan Tandy [mailto:r...@nardis.ca] 
Sent: Thursday, 18 September 2014 4:43 p.m.
To: 761...@bugs.debian.org
Subject: Bug#761406: debconf notice or NEWS.Debian entry?

Hi pkg-openldap-devel readers,

On 13/09/14 12:05 PM, Ryan Tandy wrote:
> On 13/09/14 08:41 AM, Dietrich Clauss wrote:
>> When the LDAP is used to authenticate users (e.g. in conjunction with 
>> libnss-ldapd and libpam-ldapd), the rule "olcAccess: to * by self 
>> write" allows the user to change her uidNumber and impersonate 
>> another user.
>>
>> IMO the default config should allow self-write access to userPassword 
>> and shadowLastChange only.
>
> Thanks for the report. I've removed the offending 'by self write' in 
> git. I'm not sure why that was added in the first place. The default 
> slapd.conf didn't have it and I didn't find any comments about it.
>
> I don't think I'm comfortable doing an automated ACL change to 
> existing installs. A NEWS.Debian entry suggesting the change (and 
> mentioning how to do it) might be appropriate, though.

What do you think: an entry in NEWS.Debian, or a debconf notice (conditional on 
detecting a possibly-vulnerable acl)? It occurs to me that the users most 
likely to be affected by this (default settings, haven't reviewed acls) are 
also the least likely to read apt-listchanges...

Bug#762065: error processing package python-soappy (--configure)

[Heinrich Schuchardt]

Package: python-soappy
Version: 0.12.22-1
Severity: important

python-soappy fails to install

Linux ubnt 3.17.0-rc4 #14 SMP PREEMPT Sun Sep 14 12:50:57 CEST 2014 mips64 
GNU/Linux
Ubiquity EdgeRouter lite
Debian version  : Jessie
system type : UBNT_E100 (CN5020p1.1-500-SCP)
cpu model   : Cavium Octeon+ V0.1

The following NEW packages will be installed:
  python-debianbts python-reportbug python-soappy reportbug
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/324 kB of archives.
After this operation, 919 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package python-soappy.
(Reading database ... 39027 files and directories currently installed.)
Preparing to unpack .../python-soappy_0.12.22-1_all.deb ...
Unpacking python-soappy (0.12.22-1) ...
Selecting previously unselected package python-debianbts.
Preparing to unpack .../python-debianbts_1.12_all.deb ...
Unpacking python-debianbts (1.12) ...
Selecting previously unselected package python-reportbug.
Preparing to unpack .../python-reportbug_6.5.1_all.deb ...
Unpacking python-reportbug (6.5.1) ...
Selecting previously unselected package reportbug.
Preparing to unpack .../reportbug_6.5.1_all.deb ...
Unpacking reportbug (6.5.1) ...
Processing triggers for man-db (2.6.7.1-1) ...
Processing triggers for mime-support (3.56) ...
Setting up python-soappy (0.12.22-1) ...
Sorry: OverflowError: cannot convert float infinity to integer
Sorry: OverflowError: cannot convert float infinity to integer
dpkg: error processing package python-soappy (--configure):
 subprocess installed post-installation script returned error exit status 101
dpkg: dependency problems prevent configuration of python-debianbts:
 python-debianbts depends on python-soappy; however:
  Package python-soappy is not configured yet.

dpkg: error processing package python-debianbts (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of python-reportbug:
 python-reportbug depends on python-debianbts; however:
  Package python-debianbts is not configured yet.

dpkg: error processing package python-reportbug (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of reportbug:
 reportbug depends on python-reportbug (= 6.5.1); however:
  Package python-reportbug is not configured yet.

dpkg: error processing package reportbug (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 python-soappy
 python-debianbts
 python-reportbug
 reportbug


Best regards

Heinrich Schuchardt


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

Bug#761406: debconf notice or NEWS.Debian entry?

[Ryan Tandy]

Hi pkg-openldap-devel readers,

On 13/09/14 12:05 PM, Ryan Tandy wrote:

On 13/09/14 08:41 AM, Dietrich Clauss wrote:

When the LDAP is used to authenticate users (e.g. in conjunction with
libnss-ldapd and libpam-ldapd), the rule "olcAccess: to * by self
write" allows
the user to change her uidNumber and impersonate another user.

IMO the default config should allow self-write access to userPassword
and shadowLastChange only.


Thanks for the report. I've removed the offending 'by self write' in
git. I'm not sure why that was added in the first place. The default
slapd.conf didn't have it and I didn't find any comments about it.

I don't think I'm comfortable doing an automated ACL change to existing
installs. A NEWS.Debian entry suggesting the change (and mentioning how
to do it) might be appropriate, though.


What do you think: an entry in NEWS.Debian, or a debconf notice 
(conditional on detecting a possibly-vulnerable acl)? It occurs to me 
that the users most likely to be affected by this (default settings, 
haven't reviewed acls) are also the least likely to read apt-listchanges...



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

Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC

[Bill Chatfield]

Xorg.0.log:
[29.626] 
X.Org X Server 1.16.0
Release Date: 2014-07-16
[29.626] X Protocol Version 11, Revision 0
[29.626] Build Operating System: Linux 3.2.0-4-powerpc64 ppc Debian
[29.626] Current Operating System: Linux powerbook 3.14-2-powerpc #1 Debian 
3.14.15-2 (2014-08-09) ppc
[29.626] Kernel command line: 
root=UUID=cc84edf8-5d66-4743-b12c-c1a21e26036b ro 
[29.626] Build Date: 09 September 2014  12:37:15AM
[29.626] xorg-server 2:1.16.0-2+b1 (http://www.debian.org/support) 
[29.626] Current version of pixman: 0.32.6
[29.626]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[29.626] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[29.627] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 18 00:12:07 
2014
[29.832] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[29.979] (==) No Layout section.  Using the first Screen section.
[29.979] (==) No screen section available. Using defaults.
[29.979] (**) |-->Screen "Default Screen Section" (0)
[29.979] (**) |   |-->Monitor ""
[30.044] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[30.044] (==) Automatically adding devices
[30.044] (==) Automatically enabling devices
[30.044] (==) Automatically adding GPU devices
[30.278] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[30.278]Entry deleted from font path.
[30.512] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[30.512] (==) ModulePath set to "/usr/lib/xorg/modules"
[30.512] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[30.528] (II) Loader magic: 0x20562698
[30.528] (II) Module ABI versions:
[30.528]X.Org ANSI C Emulation: 0.4
[30.528]X.Org Video Driver: 18.0
[30.528]X.Org XInput driver : 21.0
[30.528]X.Org Server Extension : 8.0
[30.530] (--) PCI:*(0:0:16:0) 1002:4e50:1002:4e50 rev 0, Mem @ 
0xb800/134217728, 0xb000/65536, I/O @ 0x0400/256, BIOS @ 
0x/131072
[30.591] (II) LoadModule: "glx"
[30.635] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[31.774] (II) Module glx: vendor="X.Org Foundation"
[31.774]compiled for 1.16.0, module version = 1.0.0
[31.774]ABI class: X.Org Server Extension, version 8.0
[31.774] (==) AIGLX enabled
[31.777] (==) Matched ati as autoconfigured driver 0
[31.777] (==) Matched modesetting as autoconfigured driver 1
[31.777] (==) Matched fbdev as autoconfigured driver 2
[31.777] (==) Assigned the driver to the xf86ConfigLayout
[31.777] (II) LoadModule: "ati"
[31.802] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[31.832] (II) Module ati: vendor="X.Org Foundation"
[31.832]compiled for 1.15.99.904, module version = 7.4.0
[31.832]Module class: X.Org Video Driver
[31.832]ABI class: X.Org Video Driver, version 18.0
[31.832] (II) LoadModule: "radeon"
[31.833] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[31.943] (II) Module radeon: vendor="X.Org Foundation"
[31.943]compiled for 1.15.99.904, module version = 7.4.0
[31.943]Module class: X.Org Video Driver
[31.943]ABI class: X.Org Video Driver, version 18.0
[31.943] (II) LoadModule: "modesetting"
[31.944] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[31.969] (II) Module modesetting: vendor="X.Org Foundation"
[31.969]compiled for 1.15.99.904, module version = 0.9.0
[31.969]Module class: X.Org Video Driver
[31.969]ABI class: X.Org Video Driver, version 18.0
[31.969] (II) LoadModule: "fbdev"
[31.970] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[31.971] (II) Module fbdev: vendor="X.Org Foundation"
[31.971]compiled for 1.15.99.904, module version = 0.4.4
[31.971]Module class: X.Org Video Driver
[31.971]ABI class: X.Org Video Driver, version 18.0
[31.971] (II) RADEON: Driver for ATI Radeon chipsets:
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
ATI Radeon Mobility X300 (M24) 3152 (PCIE),
ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI),
ATI Radeon X600 (RV380) 3E50 (PCIE),
ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
ATI Rade

Bug#762064: ITP: libpdl-graphics-gnuplot-perl -- Gnuplot-based plotting for PDL

[Dima Kogan]

Package: wnpp
Owner: Dima Kogan 
Severity: wishlist

* Package name: libpdl-graphics-gnuplot-perl
  Version : 2.003
  Upstream Author : Craig DeForest, Dima Kogan
* URL or Web page : 
https://metacpan.org/pod/distribution/PDL-Graphics-Gnuplot/README.pod
* License : perl5 (GPL or artistic)
  Description : Gnuplot-based plotting for PDL

This is a plotting package for PDL, the numerical computation
environment in perl.


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

Bug#762062: wxwidgets2.8: Should not be included in jessie

[Olly Betts]

Source: wxwidgets2.8
Version: 2.8.12.1+dfsg2-2
Severity: serious
Justification: In the package maintainer's opinion this package is unsuitable 
for release

We should not release jessie with wxwidgets2.8.

We have packages of wxwidgets3.0 and wxpython3.0 which are newer
upstream releases of the software in wxwidgets2.8, and most of the
reverse dependencies have already been migrated - by the release freeze
for jessie, we should be down to a very small number of reverse
dependencies unmigrated, most of which we have agreement to remove.

The wxWidgets library is a large and complex piece of software, and
2.8.x is unmaintained upstream.  Even before 3.0 was released, 2.8 was
neglected - the last release was 2.8.12 on 2011-03-28.  By the time
jessie releases, this release will be close to 4 years old.  By the EOL
of jessie (assuming no LTS), it'll be almost 7 years old.

The wx maintainer team in Debian is not a strong one - I've been the
only active member in recent times, though Gianfranco Costamagna has
started to get involved more recently.  Neither of us are interested
in continuing to maintain wxwidgets2.8.

Meanwhile, upstream are currently working towards a new stable release
series, with 3.2.0 slated to be released "in the beginning of 2015" -
source: http://trac.wxwidgets.org/wiki/Roadmap

Historically, upstream's prediction of release dates have tended to be
rather optimistic, but even if they're off by a whole year, we'll still
have a new upstream release series in the lifetime of jessie, which
means some applications will be wanting wxwidgets3.2 packaged in
jessie+1 because they rely on new features added in it.  And we really
don't want to be trying to maintain packages of three different upstream
releases of wx concurrently.

Cheers,
Olly


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

Bug#762061: virtualbox-dkms fails to build on standard 3.14.15 kernel

[Omar Radwan]

Package: virtualbox-dkms
Version: 4.3.14-dfsg-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

I recently got Debian installed on my laptop. Everything went smoothly,
except getting virtualbox to work was a nightmare. The virtualbox-dkms package
on Debian Testing, which at the moment is using linux 3.14, fails to build or
install.

I realized that the only way to get it working was to download a kernel
source from kernel.org, I got the 3.14.15 kernel, compile and install it
myself, then boot from it, this was the only way to get virtualbox working on
my machine. I don't think that a significant amount Debian users, which aren't
very proficient in unix-like systems, would have the expertise to compile their
own kernel and install.

After I compiled and installed the new kernel. I did "dpkg-reconfigure
virtualbox-dkms", and it compiled the package and I was able to use virtualbox.


PS: I'm using virtualbox 4.3.14



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

Kernel: Linux 3.14.15 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages virtualbox-dkms depends on:
ii  dkms2.2.0.3-1.2
ii  dpkg1.17.13
ii  virtualbox  4.3.14-dfsg-1

virtualbox-dkms recommends no packages.

virtualbox-dkms 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#762060: nodejs: non FHS config file location

[Adam Heath]

package: nodejs
version: 0.10.32-1nodesource1~wheezy1
severity: serious

==
root@HOST:~# npm config set --global proxy http://192.168.3.245:3128/
root@HOST:~# npm config list
; cli configs
registry = "https://registry.npmjs.org/";
user-agent = "npm/1.4.28 node/v0.10.32 linux x64"

; globalconfig /usr/etc/npmrc
proxy = "http://192.168.3.245:3128/";

; node bin location = /usr/bin/node
; cwd = /root
; HOME = /root
; 'npm config ls -l' to show all defaults.

==

The location of that global config is quite bad, on a debian-based 
system.  Please move it to /etc/, at the least.


I'm marking this serious, as it goes against proper debian policy.


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

Bug#760189: reopening 760189

[Josh Triplett]

reopen 760189
thanks

This bug still applies, for two reasons now: first, because it never
applied to kpartx in the first place (which has no daemons, init
scripts, or systemd services), and second, because the set of NEWS
entries now present in multipath-tools (and kpartx) effectively cancel
out: they're only relevant for people running unstable during the very
short window between the two package versions, but not for people
running stable.  People running stable do not need to see those NEWS
entries.

I would suggest dropping the entire series of systemd-related NEWS
entries at this point.

- Josh Triplett


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

Bug#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC

[Michel Dänzer]

On 18.09.2014 09:01, Bill Chatfield wrote:


I tried switching to a virtual console but got no response. I was
able to blindly enter my userid and password so that the Xfce
desktop came up, but in 8 bit color.


[...]


If I boot with the following kernel parameters I get a normal
visible session, but with software rendering. That is the
configuration under which I'm sending this bug report, so
automatically generated information might not be the same as
when the bug occurs.


Right, please provide the Xorg.0.log file and the output of dmesg 
corresponding to the bug.




 video=radeonfb:1280x854-32@60

I have determined that radeonfb is compiled into the kernel,
but drm and the newer radeon kernel modules are still
being loaded. This seems wrong, but it is a default configuration.

I'm happy to continue with the radeonfb driver since it provides
suspend/resume capabilities for my laptop. But, I'm filing the
bug because the default configuration is broken for PowerPC with
the Radeon video card. Also, I'd like to get hardware rendering working.


Hardware acceleration is only possible with radeon KMS anymore, not with 
radeonfb.



--
Earthling Michel Dänzer|  http://www.amd.com
Libre software enthusiast  |Mesa and X developer


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

Bug#734236: Brasero won't work on Debian Wheezy with LXDE desktop

[Bob Bib]

control: reassign -1 brasero
control: affects -1 lxde
control: reopen -1

2014-09-17 Len E.:
> There are 3 requirements for Brasero to work properly under LXDE
>
> i) gnome-desktop3-data and gnome-desktop-data should be installed

Looks like Brasero depends on some components
which don't get automatically pulled by "brasero" package
(while GNOME & Xfce installations provide them,
they're not provided in LXDE by default).

Do you remember the version number of Brasero
in which you've found this bug?

2014-09-16, Mateusz Łukasik:
> Package: lxde doesn't provides anything depends for Brasero.
> I want to close this bug.

In the future, if any bug is assigned to a wrong package,
please reassign it to an appropriate one,
instead of a (potentially detrimental) plain closing.


Best wishes,
Bob


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

Bug#762003: asciidoc: conffiles not removed

[Paul Wise]

On Wed, 2014-09-17 at 20:50 +0200, Joseph Herlant wrote:

> I don't understand. I already use postinst/postrm/preinst debhelpers
> files with the #DEBHELPER# token, I don't see how dh_installdeb would
> help to get through this. I'll dig a bit this way.

You are manually removing the files, dh_installdeb would move the
removals into the #DEBHELPER# token. Then you could simply remove the
scripts entirely because debhelper would automatically generate them
from the debian/asciidoc.maintscript file, more info:

http://manpages.debian.org/man0/dh_installdeb
https://en.wikipedia.org/wiki/Declarative_programming

> Are you able to reproduce that issue it in any way?

I think Jakub is right about the sequence of steps needed, but for
clarity the sequence of upgrades I took was this:

2013-11-20: 8.6.7-1 -> 8.6.9-1
2014-03-22: 8.6.9-1 -> 8.6.9-2
2014-09-17: 8.6.9-2 -> 8.6.9-3

Please try this upgrade sequence (and Jakub's one) to reproduce it.

> Are you able to check the wordpress.conf file to see if you customized
> it in any way please?

I did not, I didn't even know it was there :)

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#708132: bcache-tools ITP

[Darrick J. Wong]

Hi,

If you're interested in the bcache-status[1] tool, I'd be happy to work with
you to get (and keep) it in Debian.  I /think/ it's in the Fedora package.

(afaict the script is not in any of those git trees...)

On Wed, Sep 17, 2014 at 12:55:38PM +0100, Robie Basak wrote:
> I have some progress to report. I also think that this is ready to
> upload, though we should sort out a couple of things first.
> 
> I've added the bcache list (this is the Debian packaging bug) since
> there is a question about some of these commits that seem to be relevant
> to upstream but aren't in the upstream branch.
> 
> I've done some (functional only) testing of bcache itself with a
> colleague, and we haven't seen any major issues.
> 
> I think the packaging is good to go, though I've added a removal of one
> extraneous file and updated debian/copyright. This is in
> github.com/basak/bcache-tools. I haven't submitted any pull requests to
> avoid confusion (see below).
> 
> A colleague (James Page) is a DD and is prepared to upload, provided
> that we all agree on who will maintain the package first. I'm happy to
> step up. Who else does?
> 
> I found following all the various git trees confusing, and think we
> should resolve this soon after upload. There are three git trees I'm
> aware of, and I've added a fourth:
> 
> 1) http://evilpiepirate.org/git/bcache-tools.git
> 2) git://github.com/g2p/bcache-tools.git
> 3) git://github.com/squisher/bcache-tools.git
> 4) git://github.com/basak/bcache-tools.git

I had thought that #2 was the new upstream, but then I haven't paid attention
in a while either.

--D

[1] https://gist.github.com/djwong/6343451

> 
> Vcs-Git points to 2 (g2p). I also noted that the github branches seem to
> contain commits to the upstream source, too, that aren't present in the
> "upstream" repository (1).
> 
> Can we define which the canonical upstream source tree is, please, and
> where the canonical Debian packaging branch should be? Then we can work
> on pushing the changes back to the right places, rather than having
> scattered branches all over the place. I noticed some changes to the
> upstream source that don't appear to be in branch 1, for example.
> 
> I think it would be easiest to upload, since I think it's good to go and
> this will at least result in a definitive packaging state that we can
> work from.
> 
> In the meantime, I think branch 3 contained everything, so I cloned that
> one to add my two commits. To keep Vcs-Git correct g2p should pull my
> commits, or else we can change Vcs-Git.
> 
> So in summary:
> 
> 1) Define and agree maintainers.
> 2) g2p to pull my commits, or we agree to change Vcs-Git, or we drop
> Vcs-Git for now.
> 3) Upload. Either my colleague (James Page) can do it as he's already
> reviewed the packaging itself, or someone else. Let me know if there are
> any objections to James uploading.
> 4) Sort out which trees are canonical upstream and packaging branches,
> and push all commits to those places.
> 
> In the meantime, I'll upload to Ubuntu as I can do that straight away
> and we're quite close to release now. I hope that we can get Debian
> straightened out soon.
> 
> Robie


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

Bug#762059: apt: -v reports incorrect version number

[Dan Hill-Moses]

Package: apt
Version: 1.0.9
Severity: minor

Dear Maintainer,

In light of the recent security vulnerability, I updated from apt 1.0.8 to
1.0.9. Using the -v flag, apt is still reporting itself as 1.0.8.

$ apt -v
apt 1.0.8 for amd64 compiled on Sep 16 2014 18:06:12

$ aptitude show apt
[...]
Version: 1.0.9
[...]

Thanks for your time,
Dan



-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "true";
APT::Install-Suggests "0";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-3\.14-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-3\.2\.0-4-rt-amd64$";
APT::NeverAutoRemove:: "^linux-headers-3\.14-2-amd64$";
APT::NeverAutoRemove:: "^linux-headers-3\.2\.0-4-rt-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-3\.14-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-3\.2\.0-4-rt-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-3\.14-2-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-3\.2\.0-4-rt-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-3\.14-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-3\.2\.0-4-rt-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-3\.14-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-3\.2\.0-4-rt-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-3\.14-2-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-3\.2\.0-4-rt-amd64$";
APT::NeverAutoRemove:: "^.*-modules-3\.14-2-amd64$";
APT::NeverAutoRemove:: "^.*-modules-3\.2\.0-4-rt-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-3\.14-2-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-3\.2\.0-4-rt-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.14-2-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.2\.0-4-rt-amd64$";
APT::NeverAutoRemove:: "^linux-tools-3\.14-2-amd64$";
APT::NeverAutoRemove:: "^linux-tools-3\.2\.0-4-rt-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::Never-MarkAuto-Sections "";
APT::Never-MarkAuto-Sections:: "metapackages";
APT::Never-MarkAuto-Sections:: "restricted/metapackages";
APT::Never-MarkAuto-Sections:: "universe/metapackages";
APT::Never-MarkAuto-Sections:: "multiverse/metapackages";
APT::Never-MarkAuto-Sections:: "oldlibs";
APT::Never-MarkAuto-Sections:: "restricted/oldlibs";
APT::Never-MarkAuto-Sections:: "universe/oldlibs";
APT::Never-MarkAuto-Sections:: "multiverse/oldlibs";
APT::Update "";
APT::Update::Post-Invoke-Success "";
APT::Update::Post-Invoke-Success:: "[ ! -f /var/run/dbus/system_bus_socket ] || 
/usr/bin/dbus-send --system --dest=org.debian.apt --type=signal /org/debian/apt 
org.debian.apt.CacheChanged || true";
APT::Update::Post-Invoke-Success:: "/usr/bin/test -e 
/usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && 
/usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call 
--system --dest org.freedesktop.PackageKit --object-path 
/org/freedesktop/PackageKit --timeout 4 --method 
org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo 
> /dev/null";
APT::Architectures "";
APT::Architectures:: "amd64";
APT::Architectures:: "i386";
APT::Compressor "";
APT::Compressor::. "";
APT::Compressor::.::Name ".";
APT::Compressor::.::Extension "";
APT::Compressor::.::Binary "";
APT::Compressor::.::Cost "1";
APT::Compressor::gzip "";
APT::Compressor::gzip::Name "gzip";
APT::Compressor::gzip::Extension ".gz";
APT::Compressor::gzip::Binary "gzip";
APT::Compressor::gzip::Cost "2";
APT::Compressor::gzip::CompressArg "";
APT::Compressor::gzip::CompressArg:: "-9n";
APT::Compressor::gzip::UncompressArg "";
APT::Compressor::gzip::UncompressArg:: "-d";
APT::Compressor::bzip2 "";
APT::Compressor::bzip2::Name "bzip2";
APT::Compressor::bzip2::Extension ".bz2";
APT::Compressor::bzip2::Binary "bzip2";
APT::Compressor::bzip2::Cost "3";
APT::Compressor::bzip2::CompressArg "";
APT::Compressor::bzip2::CompressArg:: "-9";
APT::Compressor::bzip2::UncompressArg "";
APT::Compressor::bzip2::UncompressArg:: "-d";
APT::Compressor::xz "";
APT::Compressor::xz::Name "xz";
APT::Compressor::xz::Extension ".xz";
APT::Compressor::xz::Binary "xz";
APT::Compressor::xz::Cost "4";
APT::Compressor::xz::CompressArg "";
APT::Compressor::xz::CompressArg:: "-6";
APT::Compressor::xz::UncompressArg "";
APT::Compressor::xz::UncompressArg:: "-d";
APT:

Bug#762058: wine-development: Please enable WoW64 setup

[jre]

Source: wine-development
Version: 1.7.26-2
Severity: wishlist

Hi,

please enable a WoW64 setup to enable wine to run 32-bit applications in
a 64-bit wineprefix.

Has anyone already worked on this?

CC'ing Hilko Bengen who seems to have done so already (see
http://lists.alioth.debian.org/pipermail/pkg-wine-party/2013-October/003294.html).

Greets
jre


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

Bug#746272: mesa: Having the same issues as Elimar

[Rogério Brito]

Package: mesa
Followup-For: Bug #746272

Hi.

I am having the sasme issues as Elimar is having, under very similar
circumstances (with the exception that my card is a Mobility Radeon 9550,
while his is a 9600).

In particular, I can't run some programs, as they refuse to run. One example
is mpv with the driver opengl. I get, among other things:

,
| libGL error: failed to load driver: r300
| libGL error: failed to load driver: swrast
| [vo/opengl] no GLX support present
| [vo/opengl] OpenGL context creation failed!
| Error opening/initializing the selected video_out (-vo) device.
| Video: no video
| Video: no video
`

And no video appears. I can't also use other programs (desktop environments)
that need any hardware assistance.

If any further information is needed, please let me know. I don't have
access to this notebook as frequently as I'd like, though.


Thanks,

Rogério Brito.

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

Kernel: Linux 3.16-1-powerpc
Locale: LANG=en_US.utf-8, LC_CTYPE=pt_BR.utf-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

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


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

Bug#761450: Please add a d-i.debian.org pseudo package

[Cyril Brulebois]

Don Armstrong  (2014-09-17):
> On Sun, 14 Sep 2014, Cyril Brulebois wrote:
> >   d-i.debian.org -- Issues regarding the d-i.debian.org service and general 
> > Debian Installer tasks.
> 
> The pseudopackage has now been added.

Many thanks. Filed those for the moment:
  #762048 #762050 #762051 #762053 #762054 #762055 #762056 #762057

Helpful → happy.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#742561: Yet another patch for the wine script - wine64 support

[jre]

Followup-For: Bug #742561
Package: wine-development
Version: 1.7.26-2

Hi,

based on Floris' patches here another patch:

Try wine64 if
- a 64-bit executable is given as argument
  (NOTE: there are 64-bit applications with 32-bit installers, so this
  won't help everytime), or
- if the WINEPREFIX is a 64-bit
  (NOTE: don't do this once WoW64 is implemented, see
  http://wiki.winehq.org/Wine64ForPackagers.), or
- if WINEARCH is set to win64.

In all other cases use wine (32-bit).

Add error message if wine64 is requested but not found.

Greets
jre
diff --git a/debian/scripts/wine b/debian/scripts/wine
index 388f3ae..67d0db9 100755
--- a/debian/scripts/wine
+++ b/debian/scripts/wine
@@ -8,16 +8,38 @@ bindir=/usr/lib/$name
 wine32=$bindir/wine
 wine64=$bindir/wine64
 
-if test -x $wine32; then
+# Set WINEPREFIX for later use.
+if test -z $WINEPREFIX; then WINEPREFIX="$HOME/.wine"; fi
+
+# Try wine64, if
+# - a 64-bit executable is given as argument
+#   (NOTE: there are 64-bit applications with 32-bit installers, so this won't help everytime), or
+# - if the WINEPREFIX is a 64-bit
+#   (NOTE: don't do this once WoW64 is implemented, see http://wiki.winehq.org/Wine64ForPackagers.), or
+# - if WINEARCH is set to win64.
+if test -e "$1" -a "$(file -b -L "$1" | cut -d\  -f1)" = "PE32+" || \
+test -f "$WINEPREFIX/system.reg" -a "$(grep "PROCESSOR_ARCHITECTURE" $WINEPREFIX/system.reg | cut -d= -f2)" = "\"AMD64\"" || \
+test "$WINEARCH" = "win64" ; then
+if test -x $wine64; then
+	wine=$wine64
+else
+echo "error: unable to find wine64 executable."
+if [ "$(dpkg --print-architecture)" = "amd64" ]; then
+echo "as root, please execute \"apt-get install $(echo $name | sed s/wine/wine64/)\""
+else
+echo "you need $(echo $name | sed s/wine/wine64/). but this is only available on architecture amd64."
+fi
+exit 1
+fi
+# Try 32-bit wine otherwise.
+elif test -x $wine32; then
 wine=$wine32
-elif test -x $wine64; then
-wine=$wine64
+else
 if [ "$(dpkg --print-architecture)" = "amd64" -a "$(dpkg --print-foreign-architectures)" != "i386" ]; then
 echo "it looks like multiarch needs to be enabled.  as root, please"
 echo "execute \"dpkg --add-architecture i386 && apt-get update &&"
 echo "apt-get install $(echo $name | sed s/wine/wine32/)\""
 fi
-else
 echo "error: unable to find wine executable.  this shouldn't happen."
 exit 1
 fi

Bug#762057: d-i.debian.org: investigate ttf-cjk-compact generation

[Cyril Brulebois]

Package: d-i.debian.org
Severity: normal

I'm not sure what's happening here…

Trying to update ttf-cjk-compact-udeb seems to work fine, doing its
magic based on translations etc. to compute the reduced glyph sets
needed to get compact fonts files.

But some glyphs are missing, as can be seen on the very few first
g-i screens.

I've reported that here:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740151#31

but I suspect it would make sense to double check the possible delta
between what's in svn and what's in actual packages… Hence this bug
report against d-i.debian.org.

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#762056: d-i.debian.org: update jenkins job to use daily-build-overview

[Cyril Brulebois]

Package: d-i.debian.org
Severity: normal

It'd probably a good idea to update this jenkins job:
  https://jenkins.debian.net/view/d-i_misc/job/d-i_parse_build_logs/

to use this page instead:
  http://d-i.debian.org/daily-images/daily-build-overview.html


Instructions to update jenkins configuration:
  https://lists.debian.org/debian-boot/2014/09/msg00550.html

The job configuration seems to live in a separate repository though, but
patching should be easy anyway.

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#762055: d-i.debian.org: run calc-release-status regularly to catch missing tags

[Cyril Brulebois]

Package: d-i.debian.org
Severity: normal

Part of a debian-installer upload is about including a file computed
by calc-release-status; it's somewhat frustrating to see it fail
because this or that tag wasn't pushed to a repository, meaning a
failed checkout/translation lookup for said package. Then I get to
chase people instead of keeping on preparing the upload.

It would probably be a good idea to integrate that in a crontab to
help detect such issues as soon as possible, and to get a quicker
release step when everything else is ready.

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#681500: lxde: recommend audacious as a music player

[Bob Bib]

Or maybe "Recommends: lxmusic | audacious"?..


Best wishes,
Bob


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

Bug#762054: d-i.debian.org: investigate ttf-* vs. fonts-* for udebs?

[Cyril Brulebois]

Package: d-i.debian.org
Severity: normal

I'm really unsure it's a good idea but right now in jessie we have
a bunch of ttf-* udebs left, while most were renamed/introduced as
fonts-*.

I don't think it matters much (except for consistency), but there
was some request already for us to evaluate RMs after packaging got
changed (which I failed to do properly by the way) so it might make
sense to try and get that done, once and for all.

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#762053: d-i.debian.org: investigate getting published over https

[Cyril Brulebois]

Package: d-i.debian.org
Severity: normal

Everything's in the subject.

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#762052: lxde: update dependencies on deprecated packages

[Bob Bib]

Source: lxde
Source-Version: 4+nmu1
Tags: patch

Dear Maintainer,

please update dependencies on the following deprecated packages:
- lxsession-edit has been replaced by lxsession and removed (Bug#733169);
- lxpolkit has been replaced by lxsession and removed (Bug#733170);
- lxshortcut has been replaced by libfm-tools and removed (Bug#760368).


Best wishes,
Bob

--- a/debian/control
+++ b/debian/control
@@ -22,8 +22,7 @@
  to provide a desktop environment which is lightweight and fast.
  .
  This package is a metapackage depends on the recommended core components
- of the LXDE. It includes pcmanfm, lxpanel, lxsession, openbox and
- xscreensaver.
+ of the LXDE. It includes pcmanfm, lxpanel, openbox and xscreensaver.
  .
  If you just want to pick and choose the core components then feel free
  to remove this package.
@@ -33,10 +32,10 @@
 Depends:
  ${misc:Depends}, galculator, gpicview, leafpad, lxappearance,
  lxde-core, lxde-icon-theme, lxinput,
- lxrandr, lxsession-edit, lxshortcut, lxterminal, obconf, xarchiver
+ lxrandr, lxsession, libfm-tools, lxterminal, obconf, xarchiver
 Recommends:
  iceweasel | www-browser, lightdm | x-display-manager, lxmusic, menu-xdg,
- network-manager-gnome, lxpolkit, xserver-xorg
+ network-manager-gnome, xserver-xorg
 Suggests: lxlauncher, lxtask
 Description: LXDE metapackage
  LXDE (the Lightweight X11 Desktop Environment) is a project aimed
@@ -44,7 +43,7 @@
  .
  This package is a metapackage depends on the core components and
  recommended components of the LXDE. It includes lxde-core, lxappearance,
- lxinput, lxsession-edit, lxshortcut, gpicview, lxterminal, lxmusic,
+ lxinput, lxsession, libfm-tools, gpicview, lxterminal, lxmusic,
  leafpad and xarchiver.
  .
  If you just want to pick and choose the core components then feel free


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

Bug#762051: translations.txt: publish it properly (announced as utf-8)

[Cyril Brulebois]

Package: d-i.debian.org
Severity: normal

Since translations.txt support was added to dillon's crontab, it failed
to be announced as utf-8 so copying-pasting from a browser doesn't work:

  http://d-i.debian.org/translations.txt

It'd be nice if it could be announced properly.

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#762049: [dragonplayer] Unable to play an audio CD (CDDA), except for the first track

[Filipus Klutiero]

Package: dragonplayer
Version: 4:4.14.0-1
Severity: important
Tags: upstream

As reported in upstream's ticket #222844, when playing an audio CD with Dragon Player, the menu 
items "Previous Chapter" and "Next Chapter" do nothing.

Since Dragon stops playing once the first track is over, I am effectively 
unable to play tracks from an audio CD other than the first. However, this 
behavior is reportedly different for the author of the upstream ticket. I am 
using the VLC Phonon backend, 0.7.2. I am setting severity assuming that all 
Debian users are currently basically unable to play audio CDs, but if this is 
incorrect, as the upstream ticket suggests might be the case, severity could be 
re-evaluated.

--- System information. ---
Architecture: i386
Kernel: Linux 3.14-2-amd64

Debian Release: jessie/sid
990 testing debian.mirror.rafal.ca
500 unstable debian.mirror.rafal.ca
1 experimental debian.mirror.rafal.ca

--- Package information. ---
Depends (Version) | Installed
===-+-
kde-runtime (>> 4:4.10) | 4:4.14.0-2
libc6 (>= 2.4) | 2.19-11
libgcc1 (>= 1:4.1.1) | 1:4.9.1-14
libkdecore5 (>= 4:4.11) | 4:4.14.0-1
libkdeui5 (>= 4:4.11) | 4:4.14.0-1
libkio5 (>= 4:4.11) | 4:4.14.0-1
libkparts4 (>= 4:4.11) | 4:4.14.0-1
libphonon4 (>= 4:4.6.0really4.5.0) | 4:4.7.2-1
libqt4-dbus (>= 4:4.5.3) | 4:4.8.6+git64-g5dc8b2b+dfsg-2
libqtcore4 (>= 4:4.8.0) | 4:4.8.6+git64-g5dc8b2b+dfsg-2
libqtgui4 (>= 4:4.5.3) | 4:4.8.6+git64-g5dc8b2b+dfsg-2
libsolid4 (>= 4:4.11) | 4:4.14.0-1
libstdc++6 (>= 4.1.1) | 4.9.1-14
phonon | 4:4.7.2-1


Package's Recommends field is empty.

Package's Suggests field is empty.

--
Filipus Klutiero
http://www.philippecloutier.com


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

Bug#762050: kernel-summary: avoid sending notification for experimental decrufts

[Cyril Brulebois]

Package: d-i.debian.org
Severity: normal

We don't need to know that the kernel was removed from experimental
because a higher version was uploaded to experimental. Let's get a
better SNR on the list.

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#762048: kernel-summary: avoid sending notifications when rmadison fails

[Cyril Brulebois]

Package: d-i.debian.org
Severity: normal

This kind of things are annoying:
  Jul 21 Linux kernel wa (0.3K) Linux kernel ABI bump in testing: from 3.14-1 
to (none)
  Jul 21 Linux kernel wa (0.3K) Linux kernel ABI bump in unstable: from 3.14-1 
to (none)
  Jul 21 Linux kernel wa (0.3K) Linux kernel ABI bump in experimental: from 
3.16-rc5 to (none)
  Jul 22 Linux kernel wa (0.3K) Linux kernel ABI bump in testing: from (none) 
to 3.14-1
  Jul 22 Linux kernel wa (0.3K) Linux kernel ABI bump in unstable: from (none) 
to 3.14-1
  Jul 22 Linux kernel wa (0.3K) Linux kernel ABI bump in experimental: from 
(none) to 3.16-rc5

It'd be nice to catch (none) cases instead, and abort.

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#762047: xserver-xorg-video-ati: Black screen with mouse cursor on PowerPC

[Bill Chatfield]

Package: xserver-xorg-video-ati
Version: 1:7.4.0-2
Severity: important

Dear Maintainer,

   * What led up to the situation?

This happend with the default PowerPC install for Jessie "testing".

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

I tried switching to a virtual console but got no response. I was
able to blindly enter my userid and password so that the Xfce
desktop came up, but in 8 bit color.

If I run 'Xorg -configure' I get a segfault.

If I boot with the following kernel parameters I get a normal
visible session, but with software rendering. That is the
configuration under which I'm sending this bug report, so
automatically generated information might not be the same as
when the bug occurs.

video=radeonfb:1280x854-32@60

I have determined that radeonfb is compiled into the kernel,
but drm and the newer radeon kernel modules are still
being loaded. This seems wrong, but it is a default configuration.

I'm happy to continue with the radeonfb driver since it provides
suspend/resume capabilities for my laptop. But, I'm filing the
bug because the default configuration is broken for PowerPC with
the Radeon video card. Also, I'd like
to get hardware rendering working.

I can collect more info by logging in via ssh when the bug occurs.



-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Sep 14 15:37 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2494636 Sep  8 20:43 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
:00:10.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] RV350/M10 [Mobility Radeon 9600 PRO Turbo] [1002:4e50]

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 3.14-2-powerpc (debian-ker...@lists.debian.org) (gcc version 
4.8.3 (Debian 4.8.3-7) ) #1 Debian 3.14.15-2 (2014-08-09)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 22364 Sep 14 23:03 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 28598 Sep 16 14:51 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[37.150] 
X.Org X Server 1.16.0
Release Date: 2014-07-16
[37.150] X Protocol Version 11, Revision 0
[37.150] Build Operating System: Linux 3.2.0-4-powerpc64 ppc Debian
[37.151] Current Operating System: Linux powerbook 3.14-2-powerpc #1 Debian 
3.14.15-2 (2014-08-09) ppc
[37.151] Kernel command line: 
root=UUID=7f71a9ac-30da-4195-89c5-6dffcbe357b4 ro video=radeonfb:1280x854-32@60
[37.151] Build Date: 09 September 2014  12:37:15AM
[37.151] xorg-server 2:1.16.0-2+b1 (http://www.debian.org/support) 
[37.151] Current version of pixman: 0.32.6
[37.151]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[37.151] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[37.152] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Sep 16 14:51:14 
2014
[37.206] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[37.244] (==) No Layout section.  Using the first Screen section.
[37.244] (==) No screen section available. Using defaults.
[37.244] (**) |-->Screen "Default Screen Section" (0)
[37.244] (**) |   |-->Monitor ""
[37.258] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[37.258] (==) Automatically adding devices
[37.258] (==) Automatically enabling devices
[37.258] (==) Automatically adding GPU devices
[37.457] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[37.457]Entry deleted from font path.
[37.696] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[37.696] (==) ModulePath set to "/usr/lib/xorg/modules"
[37.696] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[37.725] (II) Loader magic: 0x20710698
[37.725] (II) Module ABI versions:
[37.725]X.Org ANSI C Emulation: 0.4
[37.725]X.Org Video Driver: 18.0
[37.725]X.Org XInput driver : 21.0
[37.725]X.Org Server Extension : 8.0
[37.727] (--) PCI:*(0:0:16:0) 1002:4e50:1002:4e50 rev 0, Mem @ 
0xb800/134217728, 0xb000/65536, I/O @ 0x0400/256, BIOS @ 
0x

Bug#749432: Fixed in new gnome-shell version

[ø]

Hi, Pablo.

Your output it's in Spanish, which maybe some people answering to you
can't understand. To get english output in command line, unset LANG
variable, or set it to empty string. For instance, to get english output
from your command:

$ LANG= sudo apt -t experimental install gnome-shell gdm3 gnome-session


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

Bug#762046: [youtube-dl] New version 2014.09.16.1 is out, please update

[Jens Stomber]

Package: youtube-dl
Version: 2014.08.05-1
Severity: wishlist

--- Please enter the report below this line. ---
Hi,

The actual package version does no longer work with arte+7 
http://www.arte.tv/guide/de/plus7

Please update the package to the new version 2014.09.16.1.
https://rg3.github.io/youtube-dl/download.html


regards

Jens 

--- System information. ---
Architecture: amd64
Kernel:   Linux 3.16-2.dmz.1-liquorix-amd64

Debian Release: jessie/sid
  990 testing security.debian.org 
  990 testing ftp.de.debian.org 
  980 testing debian.ids-services.de 
  500 unstableftp.de.debian.org 
  490 unstabledebian.ids-services.de 
  480 unstableliquorix.net 
  400 unstabledeb.i2p2.no 
  200 experimentalftp.de.debian.org 
  190 experimentaldebian.ids-services.de 

--- Package information. ---
Depends   (Version) | Installed
===-+-===
python-pkg-resources| 5.5.1-1
python (>= 2.7) | 2.7.8-1
python (<< 2.8) | 2.7.8-1


Recommends(Version) | Installed
===-+-
libav-tools | 6:11~beta1-2
 OR ffmpeg  | 
libav-tools | 6:11~beta1-2
 OR ffmpeg  (>= 4:0.6)  | 
 OR ffprobe | 
mplayer2| 
 OR mplayer | 3:1.1.1+20140703+svn37232-dmo1
rtmpdump| 2.4+20131018.git79459a2-4


Package's Suggests field is empty.


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

Bug#757966: RFS: lutris/0.3.4-1 [ITP]

[Eriberto]

Hi,

2014-09-17 17:41 GMT-03:00 Pierre Rudloff :
>>> 3.
>>>  - I am not sure I understand. It does use the 1.0 format.
>>>  - Where should I list the upstream authors? I don't see a field
>>> for
>>> this in the 1.0 format.
>>
>>
>>
>> You can consult any copyright in Debian packages to see an example.
>> You can use these:
>>
>>
>> http://metadata.ftp-master.debian.org/changelogs/main/n/netmate/unstable_copyright
>>
>>
>> http://metadata.ftp-master.debian.org/changelogs/main/e/ext4magic/unstable_copyright
>
> I edited the copyright file. Is it OK now?


The format is right now. However, you must to list all upstream
authors and licenses in d/copyright. See the second example above
(ext4magic). You can use this command to help you: 'grep -sriA25
copyright *'.


 6. I have added a generic README.source about quilt. Is this OK?
>>
>>
>>
>> No. My idea was talk about the original debian directory removed from
>> upstream code.
>
> I've added a sentence explaining this. Is this enough? (There is no special
> step needed, as dpkg-source -x takes care of replacing the debian folder.)

Yes. Perfect.

Cheers,

Eriberto


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

Bug#759014: RFP: bitcointrader -- Bitcoin trading application

[Dmitry Smirnov]

On Mon, 25 Aug 2014 21:05:25 Daniel Pocock wrote:
> Could this link against the OpenMAMA packages

I don't know, it is a question to upstream...

> to get real-time currency rates?

It gets real-time rates, it is one of its main features...

-- 
Regards,
 Dmitry Smirnov
 GPG key : 4096R/53968D1B


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

Bug#762025: d-e-doc: scripts get_manual fails

[Holger Levsen]

Hi, 

fellow RC bug hunters:

taffit said he would like into this issue during the weekend or maybe earlier.


cheers,
Holger


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

Bug#762044: wine: drop references to wine-doc (removed)

[Bob Bib]

Source: wine
Source-Version: 1.6.2-8

Dear Maintainer,

please remove "suggestions" of the "wine-doc" package,
as it has been removed (bug #759036).


Best wishes,
Bob


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

Bug#735390: vde2: diff for NMU version 2.3.2-4.1

[Hector Oron]

Dear maintainer,

I've prepared an NMU for vde2 (versioned as 2.3.2-4.1). The diff
is attached to this message.

Regards.

-- 
  Hector Oron
reverted:
--- vde2-2.3.2/config.log
+++ vde2-2.3.2.orig/config.log
@@ -1,382 +0,0 @@
-This file contains any messages produced by compilers while
-running configure, to aid debugging if configure makes a mistake.
-
-It was created by vde2 configure 2.3.2, which was
-generated by GNU Autoconf 2.68.  Invocation command line was
-
-  $ /root/vde2-2.3.2/./configure --build=aarch64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --libexecdir=${prefix}/lib/vde2 --srcdir=. --disable-maintainer-mode --disable-dependency-tracking --disable-silent-rules --enable-experimental --disable-python
-
-## - ##
-## Platform. ##
-## - ##
-
-hostname = arm-arm-02
-uname -m = aarch64
-uname -r = 3.16.0
-uname -s = Linux
-uname -v = #4 SMP Thu Aug 21 08:46:48 UTC 2014
-
-/usr/bin/uname -p = unknown
-/bin/uname -X = unknown
-
-/bin/arch  = unknown
-/usr/bin/arch -k   = unknown
-/usr/convex/getsysinfo = unknown
-/usr/bin/hostinfo  = unknown
-/bin/machine   = unknown
-/usr/bin/oslevel   = unknown
-/bin/universe  = unknown
-
-PATH: /usr/local/sbin
-PATH: /usr/local/bin
-PATH: /usr/sbin
-PATH: /usr/bin
-PATH: /sbin
-PATH: /bin
-
-
-## --- ##
-## Core tests. ##
-## --- ##
-
-configure:2642: checking for a BSD-compatible install
-configure:2710: result: /usr/bin/install -c
-configure:2721: checking whether build environment is sane
-configure:2771: result: yes
-configure:2912: checking for a thread-safe mkdir -p
-configure:2951: result: /bin/mkdir -p
-configure:2964: checking for gawk
-configure:2994: result: no
-configure:2964: checking for mawk
-configure:2980: found /usr/bin/mawk
-configure:2991: result: mawk
-configure:3002: checking whether make sets $(MAKE)
-configure:3024: result: yes
-configure:3180: checking for g++
-configure:3196: found /usr/bin/g++
-configure:3207: result: g++
-configure:3234: checking for C++ compiler version
-configure:3243: g++ --version >&5
-g++ (Debian/Linaro 4.9.1-14) 4.9.1
-Copyright (C) 2014 Free Software Foundation, Inc.
-This is free software; see the source for copying conditions.  There is NO
-warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-
-configure:3254: $? = 0
-configure:3243: g++ -v >&5
-Using built-in specs.
-COLLECT_GCC=g++
-COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/4.9/lto-wrapper
-Target: aarch64-linux-gnu
-Configured with: ../src/configure -v --with-pkgversion='Debian/Linaro 4.9.1-14' --with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.9 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libsanitizer --disable-libquadmath --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-arm64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-arm64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-arm64 --with-arch-directory=arm64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-multiarch --enable-checking=release --build=aarch64-linux-gnu --host=aarch64-linux-gnu --target=aarch64-linux-gnu
-Thread model: posix
-gcc version 4.9.1 (Debian/Linaro 4.9.1-14) 
-configure:3254: $? = 0
-configure:3243: g++ -V >&5
-g++: error: unrecognized command line option '-V'
-g++: fatal error: no input files
-compilation terminated.
-configure:3254: $? = 4
-configure:3243: g++ -qversion >&5
-g++: error: unrecognized command line option '-qversion'
-g++: fatal error: no input files
-compilation terminated.
-configure:3254: $? = 4
-configure:3274: checking whether the C++ compiler works
-configure:3296: g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.cpp  >&5
-configure:3300: $? = 0
-configure:3348: result: yes
-configure:3351: checking for C++ compiler default output file name
-configure:3353: result: a.out
-configure:3359: checking for suffix of executables
-configure:3366: g++ -o conftest -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.cpp  >&5
-configure:3370: $? = 0
-configure:3392: result: 
-configure:3414: checking whether we are cross compiling
-configure:3422: g++ -o conftest -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -Wl,-z,relro conftest.cpp  >&5
-configure:3426: $? = 0
-configure:3433:

Bug#708132: bcache-tools ITP

[David Mohr]

About the licensing & copyright: I emailed Gabriel and Kent Overstreet 
on 2014-06-02 but did not get a reply. I admit though that I didn't 
follow up afterwards.


On 2014-09-17 05:55, Robie Basak wrote:

As far as I know this is the status of the git trees:


1) http://evilpiepirate.org/git/bcache-tools.git


Original sources, no changes in a while.


2) git://github.com/g2p/bcache-tools.git


First clone by Gabriel, contains work and bugfixes to the bcache-tools 
userland and some initial Debian packaging.



3) git://github.com/squisher/bcache-tools.git


My work on Debian packaging. I set Vcs-Git to g2p's version instead of 
mine because that seems to be the most active upstream repository. I 
thought this was relevant for uscan, but obviously I was wrong (as was 
pointed out on mentors.debian.net).



4) git://github.com/basak/bcache-tools.git


Vcs-Git points to 2 (g2p). I also noted that the github branches seem 
to

contain commits to the upstream source, too, that aren't present in the
"upstream" repository (1).


I thought that (1) is historic at this point and considered (2) the 
upstream. I did not verify that though.


I would suggest to co-maintain the package on 
https://alioth.debian.org/projects/collab-maint


I think it would be easiest to upload, since I think it's good to go 
and

this will at least result in a definitive packaging state that we can
work from.


Fine by me.

In the meantime, I think branch 3 contained everything, so I cloned 
that

one to add my two commits. To keep Vcs-Git correct g2p should pull my
commits, or else we can change Vcs-Git.


Right, see above.


So in summary:

1) Define and agree maintainers.


I'd like to get my feet wet and co-maintain, if you're interested.


2) g2p to pull my commits, or we agree to change Vcs-Git, or we drop
Vcs-Git for now.


I'd say point it at 3) or at collab-maint, if that's where the packaging 
ends up being.



3) Upload. Either my colleague (James Page) can do it as he's already
reviewed the packaging itself, or someone else. Let me know if there 
are

any objections to James uploading.


Bernd Zeimetz, I added him to the CC, was willing to sponsor the package 
once it was ready. But since he has been pretty busy recently, I don't 
think he'll object to James uploading. I definitely don't; it'd be 
awesome to get this finally into the official repository!



4) Sort out which trees are canonical upstream and packaging branches,
and push all commits to those places.


I very much agree.

~David


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

Bug#762043: jenkins-job-builder: Configured triggers break job updating

[intrigeri]

Package: jenkins-job-builder
Version: 0.8.1-0.1
Severity: normal

Hi,

on a Jessie system with Jenkins installed from sid, a job that has:

triggers:
  - pollscm: '@daily'
  - timed: '@daily'

... triggers the following log when running `jenkins-jobs update
/etc/jenkins_jobs/jobs build_Tails_ISO_feature-jessie':

Sep 17, 2014 4:12:52 PM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn

Error while serving 
http://127.0.0.1:8080/job/build_Tails_ISO_feature-jessie/config.xml
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1484)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1484)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1484)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1484)
at 
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1476)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:429)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:370)
at 
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)
at 
org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:982)
at 
org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1043)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
at 
org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at 
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:696)
at 
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:53)
 

Bug#718803: josm only shows blank main window after start with OpenJDK 7

[Antoine Beaupré]

Package: awesome
Version: 3.4.15-1+b1
Followup-For: Bug #718803

JOSM also completely fails here. export _JAVA_AWT_WM_NONREPARENTING=1
workaround works.

This seems to be a known bug with awesome ... or java... or both. See:

https://awesome.naquadah.org/wiki/Problems_with_Java

Maybe it would be time (after two years??) to give 3.5 a try?

A.

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

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

Versions of packages awesome depends on:
ii  dbus-x11  1.8.6-2
ii  libc6 2.19-10
ii  libcairo2 1.12.16-3
ii  libdbus-1-3   1.8.6-2
ii  libev41:4.15-3
ii  libglib2.0-0  2.40.0-5
ii  libimlib2 1.4.6-2
ii  liblua5.1-0   5.1.5-7
ii  libpango1.0-0 1.36.6-1
ii  libstartup-notification0  0.12-4
ii  libx11-6  2:1.6.2-3
ii  libx11-xcb1   2:1.6.2-3
ii  libxcb-icccm4 0.4.1-1
ii  libxcb-image0 0.3.9-2
ii  libxcb-keysyms1   0.3.9-2
ii  libxcb-randr0 1.10-3
ii  libxcb-render01.10-3
ii  libxcb-shape0 1.10-3
ii  libxcb-shm0   1.10-3
ii  libxcb-util0  0.3.8-3
ii  libxcb-xinerama0  1.10-3
ii  libxcb-xtest0 1.10-3
ii  libxcb1   1.10-3
ii  libxcursor1   1:1.1.14-1
ii  libxdg-basedir1   1.2.0-1
ii  menu  2.1.47

Versions of packages awesome recommends:
ii  feh2.12-1
ii  rlwrap 0.37-5
ii  x11-xserver-utils  7.7+3

awesome 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#762041: systemd: upgrading systemd results in /run/user/ being emptied

[brian m. carlson]

Package: systemd
Version: 215-4
Severity: important

I just upgraded to systemd 215-4 from whatever was in unstable as of a
couple days ago.  I then tried to sign a git commit, and got:

  vauxhall ok % git commit -sS
  
  You need a passphrase to unlock the secret key for
  user: "brian m. carlson "
  4096-bit RSA key, ID 1F52F68B, created 2007-05-14 (main key ID 0223B187)
  
  can't connect to `/run/user/1000/keyring/gpg': No such file or directory
  gpg: can't connect to `/run/user/1000/keyring/gpg': connect failed

And now that directory is just about empty (it was empty until some
other package's upgrade completed):

  vauxhall ok % ls -l /run/user/1000
  total 0
  drwx-- 2 bmc bmc 60 Sep 17 22:45 dconf

I had this issue on another sid system the other day where my SSH agent
disappeared, and since I rely on forwarding my SSH agent to push commits
at work, I was suddenly unable to perform any useful work until I logged
out and logged back in again.

The appropriate time to clear /run and /var/run is at boot.  systemd
should not remove (or cause to be removed) anything under /run/user at
any other time, as doing so breaks things.

For reference, after logging out and logging back in, the following
directories are available:

  vauxhall ok % ls -l /run/user/1000
  total 0
  drwx-- 2 bmc bmc  60 Sep 17 23:01 dconf
  dr-x-- 2 bmc bmc   0 Sep 17 23:00 gvfs
  drwx-- 2 bmc bmc 120 Sep 17 23:00 keyring
  drwx-- 2 bmc bmc  40 Sep 17 23:01 pulse

-- Package-specific info:

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

Kernel: Linux 3.16-trunk-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

Versions of packages systemd depends on:
ii  acl 2.2.52-2
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-53.4
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1
ii  libblkid1   2.20.1-5.8
ii  libc6   2.19-11
ii  libcap2 1:2.24-4
ii  libcap2-bin 1:2.24-4
ii  libcryptsetup4  2:1.6.6-1
ii  libgcrypt11 1.5.4-3
ii  libkmod218-1
ii  liblzma55.1.1alpha+20120614-2
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
ii  libsystemd0 215-4
ii  sysv-rc 2.88dsf-53.4
ii  udev215-4
ii  util-linux  2.20.1-5.8

Versions of packages systemd recommends:
ii  dbus1.8.8-1
ii  libpam-systemd  215-4

Versions of packages systemd suggests:
pn  systemd-ui  

-- Configuration Files:
/etc/systemd/system.conf changed:
[Manager]
LogLevel=warning
LogTarget=console


-- no debconf information

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

Bug#726492: debian-edu: Task files are specifying a lot of not existing / renamed packages

[Bob Bib]

Version: 1.724

Was curious what keeps depending on old wine-doc package...
Here a small patch to start with.


Best wishes,
Bob

-

--- a/tasks/desktop-other
+++ b/tasks/desktop-other
@@ -411,7 +411,7 @@
 Responsible: ?
 NeedConfig:  ?
 
-Suggests:gnuplot, geg
+Suggests:gnuplot
 Why: Graph plotting programs.  gnuplot was requested by math teacher.
 Responsible: ?
 NeedConfig:  no
@@ -434,7 +434,7 @@
 Responsible: ?
 NeedConfig:  no
 
-Depends: inkscape | sodipodi
+Depends: inkscape
 Recommends:  gimp, gimp-data-extras, gimp-ufraw
 Suggests:kolourpaint, kpaint, netpbm, gv, dia
 Ignore:  gimp-help-cs, gimp-help-de, gimp-help-en, gimp-help-fr, \
@@ -579,7 +579,7 @@
 Responsible: Petter Reinholdtsen
 NeedConfig:  No
 
-Suggests:wine, wine-doc, libwine-alsa, libwine-oss
+Suggests:wine
 Why: Run MS Windows applications.
 Responsible: ?
 NeedConfig:  ?
@@ -594,7 +594,7 @@
 Responsible: Petter Reinholdtsen
 NeedConfig:  no
 
-Ignore:  ted, mgp
+Ignore:  mgp
 Why: Presentasjonsverktøy
 Responsible: ?
 NeedConfig:  no


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

Bug#758996: closed by Joseph Bisch (Bug#758996: fixed in winetricks 0.0+20140818+svn1202-1)

[Joseph Bisch]

On Sun, Sep 14, 2014 at 3:49 PM, Tomas Janousek  wrote:
> On Sun, Sep 14, 2014 at 02:43:00PM -0400, Joseph Bisch wrote:
>> I think the problem is bigger than it initially appears. The patch
>> Andrey provides seems to only work for i386, not amd64. The
>> wine-development package only provides wine-development[0], whereas
>> wine provides wine[1]. Winetricks searches for a wine executable, not
>> the wine-development executable. The wine32-development package
>> provides a wine executable, which isn't provided by
>> wine64-development, which is why this only affects amd64, not i386. I
>> have attached a patch that appears to fix the wine-development issue
>> by searching for wine-development if wine can't be found.
>
> Well, wine32-development does provide a wine executable, but not in $PATH, so
> I don't think it matters and it should work equally well (or not well at all)
> on both architectures.  I happen to have a i386 system and a "wine" in $PATH
> that execs wine-development, and when I remove it, winetricks complains that
>
> --
> WINE is wine, which is neither on the path nor an executable file
> --
>
> So I think that there's no amd64-specific problem and your patch isn't needed.

Line 3762[0] executes "which wine", which works with
wine32-development, because it provides a wine executable, but not
wine64-development, because that provides a wine64 executable. So on
amd64 I get the "WINE is wine, which is neither on the path nor an
executable file" without my patch. I guess this should be a separate
bug report. And the patch probably should be sent upstream.

> That being said, the logic in winetricks_init is likely wrong, as it tries
> "wine" first, but wineserver is searched in wine-{development,unstable} path
> first.  That might go horribly wrong if both wine and wine-development is
> installed (which it isn't on this box).  :-(
>
> I am not sure what the correct solution is.  I'm starting to think that
> extending both of those error messages to tell the user to correctly set
> _both_ WINE and WINESERVER environment variables might be the only safe
> option (I'd even go as far as to never look for wine-{development,unstable}
> wineserver).  And, as the comment suggests, persuade Debian wine maintainers
> to put wineserver back in path, ideally using alternatives so that it's easy
> to switch between wine and wine-development.

I agree that telling the user to set WINE and WINESERVER environment
variables sounds like a good option. And at the same time persuading
Debian wine maintainers to put wineserver in path.


[0] - 
https://code.google.com/p/winetricks/source/browse/trunk/src/winetricks#3762

Cheers,
Joseph


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

Bug#762039: smartd does not starts under systemd

[Gianluigi Tiesi]

Package: smartmontools
Version: 6.2+svn3841-1.2
Severity: normal

When using systemd, smartd does not starts, systemd logs says the daemon exists 
normally,
as it was one-shot.

Regards


-- Package-specific info:
Output of /usr/share/bug/smartmontools:
Couldn't parse /boot/config-3.14-0.bpo.2-amd64

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

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

Versions of packages smartmontools depends on:
ii  debianutils  4.4
ii  libc62.19-11
ii  libcap-ng0   0.7.4-2
ii  libgcc1  1:4.9.1-14
ii  libselinux1  2.3-2
ii  libstdc++6   4.9.1-14
ii  lsb-base 4.1+Debian13

Versions of packages smartmontools recommends:
pn  mailx | mailutils  

Versions of packages smartmontools suggests:
pn  gsmartcontrol   
pn  smart-notifier  

-- 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#762040: opennebula: Build depends on libxmlrpc-c++4-dev which is no longer built

[Emilio Pozuelo Monfort]

Source: opennebula
Version: 3.4.1-4.1
Severity: serious

Your package build depends on libxmlrpc-c++4-dev which is no longer built by
xmlrpc-c. You probably want to build depend on libxmlrpc-c++8-dev now.

Emilio


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

Bug#762038: systemd spins up stand-by disks at shutdown

[Gianluigi Tiesi]

Package: systemd
Severity: minor

Hi,
sda is my system SSD.
I've also have an hard disk (sdb),
I always spin down sdb using hdparm -y /dev/sdb
to reduce noise and increase longevity of the disk.

When using systemd, in the shutdown process the disks spins-up
just before the computer powers off.

The disk is always umounted.

Regards


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

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

Versions of packages systemd depends on:
pn  acl 
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-53.4
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1
ii  libblkid1   2.20.1-5.8
ii  libc6   2.19-11
ii  libcap2 1:2.24-4
ii  libcap2-bin 1:2.24-4
pn  libcryptsetup4  
ii  libgcrypt11 1.5.4-3
pn  libkmod2
ii  liblzma55.1.1alpha+20120614-2
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
pn  libsystemd0 
ii  sysv-rc 2.88dsf-53.4
pn  udev
ii  util-linux  2.20.1-5.8

Versions of packages systemd recommends:
pn  dbus
pn  libpam-systemd  

Versions of packages systemd suggests:
pn  systemd-ui  


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

Bug#762037: race in udev root device detection leaves root mounted read-only

[Gianluigi Tiesi]

Package: systemd
Severity: important

Hi,
after upgrading systemd/udev to version 215-4, my system starts degraded
because root remains read-only. I cannot easly see early messages,
delaying the boot with an fsck or debug on commandline does not exposes the 
problem.

The problem does not occurs using sysvinit-core

Regards


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

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

Versions of packages systemd depends on:
pn  acl 
ii  adduser 3.113+nmu3
ii  initscripts 2.88dsf-53.4
ii  libacl1 2.2.52-2
ii  libaudit1   1:2.4-1
ii  libblkid1   2.20.1-5.8
ii  libc6   2.19-11
ii  libcap2 1:2.24-4
ii  libcap2-bin 1:2.24-4
pn  libcryptsetup4  
ii  libgcrypt11 1.5.4-3
pn  libkmod2
ii  liblzma55.1.1alpha+20120614-2
ii  libpam0g1.1.8-3.1
ii  libselinux1 2.3-2
pn  libsystemd0 
ii  sysv-rc 2.88dsf-53.4
pn  udev
ii  util-linux  2.20.1-5.8

Versions of packages systemd recommends:
pn  dbus
pn  libpam-systemd  

Versions of packages systemd suggests:
pn  systemd-ui  


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

Bug#759044: tribler: Please update to use wxpython3.0

[Olly Betts]

Control: severity -1 serious
# Justification: blocks the on-going wxpython3.0 transition

[NB: If you just mail nnn...@bugs.debian.org, that doesn't get sent on
to the submitter - I only saw your reply because I happened to check the
BTS web interface.  You can explicitly CC:
nn-submit...@bugs.debian.org to send email to the submitter too.]

On Mon, Sep 15, 2014 at 11:28:18AM +0800, Ying-Chun Liu (PaulLiu) wrote:
> I need some help on this.
> After running wx-migration-tools, I got a patch as attachment.

I've already attached an nmudiff to this bug, in which I've addressed
this issue:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759044#12

That patch also turns off the wxdebug assertion checks which would avoid
the issue reported in #760552.

So please start from that patch rather than throwing away my work on
this and then asking me how to fix problems I already sent you the fix
for.

> However, it doesn't simply transit to wxpy3.0 because I get the
> following error messages when installing the packages:
> 
> 設定 tribler (6.3.1+git20140902.9a5a2604-1) ...
>   File "/usr/share/tribler/Tribler/Main/Dialogs/SaveAs.py", line 241
> dlg = wx.DirDialog(None, "Please select a directory to save this
> torrent", style=wx.0)
> 
> ^
> SyntaxError: invalid syntax

This is because the existing code is rather bogus:

dlg = wx.DirDialog(None, "Please select a directory to save this 
torrent", style=wx.wx.DD_NEW_DIR_BUTTON)

Note the double prefix: "wx.wx." - this happens to work, but isn't right
- it should be just wx.DD_NEW_DIR_BUTTON.  But this flag is deprecated
and set to 0 in both 2.8 and 3.0, so it is best to just remove it
entirely (that way you won't need to update the code when the flag gets
removed, which will probably happen in wxPython 3.2).

This is why the update script changes wx.DD_NEW_DIR_BUTTON to 0 for you
(it's much easier to get it to replace such flags with a literal 0 than
to get it to actually remove them from the code entirely).

Cheers,
Olly


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

Bug#761911: [debian-mysql] Bug#761911: mariadb-server-core-5.5: MariaDB lacks documentation of OpenSSL exception to GPL

[Clint Byrum]

Excerpts from Otto Kekäläinen's message of 2014-09-17 13:02:46 -0700:
> Hello!
> 
> The copyright file at
> http://anonscm.debian.org/cgit/pkg-mysql/mariadb-5.5.git/tree/debian/copyright
> already includes in the comment a paragraph about "FOSS License
> Exception" and on line 111 OpenSSL is specifically mentioned.
> 
> This is perhaps the wrong format?
> 
> Is this bug report a reminder to yourself to look at the issue some
> day (you have commit rights to the repo and you are the author of the
> above mentioned paragraph) or do you want me to do something? I am
> happy to help, I am not just sure what I am expected to do here.
> 

The above mentioned stuff was about the client libraries, and not about
the server daemon.

Quoting from the copyright file:

 MySQL FOSS License Exception We want free and open source
 software applications under certain licenses to be able to use
 specified GPL-licensed MySQL client libraries despite the fact
 that not all such FOSS licenses are compatible with version
 2 of the GNU General Public License.  Therefore there are
 special exceptions to the terms and conditions of the GPLv2
 as applied to these client libraries, which are identified
 and described in more detail in the FOSS License Exception at
 .

Note _GPL-licensed MySQL client libraries_.

This does not cover the server process.

> 
> Should I add to line 134 the parapraph below?
> **
>  On Debian based systems the full text of the GNU General Public License 
> version
>  2 can be found in the file `/usr/share/common-licenses/GPL-2`.
>  .
>  In addition, as a special exception, the copyright holders give
>  permission to link the code of portions of this program with the
>  OpenSSL project's "OpenSSL" library (or with modified versions of it
>  that use the same license as the "OpenSSL" library), and distribute
>  the linked executables.  You must obey the GNU General Public License
>  in all respects for all of the code used other than "OpenSSL".  If you
>  modify this file, you may extend this exception to your version of the
>  file, but you are not obligated to do so.  If you do not wish to do
>  so, delete this exception statement from your version.
> **

Where did this text come from?

> 
> About cyassl: I am working on it to find out the correct "-DWITH_SSL=" syntax.


It's entirely possible that it won't work, as YaSSL and CYaSSL are
slightly different, but both implement an OpenSSL compatible API.

We can table that if we have actual copyright holder permission to link
OpenSSL to MariaDB's server process, which I wasn't aware we had.


signature.asc
Description: PGP signature

Bug#762036: nut-nutrition: File conflict with nut-nutrition-data on upgrade

[David Mohr]

Package: nut-nutrition
Version: 20.1-1
Severity: important

Dear Maintainer,

I just ran a dist-upgrade and it fails on nut-nutrition-data:

Selecting previously unselected package nut-nutrition-data.
Preparing to unpack .../nut-nutrition-data_20.1-1_all.deb ...
Unpacking nut-nutrition-data (20.1-1) ...
dpkg: error processing archive
/var/cache/apt/archives/nut-nutrition-data_20.1-1_all.deb (--unpack):
 trying to overwrite '/usr/share/nut-nutrition/WEIGHT.lib', which is
 also in package nut-nutrition 19.2-1

Of course there is an easy workaround:
$ dpkg -r nut-nutrition && apt-get install nut-nutrition

Thanks,
~David

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

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

Versions of packages nut-nutrition depends on:
ii  libc6   2.19-11
ii  nut-nutrition-data  20.1-1

nut-nutrition recommends no packages.

nut-nutrition 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#761796: torsocks: DNS complains

[Lunar]

Control: retitle -1 Add an option to whitelist networks
Control: severity -1 wishlist
Control: forwarded -1 https://bugs.torproject.org/13184

tester:
>doing an update , flash need to download, source and build
> 
> WARNING torsocks[12360]: [connect] Connection to a local address are denied
> since it might be a TCP DNS query to a local DNS server. Rejecting it for
> safety reasons. (in tsocks_connect() at connect.c:177)
> 
> It refused localhost is my DNS going through tor, this work fine on an earlier
> build of torsocks

That's a security feature. What's missing is a way to whitelist your
particular DNS resolver, as there is no way for torsocks to know that
it's safe to use.

-- 
Lunar.''`. 
lu...@debian.org: :Ⓐ  :  # apt-get install anarchism
`. `'` 
  `-   


signature.asc
Description: Digital signature

Bug#762035: gnome-icon-theme: Please mark package as Multi-Arch: foreign

[David Kozub]

Package: gnome-icon-theme
Version: 3.12.0-1
Severity: wishlist

Dear Maintainer,

currently it's not possible to install i386 packages that depend on 
gnome-icon-theme
in amd64 Debian. This means it's impossible to install many i386 GUI 
applications.
For example, trying to install simple-scan:i386 results in the following error 
message
from aptitude:

* simple-scan:i386 depends on gnome-icon-theme:i386 [UNAVAILABLE]

Discussing the issue in OFTC IRC (#debian) I was pointed to "Multi-Arch: 
foreign" as a
possible solution.

I rebuilt gnome-icon-theme with "Multi-Arch: foreign" locally and it solved the 
issue
for me.

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

Kernel: Linux 3.17.0-rc3bug (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnome-icon-theme depends on:
ii  hicolor-icon-theme  0.13-1
ii  libgtk-3-bin3.12.2-3+b1
ii  librsvg2-common 2.40.3-2

gnome-icon-theme recommends no packages.

gnome-icon-theme 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#712787: ITP for Distkeys

[Martin Steigerwald]

Am Mittwoch, 17. September 2014, 17:47:29 schrieb Eriberto:
> Hi Martin,

Hi Eriberto,

> About your package, please:
> 
> 1. Use DH 9 instead DH 8.
> 
> 2. d/control:
> - Change Priority from 'extra' to 'optional'.
> - The Homepage field and VCS point to a site that says 'The
> project you're trying to access has been archived'.

Changed to github already in a re-uploaded distkeys package (dput -f).

> 3. d/copyright:
> - In header, the field 'Source' is wrong.
> - The 'AUTHORS' file says: 'Licensed unter GPL-2. See COPYING.'.
> So, the upstream code is GPL-2, not 2+. Note the word 'unter'. :-)

Hmmm, I see. I think back then I intended GPL-2+, so may change AUTHORS file.

> - Your year as packager should be 2013.
> 
> 4. d/rules: please, remove all comments (from '# -*- makefile' up to
> 'verbose mode').
> 
> 5. You will need update the Homepage address. Can your current
> homepage allow scans from d/watch file?

Also added a uscan file.

Will come to the other things next week when I am in office again, I think.

> Thanks for your work.

Thanks for your review.

> Cheers,
> 
> Eriberto

Ciao,
Martin

> 2014-09-17 6:34 GMT-03:00 Martin Steigerwald :
> > tags 712787 -moreinfo
> > thanks
> > 
> > Am Mittwoch, 10. September 2014, 09:07:04 schrieb Eriberto Mota:
> >> tags 712787 moreinfo
> >> thanks
> >> 
> >> 
> >> Hi Martin,
> > 
> > HI Eriberto,
> > 
> >> You didn't put the ITP number in d/changelog.
> > 
> > Did so now.
> > 
> >> To make easier the review, please, upload your package to
> >> mentors.debian.net.
> > 
> > Uploaded to
> > 
> > http://mentors.debian.net/package/distkeys
> > 
> > and hanged status to needs a sponsor.
> > 
> > Thanks,
> > Martin
> > 
> >> Thanks,
> >> 
> >> Eriberto
> >> 
> >> 2014-04-22 5:28 GMT-03:00 Martin Steigerwald :
> >> > ITP finally went through after Don added some additional stripping to
> >> > the
> >> > mail parsing.
> >> > 
> >> > ITP: distkeys -- Distkeys - upload SSH keys to servers and more
> >> > http://bugs.debian.org/745478
> >> > 
> >> > Thanks,
> > 
> > ]…}
> > 
> > 
> > 
> > --
> > Martin Steigerwald  | Consultant / Trainer
> > 
> > teamix GmbH
> > Südwestpark 43
> > 90449 Nürnberg
> > 
> > Tel.:  +49 911 30999 55 | Fax: +49 911 30999 99
> > mail: martin.steigerw...@teamix.de | web:  http://www.teamix.de | blog:
> > http://blog.teamix.de
> > 
> > Amtsgericht Nürnberg, HRB 18320 | Geschäftsführer: Oliver Kügow, Richard
> > Müller

-- 
Martin SteigerwaldMail: m...@teamix.net
Systemadministrator   Fon:  +49 (0)911 30999-0
team(ix) GmbH Fax:  +49 (0)911 30999-99
Süd-West-Patk 35, 90449 Nürnberg, Deutschland


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

Bug#759060: [o...@survex.com: Bug#759060: invesalius: Partial patch for wxPython 3.0]

[Olly Betts]

On Mon, Sep 15, 2014 at 04:32:21PM -0300, Thiago Franco Moraes wrote:
> I tested it here inside a VM.

The vtk maintainer asked me to just NMU my fix, so you should now be
able to just test in unstable.

> It's working now! Thanks! There are some problems with the widgets
> layouts and placements, but everything seems to work. I'll try to
> solve these problems.

There are two issues I am aware of which can affect these sort of things
(but probably others too):

The first is that in wxGTK 2.8, SetSize() and GetSize() for a
wxTopLevelWindow (and subclasses) returned the "client size", but in 3.0
they now return the size including window decorations.  At least some
other ports previously included the window decorations, so applications
tested on other platforms tend to get this right, but for stuff only
tested on Linux, calculated window sizes can be wrong.  Using
SetClientSize() and GetClientSize() where you don't want the size of any
window decorations to be included is the fix (and should work in 2.8
too).

The other is a bug in the height of wxSearchCtrl, which is fixed in wx
trunk but still waiting for a fix in 3.0 (I think the trunk fix can't
just be applied):

http://trac.wxwidgets.org/ticket/16422

It's probably better not to try to work around that, as you're likely
to just create more problems once it gets fixed.  I'm hoping we'll
get 3.0.2 in for jessie, and that this will include a fix for this.

Cheers,
Olly


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

Bug#762034: ITP: node-hicat -- cat with syntax highlighting.

[Leo Iannacone]

Package: wnpp
Severity: wishlist
Owner: Leo Iannacone 
X-Debbugs-CC: debian-de...@lists.debian.org

* Package name: node-hicat
  Version : 0.6.1
  Upstream Author : Rico Sta. Cruz 
* URL : https://github.com/rstacruz/hicat
* License : Expat
  Programming Lang: JavaScript
  Description : cat with syntax highlighting.
 The language is auto-detected through the file extension or 
 inferred from the contents if piped to hicat.
 .
 Node.js is an event-based server-side JavaScript engine.


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

Bug#761327: [INTL:tr] Turkish program translation of apt-listbugs

[Mert Dirik]

On 09/17/2014 01:00 AM, Francesco Poli wrote:

[...]


Thanks a lot for your contribution.
I've just pushed the updated translation to the public git repository:
it will be part of the next upload of the package.

Bye!

You're welcome. It will be great to see apt-listbugs in Turkish. Thanks 
for maintaining this great little program, I would be bitten by so many 
RC bugs so far without it :)



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

Bug#762033: node-highlight: incompatible with nodejs module name: highlight.js

[Leo Iannacone]

Source: node-highlight
Severity: important

Dear Maintainer,

This package must be renamed (and installed properly) to
node-highlight.js according with upstream module name (see
package.json).

Please, rename it asap.

Leo.

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

Kernel: Linux 3.13.0-35-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


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

Bug#760558: pu: package libsnmp-session-perl/1.13-1

[Julien Cristau]

Control: tag -1 confirmed

On Fri, Sep  5, 2014 at 11:26:13 +0100, Adam D. Barratt wrote:

> Package: release.debian.org
> Severity: wishlist
> User: release.debian@packages.debian.org
> Usertags: pu
> Tags: wheezy
> X-Debbugs-CC: libsnmp-session-p...@packages.debian.org
> 
> Hi,
> 
> I'd like to fix #628804 in stable, which causes a lot of noise from mrtg
> when libsocket6-perl is installed; a debdiff is attached.
> 
> We've been running packages containing the fix at $dayjob for a couple of
> months with no issues.
> 
> I pinged the bug report a few weeks ago but have not received a {,n}ack.
> I've X-Debbugs-CCed the maintainers in case they wish to comment.
> 
Feel free to upload.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#762032: cryptsetup: cryptroot fails on lvm if device isn't ready in time

[Niall Walsh]

Package: cryptsetup
Version: 2:1.6.6-1
Severity: normal

With the rootfs on lvm on crypt on lvm on a usb device the system can (will) 
fail to boot if the usb device has not appeared in time.

The lvm initramfs-tools script will just call lvm lvchange for the root device, 
but in this case the root device is /dev/mapper/cryptvg-root which cannot be 
seen until the crypt device has been setup.

The cryptsetup initramfs-tools script will run activate_vg if the cryptsource 
does not exist, but if the device it is on is not present yet this won't help.

If the cryptsouce still does not exist then the rootdelay loop will be run, but 
this does nothing more then wait for the device to appear.  Simply adding 
activate_vg inside this loop (e.g. on the line after the "/bin/sleep 0.1") will 
make the system bring up the prompt for the crypt devices password and then 
boot up.   The debsums error below is due to that addition.

The above "fix" creates a lot of noise as each loop before the device appears 
will trigger a couple of lines of "no volume groups found".

Sorry if I missed anything and thanks for your work,

Niall

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.16-2.slh.3-aptosid-amd64 root=/dev/mapper/cryptvg-root ro 
cryptopts=source=/dev/mapper/vg-crypt,target=cryptroot,lvm=cryptvg-root quiet

-- /etc/crypttab
# 
cryptroot   /dev/mapper/vg-cryptnoneluks

-- /etc/fstab
UUID=47120949-a8f4-46a2-9abc-98fc6279a912 /bootext4 
defaults,relatime,errors=remount-ro   02   
UUID=6d78821a-9796-4fa4-b643-64b67e73d31a /ext4 
defaults,relatime,errors=remount-ro   01   

-- lsmod
Module  Size  Used by
cpufreq_stats   3535  0 
cpufreq_conservative 6616  0 
cpufreq_powersave982  0 
af_packet  29254  2 
intel_agp  11016  0 
bochs_drm  15505  2 
ttm62823  1 bochs_drm
drm_kms_helper 41134  1 bochs_drm
drm   233783  5 ttm,bochs_drm,drm_kms_helper
syscopyarea 3438  1 bochs_drm
sysfillrect 3674  1 bochs_drm
sysimgblt   2159  1 bochs_drm
i2c_piix4   8649  0 
fuse   78742  1 
i2c_core   21182  3 drm,i2c_piix4,drm_kms_helper
intel_gtt  12280  1 intel_agp
pcspkr  1891  0 
processor  23745  0 
evdev  11032  4 
pvpanic 1675  0 
psmouse85762  0 
serio_raw   4393  0 
button  4568  0 
parport_pc 29663  1 
ppdev   5638  0 
lp  9883  0 
parport29749  3 lp,ppdev,parport_pc
autofs422913  2 
ext4  343217  2 
crc16   1319  1 ext4
jbd2   58309  1 ext4
mbcache 8795  1 ext4
xts 3063  1 
gf128mul5722  1 xts
algif_skcipher  6091  0 
af_alg  4916  1 algif_skcipher
sd_mod 38684  2 
crc_t10dif  1095  1 sd_mod
crct10dif_generic   1429  1 
crct10dif_common1332  2 crct10dif_generic,crc_t10dif
uas16266  0 
usb_storage47348  2 uas
dm_crypt   16399  1 
dm_mod 80028  12 dm_crypt
md_mod102656  0 
sg 22108  0 
sr_mod 14871  0 
cdrom  27134  1 sr_mod
ata_generic 3394  0 
pata_acpi   3283  0 
xhci_hcd   99281  0 
ehci_pci3624  0 
ehci_hcd   42430  1 ehci_pci
usbcore   163179  5 uas,usb_storage,ehci_hcd,ehci_pci,xhci_hcd
ata_piix   24944  0 
usb_common  1608  1 usbcore
libata166437  3 pata_acpi,ata_generic,ata_piix
e1000 101292  0 
scsi_mod  153282  6 sg,uas,usb_storage,libata,sd_mod,sr_mod
floppy 58764  0 


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

Kernel: Linux 3.16-2.slh.3-aptosid-amd64 (SMP w/6 CPU cores; PREEMPT)
Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages cryptsetup depends on:
ii  cryptsetup-bin 2:1.6.6-1
ii  debconf [debconf-2.0]  1.5.53
ii  dmsetup2:1.02.90-1
ii  libc6  2.19-11

Versions of packages cryptsetup recommends:
ii  busybox 1:1.22.0-8
ii  console-setup   1.112
ii  initramfs-tools [linux-initramfs-tool]  0.116
ii  kbd 1.15.5-1

Versions of packages cryptsetup suggests:
ii  dosfstools  3.0.26-3
pn  keyutils
ii  liblocale-gettext-perl  1.05-8+b1

-- debconf information:
  c

Bug#745012: NMU fixing bugs #745012 and #758010

[Aurelien Jarno]

Hi,

I have just done an NMU to fix bugs #745012 and #758010. Please find the
diff attached.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru python-shogun-3.2.0/debian/changelog python-shogun-3.2.0/debian/changelog
--- python-shogun-3.2.0/debian/changelog	2014-08-10 05:14:52.0 +0200
+++ python-shogun-3.2.0/debian/changelog	2014-09-17 23:30:26.0 +0200
@@ -1,3 +1,11 @@
+python-shogun (3.2.0-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build depend on libjson-c-dev instead of libjson-c2-dev (Closes: #745012,
+  #758010).
+
+ -- Aurelien Jarno   Wed, 17 Sep 2014 23:30:19 +0200
+
 python-shogun (3.2.0-5) unstable; urgency=low
 
   * Build depend on libjson-c2-dev instead of libjson-c-dev (Closes: #745012)
diff -Nru python-shogun-3.2.0/debian/control python-shogun-3.2.0/debian/control
--- python-shogun-3.2.0/debian/control	2014-08-10 05:14:52.0 +0200
+++ python-shogun-3.2.0/debian/control	2014-09-17 23:30:46.0 +0200
@@ -5,7 +5,7 @@
 Build-Depends: libatlas-base-dev [!powerpc !alpha !arm !armel !armhf !sh4] | liblapack-dev,
  libeigen3-dev, debhelper (>= 9), libreadline-dev | libreadline5-dev, libblas-dev,
  libglpk-dev, libnlopt-dev, libshogun-dev (>= 3.2.0~), liblzo2-dev, zlib1g-dev, liblzma-dev,
- libxml2-dev, libjson-c2-dev | libjson0-dev, cmake, libarpack2-dev, libsnappy-dev,
+ libxml2-dev, libjson-c-dev | libjson0-dev, cmake, libarpack2-dev, libsnappy-dev,
  libhdf5-dev (>= 1.8.8~) | libhdf5-serial-dev, swig3.0 (>= 3.0.2-1~),
  python-numpy (>= 1:1.7.1-1~), python-all-dev (>= 2.7.0-1~),
  libprotobuf-dev, protobuf-compiler, libcurl4-gnutls-dev, libbz2-dev, libcolpack-dev,

Bug#762003: asciidoc: conffiles not removed

[Jakub Wilk]

* Joseph Herlant , 2014-09-17, 18:43:
I don't understand how that could be possible as the following line is 
already in the d/postinst, d/postrm and d/preinst files:


 dpkg-maintscript-helper rm_conffile \
  /etc/asciidoc/wordpress.conf 8.6.9-1~ -- "$@"


The version number is wrong, because the removal code was added only in 
8.6.9-2.


From the dpkg-maintscript-helper(1) manpage: "If the conffile has not 
been shipped for several versions, and you are now modifying the 
maintainer scripts to clean up the obsolete file,  should 
be based on the version of the package that you are now preparing, not 
the first version of the package that lacked the conffile."


This sequence of upgrades reproduces the bug:
8.6.7-1 -> 8.6.9-1 -> 8.6.9-3

--
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#736173: lvextend segfault - narrowing it down

[Alasdair G Kergon]

On Wed, Sep 17, 2014 at 01:44:52PM -0700, Mike Bird wrote:
> Version: 2.02.95-8
 
>From an upstream point of view, that's a pretty old release now
and there have been numerous improvements and fixes to the
relevant allocation code.

Two choices:

  Use a more up-to-date version and there's a good chance you'll find the bug
  got fixed.

  Extend the metadata manually using vgcfgbackup, editing the text file
  to add the segment you need, and vgcfgrestore.

Alasdair


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

Bug#734568: munge: diff for NMU version 0.5.11-1.1

[Ana Guerrero Lopez]

Control: tags 734568 + pending
Control: tags 753643 + patch
Control: tags 753643 + pending

Dear maintainer,

I've prepared an NMU for munge (versioned as 0.5.11-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.
diff -Nru munge-0.5.11/debian/changelog munge-0.5.11/debian/changelog
--- munge-0.5.11/debian/changelog	2013-11-01 12:19:33.0 +0100
+++ munge-0.5.11/debian/changelog	2014-09-17 23:21:02.0 +0200
@@ -1,3 +1,17 @@
+munge (0.5.11-1.1) unstable; urgency=medium
+
+  [ Rémi Palancher ]
+  * Non-maintainer upload.
+  * Fix post-installation by generating new key in case none existed
+previously. (Closes: #753643)
+  * Updated README.Debian with instructions for key management
+  * Bumped Standards-Version to 3.9.5
+
+  [ Ana Beatriz Guerrero Lopez ]
+  * Use dh-autoreconf to fix FTBFS on ppc64el. (Closes: #734568)
+
+ -- Ana Beatriz Guerrero Lopez   Wed, 17 Sep 2014 23:21:01 +0200
+
 munge (0.5.11-1) unstable; urgency=low
 
   * New upstream release (Closes: #727467)
diff -Nru munge-0.5.11/debian/control munge-0.5.11/debian/control
--- munge-0.5.11/debian/control	2013-10-31 18:27:00.0 +0100
+++ munge-0.5.11/debian/control	2014-09-17 23:18:44.0 +0200
@@ -2,8 +2,8 @@
 Section: admin
 Priority: extra
 Maintainer: Gennaro Oliva 
-Build-Depends: debhelper (>= 7.0.0), autotools-dev, po-debconf, dpkg-dev (>= 1.13.19), zlib1g-dev, libbz2-dev, libgcrypt11-dev
-Standards-Version: 3.9.4.0
+Build-Depends: debhelper (>= 7.0.0), dh-autoreconf, po-debconf, dpkg-dev (>= 1.13.19), zlib1g-dev, libbz2-dev, libgcrypt11-dev
+Standards-Version: 3.9.5
 Homepage: http://munge.googlecode.com/
 
 Package: munge
diff -Nru munge-0.5.11/debian/postinst munge-0.5.11/debian/postinst
--- munge-0.5.11/debian/postinst	2013-10-31 18:27:00.0 +0100
+++ munge-0.5.11/debian/postinst	2014-09-17 23:24:59.0 +0200
@@ -27,6 +27,10 @@
   if [ -e /etc/munge/munge.key ] ; then
 chown munge:munge /etc/munge/munge.key
 chmod 0400 /etc/munge/munge.key
+  else
+/usr/sbin/create-munge-key
+echo "Please refer to /usr/share/doc/munge/README.Debian"\
+ "for instructions to generate more secure key."
   fi
 ;;
 
diff -Nru munge-0.5.11/debian/README.Debian munge-0.5.11/debian/README.Debian
--- munge-0.5.11/debian/README.Debian	2013-10-31 18:27:00.0 +0100
+++ munge-0.5.11/debian/README.Debian	2014-09-17 23:17:31.0 +0200
@@ -1,12 +1,20 @@
-To use munge, you need to create a secret key file /etc/munge/munge.key,
-you can run the create-munge-key script as root to generate a random
-key or follow the instructions in QUICKSTART.
+Munge daemon needs a secret key file /etc/munge/munge.key.
 
-You need to securely propagate the secret key file (eg, via ssh) to
-other hosts within the same security realm. Credentials are valid only
-within a security realm (ie, on hosts sharing the same secret key). All
-munged daemons exchanging credentials need to share the same secret key.
+If not existing previously, the package generates a new key at
+installation time. In order to minimize the generation time, the
+generator does not use a random number generator with a very good
+source of entropy. In order to generate stronger key with better
+entropy, you are advised to run the following command as root:
+
+  # create-munge-key -f -r
 
 If the secret key file is created or copyed before the package is
 installed, the installation script will accept the key instead of
 generating a new one.
+
+Then follow the instructions in QUICKSTART.
+
+You need to securely propagate the secret key file (eg, via ssh) to
+other hosts within the same security realm. Credentials are valid only
+within a security realm (ie, on hosts sharing the same secret key). All
+munged daemons exchanging credentials need to share the same secret key.
diff -Nru munge-0.5.11/debian/rules munge-0.5.11/debian/rules
--- munge-0.5.11/debian/rules	2013-11-01 12:11:54.0 +0100
+++ munge-0.5.11/debian/rules	2014-09-17 23:19:20.0 +0200
@@ -32,6 +32,7 @@
 
 config.status: configure
 	dh_testdir
+	dh_autoreconf
 	# Add here commands to configure the package. 
 	CPPFLAGS="$(shell dpkg-buildflags --get CPPFLAGS)" LDFLAGS="$(shell dpkg-buildflags --get LDFLAGS)" CFLAGS="$(CFLAGS) -Wl,-z,defs" ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info --localstatedir=/var --sysconfdir=/etc --with-crypto-lib=libgcrypt
 
@@ -61,6 +62,7 @@
 	# Add here commands to clean up after the build process.
 	[ ! -f Makefile ] || $(MAKE) distclean
 
+	dh_autoreconf_clean
 	dh_clean 
 
 install: install-indep install-arch

Bug#761057: missing license in debian/copyright

[Alan W. Irwin]

To Thorsten and also the Debian packagers for PLplot (and with a CC to Rafael
for whom there is a question below):

I am not a Debian developer or maintainer, but nevertheless I wanted
to comment on this Debian PLplot bug report in my role as long-term
upstream lead developer for both the build system and documentation
generation for this software.

It appears to me this bug report can very simply be answered with an
upstream change to the wording in the Copyright file (also copied to
debian/copyright) to the effect that all files in the source tree
unless specifically mentioned as exceptions in the Copyright file are
licensed under the LGPL.  That idea is implied by the current wording
in the Copyright file and also has been well understood by all PLplot
developers since I joined the project in 2000, but it probably needs
to be stated explicitly in our Copyright file so that Debian, Fedora,
etc., packagers will no longer have to deal with any more bug reports
like this one.

@Andrew.  Since this change would be completely non-controversial,
please go ahead and commit that wording tweak to the Copyright file
upstream (in your role as one of the core PLplot developers), and I
think in your role as the Debian packager for PLplot, you could apply
this same non-controversial patch to that effect for PLplot-5.10.0.

The rest of this is likely off-topic, but Thorsten seems keen on
this aspect so it might have some relevancy.

In an ideal free software world for at least text files, it is a
well-know "would-be-nice" to include some copyright information.  And
clearly such information is lacking in a well-defined subset of the
files in the doc subdirectory of PLplot, and regardless of whether
this issue is relevant to the current bug report or not, I believe
this issue should ultimately be dealt with upstream.

There are currently two general issues of this nature in the
files in the doc tree.

(1) The static man pages (doc/*.1).  All of those were written by
Rafael (whom I have CC'd) long ago when he was a co-leader (along with
me) for the generation of PLplot documentation.  However, he did not
state the license for these files explicitly in each file at that
time, and I certainly also did not notice that issue until now.

@Rafael (it's been a while we were last in contact so I CC'd you with
two possible e-mail addresses): Do you agree with this summary for the
historical origin of these static man pages, and do you give your
agreement that there should (1a) be an explicit license embedded in those
man page files, and also (1b) present in the pages displayed by the man
application? If so, I know one way to deal with (1a) which is to
prepend

.\"
.\" Copyright (C) 2001-2004 Rafael Laboissiere 
.\"
.\" This program is free software; [plus the remainder of the license
boilerplate]

to each of these man page files.  Of course, for (1b) I would use the
.SH COPYRIGHT macro to generate essentially the same wording in the
version displayed by the man application.  And, of course, another
sub-issue (1c) is what license to adopt?  I believe it is simplest
that for these static man pages we should use the same documentation
license text (adapted from the FreeBSD Documentation License) that the
PLplot team jointly decided (at your urging) was best for embedding in
the docbook files themselves and also in results generated from them.
Do you agree with this choice?  If so, I would do the implementation,
and send you the git commit URL so you can see exactly what I have
done.  Of course, the final sub-issue (1d) is the Copyright file has
to be tweaked to explain the licensing of these man pages, but I can
deal with that as well.


(2) The doxygen-generated files in doc/doxygen.  Those files are
generated by a doxygen command that I configured as part of our build
system (with results copied back from the build tree to source tree
for tarball releases). 
I propose to deal with embedded file copyright

and display copyright issues similarly to what I have proposed above
for (1a) through (1d).

The only caveat to that approach that I am aware of is I currently
don't know the ideal way to deal with issue (2a) (so that, e.g, the
html files generated by doxygen have an html embedded comment
concerning their licensing).  There may be a way to implement that
with appropriate doxygen configuration, but if not I can always fall
back to using a sed script.  There is a documented way to configure
doxygen to deal with issue (2b) (so that, e.g., html browsers of the
html files display the copyright information). For issue (2c) I plan
to use the same license wording for doxygen generated results as we
currently use for the docbook source files and results, and
appropriate tweaks to the Copyright file (issue 2d) are trivial.

To summarize, I think immediately answering this bug report with a
non-controversial tweak to the Copyright file should be trivial, and
in addition for upstream (and possibly to help answer the bug report
if relevant) I

Bug#761974: [INTL:sv] Swedish strings for ircd-hybrid debconf

[Dominic Hargreaves]

On Wed, Sep 17, 2014 at 02:11:05PM +0200, Martin Bagge wrote:
> package: ircd-hybrid
> severity: wishlist
> tags: patch l10n
> 
> Please consider to add this file to translation of debconf.

On Wed, Sep 17, 2014 at 05:53:34PM +0200, Anders Jonsson wrote:
> Hi Martin,
> saw two minor issues in this debconf as well:
> 
> >innebär att kompabilitet med hybserv försvinner.
> 
> The correct spelling is "kompatibilitet".
> 
> 
> >vill du troligen inte installerat detta paket
> 
> Here "installerat" should only be "installera".

Thanks both, I've applied these updates to the git repository.

Cheers,
Dominic.


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

Bug#750331: setools: diff of the NMU

[Aurelien Jarno]

Hi,

I have done an NMU to fix bugs #750331 and #753515. Please find the diff
attached.

Aurelien


-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru setools-3.3.8/debian/changelog setools-3.3.8/debian/changelog
--- setools-3.3.8/debian/changelog	2013-12-27 17:44:13.0 +0100
+++ setools-3.3.8/debian/changelog	2014-09-17 22:33:49.0 +0200
@@ -1,3 +1,18 @@
+setools (3.3.8-3.1) unstable; urgency=medium
+
+  [ Aurelien Jarno ]
+  * Non-maintainer upload.
+
+  [ Andreas Florath ]
+  * secmds/replcon.cc: Fixed prototype of lsetfilecon_raw.
+(Closes: #750331)
+
+  [ Breno Leitao ]
+  * debian/libsefs4.symbols.ppc64el: link to the ppc64 symbols file.
+(Closes: #753515)
+
+ -- Aurelien Jarno   Wed, 17 Sep 2014 22:33:48 +0200
+
 setools (3.3.8-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru setools-3.3.8/debian/libsefs4.symbols.ppc64el setools-3.3.8/debian/libsefs4.symbols.ppc64el
--- setools-3.3.8/debian/libsefs4.symbols.ppc64el	1970-01-01 01:00:00.0 +0100
+++ setools-3.3.8/debian/libsefs4.symbols.ppc64el	2013-12-27 17:44:13.0 +0100
@@ -0,0 +1,138 @@
+libsefs.so.4 libsefs4 #MINVER#
+ VERS_4.0@VERS_4.0 3.3.4.ds
+ _ZN10sefs_entryC1EP11sefs_fclistPK17sefs_context_nodejPKcS6_@VERS_4.0 3.3.4.ds
+ _ZN10sefs_entryC1EPKS_@VERS_4.0 3.3.4.ds
+ _ZN10sefs_entryC2EP11sefs_fclistPK17sefs_context_nodejPKcS6_@VERS_4.0 3.3.4.ds
+ _ZN10sefs_entryC2EPKS_@VERS_4.0 3.3.4.ds
+ _ZN10sefs_entryD1Ev@VERS_4.0 3.3.4.ds
+ _ZN10sefs_entryD2Ev@VERS_4.0 3.3.4.ds
+ _ZN10sefs_query11objectClassEPKc@VERS_4.0 3.3.4.ds
+ _ZN10sefs_query11objectClassEj@VERS_4.0 3.3.4.ds
+ _ZN10sefs_query3devEPKc@VERS_4.0 3.3.4.ds
+ _ZN10sefs_query4pathEPKc@VERS_4.0 3.3.4.ds
+ _ZN10sefs_query4roleEPKc@VERS_4.0 3.3.4.ds
+ _ZN10sefs_query4typeEPKcb@VERS_4.0 3.3.4.ds
+ _ZN10sefs_query4userEPKc@VERS_4.0 3.3.4.ds
+ _ZN10sefs_query5inodeEm@VERS_4.0 3.3.4.ds
+ _ZN10sefs_query5rangeEPKci@VERS_4.0 3.3.4.ds
+ _ZN10sefs_query5regexEb@VERS_4.0 3.3.4.ds
+ _ZN10sefs_query7compileEv@VERS_4.0 3.3.4.ds
+ _ZN10sefs_queryC1Ev@VERS_4.0 3.3.4.ds
+ _ZN10sefs_queryC2Ev@VERS_4.0 3.3.4.ds
+ _ZN10sefs_queryD1Ev@VERS_4.0 3.3.4.ds
+ _ZN10sefs_queryD2Ev@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfile10appendFileEPKc@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfile10parse_lineEPKcS1_P17re_pattern_bufferS3_@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfile11runQueryMapEP10sefs_queryPFiP11sefs_fclistPK10sefs_entryPvES7_@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfile14appendFileListEPK11apol_vector@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfileC1EPFvPvPK11sefs_fclistiPKcPcES0_@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfileC1EPK11apol_vectorPFvPvPK11sefs_fclistiPKcPcES3_@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfileC1EPKcPFvPvPK11sefs_fclistiS1_PcES2_@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfileC2EPFvPvPK11sefs_fclistiPKcPcES0_@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfileC2EPK11apol_vectorPFvPvPK11sefs_fclistiPKcPcES3_@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfileC2EPKcPFvPvPK11sefs_fclistiS1_PcES2_@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfileD0Ev@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfileD1Ev@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fcfileD2Ev@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fclist10getContextEPKcS1_S1_S1_@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fclist10getContextEPc@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fclist15associatePolicyEP11apol_policy@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fclist8runQueryEP10sefs_query@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fclistC1E16sefs_fclist_typePFvPvPKS_iPKcPcES1_@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fclistC2E16sefs_fclist_typePFvPvPKS_iPKcPcES1_@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fclistD0Ev@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fclistD1Ev@VERS_4.0 3.3.4.ds
+ _ZN11sefs_fclistD2Ev@VERS_4.0 3.3.4.ds
+ _ZN15sefs_filesystem10getDevNameEm@VERS_4.0 3.3.4.ds
+ _ZN15sefs_filesystem11buildDevMapEv@VERS_4.0 3.3.4.ds
+ _ZN15sefs_filesystem11runQueryMapEP10sefs_queryPFiP11sefs_fclistPK10sefs_entryPvES7_@VERS_4.0 3.3.4.ds
+ _ZN15sefs_filesystem12isQueryMatchEPK10sefs_queryPKcS4_PK6stat64P11apol_vectorP14apol_mls_range@VERS_4.0 3.3.4.ds
+ _ZN15sefs_filesystem8getEntryEPK17sefs_context_nodejPKcmS4_@VERS_4.0 3.3.4.ds
+ _ZN15sefs_filesystemC1EPKcPFvPvPK11sefs_fclistiS1_PcES2_@VERS_4.0 3.3.4.ds
+ _ZN15sefs_filesystemC2EPKcPFvPvPK11sefs_fclistiS1_PcES2_@VERS_4.0 3.3.4.ds
+ _ZN15sefs_filesystemD0Ev@VERS_4.0 3.3.4.ds
+ _ZN15sefs_filesystemD1Ev@VERS_4.0 3.3.4.ds
+ _ZN15sefs_filesystemD2Ev@VERS_4.0 3.3.4.ds
+ _ZN7sefs_db11runQueryMapEP10sefs_queryPFiP11sefs_fclistPK10sefs_entryPvES7_@VERS_4.0 3.3.4.ds
+ _ZN7sefs_db12upgradeToDB2Ev@VERS_4.0 3.3.4.ds
+ _ZN7sefs_db14getContextNodeEPK10sefs_entry@VERS_4.0 3.3.4.ds
+ _ZN7sefs_db4isDBEPKc@VERS_4.0 3.3.4.ds
+ _ZN7sefs_db4saveEPKc@VERS_4.0 3.3.4.ds
+ _ZN7sefs_db8getEntryEPK17sefs_context_nodejPKcmS4_@VERS_4.0 3.3.4.ds
+ _ZN7sefs_dbC1EP15sefs_filesystemPFvPvPK11sefs_fclistiPKcPcES2_@VERS_4.0 3.3.4.ds
+ _ZN7sefs_dbC1EPKcPFvPvPK11sefs_fclistiS1_PcES2_@VERS_4.0 3.3.4.ds
+ _ZN7sefs_dbC2EP15sefs_filesystemPFvPvPK11sefs_fclistiPKcPcES2_@VERS_4.0 3.3.4.ds
+ _ZN7sefs_dbC2EPKcPFvPvPK11sefs_fclistiS1_PcES2_@VERS

Bug#762031: debian-security-support: Please use interest-noawait for your trigger

[Raphael Hertzog]

On Wed, 17 Sep 2014, Raphaël Hertzog wrote:
> An "interest /usr" trigger means that any package installing a file in
> /usr will be marked as triggers-noawait instead of being immediately
 
 I meant "triggers-awaited"
> configured.

-- 
Raphaël Hertzog ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/


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

Bug#734236: closed by Mateusz Łukasik (Re: Brasero won't work on Debian Wheezy with LXDE desktop)

[Len E.]

Matuesz:

Since originally reporting this problem, I've belatedly
discovered a solution, when I was working with Debian-7.5.0-LXDE
last May.

There are 3 requirements for Brasero to work properly under LXDE

  i) gnome-desktop3-data and gnome-desktop-data should be installed

 ii) in the file /usr/share/applications/brasero-nautilus.desktop,
 change OnlyShowIn=GNOME;   to   NotShowIn=TDE;
 (I never use the Trinity desktop, so this change forces
  brasero-nautilus to be active for any desktop in actual use).

iii)  when starting a CD/DVD burning operation with brasero, do NOT
  preload the CD/DVD drive with a blank CD/DVD.  Only load the
  drive when brasero prompts for the CD/DVD.

With these 3 conditions met, I've had consistent, reliable operation
of brasero under LXDE.

Len Jarvis

*

On Tue, 16 Sep 2014 21:03:05 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the lxde package:
> 
> #734236: Brasero won't work on Debian Wheezy with LXDE desktop
> 
> It has been closed by Mateusz Łukasik .
> 
> 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 Mateusz Łukasik 
>  by
> replying to this email.
> 
> 
> -- 
> 734236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734236
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems


-- 
Len E. 


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

Bug#761947: systemd: Upgrade fails due to conflict with systemd-shim 8-1

[Paul Menzel]

Dear Martin,


thank you for your quick response!


Am Mittwoch, den 17.09.2014, 10:25 +0200 schrieb Martin Pitt:
> Version: 8-2
> 
> Control: reassign 76194 systemd-shim 8-1
> 
> Paul Menzel [2014-09-17  9:29 +0200]:
> > Dear Debian folks,
> > 
> > 
> > running `aptitude safe-upgrade`, systemd failed to upgrade because
> > systemd-shim conflicts with systemd >= 205.
> > 
> > systemd-shim (8-1) beschädigt systemd (>= 209) und ist
> > installiert.
> 
> This was fixed yesterday in systemd-shim 8-2, which works with systemd >= 209.

That is great, but it does not fix the error of broken upgrade path to
my knowledge. Users might experience that bug when systemd 215-4
migrates to testing before systemd-shim 8-2.

In my opinion, unfortunately systemd needs to have a line similar to:

Breaks: systemd-shim (<< 8-2)

I have no idea why aptitude did not figure that out itself by the
systemd-shim meta data.

Are you going to reassign to systemd or should I do it?


Thanks,

Paul


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

Bug#761819: apt-cacher-ng stores AdminAuth password insecurely

[Eduard Bloch]

tags 761819 +upstream +confirmed
thanks

Hallo,
* christoph [Tue, Sep 16 2014, 11:50:55AM]:
> Package: apt-cacher-ng
> Version: 0.7.11-2
> Severity: wishlist
> 
> Dear Maintainer,
> 
> it would be nice if apt-cacher-ng stored only the hash of the
> AdminAuth password in /etc/apt-cacher/ng/security.conf

I agree. However I first need to get 0.8 released ASAP and then I would
care about this feature.

Regards,
Eduard.


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

Bug#748878: RFS: mwc/1.7.2-1 ITP

[Eriberto Mota]

tags 748878 moreinfo
thanks


Hi again Jörg,

I am ready to review your package. Can you update the package to make
easier my review?

Cheers,

Eriberto


2014-05-21 15:29 GMT-03:00 Jörg Frings-Fürst :
> Package: sponsorship-requests
> Severity: normal
>
>   Dear mentors,
>
>   I am looking for a sponsor for my package "mwc"
>
>  * Package name: mwc
>Version : 1.7.2-1
>Upstream Author : Michael Till Beck 
>  * URL : https://github.com/Debianguru/MailWebsiteChanges
>  * License : GPL-2.0+, GPL-3.0+
>Section : utils
>
>   It builds those binary packages:
>
> mwc   - Powerful website-tracking tool
>
>   To access further information about this package, please visit the 
> following URL:
>
>   http://mentors.debian.net/package/mwc
>
>
>   Alternatively, one can download the package with dget using this command:
>
> dget -x http://mentors.debian.net/debian/pool/main/m/mwc/mwc_1.7.2-1.dsc
>
>   Changes since the last upload:
>
>* Initial release
>
>
>   Regards,
>Jörg Frings-Fürst
>
>
> --
> pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8  EBCB 422B 44B0 BE58 1B6E
> pgp Key: BE581B6E
> CAcert Key S/N: 0E:D4:56
>
> Jörg Frings-Fürst
> D-54526 Niederkail
>
> IRC: j_...@freenode.net
>  j_...@oftc.net
>
>
>
>


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

Bug#762031: debian-security-support: Please use interest-noawait for your trigger

[Raphaël Hertzog]

Package: debian-security-support
Version: 2014.09.07
Severity: normal

An "interest /usr" trigger means that any package installing a file in
/usr will be marked as triggers-noawait instead of being immediately
configured.

This is counter-productive given that debian-security-support doesn't
bring anything to those packages and they have no reason to wait until
debian-security-support's trigger is applied...

Thus please use "interest-noawait" instead of  "interest". Beware that
this directive is not supported in oldstable (it has been introduced in
dpkg 1.16.1), you will have to change that for backports to squeeze.


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

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

Versions of packages debian-security-support depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.53
ii  gettext-base   0.19.2-2

debian-security-support recommends no packages.

debian-security-support suggests no packages.

-- debconf information:
  debian-security-support/ended:
* debian-security-support/limited:


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

Bug#762030: make manual pages in libopts25-dev reproducible

[Helmut Grohne]

Package: libopts25-dev
Version: 1:5.18.3-6
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

When building autogen twice, the manual pages in libopts25-dev differ,
because autogen embeds the build time. This prevents libopts25-dev from
becoming M-A:same (see #762019) and counters the goal to have
reproducible builds, see https://wiki.debian.org/ReproducibleBuilds.
Please consider applying the attached patch or updating autogen to
5.18.4, which flip the default for "dne" to "-d", such that this patch
becomes unnecessary.

Helmut
diff -Nru autogen-5.18.3/debian/changelog autogen-5.18.3/debian/changelog
--- autogen-5.18.3/debian/changelog 2014-08-06 19:47:48.0 +0200
+++ autogen-5.18.3/debian/changelog 2014-09-17 22:56:33.0 +0200
@@ -1,3 +1,10 @@
+autogen (1:5.18.3-6.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * Make manual pages in libopts25-dev reproducible. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 17 Sep 2014 22:28:37 +0200
+
 autogen (1:5.18.3-6) unstable; urgency=medium
 
   * Bump build-dep on guile-2.0-dev to a version without #701861.
diff -Nru autogen-5.18.3/debian/patches/reproducible.diff 
autogen-5.18.3/debian/patches/reproducible.diff
--- autogen-5.18.3/debian/patches/reproducible.diff 1970-01-01 
01:00:00.0 +0100
+++ autogen-5.18.3/debian/patches/reproducible.diff 2014-09-17 
22:56:16.0 +0200
@@ -0,0 +1,20 @@
+From: Helmut Grohne 
+Subject: make manual pages in libopts25-dev reproducible
+Last-Update: 2014-09-17
+
+Do not include the build time and autogen version in manual pages in
+libopts25-dev.
+
+Index: autogen-5.18.3/autoopts/tpl/agman3.tpl
+===
+--- autogen-5.18.3.orig/autoopts/tpl/agman3.tpl2014-01-10 
20:20:57.0 +0100
 autogen-5.18.3/autoopts/tpl/agman3.tpl 2014-09-17 22:38:23.791488877 
+0200
+@@ -55,7 +55,7 @@
+ ;; The following "dne" argument is a string of 5 characters:
+ ;; '.' '\\' '"' and two spaces.  It _is_ hard to read. "
+ ;;
+-(dne ".\\\"  ")
++(dne "-d" ".\\\"  ")
+ 
+ +}
+ .SH NAME
diff -Nru autogen-5.18.3/debian/patches/series 
autogen-5.18.3/debian/patches/series
--- autogen-5.18.3/debian/patches/series2014-08-06 19:46:57.0 
+0200
+++ autogen-5.18.3/debian/patches/series2014-09-17 22:19:45.0 
+0200
@@ -2,3 +2,4 @@
 02_fix_hurd_identifiermacro.diff
 03_no_rpath_multiarch.diff
 10_handle_grep_error.diff
+reproducible.diff

Bug#736173: lvextend segfault - narrowing it down

[Mike Bird]

Version: 2.02.95-8

No errors from badblocks, pvck, vgck, lvck, fsck.

I have to use -i1 and specify PV /dev/sdb6 as LVM wants to use
PV /dev/sda6 which doesn't have the 64 free extents I need.

However if I ask for only 1 extent the lvextend works with sda6
but still segfaults with sdb6.

Tried all alloc policies - no change.

Tried --noudevsync - no change.

Tried creating new empty /etc/lvm/{backup,archive} - no change.

The segfault occurs even with -t.

Here's the last part of -vvv output before the segfault.  The
"leaving 0" seems to be an unrelated logging error as it is also
shown when lvextend is successful


  Extending logical volume IMS+++ to 130.00 GiB
  Extending segment type, striped
Allowing allocation on /dev/sda6 start PE 2048 length 683
Trying allocation using contiguous policy.
Still need 64 total extents:
  1 (1 data/0 parity) parallel areas of 64 extents each
  0 mirror logs of 0 extents each
Considering allocation area 1 as /dev/sda6 start PE 2048 length 683 
leaving 0.
Trying allocation using cling policy.
Still need 64 total extents:
  1 (1 data/0 parity) parallel areas of 64 extents each
  0 mirror logs of 0 extents each
Considering allocation area 1 as /dev/sda6 start PE 2048 length 683 
leaving 0.
Trying allocation using normal policy.
Cling_to_allocated is set
Still need 64 total extents:
  1 (1 data/0 parity) parallel areas of 64 extents each
  0 mirror logs of 0 extents each
Considering allocation area 1 as /dev/sda6 start PE 2048 length 683 
leaving 0.
Segmentation fault


If you need more info pls let me know.  Backuping up a giant LV, removing
it, creating a larger LV, and restoring is what LVM normally helps me avoid.


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

Bug#762029: sleepd: major memory leak?!

[Cyril Brulebois]

green  (2014-09-17):
> Package: sleepd
> Version: 2.07+b1
> Severity: normal
> 
> My system is swapping, and the culprit appears to be sleepd.
> 
> In top, sleepd is listed with:
> VIRT: 12.655g
> RES: 2.132g
> SHR: 1272
> %MEM: 56.0
> 
> Thank you for maintaining sleepd.

FWIW:
| Maintainer for sleepd is Debian QA Group 
| […]
| This package has been orphaned. This means that it does not have a real
| maintainer at the moment. Please consider adopting this package if you
| are interested in it. Please see bug number #756545 for more
| information.

You may want to be the next maintainer, or at least patch submitter. :)

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#752463: diff of the NMU

[Aurelien Jarno]

Hi,

I have just done a non-maintainer upload to fix this issue, please find
the diff of the NMU attached.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -u ode-0.11.1/debian/control ode-0.11.1/debian/control
--- ode-0.11.1/debian/control
+++ ode-0.11.1/debian/control
@@ -4,7 +4,8 @@
 Maintainer: Debian Games Team 
 Uploaders: Barry deFreese 
 Build-Depends: debhelper (>> 5.0.0), docbook-to-man,
- libglu1-mesa-dev | libglu-dev, libgl1-mesa-dev | libgl-dev
+ libglu1-mesa-dev | libglu-dev, libgl1-mesa-dev | libgl-dev,
+ dh-autoreconf
 Standards-Version: 3.8.2
 Vcs-Svn: svn://svn.debian.org/svn/pkg-games/packages/trunk/ode/
 Vcs-Browser: http://svn.debian.org/wsvn/pkg-games/packages/trunk/ode/?op=log
diff -u ode-0.11.1/debian/changelog ode-0.11.1/debian/changelog
--- ode-0.11.1/debian/changelog
+++ ode-0.11.1/debian/changelog
@@ -1,3 +1,14 @@
+ode (2:0.11.1-4.1) unstable; urgency=medium
+
+  [ Aurelien Jarno ]
+  * Non-maintainer upload.
+  * Build-depends on dh-autoreconf.
+
+  [ Breno Leitao ]
+  * Run dh_autoreconf to update autoconf/libtool files (Closes: #752463).
+
+ -- Aurelien Jarno   Wed, 17 Sep 2014 22:37:14 +0200
+
 ode (2:0.11.1-4) unstable; urgency=low
 
   * Team upload.
diff -u ode-0.11.1/debian/rules ode-0.11.1/debian/rules
--- ode-0.11.1/debian/rules
+++ ode-0.11.1/debian/rules
@@ -9,6 +9,7 @@
 configure: configure-stamp
 configure-stamp:
 	dh_testdir
+	dh_autoreconf
 	mkdir -p debian/build/dp debian/build/sp
 	# SP: single precision build
 	cd debian/build/sp && ../../../configure --enable-shared --prefix=/usr LIBS="-lX11"
@@ -40,6 +41,7 @@
 	
 	# Add here commands to clean up after the build process.
 	[ ! -f Makefile ] || $(MAKE) distclean
+	dh_autoreconf_clean
 	dh_clean configure-stamp build-stamp debian/ode-config.1
 
 install: build

Bug#761286: blueman: set caja as a possible file browser

[Alessandro Barbieri]

Il 17/09/2014 16:03, Christopher Schramm ha scritto:

Hi Alessandro, I've created an upstream item for this:
https://github.com/blueman-project/blueman/issues/94

I think it should be possible to set an arbitrary browser command, but I
need to check that. Anyway, built-in caja support would definitely be good.

Thanks Cristopher,

I can't set it from the applet, see bug #761284 and i can't find 
configuration files.


--
sip:alebar...@ekiga.net


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

Bug#754586: [jitsi-dev] debcheckout jitsi

[Damian Minkov]

Hi,



On Wed, Sep 17, 2014 at 11:40 PM, Kurt Roeckx  wrote:
> On Wed, Sep 17, 2014 at 11:21:06PM +0300, Damian Minkov wrote:
>> Hi,
>>
>> it is the upstream which contains the debian packaging. We commit
>> everything in resources/install/debian.
>> What's the point of this field if its not the upstream? What should we
>> put there?
>> I saw there is a bug report about missing vcs fields and I've added
>> them with values pointing to the repository containing the sources we
>> are currently packaging.
>
> It seems to contain instruction on how to generate the source
> package from that repository, including having to do a few git
> clone / svn checkouts.  The Vcs-* fields should point to the
> sources like it's in Debian so that people working on
> Debian can make changes to it.  This means among other things
> that there is a "debian" directory, instead of a
> resources/install/debian.  The full sources shouldn't even be
> there, it could be that the upstream sources are gotten from
> the .orig.tar.gz file.  Or it might have the upstream sources
> too, but most likely not contain the full upstream history, just
> those things that are uploaded to Debian.
>
> Typically the "debian" dir is not maintained upstream, but in it's
> own repository like the one in collab-maint.  You seem to have a
> different workflow.  And the Vcs-* fields you added will not result
> in people getting what they expect to find.
>
> (I don't know if I explained myself good, but I hope you
> understand what I mean.)

Thanks for clearing it. Are these values correct:

+Vcs-Git: git://anonscm.debian.org/collab-maint/jitsi.git
+Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/jitsi.git

Should we commit there or it is automatically imported? Do we have
access there? How can we update with current version or it is updated
after the package is accepted into Debian repo?

Thanks
damencho

>
>
> Kurt
>


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

Bug#712787: ITP for Distkeys

[Eriberto]

Hi Martin,

About your package, please:

1. Use DH 9 instead DH 8.

2. d/control:
- Change Priority from 'extra' to 'optional'.
- The Homepage field and VCS point to a site that says 'The
project you're trying to access has been archived'.

3. d/copyright:
- In header, the field 'Source' is wrong.
- The 'AUTHORS' file says: 'Licensed unter GPL-2. See COPYING.'.
So, the upstream code is GPL-2, not 2+. Note the word 'unter'. :-)
- Your year as packager should be 2013.

4. d/rules: please, remove all comments (from '# -*- makefile' up to
'verbose mode').

5. You will need update the Homepage address. Can your current
homepage allow scans from d/watch file?

Thanks for your work.

Cheers,

Eriberto


2014-09-17 6:34 GMT-03:00 Martin Steigerwald :
> tags 712787 -moreinfo
> thanks
>
> Am Mittwoch, 10. September 2014, 09:07:04 schrieb Eriberto Mota:
>> tags 712787 moreinfo
>> thanks
>>
>>
>> Hi Martin,
>
> HI Eriberto,
>
>>
>> You didn't put the ITP number in d/changelog.
>
> Did so now.
>
>> To make easier the review, please, upload your package to
>> mentors.debian.net.
>
> Uploaded to
>
> http://mentors.debian.net/package/distkeys
>
> and hanged status to needs a sponsor.
>
> Thanks,
> Martin
>
>> Thanks,
>>
>> Eriberto
>>
>> 2014-04-22 5:28 GMT-03:00 Martin Steigerwald :
>> > ITP finally went through after Don added some additional stripping to the
>> > mail parsing.
>> >
>> > ITP: distkeys -- Distkeys - upload SSH keys to servers and more
>> > http://bugs.debian.org/745478
>> >
>> > Thanks,
> ]…}
>
>
>
> --
> Martin Steigerwald  | Consultant / Trainer
>
> teamix GmbH
> Südwestpark 43
> 90449 Nürnberg
>
> Tel.:  +49 911 30999 55 | Fax: +49 911 30999 99
> mail: martin.steigerw...@teamix.de | web:  http://www.teamix.de | blog: 
> http://blog.teamix.de
>
> Amtsgericht Nürnberg, HRB 18320 | Geschäftsführer: Oliver Kügow, Richard 
> Müller
>
>
>


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

Bug#614874: Pending fixes for bugs in the libxml-autowriter-perl package

[pkg-perl-maintainers]

tag 614874 + pending
thanks

Some bugs in the libxml-autowriter-perl package are closed in
revision 59f223e1d6352fc5f18fe43a23daa353a8d6bd2e in branch 'master'
by Niko Tyni

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libxml-autowriter-perl.git/commit/?id=59f223e

Commit message:

Fix deprecation warnings about UNIVERSAL::import. Patch by brian m. 
carlson. (Closes: #614874)


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

Bug#761241: nvidia proprietary driver

[Alessandro Barbieri]

On Sun, 14 Sep 2014 09:57:33 +0200 Andreas Henriksson  
wrote:

> Control: reassign -1 libclutter-gtk-1.0-0
> Control: forcemerge 761009 -1
>
> Hello!
>
> Thanks for the confirmation abouth the proprietary nvidia driver is
> in use.
>
> Unfortunately it is not that easy to just blacklist the nvidia driver.
> The "driver" also replaces your entire graphics stack once it's 
installed.

> You'll basically need to reinstall your system to get rid of it.
>
> Anyway, the problem should be worked around in clutter-gtk. Thus 
reassigning

> and merging your bug report.
> Try upgrading to a newer version of clutter-gtk.
>
> Regards,
> Andreas Henriksson
>
> PS. My ISP where having problems which should now be resolved.
>
>

Today i upgraded and now works, thank for the support.

PS

this message didn't reached me, i had to reply from the site and icedove 
still refuse to send mail to you Andreas :(


--
sip:alebar...@ekiga.net


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