Bug#808315: marked as done (Parse error: 'TK_IPADDR6' expected, but got 'ipv6' (TK 315))
Your message dated Tue, 29 Dec 2015 11:19:00 + with message-id and subject line Bug#808315: fixed in drbd-utils 8.9.5-1 has caused the Debian Bug report #808315, regarding Parse error: 'TK_IPADDR6' expected, but got 'ipv6' (TK 315) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 808315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: drbd-utils Version: 8.9.2~rc1-2 "drbdadm adjust" cannot be used on Debian 8.2 when replication is configured over IPv6: # drbdadm adjust r0 drbdsetup show r0:13: Parse error: 'TK_IPADDR6' expected, but got 'ipv6' (TK 315) # drbdadm --dry-run adjust r0 drbdsetup show r0:13: Parse error: 'TK_IPADDR6' expected, but got 'ipv6' (TK 315) There is already a patch available on the upstream release: http://git.linbit.com/drbd-utils.git/commitdiff/e758c28a http://lists.linbit.com/pipermail/drbd-user/2015-December/022590.html It is not possible to adjust a resource - to apply changes made on /etc/drbd.d/*.res, one has to invoke drbdadm down/up, resulting in service interruption. I'll skip attaching further details about my configuration, as the problem is already diagnosed and fixed upstream. --- End Message --- --- Begin Message --- Source: drbd-utils Source-Version: 8.9.5-1 We believe that the bug you reported is fixed in the latest version of drbd-utils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 808...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Apollon Oikonomopoulos (supplier of updated drbd-utils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 12:26:49 +0200 Source: drbd-utils Binary: drbd-utils drbd-utils-dbg drbd8-utils Architecture: source amd64 Version: 8.9.5-1 Distribution: unstable Urgency: medium Maintainer: Debian DRBD Maintainers Changed-By: Apollon Oikonomopoulos Description: drbd-utils - RAID 1 over TCP/IP for Linux (user utilities) drbd-utils-dbg - RAID 1 over TCP/IP for Linux (user utilities' debug symbols) drbd8-utils - transitional dummy package Closes: 633547 787394 808315 Changes: drbd-utils (8.9.5-1) unstable; urgency=medium . * New upstream release (closes: #808315) + Drop d/patches/fix-8.4-manpages, it has been merged upstream. + Refresh patches * Ensure reproducible build. * Remove DRBD service file and use initscript (closes: #787394, #633547). Upstream is doing the same and the start logic is complicated enough to be a bad fit for a systemd unit. Checksums-Sha1: 185b91d0dd2680441c5d1dc05d0431375dda95d6 2229 drbd-utils_8.9.5-1.dsc 7cb29d43deef58ebfc07092d692640bd5cb2678d 772894 drbd-utils_8.9.5.orig.tar.gz c3172ba55b34f0acba33d85ba46096290dbebd10 17032 drbd-utils_8.9.5-1.debian.tar.xz 97014b5c961100e900a9dcb2d07ff16f5922c241 932992 drbd-utils-dbg_8.9.5-1_amd64.deb 7a06e68c1863f5959aeaf04f04a8fafe19315091 463196 drbd-utils_8.9.5-1_amd64.deb f2c2ca6ef2d5779b5497f40e819f505c93777c39 17640 drbd8-utils_8.9.5-1_amd64.deb Checksums-Sha256: d50d035126655e4632e1488c021ff052b4549b337e2c8ec2e20b34fcb5602955 2229 drbd-utils_8.9.5-1.dsc 659ea09c51776e7d5a791f23b44858601a53676fa6d824b87ef1b5411c4093b3 772894 drbd-utils_8.9.5.orig.tar.gz 64775eacb0eed262660188cf0e7f53e3a44be75d7ee640a12b47ac4035014264 17032 drbd-utils_8.9.5-1.debian.tar.xz f99b6285604505e4ecc181dc7de54d1b48cebdc9e667f0d0b10b9a1a4a03137b 932992 drbd-utils-dbg_8.9.5-1_amd64.deb 51cbc5b44240d965a6fc62f6f89970b1fb0b368589371506dfc8982d5312f5e4 463196 drbd-utils_8.9.5-1_amd64.deb b38d3ffbd512c6b3262141f8e9865526acc69687a5ed200c25dbe789397c38ec 17640 drbd8-utils_8.9.5-1_amd64.deb Files: 2e096404151324a3fc47efdac70fbc28 2229 admin extra drbd-utils_8.9.5-1.dsc 1873b9089db4d2051c78cab4f926114a 772894 admin extra drbd-utils_8.9.5.orig.tar.gz 550dfb1a84bf67f792f0ddeca89a9e76 17032 admin extra drbd-utils_8.9.5-1.debian.tar.xz 0f3d3ccf9d3d0d56d3ec31e69fdfd7fc 932992 debug extra drbd-utils-dbg_8.9.5-1_amd64.deb 0b2cee9dc3601bc4d47c83521a4c0856 46
Bug#633547: marked as done (drbd8-utils: Drbd init script did not start stacked resources.)
Your message dated Tue, 29 Dec 2015 11:19:00 +
with message-id
and subject line Bug#633547: fixed in drbd-utils 8.9.5-1
has caused the Debian Bug report #633547,
regarding drbd8-utils: Drbd init script did not start stacked resources.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
633547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: drbd8-utils
Version: 2:8.3.7-2.1
Severity: important
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages drbd8-utils depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib
drbd8-utils recommends no packages.
Versions of packages drbd8-utils suggests:
ii heartbeat 1:3.0.3-2 Subsystem for High-Availability Li
-- Configuration Files:
/etc/drbd.d/global_common.conf changed:
global {
usage-count no;
# minor-count dialog-refresh disable-ip-verification
}
common {
protocol C;
handlers {
pri-on-incon-degr "/usr/lib/drbd/notify-pri-on-incon-degr.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ; reboot
-f";
pri-lost-after-sb "/usr/lib/drbd/notify-pri-lost-after-sb.sh;
/usr/lib/drbd/notify-emergency-reboot.sh; echo b > /proc/sysrq-trigger ; reboot
-f";
local-io-error "/usr/lib/drbd/notify-io-error.sh;
/usr/lib/drbd/notify-emergency-shutdown.sh; echo o > /proc/sysrq-trigger ; halt
-f";
# fence-peer "/usr/lib/drbd/crm-fence-peer.sh";
# split-brain "/usr/lib/drbd/notify-split-brain.sh root";
# out-of-sync "/usr/lib/drbd/notify-out-of-sync.sh root";
# before-resync-target
"/usr/lib/drbd/snapshot-resync-target-lvm.sh -p 15 -- -c 16k";
# after-resync-target
/usr/lib/drbd/unsnapshot-resync-target-lvm.sh;
}
startup {
# wfc-timeout degr-wfc-timeout outdated-wfc-timeout
wait-after-sb;
wfc-timeout 30;
degr-wfc-timeout 30;
outdated-wfc-timeout 30;
#wait-after-sb 30;
}
disk {
# on-io-error fencing use-bmbv no-disk-barrier no-disk-flushes
# no-disk-drain no-md-flushes max-bio-bvecs
}
net {
# snd‐buf-size rcvbuf-size timeout connect-int ping-int
ping-timeout max-buffers
# max-epoch-size ko-count allow-two-primaries cram-hmac-alg
shared-secret
# after-sb-0pri after-sb-1pri after-sb-2pri data-integrity-alg
no-tcp-cork
}
syncer {
# rate after al-extents use-rle cpu-mask verify-alg csums-alg
}
}
/etc/init.d/drbd changed:
DEFAULTFILE="/etc/default/drbd"
DRBDADM="/sbin/drbdadm"
DRBDSETUP="/sbin/drbdsetup"
PROC_DRBD="/proc/drbd"
MODPROBE="/sbin/modprobe"
RMMOD="/sbin/rmmod"
UDEV_TIMEOUT=10
ADD_MOD_PARAM=""
if [ -f $DEFAULTFILE ]; then
. $DEFAULTFILE
fi
test -f $DRBDADM || exit 5
log_daemon_msg() { echo -n "${1:-}: ${2:-}"; }
log_end_msg() { echo "."; }
if [ -f /lib/lsb/init-functions ]; then
. /lib/lsb/init-functions
fi
function assure_module_is_loaded
{
[ -e "$PROC_DRBD" ] && return
$MODPROBE -s drbd `$DRBDADM sh-mod-parms` $ADD_MOD_PARAM || {
echo "Can not load the drbd module."$'\n'; exit 20
}
# tell klogd to reload module symbol information ...
[ -e /var/run/klogd.pid ] && [ -x /sbin/klogd ] && /sbin/klogd -i
}
function adjust_with_progress
{
IFS_O=$IFS
NEWLINE='
'
IFS=$NEWLINE
local res
COMMANDS=`$DRBDADM -d -n res adjust all` || exit 20
echo -n "[ "
for CMD in $COMMANDS; do
case "$CMD" in
res=*) eval "$CMD";;
*\ disk\ *) echo -n "d($res) " ;;
*\ syncer\ *) echo -n "s($res) " ;;
*\ net\ *) echo -n "n($res)
Bug#807688: marked as done (RM: mono [powerpc] -- ANAIS; Architecture no longer well-maintained, FTBFS)
Your message dated Tue, 29 Dec 2015 11:56:24 + with message-id and subject line Bug#807688: Removed package(s) from unstable has caused the Debian Bug report #807688, regarding RM: mono [powerpc] -- ANAIS; Architecture no longer well-maintained, FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 807688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ftp.debian.org Severity: normal Sadly I was unable to resolve outstanding issues with PowerPC 32-bit big-endian on Mono. It's time to get rid of this arch from this package. PPC64el has some proper support, including upstream CI. --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libmono-2.0-1 | 3.2.8+dfsg-10 | powerpc libmono-2.0-dev | 3.2.8+dfsg-10 | powerpc libmono-profiler | 3.2.8+dfsg-10 | powerpc libmonoboehm-2.0-1 | 3.2.8+dfsg-10 | powerpc libmonoboehm-2.0-1-dbg | 3.2.8+dfsg-10 | powerpc libmonoboehm-2.0-dev | 3.2.8+dfsg-10 | powerpc libmonosgen-2.0-1 | 3.2.8+dfsg-10 | powerpc libmonosgen-2.0-1-dbg | 3.2.8+dfsg-10 | powerpc libmonosgen-2.0-dev | 3.2.8+dfsg-10 | powerpc mono-complete | 3.2.8+dfsg-10 | powerpc mono-jay | 3.2.8+dfsg-10 | powerpc mono-runtime | 3.2.8+dfsg-10 | powerpc mono-runtime-boehm | 3.2.8+dfsg-10 | powerpc mono-runtime-common | 3.2.8+dfsg-10 | powerpc mono-runtime-dbg | 3.2.8+dfsg-10 | powerpc mono-runtime-sgen | 3.2.8+dfsg-10 | powerpc mono-utils | 3.2.8+dfsg-10 | powerpc --- Reason --- ANAIS; Architecture no longer well-maintained, FTBFS -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 807...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/807688 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Chris Lamb (the ftpmaster behind the curtain)--- End Message ---
Bug#752961: marked as done (vor: FTBFS - missing -lm)
Your message dated Tue, 29 Dec 2015 11:58:49 + with message-id and subject line Bug#809267: Removed package(s) from unstable has caused the Debian Bug report #752961, regarding vor: FTBFS - missing -lm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 752961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vor Version: 0.5.5-2 Severity: serious Usertags: goto-cc During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder and pbuilder) the build failed with the following error. [...] gcc font.o args.o dust.o file.o mt.o rocks.o score.o sprite.o sound.o autopilot.o main.o -L/usr/lib/x86_64-linux-gnu -lSDL -lSDL_image -lSDL_mixer -o vor ld.bfd.orig: main.o: undefined reference to symbol 'cos@@GLIBC_2.2.5' //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status Makefile:114: recipe for target 'vor' failed make[1]: *** [vor] Error 1 The full build log is attached; please do let me know if the problem is unreproducible. The problem here appears to be a missing "-lm" in the compiler/linker command line. Best, Michael vor-build-log.txt.gz Description: application/gunzip pgpd3hjHg9g4A.pgp Description: PGP signature --- End Message --- --- Begin Message --- Version: 0.5.5-2+rm Dear submitter, as the package vor has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/809267 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Chris Lamb (the ftpmaster behind the curtain)--- End Message ---
Bug#807541: marked as done (RM: haskell-certificate -- ROM; superceded by x509)
Your message dated Tue, 29 Dec 2015 12:02:43 + with message-id and subject line Bug#807541: Removed package(s) from unstable has caused the Debian Bug report #807541, regarding RM: haskell-certificate -- ROM; superceded by x509 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 807541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, this package is superceded by haskell-x509, please remove. Thanks, Joachim -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlZpOxgACgkQ9ijrk0dDIGxstwCeNDsGKHU/JCk9gkbQUzQNRz5V zykAoJZEW6gR9hekzbCT/KoRv4V9YIC4 =Iynl -END PGP SIGNATURE- --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: haskell-certificate |1.3.9-4 | source libghc-certificate-dev |1.3.9-4 | mips64el libghc-certificate-dev | 1.3.9-4+b2 | arm64, armhf, hurd-i386, kfreebsd-amd64, kfreebsd-i386, mips, ppc64el, s390x libghc-certificate-dev | 1.3.9-4+b3 | powerpc libghc-certificate-dev | 1.3.9-4+b4 | amd64, mipsel libghc-certificate-dev | 1.3.9-4+b5 | i386 libghc-certificate-doc |1.3.9-4 | all libghc-certificate-prof |1.3.9-4 | mips64el libghc-certificate-prof | 1.3.9-4+b2 | arm64, armhf, hurd-i386, kfreebsd-amd64, kfreebsd-i386, mips, ppc64el, s390x libghc-certificate-prof | 1.3.9-4+b3 | powerpc libghc-certificate-prof | 1.3.9-4+b4 | amd64, mipsel libghc-certificate-prof | 1.3.9-4+b5 | i386 --- Reason --- ROM; superceded by x509 -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 807...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/807541 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Chris Lamb (the ftpmaster behind the curtain)--- End Message ---
Bug#809267: marked as done (RM: vor -- RoQA; FTBFS, buggy, not maintained)
Your message dated Tue, 29 Dec 2015 11:58:44 + with message-id and subject line Bug#809267: Removed package(s) from unstable has caused the Debian Bug report #809267, regarding RM: vor -- RoQA; FTBFS, buggy, not maintained to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809267 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ftp.debian.org Severity: normal vor only seen two uploads in the archive, and hasn't been uploaded for more than 5 years. In addition it is not buildable anymore for 1.5 years (RC bug#752961). As a consequence it is not available in jessie nor in stretch. I therefore recommend to remove this package from the archive. --- End Message --- --- Begin Message --- We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: vor |0.5.5-2 | source, amd64, armel, armhf, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390x vor | 0.5.5-2+b1 | hurd-i386 --- Reason --- RoQA; FTBFS, buggy, not maintained -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/809267 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Chris Lamb (the ftpmaster behind the curtain)--- End Message ---
Bug#745268: marked as done (vor: Please move from contrib to main (povray is now agpl))
Your message dated Tue, 29 Dec 2015 11:58:49 + with message-id and subject line Bug#809267: Removed package(s) from unstable has caused the Debian Bug report #745268, regarding vor: Please move from contrib to main (povray is now agpl) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 745268: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: vor Version: 0.5.5-2 Severity: normal Dear Maintainers, Povray finally has a DFSG-compliant license! I'm so excited. This means that vor can now be included in main right?! I'm pretty sure the old povray license was the only thing relegating vor to contrib. Please move vor to main :) Note: It looks like the debian package for this new (AGPL-licensed) version of povray is still a work in progress, in that it only successfully builds on one architecture. Do you need to wait for it to build on more architectures before moving vor to main? I'm pretty sure povray is _not_ used in building the debian package for vor (because the upstream tarball releases of vor come with the graphics already rendered.) I think it is sufficient (for vor to be allowed into main) that povray is available from povray.org under a DFSG-compliant license, but this paragraph is here in case I'm wrong about that. Thank you thank you! -- Jason -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.13-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Version: 0.5.5-2+rm Dear submitter, as the package vor has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/809267 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Chris Lamb (the ftpmaster behind the curtain)--- End Message ---
Bug#808490: marked as done (haskell-certificate: FTBFS with ghc 7.10(?): Non type-variable argument in the constraint: MonadError [Char] m)
Your message dated Tue, 29 Dec 2015 12:02:49 +
with message-id
and subject line Bug#807541: Removed package(s) from unstable
has caused the Debian Bug report #808490,
regarding haskell-certificate: FTBFS with ghc 7.10(?): Non type-variable
argument in the constraint: MonadError [Char] m
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
808490: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-certificate
Version: 1.3.9-4
Severity: serious
Justification: fails to build from source
Tags: sid
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
The package fails to build:
[ 4 of 10] Compiling Data.Certificate.X509.Ext ( Data/Certificate/X509/Ext.hs,
dist-ghc/build/Data/Certificate/X509/Ext.o )
Data/Certificate/X509/Ext.hs:116:17:
Non type-variable argument in the constraint: MonadError [Char] m
(Use FlexibleContexts to permit this)
When checking that ‘toStringy’ has the inferred type
toStringy :: forall (m :: * -> *).
MonadError [Char] m =>
ASN1 -> m [Char]
In an equation for ‘extDecode’:
extDecode l
= runParseASN1 parse l
where
parse
= do { c <- getNextContainer Sequence;
}
toStringy (Other Context 2 b) = return $ BC.unpack b
toStringy b
= throwError
("ExtSubjectAltName: not coping with anything else " ++
show b)
In the instance declaration for ‘Extension ExtSubjectAltName’
/usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp'
failed
make: *** [build-ghc-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/haskell-certificate.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Version: 1.3.9-4+rm
Dear submitter,
as the package haskell-certificate has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/807541
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---
Bug#796932: marked as done (hhvm: FTBFS on buildds (unsatisfiable libjpeg62-dev build-dep))
Your message dated Tue, 29 Dec 2015 12:34:58 + with message-id and subject line Bug#796932: fixed in hhvm 3.11.0+dfsg-1 has caused the Debian Bug report #796932, regarding hhvm: FTBFS on buildds (unsatisfiable libjpeg62-dev build-dep) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 796932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hhvm Version: 3.2.0+dfsg1-2 Severity: serious Please build-depend on libjpeg-dev instead. See https://buildd.debian.org/status/fetch.php?pkg=hhvm&arch=amd64&ver=3.2.0%2Bdfsg1-2%2Bb1&stamp=1440537145 Cheers, Julien signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: hhvm Source-Version: 3.11.0+dfsg-1 We believe that the bug you reported is fixed in the latest version of hhvm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 796...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Faidon Liambotis (supplier of updated hhvm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 02:57:38 +0200 Source: hhvm Binary: hhvm hhvm-dbg hhvm-dev Architecture: source amd64 Version: 3.11.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian HHVM packaging team Changed-By: Faidon Liambotis Description: hhvm - HipHop Virtual Machine, a JIT replacement for PHP - main runtime hhvm-dbg - HipHop Virtual Machine, a JIT replacement for PHP - debugging sym hhvm-dev - HipHop Virtual Machine, a JIT replacement for PHP - development f Closes: 796932 Changes: hhvm (3.11.0+dfsg-1) unstable; urgency=medium . [ Faidon Liambotis ] * New upstream release. * Build with stock gcc again; folly's gcc 5.0 issues have been fixed. * Refresh all debian/patches; drop: - support-more-sql-stats: merged upstream - ezc-fix-z-type-in-zend_parse_parameters: was a backport - use_system_TZinfo: merged upstream - fix_freetype_include: unused/unneeded - hack_license.patch: obsolete - license_folly.patch: superfluous * Drop our own debian/-shipped manpages, as these have been merged into the upstream tree instead and enhanced since. * Add Build-depends on gawk, gperf, libboost-context-dev, libre2-dev, libgmp-dev. * Build-depend on libjpeg-dev instead of libjpeg62-dev. (Closes: #796932) * Build-depend on libvpx-dev to enable WebP support for gd. * Drop libiconv-hook-dev dependency and associated patch, libc6's iconv.h should be enough for HHVM and it doesn't appear like upstream's intention was ever to link against libiconv-hook. * Disable asynchronous MySQL support; it depends on the webscalesql fork of libmysqlclient-dev which is not packaged separately in Debian. Upstream bundles it under their third-party repository but it has been stripped from this packaging as the full forked MySQL 5.6 source is too big to be embedded into this package. * Drop patch enable_relro_hack, that enabled hardening (relro) for hh_client/hh_server. Current recommendation by the OCaml team is to not attempt to do any hardening until the OCaml runtime itself gets fixed first (#702349). * Add patch fix_stats_error to fix a MySQL statistics collection error. * Add patch fix-makeparser-bison3 to fix a make-parser.sh incompatibility when ran with Bison3. * Set HOME to debian/build when running the tests so that HHVM can write the HHBC even when $HOME does not exist, or to not leave garbage behind when it exists. * Switch our Provides: hhvm-api-$version to the major/minor HHVM released, based on upstream's recommendation of using HHVM_VERSION_BRANCH. * Remove sources of build variance to hopefully make the build reproducible: - Pass $COMPILER_ID to the compilation process, based on the package's version from debian/changelog. - Add patch reproducible-sort to pass LC_ALL=C to sort. - Add patch reproducible-hack-builddate to remove __DATE__/__TIME__. embedding f
Bug#803020: marked as done (switchconf uses deprecated find -perm +xxx syntax, please switch to find -perm /+++)
Your message dated Tue, 29 Dec 2015 12:49:00 +
with message-id
and subject line Bug#803020: fixed in switchconf 0.0.9-2.1
has caused the Debian Bug report #803020,
regarding switchconf uses deprecated find -perm +xxx syntax, please switch to
find -perm /+++
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
803020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: switchconf
Version: 0.0.9-2
User: ametz...@debian.org
Usertags: find-perm-plus
Hello,
the switchconf package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.
The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.
--
ametzler@argenau:/tmp/FINDPERM$ grep -r -- '-perm +' switchconf-0.0.9/
switchconf-0.0.9/switchconf:for r in `find ${scriptsdir} -type f -perm +1 |
sort`; do
--
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
--- Begin Message ---
Source: switchconf
Source-Version: 0.0.9-2.1
We believe that the bug you reported is fixed in the latest version of
switchconf, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 803...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Metzler (supplier of updated switchconf package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 20 Dec 2015 15:01:58 +0100
Source: switchconf
Binary: switchconf
Architecture: source all
Version: 0.0.9-2.1
Distribution: unstable
Urgency: medium
Maintainer: Jose Calhariz
Changed-By: Andreas Metzler
Description:
switchconf - switch between system configuration sets
Closes: 803020
Changes:
switchconf (0.0.9-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Use "find -perm /x" instead of "find -perm +x". Closes: #803020
Checksums-Sha1:
3f7c7bebfcb2b9e9401db49fe71359c22be56290 1659 switchconf_0.0.9-2.1.dsc
8b4e7f8454319686713448babaf180f9fb8790f6 6470 switchconf_0.0.9-2.1.diff.gz
1308d67118374df28e04b5ed13faa23fb871af39 10274 switchconf_0.0.9-2.1_all.deb
Checksums-Sha256:
43f976e429451097e37e06b7067556b3e347773fd1e29cb2497131faa898d2ad 1659
switchconf_0.0.9-2.1.dsc
4cd22b3a780393f27b1aaadc1a16899638eb3082435060c69bb695629fe41d90 6470
switchconf_0.0.9-2.1.diff.gz
adee5b9e88022904b44725f9d47d1713ca042e243ddda780a78e3d2133cd69c4 10274
switchconf_0.0.9-2.1_all.deb
Files:
f7b5de954951eb7a3cf80985a104f3bc 1659 admin optional switchconf_0.0.9-2.1.dsc
c089a5690955d173a74f1a4d0ca453d6 6470 admin optional
switchconf_0.0.9-2.1.diff.gz
2f01885700168a7790831f3f19c0d833 10274 admin optional
switchconf_0.0.9-2.1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCgAGBQJWdrU9AAoJEKVPAYVDghSE2t0P/R9Rsjf/F/hfQGwFwgDiunWs
DeAMMYOAlUvaGVxmGDTy/RrcFGIjZhRxhIHF4FoF/VJGcSKYI/4otelvHbq/3LOS
5n9TA5G0qOw2et12g7YtB4SJfYJ48opTvMWglHUROeBvN9nK/EpygfDIXvX4Y9Ez
QONOBnkF+tobr7pn00R8FLPzg5AMwKreCLCIx7EICmOLY3MwacL3vBu3/zcrox05
vwmzp5IPBq/jRRKehEd9AQMrsOO1sJEWDrJXSgifh5ybGXMkx+P6URuWKMYxR/61
xvCMp8Hx3/srJJRMkmKEBATVssaErh1Y8Wy1JSAy/CLYQ1pRvkFH6moHXUX8bMd0
x9ixqx0O87+7s/ogsv0riLBviqgZlAzJp5V2iHcb3a9rLKtKeRPRNFY+eizPwMR6
eM54UxAj+KJOblGS6cqOqTNq324yFECc7lJW3k0WPbOUMWBOqO/LoUrX4PtlbzQl
G49eh3/lSZhaNN1wc6tafQVUtsyDosAfAR+o3m/RrzGH+if0qK5tg6RsQwXxxs6L
XUaYvRbk0QFDhbTANUjqhd/YmksL/3e59hIRXOeYmT/b8EQirqgVnjayn1c7eBTd
mrqeb4yhdlxNMrlkiCoyMedCUDy7v95ZqvnE7EzaXLkyQuLAQ9bZZ221rsoWsRm9
PNESsxv2wXWiLec7velj
=rZja
-END PGP SIGNATURE End Message ---
Bug#808893: marked as done (catdoc: failed to parse regular doc files)
Your message dated Tue, 29 Dec 2015 12:48:55 + with message-id and subject line Bug#808893: fixed in catdoc 1:0.94.3~git20151007.fd634c2+dfsg-3 has caused the Debian Bug report #808893, regarding catdoc: failed to parse regular doc files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 808893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: catdoc Version: 1:0.94.3~git20151007.fd634c2+dfsg-2 Severity: important Hello, I tried this version of catdoc with most of doc files on my workstation, none works. Some example output: 1-- [This was fast-saved 5 times. Some information is lost] File ended before textstart. Probably it is broken. Try -b switch 2-- [This was fast-saved 1 times. Some information is lost] [File is encrypted. Encryption key = ] I create a doc file with only 4 chinese chars "测试文档", and it fails alse. See attachment for the test file. Thanks -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'work'), (500, 'testing-updates'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages catdoc depends on: ii libc6 2.21-5 catdoc recommends no packages. Versions of packages catdoc suggests: pn tk | wish -- no debconf information test.doc Description: MS-Word document --- End Message --- --- Begin Message --- Source: catdoc Source-Version: 1:0.94.3~git20151007.fd634c2+dfsg-3 We believe that the bug you reported is fixed in the latest version of catdoc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 808...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martín Ferrari (supplier of updated catdoc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 12:38:12 + Source: catdoc Binary: catdoc Architecture: source amd64 Version: 1:0.94.3~git20151007.fd634c2+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Martín Ferrari Changed-By: Martín Ferrari Description: catdoc - Convert Word, Excel, and PowerPoint files to plain text Closes: 808893 Changes: catdoc (1:0.94.3~git20151007.fd634c2+dfsg-3) unstable; urgency=medium . * Fix bug introduced when fixing #679877 that rendered catdoc mostly useless. Closes: #808893. Checksums-Sha1: 537cb16a9205c7dca936395cdd6be89527af6236 1951 catdoc_0.94.3~git20151007.fd634c2+dfsg-3.dsc f578fff81a688a6bc14d412edce3ed1293fab575 51856 catdoc_0.94.3~git20151007.fd634c2+dfsg-3.debian.tar.xz 0126092b9581a1521f46adf7aad870924f7b97ae 109090 catdoc-dbgsym_0.94.3~git20151007.fd634c2+dfsg-3_amd64.deb 2063f3202bf695361f25e9f75fdabc1e92e3197b 86944 catdoc_0.94.3~git20151007.fd634c2+dfsg-3_amd64.deb Checksums-Sha256: fe176ee0ad8b5e922b3376c1d733744e369faa13fa8e3c071633b80b59bd76c0 1951 catdoc_0.94.3~git20151007.fd634c2+dfsg-3.dsc 07a56f2964de0836c477c83e36d3f5e1c080a4c50eac374cad7e49a09985cfc1 51856 catdoc_0.94.3~git20151007.fd634c2+dfsg-3.debian.tar.xz 3637aaa408488fd009cbb519cfcd16c27d8ddf9e08516a120a8d85ec101d459b 109090 catdoc-dbgsym_0.94.3~git20151007.fd634c2+dfsg-3_amd64.deb 2b3fb6d2f59f62e7c72e277ba706dfc94758af6cffbd2d8196385c6c376e3143 86944 catdoc_0.94.3~git20151007.fd634c2+dfsg-3_amd64.deb Files: f10384dafa4f355bdf0facdc763b0d9c 1951 text optional catdoc_0.94.3~git20151007.fd634c2+dfsg-3.dsc 7f421aca17ba6b374bde89b50d417ae2 51856 text optional catdoc_0.94.3~git20151007.fd634c2+dfsg-3.debian.tar.xz cf3b6dc07e822e78a35fbbbe6bd74953 109090 debug extra catdoc-dbgsym_0.94.3~git20151007.fd634c2+dfsg-3_amd64.deb b759d7f5051792da2ca63305075703ea 86944 text optional catdoc_0.94.3~git20151007.fd634c2+dfsg-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWgn8RAAoJEF3Y4L+Ro9Pa8qAP/3vzp4Cm1Jl17q/THn8J7JQx 07BJacNm/pJ+t/F3vJPlmQ3
Processed: Re: [aptitude] warn when changes affect large subtrees
Processing control commands: > retitle -1 aptitude: warn when changes affect large subtrees Bug #563297 [aptitude] aptitude: warn when changes effect large subtrees Changed Bug title to 'aptitude: warn when changes affect large subtrees' from 'aptitude: warn when changes effect large subtrees' > tags -1 + wontfix Bug #563297 [aptitude] aptitude: warn when changes affect large subtrees Added tag(s) wontfix. > close -1 Bug #563297 [aptitude] aptitude: warn when changes affect large subtrees Marked Bug as done -- 563297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#793307: marked as done (aptitude: Add a confirmation for changing 'automatic' flag)
Your message dated Tue, 29 Dec 2015 13:43:15 + with message-id <20151229134311.ga30...@reva.itsari.org> and subject line Re: [Aptitude-devel] Bug#793307: Bug#793307: aptitude: Add a confirmation for changing 'automatic' flag has caused the Debian Bug report #793307, regarding aptitude: Add a confirmation for changing 'automatic' flag to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 793307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: aptitude Version: 0.6.11-1+b1 Severity: wishlist Dear Maintainer, I occasionally pressed 'm' button when 'All installed packages' item was choosen, so all my packages were marked as manually installed. 'm' is placed right under 'j' which is often used for navigation, so occasional presses on it is a real problem for me. Please, add some kind of confirmation for changing package 'automatic' flag with 'm' button. Also, I saw some bugs when aptitude forgets 'automatic' flag for some packages and I thought some of them may be inspited by occasional 'm' press. -- Package-specific info: Terminal: rxvt-unicode $DISPLAY is set. which aptitude: /usr/bin/aptitude aptitude version information: aptitude 0.6.11 compiled at Nov 8 2014 13:34:39 Compiler: g++ 4.9.1 Compiled against: apt version 4.12.0 NCurses version 5.9 libsigc++ version: 2.4.0 Gtk+ support disabled. Qt support disabled. Current library versions: NCurses version: ncurses 5.9.20150516 cwidget version: 0.5.17 Apt version: 4.12.0 aptitude linkage: linux-vdso.so.1 (0x7ffefdbc2000) libapt-pkg.so.4.12 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12 (0x7f8c8d223000) libncursesw.so.5 => /lib/x86_64-linux-gnu/libncursesw.so.5 (0x7f8c8cfed000) libtinfo.so.5 => /lib/x86_64-linux-gnu/libtinfo.so.5 (0x7f8c8cdc3000) libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x7f8c8cbbd000) libcwidget.so.3 => /usr/lib/x86_64-linux-gnu/libcwidget.so.3 (0x7f8c8c8a7000) libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x7f8c8c5d9000) libboost_iostreams.so.1.55.0 => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.55.0 (0x7f8c8c3c1000) libxapian.so.22 => /usr/lib/libxapian.so.22 (0x7f8c8bfaa000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f8c8bd8d000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f8c8ba81000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f8c8b78) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7f8c8b56a000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f8c8b1c1000) libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7f8c8afbe000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f8c8adba000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f8c8ab9f000) libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x7f8c8a98f000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f8c8a76c000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f8c8a564000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7f8c8a35f000) /lib64/ld-linux-x86-64.so.2 (0x7f8c8dbe5000) -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (99, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages aptitude depends on: ii aptitude-common 0.6.11-1 ii libapt-pkg4.121.0.9.10 ii libboost-iostreams1.55.0 1.55.0+dfsg-4 ii libc6 2.19-19 ii libcwidget3 0.5.17-2 ii libgcc1 1:5.1.1-14 ii libncursesw5 5.9+20150516-2 ii libsigc++-2.0-0c2a2.4.1-1 ii libsqlite3-0 3.8.10.2-1 ii libstdc++65.1.1-14 ii libtinfo5 5.9+20150516-2 ii libxapian22 1.2.21-1 Versions of packages aptitude recommends: ii aptitude-doc-en [aptitude-doc] 0.6.11-1 ii libparse-debianchangelog-perl 1.2.0-5 ii sens
Bug#807798: marked as done (ITP: ruby-rails-assets-jquery.nicescroll -- provide jquery.nicescroll via rails asset pipeline)
Your message dated Tue, 29 Dec 2015 13:53:00 + with message-id and subject line Bug#807798: fixed in ruby-rails-assets-jquery-nicescroll 3.6.6-1 has caused the Debian Bug report #807798, regarding ITP: ruby-rails-assets-jquery.nicescroll -- provide jquery.nicescroll via rails asset pipeline to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 807798: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 package: wnpp severity: wishlist owner: Pirate Praveen from rails-assets.org -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWbQSpAAoJEM4fnGdFEsIqu+kP/1hVbeX5m3fuin5+C/YI3yCj iCa5Qi6AZ8c/Z5tjLwmeWm++TqdQ6oCQGAjMcJHf12sdlw70+5tjpxMjHDUh/P7H XeGi+7t+msNy7uyfnuKKrdX+cbBda/x2rQN4gnQr6arG7zoo3SufkLIKGT2jLSxM pByqt2EC2CVTUTtAOztMUtLNT4gJW/Cm54/Lpg7QD1E+sJDTpBvtB069ZjmG0Q02 PvRbSDF3YyEjzhd9q3aRlM/7NZUYUknROYHlsJ36aW8spHylclUedfWiZ7CKcZv1 9C8vzBUL5mUq56pCXGG4eWaLEQ+2EiCByJUv9otmTRt9xSAYHHd8JUkI4nlW7SZD AxTkCbh1FtyDieHg3euaLOHYr8pK5JesIJdK1N9iqbf5Bvqt1hXZb7zPcdc1a6wh qHILqph0zq42bPW8W41jO1OXBwD0jQUYJy1IBzj5ZmQ5CHgXUuq4A2i8+WdY1zfO 6Nc6yrI1WY++UH/GVtb854EiO7wPQydCMTFKgCZs20hZC87SsIET+zlyiCVdsnYi Iqdb96UUmga6+3Wm4Xi+xFb0x47159dgb+49h9lMnxh7V6bY5DAK+/XdTtS+NCnD YJ9gsUCS8ICNl6tQIbDwe8q5+7KzKq4OKirm5ThNglUvILa+JeKR8FkKMg3+3pOA P2RxMIr6MxHkeJS+206m =ECHC -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: ruby-rails-assets-jquery-nicescroll Source-Version: 3.6.6-1 We believe that the bug you reported is fixed in the latest version of ruby-rails-assets-jquery-nicescroll, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 807...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated ruby-rails-assets-jquery-nicescroll package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 13 Dec 2015 15:48:37 +0530 Source: ruby-rails-assets-jquery-nicescroll Binary: ruby-rails-assets-jquery-nicescroll libjs-jquery-nicescroll Architecture: source all Version: 3.6.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Pirate Praveen Description: libjs-jquery-nicescroll - jquery plugin, for nice scrollbars ruby-rails-assets-jquery-nicescroll - provide jquery.nicescroll via rails asset pipeline Closes: 807798 Changes: ruby-rails-assets-jquery-nicescroll (3.6.6-1) unstable; urgency=medium . * Initial release (Closes: #807798) Checksums-Sha1: 2981a22c327b026acdc58817c1ac68649814e2ca 2419 ruby-rails-assets-jquery-nicescroll_3.6.6-1.dsc ab7bf5566b835c1221eb8a94ff7f216eacfe0b14 45138 ruby-rails-assets-jquery-nicescroll_3.6.6.orig.tar.gz 1b9605f69f92b9a9c6b65336ba20f41585336ba2 2608 ruby-rails-assets-jquery-nicescroll_3.6.6-1.debian.tar.xz 8ee8a7cc0ee16470d60e45a97d447aa17599fd64 37874 libjs-jquery-nicescroll_3.6.6-1_all.deb f5437dd98a382add35b975185931defcde6ee4bf 4218 ruby-rails-assets-jquery-nicescroll_3.6.6-1_all.deb Checksums-Sha256: 9cd02b95a68bd6d0158275cc4ce1a3cb76ac74b52e4a2ea9cf6bb2a40fa363fe 2419 ruby-rails-assets-jquery-nicescroll_3.6.6-1.dsc 8fced5d587bd3fab2c2cf44215f88b9930e7d95332cfc3bcf3e3e733b6e46dcf 45138 ruby-rails-assets-jquery-nicescroll_3.6.6.orig.tar.gz cd9f1bdefb0d1b700ea5781e5684e11fa737055abc21dcb7b9e2896a01deff27 2608 ruby-rails-assets-jquery-nicescroll_3.6.6-1.debian.tar.xz 2d2d3d74c53f44d620ec3fa06f2b8d881063d0240dd3563ec93d5c019299d4f1 37874 libjs-jquery-nicescroll_3.6.6-1_all.deb 21266fe2bbee1c158970459a275fa2a687b5b5b6ef6229fd5fe71228e0f9d4d2 4218 ruby-rails-assets-jquery-nicescroll_3.6.6-1_all.deb Files: 713bdc122f954b9ce2834f59c1927b90 2419 ruby optional ruby-rails-assets-jquery-nicescroll_3.6.6-1.dsc bd87fd06848d8aa4a5dde81836a0b5da 45138 ruby optional ruby-rails-assets-jquery-nicescroll_3.6.6.orig.tar.gz 8ac0e51f19da64e4621fd05ceb931a05 2608 ruby optional ruby-rails-assets-jquery-nicescroll_3.6.6-1.debian.tar.xz 4b45b8bef7fa92470540876f5e9cdef0 37874 web optional libjs-jquery-nicescroll_3.6.6-1_all.deb 21098d293a115d1db07f87c5081b321b 4218 ruby
Bug#797146: marked as done (RFP: ruby-middleware -- Generalized implementation of the middleware abstraction for Ruby)
Your message dated Tue, 29 Dec 2015 13:52:59 + with message-id and subject line Bug#797146: fixed in ruby-middleware 0.1.0-1 has caused the Debian Bug report #797146, regarding RFP: ruby-middleware -- Generalized implementation of the middleware abstraction for Ruby to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 797146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist * Package name: ruby-middleware Version : 0.1.0 Upstream Author : Mitchell Hashimoto * URL : https://github.com/mitchellh/middleware * License : MIT Programming Lang: Ruby Description : Generalized implementation of the middleware abstraction for Ruby --- End Message --- --- Begin Message --- Source: ruby-middleware Source-Version: 0.1.0-1 We believe that the bug you reported is fixed in the latest version of ruby-middleware, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 797...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Lee (李健秋) (supplier of updated ruby-middleware package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 28 Aug 2015 14:00:00 +0800 Source: ruby-middleware Binary: ruby-middleware Architecture: source all Version: 0.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Andrew Lee (李健秋) Description: ruby-middleware - middleware abstraction for Ruby. Closes: 797146 Changes: ruby-middleware (0.1.0-1) unstable; urgency=medium . * Initial release (Closes: #797146) Checksums-Sha1: ff613b820273199919461ba28d842e868dc5b7e2 2080 ruby-middleware_0.1.0-1.dsc 6f81e5ea41cfb97b279692fff6060a327855d2d2 8493 ruby-middleware_0.1.0.orig.tar.gz 049684dba801cea325dbf2589b956bdd10ad94dd 2236 ruby-middleware_0.1.0-1.debian.tar.xz a69936161078ea69c9e02517375a5419538b08e8 8348 ruby-middleware_0.1.0-1_all.deb Checksums-Sha256: 0d46eaac7fa0a6c903664ab8fbfb144c0b642e8059cf489fc1cb1f7e1d397f5d 2080 ruby-middleware_0.1.0-1.dsc c48be6bbfde340aa261b42957c5e67cbef006499f601bb381626278a47f444ae 8493 ruby-middleware_0.1.0.orig.tar.gz d454a75907fbd0bde8eeb6896fa2a5715582a1a302745062a3e2a655f77a855b 2236 ruby-middleware_0.1.0-1.debian.tar.xz 1abd0abd0ee2b5e9c54bffbf3c4df51ee6e5f22520e968a27e7f63bdb742cc1b 8348 ruby-middleware_0.1.0-1_all.deb Files: 22ca31de4d4a488243e5fc3b846e1d2c 2080 ruby optional ruby-middleware_0.1.0-1.dsc e0cbe534a9c7e59355755dba020c2e9a 8493 ruby optional ruby-middleware_0.1.0.orig.tar.gz 57bb820a827a84b31403f9e601db4de7 2236 ruby optional ruby-middleware_0.1.0-1.debian.tar.xz afb8309f56648da841c099c76ad5a52c 8348 ruby optional ruby-middleware_0.1.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWglxHAAoJEOfL4VKsF/lzRFkQAJg9ErgYJyl8fuM8RLDN/t1Q oL9DVbQuZ2tJZxyY3mJ1oDw5L5gQesswbyLxQFbfnfQgx7ylQ3fDDzcfk8SuGS5Z 0dPXCttEF7bJ39RkUDjPF0zrGuYLDVn7vGq0n4CFNgrAoANdif/nGeIyxF++IdB4 auYMqenQPXXqP0FCRuoRNQbv5zZTkymruGU+SgRD14P+8Y+ImpiZ+cUIi2ikkm5D h7JGWOi0+sVkAcWmaPE6G3PD65b8UQxgvdkFcQZT+WAV9Vsp88KyUgGdhh8n1K7t VZlbVCGOrUwmEoIEIvl1h5y5mJSwZ8AAFLmEy9T16Nt3tIFYAthK3NNh48kJkI6x IYtnVMgINXv6bU2zfXXvb9os0wiMaZ+cgSQJq4uhyKNVzeb3lGNs9GGAFlAokiWj QOxPF72YlOG0snInnv4CCMVHT/AbtZMl/ln91pGNDrVOA13+HMon3OvYPcgORJ3O fKxFaHBFbLgGV0yGUSrcUX8vPWIp4DRRVMxdeSs95yqC51k1I1gv1oWShWqzVkQR g8dV/vYbqGmyR7VdmG7BpcqPKzkLllsVzQAyKsPdeEHgymzgoVEtCdLR4BgwmerI gvxm7IsrBZsYsvhMxQ/CwX9Rma6Apx+P63Nrh4Jgl/0QGPUl3cGvnb56TOPrBjXT Gja8RfVKV6AQFxYQk9fo =wafX -END PGP SIGNATURE End Message ---
Bug#797143: marked as done (RFP: ruby-innertube -- A thread-safe resource pool, originally borne in riak-client (Ripple).)
Your message dated Tue, 29 Dec 2015 13:52:59 + with message-id and subject line Bug#797143: fixed in ruby-innertube 1.1.0-1 has caused the Debian Bug report #797143, regarding RFP: ruby-innertube -- A thread-safe resource pool, originally borne in riak-client (Ripple). to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 797143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist * Package name: ruby-innertube Version : 1.1.0 Upstream Author : Sean Cribbs Kyle Kingsbury * URL : http://github.com/basho/innertube * License : MIT Programming Lang: Ruby Description : A thread-safe resource pool, originally borne in riak-client (Ripple). Because everyone needs their own pool library. --- End Message --- --- Begin Message --- Source: ruby-innertube Source-Version: 1.1.0-1 We believe that the bug you reported is fixed in the latest version of ruby-innertube, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 797...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Lee (李健秋) (supplier of updated ruby-innertube package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 28 Aug 2015 13:35:09 +0800 Source: ruby-innertube Binary: ruby-innertube Architecture: source all Version: 1.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Andrew Lee (李健秋) Description: ruby-innertube - thread-safe re-entrant resource pool Closes: 797143 Changes: ruby-innertube (1.1.0-1) unstable; urgency=medium . * Initial release (Closes: #797143) Checksums-Sha1: 4f25514a6900d096d77031417b36afef6f11d608 2063 ruby-innertube_1.1.0-1.dsc bd8dd2343180225f6c395546a1526e29f1bc4cad 8232 ruby-innertube_1.1.0.orig.tar.gz 1aa45d21797c4914f46046b56bb46198b96d52f8 2124 ruby-innertube_1.1.0-1.debian.tar.xz 87cd90227b41bbbc53fb56334070670d47be862f 5142 ruby-innertube_1.1.0-1_all.deb Checksums-Sha256: ca8b30ec0b822c863cc5079ee059a2409b7f85420f630e887c80cd942cef15ca 2063 ruby-innertube_1.1.0-1.dsc 6a27da82e47c390e67130d67d64cf7e7a6ce5d073223eafcc7bf984af1dcda4f 8232 ruby-innertube_1.1.0.orig.tar.gz 12c15bfd533b0df30c574e10a49ece284159b14965d9cf328c4f61c075b7fab0 2124 ruby-innertube_1.1.0-1.debian.tar.xz 7fdbb4d050e9423e44a2a43458ece51facad3b02db9fc9771a4c45a6092fcd61 5142 ruby-innertube_1.1.0-1_all.deb Files: 73b859664a94193716f08ec22c79fb00 2063 ruby optional ruby-innertube_1.1.0-1.dsc b09be05bba5f6c8e4dce6fcb4193adb0 8232 ruby optional ruby-innertube_1.1.0.orig.tar.gz be1dc5a2aa9ebd2a78783c687170b070 2124 ruby optional ruby-innertube_1.1.0-1.debian.tar.xz a4c08458777d54470ac6f5ca8588870b 5142 ruby optional ruby-innertube_1.1.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWgWpUAAoJEOfL4VKsF/lzDp4P/1hadjBn1nChMZZSkSiPFzJm GN0FI4IWxZ36M9IRaU1s1gh3S+Qbdhr012IC/LjbGTbrVJm31vYzhJuL1MKly7IT viKxpvAYykZw5HcDGhTJnxRKkW1RJe9Y6sjhOevVoOxIN7XWv0RFfeNdDcz0XKxa pHA5iCh/7Txv6gA9AnAr0nEepu6kvz/ISfQ9zZ58bNBnt9s7SOLESDEO8hQnr1IF 2O4NwXAaYuPwn7Gp2eWVQBcAGzg4kNp5pwZSFnL+TYCi8/mI87ANWu+DXMoMx72p o6izS0Dw3CNdKP54+GxP/z0oDDYwq4++oRegRuJ2NwFU+Q/h9NWi1v2fMGgmdi0i +Cbr1P29DLB80ItNXISs6IGIKFhVrRYP2GXQziHxDN/3eQKzV+ZuOA4n9mA5mwj8 EijyPGTwVlVAf9htJCK54i347iW5MD8FM+NcW7fiPREzDskC+YUQ+431fNbwzVC6 srNUfjXBfbYJ0z4tVekh4TPDm0wWoB3hrjxd8JwdCidnqkmADQImBoHXA8IAXvHN 3nKks0IbVp4dF5v20/ez4xuj8f5INbDg+K2WRmGcgbbPeBVRC5on3OCXxx+JZ89G QkdzWHXUm4QaLx5aAi5f83+GfXXXPF2WsQTA1cu5U+2XCO4fkfuCXsSldQPqgpy3 wqs9Klg13jHrw7UEkaUy =7ydx -END PGP SIGNATURE End Message ---
Bug#797152: marked as done (RFP: ruby-rails-tokeninput -- Jquery Tokeninput automated install for Rails 3.1+)
Your message dated Tue, 29 Dec 2015 13:53:01 + with message-id and subject line Bug#797152: fixed in ruby-rails-tokeninput 1.7.0-1 has caused the Debian Bug report #797152, regarding RFP: ruby-rails-tokeninput -- Jquery Tokeninput automated install for Rails 3.1+ to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 797152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797152 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist * Package name: ruby-rails-tokeninput Version : 1.7.0 Upstream Author : Han * License : MIT Programming Lang: Ruby Description : Jquery Tokeninput automated install for Rails 3.1+ Gem installation of jquery tokeninput scripts and stylesheets. --- End Message --- --- Begin Message --- Source: ruby-rails-tokeninput Source-Version: 1.7.0-1 We believe that the bug you reported is fixed in the latest version of ruby-rails-tokeninput, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 797...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Lee (李健秋) (supplier of updated ruby-rails-tokeninput package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 28 Aug 2015 14:34:17 +0800 Source: ruby-rails-tokeninput Binary: ruby-rails-tokeninput Architecture: source all Version: 1.7.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Andrew Lee (李健秋) Description: ruby-rails-tokeninput - jquery tokeninput automated install Closes: 797152 Changes: ruby-rails-tokeninput (1.7.0-1) unstable; urgency=medium . * Initial release (Closes: #797152) Checksums-Sha1: 05fcff9a4b21f8837d285a3aa04f7f977ae307ee 2132 ruby-rails-tokeninput_1.7.0-1.dsc 1e0b4e7e799300065145db4e8123662d31ac8d89 16833 ruby-rails-tokeninput_1.7.0.orig.tar.gz 90db044a854b6ca91d19029a94492d9afa2b4e69 2376 ruby-rails-tokeninput_1.7.0-1.debian.tar.xz 3c27d6c2aec1738be3a56a590af03cf84e6c402c 16606 ruby-rails-tokeninput_1.7.0-1_all.deb Checksums-Sha256: d833446980989a065a8bc241019ed0f2ddd105ab46e0be64554a7e94fdfaaffe 2132 ruby-rails-tokeninput_1.7.0-1.dsc 42a5a2921801878c56aa7af686d3cb18bac141a2f8cf058ee947308fdf6b4a2d 16833 ruby-rails-tokeninput_1.7.0.orig.tar.gz 2ceb5e3a043b8a9736a397fa157003ca2fa3327b0292755a9d6129a9775ae617 2376 ruby-rails-tokeninput_1.7.0-1.debian.tar.xz d39760413a8d62a3cd0f0c0a276e8366dca2d84cf68314e40059ac3d7b31c00a 16606 ruby-rails-tokeninput_1.7.0-1_all.deb Files: 3a7118aa741ba7c022ba916b216c93ab 2132 ruby optional ruby-rails-tokeninput_1.7.0-1.dsc 9a78bebfc14fa6aceceab61efe7291cf 16833 ruby optional ruby-rails-tokeninput_1.7.0.orig.tar.gz ca2b78d4dafe8fc06dd02cf106d37953 2376 ruby optional ruby-rails-tokeninput_1.7.0-1.debian.tar.xz 7217c29c864ca2002abcae6312de60a6 16606 ruby optional ruby-rails-tokeninput_1.7.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWgm1cAAoJEOfL4VKsF/lzQ00P/3vFtDj4HWKrksVfic84hfGM cobqbREQscMb/qnyEgfFIgMBNAfApaiDpJkjgBlcOvDjdVOJgPNlcgRxS3LuSim2 Z83rGSR7k3D4fXgH8GPdNgrwNmJebZzwh6PVErxePjRSr1UNGJq3N0JVrrGfB25Q F8v5VuVzhNViDjCauY9OqZWgLJEWTK3qrAwm/5LrtjKaG7aLCjNtg2y6VQyzJnYL R/lX30Qsrqfds891vpHjvHmLE5eufIiAjbXHZX/T+DgeABGqvgk4UOnPo8X1ofdX t+3pNHgumPk4/vj8/a4Sw2F8Xa/U3OPj53Sp212nIwUunOneQBqdGPnvztmQvfIq +EeADA6GmKoosQ2UYsSYBlIQHvW1xQN38BOyDn+B32BWdhhM26GfeDsnyENaOwoi M4N20eWlCGrSl554H40XAcWYuaIqsXSJwgFdrdEVP6LwrJFCznkNIyDQypACh8z4 zZmr6s+wfCVauyCjUN96rsGLIMp+j6hX/N4MFNLXDMdCZoUyFz/heO8voTYDYtgp tAQIVfqr3dSct24VZm/iZJ5GcA5Cdf3etLh97RKzU1PDh9xIhIOW5iu8mu/bCJcs i+RA7OiO+MZsrV42TahQSnUUPdLzhVUp3XzktxBi25nXRpdaECQi4xe11ttCxNPH 8WmHOxkLdwbgzn9RoS/x =p+bV -END PGP SIGNATURE End Message ---
Bug#797144: marked as done (RFP: ruby-joiner -- Builds ActiveRecord joins from association paths)
Your message dated Tue, 29 Dec 2015 13:52:59 + with message-id and subject line Bug#797144: fixed in ruby-joiner 0.3.4-1 has caused the Debian Bug report #797144, regarding RFP: ruby-joiner -- Builds ActiveRecord joins from association paths to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 797144: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist * Package name: ruby-joiner Version : 0.3.4 Upstream Author : Pat Allan * URL : https://github.com/pat/joiner * License : MIT Programming Lang: Ruby Description : Builds ActiveRecord joins from association paths Builds ActiveRecord outer joins from association paths and provides references to table aliases. --- End Message --- --- Begin Message --- Source: ruby-joiner Source-Version: 0.3.4-1 We believe that the bug you reported is fixed in the latest version of ruby-joiner, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 797...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Lee (李健秋) (supplier of updated ruby-joiner package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 28 Aug 2015 13:41:58 +0800 Source: ruby-joiner Binary: ruby-joiner Architecture: source all Version: 0.3.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Andrew Lee (李健秋) Description: ruby-joiner - builds activerecord joins from association paths Closes: 797144 Changes: ruby-joiner (0.3.4-1) unstable; urgency=medium . * Initial release (Closes: #797144) Checksums-Sha1: a815148a54b36b5293b615f09e0fa7ac31e482f4 2026 ruby-joiner_0.3.4-1.dsc 0a941095e74bee36d3073cd1e8bece0d6a8fccfd 5219 ruby-joiner_0.3.4.orig.tar.gz 492a557cc1b04e76b61bd79ad6fdd8b6a0bae581 2264 ruby-joiner_0.3.4-1.debian.tar.xz c744ad608d3bef55b91201430c2b1e3ccfa065db 4842 ruby-joiner_0.3.4-1_all.deb Checksums-Sha256: 59843dbadedec433a65746c18eb5edde7cbb399f32ba9c672dec301bed9b309b 2026 ruby-joiner_0.3.4-1.dsc e3378583e1fce466adec80b6cbffc1fc9075f306e69df1459b0627d8e7741848 5219 ruby-joiner_0.3.4.orig.tar.gz 7ca79147163554abe1588c34fde5929050a95f1b986a0f9e11d2cf5a416c3e8b 2264 ruby-joiner_0.3.4-1.debian.tar.xz 820145e2c2d009a1322692554cec25733c9063ca46d6998d2ded701c87599bcd 4842 ruby-joiner_0.3.4-1_all.deb Files: 1a53fb223686bd940bf1f676bc4df396 2026 ruby optional ruby-joiner_0.3.4-1.dsc a6acf22b734ff6f6736c6d4bc863ed38 5219 ruby optional ruby-joiner_0.3.4.orig.tar.gz 45e972e65c06f363f51c2caabba55114 2264 ruby optional ruby-joiner_0.3.4-1.debian.tar.xz d768fdfde5e023ea3e39920f9a24f12a 4842 ruby optional ruby-joiner_0.3.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWgWv9AAoJEOfL4VKsF/lz6ocP+wVPNzy1eR6VLxrQU+FyNHJb aEKuFhYkfsAGxJ5lbLxlKkJVrw7yl+F+tdJAPSeYkYhT1h3qNxx4zYWNuXHdppeq 3L/Y/oLo9TTR5evyH3C6ZerQYqAyKrXNIm0PPS5pNnexXF0Vo81wVfQANdZSXQ1I BhUihfJFrfCfxzHKe9lHqN9hK6hou5GG0DP2a2lwm9OAJua2hiOEsYSX3+Njmt/n pacr54aUHSRChcnJ7t2PYmke7G5qFR0ZioO/R4OIrW8n0KAXel7oaCsFGcZmZp6V +XA1edbGlxkM4f+FLkWztrjSxlVyD4d9SKLFnsk6gadZSoSGwiphtVnhnRtrtKEc lkvDtia4SZ6WoZUdpzvHlihRXOCaC7VB44lmCL32j3d0CWBexdEfFF1E7hVyBYoF hr6AU6FgEmKV9QEvIbZNSE/H+aUhn3T9h7GS90sbk45CBfjXYiiHJf/3ZIDYasGi vEEpwfb+aT/I8iT01P96O0fMURBwNXLXyoc5DmjDGFvtl8d7YOB5kVE0X5iISM70 dJ2oSMRYv+XKGJV5seZbVB78kghDtVBhqws6E5Be0FPtpOVjgq4VcxSdTPj0Nnxp 1Vyk6lnUOAHyI3OlK6vpkwOEUey2kg6CDAuSC7xvwcQf1Lt3DgjJaqmO1QvyreVW ShFWY19OPCp9oKtdUs63 =DRdh -END PGP SIGNATURE End Message ---
Bug#797147: marked as done (RFP: ruby-pundit -- OO authorization for Rails)
Your message dated Tue, 29 Dec 2015 13:53:00 + with message-id and subject line Bug#797147: fixed in ruby-pundit 1.0.1-1 has caused the Debian Bug report #797147, regarding RFP: ruby-pundit -- OO authorization for Rails to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 797147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797147 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist * Package name: ruby-pundit Version : 1.0.1 Upstream Author : Jonas Nicklas Elabs AB * URL : https://github.com/elabs/pundit * License : MIT Programming Lang: Ruby Description : OO authorization for Rails Object oriented authorization for Rails applications. --- End Message --- --- Begin Message --- Source: ruby-pundit Source-Version: 1.0.1-1 We believe that the bug you reported is fixed in the latest version of ruby-pundit, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 797...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Lee (李健秋) (supplier of updated ruby-pundit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 28 Aug 2015 14:07:05 +0800 Source: ruby-pundit Binary: ruby-pundit Architecture: source all Version: 1.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Andrew Lee (李健秋) Description: ruby-pundit - oo authorization for rails Closes: 797147 Changes: ruby-pundit (1.0.1-1) unstable; urgency=medium . * Initial release (Closes: #797147) Checksums-Sha1: 5341de6c9d73423454cbf2029885ee2ae52f8329 2031 ruby-pundit_1.0.1-1.dsc 210d6575f6e63acd1bf91001f3311cd6e039b4f8 16055 ruby-pundit_1.0.1.orig.tar.gz 915406f63c7c89fe59636f3f2bd5b215a31da22f 2152 ruby-pundit_1.0.1-1.debian.tar.xz 7a8d97dfc8e528ae032a236f29515c9162908d5c 14100 ruby-pundit_1.0.1-1_all.deb Checksums-Sha256: f2edd7b0a560da0046875fd0c2ecda42509a1ca01842c880d77b2ddfdd6a6281 2031 ruby-pundit_1.0.1-1.dsc c2a25ea3d3dd615ba661b2e6618c3c664c90cecf98de3d00c88f424c6b2317b4 16055 ruby-pundit_1.0.1.orig.tar.gz 627597d14dd091c999478a08993ec72a3edae1f76e26c3a515e987870caa3e01 2152 ruby-pundit_1.0.1-1.debian.tar.xz 6e359e946fda67d219e1e8143f890bf973b97de13f8211c3302a46e65b6a728c 14100 ruby-pundit_1.0.1-1_all.deb Files: 0dc7fed658ee8afd09a3d16c6cc8a341 2031 ruby optional ruby-pundit_1.0.1-1.dsc 8e2d3ad5255171a4e1d771b0aa45478a 16055 ruby optional ruby-pundit_1.0.1.orig.tar.gz 9bffea2870bae8ba5e776e4d59bb98d1 2152 ruby optional ruby-pundit_1.0.1-1.debian.tar.xz 99796209e121b46272570e3f55953e0a 14100 ruby optional ruby-pundit_1.0.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWgmq8AAoJEOfL4VKsF/lzeuYP/juXTkZRSukRvZDeUZhV4dgb YSyNISGk/r4ngwiFjttSZhUgQS0UxqIIlWJo0SEDdNZ2FchsrtwD5jXaztRRibQR EOBvRcBT4A7gd8twweAAthra/n2tvqJwBX9dJVBJ+UF4f7iw1so6fJpxABwMuFFd NNSRqvYR04o6UvN2OHxZ6XyPJAqe3iiKPeoNimIxHQhwTh2u/1H5D6D+D949jLGK lddjb786tDm9bXufA/MEUHhPnwUbxAbvsxnj7sY4wcFZT+ugDcoWSfc9029HQC8c B+REJ+zgisyk4UoFutYKrlwWJgazijCe2kB7LnSAXuZQcG3+MErOeX+O0uT0ZWPg oHwzK+C/8/YRgP27G8nulyfNFvXzO1pI8BMwKf2vOnxlztnSPtENd9k62fvXk/uB qwsduIyow8LI4xPp7t19kOq/qAaHdK5YL17Hh7evZLoc9MCaaUT1avbZTU3VeYwE ZC5yvd+KLiUzfLUaboQyKxDUzGG+BK+Pwsug4Lqi94SvY82fMNBT+e2KPbcnwvEj iBxLbPn0K0UHFyJygI+fEVZba42oZ4whqI58Odu6uHl1uTA/F0wscYBrRWN73o36 wMvsXBJq4Uktt0anEZffD8t0jr6p8csVAj1NoK/XTMnUMj+3cpdxa8L3ufmZvvEz bxS7ueCtwABUj5wzrH9G =ePjk -END PGP SIGNATURE End Message ---
Bug#809333: marked as done (musixtex: Bogus file /usr/share/texmf/fonts/map/dvips/musixtex-fonts/' in package)
Your message dated Tue, 29 Dec 2015 14:23:41 + with message-id and subject line Bug#809333: fixed in musixtex 1:1.20.ctan20151216-2 has caused the Debian Bug report #809333, regarding musixtex: Bogus file /usr/share/texmf/fonts/map/dvips/musixtex-fonts/' in package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: musixtex Version: 1:1.20.ctan20151216-1 Severity: minor Dear Maintainer, The musixtex package contains a file called /usr/share/texmf/fonts/map/dvips/musixtex-fonts/' (single quote as filename), its content looks like a misnamed font.map file. This may lead to quotation mismatches in skripts scanning the file system. *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 4.2.6-64 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages musixtex depends on: ii tex-common6.04 ii texlive-base 2015.20151225-1 ii texlive-binaries 2015.20150524.37493-7+b1 Versions of packages musixtex recommends: ii ghostscript 9.06~dfsg-2+deb8u1 Versions of packages musixtex suggests: ii m-tx 0.61.ctan20151217-1 ii pmx 2.7.0.ctan20150301-2 -- no debconf information --- End Message --- --- Begin Message --- Source: musixtex Source-Version: 1:1.20.ctan20151216-2 We believe that the bug you reported is fixed in the latest version of musixtex, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Norbert Preining (supplier of updated musixtex package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 21:41:14 +0900 Source: musixtex Binary: musixtex Architecture: source amd64 Version: 1:1.20.ctan20151216-2 Distribution: unstable Urgency: medium Maintainer: Debian TeX Maintainers Changed-By: Norbert Preining Description: musixtex - Typeset music scores with TeX Closes: 809333 Changes: musixtex (1:1.20.ctan20151216-2) unstable; urgency=medium . * remove dummy ' file, thanks Klaus Knopper (Closes: #809333) Checksums-Sha1: 836824c01ffcc18c711d9f2b843cc52507b87804 1989 musixtex_1.20.ctan20151216-2.dsc e1a1a2393724da6dd64656d92a279cfa01e6f6e9 17348 musixtex_1.20.ctan20151216-2.debian.tar.xz 9dadd6475c51633f7988e93e48b6e146914164c4 6298182 musixtex_1.20.ctan20151216-2_amd64.deb Checksums-Sha256: 3d5ab2e3659bd3b63e19e23b811dccd9cab36c8f394644a4b6358f23d11d0f85 1989 musixtex_1.20.ctan20151216-2.dsc 2c65f7b1fb22fa83131e20712e75cc04a09b589731275a3aea02b977066f30f7 17348 musixtex_1.20.ctan20151216-2.debian.tar.xz adb530f0dd35ae8774978844db86ee8c3c720333fd782797b685bba5a6163c94 6298182 musixtex_1.20.ctan20151216-2_amd64.deb Files: 6488453438c01b3f7e4c123358076d33 1989 tex optional musixtex_1.20.ctan20151216-2.dsc c863fc41aeae70ff2d1f0ed3f8d4af7d 17348 tex optional musixtex_1.20.ctan20151216-2.debian.tar.xz ca9f91ce810f4bfaebff706a8ea0ff0e 6298182 tex optional musixtex_1.20.ctan20151216-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVoKAPGyspEiGDNwTAQhAxg//RPN7wS8My1ryhTf5ypbyjBDVBCxmvsWo d5gK8Db5l2oUNNZdge3Ihq2qWL0+ZfQ6jHzTf7LFFdYaUNOAvhpSP8KG1ALPZxUe XeHvngN7GLz7K6Qczr8LbYnLX/8aotbIqIZBpvuRM6P2W8Z+iY2pY9eJn+PD4Hb7 p3vAAtzw0y+o8mESaHGuVp9FzL1KgG0wvoofbjtQRiUvUnMi0IVIGge9qYQ6RK3L /EILEtO5c+jlr0qwyB4SkNxbYNt8V6tBrJE/thkn9dhcq8TZY7Stw+G7t1RU0IuA GDdbSuQ3wE7JAR7ZE2hRILlDlOxgvYHQ4CkkGN0HO5ttkMU0Z6//6g8HeS4k9yVW L35X2nXV+nfNF8i987UlUWGshxhT/RKSeiN0gHa5i0vuRd5qwPU7tdgNvkMOf7Fp JCKqwFtg1a2Dx2jjW5caAvSKzSARJNRAsO6+NeJsN5ARty5kIGsw+J6zI3HakN3v XAMKaQhcPbO2lV1X052OhAvIDM7FnrnxRx4YHld3FJdvYhmsnsKT7Jngieqd8HSG 2NazwTY/TzDCx8koo32FaEedIhplJKJGKba1afLXL
Bug#803976: marked as done (cyrus-common: /usr/lib/cyrus/bin/upgrade-db delete /var/lib/cyrus/db on upgrade from wheezy to jessie)
Your message dated Tue, 29 Dec 2015 14:23:22 + with message-id and subject line Bug#803976: fixed in cyrus-imapd-2.4 2.4.18-3 has caused the Debian Bug report #803976, regarding cyrus-common: /usr/lib/cyrus/bin/upgrade-db delete /var/lib/cyrus/db on upgrade from wheezy to jessie to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 803976: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803976 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cyrus-common Version: 2.4.17+caldav~beta10-18 Severity: important Dear Maintainer, I had the same problem I had when I upgraded from squeeze to wheezy and we had resolved at #706862 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706862 The script /usr/lib/cyrus/bin/upgrade-db delete the directory /var/lib/cyrus/db The same solution works fine for me:: Replace: while read -r OLD_DBKEY OLD_DBVALUE ; do ... done < $OLD_LIST for: cat $OLD_LIST | \ while read -r OLD_DBKEY OLD_DBVALUE ; do ... done This creates a new child process with diferent variables Source: http://serverfault.com/questions/259339/bash-variable-loses-value-at-end-of-while-read-loop >From already thank you very much. Agu -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cyrus-common depends on: ii adduser 3.113+nmu3 ii db-upgrade-util 5.3.0 ii db-util 5.3.0 ii debconf [debconf-2.0] 1.5.56 ii dpkg1.17.25 ii gawk1:4.1.1+dfsg-1 ii libc6 2.19-18+deb8u1 ii libcomerr2 1.42.12-1.1 ii libdb5.35.3.28-9 ii libical1a 1.0-1.3 ii libkrb5-3 1.12.1+dfsg-19 ii libldap-2.4-2 2.4.40+dfsg-1+deb8u1 ii libsasl2-2 2.1.26.dfsg1-13+deb8u1 ii libsasl2-modules2.1.26.dfsg1-13+deb8u1 ii libsnmp30 5.7.2.1+dfsg-1 ii libsqlite3-03.8.7.1-1+deb8u1 ii libssl1.0.0 1.0.1k-3+deb8u1 ii libwrap07.6.q-25 ii libzephyr4 3.1.2-1 ii netbase 5.3 ii perl5.20.2-3+deb8u1 ii postfix [mail-transport-agent] 2.11.3-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages cyrus-common recommends: ii cyrus-admin 2.4.17+caldav~beta10-18 ii cyrus-imapd 2.4.17+caldav~beta10-18 ii cyrus-pop3d 2.4.17+caldav~beta10-18 Versions of packages cyrus-common suggests: ii apt-listchanges2.85.13+nmu1 ii cyrus-admin2.4.17+caldav~beta10-18 pn cyrus-caldav ii cyrus-clients 2.4.17+caldav~beta10-18 pn cyrus-doc ii cyrus-imapd2.4.17+caldav~beta10-18 pn cyrus-murder pn cyrus-nntpd ii cyrus-pop3d2.4.17+caldav~beta10-18 pn cyrus-replication ii sasl2-bin 2.1.26.dfsg1-13+deb8u1 -- Configuration Files: /etc/imapd.conf changed (relevant) configdirectory: /var/lib/cyrus proc_path: /var/run/cyrus/proc mboxname_lockpath: /var/run/cyrus/lock defaultpartition: default partition-default: /var/spool/cyrus/mail (... other) -- debconf information: * cyrus-common/removespools: true --- End Message --- --- Begin Message --- Source: cyrus-imapd-2.4 Source-Version: 2.4.18-3 We believe that the bug you reported is fixed in the latest version of cyrus-imapd-2.4, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 803...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý (supplier of updated cyrus-imapd-2.4 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Dec 2015 14:40:40 +0100 Source: cyr
Bug#809133: marked as done (ggcov: FTBFS: ERROR: (test001) tggcov failed, see log or re-run with -D all,verbose --no-log)
Your message dated Tue, 29 Dec 2015 14:32:28 + with message-id and subject line Bug#809133: fixed in ggcov 0.9-10 has caused the Debian Bug report #809133, regarding ggcov: FTBFS: ERROR: (test001) tggcov failed, see log or re-run with -D all,verbose --no-log to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ggcov Version: 0.9-9 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, ggcov fails to build from source in unstable/amd64. [..] debian/rules override_dh_auto_test make[1]: Entering directory '/home/lamby/temp/cdt.20151227140648.NrwtHfgh8n/ggcov-0.9' (cd test && ./runtest) Running tests hostname: "b2f2f9bb7807" date: "20151227T140923" uname -s: "Linux" uname -m: "x86_64" uname -r: "4.2.0-1-amd64" head -1 /etc/os-release: "PRETTY_NAME="Debian GNU/Linux stretch/sid"" which gcc: "/usr/bin/gcc" gcc --version: "gcc (Debian 5.3.1-4) 5.3.1 20151219" which g++: "/usr/bin/g++" g++ --version: "g++ (Debian 5.3.1-4) 5.3.1 20151219" PASS: (test000) unit tests ERROR: (test001) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test002) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test004) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test005.1) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test006) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test007) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test008.0) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test009) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test010) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test011.1) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test013) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test014) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test015.a001) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test016.1) tggcov failed, see log or re-run with -D all,verbose --no-log PASS: (test021) unit test for libpopt / fakepopt.c ERROR: (test029) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test030) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test033) tggcov failed, see log or re-run with -D all,verbose --no-log ERROR: (test034) tggcov failed, see log or re-run with -D all,verbose --no-log Total: 2/20 tests passed debian/rules:34: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory '/home/lamby/temp/cdt.20151227140648.NrwtHfgh8n/ggcov-0.9' debian/rules:12: recipe for target 'build' failed make: *** [build] Error 2 [..] The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- ggcov.0.9-9.unstable.amd64.log.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Source: ggcov Source-Version: 0.9-10 We believe that the bug you reported is fixed in the latest version of ggcov, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated ggcov package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 00:10:40 + Source: ggcov Binary: ggcov Architecture: source amd64 Version: 0.9-10 Distribution: sid Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastai
Bug#809330: marked as done (initramfs-tools: not able to create a fresh initramfs image)
Your message dated Tue, 29 Dec 2015 20:36:32 +0530 with message-id <1451401592.10819.6.ca...@researchut.com> and subject line Re: initramfs-tools: not able to create a fresh initramfs image has caused the Debian Bug report #809330, regarding initramfs-tools: not able to create a fresh initramfs image to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initramfs-tools Version: 0.120 Severity: important The bug was seen on a different test box. But given the logs below, the information provided should be sufficient to confirm. root@debian-sanboot:/# update-initramfs -c /boot/sanboot.initramfs Invalid argument for option -k. Usage: /usr/sbin/update-initramfs [OPTION]... Options: -k [version] Specify kernel version or 'all' -c Create a new initramfs -u Update an existing initramfs -d Remove an existing initramfs -t Take over a custom initramfs with this one -b Set alternate boot directory -v Be verbose -h This message root@debian-sanboot:/# update-initramfs -c /boot/sanboot.initramfs -k `uname -r` Invalid argument for option -k. Usage: /usr/sbin/update-initramfs [OPTION]... Options: -k [version] Specify kernel version or 'all' -c Create a new initramfs -u Update an existing initramfs -d Remove an existing initramfs -t Take over a custom initramfs with this one -b Set alternate boot directory -v Be verbose -h This message The issue is seen only with -c. root@debian-sanboot:/# update-initramfs -u -k `uname -r` update-initramfs: Generating /boot/initrd.img-4.3.0-1-amd64 On the other hand, mkinitramfs works fine. root@debian-sanboot:~# mkinitramfs -o /boot/sanboot.init root@debian-sanboot:~# -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 22M Oct 8 21:54 /boot/initrd.img-4.1.8+ -rw-r--r-- 1 root root 31M Nov 7 12:29 /boot/initrd.img-4.2.5+ -rw-r--r-- 1 root root 30M Dec 28 12:00 /boot/initrd.img-4.3.0-1-amd64 -rw-r--r-- 1 root root 31M Dec 12 12:08 /boot/initrd.img-4.3.1+ -rw-r--r-- 1 root root 31M Dec 16 17:10 /boot/initrd.img-4.3.3+ -- /proc/cmdline BOOT_IMAGE=/vmlinuz-4.3.3+ root=UUID=339197eb-781c-4a32-9265-060536dfa9e0 ro cgroup_enable=memory swapaccount=1 libata.force=1:3 quiet scsi_mod.use_blk_mq=1 dm_mod.use_blk_mq=1 no_console_suspend splash -- resume RESUME=/dev/mapper/SSHDCrypt-SWAP -- /proc/filesystems btrfs ext3 ext4 fuseblk vfat -- lsmod Module Size Used by uas20480 0 usb_storage65536 1 uas vhost_net 20480 5 vhost 32768 1 vhost_net macvtap20480 1 vhost_net macvlan24576 1 macvtap tun28672 11 vhost_net ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter veth 16384 0 ctr16384 2 ccm20480 2 rfcomm 69632 2 binfmt_misc20480 1 bnep 20480 2 bridge114688 0 stp16384 1 bridge llc16384 2 stp,bridge ip6table_mangle16384 0 ip6table_nat 16384 0 nf_nat_ipv616384 1 ip6table_nat nf_log_ipv616384 2 nf_conntrack_ipv6 16384 5 nf_defrag_ipv6 36864 1 nf_conntrack_ipv6 ip6table_filter16384 1 ip6_tables 28672 3 ip6table_filter,ip6table_mangle,ip6table_nat xt_CHECKSUM16384 2 iptable_mangle 16384 1 ipt_MASQUERADE 16384 1 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 3 nf_nat_ipv4,nf_nat_ipv6,nf_nat_masquerade_ipv4 nf_log_ipv416384 2 nf_log_common 16384 2 nf_log_ipv4,nf_log_ipv6 xt_LOG 16384 4 xt_limit 16384 4 xt_tcpudp 16384 12 xt_mac 16384 6 nf_conntrack_ipv4 20480 9 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_multiport 16384 4 xt_recent 20480 12 xt_addrtype16384 9 xt_conntrack 16384 12 nf_conntrack 118784 7 nf_nat,nf_nat_ipv4,nf_nat_ipv6,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntr
Bug#723987: marked as done (console-common: keymap.sh prevents console-common from being removed)
Your message dated Tue, 29 Dec 2015 15:37:20 + with message-id and subject line Bug#723987: fixed in console-common 0.7.89 has caused the Debian Bug report #723987, regarding console-common: keymap.sh prevents console-common from being removed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 723987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-common Version: 0.7.87 Severity: important Tags: d-i Dear Maintainer, When trying to remove console-common through various means, I keep running into this issue; sudo apt-get remove console-common Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: console-common 0 upgraded, 0 newly installed, 1 to remove and 3 not upgraded. 1 not fully installed or removed. After this operation, 811 kB disk space will be freed. Do you want to continue [Y/n]? Y (Reading database ... 226607 files and directories currently installed.) Removing console-common ... Failed to issue method call: Unit keymap.sh.service not loaded. invoke-rc.d: initscript keymap.sh, action "stop" failed. dpkg: error processing console-common (--remove): subprocess installed pre-removal script returned error exit status 5 update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Failed to issue method call: Unit keymap.sh.service failed to load: No such file or directory. See system logs and 'systemctl status keymap.sh.service' for details. invoke-rc.d: initscript keymap.sh, action "start" failed. dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 6 Errors were encountered while processing: console-common E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-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 console-common depends on: ii console-data 2:1.12-2 ii debconf [debconf-2.0] 1.5.51 ii debianutils4.4 ii kbd1.15.5-1 ii lsb-base 4.1+Debian12 console-common recommends no packages. console-common suggests no packages. -- Configuration Files: /etc/init.d/keymap.sh changed [not included] -- debconf information: * console-data/keymap/policy: Select keymap from arch list console-data/bootmap-md5sum: fb08bd87d57e5a2387e0872d38f21f5c console-data/keymap/full: console-data/keymap/template/variant: console-data/keymap/template/layout: * console-data/keymap/family: qwerty console-data/keymap/ignored: console-data/keymap/powerpcadb: console-data/keymap/template/keymap: Regards, Jeremiah --- End Message --- --- Begin Message --- Source: console-common Source-Version: 0.7.89 We believe that the bug you reported is fixed in the latest version of console-common, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 723...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated console-common package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 01:04:20 + Source: console-common Binary: console-common dh-consoledata Architecture: source all Version: 0.7.89 Distribution: sid Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: console-common - basic infrastructure for text console configuration dh-consoledata - debhelper-based script to help packaging console data files Closes: 276220 502897 516002 677314 723987 796606 Changes: console-common (0.7.89) unstable; urgency=medium . [Felipe Sateler] * Drop keymap.sh script, superseded in favor of console-setup Closes: #796606, #677314, #276220, #516002, #723987. . [Alastai
Bug#276220: marked as done (console-common: keymap.sh stops the boot using serial console)
Your message dated Tue, 29 Dec 2015 15:37:20 + with message-id and subject line Bug#276220: fixed in console-common 0.7.89 has caused the Debian Bug report #276220, regarding console-common: keymap.sh stops the boot using serial console to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 276220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=276220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-common Version: 0.7.47 Severity: important My router running sarge stopped booting after a kernel change... after using the serial console to get in, pressing ^C the boot just continues. The problem is in keymap.sh: Starting Bootlog daemon: bootlogd. DEBUG: I'm initrd-tools.sh with set -x ++ . /etc/default/initrd-tools.sh +++ KEEPINITRD= ++ '[' '' = yes ']' ++ command -v blockdev ++ '[' -f /proc/mounts ']' ++ grep -q '^[^ ]* /initrd ' /proc/mounts ++ '[' -c /initrd/dev/.devfsd ']' ++ umount /initrd ++ '[' -b /dev/ram0 ']' ++ blockdev --flushbufs /dev/ram0 DEBUG I'm keymap.sh with set -x +++ fgconsole ++ CONSOLE_TYPE=serial ++ command -v loadkeys ++ CONFDIR=/etc/console ++ CONFFILEROOT=boottime ++ EXT=kmap ++ CONFFILE=/etc/console/boottime.kmap.gz ++ case "$1" in ++ unmount_proc=no ++ '[' '!' -x /proc/1 ']' ++ reset_kernel ++ '[' -x /sbin/sysctl ']' ++ '[' -r /etc/sysctl.conf ']' ++ grep -v '^\#' /etc/sysctl.conf ++ grep -q keycodes ++ '[' 1 = 0 ']' ++ '[' -f /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes ']' ++ linux_keycodes=1 ++ '[' 1 -gt 0 ']' ++ '[' -r /etc/console/boottime.kmap.gz ']' ++ unicode_start_stop ++ '[' -x /usr/bin/unicode_start ']' ++ '[' -x /usr/bin/unicode_stop ']' ++ '[' -r /etc/environment ']' ++ for var in LANG LC_ALL LC_CTYPE +++ egrep '^[^#]*LANG=' /etc/environment +++ cut -d= -f2 ++ value=es_ES@euro ++ eval LANG=es_ES@euro +++ LANG=es_ES@euro ++ for var in LANG LC_ALL LC_CTYPE +++ egrep '^[^#]*LC_ALL=' /etc/environment +++ cut -d= -f2 ++ value= ++ eval LC_ALL= +++ LC_ALL= ++ for var in LANG LC_ALL LC_CTYPE +++ egrep '^[^#]*LC_CTYPE=' /etc/environment +++ cut -d= -f2 ++ value= ++ eval LC_CTYPE= +++ LC_CTYPE= +++ LANG=es_ES@euro +++ LC_ALL= +++ LC_CTYPE= +++ locale charmap ++ CHARMAP=ISO-8859-15 ++ '[' ISO-8859-15 = UTF-8 ']' ++ /usr/bin/unicode_stop ï ^[[24;4R ^--- here the boot up stops forever. hitting ^C it continues... ^[[24;4RSetting disc parameters: /dev/hda, /dev/hdc, /dev/hdd, done. Activating swap. Adding 358836k swap on /dev/hda1. Priority:9 extents:1 Checking root file system... fsck 1.35 (28-Feb-2004) /dev/hda5: clean, 81249/320640 files, 451253/640079 blocks EXT3 FS on hda5, internal journal System time was Tue Oct 12 17:45:19 UTC 2004. Setting the System Clock using the Hardware Clock as reference... [...] It breaks my system, so it is important in my opinion. Regards, -- Roberto Lumbreras .''`. Debian Developer `. `' `- -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-k7 Locale: LANG=es_ES@euro, LC_CTYPE=es_ES@euro Versions of packages console-common depends on: ii console-data2002.12.04dbs-46 Keymaps, fonts, charset maps, fall ii console-tools 1:0.2.3dbs-55Linux console and font utilities ii debconf 1.4.32 Debian configuration management sy ii debianutils 2.8.4Miscellaneous utilities specific t -- debconf information: console-data/keymap/template/layout: * console-data/keymap/family: qwerty console-data/keymap/powerpcadb: console-data/keymap/template/variant: console-data/keymap/ignored: console-data/keymap/full: console-data/keymap/template/keymap: * console-data/keymap/policy: Don't touch keymap console-data/bootmap-md5sum: 5ec8881eec66ecaa0d1ddfc5aae0202f --- End Message --- --- Begin Message --- Source: console-common Source-Version: 0.7.89 We believe that the bug you reported is fixed in the latest version of console-common, which is due to be installed in the Debian FTP archive.
Bug#516002: marked as done (console-common: keymap is not loaded at startup)
Your message dated Tue, 29 Dec 2015 15:37:20 + with message-id and subject line Bug#516002: fixed in console-common 0.7.89 has caused the Debian Bug report #516002, regarding console-common: keymap is not loaded at startup to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 516002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-common Version: 0.7.80 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have to run /etc/init.d/keymap.sh manually to load the keymap. - -- System Information: Debian Release: 5.0 Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=sv_SE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages console-common depends on: ii console-data 2:1.07-11 keymaps, fonts, charset maps, fall ii console-tools1:0.2.3dbs-65.1 Linux console and font utilities ii debconf [debconf-2.0]1.5.24 Debian configuration management sy ii debianutils 2.31Miscellaneous utilities specific t ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip console-common recommends no packages. console-common suggests no packages. - -- debconf information: console-data/keymap/template/layout: * console-data/keymap/family: qwerty console-data/keymap/powerpcadb: console-data/keymap/template/variant: console-data/keymap/ignored: * console-data/keymap/full: se-latin1 console-data/keymap/template/keymap: * console-data/keymap/policy: Select keymap from arch list console-data/bootmap-md5sum: eff9ea13a729b014c19cf311f23b649a -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkmcVhYACgkQw5UvgfnzqGqwYACbB3yISeRxHpsWaj8ad5h4XDwR x0kAnAy8sAxrjj6+Isp06Ms6KoxIgPAS =iXZJ -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: console-common Source-Version: 0.7.89 We believe that the bug you reported is fixed in the latest version of console-common, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 516...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated console-common package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 01:04:20 + Source: console-common Binary: console-common dh-consoledata Architecture: source all Version: 0.7.89 Distribution: sid Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: console-common - basic infrastructure for text console configuration dh-consoledata - debhelper-based script to help packaging console data files Closes: 276220 502897 516002 677314 723987 796606 Changes: console-common (0.7.89) unstable; urgency=medium . [Felipe Sateler] * Drop keymap.sh script, superseded in favor of console-setup Closes: #796606, #677314, #276220, #516002, #723987. . [Alastair McKinstry] * Move to Standards-Version: 3.9.6 * If 'machine' not in /proc/cpuinfo, use 'platform'. Closes: #502897. Checksums-Sha1: be1d25c0dea3f116ff247f34d8582411f46ed723 1624 console-common_0.7.89.dsc d3e78faaabc3f7e7ac4d13c3d07cb0ec45ce6e62 136164 console-common_0.7.89.tar.xz 633af24755cb50536e6dd0d032750428748f74a0 120254 console-common_0.7.89_all.deb 5790a0f99eb57dacc65f889dc93007ba2d110854 78698 dh-consoledata_0.7.89_all.deb Checksums-Sha256: 3469ed60dd6cd9265d60cb754af6549fdc83513334427efea87b13daaf481cd3 1624 console-common_0.7.89.dsc 6bd10c7e06c1fc3acb3325b54ee4c24fd5a9302eaa06ef1ea1d3d7038c612ba2 136164 console-common_0.7.89.tar.xz 1ae5cac10fbdefc88eadfcb807d03986ac4a6e48f68c689a300e9bf7282704cb 120254 console-common_0.7.89_all.deb 4e7e0ca89d751f10ff07ec6f530ffc02154d8b2ed4cdeeacb0f298501a2fb9b0 78698 dh-consoledata_0.7.89_all.deb Files: 5676236a258e6a09239adbb6ed479b84 1624 utils optional console-common_0.7.89.dsc d3363bc084037bd03f7062f0881e66a7 136164 utils optional console-common_0.7.89.tar.xz 589bb85f4cf5e4901bb38ad243a4d6ec 120254 uti
Bug#677314: marked as done (console-common: Please ship systemd service file)
Your message dated Tue, 29 Dec 2015 15:37:20 + with message-id and subject line Bug#677314: fixed in console-common 0.7.89 has caused the Debian Bug report #677314, regarding console-common: Please ship systemd service file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 677314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-data Version: 0.7.87 Severity: wishlist User: syst...@packages.debian.org Usertags: console-common Dear Debian folks, it would be great if you could enable systemd support for console-common by packaging a service file [1] which could be loaded instead of `/etc/init.d/keymap.sh`. Thank you very much, Paul -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages console-common depends on: ii console-data 2:1.12-2 ii console-tools 1:0.2.3dbs-70 ii debconf [debconf-2.0] 1.5.43 ii debianutils4.3.1 ii lsb-base 4.1+Debian7 console-common recommends no packages. console-common suggests no packages. -- debconf information: console-data/keymap/powerpcadb: console-data/keymap/ignored: console-data/keymap/full: console-data/keymap/template/keymap: * console-data/keymap/policy: Don't touch keymap console-data/bootmap-md5sum: none console-data/keymap/template/layout: console-data/keymap/family: qwerty console-data/keymap/template/variant: signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: console-common Source-Version: 0.7.89 We believe that the bug you reported is fixed in the latest version of console-common, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated console-common package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 01:04:20 + Source: console-common Binary: console-common dh-consoledata Architecture: source all Version: 0.7.89 Distribution: sid Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: console-common - basic infrastructure for text console configuration dh-consoledata - debhelper-based script to help packaging console data files Closes: 276220 502897 516002 677314 723987 796606 Changes: console-common (0.7.89) unstable; urgency=medium . [Felipe Sateler] * Drop keymap.sh script, superseded in favor of console-setup Closes: #796606, #677314, #276220, #516002, #723987. . [Alastair McKinstry] * Move to Standards-Version: 3.9.6 * If 'machine' not in /proc/cpuinfo, use 'platform'. Closes: #502897. Checksums-Sha1: be1d25c0dea3f116ff247f34d8582411f46ed723 1624 console-common_0.7.89.dsc d3e78faaabc3f7e7ac4d13c3d07cb0ec45ce6e62 136164 console-common_0.7.89.tar.xz 633af24755cb50536e6dd0d032750428748f74a0 120254 console-common_0.7.89_all.deb 5790a0f99eb57dacc65f889dc93007ba2d110854 78698 dh-consoledata_0.7.89_all.deb Checksums-Sha256: 3469ed60dd6cd9265d60cb754af6549fdc83513334427efea87b13daaf481cd3 1624 console-common_0.7.89.dsc 6bd10c7e06c1fc3acb3325b54ee4c24fd5a9302eaa06ef1ea1d3d7038c612ba2 136164 console-common_0.7.89.tar.xz 1ae5cac10fbdefc88eadfcb807d03986ac4a6e48f68c689a300e9bf7282704cb 120254 console-common_0.7.89_all.deb 4e7e0ca89d751f10ff07ec6f530ffc02154d8b2ed4cdeeacb0f298501a2fb9b0 78698 dh-consoledata_0.7.89_all.deb Files: 5676236a258e6a09239adbb6ed479b84 1624 utils optional console-common_0.7.89.dsc d3363bc084037bd03f7062f0881e66a7 136164 utils optional console-common_0.7.89.tar.xz 589bb85f4cf5e4901bb38ad243a4d6ec 120254 utils optional console-common_0.7.89_all.deb 6e3b751604b04e1e
Bug#796606: marked as done (console-common: Has init script in runlevel S but no matching service file)
Your message dated Tue, 29 Dec 2015 15:37:20 + with message-id and subject line Bug#796606: fixed in console-common 0.7.89 has caused the Debian Bug report #796606, regarding console-common: Has init script in runlevel S but no matching service file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 796606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-common Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: init-rcs-service Hi, Your package console-common has an initscript that is enabled in runlevel S, but it does not provide a corresponding systemd service unit. Systemd generates units for all sysv init scripts that do not have a corresponding systemd unit. By default, it sets DefaultDependencies=yes, which means they get ordered after early boot has finished. The problem is that to preserve the runlevel S semantics, systemd in debian is currently[1] ordering all S services Before=sysinit.target. This target is particularly early in the boot sequence, which means that it is most of the time too strict. In turn, this means it is fairly easy to end up with dependency cycles. For an example, see bug [763315]. Do note that the cycle still exists with sysvinit, it is just that systemd complains more loudly. Please add a systemd unit for the given service with the appropriate dependencies, which most of the time will be less strict than Before=sysinit.target. In other cases, the script is simply not applicable in systemd, in which case the package should ship a symlink to /dev/null as /lib/systemd/system/.service. We have prepared a transition wiki page[2] explaining the issue in more detail, and outlining some general guidance. Please refer to it as it will have useful information. If you have any other doubts, feel free to ask in pkg-systemd-maintain...@lists.alioth.debian.org -- [1] http://sources.debian.net/src/systemd/222-2/debian/patches/Add-support-for-rcS.d-init-scripts-to-the-sysv-gener.patch/ [763315] https://bugs.debian.org/763315 [2] https://wiki.debian.org/Teams/pkg-systemd/rcSMigration --- End Message --- --- Begin Message --- Source: console-common Source-Version: 0.7.89 We believe that the bug you reported is fixed in the latest version of console-common, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 796...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated console-common package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 01:04:20 + Source: console-common Binary: console-common dh-consoledata Architecture: source all Version: 0.7.89 Distribution: sid Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: console-common - basic infrastructure for text console configuration dh-consoledata - debhelper-based script to help packaging console data files Closes: 276220 502897 516002 677314 723987 796606 Changes: console-common (0.7.89) unstable; urgency=medium . [Felipe Sateler] * Drop keymap.sh script, superseded in favor of console-setup Closes: #796606, #677314, #276220, #516002, #723987. . [Alastair McKinstry] * Move to Standards-Version: 3.9.6 * If 'machine' not in /proc/cpuinfo, use 'platform'. Closes: #502897. Checksums-Sha1: be1d25c0dea3f116ff247f34d8582411f46ed723 1624 console-common_0.7.89.dsc d3e78faaabc3f7e7ac4d13c3d07cb0ec45ce6e62 136164 console-common_0.7.89.tar.xz 633af24755cb50536e6dd0d032750428748f74a0 120254 console-common_0.7.89_all.deb 5790a0f99eb57dacc65f889dc93007ba2d110854 78698 dh-consoledata_0.7.89_all.deb Checksums-Sha256: 3469ed60dd6cd9265d60cb754af6549fdc83513334427efea87b13daaf481cd3 1624 console-common_0.7.89.dsc 6bd10c7e06c1fc3acb3325b54ee4c24fd5a9302eaa06ef1ea1d3d7038c612ba2 136164 console-common_0.7.89.tar.xz 1ae5cac10fbdefc88eadfcb807d03986ac4a6e48f68c689a300e9bf7282704cb 120254 console-common_0.7.89_all.deb 4e7e0ca89d751f10ff07ec6f530ffc02154d8b2ed4cdeeacb0f298
Bug#796606: marked as done (console-common: Has init script in runlevel S but no matching service file)
Your message dated Tue, 29 Dec 2015 15:37:20 + with message-id and subject line Bug#677314: fixed in console-common 0.7.89 has caused the Debian Bug report #677314, regarding console-common: Has init script in runlevel S but no matching service file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 677314: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677314 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-common Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: init-rcs-service Hi, Your package console-common has an initscript that is enabled in runlevel S, but it does not provide a corresponding systemd service unit. Systemd generates units for all sysv init scripts that do not have a corresponding systemd unit. By default, it sets DefaultDependencies=yes, which means they get ordered after early boot has finished. The problem is that to preserve the runlevel S semantics, systemd in debian is currently[1] ordering all S services Before=sysinit.target. This target is particularly early in the boot sequence, which means that it is most of the time too strict. In turn, this means it is fairly easy to end up with dependency cycles. For an example, see bug [763315]. Do note that the cycle still exists with sysvinit, it is just that systemd complains more loudly. Please add a systemd unit for the given service with the appropriate dependencies, which most of the time will be less strict than Before=sysinit.target. In other cases, the script is simply not applicable in systemd, in which case the package should ship a symlink to /dev/null as /lib/systemd/system/.service. We have prepared a transition wiki page[2] explaining the issue in more detail, and outlining some general guidance. Please refer to it as it will have useful information. If you have any other doubts, feel free to ask in pkg-systemd-maintain...@lists.alioth.debian.org -- [1] http://sources.debian.net/src/systemd/222-2/debian/patches/Add-support-for-rcS.d-init-scripts-to-the-sysv-gener.patch/ [763315] https://bugs.debian.org/763315 [2] https://wiki.debian.org/Teams/pkg-systemd/rcSMigration --- End Message --- --- Begin Message --- Source: console-common Source-Version: 0.7.89 We believe that the bug you reported is fixed in the latest version of console-common, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated console-common package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 01:04:20 + Source: console-common Binary: console-common dh-consoledata Architecture: source all Version: 0.7.89 Distribution: sid Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: console-common - basic infrastructure for text console configuration dh-consoledata - debhelper-based script to help packaging console data files Closes: 276220 502897 516002 677314 723987 796606 Changes: console-common (0.7.89) unstable; urgency=medium . [Felipe Sateler] * Drop keymap.sh script, superseded in favor of console-setup Closes: #796606, #677314, #276220, #516002, #723987. . [Alastair McKinstry] * Move to Standards-Version: 3.9.6 * If 'machine' not in /proc/cpuinfo, use 'platform'. Closes: #502897. Checksums-Sha1: be1d25c0dea3f116ff247f34d8582411f46ed723 1624 console-common_0.7.89.dsc d3e78faaabc3f7e7ac4d13c3d07cb0ec45ce6e62 136164 console-common_0.7.89.tar.xz 633af24755cb50536e6dd0d032750428748f74a0 120254 console-common_0.7.89_all.deb 5790a0f99eb57dacc65f889dc93007ba2d110854 78698 dh-consoledata_0.7.89_all.deb Checksums-Sha256: 3469ed60dd6cd9265d60cb754af6549fdc83513334427efea87b13daaf481cd3 1624 console-common_0.7.89.dsc 6bd10c7e06c1fc3acb3325b54ee4c24fd5a9302eaa06ef1ea1d3d7038c612ba2 136164 console-common_0.7.89.tar.xz 1ae5cac10fbdefc88eadfcb807d03986ac4a6e48f68c689a300e9bf7282704cb 120254 console-common_0.7.89_all.deb 4e7e0ca89d751f10ff07ec6f530ffc02154d8b2ed4cdeeacb0f298
Bug#806354: marked as done (django-polymorphic: FTBFS with Django 1.9)
Your message dated Tue, 29 Dec 2015 15:37:29 + with message-id and subject line Bug#806354: fixed in django-polymorphic 0.8.1-1 has caused the Debian Bug report #806354, regarding django-polymorphic: FTBFS with Django 1.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 806354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: django-polymorphic Version: 0.7.2-1 Severity: important User: python-dja...@packages.debian.org Usertags: django19 django19-ftbfs Hi, Whilst rebuilding all reverse build-dependencies of python-django with the latest release candidate, I noticed that django-polymorphic FTBFS with 1.9~rc2. Please update your package to work with Django 1.9 as I will uploading it to unstable once it is released in early December 2015 (and at the same time raising the severity of this bug to RC). Typical issues include: * "django.utils.importlib" has been removed in favour of just "importlib" * Template builtins have been removed, removing "template.base.builtins", "django.template.base.add_to_builtins", etc. You can read more here: https://chris-lamb.co.uk/posts/importerror-cannot-import-name-add_to_builtins-under-django-19 * "django.forms.models.save_instance" has been removed: - https://github.com/django/django/commit/8656cfc4e01332426e5e4b78c20a4e9ec443b293 - https://github.com/django/django/commit/b11564fd36587b1077bf7d77b62b7879cc08c382 * "django.utils.unittest" has been removed in favour of just "unittest" The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- django-polymorphic_0.7.2-1_amd64.build.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Source: django-polymorphic Source-Version: 0.8.1-1 We believe that the bug you reported is fixed in the latest version of django-polymorphic, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 806...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Fladischer (supplier of updated django-polymorphic package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Dec 2015 16:16:34 +0100 Source: django-polymorphic Binary: python-django-polymorphic python3-django-polymorphic python-django-polymorphic-doc Architecture: source all Version: 0.8.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Michael Fladischer Description: python-django-polymorphic - Seamless Polymorphic Inheritance for Django Models python-django-polymorphic-doc - Seamless Polymorphic Inheritance for Django Models (Documentation python3-django-polymorphic - Seamless Polymorphic Inheritance for Django Models (Python3 versi Closes: 806354 Changes: django-polymorphic (0.8.1-1) unstable; urgency=medium . * New upstream release (Closes: #806354). * Add NEWS file to document backwards incompatible changes. Checksums-Sha1: 68c6940023d9d93aea54aa444ef1f2628736b0ba 2390 django-polymorphic_0.8.1-1.dsc 7922ca7f9fd895e283a1518b06d4511c757f8b79 64375 django-polymorphic_0.8.1.orig.tar.gz d7cbabb843e852d1a310cce7fb9f24c0be505a45 3632 django-polymorphic_0.8.1-1.debian.tar.xz 6aa075b5fa840407b34c3904b06aae502cc37cc5 51524 python-django-polymorphic-doc_0.8.1-1_all.deb 4365282cdbef59a16a6e4904774014e3621a9015 36402 python-django-polymorphic_0.8.1-1_all.deb ec3dba86462f8e13e3225de8e4af9d9e91df8b8b 36310 python3-django-polymorphic_0.8.1-1_all.deb Checksums-Sha256: 864107707c139ae638eeafd6b80d10dbba5714b001d5afdd110c2d2ea4c3dafd 2390 django-polymorphic_0.8.1-1.dsc b3899668f6fe0e7c3921a3c2d1fb03121f9ffb702fb63de14d7ac863c9c54569 64375 django-polymorphic_0.8.1.orig.tar.gz d03ce24b0d80b51f2cb0fee3bdeb1168e4105a44162bf5fe20d2974a0da75716 3632 django-polymorphic_0.8.1-1.debian.tar.xz 9cd7a96717c2043cf8df610d79f3c989ba0059b8624e2f92855d62b9f8a9b984 51524 python-django-polymorphic-doc_0.8.1-1_all.
Bug#502897: marked as done (console-data: Debconf module aborted (No "machine" field in /proc/cpuinfo))
Your message dated Tue, 29 Dec 2015 15:37:20 + with message-id and subject line Bug#502897: fixed in console-common 0.7.89 has caused the Debian Bug report #502897, regarding console-data: Debconf module aborted (No "machine" field in /proc/cpuinfo) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 502897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502897 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-data Version: 2:1.07-11 Severity: normal Setting up console-data (2:1.07-11) ... Debconf module aborted (No "machine" field in /proc/cpuinfo) - using old config mechanism. note this is a ps3, so these are the contents of /proc/cpuinfo in case it helps: processor : 0 cpu : Cell Broadband Engine, altivec supported clock : 3192.00MHz revision: 16.0 (pvr 0070 1000) processor : 1 cpu : Cell Broadband Engine, altivec supported clock : 3192.00MHz revision: 16.0 (pvr 0070 1000) timebase: 7980 platform: PS3 model : SonyPS3 BR sean -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: powerpc (ppc64) Kernel: Linux 2.6.26-1-powerpc64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages console-data depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy Versions of packages console-data recommends: ii console-common 0.7.80 basic infrastructure for text cons ii console-tools1:0.2.3dbs-65.1 Linux console and font utilities Versions of packages console-data suggests: pn unicode-data (no description available) -- debconf information: console-keymaps-dec/keymap: console-data/keymap/template/layout: console-data/keymap/family: qwerty console-keymaps-amiga/keymap: console-keymaps-at/keymap: console-data/keymap/full: console-keymaps-atari/keymap: console-keymaps-usb/keymap: console-keymaps-acorn/keymap: console-keymaps-mac/keymap: console-data/keymap/template/keymap: console-data/keymap/powerpcadb: * console-data/keymap/policy: Don't touch keymap console-keymaps-sun/keymap: console-data/keymap/template/variant: console-data/bootmap-md5sum: none console-data/keymap/ignored: --- End Message --- --- Begin Message --- Source: console-common Source-Version: 0.7.89 We believe that the bug you reported is fixed in the latest version of console-common, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 502...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated console-common package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 01:04:20 + Source: console-common Binary: console-common dh-consoledata Architecture: source all Version: 0.7.89 Distribution: sid Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: console-common - basic infrastructure for text console configuration dh-consoledata - debhelper-based script to help packaging console data files Closes: 276220 502897 516002 677314 723987 796606 Changes: console-common (0.7.89) unstable; urgency=medium . [Felipe Sateler] * Drop keymap.sh script, superseded in favor of console-setup Closes: #796606, #677314, #276220, #516002, #723987. . [Alastair McKinstry] * Move to Standards-Version: 3.9.6 * If 'machine' not in /proc/cpuinfo, use 'platform'. Closes: #502897. Checksums-Sha1: be1d25c0dea3f116ff247f34d8582411f46ed723 1624 console-common_0.7.89.dsc d3e78faaabc3f7e7ac4d13c3d07cb0ec45ce6e62 136164 console-common_0.7.89.tar.xz 633af24755cb50536e6dd0d032750428748f74a0 120254 console-common_0.7.89_all.deb 5790a0f99eb57dacc65f889dc93007ba2d110854 78698 dh-consoledata_0.7.89_all.deb Checksums-Sha256: 3469ed60dd6cd9265d60cb754af6549
Bug#677314: marked as done (console-common: Please ship systemd service file)
Your message dated Tue, 29 Dec 2015 15:37:20 + with message-id and subject line Bug#796606: fixed in console-common 0.7.89 has caused the Debian Bug report #796606, regarding console-common: Please ship systemd service file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 796606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: console-data Version: 0.7.87 Severity: wishlist User: syst...@packages.debian.org Usertags: console-common Dear Debian folks, it would be great if you could enable systemd support for console-common by packaging a service file [1] which could be loaded instead of `/etc/init.d/keymap.sh`. Thank you very much, Paul -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages console-common depends on: ii console-data 2:1.12-2 ii console-tools 1:0.2.3dbs-70 ii debconf [debconf-2.0] 1.5.43 ii debianutils4.3.1 ii lsb-base 4.1+Debian7 console-common recommends no packages. console-common suggests no packages. -- debconf information: console-data/keymap/powerpcadb: console-data/keymap/ignored: console-data/keymap/full: console-data/keymap/template/keymap: * console-data/keymap/policy: Don't touch keymap console-data/bootmap-md5sum: none console-data/keymap/template/layout: console-data/keymap/family: qwerty console-data/keymap/template/variant: signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: console-common Source-Version: 0.7.89 We believe that the bug you reported is fixed in the latest version of console-common, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 796...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated console-common package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 01:04:20 + Source: console-common Binary: console-common dh-consoledata Architecture: source all Version: 0.7.89 Distribution: sid Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: console-common - basic infrastructure for text console configuration dh-consoledata - debhelper-based script to help packaging console data files Closes: 276220 502897 516002 677314 723987 796606 Changes: console-common (0.7.89) unstable; urgency=medium . [Felipe Sateler] * Drop keymap.sh script, superseded in favor of console-setup Closes: #796606, #677314, #276220, #516002, #723987. . [Alastair McKinstry] * Move to Standards-Version: 3.9.6 * If 'machine' not in /proc/cpuinfo, use 'platform'. Closes: #502897. Checksums-Sha1: be1d25c0dea3f116ff247f34d8582411f46ed723 1624 console-common_0.7.89.dsc d3e78faaabc3f7e7ac4d13c3d07cb0ec45ce6e62 136164 console-common_0.7.89.tar.xz 633af24755cb50536e6dd0d032750428748f74a0 120254 console-common_0.7.89_all.deb 5790a0f99eb57dacc65f889dc93007ba2d110854 78698 dh-consoledata_0.7.89_all.deb Checksums-Sha256: 3469ed60dd6cd9265d60cb754af6549fdc83513334427efea87b13daaf481cd3 1624 console-common_0.7.89.dsc 6bd10c7e06c1fc3acb3325b54ee4c24fd5a9302eaa06ef1ea1d3d7038c612ba2 136164 console-common_0.7.89.tar.xz 1ae5cac10fbdefc88eadfcb807d03986ac4a6e48f68c689a300e9bf7282704cb 120254 console-common_0.7.89_all.deb 4e7e0ca89d751f10ff07ec6f530ffc02154d8b2ed4cdeeacb0f298501a2fb9b0 78698 dh-consoledata_0.7.89_all.deb Files: 5676236a258e6a09239adbb6ed479b84 1624 utils optional console-common_0.7.89.dsc d3363bc084037bd03f7062f0881e66a7 136164 utils optional console-common_0.7.89.tar.xz 589bb85f4cf5e4901bb38ad243a4d6ec 120254 utils optional console-common_0.7.89_all.deb 6e3b751604b04e1e
Bug#808465: marked as done (unicode-data: sort error in NameAliases.txt)
Your message dated Tue, 29 Dec 2015 15:49:14 + with message-id and subject line Bug#808465: fixed in unicode-data 8.0-3 has caused the Debian Bug report #808465, regarding unicode-data: sort error in NameAliases.txt to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 808465: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808465 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: unicode-data Version: 8.0-2 Severity: minor Tags: patch upstream Hello. Code points in /usr/share/unicode/NameAliases.txt are not sorted. This makes the file much harder to use efficiently. Because - moving only one code sorts the file - the header says that the file is intended to be parsed I bet that this is not intentional. A trivial patch is attached. --- /usr/share/unicode/NameAliases.txt 2015-10-12 16:39:44.0 +0200 +++ NameAliases.txt 2015-12-20 12:16:42.298438420 +0100 @@ -287,7 +287,6 @@ 2B7A;LEFTWARDS TRIANGLE-HEADED ARROW WITH DOUBLE VERTICAL STROKE;correction 2B7C;RIGHTWARDS TRIANGLE-HEADED ARROW WITH DOUBLE VERTICAL STROKE;correction A015;YI SYLLABLE ITERATION MARK;correction -FE18;PRESENTATION FORM FOR VERTICAL RIGHT WHITE LENTICULAR BRACKET;correction FE00;VS1;abbreviation FE01;VS2;abbreviation FE02;VS3;abbreviation @@ -304,6 +303,7 @@ FE0D;VS14;abbreviation FE0E;VS15;abbreviation FE0F;VS16;abbreviation +FE18;PRESENTATION FORM FOR VERTICAL RIGHT WHITE LENTICULAR BRACKET;correction FEFF;BYTE ORDER MARK;alternate FEFF;BOM;abbreviation FEFF;ZWNBSP;abbreviation --- End Message --- --- Begin Message --- Source: unicode-data Source-Version: 8.0-3 We believe that the bug you reported is fixed in the latest version of unicode-data, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 808...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated unicode-data package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 02:15:32 + Source: unicode-data Binary: unicode-data Architecture: source all Version: 8.0-3 Distribution: sid Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: unicode-data - Property data for the Unicode character set Closes: 808465 809188 Changes: unicode-data (8.0-3) unstable; urgency=medium . * Fetch new allkeys.txt for Unicode 8. Closes: #809188. * Move to S-V: 3.9.6. No changes required. * Fix sort error in NameAliases.txt. Closes: #808465. Checksums-Sha1: 935f8db4477bfa6a69ab7575516c4226075eb0c6 1757 unicode-data_8.0-3.dsc bf08a21b15a4141ae48f19910c16a7b8ec1d44fc 225872 unicode-data_8.0-3.debian.tar.xz f5a142a97804598002de393d0603eee9dfa960cf 6987020 unicode-data_8.0-3_all.deb Checksums-Sha256: 7c08603afe3d692b44fd507bf8aae3501937f28979f534dd691e0253468b3b0f 1757 unicode-data_8.0-3.dsc bc70cc5b9d1a5b8bab429638b69143115ef0fe959c3002f3a6dc1365e1fb21c4 225872 unicode-data_8.0-3.debian.tar.xz a7b8bdc0cd8a2b7ecda6dd0c6443dd9fe293b05288b69025b4da2be78b00e96a 6987020 unicode-data_8.0-3_all.deb Files: 9d24f7f65d58bb2e5e87e0752181880c 1757 misc optional unicode-data_8.0-3.dsc cacc07a71fe4572248251eb21d57b943 225872 misc optional unicode-data_8.0-3.debian.tar.xz 8e417625e0dad931181b387f23f37c3d 6987020 misc optional unicode-data_8.0-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWge6UAAoJEMvmu05dmtOlB7IP/jFjI8AaV40prcajpjpi2bFF DCBfW7dv/HkuDGZM5/blEvAHLraKpMX/OeqdJwVSOO7feNNJiWUbIJC43WJfyQl8 DvVVnQkHFqx8cA18g3e1Lg5iBQ25wDMV0uAiQriwo69djXky4x/M6/USvc8eoND3 tPdk61IHw8/UpNRt0PL4yT2iyvbWUoCEMwl5wXDlN/ysnt+kU08IeqeK82TMPldb c2I7ufXuHJ4sfdV0jogj3XHTGpkTv4lB4scrn2BeKvazbj/BrI5mjgJeTACh8Uoa P8aNleNZ/aYAV9GyAbt93ZkZJwXoFNifamTDePx+AV6sR/xpqf/jgc8X3KbC6k81 pBnqKnFm5e/Qx48lKJ/EpuHxzFvx0c5TmvrvmaESfNLmID37rDgcc4hLazSgJxrl dmwCapjrFzQSvux/wOVQGSRh4bhrQpX/XItRJuVmvBLDuTp1vlcUKIaNZ2XKZa0i fDxhaKW+g0suuwuBom0ELjFg0zrDfyOgQ+i39SnwWtBarpXewl5eXTnBW9wT1tHi CsNuL7ThiAFGI/hDYP89aNn6rXP8y+44KlWT5pW1VZSQ1mXU3b1yj1t0qtvOjatl Bk7dniJK0en4qyvWqtlsZst6PbcqxNcKffYqLCw4+LvKq6f5M1OA1UX660C93oNS xBNdI3jV8g1eh2k6TOGg =axf5 -END PGP SIGNATURE End Message ---
Bug#809188: marked as done (unicode-data: allkeys.txt is from unicode 7.0)
Your message dated Tue, 29 Dec 2015 15:49:14 + with message-id and subject line Bug#809188: fixed in unicode-data 8.0-3 has caused the Debian Bug report #809188, regarding unicode-data: allkeys.txt is from unicode 7.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: src:unicode-data version: 8.0-2 The version of allkeys.txt included is version 7.0.0 in the unicode-data 8.0 package, not the expected version 8.0.0. Best wishes, Mike --- End Message --- --- Begin Message --- Source: unicode-data Source-Version: 8.0-3 We believe that the bug you reported is fixed in the latest version of unicode-data, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Alastair McKinstry (supplier of updated unicode-data package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 02:15:32 + Source: unicode-data Binary: unicode-data Architecture: source all Version: 8.0-3 Distribution: sid Urgency: medium Maintainer: Alastair McKinstry Changed-By: Alastair McKinstry Description: unicode-data - Property data for the Unicode character set Closes: 808465 809188 Changes: unicode-data (8.0-3) unstable; urgency=medium . * Fetch new allkeys.txt for Unicode 8. Closes: #809188. * Move to S-V: 3.9.6. No changes required. * Fix sort error in NameAliases.txt. Closes: #808465. Checksums-Sha1: 935f8db4477bfa6a69ab7575516c4226075eb0c6 1757 unicode-data_8.0-3.dsc bf08a21b15a4141ae48f19910c16a7b8ec1d44fc 225872 unicode-data_8.0-3.debian.tar.xz f5a142a97804598002de393d0603eee9dfa960cf 6987020 unicode-data_8.0-3_all.deb Checksums-Sha256: 7c08603afe3d692b44fd507bf8aae3501937f28979f534dd691e0253468b3b0f 1757 unicode-data_8.0-3.dsc bc70cc5b9d1a5b8bab429638b69143115ef0fe959c3002f3a6dc1365e1fb21c4 225872 unicode-data_8.0-3.debian.tar.xz a7b8bdc0cd8a2b7ecda6dd0c6443dd9fe293b05288b69025b4da2be78b00e96a 6987020 unicode-data_8.0-3_all.deb Files: 9d24f7f65d58bb2e5e87e0752181880c 1757 misc optional unicode-data_8.0-3.dsc cacc07a71fe4572248251eb21d57b943 225872 misc optional unicode-data_8.0-3.debian.tar.xz 8e417625e0dad931181b387f23f37c3d 6987020 misc optional unicode-data_8.0-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWge6UAAoJEMvmu05dmtOlB7IP/jFjI8AaV40prcajpjpi2bFF DCBfW7dv/HkuDGZM5/blEvAHLraKpMX/OeqdJwVSOO7feNNJiWUbIJC43WJfyQl8 DvVVnQkHFqx8cA18g3e1Lg5iBQ25wDMV0uAiQriwo69djXky4x/M6/USvc8eoND3 tPdk61IHw8/UpNRt0PL4yT2iyvbWUoCEMwl5wXDlN/ysnt+kU08IeqeK82TMPldb c2I7ufXuHJ4sfdV0jogj3XHTGpkTv4lB4scrn2BeKvazbj/BrI5mjgJeTACh8Uoa P8aNleNZ/aYAV9GyAbt93ZkZJwXoFNifamTDePx+AV6sR/xpqf/jgc8X3KbC6k81 pBnqKnFm5e/Qx48lKJ/EpuHxzFvx0c5TmvrvmaESfNLmID37rDgcc4hLazSgJxrl dmwCapjrFzQSvux/wOVQGSRh4bhrQpX/XItRJuVmvBLDuTp1vlcUKIaNZ2XKZa0i fDxhaKW+g0suuwuBom0ELjFg0zrDfyOgQ+i39SnwWtBarpXewl5eXTnBW9wT1tHi CsNuL7ThiAFGI/hDYP89aNn6rXP8y+44KlWT5pW1VZSQ1mXU3b1yj1t0qtvOjatl Bk7dniJK0en4qyvWqtlsZst6PbcqxNcKffYqLCw4+LvKq6f5M1OA1UX660C93oNS xBNdI3jV8g1eh2k6TOGg =axf5 -END PGP SIGNATURE End Message ---
Bug#806353: marked as done (django-picklefield: FTBFS with Django 1.9)
Your message dated Tue, 29 Dec 2015 17:33:36 +0100 with message-id <20151229163336.ga29...@home.ouaza.com> and subject line Re: Processed (with 1 error): reassign 806353 to src:python-django, merging 806353 807683 has caused the Debian Bug report #806353, regarding django-picklefield: FTBFS with Django 1.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 806353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: django-picklefield Version: 0.3.1-2 Severity: important User: python-dja...@packages.debian.org Usertags: django19 django19-ftbfs Hi, Whilst rebuilding all reverse build-dependencies of python-django with the latest release candidate, I noticed that django-picklefield FTBFS with 1.9~rc2. Please update your package to work with Django 1.9 as I will uploading it to unstable once it is released in early December 2015 (and at the same time raising the severity of this bug to RC). Typical issues include: * "django.utils.importlib" has been removed in favour of just "importlib" * Template builtins have been removed, removing "template.base.builtins", "django.template.base.add_to_builtins", etc. You can read more here: https://chris-lamb.co.uk/posts/importerror-cannot-import-name-add_to_builtins-under-django-19 * "django.forms.models.save_instance" has been removed: - https://github.com/django/django/commit/8656cfc4e01332426e5e4b78c20a4e9ec443b293 - https://github.com/django/django/commit/b11564fd36587b1077bf7d77b62b7879cc08c382 * "django.utils.unittest" has been removed in favour of just "unittest" The full build log is attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- django-picklefield_0.3.1-2_amd64.build.txt.gz Description: Binary data --- End Message --- --- Begin Message --- Version: 1.9-1 It was a bit pointless to reassign this bug when it was already fixed... you should have just closed it. Cheers, On Sun, 27 Dec 2015, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > reassign 806353 src:python-django 1.9-1 > Bug #806353 [src:django-picklefield] django-picklefield: FTBFS with Django 1.9 > Bug reassigned from package 'src:django-picklefield' to 'src:python-django'. > No longer marked as found in versions django-picklefield/0.3.1-2. > Ignoring request to alter fixed versions of bug #806353 to the same values > previously set > Bug #806353 [src:python-django] django-picklefield: FTBFS with Django 1.9 > Marked as found in versions python-django/1.9-1. > > merge 806353 807683 > Bug #806353 [src:python-django] django-picklefield: FTBFS with Django 1.9 > Unable to merge bugs because: > severity of #807683 is 'important' not 'serious' > package of #807683 is 'python-django' not 'src:python-django' > Failed to merge 806353: Did not alter merged bugs. > > > thanks > Stopping processing here. > > Please contact me if you need assistance. > -- > 806353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806353 > 807683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807683 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/--- End Message ---
Bug#690798: marked as done (iceweasel16 breaks xul-ext-tabmixplus)
Your message dated Tue, 29 Dec 2015 17:56:14 +0100
with message-id <1451408174.13713.12.ca...@scientia.net>
and subject line Re: iceweasel16 breaks xul-ext-tabmixplus
has caused the Debian Bug report #690798,
regarding iceweasel16 breaks xul-ext-tabmixplus
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
690798: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iceweasel
Version: 16.0.1-1
Severity: normal
Tags: upstream
Hi.
Iceweasel 16.0.1 packages break xul-ext-tabmixplus 0.4.0.2, or vice versa.
I already reported the symtoms upstream.
Please, add a Break :)
Cheers,
Chris.
-- Package-specific info:
-- Extensions information
Name: Adblock Plus
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
Package: xul-ext-adblock-plus
Status: enabled
Name: Certificate Patrol
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/certpat...@psyc.eu
Package: xul-ext-certificatepatrol
Status: enabled
Name: Cookie Monster
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{45d8ff86-d909-11db-9705-005056c8}
Package: xul-ext-cookie-monster
Status: enabled
Name: Default theme
Location: /usr/lib/iceweasel/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled
Name: Download Statusbar
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{D4DD63FA-01E4-46a7-B6B1-EDAB7D6AD389}
Package: xul-ext-downloadstatusbar
Status: enabled
Name: DownThemAll!
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{DDC359D1-844A-42a7-9AA1-88A850A938A8}
Package: xul-ext-downthemall
Status: enabled
Name: Firebug
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/fire...@software.joehewitt.com
Package: xul-ext-firebug
Status: enabled
Name: FirePath
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/firexp...@pierre.tholence.com
Package: xul-ext-firexpath
Status: enabled
Name: Flashblock
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{3d7eb24f-2740-49df-8937-200b1cc08f8a}
Package: xul-ext-flashblock
Status: enabled
Name: HTTPS-Everywhere
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/https-everywh...@eff.org
Package: xul-ext-https-everywhere
Status: enabled
Name: Live HTTP headers
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{8f8fe09b-0bd3-4470-bc1b-8cad42b8203a}
Package: xul-ext-livehttpheaders
Status: enabled
Name: NoScript
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{73a6fe31-595d-460b-a920-fcc0f8843232}
Package: xul-ext-noscript
Status: enabled
Name: SearchLoad Options
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/searchloadoptions@esteban.torres
Package: xul-ext-searchload-options
Status: enabled
Name: Status-4-Evar
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/status4e...@caligonstudios.com
Package: xul-ext-status4evar
Status: enabled
Name: Tab Mix Plus
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{dc572301-7619-498c-a57d-39143191b318}
Package: xul-ext-tabmixplus
Status: user-disabled
Name: Torbutton
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{e0204bd5-9d31-402b-a99d-a6aa8ffebdca}
Package: xul-ext-torbutton
Status: enabled
Name: User Agent Switcher
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{e968fc70-8f95-4ab9-9e79-304de2a71ee1}
Package: xul-ext-useragentswitcher
Status: enabled
Name: Web Developer
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{c45c406e-ab73-11d8-be73-000a95be3b12}
Package: xul-ext-webdeveloper
Status: enabled
-- Plugins information
Name: DivX® Web Player
Location: /usr/lib/mozilla/plugins/libtotem-mully-plugin.so
Package: totem-mozilla
Status: enabled
Name: Gnome Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Status: disabled
Name: IcedTea-Web Plugin (using IcedTea-Web 1.3 (1.3-1))
Location: /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
Package: icedtea-7-plugin:amd64
Status: disabled
Name: QuickTime Plug-in 7.6.6
Location: /usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so
Package: totem-mozilla
Status: enabled
Bug#747834: marked as done (iceweasel: switching between tabs does no longer work with ctrl+page up/down)
Your message dated Tue, 29 Dec 2015 18:06:24 +0100
with message-id <1451408784.13713.14.ca...@scientia.net>
and subject line Re: iceweasel: switching between tabs does no longer work with
ctrl+page up/down
has caused the Debian Bug report #747834,
regarding iceweasel: switching between tabs does no longer work with ctrl+page
up/down
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
747834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iceweasel
Version: 29.0.1-1
Severity: important
As the title says... well but this is just one of the dozens of things
that seems to be broken in the 29 version of iceweasel...
Cheers,
Chris.
-- Package-specific info:
-- Extensions information
Name: Adblock Plus
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
Package: xul-ext-adblock-plus
Status: enabled
Name: Certificate Patrol
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/certpat...@psyc.eu
Package: xul-ext-certificatepatrol
Status: enabled
Name: Cookie Monster
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{45d8ff86-d909-11db-9705-005056c8}
Package: xul-ext-cookie-monster
Status: enabled
Name: Default theme
Location:
/usr/lib/iceweasel/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled
Name: DownThemAll!
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{DDC359D1-844A-42a7-9AA1-88A850A938A8}
Package: xul-ext-downthemall
Status: enabled
Name: Firebug
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/fire...@software.joehewitt.com
Package: xul-ext-firebug
Status: user-disabled
Name: FirePath
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/firexp...@pierre.tholence.com
Package: xul-ext-firexpath
Status: enabled
Name: Flashblock
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{3d7eb24f-2740-49df-8937-200b1cc08f8a}
Package: xul-ext-flashblock
Status: enabled
Name: GNOME Keyring integration
Location:
/usr/lib/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{6f9d85e0-794d-11dd-ad8b-0800200c9a66}
Package: xul-ext-gnome-keyring
Status: app-disabled
Name: HTTPS-Everywhere
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/https-everywh...@eff.org
Package: xul-ext-https-everywhere
Status: enabled
Name: Live HTTP headers
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{8f8fe09b-0bd3-4470-bc1b-8cad42b8203a}
Package: xul-ext-livehttpheaders
Status: enabled
Name: NoScript
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{73a6fe31-595d-460b-a920-fcc0f8843232}
Package: xul-ext-noscript
Status: enabled
Name: SearchLoad Options
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/searchloadoptions@esteban.torres
Package: xul-ext-searchload-options
Status: enabled
Name: Status-4-Evar
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/status4e...@caligonstudios.com
Package: xul-ext-status4evar
Status: enabled
Name: Tab Mix Plus
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{dc572301-7619-498c-a57d-39143191b318}
Package: xul-ext-tabmixplus
Status: enabled
Name: User Agent Switcher
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{e968fc70-8f95-4ab9-9e79-304de2a71ee1}
Package: xul-ext-useragentswitcher
Status: enabled
Name: Web Developer
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{c45c406e-ab73-11d8-be73-000a95be3b12}
Package: xul-ext-webdeveloper
Status: enabled
Name: Y U no validate
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{20d36f97-15da-47ed-9f0a-13cbe85bdc84}
Package: xul-ext-y-u-no-validate
Status: enabled
-- Plugins information
Name: Cinnamon Integration
Location: /usr/lib/mozilla/plugins/libcinnamon-browser-plugin.so
Package: cinnamon
Status: disabled
Name: DivX Browser Plug-In
Location: /usr/lib/mozilla/plugins/gecko-mediaplayer-dvx.so
Package: gecko-mediaplayer
Status: enabled
Name: DivX® Web Player
Location: /usr/lib/mozilla/plugins/libtotem-mully-plugin.so
Package: totem-mozilla
Status: disabled
Name: Gnome Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Bug#775645: marked as done (iceweasel: new default of dom.indexeddb.enabled=false in FF35 breaks several core functionalities and add-ons)
Your message dated Tue, 29 Dec 2015 18:09:30 +0100
with message-id <1451408970.13713.15.ca...@scientia.net>
and subject line Re: iceweasel: new default of dom.indexeddb.enabled=false in
FF35 breaks several core functionalities and add-ons
has caused the Debian Bug report #775645,
regarding iceweasel: new default of dom.indexeddb.enabled=false in FF35 breaks
several core functionalities and add-ons
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
775645: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iceweasel
Version: 35.0-1
Severity: important
Hi.
Since I've upgraded to 35, I've experienced multiple issues.
- One of them is the breakage of search load options, which I've
already reported in #775391.
- Another was that the search bar didn't work anymore at all
(i.e. hitting enter and nothing happened at all).
This turned out to be a problem in tab mix plus, which was solved
by the version 0.4.1.6 already in experimental.
But several problems remained, which I first suspected to be tab
mix plus either:
- Undo closing tabs (Ctrl-Shift-t) no longer worked.
- session management (at least with the SM from TM+) didn't work
anymore, neither on restart after crash, nor on loading manually
saved sessions.
I've reported these upstream at:
http://tmp.garyr.net/forum/viewtopic.php?f=2&t=19018
I further found out that add block plus stopped working, which
meant:
- adds were shown
- I cannot longer open the preferences of the add on (nothing
happens when I click on the button).
- And everything from add on's page in the add on manager is
displayed broken,... it doesn't display the underscore on the
objects, but "&" before (see the screenshot for what I mean).
So I came to the suspicion it may not be TM+ and digged deeper:
With a fresh profile everything seems to work fine again,
but it would be really annoying having to start from scratch,
since I have so many settings in FF and all plugins.
Starting FF with an empty .mozilla gives:
$ iceweasel
(process:12321): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size
== 0' failed
1421544782793 addons.xpi WARNException running bootstrap method
startup on fire...@software.joehewitt.com: TypeError: scope.gcli.addCommand is
not a function (resource://firebug/gcli.js:126:4) JS Stack trace:
addcomm...@gcli.js:126:5 < registercomma...@gcli.js:132:1 <
firebuggclicommands.star...@gcli.js:45:9 <
startup@resource://gre/modules/addons/XPIProvider.jsm ->
file:///usr/share/mozilla/extensions/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/fire...@bootstrap.js:78:5
< xpi_callbootstrapmet...@xpiprovider.jsm:4436:9 <
xpi_star...@xpiprovider.jsm:2159:13 < callprovi...@addonmanager.jsm:208:12 <
_startprovi...@addonmanager.jsm:667:5 < ami_star...@addonmanager.jsm:821:9 <
amp_star...@addonmanager.jsm:2399:5 < amc_obse...@addonmanager.js:55:7
0 migrated.
console.error:
[CustomizableUI]
TypeError: window.caligon.status4evar is undefined --
resource://status4evar/Australis.jsm:166
=> everything seems to work again, even Search Load Options, which is why
I'll close that bug shortly after.
Starting FF with my profile (i.e. the one where I get all these
errors shows):
$ iceweasel
(process:10162): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size
== 0' failed
1421543699278 addons.xpi ERROR Failed to load bootstrap addon
searchloadoptions@esteban.torres from
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/searchloadoptions@esteban.torres:
[Exception... "Unexpected error in XPConnect" nsresult: "0x80570008
(NS_ERROR_XPC_UNEXPECTED)" location: "JS frame ::
resource://gre/modules/addons/XPIProvider.jsm :: XPI_loadBootstrapScope :: line
4307" data: no] Stack trace:
XPI_loadBootstrapScope()@resource://gre/modules/addons/XPIProvider.jsm:4307 <
XPI_callBootstrapMethod()@resource://gre/modules/addons/XPIProvider.jsm:4408 <
XPI_startup()@resource://gre/modules/addons/XPIProvider.jsm:2159 <
callProvider()@resource://gre/modules/AddonManager.jsm:208 <
_startProvider()@resource://gre/modules/AddonManager.jsm:667 <
AMI_startup()@resource://gre/modules/AddonManager.jsm:821 <
AMP_startup()@resource://gre/modules/AddonManager.jsm:2399 <
AMC_observe()@resource://gre/components/addonManager.js:55 <
1421543699280 addons.xpi ERROR Fail
Bug#809213: marked as done (tracker.debian.org: reveal documentation)
Your message dated Tue, 29 Dec 2015 18:16:21 +0100 with message-id <20151229171621.gc17...@home.ouaza.com> and subject line Re: Bug#809213: tracker.debian.org: reveal documentation has caused the Debian Bug report #809213, regarding tracker.debian.org: reveal documentation to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tracker.debian.org Severity: normal Currently most of the documentation is hidden: we have a link to the contributing section, but once there there is little hint about the other chapters (the left column is only a subset of the documentation and one need to click on "table of contents" to access it fully) I would replace the "How to contribute" link target with: https://tracker.debian.org/docs/index.html Note for some reason I do not remember the content of the HTML footer is customised on the server. Cheers, Christophe --- End Message --- --- Begin Message --- Hi, On Mon, 28 Dec 2015, Christophe Siraut wrote: > Currently most of the documentation is hidden: we have a link to the > contributing section, but once there there is little hint about the > other chapters (the left column is only a subset of the documentation > and one need to click on "table of contents" to access it fully) > > I would replace the "How to contribute" link target with: > > https://tracker.debian.org/docs/index.html > > Note for some reason I do not remember the content of the HTML footer is > customised on the server. Updated /srv/tracker.debian.org/data/templates/core/footer.html to include a direct link to the documentation but kept the "How to contribute" link. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/--- End Message ---
Bug#803075: marked as done (please symlink mrconvert into /usr/bin)
Your message dated Tue, 29 Dec 2015 17:34:39 + with message-id and subject line Bug#803075: fixed in mrtrix 0.2.12-2 has caused the Debian Bug report #803075, regarding please symlink mrconvert into /usr/bin to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 803075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mrtrix Version: 0.2.12-1+b2 Severity: normal I see no reason why mrconvert shouldn't be available from under /usr/bin whenever mrview already is. may be even all the ones with mr prefix could be (I didn't check for possible collisions within debian packages content besides mrconvert which wouldn't collide) $> dpkg -L mrtrix | grep bin/mr /usr/lib/mrtrix/bin/mrabs /usr/lib/mrtrix/bin/mradd /usr/lib/mrtrix/bin/mrcat /usr/lib/mrtrix/bin/mrconvert /usr/lib/mrtrix/bin/mrinfo /usr/lib/mrtrix/bin/mrmult /usr/lib/mrtrix/bin/mrstats /usr/lib/mrtrix/bin/mrtransform /usr/lib/mrtrix/bin/mrview -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mrtrix depends on: ii libatk1.0-0 2.18.0-1 ii libatkmm-1.6-1v5 2.24.1-1 ii libc6 2.19-22 ii libcairo2 1.14.2-2 ii libcairomm-1.0-1v51.12.0-1 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.6-2 ii libgcc1 1:5.2.1-22 ii libgdk-pixbuf2.0-02.32.1-1 ii libgl1-mesa-glx [libgl1] 10.6.8-1 ii libglib2.0-0 2.46.1-1 ii libglibmm-2.4-1v5 2.46.1-1 ii libglu1-mesa [libglu1]9.0.0-2.1 ii libgsl0ldbl 1.16+dfsg-4 ii libgtk2.0-0 2.24.28-1 ii libgtkglext1 1.2.0-3.2 ii libgtkmm-2.4-1v5 1:2.24.4-2+b1 ii libice6 2:1.0.9-1+b1 ii libpango-1.0-01.38.0-3 ii libpangocairo-1.0-0 1.38.0-3 ii libpangoft2-1.0-0 1.38.0-3 ii libpangomm-1.4-1v52.38.1-1 ii libpangox-1.0-0 0.0.2-5 ii libsigc++-2.0-0v5 2.6.1-2 ii libsm62:1.2.2-1+b1 ii libstdc++65.2.1-22 ii libx11-6 2:1.6.3-1 ii libxmu6 2:1.1.2-1 ii libxt61:1.1.4-1+b1 ii zlib1g1:1.2.8.dfsg-2+b1 mrtrix recommends no packages. Versions of packages mrtrix suggests: pn matlab-support pn mrtrix-doc ii octave 4.0.0-5 -- no debconf information --- End Message --- --- Begin Message --- Source: mrtrix Source-Version: 0.2.12-2 We believe that the bug you reported is fixed in the latest version of mrtrix, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 803...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Hanke (supplier of updated mrtrix package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 17:30:51 +0100 Source: mrtrix Binary: mrtrix mrtrix-doc Architecture: source amd64 all Version: 0.2.12-2 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team Changed-By: Michael Hanke Description: mrtrix - diffusion-weighted MRI white matter tractography mrtrix-doc - documentation for mrtrix Closes: 803075 805814 Changes: mrtrix (0.2.12-2) unstable; urgency=medium . * Add patch to include to fix FTBFS due to missing size_t. Courtesy of Iain Lane . * Adjust build-dependencies for GSL2 (Closes: #805814). * Make all top-level tools available in /usr/bin (Closes: #803075). * Bumped Standards-version to 3.9.6 -- no changes necessary. * Remove Debian menu file and keep .desktop file. * Standardize debian/control with CME Checksums-Sha1: ea722f49ba93890d522d4417595d635dca66b5fd 2090 mrtrix_0.2.12-2.ds
Bug#809279: marked as done ([ -n "$@" ] returns true when calling function/script with no arguments)
Your message dated Tue, 29 Dec 2015 10:46:13 -0700 with message-id <20151229102607077386...@bob.proulx.com> and subject line Re: Bug#809279: [ -n "$@" ] returns true when calling function/script with no arguments has caused the Debian Bug report #809279, regarding [ -n "$@" ] returns true when calling function/script with no arguments to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bash Version: 4.3-12 bash returns true on [ -n "$@" ] even when the scrpit/function is called without any arguments. despite this (from man bash): > When there are no positional parameters, "$@" and $@ expand to > nothing (i.e., they are removed). example: >01:22:20 363 ~$ cat /tmp/test #!/bin/bash echo -e "\$@=<$@>" [ -n "$@" ] && echo "[ -n \"\$@\" ] is true!" >01:22:22 363 ~$ /tmp/test $@=<> [ -n "$@" ] is true! >01:22:27 363 ~$ /tmp/test 111 $@=<111> [ -n "$@" ] is true! although [ -z "$@" ] works as expected. -n also works fine with any other undeclared/null variable --- End Message --- --- Begin Message --- dimas wrote: > bash returns true on [ -n "$@" ] even when the scrpit/function is called Due to the way "$@" works, as you quoted from the documentation, it is hard to imagine any valid use of [ -n "$@" ]. The reason is, as you quoted, it creates a variable number of arguments. Passing in a variable number of arguments to the [ test builtin will have behavior dependent upon the number of arguments. I don't see how that can ever be a valid construct. I hesitate to say that you wanted "$*" instead because I don't think that is actually what you want either. What are you trying to do? > without any arguments. despite this (from man bash): > > When there are no positional parameters, "$@" and $@ expand to > > nothing (i.e., they are removed). Correct. "$@" is expanded to be your positional parameters. Either zero, one, or many. That makes it unsuitable for use in the way you are asking with [ -n "$@" ] because it means that [ will have a variable number of arguments. That is not a valid construct. > #!/bin/bash > echo -e "\$@=<$@>" > [ -n "$@" ] && echo "[ -n \"\$@\" ] is true!" I think you are missing that [ works by looking at the number of arguments it is given. Here is the online standards documentation. Read the section that documents how 'test' behaves with different numbers of arguments. The section: The algorithm for determining the precedence of the operators and the return value that shall be generated is based on the number of arguments presented to test. http://pubs.opengroup.org/onlinepubs/009695399/utilities/test.html > >01:22:22 363 ~$ /tmp/test > $@=<> > [ -n "$@" ] is true! > >01:22:27 363 ~$ /tmp/test 111 > $@=<111> > [ -n "$@" ] is true! If there are no arguments then the "$@" expansion leaves nothing behind. It disappears. That leaves the shell with [ -n ] which is exactly the same as [ foo ] in behavior, always true. With only the single argument test exits true if the argument is not null. Since "-n" is not null then 'test' exits true. With only one argument -n is not an operand but now is simply a string, just like "foo". In order for -n to be an operand test needs two arguments. And with "$@" the question is what happens if you pass it in three. Or fifteen. Likely a syntax error but it depends upon the specific argument list. Because "$@" creates a variable number of arguments I don't think it is ever valid in a construct such as [ -n "$@" ]. This isn't a bug and bash is working as expected, as documented, and as required for standards compatibility with legacy and other shells. Therefore I am going to go ahead and mark the bug as closed. But please let's keep discussing the problem so as to be able to resolve your issue. Bob signature.asc Description: PGP signature --- End Message ---
Bug#808924: marked as done (pgadmin3 uses deprecated find -perm +xxx syntax, please switch to find -perm /+++)
Your message dated Tue, 29 Dec 2015 19:01:59 +0100
with message-id <20151229180159.ga1...@msg.df7cb.de>
and subject line Re: Bug#808924: pgadmin3 uses deprecated find -perm +xxx
syntax, please switch to find -perm /+++
has caused the Debian Bug report #808924,
regarding pgadmin3 uses deprecated find -perm +xxx syntax, please switch to
find -perm /+++
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
808924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pgadmin3
Version: 1.20.0-3
User: ametz...@debian.org
Usertags: find-perm-plus
Hello,
the pgadmin3 package uses find -perm +xxx. This GNU extension
syntax is deprecated and does not work in GNU findutils 4.5.11 and
later. Please change to find -perm /xxx instead.
The new syntax was introduced in 4.2.25 (October 2005) and should
therefore be available on any relevant system.
--
pgadmin3_1.20.0-3/pkg/mac/complete-bundle.sh
#We skip nested apps here - those are treated specially
todo=$(file `find ./ -perm +0111 ! -type d ! -path "*.app/*" ! -name
"*.app"` | grep -E "Mach-O (i386 )?executable" | awk -F ':| ' '{ORS=" "; print
$1}' | uniq)
echo "App: $tag: Found executables: $todo"
PathRank: 1.3797463, Final: 1.4480438
--
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--- End Message ---
--- Begin Message ---
Control: tags -1 upstream
Re: Andreas Metzler 2015-12-24 <20151224122927.gi1...@argenau.bebt.de>
> Hello,
>
> the pgadmin3 package uses find -perm +xxx. This GNU extension
> syntax is deprecated and does not work in GNU findutils 4.5.11 and
> later. Please change to find -perm /xxx instead.
>
> The new syntax was introduced in 4.2.25 (October 2005) and should
> therefore be available on any relevant system.
>
> --
> pgadmin3_1.20.0-3/pkg/mac/complete-bundle.sh
>
> #We skip nested apps here - those are treated specially
> todo=$(file `find ./ -perm +0111 ! -type d ! -path "*.app/*" ! -name
> "*.app"` | grep -E "Mach-O (i386 )?executable" | awk -F ':| ' '{ORS=" ";
> print $1}' | uniq)
> echo "App: $tag: Found executables: $todo"
>
> PathRank: 1.3797463, Final: 1.4480438
> --
>
> cu Andreas
Hi Andreas,
thanks for the report, I'm Cc'ing the PgAdmin upstream maintainers to
make them aware of the issue.
For Debian, I'm simply closing the bug because the deprecated syntax
is only used in mac build scripts which are not relevant on Linux.
Christoph
--
c...@df7cb.de | http://www.df7cb.de/
signature.asc
Description: Digital signature
--- End Message ---
Bug#772231: marked as done (hwloc: bashism in /bin/sh script)
Your message dated Tue, 29 Dec 2015 18:05:34 + with message-id and subject line Bug#772231: fixed in hwloc 1.11.2-1 has caused the Debian Bug report #772231, regarding hwloc: bashism in /bin/sh script to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 772231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: hwloc Severity: minor Version: 1.10.0-3 User: debian-rele...@lists.debian.org Usertags: goal-dash Hi, I've ran checkbashisms (from the 'devscripts' package) over the whole archive and I found that your package has a /bin/sh script that uses a "bashism". checkbashisms' output: > possible bashism in ./usr/bin/hwloc-assembler-remote line 87 (exit|return > with negative status code): > test $force -eq 0 && exit -1; Not using bash (or a Debian Policy compliant shell interpreter that doesn't provide such an extra feature) as /bin/sh is likely to lead to errors or unexpected behaviours. Please be aware that dash is the default /bin/sh. Please closely examine the above output and the script, and determine what the proper severity of the bug is, and adjust it accordingly. If it's important or greater please hurry to get this fixed for jessie. Hints about how to fix bashisms can be found at: https://wiki.ubuntu.com/DashAsBinSh Thanks in advance, Raphael Geissert --- End Message --- --- Begin Message --- Source: hwloc Source-Version: 1.11.2-1 We believe that the bug you reported is fixed in the latest version of hwloc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 772...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated hwloc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Dec 2015 18:31:50 +0100 Source: hwloc Binary: hwloc hwloc-nox libhwloc-dev libhwloc5 libhwloc-plugins libhwloc-common libhwloc-doc Architecture: source amd64 all Version: 1.11.2-1 Distribution: unstable Urgency: medium Maintainer: Samuel Thibault Changed-By: Samuel Thibault Description: hwloc - Hierarchical view of the machine - utilities hwloc-nox - Hierarchical view of the machine - non-X version of utilities libhwloc-common - Hierarchical view of the machine - common files libhwloc-dev - Hierarchical view of the machine - static libs and headers libhwloc-doc - Hierarchical view of the machine - documentation libhwloc-plugins - Hierarchical view of the machine - plugins libhwloc5 - Hierarchical view of the machine - shared libs Closes: 772231 806700 Changes: hwloc (1.11.2-1) unstable; urgency=medium . * New upstream release - hwloc.install: Add /usr/sbin for hwloc-dump-hwdata. * control: - Drop multiarch-support pre-depend. - Enable numa on mips64*. Closes: #806700. * compat: Bump to 9. * rules: Clear. * hwloc.menu: Remove, replaced by desktop file. * patches/bashism: Make hwloc-assembler-remote use bash since it uses bashisms. Closes: #772231. Checksums-Sha1: e941700e2954843673aa2f8d76e0719e666c570c 2539 hwloc_1.11.2-1.dsc 3d68de060808f04349538be4e63cde501cd53b0a 4019136 hwloc_1.11.2.orig.tar.bz2 6292e39d2158c4f22a675b1c9bccdec5bb46 9725 hwloc_1.11.2-1.debian.tar.bz2 c10268e45e16d5dd3b87df98feb7d3a36770fbfc 180486 hwloc-dbgsym_1.11.2-1_amd64.deb ed8add6c020614ddb13114b492a1fede52657dc8 127022 hwloc-nox-dbgsym_1.11.2-1_amd64.deb 1d9b2233a47c93af3da5db71528589a5f0f99dfb 137512 hwloc-nox_1.11.2-1_amd64.deb fe2b9053a2c5c2c88827fd9941943d5f09059266 155406 hwloc_1.11.2-1_amd64.deb 5e49ffa4a5fd1239bacb851bd1cfecfd63596e30 7504 libhwloc-common_1.11.2-1_all.deb b7fb089496656592ae36e89cfa9ac91ff18c680e 148148 libhwloc-dev_1.11.2-1_amd64.deb 5f18342c1e732dbaae45ec43aff3f1e1279d91b8 2017194 libhwloc-doc_1.11.2-1_all.deb f72751ea9c102f2ae9d057f32214d6e5fb529d5b 23448 libhwloc-plugins-dbgsym_1.11.2-1_amd64.deb 46bd87c60d53a209552a0ef15e4187ecf8a34e9f 15488 libhwloc-plugins_1.11.2-1_amd64.deb 66ff4a321d0d55d940d0828fa74e65536befcfc3 114666 libhwloc5-dbgsym_1.1
Bug#809285: marked as done (plexus-compiler: FTBFS: Plugin org.apache.maven.plugins:maven-release-plugin:2.5.1 or one of its dependencies could not be resolved: Cannot access central)
Your message dated Tue, 29 Dec 2015 18:06:19 + with message-id and subject line Bug#809285: fixed in plexus-compiler 2.4-3 has caused the Debian Bug report #809285, regarding plexus-compiler: FTBFS: Plugin org.apache.maven.plugins:maven-release-plugin:2.5.1 or one of its dependencies could not be resolved: Cannot access central to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: plexus-compiler Version: 2.4-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, plexus-compiler fails to build from source in unstable/amd64: [..] testCompilingSources(org.codehaus.plexus.compiler.javac.JavaxToolsCompilerTest) Time elapsed: 0.001 sec <<< ERROR! java.lang.IllegalAccessError: tried to access field org.codehaus.plexus.PlexusTestCase.container from class org.apache.maven.artifact.test.ArtifactTestCase at org.apache.maven.artifact.test.ArtifactTestCase.setUp(ArtifactTestCase.java:70) at org.codehaus.plexus.compiler.javac.AbstractJavacCompilerTest.setUp(AbstractJavacCompilerTest.java:50) at junit.framework.TestCase.runBare(TestCase.java:128) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) 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.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:95) at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:131) at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:108) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) Running org.codehaus.plexus.compiler.javac.JavacCompilerTest Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 0.001 sec <<< FAILURE! - in org.codehaus.plexus.compiler.javac.JavacCompilerTest testBuildCompilerArgs13(org.codehaus.plexus.compiler.javac.JavacCompilerTest) Time elapsed: 0 sec <<< ERROR! java.lang.IllegalAccessError: tried to access field org.codehaus.plexus.PlexusTestCase.container from class org.apache.maven.artifact.test.ArtifactTestCase at org.apache.maven.artifact.test.ArtifactTestCase.setUp(ArtifactTestCase.java:70) at org.codehaus.plexus.compiler.javac.AbstractJavacCompilerTest.setUp(AbstractJavacCompilerTest.java:50) at org.codehaus.plexus.compiler.javac.JavacCompilerTest.setUp(JavacCompilerTest.java:30) at junit.framework.TestCase.runBare(TestCase.java:128) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) 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.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:95) at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:131) at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Pr
Bug#806700: marked as done (hwloc: please enable numa support of mips64 mips64el)
Your message dated Tue, 29 Dec 2015 18:05:34 + with message-id and subject line Bug#806700: fixed in hwloc 1.11.2-1 has caused the Debian Bug report #806700, regarding hwloc: please enable numa support of mips64 mips64el to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 806700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:hwloc Version: 1.11.1-1 Please enable numa support for mips64el and mips64. I tested it on mips64el, it works well. -- YunQiang Su --- End Message --- --- Begin Message --- Source: hwloc Source-Version: 1.11.2-1 We believe that the bug you reported is fixed in the latest version of hwloc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 806...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Thibault (supplier of updated hwloc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Dec 2015 18:31:50 +0100 Source: hwloc Binary: hwloc hwloc-nox libhwloc-dev libhwloc5 libhwloc-plugins libhwloc-common libhwloc-doc Architecture: source amd64 all Version: 1.11.2-1 Distribution: unstable Urgency: medium Maintainer: Samuel Thibault Changed-By: Samuel Thibault Description: hwloc - Hierarchical view of the machine - utilities hwloc-nox - Hierarchical view of the machine - non-X version of utilities libhwloc-common - Hierarchical view of the machine - common files libhwloc-dev - Hierarchical view of the machine - static libs and headers libhwloc-doc - Hierarchical view of the machine - documentation libhwloc-plugins - Hierarchical view of the machine - plugins libhwloc5 - Hierarchical view of the machine - shared libs Closes: 772231 806700 Changes: hwloc (1.11.2-1) unstable; urgency=medium . * New upstream release - hwloc.install: Add /usr/sbin for hwloc-dump-hwdata. * control: - Drop multiarch-support pre-depend. - Enable numa on mips64*. Closes: #806700. * compat: Bump to 9. * rules: Clear. * hwloc.menu: Remove, replaced by desktop file. * patches/bashism: Make hwloc-assembler-remote use bash since it uses bashisms. Closes: #772231. Checksums-Sha1: e941700e2954843673aa2f8d76e0719e666c570c 2539 hwloc_1.11.2-1.dsc 3d68de060808f04349538be4e63cde501cd53b0a 4019136 hwloc_1.11.2.orig.tar.bz2 6292e39d2158c4f22a675b1c9bccdec5bb46 9725 hwloc_1.11.2-1.debian.tar.bz2 c10268e45e16d5dd3b87df98feb7d3a36770fbfc 180486 hwloc-dbgsym_1.11.2-1_amd64.deb ed8add6c020614ddb13114b492a1fede52657dc8 127022 hwloc-nox-dbgsym_1.11.2-1_amd64.deb 1d9b2233a47c93af3da5db71528589a5f0f99dfb 137512 hwloc-nox_1.11.2-1_amd64.deb fe2b9053a2c5c2c88827fd9941943d5f09059266 155406 hwloc_1.11.2-1_amd64.deb 5e49ffa4a5fd1239bacb851bd1cfecfd63596e30 7504 libhwloc-common_1.11.2-1_all.deb b7fb089496656592ae36e89cfa9ac91ff18c680e 148148 libhwloc-dev_1.11.2-1_amd64.deb 5f18342c1e732dbaae45ec43aff3f1e1279d91b8 2017194 libhwloc-doc_1.11.2-1_all.deb f72751ea9c102f2ae9d057f32214d6e5fb529d5b 23448 libhwloc-plugins-dbgsym_1.11.2-1_amd64.deb 46bd87c60d53a209552a0ef15e4187ecf8a34e9f 15488 libhwloc-plugins_1.11.2-1_amd64.deb 66ff4a321d0d55d940d0828fa74e65536befcfc3 114666 libhwloc5-dbgsym_1.11.2-1_amd64.deb c479f4e7b0c91c076ce3d05ac4ad03ca2fc84ee7 91990 libhwloc5_1.11.2-1_amd64.deb Checksums-Sha256: b7bdc6cb6154d60af8db90930e54a50d04b8ccc822e3a5cd96b16e543eb4e0dd 2539 hwloc_1.11.2-1.dsc 8c029b6b1638245837707bfa6c865f448af4e49e7d352335e019d818b51fecf8 4019136 hwloc_1.11.2.orig.tar.bz2 c8ececfb7b18929186f53341452ac4e18659c9d4eb395493543cfa8e85b0fb23 9725 hwloc_1.11.2-1.debian.tar.bz2 8410bcb52935f55ad452295f89210860cbf7199950e814cf5e777c3bdcd47d25 180486 hwloc-dbgsym_1.11.2-1_amd64.deb db40d9950c5ddb4c8ac23d42cd887d29f3c1e0918897d763d97eccd5fa19de66 127022 hwloc-nox-dbgsym_1.11.2-1_amd64.deb 73567fccb2dea1f55c58ae4d0d7875a4a1975b82240119b7d92557a22c788cda 137512 hwloc-nox_1.11.2-1_amd64.deb f64058e5a248d00c6752af5a7ccf04c64890c8b000b4a8b19eef6f71b6b9423a 155406 hwloc_1.11.2-1_amd64.deb d81883a9b3650a2a65b004523c44ddcdd787610591ab37f92c19061e144133cb 7504 libhwloc
Bug#802498: marked as done (Mouse grab stuck when clicking 'Remember password' in Iceweasel)
Your message dated Tue, 29 Dec 2015 19:09:41 + with message-id <1451416181.25978.52.ca...@decadent.org.uk> and subject line Re: Mouse grab stuck when clicking 'Remember password' in Iceweasel has caused the Debian Bug report #802498, regarding Mouse grab stuck when clicking 'Remember password' in Iceweasel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 802498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell Version: 3.18.0-1 Severity: important (I've only seen this behaviour when using Iceweasel, but that hasn't been upgraded recently whereas gnome-shell was upgraded yesterday.) Iceweasel pops up a transient to ask whether a new web site password should be remembered. If I attempt to dismiss this by clicking the 'Remember password' button, the transient stays in place, the browser hangs and the mouse remains grabbed. This doesn't happen if I dismiss the transient by clicking the close button on it. The following log lines appear to be related to this: Oct 20 16:48:48 deadeye gnome-session[9878]: (gnome-shell:9979): mutter-CRITICAL **: meta_window_focus: assertion '!window->override_redirect' failed Oct 20 16:48:49 deadeye gnome-session[9878]: ** (gnome-shell:9979): CRITICAL **: remove_mnemonics: assertion 'label != NULL' failed Ben. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii evolution-data-server3.18.0-3 ii gir1.2-accountsservice-1.0 0.6.40-3 ii gir1.2-atspi-2.0 2.18.1-1 ii gir1.2-caribou-1.0 0.4.19-1 ii gir1.2-clutter-1.0 1.24.2-1 ii gir1.2-freedesktop 1.46.0-1 ii gir1.2-gcr-3 3.18.0-1 ii gir1.2-gdesktopenums-3.0 3.18.0-1 ii gir1.2-gdm3 3.18.0-2 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.46.0-1 ii gir1.2-gnomebluetooth-1.03.18.0-1 ii gir1.2-gnomedesktop-3.0 3.18.1-1 ii gir1.2-gtk-3.0 3.18.2-1 ii gir1.2-gweather-3.0 3.18.1-1 ii gir1.2-ibus-1.0 1.5.10-1 ii gir1.2-mutter-3.03.18.0-1+b1 ii gir1.2-networkmanager-1.01.0.6-1 ii gir1.2-nmgtk-1.0 1.0.6-2 ii gir1.2-pango-1.0 1.38.0-3 ii gir1.2-polkit-1.00.105-12 ii gir1.2-soup-2.4 2.52.1-1 ii gir1.2-telepathyglib-0.120.24.1-1.1 ii gir1.2-telepathylogger-0.2 0.8.1-1 ii gir1.2-upowerglib-1.00.99.3-1+b2 ii gjs 1.43.3-2 ii gnome-backgrounds3.18.0-1 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.18.1-1+b1 ii gnome-shell-common 3.18.0-1 ii gsettings-desktop-schemas3.18.0-1 ii libatk-bridge2.0-0 2.18.1-1 ii libatk1.0-0 2.18.0-1 ii libc62.19-22 ii libcairo21.14.2-2 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libclutter-1.0-0 1.24.2-1 ii libcogl-pango20 1.22.0-1 ii libcogl201.22.0-1 ii libcroco30.6.8-3+b1 ii libdbus-glib-1-2 0.102-1 ii libecal-1.2-19 3.18.0-3 ii libedataserver-1.2-213.18.0-3 ii libgcr-base-3-1 3.18.0-1 ii libgdk-
Bug#679424: marked as done (arno-iptables-firewall nf_conntrack: table full, dropping packet.)
Your message dated Tue, 29 Dec 2015 20:22:31 +0100 with message-id <20151229192231.GA23138@meiner> and subject line Configurable via CONNTRACK has caused the Debian Bug report #679424, regarding arno-iptables-firewall nf_conntrack: table full, dropping packet. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 679424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679424 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: arno-iptables-firewall Version: 1.9.2.k-4 when starting or restarting arno-iptables-firewall its setting ulimit value too small (16384). per /etc/rc.local or manually you have to set: echo "131072" > /proc/sys/net/ipv4/netfilter/ip_conntrack_max echo "131072" > /sys/module/nf_conntrack/parameters/hashsize i am using: Debian Squeeze/stable 6.0.5 kernel 2.6.32-5-amd64 x86_64 GNU/Linux libc6 2.11.3-4 best regards ralf schaefer -- - Ralf Schaefer Wissenschaftszentrum Berlin für Sozialforschung gGmbH -DV/IT- Reichpietschufer 50 10785 Berlin Germany Fon :++49-30-25491-585/596 Fax :++49-30-25491-558 Mail:r...@wzb.eu Service: Mo-Fr 9.00-17.00 Geschäftsführung: Prof. Jutta Allmendinger Ph.D. / Heinrich Baßler Sitz der Gesellschaft: Berlin / Amtsgericht Charlottenburg / HRB 4303 - --- End Message --- --- Begin Message --- Bit of bug maintenance: This value is configurable via the CONNTRACK setting in /etc/arno-iptables/firewall/forewall.conf The default should work for most scenarios. Best, Michael--- End Message ---
Bug#803638: marked as done (doesn't start with systemd-networkd)
Your message dated Tue, 29 Dec 2015 19:43:49 + with message-id and subject line Bug#803638: fixed in arno-iptables-firewall 2.0.1.f-1 has caused the Debian Bug report #803638, regarding doesn't start with systemd-networkd to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 803638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: arno-iptables-firewall Version: 2.0.1.e-1 After activating systemd-networkd arno-iptables -firewall failed to load at boot. Reloading it maually resolves all problems. Probably firewall tries to start too early. I tried to add service file from: https://github.com/arno-iptables-firewall/aif/blob/master/lib/systemd/system/arno-iptables-firewall.service to my system and it solves problem. -- Petr Baláš - petr at balas dot cz --- End Message --- --- Begin Message --- Source: arno-iptables-firewall Source-Version: 2.0.1.f-1 We believe that the bug you reported is fixed in the latest version of arno-iptables-firewall, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 803...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Hanke (supplier of updated arno-iptables-firewall package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 19:53:58 +0100 Source: arno-iptables-firewall Binary: arno-iptables-firewall Architecture: source all Version: 2.0.1.f-1 Distribution: unstable Urgency: medium Maintainer: Michael Hanke Changed-By: Michael Hanke Description: arno-iptables-firewall - single- and multi-homed firewall script with DSL/ADSL support Closes: 778845 796587 803638 Changes: arno-iptables-firewall (2.0.1.f-1) unstable; urgency=medium . * Bumped Standards-Version to 3.9.6; no changes necessary. * Add package conflict to iptables-persistent to prevent undesired behavior that reverts all iptables rules set by this package (Closes: #778845). * Standardize and modernize debian/control via CME. * Install systemd service file (Closes: #803638, #796587), and adjust patches to use correct paths for Debian. Checksums-Sha1: 5e7de75f9831a1e0b9297aecd0d635a52a23075a 1973 arno-iptables-firewall_2.0.1.f-1.dsc af32d7757a3e85a7b92b88c8e4dfdfd86bb32b16 129893 arno-iptables-firewall_2.0.1.f.orig.tar.gz 3ace05303a663103ccd1d5382452148d319b1d64 53244 arno-iptables-firewall_2.0.1.f-1.debian.tar.xz 22535912e2dcdb4f6bfc31f8f14cf321e3ade4bc 145104 arno-iptables-firewall_2.0.1.f-1_all.deb Checksums-Sha256: 4f2f8e47c0722a703a44014123449184b57ffc8bdee905223a084df18a453146 1973 arno-iptables-firewall_2.0.1.f-1.dsc 198848b8241b31f8498b43517af13879f55e00d17edfc6647ca48b43af2789a9 129893 arno-iptables-firewall_2.0.1.f.orig.tar.gz 7b019dfb5b07269a0ada4dc345978ac66e7c650ca89aa6652a81820e3cfd1e43 53244 arno-iptables-firewall_2.0.1.f-1.debian.tar.xz bdf16c5e29aec75bb4efd3af11026214aec2c23606557b763f686e489fe39e8c 145104 arno-iptables-firewall_2.0.1.f-1_all.deb Files: 6e84aa728556ae875288b352b47b0c7f 1973 net optional arno-iptables-firewall_2.0.1.f-1.dsc 7a7b5d448b0103d3c1bf6fe3187caf58 129893 net optional arno-iptables-firewall_2.0.1.f.orig.tar.gz 9aa6404917663aca0fd82d401008bc28 53244 net optional arno-iptables-firewall_2.0.1.f-1.debian.tar.xz 03a6898090a514c0658f82361871c9f0 145104 net optional arno-iptables-firewall_2.0.1.f-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWgt4CAAoJEMBz0ih/+56bm+4P/2WyUc53xbEOQcyJbr5rxs3o lGVjBv+TXR0VOiSCRrzkQZYJmkYU6zrkguWzzCtrK43tAo1x9R7uNYHABPtGahcB 75U6+frmsTOy0BnFFz0nFEl+tj6BMrW5zr2zp+mkFnP6tXy1uDy3/Iq9QnPMWlnk 9kA50jDRrKwZh5ugB+RfF8Q6hZrGoyJ2uNq30pdzLH963nvirWHHa0glRONlEsHj ac9nsMx8wQ+pU2RkrgJEvHyZmpy2CN0PNN6AJJZsy5a44q3izQfPuxunuu6IkCJw nJwf7gUdu3S0KZPIMjMD+Xk+Iy4FJdq0n9Sd7UkdWPWIpUtQ/XXmmiLHEWFSGVlv c4cfT3tRo59QRjEzGJAycQLRZZ2acKyApbARDnJ5EdRMgorPShYtN3w60ZSlgoss WLDY+7GVaglHop3oNFEUDTMCF3NGEUIGZW+0o6YxTXviD3u2m4u6a3FnBf3cXrZy 6RUUK2/75RCoZvkI4MXjZDK9x7LrRHtjrYWs7/jBf3cdgI+uJpPGNkIZ13B3LStk MXp/8ZKG9mcQeT+pQI1lGwBuGjsBAKCqLZ/Ln86z3O2n+ldJUHvX+/XO4YKe4Fdu f01eu9UUxkwh9Y5Ui5AipdI93SuM8UqfC
Bug#796587: marked as done (arno-iptables-firewall: Has init script in runlevel S but no matching service file)
Your message dated Tue, 29 Dec 2015 19:43:49 + with message-id and subject line Bug#796587: fixed in arno-iptables-firewall 2.0.1.f-1 has caused the Debian Bug report #796587, regarding arno-iptables-firewall: Has init script in runlevel S but no matching service file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 796587: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796587 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: arno-iptables-firewall Severity: important User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: init-rcs-service Hi, Your package arno-iptables-firewall has an initscript that is enabled in runlevel S, but it does not provide a corresponding systemd service unit. Systemd generates units for all sysv init scripts that do not have a corresponding systemd unit. By default, it sets DefaultDependencies=yes, which means they get ordered after early boot has finished. The problem is that to preserve the runlevel S semantics, systemd in debian is currently[1] ordering all S services Before=sysinit.target. This target is particularly early in the boot sequence, which means that it is most of the time too strict. In turn, this means it is fairly easy to end up with dependency cycles. For an example, see bug [763315]. Do note that the cycle still exists with sysvinit, it is just that systemd complains more loudly. Please add a systemd unit for the given service with the appropriate dependencies, which most of the time will be less strict than Before=sysinit.target. In other cases, the script is simply not applicable in systemd, in which case the package should ship a symlink to /dev/null as /lib/systemd/system/.service. We have prepared a transition wiki page[2] explaining the issue in more detail, and outlining some general guidance. Please refer to it as it will have useful information. If you have any other doubts, feel free to ask in pkg-systemd-maintain...@lists.alioth.debian.org -- [1] http://sources.debian.net/src/systemd/222-2/debian/patches/Add-support-for-rcS.d-init-scripts-to-the-sysv-gener.patch/ [763315] https://bugs.debian.org/763315 [2] https://wiki.debian.org/Teams/pkg-systemd/rcSMigration --- End Message --- --- Begin Message --- Source: arno-iptables-firewall Source-Version: 2.0.1.f-1 We believe that the bug you reported is fixed in the latest version of arno-iptables-firewall, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 796...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Hanke (supplier of updated arno-iptables-firewall package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 19:53:58 +0100 Source: arno-iptables-firewall Binary: arno-iptables-firewall Architecture: source all Version: 2.0.1.f-1 Distribution: unstable Urgency: medium Maintainer: Michael Hanke Changed-By: Michael Hanke Description: arno-iptables-firewall - single- and multi-homed firewall script with DSL/ADSL support Closes: 778845 796587 803638 Changes: arno-iptables-firewall (2.0.1.f-1) unstable; urgency=medium . * Bumped Standards-Version to 3.9.6; no changes necessary. * Add package conflict to iptables-persistent to prevent undesired behavior that reverts all iptables rules set by this package (Closes: #778845). * Standardize and modernize debian/control via CME. * Install systemd service file (Closes: #803638, #796587), and adjust patches to use correct paths for Debian. Checksums-Sha1: 5e7de75f9831a1e0b9297aecd0d635a52a23075a 1973 arno-iptables-firewall_2.0.1.f-1.dsc af32d7757a3e85a7b92b88c8e4dfdfd86bb32b16 129893 arno-iptables-firewall_2.0.1.f.orig.tar.gz 3ace05303a663103ccd1d5382452148d319b1d64 53244 arno-iptables-firewall_2.0.1.f-1.debian.tar.xz 22535912e2dcdb4f6bfc31f8f14cf321e3ade4bc 145104 arno-iptables-firewall_2.0.1.f-1_all.deb Checksums-Sha256: 4f2f8e47c0722a703a44014123449184b57ffc8bdee905223a084df18a453146 1973 arno-iptables-firewall_2.0.1.f-1.dsc 198848b8241b31f8498b43517af13879f55e00d17edfc6647ca48b43af2789a9 129893 arno-iptables-firewall_2.0.1.f.orig.tar.gz
Bug#778845: marked as done (arno-iptables-firewall conflicts with iptables-persistent)
Your message dated Tue, 29 Dec 2015 19:43:49 + with message-id and subject line Bug#778845: fixed in arno-iptables-firewall 2.0.1.f-1 has caused the Debian Bug report #778845, regarding arno-iptables-firewall conflicts with iptables-persistent to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 778845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: arno-iptables-firewall Version: 2.0.1.c-1 Severity: important Dear Maintainer, I had a Lenny system here with arno-iptables-firewall and iptables-persistent installed. The execution order of the start-stop scripts was then such that - first arno-iptables-firewall starts up - then iptables-persistent restores the state - then arno-iptables-firewall stops - then iptables-persistent saves the state Thus, the arno-iptables-firewall rules were always cancelled. Please check if this is still the case in testing and, if yes, consider inserting a conflict to iptables-persistent in arno-iptables-firewall. Cheers Stephan Hachinger -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.1 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15) (ignored: LC_ALL set to de_DE@euro) Shell: /bin/sh linked to /bin/bash Versions of packages arno-iptables-firewall depends on: ii debconf [debconf-2.0] 1.5.49 ii gawk 1:4.0.1+dfsg-2.1 ii iproute1:3.16.0-2~bpo70+1 ii iptables 1.4.14-3.1 Versions of packages arno-iptables-firewall recommends: ii curl 7.26.0-1+wheezy12 ii dnsutils 1:9.9.5.dfsg-4~bpo70+1 ii rsyslog 7.6.3-2~bpo70+1 arno-iptables-firewall suggests no packages. -- debconf-show failed --- End Message --- --- Begin Message --- Source: arno-iptables-firewall Source-Version: 2.0.1.f-1 We believe that the bug you reported is fixed in the latest version of arno-iptables-firewall, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 778...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Hanke (supplier of updated arno-iptables-firewall package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 19:53:58 +0100 Source: arno-iptables-firewall Binary: arno-iptables-firewall Architecture: source all Version: 2.0.1.f-1 Distribution: unstable Urgency: medium Maintainer: Michael Hanke Changed-By: Michael Hanke Description: arno-iptables-firewall - single- and multi-homed firewall script with DSL/ADSL support Closes: 778845 796587 803638 Changes: arno-iptables-firewall (2.0.1.f-1) unstable; urgency=medium . * Bumped Standards-Version to 3.9.6; no changes necessary. * Add package conflict to iptables-persistent to prevent undesired behavior that reverts all iptables rules set by this package (Closes: #778845). * Standardize and modernize debian/control via CME. * Install systemd service file (Closes: #803638, #796587), and adjust patches to use correct paths for Debian. Checksums-Sha1: 5e7de75f9831a1e0b9297aecd0d635a52a23075a 1973 arno-iptables-firewall_2.0.1.f-1.dsc af32d7757a3e85a7b92b88c8e4dfdfd86bb32b16 129893 arno-iptables-firewall_2.0.1.f.orig.tar.gz 3ace05303a663103ccd1d5382452148d319b1d64 53244 arno-iptables-firewall_2.0.1.f-1.debian.tar.xz 22535912e2dcdb4f6bfc31f8f14cf321e3ade4bc 145104 arno-iptables-firewall_2.0.1.f-1_all.deb Checksums-Sha256: 4f2f8e47c0722a703a44014123449184b57ffc8bdee905223a084df18a453146 1973 arno-iptables-firewall_2.0.1.f-1.dsc 198848b8241b31f8498b43517af13879f55e00d17edfc6647ca48b43af2789a9 129893 arno-iptables-firewall_2.0.1.f.orig.tar.gz 7b019dfb5b07269a0ada4dc345978ac66e7c650ca89aa6652a81820e3cfd1e43 53244 arno-iptables-firewall_2.0.1.f-1.debian.tar.xz bdf16c5e29aec75bb4efd3af11026214aec2c23606557b763f686e489fe39e8c 145104 arno-iptables-firewall_2.0.1.f-1_all.deb Files: 6e84aa728556ae875288b352b47b0c7f 1973 net optional arno-iptables-firewall_2.0
Bug#805835: marked as done (voxbo: Fails to build with GSL 2)
Your message dated Tue, 29 Dec 2015 19:46:57 + with message-id and subject line Bug#805835: fixed in voxbo 1.8.5~svn1246-2 has caused the Debian Bug report #805835, regarding voxbo: Fails to build with GSL 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 805835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: voxbo Version: 1.8.5~svn1246-1.1 Severity: important Tags: upstream Dear Maintainer, Your package fails to build with GSL 2: fitOneOverF.cpp: In function 'VB_Vector* curvefit(VB_Vector*, VB_Vector*, VB_Vector*, double, double, double, double, const char*, bool)': fitOneOverF.cpp:205:26: error: 'struct gsl_multifit_fdfsolver' has no member named 'J' gsl_multifit_covar (s->J, 0.0, covar); ^ fitOneOverF.cpp: In function 'VB_Vector* curvefit12(VB_Vector*, VB_Vector*, VB_Vector*, double, double, double, const char*, bool)': fitOneOverF.cpp:398:26: error: 'struct gsl_multifit_fdfsolver' has no member named 'J' gsl_multifit_covar (s->J, 0.0, covar); ^ This needs to be fixed for the ongoing gsl transition (#804246). The full build log is attached, as is a patch to update the build dependencies for GSL 2 (changing libgsl0-dev to libgsl-dev). Kind Regards, Bas I: using cowbuilder as pbuilder dpkg-checkbuilddeps: Unmet build dependencies: libgsl-dev libqt4-dev libxi-dev W: Unmet build-dependency in source dpkg-buildpackage: source package voxbo dpkg-buildpackage: source version 1.8.5~svn1246-1.2 dpkg-buildpackage: source distribution UNRELEASED dpkg-buildpackage: source changed by Bas Couwenberg dpkg-source --before-build voxbo-1.8.5~svn1246 dpkg-checkbuilddeps: Unmet build dependencies: libgsl-dev libqt4-dev libxi-dev dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: warning: (Use -d flag to override.) dpkg-buildpackage: warning: this is currently a non-fatal warning with -S, but will probably become fatal in the future fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean make[1]: Entering directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246' for dir in lib vbwidgets fileformats munge stats crunch stand_alone utils resample gdscript scheduler scripts qtglm vbview vbsequence qtvlsm client server dbutil ; do make -C $dir clean ; done make[2]: Entering directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246/lib' rm -f a.out *.o *.so *~ *.exe *.a core.[0-9]* *.hlp.h *.moc.h moc_*.cpp rsrc.cpp test make[2]: Leaving directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246/lib' make[2]: Entering directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246/vbwidgets' rm -f a.out *.o *.so *~ *.exe *.a core.[0-9]* *.hlp.h *.moc.h moc_*.cpp rsrc.cpp libvbwidgets.a make[2]: Leaving directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246/vbwidgets' make[2]: Entering directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246/fileformats' rm -f a.out *.o *.so *~ *.exe *.a core.[0-9]* *.hlp.h *.moc.h moc_*.cpp rsrc.cpp dcmsplit dicominfo ffinfo vbrename analyzeinfo niftiinfo make[2]: Leaving directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246/fileformats' make[2]: Entering directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246/munge' rm -f a.out *.o *.so *~ *.exe *.a core.[0-9]* *.hlp.h *.moc.h moc_*.cpp rsrc.cpp tes2cub vb2cub vb2img vb2imgs vb2tes vb2vmp vbconv vbmunge vbcmp vbshift vbsmooth vbmaskmunge vecsplit vbinterpolate vbthresh vbprep vbbatch sumrfx calcperf cub2pngs setorigin fillmask vbhdr vbsim vbregion vborient vbi vbmerge4d vbvec2hdr vbse vbmaskinfo vboverlap vbimagemunge vbim vbfilter vbmaskcompare vbtool make[2]: Leaving directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246/munge' make[2]: Entering directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246/stats' rm -f vbvolregress vbmakeregress vbstatmap vbdumpstats glminfo vbperminfo vbxts vbtmap vbmakeresid vbfdr vbpermvec vbscoregen vbmap a.out *.o *.so *~ *.exe *.a core.[0-9]* *.hlp.h *.moc.h moc_*.cpp rsrc.cpp make[2]: Leaving directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246/stats' make[2]: Entering directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246/crunch' rm -f a.out *.o *.so *~ *.exe *.a core.[0-9]* *.hlp.h *.moc.h moc_*.cpp rsrc.cpp vbmm2 vbmakeglm vbmakefilter make[2]: Leaving directory '/home/bas/tmp/debian/voxbo-1.8.5~svn1246/crunch' make[2]:
Bug#808928: marked as done (lcdproc uses deprecated find -perm +xxx syntax, please switch to find -perm /+++)
Your message dated Tue, 29 Dec 2015 19:44:46 + with message-id and subject line Bug#808928: fixed in lcdproc 0.5.7-4 has caused the Debian Bug report #808928, regarding lcdproc uses deprecated find -perm +xxx syntax, please switch to find -perm /+++ to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 808928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lcdproc Version: 0.5.7-3 User: ametz...@debian.org Usertags: find-perm-plus Hello, the lcdproc package uses find -perm +xxx. This GNU extension syntax is deprecated and does not work in GNU findutils 4.5.11 and later. Please change to find -perm /xxx instead. The new syntax was introduced in 4.2.25 (October 2005) and should therefore be available on any relevant system. -- lcdproc_0.5.7-3/debian/autogen.sh echo Generating list of executable files... rm -f debian/executable.files find -type f -perm +111 ! -name '.*' -fprint debian/executable.files } -- cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' --- End Message --- --- Begin Message --- Source: lcdproc Source-Version: 0.5.7-4 We believe that the bug you reported is fixed in the latest version of lcdproc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 808...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominique Dumont (supplier of updated lcdproc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Dec 2015 19:26:08 +0100 Source: lcdproc Binary: lcdproc lcdproc-extra-drivers lcdproc-dbg Architecture: source amd64 Version: 0.5.7-4 Distribution: unstable Urgency: medium Maintainer: Dominique Dumont Changed-By: Dominique Dumont Description: lcdproc- LCD display driver daemon and clients lcdproc-dbg - debugging symbols for lcdproc lcdproc-extra-drivers - extra drivers for the LCD display driver daemon Closes: 808928 Changes: lcdproc (0.5.7-4) unstable; urgency=medium . * copyright: fixed typo that trigger lintian errors * Remove autogen hack and and use dh-autoreconf (Closes: #808928) (Tx Andreas) * rules: removed obsolete dh_installinit params * Ship a systemd service file using dh-systemd Checksums-Sha1: 52a00495c4c1db1926859c3636416052ce38ba61 2563 lcdproc_0.5.7-4.dsc 4b5dcce3bff097903d07566e327340f8408f9dd2 12760 lcdproc_0.5.7-4.debian.tar.xz 8d4d16db2d61b6f72d3d1229977b85b83f75cceb 886724 lcdproc-dbg_0.5.7-4_amd64.deb bf98c6cb2fd0ea2ffe673baa567397a66af36250 81190 lcdproc-extra-drivers_0.5.7-4_amd64.deb 9d270ff8b0d013edce2540c9e7061fc18c1ac1f2 291772 lcdproc_0.5.7-4_amd64.deb Checksums-Sha256: d5f02ac5afa107ba6ac850753cad029982a0fd08e4f4b1279b8d0a769ccb8e39 2563 lcdproc_0.5.7-4.dsc a71e639db7178335e680799c4ad28b910bb909a26b0622831cec15cd2ef4cc67 12760 lcdproc_0.5.7-4.debian.tar.xz 83e07f7e6edcd572df16676b18224283d7eac4e3e3e3d3e26933944af425d19a 886724 lcdproc-dbg_0.5.7-4_amd64.deb a4b041aa4f16c2a071a95c654c8a9202df44af0f7ad017676f6f7c25a6c59726 81190 lcdproc-extra-drivers_0.5.7-4_amd64.deb a19736e841cade0ce7e9da05cb0b0732bcce99bd709b1190897ad3a9e39c14cc 291772 lcdproc_0.5.7-4_amd64.deb Files: 81aba8d754e3a26058f538cf32914f8e 2563 utils extra lcdproc_0.5.7-4.dsc 729d7d828c0e0f23a79d0fbcf43888c3 12760 utils extra lcdproc_0.5.7-4.debian.tar.xz 786bcbc0c0bcf7f8fbe800bca1b8b081 886724 debug extra lcdproc-dbg_0.5.7-4_amd64.deb b3cc0fe99b74611897e52c1135468481 81190 utils extra lcdproc-extra-drivers_0.5.7-4_amd64.deb 12eec9fcc9528152ffd6b27849be51ee 291772 utils extra lcdproc_0.5.7-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJWgtVDAAoJEMMfT9lJqytsgFQP/3G643JG7PfoqwA77CRcd3EV mrw9CXB+2rHcD/w2Jn24AymEJN++11E2Y71kXNmW1VAoLpfOOXcPRMhVWNQfc56a 38QrPW64a1clKTltd1w4KwEhMQt+mJ2X+jqMbqYI0oB67mEdi0pgV9T05Ey8Utcp KxX4zAiE/5zR2gIPHrvB2F74nYiOq55j2uW9jXfjNmAzT/gMFUH5ydCVI++bPTrc Wxxno1+gUPO1pOKLl/h2PUuLTNiSC+PNtgUkrVy2tntu
Processed: Re: Bug#797159: Update twinkle to QT5
Processing commands for cont...@bugs.debian.org: > close 797159 1:1.9.0+dfsg-1 Bug #797159 [twinkle] Update twinkle to QT5 Marked as fixed in versions twinkle/1:1.9.0+dfsg-1. Bug #797159 [twinkle] Update twinkle to QT5 Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 797159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809356: marked as done (gnome-themes-standard-data: left over legacy files)
Your message dated Tue, 29 Dec 2015 21:02:26 +0100 with message-id <1451419346.13713.19.ca...@scientia.net> and subject line Re: Bug#809356: gnome-themes-standard-data: left over legacy files has caused the Debian Bug report #809356, regarding gnome-themes-standard-data: left over legacy files to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-themes-standard-data Version: 3.18.0-2 Severity: normal Hi. During upgrade to -2: Unpacking gnome-themes-standard-data (3.18.0-2) over (3.18.0-1) ... dpkg: warning: unable to delete old directory '/usr/share/icons/default': Directory not empty That directory contains: ls -al /usr/share/icons/default total 4 drwxr-xr-x 1 root root 22 Jul 18 2008 . drwxr-xr-x 1 root root 326 Nov 26 18:03 .. lrwxrwxrwx 1 root root 32 Nov 14 2009 index.theme -> /etc/alternatives/x-cursor-theme which was hoever not created by myself, so I guess gnome-themes-standard-data would need to clean that up and then properly remove the dir. Could you please repeat that in one of the upcomming uploads so that users don't have stale files which never again get removed? Thanks, Chris. --- End Message --- --- Begin Message --- On Tue, 2015-12-29 at 23:00 +0300, Dmitry Shachnev wrote: > No, it has just been moved from gnome-themes-standard to adwaita- > icon-theme > (because that's where the icons really live), which is a hard > dependency. > That file is not stale. Ah I see... then I guess we can just close that as you proposed before :-) Thanks for clearing that up, Chris. smime.p7s Description: S/MIME cryptographic signature --- End Message ---
Bug#252264: marked as done (aptitude: explicit selection of less-scored version is sticky)
Your message dated Tue, 29 Dec 2015 21:13:06 +0100 with message-id <20151229201305.gz10...@sym.noone.org> and subject line Re: [Aptitude-devel] Bug#252264: aptitude: explicit selection of less-scored version is sticky has caused the Debian Bug report #252264, regarding aptitude: explicit selection of less-scored version is sticky to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 252264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252264 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: aptitude Version: 0.2.14.1-2 Severity: normal On my sarge box, if I explicitely select for installation a sid version of a package that is already uptodate according to sarge, and then later (same session, no install run in between) change my mind and reselect the sarge version, then aptitude still considers the sid version as being the one to install. IOW, it is the sid version appearing in the "available version" column, if I hit '+' the sid version gets selected, and if I insist on keeping the sarge version the package appears in the 'get' listing as an ordinary package for which a new version is available in sarge, but for which upgrade was not requested. After the other packages get upgraded, and cache gets refreshed, the behaviour is back to normal... at one detail: 2 packages suggested by an installed one are now selected for automatic installation, although I don't think they were here before, and I did not select them explicitely. Rather, IIRC they were pulled by one sid-only package I had tagged for install before changing my mind, and I'm quite sure they were untagged when I deselected that sid package (qdvdauthor, from Christian Marillat's repository). -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (90, 'experimental'), (90, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.24-smp Locale: LANG=C, LC_CTYPE=C Versions of packages aptitude depends on: ii apt [libapt-pkg-libc6.3-5-3 0.5.25 Advanced front-end for dpkg ii libc6 2.3.2.ds1-12 GNU C Library: Shared libraries an ii libgcc1 1:3.3.3-9GCC support library ii libncurses5 5.4-3Shared libraries for terminal hand ii libsigc++-1.2-5c102 1.2.5-1 Type-safe Signal Framework for C++ ii libstdc++5 1:3.3.3-9The GNU Standard C++ Library v3 -- no debconf information -- Yann Dirson |Why make M$-Bill richer & richer ? Debian-related: | Support Debian GNU/Linux: Pro: | Freedom, Power, Stability, Gratuity http://ydirson.free.fr/| Check <http://www.debian.org/> --- End Message --- --- Begin Message --- Version: 0.6.8.2-1 Hi, Manuel A. Fernandez Montecelo wrote: > >On my sarge box, if I explicitely select for installation a sid version of a > >package that is already uptodate according to sarge, and then later (same > >session, no install run in between) change my mind and reselect the sarge > >version, then aptitude still considers the sid version as being the one to > >install. IOW, it is the sid version appearing in the "available version" > >column, if I hit '+' the sid version gets selected, and if I insist on > >keeping the sarge version the package appears in the 'get' listing as an > >ordinary package for which a new version is available in sarge, but for > >which upgrade was not requested. > > > >After the other packages get upgraded, and cache gets refreshed, the > >behaviour is back to normal... Sounds familiar, indeed. > I am not sure if I follow 100% the steps here, since the descriptions > are a bit vague and somewhat difficult to parse for me... It's probably clearer what he means if you ran into this in the past, too. :-) If you rebuilt the view (pressing "l" and then Enter without changing the value) usually moved that package into the "upgradable packages" section and stayed there. > but I was trying to upgrade iceweasel to different versions of > unstable and experimental several times and the behaviour was the > expected one. The package iceweasel is a good example to test and I can no more reproduce that behaviour in neither Sid nor Wheezy (oldstable; aptitude 0.6.8.2-1) which was quite well known to me (but never considered an issue, more a little peculiarity. I
Bug#746054: marked as done (twinkle: FTBFS: configure: error: Library requirements (libzrtpcpp >= 1.3.0) not met)
Your message dated Tue, 29 Dec 2015 15:25:01 -0500 with message-id <20151229202501.GA18632@alcyone> and subject line Re: twinkle: FTBFS: configure: error: Library requirements (libzrtpcpp >= 1.3.0) not met has caused the Debian Bug report #746054, regarding twinkle: FTBFS: configure: error: Library requirements (libzrtpcpp >= 1.3.0) not met to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 746054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: twinkle Version: 1:1.4.2-4 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140426 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for speex/speex_preprocess.h... yes > checking speex/speex_echo.h usability... yes > checking speex/speex_echo.h presence... yes > checking for speex/speex_echo.h... yes > checking for libzrtpcpp >= 1.3.0... Package libcrypto was not found in the > pkg-config search path. Perhaps you should add the directory containing > `libcrypto.pc' to the PKG_CONFIG_PATH environment variable Package > 'libcrypto', required by 'libzrtpcpp', not found > configure: error: Library requirements (libzrtpcpp >= 1.3.0) not met; > consider adjusting the PKG_CONFIG_PATH environment variable if your libraries > are in a nonstandard prefix so pkg-config can find them. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/04/26/twinkle_1.4.2-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Hi David, This bug is fixed in libzrtpcpp/2.3.4-1.1, which depends on libssl-dev. https://bugs.debian.org/746655 Regards, Peter--- End Message ---
Bug#667527: marked as done (lfm: Theme key bindings like Total Commander ?)
Your message dated Tue, 29 Dec 2015 20:36:08 +
with message-id
and subject line Bug#667527: fixed in lfm 3.0-1
has caused the Debian Bug report #667527,
regarding lfm: Theme key bindings like Total Commander ?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
667527: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lfm
Version: 2.2-1
Severity: wishlist
Hello,
Like gimp for theme for photoshop, it would be nice that lfm could be copy
paste a config file
keybinding so that it looks like TC
shift F6 to rename
Shift f4 to make a txt file (nano )
shift f5 to cp -r a folder.
and so on ...
a theme like tc
thank you
-- System Information:
Debian Release: 6.0.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lfm depends on:
ii python 2.6.6-3+squeeze6 interactive high-level object-orie
ii python-support 1.0.10 automated rebuilding support for P
lfm recommends no packages.
lfm suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lfm
Source-Version: 3.0-1
We believe that the bug you reported is fixed in the latest version of
lfm, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 667...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Echeverry (supplier of updated lfm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 21 Dec 2015 15:28:44 -0500
Source: lfm
Binary: lfm
Architecture: source all
Version: 3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverry
Changed-By: Daniel Echeverry
Description:
lfm- simple but powerful file manager for the UNIX console
Closes: 588023 667527 694922 700274 727260 742757
Changes:
lfm (3.0-1) unstable; urgency=medium
.
* New upstream release. (Closes: #727260, #742757, #667527,
#694922, #700274, #588023)
* debian/control
+ Change Homepage field
+ Remove python (>= 2.6.6-3~) in B-D-I field
+ Add python3-all in B-D-I field
+ Change X-Python-Version to X-Python3-Version
now the code works with python3
+ Change ${python:Depends} to ${python3:Depends} in Depends
* debian/copyright
+ Update source field
+ Extend copyright holder years
* Remove lfm.docs file
* Remove lfm.links file
* debian/patches
+ Update ignore_COPYING.patch patch
+ Remove remove_install_changelog.patch patch
+ Add fix_interpreter.diff patch
+ Fix shebang
* debian/rules
+ unexport LANG variables to prevent encoding error
+ Use dh-python helper and pybuild as buildsystem
+ export PYBUILDNAME variable
+ Remove override_dh_compress
+ Remove override_dh_auto_install
+ Add override_dh_installchangelogs to install upstream changelog
* Update debian/watch file
Checksums-Sha1:
668efd8adefa6e73b1d14fc7465d7b57f67b2745 1680 lfm_3.0-1.dsc
a7ef8503c1a9b054ad64c2327173a02eb741389c 87341 lfm_3.0.orig.tar.gz
b070037ba5211092fbac11708f05ced9956dae65 3812 lfm_3.0-1.debian.tar.xz
bb92afc4870123a638b00985ef1f6f3282f9b72d 73186 lfm_3.0-1_all.deb
Checksums-Sha256:
1876d0967ece84ea085c15e72418e70fa48997ad25449c9db03c065bd4636b15 1680
lfm_3.0-1.dsc
dcb9c3dc3122ed41bfb72ed2f03e41afa917d17b23ee8459371e7f39e9b888e7 87341
lfm_3.0.orig.tar.gz
2621beea0fbb2b0da068098dee56356f89ef7ccc8bb028d7222aeceec67f2324 3812
lfm_3.0-1.debian.tar.xz
4b82d8866650af960b086dd84937ec55c25be1ba89dc5dfa2032c9f2bae24c9f 73186
lfm_3.0-1_all.deb
Files:
3de2f03963023b3a550192ecabfda456 1680 utils optional lfm_3.0-1.dsc
9c13c5fafcb1aecd43f51fa9b0278000 87341 utils optional lfm_3.0.orig.tar.gz
d83fe874e02489fbcddaca855de7d84a 3812 utils optional lfm_3.0-1.debian.tar.xz
f8df071045da7c6c701f3e8a3c05e379 73186 utils optional lfm_3.0-1_all.deb
-BEGIN PGP SIGNATURE
Bug#694922: marked as done (accents make lfm crash)
Your message dated Tue, 29 Dec 2015 20:36:08 +
with message-id
and subject line Bug#694922: fixed in lfm 3.0-1
has caused the Debian Bug report #694922,
regarding accents make lfm crash
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
694922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lfm
Version: 2.2-1
Severity: important
r
-- System Information:
Debian Release: 6.0.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages lfm depends on:
ii python 2.6.6-3+squeeze6 interactive high-level object-orie
ii python-support 1.0.10 automated rebuilding support for P
lfm recommends no packages.
lfm suggests no packages.
File "/usr/bin/lfm", line 27, in
lfm_start(sys.argv)
File "/usr/share/lfm/lfm/lfm.py", line 924, in lfm_start
path = curses.wrapper(main, prefs, paths1, paths2)
File "/usr/lib/python2.6/curses/wrapper.py", line 43, in wrapper
return func(stdscr, *args, **kwds)
File "/usr/share/lfm/lfm/lfm.py", line 845, in main
app.load_paths(paths1, paths2)
File "/usr/share/lfm/lfm/lfm.py", line 90, in load_paths
self.lpane.load_tabs_with_paths(paths1)
File "/usr/share/lfm/lfm/lfm.py", line 299, in load_tabs_with_paths
err = tab.init(utils.decode(path))
File "/usr/share/lfm/lfm/lfm.py", line 795, in init
err = self.init_dir(path)
File "/usr/share/lfm/lfm/lfm.py", line 612, in init_dir
self.nfiles, self.files = files.get_dir(path,
app.prefs.options['show_dotfiles'])
File "/usr/share/lfm/lfm/files.py", line 252, in get_dir
if ask_convert_invalid_encoding_filename(newf):
File "/usr/share/lfm/lfm/utils.py", line 1001, in
ask_convert_invalid_encoding_filename
'In file <%s>, convert' % filename)
File "/usr/share/lfm/lfm/messages.py", line 326, in confirm
win.addstr(1, 2 , '%s?' % utils.encode(question))
File "/usr/share/lfm/lfm/utils.py", line 976, in encode
return buf.encode(g_encoding)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe9' in position
33: ordinal not in range(128)
maybe due to _Op??ration
that has some e with accents
sincerely,
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lfm
Source-Version: 3.0-1
We believe that the bug you reported is fixed in the latest version of
lfm, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 694...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Echeverry (supplier of updated lfm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 21 Dec 2015 15:28:44 -0500
Source: lfm
Binary: lfm
Architecture: source all
Version: 3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverry
Changed-By: Daniel Echeverry
Description:
lfm- simple but powerful file manager for the UNIX console
Closes: 588023 667527 694922 700274 727260 742757
Changes:
lfm (3.0-1) unstable; urgency=medium
.
* New upstream release. (Closes: #727260, #742757, #667527,
#694922, #700274, #588023)
* debian/control
+ Change Homepage field
+ Remove python (>= 2.6.6-3~) in B-D-I field
+ Add python3-all in B-D-I field
+ Change X-Python-Version to X-Python3-Version
now the code works with python3
+ Change ${python:Depends} to ${python3:Depends} in Depends
* debian/copyright
+ Update source field
+ Extend copyright holder years
* Remove lfm.docs file
* Remove lfm.links file
* debian/patches
+ Update ignore_COPYING.patch patch
+ Remove remove_install_changelog.patch patch
+ Add fix_interpreter.diff patch
+ Fix shebang
* debian
Bug#588023: marked as done (lfm: some crash during uses)
Your message dated Tue, 29 Dec 2015 20:36:08 +
with message-id
and subject line Bug#588023: fixed in lfm 3.0-1
has caused the Debian Bug report #588023,
regarding lfm: some crash during uses
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
588023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lfm
Version: 2.2-1
Severity: normal
Dear Sir;
I created a folder and suddenly it crashed, lfm.
bet regards
Traceback (most recent call last):
File "/usr/bin/lfm", line 27, in
lfm_start(sys.argv)
File "/usr/share/lfm/lfm/lfm.py", line 924, in lfm_start
path = curses.wrapper(main, prefs, paths1, paths2)
File "/usr/lib/python2.5/curses/wrapper.py", line 44, in wrapper
return func(stdscr, *args, **kwds)
File "/usr/share/lfm/lfm/lfm.py", line 848, in main
ret = app.run()
File "/usr/share/lfm/lfm/lfm.py", line 198, in run
ret = self.act_pane.manage_keys()
File "/usr/share/lfm/lfm/lfm.py", line 571, in manage_keys
ret = actions.do(self.act_tab, ch)
File "/usr/share/lfm/lfm/actions.py", line 165, in do
exec(act)
File "", line 1, in
File "/usr/share/lfm/lfm/actions.py", line 782, in make_dir
newdir = doEntry(tab.path, 'Make directory', 'Type directory name')
File "/usr/share/lfm/lfm/actions.py", line 1313, in doEntry
tabpath).run()
File "/usr/share/lfm/lfm/messages.py", line 906, in run
ans = self.active_widget.manage_keys()
File "/usr/share/lfm/lfm/messages.py", line 727, in manage_keys
self.show()
File "/usr/share/lfm/lfm/messages.py", line 720, in show
self.entry.addstr(utils.encode(textstr[:ew]), curses.color_pair(11) |
curses.A_BOLD)
File "/usr/share/lfm/lfm/utils.py", line 976, in encode
return buf.encode(g_encoding)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xc3' in position 3:
ordinal not in range(128)
#
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-3-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages lfm depends on:
ii python2.5.4-9An interactive high-level object-o
ii python-support1.0.8 automated rebuilding support for P
lfm recommends no packages.
lfm suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lfm
Source-Version: 3.0-1
We believe that the bug you reported is fixed in the latest version of
lfm, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 588...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Echeverry (supplier of updated lfm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 21 Dec 2015 15:28:44 -0500
Source: lfm
Binary: lfm
Architecture: source all
Version: 3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverry
Changed-By: Daniel Echeverry
Description:
lfm- simple but powerful file manager for the UNIX console
Closes: 588023 667527 694922 700274 727260 742757
Changes:
lfm (3.0-1) unstable; urgency=medium
.
* New upstream release. (Closes: #727260, #742757, #667527,
#694922, #700274, #588023)
* debian/control
+ Change Homepage field
+ Remove python (>= 2.6.6-3~) in B-D-I field
+ Add python3-all in B-D-I field
+ Change X-Python-Version to X-Python3-Version
now the code works with python3
+ Change ${python:Depends} to ${python3:Depends} in Depends
* debian/copyright
+ Update source field
+ Extend copyright holder years
* Remove lfm.docs file
* Remove lfm.links file
* debian/patches
+ Update ignore_COPYING.patch patch
+ Remove remove_install_changelog.patch patch
+ Add fix_interpreter.diff patch
Bug#727260: marked as done (le: grep hangs up on search)
Your message dated Tue, 29 Dec 2015 20:36:08 +
with message-id
and subject line Bug#727260: fixed in lfm 3.0-1
has caused the Debian Bug report #727260,
regarding le: grep hangs up on search
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
727260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: le
Version: 1.14.9-2
Severity: normal
Dear Maintainer,
This is what happened:
I went to /var/log/ and pressed F3 on dpkg.log, then I
pressed / to search. I entered vi in the search box, and it
froze up. I had to do a 'pkill grep' to get out of it.
Apparently, grep mistakes the search for vi as a call to the vi
program.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.10-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages le depends on:
ii libc6 2.17-93
ii libgcc1 1:4.8.1-10
ii libncursesw5 5.9+20130608-1
ii libtinfo5 5.9+20130608-1
le recommends no packages.
le suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lfm
Source-Version: 3.0-1
We believe that the bug you reported is fixed in the latest version of
lfm, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 727...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Echeverry (supplier of updated lfm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 21 Dec 2015 15:28:44 -0500
Source: lfm
Binary: lfm
Architecture: source all
Version: 3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverry
Changed-By: Daniel Echeverry
Description:
lfm- simple but powerful file manager for the UNIX console
Closes: 588023 667527 694922 700274 727260 742757
Changes:
lfm (3.0-1) unstable; urgency=medium
.
* New upstream release. (Closes: #727260, #742757, #667527,
#694922, #700274, #588023)
* debian/control
+ Change Homepage field
+ Remove python (>= 2.6.6-3~) in B-D-I field
+ Add python3-all in B-D-I field
+ Change X-Python-Version to X-Python3-Version
now the code works with python3
+ Change ${python:Depends} to ${python3:Depends} in Depends
* debian/copyright
+ Update source field
+ Extend copyright holder years
* Remove lfm.docs file
* Remove lfm.links file
* debian/patches
+ Update ignore_COPYING.patch patch
+ Remove remove_install_changelog.patch patch
+ Add fix_interpreter.diff patch
+ Fix shebang
* debian/rules
+ unexport LANG variables to prevent encoding error
+ Use dh-python helper and pybuild as buildsystem
+ export PYBUILDNAME variable
+ Remove override_dh_compress
+ Remove override_dh_auto_install
+ Add override_dh_installchangelogs to install upstream changelog
* Update debian/watch file
Checksums-Sha1:
668efd8adefa6e73b1d14fc7465d7b57f67b2745 1680 lfm_3.0-1.dsc
a7ef8503c1a9b054ad64c2327173a02eb741389c 87341 lfm_3.0.orig.tar.gz
b070037ba5211092fbac11708f05ced9956dae65 3812 lfm_3.0-1.debian.tar.xz
bb92afc4870123a638b00985ef1f6f3282f9b72d 73186 lfm_3.0-1_all.deb
Checksums-Sha256:
1876d0967ece84ea085c15e72418e70fa48997ad25449c9db03c065bd4636b15 1680
lfm_3.0-1.dsc
dcb9c3dc3122ed41bfb72ed2f03e41afa917d17b23ee8459371e7f39e9b888e7 87341
lfm_3.0.orig.tar.gz
2621beea0fbb2b0da068098dee56356f89ef7ccc8bb028d7222aeceec67f2324 3812
lfm_3.0-1.debian.tar.xz
4b82d8866650af960b086dd84937ec55c25be1ba89dc5dfa2032c9f2bae24c9f 73186
lfm_3.0-1_all.deb
Files:
3de2f03963023b3a550192ecabfda456 1680 utils optional lfm_3.0-1.dsc
9c13c5fafcb1aecd43f51fa9b0278000 87341 utils optional lfm_3.0.orig.tar.gz
d83fe874e02489fbcddaca855de7d84a 3812 utils optional lfm_3.0-1.debian.tar.xz
f8df071045da7c6c701f3e8a3c05e379 73186 utils optional lfm_3.0-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG
Bug#809346: marked as done (libphp-adodb: trying to overwrite '/usr/share/doc-base/doc-base', which is also in package doc-base 0.10.6)
Your message dated Tue, 29 Dec 2015 20:36:14 + with message-id and subject line Bug#809346: fixed in libphp-adodb 5.20.2-2 has caused the Debian Bug report #809346, regarding libphp-adodb: trying to overwrite '/usr/share/doc-base/doc-base', which is also in package doc-base 0.10.6 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809346 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libphp-adodb Version: 5.20.2-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, I tried to install this package and got the following errors: bminton:~# apt-get install libphp-adodb Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: libphp-adodb 0 upgraded, 1 newly installed, 0 to remove and 705 not upgraded. 714 not fully installed or removed. Need to get 0 B/454 kB of archives. After this operation, 2,307 kB of additional disk space will be used. etckeeper warning: special files could cause problems with git: ./runit/getty-2/supervise/ok ./runit/getty-2/supervise/control ./runit/getty-4/supervise/ok ./runit/getty-4/supervise/control ./runit/getty-3/supervise/ok ./runit/getty-3/supervise/control ./runit/getty-5/supervise/ok ./runit/getty-5/supervise/control [master ddba03d] saving uncommitted changes in /etc prior to apt run Author: Brian Minton 2 files changed, 3 insertions(+) create mode 100644 php5/conf.d/adodb.ini Preconfiguring packages ... (Reading database ... 1487348 files and directories currently installed.) Preparing to unpack .../libphp-adodb_5.20.2-1_all.deb ... Unpacking libphp-adodb (5.20.2-1) ... dpkg: error processing archive /var/cache/apt/archives/libphp-adodb_5.20.2-1_all.deb (--unpack): trying to overwrite '/usr/share/doc-base/doc-base', which is also in package doc-base 0.10.6 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for doc-base (0.10.6) ... Processing 2 added doc-base files... Error while merging /usr/share/doc-base/libsvnclientadapter-java-doc with /usr/share/doc-base/libsvnclientadapter-java-doc-javadoc: format html already defined. Registering documents with dwww... Registering documents with scrollkeeper... Errors were encountered while processing: /var/cache/apt/archives/libphp-adodb_5.20.2-1_all.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) - -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libphp-adodb depends on: ii cdebconf [debconf-2.0] 0.201 ii debconf [debconf-2.0] 1.5.58 ii php55.6.16+dfsg-2 ii php5-cli5.6.16+dfsg-2 Versions of packages libphp-adodb recommends: ii php5-odbc5.6.16+dfsg-2 ii php5-pgsql 5.6.16+dfsg-2 ii php5-sybase 5.6.16+dfsg-2 Versions of packages libphp-adodb suggests: ii php5-adodb 5.04-7+b3 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iF4EAREIAAYFAlaCwNsACgkQa46zoGXPuqkOfgD/Y1WwJqFZ9Yz8++FZ6IIiAQnv G3d/eeQsrkNViQwWk2gA/io8su042a2AB1tiP4JPqXjFQRufNWBeRvqBAZcUuQPz =En4w -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: libphp-adodb Source-Version: 5.20.2-2 We believe that the bug you reported is fixed in the latest version of libphp-adodb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jean-Michel Vourgère (supplier of updated libphp-adodb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 21:07:19 +0100 Source: libphp-adodb Binary: libphp-adodb Architecture: source all Version: 5.20.2-2 Distribution: unstable Urgency:
Bug#700274: marked as done (lfm: serious - crash with german characters)
Your message dated Tue, 29 Dec 2015 20:36:08 +
with message-id
and subject line Bug#700274: fixed in lfm 3.0-1
has caused the Debian Bug report #700274,
regarding lfm: serious - crash with german characters
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
700274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lfm
Version: 2.2-1
Severity: important
HI,
I use vifm and it works fine, but lfm cannot handle sthg else than english
chars.
German chars leave a brutal crash of lfm.
Please a fix fast.
Sincerely / Thanks.
Y.
-- System Information:
Debian Release: 6.0.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lfm depends on:
ii python 2.6.6-3+squeeze6 interactive high-level object-orie
ii python-support 1.0.10 automated rebuilding support for P
lfm recommends no packages.
lfm suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lfm
Source-Version: 3.0-1
We believe that the bug you reported is fixed in the latest version of
lfm, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 700...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Echeverry (supplier of updated lfm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 21 Dec 2015 15:28:44 -0500
Source: lfm
Binary: lfm
Architecture: source all
Version: 3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverry
Changed-By: Daniel Echeverry
Description:
lfm- simple but powerful file manager for the UNIX console
Closes: 588023 667527 694922 700274 727260 742757
Changes:
lfm (3.0-1) unstable; urgency=medium
.
* New upstream release. (Closes: #727260, #742757, #667527,
#694922, #700274, #588023)
* debian/control
+ Change Homepage field
+ Remove python (>= 2.6.6-3~) in B-D-I field
+ Add python3-all in B-D-I field
+ Change X-Python-Version to X-Python3-Version
now the code works with python3
+ Change ${python:Depends} to ${python3:Depends} in Depends
* debian/copyright
+ Update source field
+ Extend copyright holder years
* Remove lfm.docs file
* Remove lfm.links file
* debian/patches
+ Update ignore_COPYING.patch patch
+ Remove remove_install_changelog.patch patch
+ Add fix_interpreter.diff patch
+ Fix shebang
* debian/rules
+ unexport LANG variables to prevent encoding error
+ Use dh-python helper and pybuild as buildsystem
+ export PYBUILDNAME variable
+ Remove override_dh_compress
+ Remove override_dh_auto_install
+ Add override_dh_installchangelogs to install upstream changelog
* Update debian/watch file
Checksums-Sha1:
668efd8adefa6e73b1d14fc7465d7b57f67b2745 1680 lfm_3.0-1.dsc
a7ef8503c1a9b054ad64c2327173a02eb741389c 87341 lfm_3.0.orig.tar.gz
b070037ba5211092fbac11708f05ced9956dae65 3812 lfm_3.0-1.debian.tar.xz
bb92afc4870123a638b00985ef1f6f3282f9b72d 73186 lfm_3.0-1_all.deb
Checksums-Sha256:
1876d0967ece84ea085c15e72418e70fa48997ad25449c9db03c065bd4636b15 1680
lfm_3.0-1.dsc
dcb9c3dc3122ed41bfb72ed2f03e41afa917d17b23ee8459371e7f39e9b888e7 87341
lfm_3.0.orig.tar.gz
2621beea0fbb2b0da068098dee56356f89ef7ccc8bb028d7222aeceec67f2324 3812
lfm_3.0-1.debian.tar.xz
4b82d8866650af960b086dd84937ec55c25be1ba89dc5dfa2032c9f2bae24c9f 73186
lfm_3.0-1_all.deb
Files:
3de2f03963023b3a550192ecabfda456 1680 utils optional lfm_3.0-1.dsc
9c13c5fafcb1aecd43f51fa9b0278000 87341 utils optional lfm_3.0.orig.tar.gz
d83fe874e02489fbcddaca855de7d84a 3812 utils optional lfm_3.0-1.debian.tar.xz
f8df071045da7c6c701f3e8a3c05e379 73186 utils optional lfm_3.0-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCgAGBQJWgujoAAoJENX9/BVhaL9glsMQANPH2Fm2d4GL0ogwBI
Bug#727271: marked as done (lfm: grep hangs up on search)
Your message dated Tue, 29 Dec 2015 20:36:08 +
with message-id
and subject line Bug#727260: fixed in lfm 3.0-1
has caused the Debian Bug report #727260,
regarding lfm: grep hangs up on search
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
727260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lfm
Version: 2.3-1
Severity: normal
Dear Maintainer,
This is what happened:
I went to /var/log/ and pressed F3 on dpkg.log, then I
pressed / to search. I entered vi in the search box, and it
froze up. I had to do a 'pkill grep' to get out of it.
Apparently, grep mistakes the search for vi as a call to the vi
program.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.10-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lfm depends on:
ii python 2.7.5-5
ii python-support 1.0.15
lfm recommends no packages.
lfm suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lfm
Source-Version: 3.0-1
We believe that the bug you reported is fixed in the latest version of
lfm, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 727...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Echeverry (supplier of updated lfm package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 21 Dec 2015 15:28:44 -0500
Source: lfm
Binary: lfm
Architecture: source all
Version: 3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Echeverry
Changed-By: Daniel Echeverry
Description:
lfm- simple but powerful file manager for the UNIX console
Closes: 588023 667527 694922 700274 727260 742757
Changes:
lfm (3.0-1) unstable; urgency=medium
.
* New upstream release. (Closes: #727260, #742757, #667527,
#694922, #700274, #588023)
* debian/control
+ Change Homepage field
+ Remove python (>= 2.6.6-3~) in B-D-I field
+ Add python3-all in B-D-I field
+ Change X-Python-Version to X-Python3-Version
now the code works with python3
+ Change ${python:Depends} to ${python3:Depends} in Depends
* debian/copyright
+ Update source field
+ Extend copyright holder years
* Remove lfm.docs file
* Remove lfm.links file
* debian/patches
+ Update ignore_COPYING.patch patch
+ Remove remove_install_changelog.patch patch
+ Add fix_interpreter.diff patch
+ Fix shebang
* debian/rules
+ unexport LANG variables to prevent encoding error
+ Use dh-python helper and pybuild as buildsystem
+ export PYBUILDNAME variable
+ Remove override_dh_compress
+ Remove override_dh_auto_install
+ Add override_dh_installchangelogs to install upstream changelog
* Update debian/watch file
Checksums-Sha1:
668efd8adefa6e73b1d14fc7465d7b57f67b2745 1680 lfm_3.0-1.dsc
a7ef8503c1a9b054ad64c2327173a02eb741389c 87341 lfm_3.0.orig.tar.gz
b070037ba5211092fbac11708f05ced9956dae65 3812 lfm_3.0-1.debian.tar.xz
bb92afc4870123a638b00985ef1f6f3282f9b72d 73186 lfm_3.0-1_all.deb
Checksums-Sha256:
1876d0967ece84ea085c15e72418e70fa48997ad25449c9db03c065bd4636b15 1680
lfm_3.0-1.dsc
dcb9c3dc3122ed41bfb72ed2f03e41afa917d17b23ee8459371e7f39e9b888e7 87341
lfm_3.0.orig.tar.gz
2621beea0fbb2b0da068098dee56356f89ef7ccc8bb028d7222aeceec67f2324 3812
lfm_3.0-1.debian.tar.xz
4b82d8866650af960b086dd84937ec55c25be1ba89dc5dfa2032c9f2bae24c9f 73186
lfm_3.0-1_all.deb
Files:
3de2f03963023b3a550192ecabfda456 1680 utils optional lfm_3.0-1.dsc
9c13c5fafcb1aecd43f51fa9b0278000 87341 utils optional lfm_3.0.orig.tar.gz
d83fe874e02489fbcddaca855de7d84a 3812 utils optional lfm_3.0-1.debian.tar.xz
f8df071045da7c6c701f3e8a3c05e379 73186 utils optional lfm_3.0-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCgAGBQJWgujoAAoJENX9/BVhaL9glsMQANPH2Fm2
Bug#742757: marked as done (lfm: crashes when showing infos about a file with a given long filename pattern)
Your message dated Tue, 29 Dec 2015 20:36:08 +
with message-id
and subject line Bug#742757: fixed in lfm 3.0-1
has caused the Debian Bug report #742757,
regarding lfm: crashes when showing infos about a file with a given long
filename pattern
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
742757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lfm
Version: 2.3-1
Severity: important
--- DESCRIPTION ---
lfm crashes when it has to show informations (pressing "i" on the file) about a
file having this name pattern:
my_very_long_file_name_which_exceeds_the_terminal_width.(www.some-site.com)
in general, any file with a name in this form crashes it:
aa(zzz.xxx-ccc.vvv)
where the first part of the name (the "a"s) is a long string which exceeds the
terminal width.
--- RESULTS ---
This is what i get in my terminal after the crash:
Traceback (most recent call last):
File "/usr/bin/lfm", line 27, in
lfm_start(sys.argv)
File "/usr/share/lfm/lfm/lfm.py", line 1155, in lfm_start
path = curses.wrapper(main, prefs, paths1, paths2)
File "/usr/lib/python2.7/curses/wrapper.py", line 43, in wrapper
return func(stdscr, *args, **kwds)
File "/usr/share/lfm/lfm/lfm.py", line 1077, in main
ret = app.run()
File "/usr/share/lfm/lfm/lfm.py", line 209, in run
ret = self.act_pane.manage_keys()
File "/usr/share/lfm/lfm/lfm.py", line 804, in manage_keys
ret = actions.do(self.act_tab, ch)
File "/usr/share/lfm/lfm/actions.py", line 169, in do
exec(act)
File "", line 1, in
File "/usr/share/lfm/lfm/actions.py", line 569, in file_info
do_show_file_info(tab)
File "/usr/share/lfm/lfm/actions.py", line 1202, in do_show_file_info
show_info(tab, tab.sorted[tab.file_i])
File "/usr/share/lfm/lfm/actions.py", line 1195, in show_info
pyview.InternalView('Information about \'%s\'' % encode(file), buf).run()
File "/usr/share/lfm/lfm/pyview.py", line 109, in __init__
self.init_curses()
File "/usr/share/lfm/lfm/pyview.py", line 152, in init_curses
self.win_title.addstr(0, int((app.maxw-len(title))/2), title)
_curses.error: addstr() returned ERR
--- TO REPRODUCE ---
$ touch
aaa\(www.some-site.com\)
$ lfm
$ < Once in lfm, browse for the file and press "i" on it to show its
informations >
I think the filename lenght may vary depending on the width of the terminal we
are testing in.
--- WHAT I TRIED ---
i'll refer to this filename:
aaa(www.some-site.com)
I tested the issue creating some files with different names, trying to exclude
isolate the issue.
I couldn't come to a conclusion, or investigate more, since it has a very weird
behaviour. For example:
- using the above filename, but followed by something like
"(ww.some-site.ccc)" doesn't crash it;
- using the above filename, but with no brackets and an underscore separating
the a's string from the url part, crashes it;
- using the above filename, but with no brackets and an nothing separating the
a's string from the url part, doesn't crash it;
- using the above filename, but with no hyphen, doesn't crash it;
- using the above filename, but with a shorter a's string, doesn't crash it;
I guess one should focus on the last part of the filename (the one including
brackets, dots and hyphens)
I flagged this issue as "important" since it makes the software unusable, and
there may be some more filename patterns affected by it.
Thanks for your nice work.
Bye.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.13-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lfm depends on:
ii python 2.7.5-5
ii python-support 1.0.15
lfm recommends no packages.
lfm suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lfm
Source-Version: 3.0-1
We believe
Bug#737895: marked as done (twinkle: Twinkle UI does not show at all)
Your message dated Tue, 29 Dec 2015 15:40:24 -0500 with message-id <20151229204024.GA19399@alcyone> and subject line Re: twinkle: Twinkle UI does not show at all has caused the Debian Bug report #737895, regarding twinkle: Twinkle UI does not show at all to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 737895: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: twinkle Version: 1:1.4.2-4 Severity: normal I don't know how this happens; possibly some configuration in my user is creating this situation (as otherwise nobody would be able to use twinkle), but in any case it seems serious enough to warrant a bug report. I have just installed twinkle, and when I try to run it, absolutely nothing happens. I tried removing the ~/.twinkle directory but still no cookie: $ rm -rf .twinkle/ $ twinkle Critical: Cannot open file for reading: /home/tincho/.twinkle/twinkle.cfg ^C I honestly don't know what to do, or what information to provide. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IE.utf8, LC_CTYPE=en_IE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages twinkle depends on: ii libasound21.0.27.2-3 ii libboost-regex1.54.0 1.54.0-4+b1 ii libc6 2.17-97 ii libccgnu2-1.8-0 1.8.1-6 ii libccrtp0 2.0.6-3 ii libgcc1 1:4.8.2-14 ii libgsm1 1.0.13-4 ii libmagic1 1:5.14-2 ii libncurses5 5.9+20140118-1 ii libreadline6 6.2+dfsg-0.1 ii libsndfile1 1.0.25-9 ii libspeex1 1.2~rc1.1-1 ii libspeexdsp1 1.2~rc1.1-1 ii libstdc++64.8.2-14 ii libtinfo5 5.9+20140118-1 ii libucommon6 6.0.7-1.1 ii libxml2 2.9.1+dfsg1-3 ii libzrtpcpp2 2.3.4-1 ii zlib1g1:1.2.8.dfsg-1 twinkle recommends no packages. twinkle suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1:1.9.0+dfsg-1 Hi Martín, Twinkle was ported to Qt 5 and a new version has been uploaded to Debian. Regards, Peter--- End Message ---
Bug#677166: marked as done (offlineimap: Regularly hangs due to an exception and must be killed)
Your message dated Tue, 29 Dec 2015 20:48:51 + with message-id and subject line Bug#677166: fixed in offlineimap 6.6.1+dfsg1-1 has caused the Debian Bug report #677166, regarding offlineimap: Regularly hangs due to an exception and must be killed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 677166: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: offlineimap Version: 6.5.4-2 Severity: important I regularly get an exception like the one below and then offlineimap just hangs. Folder [Gmail]/Spam [acc: vega.james]: ERROR: list.remove(x): x not in list ERROR: Syncing folder Spam [acc: vega.james] list.remove(x): x not in list ERROR: ERROR in syncfolder for vega.james folder Spam: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/offlineimap/accounts.py", line 446, in syncfolder localfolder.syncmessagesto(remotefolder, statusfolder) File "/usr/lib/python2.7/dist-packages/offlineimap/folder/Base.py", line 526, in syncmessagesto action(dstfolder, statusfolder) File "/usr/lib/python2.7/dist-packages/offlineimap/folder/Base.py", line 409, in syncmessagesto_copy register = 0) File "/usr/lib/python2.7/dist-packages/offlineimap/folder/Base.py", line 335, in copymessageto new_uid = dstfolder.savemessage(uid, message, flags, rtime) File "/usr/lib/python2.7/dist-packages/offlineimap/folder/IMAP.py", line 611, in savemessage self.imapserver.releaseconnection(imapobj) File "/usr/lib/python2.7/dist-packages/offlineimap/imapserver.py", line 112, in releaseconnection self.assignedconnections.remove(connection) ValueError: list.remove(x): x not in list -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-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 offlineimap depends on: ii libjs-sphinxdoc 1.1.3+dfsg-4 ii python 2.7.3~rc2-1 ii python2.62.6.7-4 ii python2.72.7.3~rc2-2.1 Versions of packages offlineimap recommends: ii python-sqlite 1.0.1-9 Versions of packages offlineimap suggests: pn doc-base pn python-kerberos -- no debconf information --- End Message --- --- Begin Message --- Source: offlineimap Source-Version: 6.6.1+dfsg1-1 We believe that the bug you reported is fixed in the latest version of offlineimap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 677...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated offlineimap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 28 Dec 2015 18:12:09 +0200 Source: offlineimap Binary: offlineimap Architecture: source all Version: 6.6.1+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Ilias Tsitsimpis Changed-By: Ilias Tsitsimpis Description: offlineimap - IMAP/Maildir synchronization and reader support Closes: 677166 Changes: offlineimap (6.6.1+dfsg1-1) unstable; urgency=medium . * New upstream release (Closes: #677166) * Add missing docbook-xsl build dependency * Update patches to apply cleanly on new upstream Checksums-Sha1: e37ba2ef287f005eea4b3bd05d1bb3b8d0c87b4c 2073 offlineimap_6.6.1+dfsg1-1.dsc d97d089662c8d1a5f3de2a28024e42ad848a5efe 167284 offlineimap_6.6.1+dfsg1.orig.tar.gz 4c12e96de825d55e5b90ca29326403c88a5bd4d6 21408 offlineimap_6.6.1+dfsg1-1.debian.tar.xz 5a95b75090329711ee5dd887bb24b7e73a106a75 145224 offlineimap_6.6.1+dfsg1-1_all.deb Checksums-Sha256: 64db31cabcc6d7efcb7b155fcf64e50bad849c68ceac1903574c8b3d9a398426 2073 offlineimap_6.6.1+dfsg1-1.dsc cc6c588f411ee45d3e310634233d5043bdf42144b16aa7cfd8a732599f3b8d90 167284 offlineimap_6.6.1+dfsg1.orig.tar.gz 40efc456b08189baccef963ebfbedc55b278e8171da67d0872bbd130d32a4fed 21408 offlineimap_6.6.1+dfsg1-1
Bug#782359: marked as done (twinkle just doesn't launch)
Your message dated Tue, 29 Dec 2015 15:48:26 -0500 with message-id <20151229204826.GA20134@alcyone> and subject line Re: twinkle just doesn't launch has caused the Debian Bug report #782359, regarding twinkle just doesn't launch to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 782359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: twinkle Version: 1:1.4.2-4 Severity: important Dear Maintainer, Here is what I have when trying twinkle on jessie : name@desktop:~$ twinkle Critical: Cannot open file for reading: /home/name/.twinkle/twinkle.cfg ^C name@desktop:~$ touch /home/name/.twinkle/twinkle.cfg name@desktop:~$ twinkle Twinkle 1.4.2, February 25 2009 Copyright (C) 2005-2009 Michel de Boer Users: * twinkle Local IP: 255.255.255.255 twinkle: registering phone... Twinkle> twinkle, registration failed: 404 Not Found ^D Info: Deregistering phone... ^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^CProcessus arrêté and I had to kill -9 the process to get access to the console again. And now that I've overwritten my clipboard, I don't remember the yahoo groups address reportbug asked me to CC this bug report to. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (980, 'stable-updates'), (980, 'stable'), (90, 'experimental'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages twinkle depends on: ii libasound21.0.28-1 ii libboost-regex1.54.0 1.54.0-5+b1 ii libc6 2.19-17 ii libccgnu2-1.8-0 1.8.1-6+b2 ii libccrtp0 2.0.3-4 ii libgcc1 1:4.9.2-10 ii libgsm1 1.0.13-4 ii libmagic1 1:5.22+15-2 ii libncurses5 5.9+20140913-1+b1 ii libreadline6 6.3-8+b3 ii libsndfile1 1.0.25-9.1 ii libspeex1 1.2~rc1.2-1 ii libspeexdsp1 1.2~rc1.2-1 ii libstdc++64.9.2-10 ii libtinfo5 5.9+20140913-1+b1 ii libucommon6 6.1.10-1 ii libxml2 2.9.1+dfsg1-5 ii libzrtpcpp2 2.3.4-1+b1 ii zlib1g1:1.2.8.dfsg-2+b1 twinkle recommends no packages. twinkle suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 1:1.9.0+dfsg-1 On Fri, Apr 10, 2015 at 10:46:48PM +0200, eingousef wrote: > Here is what I have when trying twinkle on jessie : > > name@desktop:~$ twinkle > > Critical: Cannot open file for reading: /home/name/.twinkle/twinkle.cfg A new version of Twinkle that reenables the GUI has been uploaded to Debian unstable and will be shipped with the next Debian stable release (stretch). Peter--- End Message ---
Bug#794837: marked as done (Explicit logging for violations of blacklisted directories)
Your message dated Tue, 29 Dec 2015 21:07:10 + with message-id and subject line Bug#794837: fixed in firejail 0.9.36-1 has caused the Debian Bug report #794837, regarding Explicit logging for violations of blacklisted directories to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 794837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firejail Version: 0.9.28-1 Severity: wishlist Using iceweasel with firejail prevented the leak of SSH keys in the Firefox exploit announced today: https://blog.mozilla.org/security/2015/08/06/firefox-exploit-found-in-the-wild/ It would be very useful if there were a firejail option to explicitiy warn the user if a firejailed application tries to access a blacklisted file/directory, so that such zero days are detected earlier (since no non-malicious use of Firefox will ever access my .ssh directory). Cheers, Moritz --- End Message --- --- Begin Message --- Source: firejail Source-Version: 0.9.36-1 We believe that the bug you reported is fixed in the latest version of firejail, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 794...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Reiner Herrmann (supplier of updated firejail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 20:46:42 +0100 Source: firejail Binary: firejail Architecture: source amd64 Version: 0.9.36-1 Distribution: unstable Urgency: low Maintainer: Reiner Herrmann Changed-By: Reiner Herrmann Description: firejail - sandbox to restrict the application environment Closes: 794837 Changes: firejail (0.9.36-1) unstable; urgency=low . * New upstream release. - Support for logging of blacklist violations (Closes: #794837) * Updated Homepage field. * Dropped reproducibility patch, which has been applied upstream. * Dropped debian/missing-sources. Upstream removed binaries from release tarball. Checksums-Sha1: 4a50fb3e99c272b8917acbe42c4c8577dd41792a 1729 firejail_0.9.36-1.dsc 698c32955f4efc2b335174381f389b99e53af858 151123 firejail_0.9.36.orig.tar.bz2 37e9451a8378a0805938703d8115b9f6aab68f59 2648 firejail_0.9.36-1.debian.tar.xz 122be913c6518f4cea449b37bef7e4b02b1843a8 348552 firejail-dbgsym_0.9.36-1_amd64.deb 2c609a0902ec7cf06c957bc904c32920d5ec9493 136182 firejail_0.9.36-1_amd64.deb Checksums-Sha256: 876caecf22a0e1bf39b531a6b5b16a464e4f588712c739a0613a092e8740cbee 1729 firejail_0.9.36-1.dsc db16c93e6f838048b0bbcb3b90aa191f79860382c5197fd2ac6df51f1a469510 151123 firejail_0.9.36.orig.tar.bz2 654afb8bcb2bd15632581ac0279659cff8eb6df9a887bd5f2496d62924c3d8b8 2648 firejail_0.9.36-1.debian.tar.xz 1f62f4e4d90dd02dffde04af98feca1634e07e76a7f1946e20b6ff0248969417 348552 firejail-dbgsym_0.9.36-1_amd64.deb d619cf38931b4db40cc56074fe31c9d399dfdbd1515265932c4cb2b35b8fc480 136182 firejail_0.9.36-1_amd64.deb Files: 848dd0d5677a3b6160fa5b642a7514e1 1729 utils optional firejail_0.9.36-1.dsc 82e14802eba6c59aa6a56576769f99dc 151123 utils optional firejail_0.9.36.orig.tar.bz2 b54f8420f13459a66f4ca266def2eee8 2648 utils optional firejail_0.9.36-1.debian.tar.xz f83c1a2237112f9f380394b0fc9384b7 348552 debug extra firejail-dbgsym_0.9.36-1_amd64.deb c32d08add12892b98904b0fae670ad88 136182 utils optional firejail_0.9.36-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWgvHPAAoJENzjEOeGTMi/EowP/i8fWuj96jUzpbdAALt3LIme X1v0Q7QtwM/s31P6ZyykL6O/HpV3qDyEiJDe12QPF+n3Pc7y+NiE8QXCFHEl0Q6F KyTqjWlD6ldvOQRQtIzz8n7IdbsKXG59JfBb8uyWHPY9Kd70UaMHeLCLC9cWVSo3 Z/YwjOBN/gkvY+O4YC/ve7FsF5kaIyXrbDDltwd93pyECVawEX0Y0NiQNaO/605q 9G3bJOGDz9YQ4rHUUjTOy1VUkwu0OegXSKyChBPffix5r+lEj4FQJzgnxtQM7BEb UNInTfFKVO0GU9QJoLahHRq3UFcNP/AVVS7H9IJ+EXsaY3uoEN9II8BIJUt9OmPm hiPBdLnyQLnhcWmM7uQAkS+srt7irDhklYhXK7JcQEUG9OSo2FN0DvnIfHaKk+ZO iL6YLgLng7yzgY55BMi8AkgNve2TcezEHEayFKXTvkFS7KV36WAoKZCPAxa/9tsD I+7y2SKACNz5jtIfdjOxK+DQBcQ0ZBG6yBi/rVRQTO8Y28ihIiOq5XTp+3I14nt1 pCazFPhmKlBtdEwt59y+1s4X0yqbHqhUbnvb5MJ1aYQV5QqMf7lEjHSZSGm0lJgW oNnrxBQTS/N+F//z4Ib198jqcHL25T9JW4OKhdV1fpeAT71tXdv4xGGWlA4dbHu7
Bug#808538: marked as done (RFS: corebird/1.1-1 [ITP])
Your message dated Tue, 29 Dec 2015 22:47:52 +0100 with message-id <20151229214752.ga2...@shiftout.net> and subject line Re: Bug#808538: RFS: corebird has caused the Debian Bug report #808538, regarding RFS: corebird/1.1-1 [ITP] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 808538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808538 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "corebird" Package name: corebird Version : 1.1-1 Upstream Author : Timm Bäder URL : http://corebird.baedert.org License : GPL-3+ Section : misc It builds those binary packages: corebird - Native Gtk+ Twitter client for the Linux desktop To access further information about this package, please visit the following URL: http://mentors.debian.net/package/corebird Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/corebird/corebird_1.1-1.dsc More information about corebird can be obtained from http://corebird.baedert.org. Regards, Philip Rinn -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (600, 'testing'), (550, 'unstable'), (500, 'testing-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Hi, On Tue, Dec 29, 2015 at 07:16:08PM +0100, Philip Rinn wrote: > I uploaded a revised build to http://mentors.debian.net/package/corebird Uploaded. (: Thanks, Iain @ 32c3 -- --- End Message ---
Processed: forcibly merging 808785 809349
Processing commands for cont...@bugs.debian.org:
> forcemerge 808785 809349
Bug #808785 {Done: Ondřej Surý } [liblmdb0]
/sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/liblmdb.so.0 is not a symbolic
link
Bug #809349 [liblmdb0] /sbin/ldconfig.real:
/usr/lib/x86_64-linux-gnu/liblmdb.so.0 is not a symbolic link
Marked Bug as done
Marked as fixed in versions lmdb/0.9.17-3.
Marked as found in versions lmdb/0.9.17-1.
Merged 808785 809349
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
808785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808785
809349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#784850: marked as done (samba: Samba doesn't get printer list from cups)
Your message dated Tue, 29 Dec 2015 23:28:06 + with message-id <20151229232806.ga24...@jelmer.uk> and subject line Re: [Pkg-samba-maint] Bug#784850: bug closed has caused the Debian Bug report #784850, regarding samba: Samba doesn't get printer list from cups to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 784850: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: samba Version: 2:4.1.17+dfsg-2 Severity: normal Dear Maintainer, In a fresh Debian Jessie setup running with the KDE desktop. CUPS recognises and prints to remote printers attached to Windows 7 machines. CUPS recognises and prints to printer connected directly to the Jessie server SAMBA can share and read files from Windows 7 machines. The printer connected to Debian appears as shared in the CUPS web interface and Windows 7 clients can print directly to CUPS using IPP and the printer address: http://harpia:631/printers/Stylus-COLOR-777 But Samba doesn't show the printer connected to Debian Jessie as available. Using smbtree -U. doesn't show the printer in Debian as available and people coming with their laptops can't see the printer in Windows. It seems that Samba can't connect to CUPS to get the list of available printers in the Debian server. It can also be a problem in CUPS but since it can share the printer directly to Windows using IPP it seems to me that the problem is with samba. The setup and the same smb.conf worked perfectly in Debian Squeeze, the same problem happened in Wheezy and happens now in Jessie. Here is the smb.conf file testparm shows it as correct. -- [global] workgroup = KAMEHOUSE netbios name = HARPIA security = user map to guest = Bad User printcap name = cups disable spoolss = Yes show add printer wizard = No printing = cups name resolve order = bcast host wins lmhosts load printers = yes [data] comment = data1 path = /media/ntfs/share read only = Yes guest ok = Yes [media] path = /media/deposito/Media read only = Yes guest ok = Yes [printers] comment = Printer in Linux path = /var/spool/samba guest ok = Yes printable = Yes use client driver = Yes browseable = Yes -- Note: If I add this to smb.conf [Stylus-COLOR-777] comment=Local printer printer=Stylus-COLOR-777 path=/var/spool/samba/ printing=cups printcap name=cups printable=yes use client driver=yes guest ok=yes writable=no then the printer is shown as available to smbtree -U and Windows 7 clients but trying to add the printer shows Windows couldn't connect to the printer Error 0x002e in Windows It doesn't even let you choose the printer model or driver. So it seems that samba is showing the printer name but is not communicating with cups or getting the list of printers from CUPS. Thanks -- System Information: Debian Release: 8.0 Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages samba depends on: ii adduser 3.113+nmu3 ii dpkg 1.17.25 ii libasn1-8-heimdal1.6~rc2+dfsg-9 ii libbsd0 0.7.0-2 ii libc62.19-18 ii libcomerr2 1.42.12-1.1 ii libhdb9-heimdal [heimdal-hdb-api-8] 1.6~rc2+dfsg-9 ii libkdc2-heimdal 1.6~rc2+dfsg-9 ii libkrb5-26-heimdal 1.6~rc2+dfsg-9 ii libldb1 2:1.1.17-2 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpopt0 1.16-10 ii libpython2.7 2.7.9-2 ii libroken18-heimdal 1.6~rc2+dfsg-9 ii libtalloc2 2.1.1-2 ii libtdb1 1.3.1-1 ii libtevent0 0.9.21-1 ii lsb-base 4.1+Debian13+nmu1 ii multiarch-support2.19-18 ii procps 2:3.3.9-9 ii python 2.7.9-1 ii python-dnspython 1.12.0-1 ii python-ntdb 1.0-5 ii python-samba 2:4.1.17+dfsg-2 pn python2.7:any ii samba-common
Bug#807964: marked as done ([python3-pafy] some videos dont works in mps-youtube, error says "javascript")
Your message dated Tue, 29 Dec 2015 23:38:00 + with message-id and subject line Bug#807964: fixed in pafy 0.3.80-1 has caused the Debian Bug report #807964, regarding [python3-pafy] some videos dont works in mps-youtube, error says "javascript" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 807964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-pafy Version: 0.3.78-1 Severity: normal Hello I'm in testing, now using: ii mps-youtube 0.2.5-5 ii python3-pafy0.3.78-1 With some videos mps-youtube has an error like in: https://github.com/mps-youtube/mps-youtube/issues/378 So, the problem is in the pafy version 0.3.78... We need the version 0.4.2 or newest for solve this... But I have test to "compile" a new pafy package with these sources and the final error is (it is not literal): no module youtube_dl... I have youtube-dl installed: youtube-dl 2015.11.27.1-1 but it is a python 2 program, and mps-youtube and pafy are python 3. I think that this is the problem and it not find the youtube_dl module... So, I think that this is hard to solve. The key is in this debian bugreport for youtube-dl, when it is requested to go to python 3: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723990 I'm not a developer, and I may be wrong, but if it is the case, you can tell to the youtube-dl maintainer to go to python 3... :-D Excuse my bad english. Many thanks for maintain this. Greetings. Martintxo. --- System information. --- Architecture: i386 Kernel: Linux 4.2.0-1-686-pae Debian Release: stretch/sid 500 testing-updates ftp.debian.org 500 testing security.debian.org 500 testing ftp.de.debian.org 10 testing www.deb-multimedia.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. Sustrai Erakuntza: respuesta jurídico-técnica a proyectos insostenibles. proiektu jasangaitzei erantzun juridiko-teknikoa. http://www.fundacionsustrai.org http://www.sustraierakuntza.org --- End Message --- --- Begin Message --- Source: pafy Source-Version: 0.3.80-1 We believe that the bug you reported is fixed in the latest version of pafy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 807...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Zlatan Todoric (supplier of updated pafy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 21 Dec 2015 03:28:25 +0100 Source: pafy Binary: python3-pafy Architecture: source all Version: 0.3.80-1 Distribution: unstable Urgency: low Maintainer: Zlatan Todoric Changed-By: Zlatan Todoric Description: python3-pafy - Download videos and retrieve metadata from YouTube Closes: 807964 Changes: pafy (0.3.80-1) unstable; urgency=low . * New upstream release (Closes: #807964) * debian/copyright: add jsinterp.py Checksums-Sha1: b09d5df5c7be44ac29a609d7871f0cfdc134bbec 1713 pafy_0.3.80-1.dsc ae8bdb78e9e749803b1ac8c8b414c83060914efa 56071 pafy_0.3.80.orig.tar.gz b63449aae86de33849d76894a89d1fb0bdd9ab48 4808 pafy_0.3.80-1.debian.tar.xz f6ba5271922839a3080e0a95ecfcc504a3ae82f6 26176 python3-pafy_0.3.80-1_all.deb Checksums-Sha256: b0e2b3dcfd9330b133fdfba18db1de456424d46f83247a067711b898d80f2661 1713 pafy_0.3.80-1.dsc 66f8e6cf0e590270e873f0be6dca3fc130b855de784c0dcb0bd7860a3c91 56071 pafy_0.3.80.orig.tar.gz 8b9c20d8522232c24413fba78b6426163f477c36f3477ca1199bd676228aaf5d 4808 pafy_0.3.80-1.debian.tar.xz 6fe04df9017c0404bf7b4552493deca012267013b46cd50ccddcb1694d05cc44 26176 python3-pafy_0.3.80-1_all.deb Files: 1a3599445495a147f8784441a154a71b 1713 python extra pafy_0.3.80-1.dsc c9c52c7fd23e2c488955cf1c30ed8026 56071 python extra pafy_0.3.80.orig.tar.gz cce11eae34cfb1c05457a61fd3b74d65 4808 python extra pafy_0.3.80-1.debian.tar.xz ea1104c393bdf3b5cabdbd5d1a3c05d3 26176 python extra python3-pafy_0.3.80-1_all.deb --
Bug#792178: marked as done (gunroar: please make the build reproducible)
Your message dated Tue, 29 Dec 2015 23:34:53 +
with message-id
and subject line Bug#792178: fixed in gunroar 0.15.dfsg1-8
has caused the Debian Bug report #792178,
regarding gunroar: please make the build reproducible
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
792178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792178
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gunroar
Version: 0.15.dfsg1-7
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: locale
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Hi!
While working on the "reproducible builds" effort [1], we have noticed
that gunroar could not be built reproducibly.
The order of source files varies depending on the locale.
The attached patch fixes this by setting LC_ALL to C before sorting.
Regards,
Reiner
[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/patches/makefile.patch b/debian/patches/makefile.patch
index 9bc724a..86c14f9 100644
--- a/debian/patches/makefile.patch
+++ b/debian/patches/makefile.patch
@@ -5,7 +5,7 @@
+++ b/Makefile
@@ -0,0 +1,11 @@
+GDC=gdc
-+DSRC=$(shell find import src/abagames -name "*.d" | sort)
++DSRC=$(shell find import src/abagames -name "*.d" | LC_ALL=C sort)
+EXE=gunroar
+
+all: $(EXE)
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gunroar
Source-Version: 0.15.dfsg1-8
We believe that the bug you reported is fixed in the latest version of
gunroar, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 792...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Markus Koschany (supplier of updated gunroar package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 29 Dec 2015 22:33:19 +0100
Source: gunroar
Binary: gunroar gunroar-data
Architecture: source
Version: 0.15.dfsg1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team
Changed-By: Markus Koschany
Description:
gunroar- 360-degree gunboat shooter
gunroar-data - 360-degree gunboat shooter - game data
Closes: 792178
Changes:
gunroar (0.15.dfsg1-8) unstable; urgency=medium
.
* Team upload.
* Declare compliance with Debian Policy 3.9.6.
* wrap-and-sort -sa.
* Vcs-Browser: Use https.
* gunroar.desktop: Add keywords and a comment in German.
* makefile.patch: Make the build reproducible by setting LC_ALL to C before
sorting.
Thanks to Reiner Herrmann for the report and patch. (Closes: #792178)
* gunroar-data: Remove superfluous ${shlibs:Depends} substvar.
* gunroar-data: Suggest gunroar.
Checksums-Sha1:
e4c770baf35c844150b7ec1225629d0f99cf269d 2352 gunroar_0.15.dfsg1-8.dsc
25c2cf93e45057cc8808ee6d77bed63f65bec09e 30040
gunroar_0.15.dfsg1-8.debian.tar.xz
Checksums-Sha256:
48d9d4588d572784d00d4803a2011ebcb78c736ce255fc1cb69d31d03bbf7df5 2352
gunroar_0.15.dfsg1-8.dsc
9833cde0a7186d3898c3919ec59c56bae8c0ad3d6686e1c112c3759a50190cb9 30040
gunroar_0.15.dfsg1-8.debian.tar.xz
Files:
de1b1192d5c3dd16c3e23dde9d342d17 2352 games extra gunroar_0.15.dfsg1-8.dsc
9c4977a602933e963ace26d50491ae78 30040 games extra
gunroar_0.15.dfsg1-8.debian.tar.xz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQJ8BAEBCgBmBQJWgwMbXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1HkbR8P/3b/ghRSrJSx8uHaXc1x//4z
H9BmqXlxqA/oLdzvFJhLvggcDn/4FHRWNEDv3H5wesSb+J9usr0QyJ6hJtNplG0/
t0eC1LJtItzpjb2FMpaxho7EHcuk9EDHMrcy747/2B+ttxGqvjLlmqCviDN0rpWc
BTvI8krm95pKMewQJfHWxKCynG1Qu5k7L5PW9B4jMkG5aMtLl21em29dEZjFTHQV
5wmcpE9sWc/VYhsCJiBZw7akdEwP3jKI8pZo/izGl5jWmny/yyFOI+1V1JgsgIrp
jfpm86qTbdWMX9yhyAaXytyowdpVWstplvTaiRsjcQxGX5rgfhkaZqoS0MLN8V/W
jxVSth0vp2xUnmx4z/1Up1gCXi9tqCMnBwZXIh3CQpcPfjSSRj3syT6gH+GnzU+u
JFYCC5R9nDXRT10/2+hHKKdy2o1yo4AyThdT6mKzT/jNyTYYsjG7xum6zANxVsKd
M7YzFGz/OIvu7rjI9NtvB6rllDmmDuBhENvrizYYOg9ZgoGRgrAa/ECiB7crDxn6
ZvvoxXbMYlyBONb58Z4uowKDjlGLY4yOJeu2b10PvK9UCIIXUr6cu+gf9th3WH0n
3uRGNGH9Us03LbxiSMU9rgCuxgm6YKXS8atB4BAv3uvl38qJqhf2pcoSQHG8CIHT
96hop
Bug#795945: marked as done (projectl: please make the build reproducible)
Your message dated Tue, 29 Dec 2015 23:38:57 + with message-id and subject line Bug#795945: fixed in projectl 1.001.dfsg1-8 has caused the Debian Bug report #795945, regarding projectl: please make the build reproducible to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 795945: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795945 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: projectl Version: 1.001.dfsg1-7 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: locale X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Hi! While working on the "reproducible builds" effort [1], we have noticed that projectl could not be built reproducibly. A file list is sorted with "sort", which behaves differently depending on the locale. The attached patch fixes this by sorting with LC_ALL set to C. Regards, Reiner [1]: https://wiki.debian.org/ReproducibleBuilds diff --git a/debian/patches/makefile.patch b/debian/patches/makefile.patch index 789a4c4..1d9cb0f 100644 --- a/debian/patches/makefile.patch +++ b/debian/patches/makefile.patch @@ -6,7 +6,7 @@ +++ b/Makefile @@ -0,0 +1,11 @@ +GDC=gdc -+DSRC=$(shell find import src -name "*.d" -not -iname '*mpeg*' | sort) ++DSRC=$(shell find import src -name "*.d" -not -iname '*mpeg*' | LC_ALL=C sort) +EXE=projectl + +all: $(EXE) signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: projectl Source-Version: 1.001.dfsg1-8 We believe that the bug you reported is fixed in the latest version of projectl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 795...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated projectl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 29 Dec 2015 23:21:40 +0100 Source: projectl Binary: projectl Architecture: source Version: 1.001.dfsg1-8 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Markus Koschany Description: projectl - sword action shooting Closes: 795945 Changes: projectl (1.001.dfsg1-8) unstable; urgency=medium . * Team upload. * Declare compliance with Debian Policy 3.9.6. * wrap-and-sort -sa. * Vcs-Browser: Use https. * projectl.desktop: Add keywords and a comment in German. * makefile.patch: Make the build reproducible by sorting with LC_ALL set to C. Thanks to Reiner Herrmann for the report and patch. (Closes: #795945) * Drop README.source because source format 3.0 uses quilt by default. Checksums-Sha1: a25640ce84c494a194b3602af5db47827808c287 2305 projectl_1.001.dfsg1-8.dsc 28154b3b884d20f8694623af0116aa00ea2b6646 32680 projectl_1.001.dfsg1-8.debian.tar.xz Checksums-Sha256: c63389ffdf4560485a6cc7f27cf560a2de9bfcaeff44c6dba315be1c7cdba335 2305 projectl_1.001.dfsg1-8.dsc 2d9216f1ae2eb65b763d7e9fc2a6a070a45b9e471e12b247a528eb738c58db51 32680 projectl_1.001.dfsg1-8.debian.tar.xz Files: dc994c84299777bc84908ccd2cef88e9 2305 games optional projectl_1.001.dfsg1-8.dsc 256b938d9605c7450d6cb9ae948b9447 32680 games optional projectl_1.001.dfsg1-8.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJWgwruXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1Hk/0gP/3/g2T/XqMQGqBAb/kIfXZ2g QSHMpBL6F/JvSa5pWdVxv2m8+w+CzJrKufymiqmogkrkGFEllN3lAhfvwPvrQ4Mh HQwvWg7azDSRJzbNQnu2ve0AoqbNdN+vWRBsEjDjBQh6WBecFrqVJUkU38qboTMX cunlvr095DN24GcMJvQ8fW502hkXlg5Hcz8V+MYb6HHSWAlhVwtvmoF3aCZ8JdXe ViajK0EwC2UjR/+JVTLNLiwy6q7D7eJjDrOnr841YMUBCM5R1jHpgJd6MPTeTQRA QhEVKFRGKya6B6TwjNaaOpnXwGZqsFWksRt1qcOOp6goxmF1wiwacKpiT15bsYnG Ciw7YkZbO28Svusqt7jdz+rqiIUfU/L9SB+Ai8zm5kOwhQcQwQAOIaabqWOR3/HJ wyG4pfoX4Of/m2ekUvaTs1CPZWICwAVZy9sHkFBgw5XVSi1C5oOcjHW6KTooZXBm bT2la2Lp7nxGepoU6elJbHh2xMCfh+EzEx519qv7eADTwFwQWlBRPYn5cm3TFl9U IpFC+xh/Zxce4e/+KBPQwyNwTYmTXb4ZfKYFGY+I90I6zCDrOK4L8/DoS9qJj/pH J/KEAeQAnRS8QyCbzrxJpXxAf75aH5NAFqJZ5jobEWCV0Y6lA2b8MjUlOW7hUAC6 O
Bug#799841: marked as done (Beta release of saods9 entered unstable)
Your message dated Tue, 29 Dec 2015 23:42:46 + with message-id and subject line Bug#799841: fixed in saods9 7.4+repack-1 has caused the Debian Bug report #799841, regarding Beta release of saods9 entered unstable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 799841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: saods9 Version: 7.4~b7+repack-3 Severity: Serious This package should not have gone to unstable. It shall not enter testing. --- End Message --- --- Begin Message --- Source: saods9 Source-Version: 7.4+repack-1 We believe that the bug you reported is fixed in the latest version of saods9, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 799...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated saods9 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 29 Dec 2015 22:20:42 +0100 Source: saods9 Binary: saods9 tksao saods9-tclpackages saods9-doc Architecture: source Version: 7.4+repack-1 Distribution: unstable Urgency: low Maintainer: Debian Astronomy Maintainers Changed-By: Ole Streicher Description: saods9 - Image display tool for astronomy saods9-doc - Image display tool for astronomy (help files/documentation) saods9-tclpackages - Tcl/Tk packages provided with DS9 tksao - Tk widgets for astronomical imaging and data visualization Closes: 799841 Changes: saods9 (7.4+repack-1) unstable; urgency=low . * New stable upstream version. Closes: #799841 Checksums-Sha1: 0786196203c9810d386d4bf0cf93df9562e7fbd6 2457 saods9_7.4+repack-1.dsc 05c84756c2f502a945e5b432fe25d019b21816bf 9031863 saods9_7.4+repack.orig.tar.gz e47460e22c60103b02c3fbb93a8be6b12505f7a2 21676 saods9_7.4+repack-1.debian.tar.xz Checksums-Sha256: 1efc8152f846932cdbd9490c40fe2fefb3640deee7e784818782a3cac88a2a11 2457 saods9_7.4+repack-1.dsc 1a5dc0132b11d1dae8be09430f7cc975cfbe65e8b8033e921e7cb7db6c8c2cad 9031863 saods9_7.4+repack.orig.tar.gz 0282ba4325953390d4c2e2525c78633597115a8d2d8e81a71b297993f650 21676 saods9_7.4+repack-1.debian.tar.xz Files: 8c2e1d3352c1a0d036bb9fdd14029123 2457 science optional saods9_7.4+repack-1.dsc 21eb8710aae44741aaa0199f76b639c7 9031863 science optional saods9_7.4+repack.orig.tar.gz 5a4ade30b0efd8039f57ae3a5d1a5fe6 21676 science optional saods9_7.4+repack-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJWgvvZAAoJEHEVr9B3ENz3wFAQAMlPf52kEUmfECIRHVz/KbK3 uJ1gV3ae8i9dBqpWY+dUKy4NTisKj21oqBFiDHdgJ38RqgjXDv0JjgacOT4Z4swA 9vge5BkbXbdfcjhnEMcTJzSUDohIhsew4w9n35N3B8ul08RCBygWVMnWKCGm3NuJ wqHxNgobFNCmm/Fsf04CnyRqXRQq0ohv05SoZKtjoAn2osi1It1jLrXfvvW8marG DtF1RBf7HplfTF+XW9/4uRGUlCaQ1LVa4Pe6nQENmMPvptkO8IrG2NZaLSy/Pu4I R79dBiEFiQkbkoOwD6Q8yeF7fI738UtrkkoKuYOvmUoCvgqjsDhDYyv8pCbhiMCF pkiSnutTg9HkDWvgt1+GRWL5KAcw+0INvSudQSy9XeCrMqg5kj7b8AH+wqy0ohvT JU+fFnrH3FqgnTJxzMg5cB3JHhuK3HrWmrfLDDZt9opgzknrSmLk5CP0mk6ugGdV pESAyXb1z6qgLjwQgRILFTP09lLsZJoBkgNWKm2FKmYdg0D48GzcUSMaznn60bAI YwAysSfmOVRhdD1LoHb49yW3UNJxOJjlK+kq2zzcyKMhgY08fhAR3COAw+Vam9kM TXhlnC3k5vxpsHuhJQr0JBBRMZf+vWc5ZaitslLfZZL1+5AxuHy8MDuOlE8IYjA3 oOUEedPoE1+Ijc6+5L0h =YS/X -END PGP SIGNATURE End Message ---
Bug#806858: marked as done (s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied)
Your message dated Tue, 29 Dec 2015 23:42:36 + with message-id and subject line Bug#806858: fixed in s-nail 14.8.5-5 has caused the Debian Bug report #806858, regarding s-nail: mailx: Unable to (dot) lock mailbox, aborting operation: Permission denied to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 806858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: s-nail Version: 14.8.5-3 Severity: normal Dear Maintainer, trying to read local mails in /var/mail with mailx fails with output as follows: Creating dotlock for "/var/mail/" . Unable to (dot) lock mailbox, aborting operation: Permission denied Creating dotlock for "/var/mail/" . Unable to (dot) lock mailbox, aborting operation: Permission denied (where I replaced the user name with ""). Any ideas? Regards, jvp. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0 (SMP w/2 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages s-nail depends on: ii base-files9.5 ii libc6 2.21-1 ii libcomerr21.42.13-1 ii libgssapi-krb5-2 1.13.2+dfsg-4 ii libidn11 1.32-3 ii libk5crypto3 1.13.2+dfsg-4 ii libkrb5-3 1.13.2+dfsg-4 ii libssl1.0.2 1.0.2d-3 ii libtinfo5 6.0+20151024-2 s-nail recommends no packages. Versions of packages s-nail suggests: ii exim4-daemon-light [mail-transport-agent] 4.86-7 -- no debconf information --- End Message --- --- Begin Message --- Source: s-nail Source-Version: 14.8.5-5 We believe that the bug you reported is fixed in the latest version of s-nail, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 806...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen (supplier of updated s-nail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Dec 2015 22:18:54 +0100 Source: s-nail Binary: s-nail heirloom-mailx Architecture: source Version: 14.8.5-5 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen Changed-By: Hilko Bengen Description: heirloom-mailx - feature-rich BSD mail(1) -- transitional package s-nail - feature-rich BSD mail(1) Closes: 806858 Changes: s-nail (14.8.5-5) unstable; urgency=medium . * Install s-nail-privsep setuid root (Closes: #806858) Checksums-Sha1: f80d374bba455b5628709edc964a573a36d395f8 1980 s-nail_14.8.5-5.dsc a29a3c37f9a317bcaf6c561ea1752e94a99b0bd8 9612 s-nail_14.8.5-5.debian.tar.xz Checksums-Sha256: 562ff358393406714731fb5b50cd888a7cf056aecdd020e016c0d96f6d2e12fb 1980 s-nail_14.8.5-5.dsc 54466bdf25ef4c299d2a1433fb2fb8a1c1824981ed68bedcdd019e3c508f4fde 9612 s-nail_14.8.5-5.debian.tar.xz Files: 336b37ecf4d6f921203b33cb18aa887d 1980 mail optional s-nail_14.8.5-5.dsc a82473d676dcde538dc994ee78f6f69f 9612 mail optional s-nail_14.8.5-5.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWgwOKAAoJEHW3EGNcITp+9hEP/1k6yZQKvq8VRWixWbSbmC6Q Y8yxWAylNnjt2DRHRR+enBUl13FeLbzYShY6uP12/CU6xX2qBa8VG61DWMKCqRZG EicYCWj0s3awM1PiDAkirPy0O5/NXy4heT8dH+H7lrXxatKbpH49qRh1hRE4IufM 9oucRxTtIZc5930qegxUWmvVE2iRo2xA8SMkJPVCOsHlz6Td3gPdlLiidlLBSIx5 b6nqFQP7SjPa9ZHNDuGMd/WIAUa6nUG64nypAIbwu8Rv+sjSbWNCBJOzknfeK5aJ ZFUfBojwqyEGNdj9G+FzMxPVkvEiaT9DpBKjSRBKOh9jcDmq3C9zLkiAaAbPzveV btfTYM0XMJ28PAMAPid9ggolgNr3ybz8IJWwwik/F3s9fApzEX6KAlJQW/72yYgF yVCU8YsAzdAlkqS7KVxFP5CW7gSx3YeQHRs3fBsuslCb3rqKNixA6yR7YABu89c9 XQ20ejOVl7UYNcyvQ9h9RvMZzXl8FOr/julj04VJESez92tbDlvAFCQ0SeAM6vlk G6dHl3uFUTGT5uV5LGtunGNqUSabQPp/PtyObT2kMDyjuqmC3sQcJBrfvh3fiKN1 QHciI5aM0e6Uqnp2qLqDGGWwYgsx55T1HSGff6Gzqrl/IyYpe6JDn424wDjSItyd eH5d3idpjxXRt8eDWyFj =zIGX -END PGP SIGNATURE End Message ---
Bug#809291: marked as done (sleekxmpp: FTBFS: ImportError: No module named thirdparty.statemachine)
Your message dated Tue, 29 Dec 2015 23:42:54 +
with message-id
and subject line Bug#809291: fixed in sleekxmpp 1.3.1-3
has caused the Debian Bug report #809291,
regarding sleekxmpp: FTBFS: ImportError: No module named thirdparty.statemachine
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
809291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sleekxmpp
Version: 1.3.1-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
sleekxmpp fails to build from source in unstable/amd64:
[..]
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py clean
Traceback (most recent call last):
File "setup.py", line 19, in
from sleekxmpp.version import __version__
File
"/home/lamby/temp/cdt.20151229004944.Gui5ulWWiP/sleekxmpp-1.3.1/sleekxmpp/__init__.py",
line 20, in
from sleekxmpp.stanza import Message, Presence, Iq
File
"/home/lamby/temp/cdt.20151229004944.Gui5ulWWiP/sleekxmpp-1.3.1/sleekxmpp/stanza/__init__.py",
line 10, in
from sleekxmpp.stanza.error import Error
File
"/home/lamby/temp/cdt.20151229004944.Gui5ulWWiP/sleekxmpp-1.3.1/sleekxmpp/stanza/error.py",
line 9, in
from sleekxmpp.xmlstream import ElementBase, ET
File
"/home/lamby/temp/cdt.20151229004944.Gui5ulWWiP/sleekxmpp-1.3.1/sleekxmpp/xmlstream/__init__.py",
line 14, in
from sleekxmpp.xmlstream.xmlstream import XMLStream, RESPONSE_TIMEOUT
File
"/home/lamby/temp/cdt.20151229004944.Gui5ulWWiP/sleekxmpp-1.3.1/sleekxmpp/xmlstream/xmlstream.py",
line 35, in
from sleekxmpp.thirdparty.statemachine import StateMachine
ImportError: No module named thirdparty.statemachine
E: pybuild pybuild:274: clean: plugin distutils failed with: exit code=1:
python2.7 setup.py clean
dh_auto_clean: pybuild --clean -i python{version} -p 2.7 --dir . returned
exit code 13
debian/rules:8: recipe for target 'clean' failed
make: *** [clean] Error 25
[..]
The full build log is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
sleekxmpp.1.3.1-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: sleekxmpp
Source-Version: 1.3.1-3
We believe that the bug you reported is fixed in the latest version of
sleekxmpp, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 809...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
W. Martin Borgert (supplier of updated sleekxmpp package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 29 Dec 2015 21:36:59 +
Source: sleekxmpp
Binary: python-sleekxmpp python3-sleekxmpp
Architecture: source all
Version: 1.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: W. Martin Borgert
Description:
python-sleekxmpp - Python XMPP (Jabber) Library Implementing Everything as a
Plugin
python3-sleekxmpp - Python XMPP (Jabber) Library Implementing Everything as a
Plugin
Closes: 809291
Changes:
sleekxmpp (1.3.1-3) unstable; urgency=medium
.
* Leave thirdparty/__init__.py (Closes: #809291). Thanks to Chris Lamb.
Checksums-Sha1:
b37a76628ca2df48a1b862efb0c0fcf0c3b029cf 2196 sleekxmpp_1.3.1-3.dsc
0b210c79ba2e0cba61b24dba365131ac9605e66f 21704 sleekxmpp_1.3.1-3.debian.tar.xz
eb1687e152fa8cd76169ad456720e380cf881d32 196850
python-sleekxmpp_1.3.1-3_all.deb
7f15d6b8676dae75f6592ad4e0bdbb33b518a6d8 196970
python3-sleekxmpp_1.3.1-3_all.deb
Checksums-Sha256:
f93d232dc561a9925309e16497fbc9989c5b2fad2664ddc711e0556ae37350c4 2196
sleekxmpp_1.3.1-3.dsc
9e6f56605016d4610c1e1fb1b6e10fa597b139b9838ef92ae0d8d1ff37f4f440 21704
sleekxmpp_1.3.1-3.debian.tar.xz
86804538af21e9ec49bab01070fe2dcd453df17e93773765d957d347f93913b7 196850
python-sleekxmpp_1.3.1-3
Bug#809160: marked as done (apt: [doc] apt.conf(5) man page (file apt.conf.5.xml in source) possible minor mistakes)
Your message dated Wed, 30 Dec 2015 00:18:49 + with message-id and subject line Bug#809160: fixed in apt 1.1.10 has caused the Debian Bug report #809160, regarding apt: [doc] apt.conf(5) man page (file apt.conf.5.xml in source) possible minor mistakes to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809160 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apt Version: 1.1.8 Severity: minor Hi! in the apt.conf(5) man page[1] I think there are a couple of minor mistakes. In the paragraph «The value should be a normal URI to a text file, expect that package specific data is replaced with the placeholder @CHANGEPATH@. The value for it is: 1. if the package is from a component (e.g. main) this is the first part otherwise it is omitted, 2. the first letter of source package name, expect if the source package name starts with 'lib' in which case it will be the first four letters. 3. The complete source package name. 4. the complete name again and 5. the source version.» I think both occurrence of "expect" should be instead "except". Afterwards in the same page there is: «Package action lines consist of five fields in Version 2: old version, direction of version change (< for upgrades, > for downgrades, = for no change), new version, action.» Unless I am missing something those are only 4 fields, not 5 (1 old version, 2 direction of change, 3 new version, 4 action). (Maybe it was related to Version 3 with the Multiarch field too??, just a thought, I am not sure). Very shortly after that there is a quote missing (the opening quote for the type "foreign" in «In Version 3 after each version field follows the architecture of this version, which is "-" if there is no version, and a field showing the MultiArch type "same", foreign", "allowed" or "none".» I hope I am not wasting your time. Thanks, beatrice [1] I checked the last xml source version here here http://sources.debian.net/src/apt/1.1.8/doc/apt.conf.5.xml/ --- End Message --- --- Begin Message --- Source: apt Source-Version: 1.1.10 We believe that the bug you reported is fixed in the latest version of apt, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julian Andres Klode (supplier of updated apt package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 30 Dec 2015 00:40:53 +0100 Source: apt Binary: apt libapt-pkg5.0 libapt-inst2.0 apt-doc libapt-pkg-dev libapt-pkg-doc apt-utils apt-transport-https Architecture: source Version: 1.1.10 Distribution: unstable Urgency: medium Maintainer: APT Development Team Changed-By: Julian Andres Klode Description: apt- commandline package manager apt-doc- documentation for APT apt-transport-https - https download transport for APT apt-utils - package management related utility programs libapt-inst2.0 - deb package format runtime library libapt-pkg-dev - development files for APT's libapt-pkg and libapt-inst libapt-pkg-doc - documentation for APT development libapt-pkg5.0 - package management runtime library Closes: 808102 809160 Changes: apt (1.1.10) unstable; urgency=medium . [ David Kalnischkies ] * deal with empty values properly in deb822 parser (Closes: 808102) . [ Beatrice Torracca ] * fix 3 typos/omissions in apt.conf(5) (Closes: 809160) . [ Julian Andres Klode ] * BufferedWriter: flushing: Check for written < size instead of <= * aptconfiguration: Set default compression level to 6 * BufferedFileFdPrivate: Make InternalFlush() save against errors * Switch to DJB hashing and use prime number as table size * Turn tolower_ascii() and isspace_ascii() into inline functions * Fix test case that was broken by switch of hash function * pkgTagSection::Scan: Fix read of uninitialized value * pkgCacheGenerator: Allow passing down an already created cache * A
Bug#808102: marked as done (apt: `apt-cache policy` does not find package listed in `/var/lib/dpkg/status`)
Your message dated Wed, 30 Dec 2015 00:18:49 + with message-id and subject line Bug#808102: fixed in apt 1.1.10 has caused the Debian Bug report #808102, regarding apt: `apt-cache policy` does not find package listed in `/var/lib/dpkg/status` to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 808102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt Version: 1.1.5 Severity: important Dear Maintainer, I was installing upgrades the other day and everything appeared to work correctly. Then I went to manually install a package and `apt` said that there were missing dependencies and I needed to run `apt-get install -f` to fix them. I did this, but the problem persisted. Digging into it more, I found that `evince` depends on `libevdocument3-4`. Both of these are installed according to `dpkg -l` and both are present in `/var/lib/dpkg/status` However, `apt-cache policy libevdocument3-4` said the file was not installed. After trying multiple things, I found that if I moved `libevdocument3-4` up next to `evince` in `/var/lib/dpkg/status`, then everything worked correctly. I just ran `apt-get upgrade` and now it is telling me: apt-get install Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: gir1.2-gnomebluetooth-1.0 : Depends: libgnome-bluetooth13 (>= 3.12.0) but it is not installed gnome-bluetooth : Depends: libgnome-bluetooth13 (>= 3.12.0) but it is not installed gnome-control-center : Depends: libgnome-bluetooth13 (>= 3.12.0) but it is not installed E: Unmet dependencies. Try using -f. So this seems to be a broader issue where if I fix one thing then another breaks. `libgnome-bluetooth13` is installed and present in `/var/lib/dpkg/status`. -- Wayne Rowcliffe -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "1"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-4\.1\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-image-4\.2\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-headers-4\.1\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-headers-4\.2\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-4\.1\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-4\.2\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-4\.1\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-4\.2\.0-1-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-image-4\.1\.0-2-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-image-4\.2\.0-1-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-headers-4\.1\.0-2-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-headers-4\.2\.0-1-amd64$"; APT::NeverAutoRemove:: "^gnumach-image-4\.1\.0-2-amd64$"; APT::NeverAutoRemove:: "^gnumach-image-4\.2\.0-1-amd64$"; APT::NeverAutoRemove:: "^.*-modules-4\.1\.0-2-amd64$"; APT::NeverAutoRemove:: "^.*-modules-4\.2\.0-1-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-4\.1\.0-2-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-4\.2\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.1\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.2\.0-1-amd64$"; APT::NeverAutoRemove:: "^linux-tools-4\.1\.0-2-amd64$"; APT::NeverAutoRemove:: "^linux-tools-4\.2\.0-1-amd64$"; APT::NeverAutoRemove:: "^postgresql-"; 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::VersionedKernelPackag
Bug#809296: marked as done (wbar-config in same package garbles the config file.)
Your message dated Wed, 30 Dec 2015 01:04:59 + with message-id and subject line Bug#809296: fixed in wbar 2.3.4-5 has caused the Debian Bug report #809296, regarding wbar-config in same package garbles the config file. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wbar Version: 2.3.4-4 Severity: normal Making changes to the wbar configuration using wbar-config garbles the second line of the $HOME/.wbar file which normally contains the parameters to wbar. Running wbar after that places the wbar image in a seemingly arbitrary manner on the screen. I haven't run wbar for sometime and this behavior just started so it might be changes in one of the other libraries wbar depands on. Just a guess. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 4.3.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages wbar depends on: ii libc6 2.21-6 ii libgcc1 1:5.3.1-4 ii libimlib2 1.4.7-1+b1 ii libstdc++6 5.3.1-4 ii libx11-62:1.6.3-1 Versions of packages wbar recommends: ii fonts-liberation 1.07.4-1 pn lxde-icon-theme Versions of packages wbar suggests: ii bash-completion 1:2.1-4.2 ii wbar-config 2.3.4-4 -- Configuration Files: /etc/xdg/autostart/wbar.desktop [Errno 2] No such file or directory: u'/etc/xdg/autostart/wbar.desktop' -- no debconf information --- End Message --- --- Begin Message --- Source: wbar Source-Version: 2.3.4-5 We believe that the bug you reported is fixed in the latest version of wbar, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated wbar package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 30 Dec 2015 01:14:36 +0100 Source: wbar Binary: wbar wbar-config Architecture: source Version: 2.3.4-5 Distribution: unstable Urgency: medium Maintainer: Markus Koschany Changed-By: Markus Koschany Description: wbar - light and fast launch bar wbar-config - GUI tool to configure wbar Closes: 809296 Changes: wbar (2.3.4-5) unstable; urgency=medium . * Drop clang-FTBFS.patch. Reopen #741741 again, because the clang-FTBFS.patch was incomplete and caused a regression when using wbar-config. Thanks to Frank McCormick for the report. (Closes: #809296) Checksums-Sha1: 4302c334d09cb90a65813d67c1cda443eaa1d5c6 2075 wbar_2.3.4-5.dsc 4af14efc74e089e36485368eb0424d5d4322ea1b 7752 wbar_2.3.4-5.debian.tar.xz Checksums-Sha256: 81dc54e2e8061748c69bc3e76da14e5a6f2d354174b4879fae9a54d4dc8271b4 2075 wbar_2.3.4-5.dsc 516b28fac5784a5912d1df3b9f154a1cc9724ceb4b496d94b2916fd125f3abc9 7752 wbar_2.3.4-5.debian.tar.xz Files: 534a2c3234336f70f98c5678736ff8a9 2075 x11 optional wbar_2.3.4-5.dsc 124fa33d34b0e0d111e6d536338a2333 7752 x11 optional wbar_2.3.4-5.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJWgyRXXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1HkoQgP/1WK030Im8M0UNY8ileNqu62 VDKiqI39vXh0YK9AUKYweXOGvySkGun+85G3h7+gsKejChYhBZh4mq2xR2ls3IFW u6uQ6dy8XQTBO2MbX2ec7gOC6OSkXinrUNr7Y7x4BtrDApQCUanyEDZggvO6qQ/8 dVCWsuG0Qo1xRwTWlmvFD6jFBFQWYvbJxm5IwoUUQc4RrsNoIJiBVAnf2NnYsJqp No6TjdQ08ribKUfqaWJp4mG2fGfp6jn0krQkJ1Me7KzfTH/YuMRNqDuZwAJOoctF SIJJkIBDUifLUmmAAk6aQMo+TbyiNOuC5IXcGHXwGfZo3Zi5AS7AiYoS14sRyvX3 QNwZtNYQRdOHDOV2dxOZXJKmsQZWoOr/xltaRf1au94Nwm11JO2U6qH6tgxvRC4g M4ELW20Si97ZaYqu0hG31ZjijHIlaJ2xkylQudax7JeSGyGJul5wYLuAx2Ij/jSb wq7nVTpiv0x+zC+wwVNwCgrZZwscSPkj/CsTd+ciUEPpUF3gNkeZjfPBbGAvKovk VLGjMDMEMiSaA4z7Fy+yvpDlfKuxh6SRZk4BxJ/h4bhYB6REoPWY8wEAQ61RaQKZ stra5atbK5/ck0mA24/NG2Cb+51cI9IM2LYTm/ZfH0GqDHdpm24uhzOIG5c6
Bug#809378: marked as done (linux-libc-dev missing direct rendering manager headers)
Your message dated Wed, 30 Dec 2015 01:53:08 + with message-id <1451440388.25978.65.ca...@decadent.org.uk> and subject line Re: Bug#809378: linux-libc-dev missing direct rendering manager headers has caused the Debian Bug report #809378, regarding linux-libc-dev missing direct rendering manager headers to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-libc-dev Version: 3.16.7-ckt20-1+deb8u1 Severity: normal Dear Maintainer, I wanted to write some C code to learn the Direct Rendering Manager interface, without using libdrm. Googling found me this tutorial [1]. I didn't get very far because I was missing . "Userspace headers from the Linux kernel" are both provided by linux-libc-dev and present in the include/uapi directory of the linux-headers of /usr/src. My /usr/src/linux-headers-3.16.../include/uapi has nine directories: asm-generic, drm, linux, mtd, rdma, scsi, sound, video, and xen. All of these except drm and scsi are in linux-libc-dev, and libc6 has scsi. Extensive googling has led me to believe that no Debian package other than the linux-headers has the drm headers, and none have them in /usr/include. It seems like this package should include the drm headers. Thank you for your consideration. [1]: http://betteros.org/tut/graphics1.php#dumb [2]: https://web.archive.org/web/20150815051638/http://betteros.org/tut/graphics1.php -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information --- End Message --- --- Begin Message --- On Wed, 2015-12-30 at 01:44 +0100, Nebuchadnezzar III wrote: > Package: linux-libc-dev > Version: 3.16.7-ckt20-1+deb8u1 > Severity: normal > > Dear Maintainer, > > I wanted to write some C code to learn the Direct Rendering Manager interface, > without using libdrm. Googling found me this tutorial [1]. I didn't get very > far > because I was missing . "Userspace headers from the Linux kernel" are > both provided by linux-libc-dev and present in the include/uapi directory of > the > linux-headers of /usr/src. My /usr/src/linux-headers-3.16.../include/uapi has > nine directories: asm-generic, drm, linux, mtd, rdma, scsi, sound, video, and > xen. All of these except drm and scsi are in linux-libc-dev, and libc6 has > scsi. > Extensive googling has led me to believe that no Debian package other than the > linux-headers has the drm headers, and none have them in /usr/include. It > seems > like this package should include the drm headers. > > Thank you for your consideration. > > [1]: http://betteros.org/tut/graphics1.php#dumb > [2]: > https://web.archive.org/web/20150815051638/http://betteros.org/tut/graphics1.php You want libdrm-dev. Ben. -- Ben Hutchings This sentence contradicts itself - no actually it doesn't. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#804196: marked as done (midori gets bad results from https://www.howsmyssl.com/)
Your message dated Wed, 30 Dec 2015 03:36:01 +
with message-id
and subject line Bug#804196: fixed in midori 0.5.11-ds1-1
has caused the Debian Bug report #804196,
regarding midori gets bad results from https://www.howsmyssl.com/
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
804196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: midori
Version: 0.5.11-2
Severity: wishlist
"Bad" results from https://www.howsmyssl.com/ . Need to improve security.
--- End Message ---
--- Begin Message ---
Source: midori
Source-Version: 0.5.11-ds1-1
We believe that the bug you reported is fixed in the latest version of
midori, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 804...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sergio Durigan Junior (supplier of updated midori
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 27 Dec 2015 16:12:18 -0500
Source: midori
Binary: midori midori-dbg
Architecture: source amd64
Version: 0.5.11-ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Sergio Durigan Junior
Changed-By: Sergio Durigan Junior
Description:
midori - fast, lightweight graphical web browser
midori-dbg - fast, lightweight graphical web browser (debug symbols)
Closes: 799963 804196 805457
Changes:
midori (0.5.11-ds1-1) unstable; urgency=medium
.
* Rename package (and source tarball) in order to fix a mistake that
happened when uploading the first version of the "0.5.11" version.
Somehow, the source tarball was different than the original tarball.
Fortunately, the only difference were the timestamps.
* Update version of Chromium's User-Agent string.
We identify ourselves as Chromium to other websites, but the version
we use in the User-Agent string is pretty old. This commit updates it
to a newer version (49.0.2571.2, from Nov 22 2015). The positive
side-effect from doing this is that Google does not bother the user
asking her to upgrade to a "newer Chrome". (Closes: #805457)
* Convert patch add-debian-searches to gbp-pq.
Trivial adjustment on add-debian-searches in order to make it
compliant with gbp-pq.
* Better handling of self-signed certificates.
Midori needs gcr/gnome-keyring in order to fully work with self-signed
TLS certificates. This commit improves the error message that is
displayed when clicking on "Trust this website" does not work, and
also makes the Debian Midori package recommend installing
gnome-keyring. This is the best we can do for now. (Closes: #799963)
* Improve security by making sure that we use a safe set of ciphers.
This comes from Debian bug #804196 (LP Bug #1517265). When Midori
uses libwebkitgtk, it inherits the default value of the
G_TLS_GNUTLS_PRIORITY environment variable. Unfortunately this value
is not safe enough because it still lets GnuTLS to enable to unsafe
ciphers. Therefore, we need to set this variable ourselves and make
sure that Midori is using safe ciphers for TLS operations. (Closes:
#804196)
* Override "source-is-missing data/autosuggestcontrol.js"
Lintian is wrongly reporting a "source-is-missing" error for
data/autosuggestcontrol.js. I have reported a bug against it (809170)
and now I am overriding the error.
* Fix Vcs-* URLs.
The package was still using old, non-canonical URLs for
Vcs-{Git,Browser}. Update them now.
* Remove midori.menu (and solve lintian warning)
Lintian was warning "command-in-menu-file-and-desktop-file". Since
Midori already ships a .desktop file, it is time to remove the
midori.menu file from the package.
Checksums-Sha1:
5f560ff8f22812edaeab71be1f29f94b6880d6cc 2263 midori_0.5.11-ds1-1.dsc
64c86935028feb5f89d799c2acacaad67764da6f 1428791 midori_0.5.11-ds1.orig.tar.bz2
e09696f45b901a29ba525c169a9bc47eba20eafd 17896
midori_0.5.11-ds1-1.debian.tar.xz
431e1772
Bug#799963: marked as done (Improve warning message when gnome-keyring is not running (and self-signed cert cannot be trusted))
Your message dated Wed, 30 Dec 2015 03:36:00 + with message-id and subject line Bug#799963: fixed in midori 0.5.11-ds1-1 has caused the Debian Bug report #799963, regarding Improve warning message when gnome-keyring is not running (and self-signed cert cannot be trusted) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 799963: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: midori Version: 0.5.11-2 Hello, midori 0.5.11-2 (running on current unstable, desktop environment is XFCE) shows problems with accepting a self-signed certificate for https connections. When trying to open an https-URL that uses a self-signed certificate, the following message gets displayed: "Security unknown The signing certificate authority is not known." So far everything is ok, but pressing the "Trust this website" button results in "Error granting trust: Couldn't find a place to store the pinned certificate pkcs11:library-manufacturer=GNOME%20Keyring , pkcs11:library-description=PKCS%2311%20Kit%20Trust%20Module" Regards, Karsten -- Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der Werbung sowie der Markt- oder Meinungsforschung. --- End Message --- --- Begin Message --- Source: midori Source-Version: 0.5.11-ds1-1 We believe that the bug you reported is fixed in the latest version of midori, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 799...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sergio Durigan Junior (supplier of updated midori package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 27 Dec 2015 16:12:18 -0500 Source: midori Binary: midori midori-dbg Architecture: source amd64 Version: 0.5.11-ds1-1 Distribution: unstable Urgency: medium Maintainer: Sergio Durigan Junior Changed-By: Sergio Durigan Junior Description: midori - fast, lightweight graphical web browser midori-dbg - fast, lightweight graphical web browser (debug symbols) Closes: 799963 804196 805457 Changes: midori (0.5.11-ds1-1) unstable; urgency=medium . * Rename package (and source tarball) in order to fix a mistake that happened when uploading the first version of the "0.5.11" version. Somehow, the source tarball was different than the original tarball. Fortunately, the only difference were the timestamps. * Update version of Chromium's User-Agent string. We identify ourselves as Chromium to other websites, but the version we use in the User-Agent string is pretty old. This commit updates it to a newer version (49.0.2571.2, from Nov 22 2015). The positive side-effect from doing this is that Google does not bother the user asking her to upgrade to a "newer Chrome". (Closes: #805457) * Convert patch add-debian-searches to gbp-pq. Trivial adjustment on add-debian-searches in order to make it compliant with gbp-pq. * Better handling of self-signed certificates. Midori needs gcr/gnome-keyring in order to fully work with self-signed TLS certificates. This commit improves the error message that is displayed when clicking on "Trust this website" does not work, and also makes the Debian Midori package recommend installing gnome-keyring. This is the best we can do for now. (Closes: #799963) * Improve security by making sure that we use a safe set of ciphers. This comes from Debian bug #804196 (LP Bug #1517265). When Midori uses libwebkitgtk, it inherits the default value of the G_TLS_GNUTLS_PRIORITY environment variable. Unfortunately this value is not safe enough because it still lets GnuTLS to enable to unsafe ciphers. Therefore, we need to set this variable ourselves and make sure that Midori is using safe ciphers for TLS operations. (Closes: #804196) * Override "source-is-missing data/autosuggestcontrol.js" Lintian is wrongly reporting a "
Bug#809360: marked as done (liblwp-useragent-chicaching-perl: Should be arch: all, not arch: any)
Your message dated Wed, 30 Dec 2015 03:35:37 + with message-id and subject line Bug#809360: fixed in liblwp-useragent-chicaching-perl 0.03-2 has caused the Debian Bug report #809360, regarding liblwp-useragent-chicaching-perl: Should be arch: all, not arch: any to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: liblwp-useragent-chicaching-perl Version: 0.03-1 Severity: normal Dear Maintainer, This is a pure-perl module, so it should be Architecture: all, not Architecture: any, which wastes buildd capacity and archive space. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: liblwp-useragent-chicaching-perl Source-Version: 0.03-2 We believe that the bug you reported is fixed in the latest version of liblwp-useragent-chicaching-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated liblwp-useragent-chicaching-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 30 Dec 2015 08:21:18 +0530 Source: liblwp-useragent-chicaching-perl Binary: liblwp-useragent-chicaching-perl Architecture: source all Version: 0.03-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Jonas Smedegaard Description: liblwp-useragent-chicaching-perl - LWP::UserAgent with caching based on CHI Closes: 809360 Changes: liblwp-useragent-chicaching-perl (0.03-2) unstable; urgency=medium . * Fix build package as arch-dependent. Closes: Bug#809360. Thanks to Dagfinn Ilmari Mannsåker. Checksums-Sha1: 2b874cce9f9612a5ab31189e6993c0548fbe6bae 2389 liblwp-useragent-chicaching-perl_0.03-2.dsc 7a08b1e2f442926f8f42865b03bc9088c333a488 3204 liblwp-useragent-chicaching-perl_0.03-2.debian.tar.xz be641b8c1da56ca4c12a80dd37d604b6400e50d1 22722 liblwp-useragent-chicaching-perl_0.03-2_all.deb Checksums-Sha256: 81b6fdeabe9043141328253b1e569c8ecc69817a065cdc1875951df54e82dff4 2389 liblwp-useragent-chicaching-perl_0.03-2.dsc 48f1e796e098e2e39f01bc324a365905c9bae37575e3b020788251bbd770b992 3204 liblwp-useragent-chicaching-perl_0.03-2.debian.tar.xz 73fc52f1c3c31819c9bc7850c029c73152e651668f3cad943caf1859c05f6b80 22722 liblwp-useragent-chicaching-perl_0.03-2_all.deb Files: 15b91f31c65b82c6b76978b8a6ef9286 2389 perl optional liblwp-useragent-chicaching-perl_0.03-2.dsc fa9de1087c4726b32b14ec47127fbec8 3204 perl optional liblwp-useragent-chicaching-perl_0.03-2.debian.tar.xz 96ad08debfb4e68eb14b7482bf0804ee 22722 perl optional liblwp-useragent-chicaching-perl_0.03-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWg0e5AAoJECx8MUbBoAEhQhwQAIvRZX90vXJ/XebqzyHo8e+Q NxNyPwRYwMeJuqmSQuBbLzMtlQqz6k3lwEMOLASVTRpt6TYpio6w7CNMT2X33vuk MAnPcGQVxZefGd65IsLQDyA5GSSl6NPZIzzo5CrG357mUxn5GHmyf8SXPOiueiIF 7wEoxdQccTLAW+vtGjPe0fBpZ5L2uioN9WMwaOhdRbFuqIrt2LtZsMb/2ve1s6xV C68ussJRFxk8l2PKj+m3EdCjyJHeCzR0YPwqKyTSWztrAnB/+GuKdR6aK2V66q97 UXrKHuBu0Y/fwREsydUBNJoV8Iz1Ydzwk1hiHnlzMNeVkfHjookFT99WvWE0CH5c oElj+g+B2Yioe9MhUrqERcKPM2feUZyQsqDHBB+6XBYBzXzKk49y3pcZdYn5aqWt Gm9ezL3srYv9Sr903Vzto2gnVYRLtxIY3frZ1Gz321fI3HQ7HY+S/94DitCW+zWr TqqdDXKrPjYSHxHl1VIgVW9mUTIYwINRH95SS4hUucRyyq1ZQnGit6HtiEagMfmz 7Ma1ig521Isc6A9oAtkYimpqo9/EM5u26j070ACaSdwOhTITpsAtj2ZAkv++YUkz Zn/Fj2JSbGRkkJptd2hPspatnTWdhHNZM0w6tDjjLoMwZLk4KHeW92eVNnG/i2Ai fvJDp2SlttT7teH8A9Q5 =Q8ni -END PGP SIGNATURE End Message ---
Bug#805123: marked as done (swi-prolog: FTBFS on ppc64el)
Your message dated Wed, 30 Dec 2015 03:36:31 + with message-id and subject line Bug#805123: fixed in swi-prolog 7.2.0-3 has caused the Debian Bug report #805123, regarding swi-prolog: FTBFS on ppc64el to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 805123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805123 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: swi-prolog Version: 7.2.0-2 Severity: serious Control: block 797926 by -1 Hi, Your package is failing to build with the following error on ppc64el: JUNIT=/usr/share/java/junit.jar JAVA=java JAVA_PRELOAD= ./test-java.sh Welcome to SWI-Prolog (Multi-threaded, 64 bits, Version 7.2.0) Copyright (c) 1990-2015 University of Amsterdam, VU Amsterdam SWI-Prolog comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. Please visit http://www.swi-prolog.org for details. For help, use ?- help(Topic). or ?- apropos(Word). % halt ERROR: /«PKGBUILDDIR»/packages/jpl/jpl.pl:4164: '$open_shared_object'/3: libjpl: cannot open shared object file: No such file or directory Failed to invoke suite():java.lang.UnsatisfiedLinkError: no jpl in java.library.path Makefile:66: recipe for target 'check_java' failed make[2]: *** [check_java] Error 1 A full log is available at: https://buildd.debian.org/status/fetch.php?pkg=swi-prolog&arch=ppc64el&ver=7.2.0-2%2Bb1&stamp=1446804933 Kurt --- End Message --- --- Begin Message --- Source: swi-prolog Source-Version: 7.2.0-3 We believe that the bug you reported is fixed in the latest version of swi-prolog, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 805...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Євгеній Мещеряков (supplier of updated swi-prolog package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 30 Dec 2015 04:00:32 +0100 Source: swi-prolog Binary: swi-prolog swi-prolog-nox swi-prolog-x swi-prolog-java swi-prolog-odbc Architecture: source Version: 7.2.0-3 Distribution: unstable Urgency: medium Maintainer: Євгеній Мещеряков Changed-By: Євгеній Мещеряков Description: swi-prolog - ISO/Edinburgh-style Prolog interpreter swi-prolog-java - Bidirectional interface between SWI-Prolog and Java swi-prolog-nox - ISO/Edinburgh-style Prolog interpreter (without X support) swi-prolog-odbc - ODBC library for SWI-Prolog swi-prolog-x - User interface library for SWI-Prolog (with X support) Closes: 805123 Changes: swi-prolog (7.2.0-3) unstable; urgency=medium . * Use ppc64le subdirectory for jre libraries on ppc64el, even if online file list says otherwise... Hopefully closes: #805123 Checksums-Sha1: 1ba9edb64acd162b9817843150dc1341b74fec67 2939 swi-prolog_7.2.0-3.dsc 5cf74c1d1e89a8a1916dc854c046675057b42433 19808 swi-prolog_7.2.0-3.debian.tar.xz Checksums-Sha256: bcc798ea1f16315e57529921b218481c4087ebf9cc6648d5bb576ddb0f85811a 2939 swi-prolog_7.2.0-3.dsc a1c36d95ef56e385c7d6df911c43a4ec072988fb1ac4ab729567391835f5fe90 19808 swi-prolog_7.2.0-3.debian.tar.xz Files: bde215b373885939c45c4130a98d4450 2939 interpreters optional swi-prolog_7.2.0-3.dsc ca831cb3a51937ce2d077f8c56c40dba 19808 interpreters optional swi-prolog_7.2.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWg0mXAAoJEMFtqOf0Ubk83zYP/iDXRH0+r4LSQ3S6X3LNo0bg us3reK0V6HTRxe0s1G6Nrhmw6TvlySruWzgIgTPX+u18fQRFEbp0C4RB/wPr1xoH zuz2jzmfeAdYDAQLwTLsURqq83X3YYCtUSXbFca/laC6uefVUbBradEwX1PV9nzF s4q0LZMqEMaMYnAi8BpyK/WESgfCj9CZVUklNOoRW5qppCPpkXLs8FF+0a6YAtHT uibRudNVhQb5WSBS67rBELSm8ciLQLsujiUjay8epJDNG8RQr0bHBbzYW5wJC+g5 EZuyg99a28KU9tT0COMTdNZRz/5XtcosjzccWJphas8TANiQGC8URdfFqG9nLP2p pzExtbbOdoV2aawrodxPcSzrjF5icodZ1bq2v0rmIJxkJt6JperQ7Od5viM41L+g XRl7/DdqC62gBNi5e0OyMmui1DlYrACDxfcS3UocctkNhbawufaeeZubkIh99xKl yTcZfAa0qvq3P6AzcHHQeOU8Eg0pOHRVsDGSB+XI1JVFEKKMWWjCCkk29U3YGiti BKWugeykm9Nd+vC+BKXS3BBF6IfdZcImemaqsPMID9PKgKTqiU/T+cFgyutPqYJA 5iBzjAlD0khj9taiXOvPUXlTi97u5E4+tcO5B2LNWxwU5hSBFcXt0nANuk7pCSz2 JhmAU+o7b8ifiRY7akmC =UEiw -END PGP SIGNATURE End Message ---
Bug#809361: marked as done (librdf-ns-curated-perl: Should be arch: all, not arch: any)
Your message dated Wed, 30 Dec 2015 03:35:43 + with message-id and subject line Bug#809361: fixed in librdf-ns-curated-perl 0.002-2 has caused the Debian Bug report #809361, regarding librdf-ns-curated-perl: Should be arch: all, not arch: any to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809361: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809361 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librdf-ns-curated-perl Version: 0.002-1 Severity: normal Dear Maintainer, This is a pure-perl module, so it should be Architecture: any, not Architecture: all, which wastes buildd capacity and archive space. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: librdf-ns-curated-perl Source-Version: 0.002-2 We believe that the bug you reported is fixed in the latest version of librdf-ns-curated-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated librdf-ns-curated-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 30 Dec 2015 08:18:06 +0530 Source: librdf-ns-curated-perl Binary: librdf-ns-curated-perl Architecture: source all Version: 0.002-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Jonas Smedegaard Description: librdf-ns-curated-perl - curated set of RDF prefixes Closes: 809361 Changes: librdf-ns-curated-perl (0.002-2) unstable; urgency=medium . * Fix build package as arch-independent. Closes: Bug#809361. Thanks to Dagfinn Ilmari Mannsåker. Checksums-Sha1: ed9e7d230caaf17dd7e8cef806d5c6f0d9faf034 2143 librdf-ns-curated-perl_0.002-2.dsc 5159ce835e6d3c80e86d60d35a6de5b817511a8b 3000 librdf-ns-curated-perl_0.002-2.debian.tar.xz a81ecbd91f8926ffc302a092c14091579484b607 9280 librdf-ns-curated-perl_0.002-2_all.deb Checksums-Sha256: dfaf748278f5cb3bc3645e0b721edefff0c73b0c0eadb333fef4dc8a672745fd 2143 librdf-ns-curated-perl_0.002-2.dsc 5ab83c6f22df4b24c31ec69bf98e0fb9d26cbbdb23fcbce6d6ea7e721f5331a7 3000 librdf-ns-curated-perl_0.002-2.debian.tar.xz b5f1503ba6cd24b89ad985ac8e2820a73ada1d1075dadd6ceeb5c871f3f655c6 9280 librdf-ns-curated-perl_0.002-2_all.deb Files: 254356c204e4a28544057cfe220cf1e6 2143 perl optional librdf-ns-curated-perl_0.002-2.dsc 7ee2037ef822d3742928a73d2a416126 3000 perl optional librdf-ns-curated-perl_0.002-2.debian.tar.xz 581d9dc0a8361609adcacf72f14b6757 9280 perl optional librdf-ns-curated-perl_0.002-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWg0bbAAoJECx8MUbBoAEhM+AP/265Qem766wPawO/EAAPjkUJ gS5qQs1w76qiA2PwXm4vmXGoLV7hKYPFYde+2zLxGRd/MNsxWD4kO4LZXBvdZVtH qGoUIZSOF21ivfAz7IZpNQJxRME5mvMDp9l5czsjqx87IzUZN9fYCjLdxbvzs03a YIbImdLe5XgbEdyluWv3Q9jMoWawY7PKFTvIcEDLiAr6Wk9BSrvwm5NtXZY4xtAw 4ocq6UXyrzsuyKa/eq+apAJyvEzNAW0bMmK4iwgSHp6rKwJrw23D5Xaksjfi+GnP 5ff1dpHO81gGYbSt73RTUzNpeoCS5wuCdPQCxuizMDF5FOwIl2c0MNzni4drxRpf knSZ8ZwVaCs1weHVpdOqADhtS4LQuYscy1mH0xsVnx91ETTWJlXp/MnP20qJtqna 8PaQ8PWEeYGW7jYtqKvPK89WVBYhOBWG6+JhduC0aLV2JvIZ3Col196d0OydH+Uy xyB2Lgy9atTpr/6dfOHDpmMEPJUN4NJLPyTx7s7jci2QO16deOwsQy05R0XKJSRA +s5afkYRvRqpu8bmjm4WPYafTAcYh/E4BiywzzX2ftPJsSGSGBAHzzBtUJJJzXyr 5L8JP10MW7XVLgjA1Tp8Y66hnaUT79ZgHtWLnrl2q4xhB80yDPAK6cLSCDf4ku2f d7UDKnhrppCUlB3XXUui =poPD -END PGP SIGNATURE End Message ---
Bug#805457: marked as done ("We've detected you're using an older version of Chrome. Update to stay secure")
Your message dated Wed, 30 Dec 2015 03:36:01 +
with message-id
and subject line Bug#805457: fixed in midori 0.5.11-ds1-1
has caused the Debian Bug report #805457,
regarding "We've detected you're using an older version of Chrome. Update to
stay secure"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
805457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: midori
Version: 0.5.11-2
Severity: wishlist
$ midori https://www.google.com/?hl=en
says
"We've detected you're using an older version of Chrome. Update to stay secure"
--- End Message ---
--- Begin Message ---
Source: midori
Source-Version: 0.5.11-ds1-1
We believe that the bug you reported is fixed in the latest version of
midori, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 805...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sergio Durigan Junior (supplier of updated midori
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 27 Dec 2015 16:12:18 -0500
Source: midori
Binary: midori midori-dbg
Architecture: source amd64
Version: 0.5.11-ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Sergio Durigan Junior
Changed-By: Sergio Durigan Junior
Description:
midori - fast, lightweight graphical web browser
midori-dbg - fast, lightweight graphical web browser (debug symbols)
Closes: 799963 804196 805457
Changes:
midori (0.5.11-ds1-1) unstable; urgency=medium
.
* Rename package (and source tarball) in order to fix a mistake that
happened when uploading the first version of the "0.5.11" version.
Somehow, the source tarball was different than the original tarball.
Fortunately, the only difference were the timestamps.
* Update version of Chromium's User-Agent string.
We identify ourselves as Chromium to other websites, but the version
we use in the User-Agent string is pretty old. This commit updates it
to a newer version (49.0.2571.2, from Nov 22 2015). The positive
side-effect from doing this is that Google does not bother the user
asking her to upgrade to a "newer Chrome". (Closes: #805457)
* Convert patch add-debian-searches to gbp-pq.
Trivial adjustment on add-debian-searches in order to make it
compliant with gbp-pq.
* Better handling of self-signed certificates.
Midori needs gcr/gnome-keyring in order to fully work with self-signed
TLS certificates. This commit improves the error message that is
displayed when clicking on "Trust this website" does not work, and
also makes the Debian Midori package recommend installing
gnome-keyring. This is the best we can do for now. (Closes: #799963)
* Improve security by making sure that we use a safe set of ciphers.
This comes from Debian bug #804196 (LP Bug #1517265). When Midori
uses libwebkitgtk, it inherits the default value of the
G_TLS_GNUTLS_PRIORITY environment variable. Unfortunately this value
is not safe enough because it still lets GnuTLS to enable to unsafe
ciphers. Therefore, we need to set this variable ourselves and make
sure that Midori is using safe ciphers for TLS operations. (Closes:
#804196)
* Override "source-is-missing data/autosuggestcontrol.js"
Lintian is wrongly reporting a "source-is-missing" error for
data/autosuggestcontrol.js. I have reported a bug against it (809170)
and now I am overriding the error.
* Fix Vcs-* URLs.
The package was still using old, non-canonical URLs for
Vcs-{Git,Browser}. Update them now.
* Remove midori.menu (and solve lintian warning)
Lintian was warning "command-in-menu-file-and-desktop-file". Since
Midori already ships a .desktop file, it is time to remove the
midori.menu file from the package.
Checksums-Sha1:
5f560ff8f22812edaeab71be1f29f94b6880d6cc 2263 midori_0.5.11-ds1-1.dsc
64c86935028feb5f89d799c2acacaad67764da6f 1428791 midori_0
Bug#801106: marked as done (sddm-greeter fails to start)
Your message dated Wed, 30 Dec 2015 01:01:20 -0500 with message-id <2091693.GgmntflHtQ@kitterma-e6430> and subject line Re: Bug#801106: sddm-greeter fails to start has caused the Debian Bug report #801106, regarding sddm-greeter fails to start to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 801106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801106 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sddm Version: 0.12.0-4 Severity: critical Justification: breaks the whole system Dear Maintainer, * What led up to the situation? Reboot after installing nvidia 340.93-3 (latest testing version). I had tried stopping sddm; rmmod nvidia; and restarting again ... got the sddm-greeter would not start error and hoped a reboot would fix. The only way I could get a working plasma5 was to install and use lightdm/lightdm-kde-greeter. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sddm depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.57 ii libc6 2.19-22 ii libgcc1 1:5.2.1-17 ii libpam0g 1.1.8-3.1 ii libqt5core5a 5.4.2+dfsg-9 ii libqt5dbus5 5.4.2+dfsg-9 ii libqt5gui55.4.2+dfsg-9 ii libqt5network55.4.2+dfsg-9 ii libqt5qml55.4.2-6 ii libqt5quick5 5.4.2-6 ii libstdc++65.2.1-17 ii libsystemd0 226-3 ii libxcb-xkb1 1.10-3+b1 ii libxcb1 1.10-3+b1 ii qml-module-qtquick2 5.4.2-6 ii sddm-theme-breeze [sddm-theme]4:5.4.1-1 ii sddm-theme-circles [sddm-theme] 0.12.0-4 ii sddm-theme-elarun [sddm-theme]0.12.0-4 ii sddm-theme-maldives [sddm-theme] 0.12.0-4 ii sddm-theme-maui [sddm-theme] 0.12.0-4 sddm recommends no packages. Versions of packages sddm suggests: ii libpam-kwallet5 5.4.1-1 -- debconf information excluded --- End Message --- --- Begin Message --- On Tue, 06 Oct 2015 14:02:56 +0200 Diederik de Haas wrote: > On Tuesday 06 October 2015 11:54:15 Andy Wood wrote: > > Package: sddm > > ... > > Reboot after installing nvidia 340.93-3 (latest testing version). > > See https://bugs.debian.org/799948 > > (workaround "adduser sddm video") Based on the discussion in #799948, I believe this bug can be closed now. Scott K signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: forcibly merging 808785 809311
Processing commands for cont...@bugs.debian.org:
> forcemerge 808785 809311
Bug #808785 {Done: Ondřej Surý } [liblmdb0]
/sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/liblmdb.so.0 is not a symbolic
link
Bug #809349 {Done: Ondřej Surý } [liblmdb0]
/sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/liblmdb.so.0 is not a symbolic
link
Bug #809311 [liblmdb0] [package:liblmdb0] /sbin/ldconfig.real:
/usr/lib/x86_64-linux-gnu/liblmdb.so.0 is not a symbolic link
Severity set to 'normal' from 'minor'
Marked Bug as done
Marked as fixed in versions lmdb/0.9.17-3.
Bug #809349 {Done: Ondřej Surý } [liblmdb0]
/sbin/ldconfig.real: /usr/lib/x86_64-linux-gnu/liblmdb.so.0 is not a symbolic
link
Merged 808785 809311 809349
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
808785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808785
809311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809311
809349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#795482: marked as done (qtbase-opensource-src: Non-free code possibly in torrent example)
Your message dated Wed, 30 Dec 2015 10:18:39 +0300 with message-id <145145991985.10689.15534246718489015...@mitya57.me> and subject line Re: Bug#795482: Moreinfo has caused the Debian Bug report #795482, regarding qtbase-opensource-src: Non-free code possibly in torrent example to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 795482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795482 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qtbase-opensource-src Version: 5.5.0+dfsg-3 Severity: serious Justification: Policy 4.5 During New review I ran across this: O: qtbase-opensource-src source: license-problem-non-free-RFC examples/network/doc/src/torrent.qdoc I looked and that file indeed has the non-free licensing terms. It isn't clear (and I didn't investigate) the degree to which those terms apply to any code in examples/network/torrent/, but this needs investigation as code that it applies to is non-free. --- End Message --- --- Begin Message --- Version: 5.6.0~beta+dfsg-1 On Fri, 14 Aug 2015 10:17:25 -0400, Scott Kitterman wrote: > I don't see any reason to believe that code is non-free. I think the approach > taken in https://codereview.qt-project.org/#/c/123431/ to resolve this > ambiguity is the right one. And that change was applied in Qt 5.6 beta, so closing this bug. -- Dmitry Shachnev signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#685861: marked as done (Rsync: failing on a basic sync example (override plz))
Your message dated Wed, 30 Dec 2015 09:59:30 +0100 with message-id <20151230085930.ga10...@msgid.wurtel.net> and subject line Re: Bug#685861: Rsync: failing on a basic sync example (override plz) has caused the Debian Bug report #685861, regarding Rsync: failing on a basic sync example (override plz) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 685861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rsync Version: 3.0.7-2 Severity: important Hi, you should really think to allow by default to make rsync to work ;) I just tried rsync, to move from Ibm sync default app on Linux platform, and rsync isn't so much reliable to backup a server (independently on the FS) :) Here a quick example cp -r Documents/contacs /tmp ~/Documents$ rsync -av contacs/ /tmp/ sending incremental file list ./ rsync: failed to set times on "/tmp/.": Operation not permitted (1) sent 463 bytes received 16 bytes 958.00 bytes/sec total size is 284326 speedup is 593.58 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1060) [sender=3.0.7] Please could you make rsync working, and more reliable while copying. I hope that it may contribute to improvements of rsync. Best regards Pat -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages rsync depends on: ii base-files 6.0squeeze2 Debian base system miscellaneous f ii libacl1 2.2.49-4 Access control list shared library ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libpopt01.16-1 lib for parsing cmdline parameters ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip rsync recommends no packages. Versions of packages rsync suggests: ii openssh-client1:5.5p1-6 secure shell (SSH) client, for sec ii openssh-server1:5.5p1-6 secure shell (SSH) server, for sec -- no debconf information --- End Message --- --- Begin Message --- On Sat 25 Aug 2012, patrick295767 wrote: > > you should really think to allow by default to make rsync to work ;) > I just tried rsync, to move from Ibm sync default app on Linux platform, and > rsync isn't > so much reliable to backup a server (independently on the FS) :) > > Here a quick example > > cp -r Documents/contacs /tmp > > ~/Documents$ rsync -av contacs/ /tmp/ > sending incremental file list > ./ > rsync: failed to set times on "/tmp/.": Operation not permitted (1) This is because /tmp is not owned by you and you don't have any superuser privileges. This is not a problem with rsync; closing this bug report now. Paul--- End Message ---
Bug#802524: marked as done (nitime: FTBFS: ImportError: cannot import name mpl)
Your message dated Wed, 30 Dec 2015 09:51:02 + with message-id and subject line Bug#802524: fixed in nitime 0.5-3 has caused the Debian Bug report #802524, regarding nitime: FTBFS: ImportError: cannot import name mpl to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 802524: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802524 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nitime Version: 0.5-2 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: make[2]: Entering directory '/nitime-0.5/doc' ../tools/make_examples.py Traceback (most recent call last): File "../tools/make_examples.py", line 96, in execfile(script) File "ar_est_1var.py", line 31, in from nitime.viz import plot_tseries File "/nitime-0.5/debian/tmp/usr/lib/python2.7/dist-packages/nitime/viz.py", line 19, in from matplotlib import mpl ImportError: cannot import name mpl Makefile:79: recipe for target 'rstexamples' failed Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/nitime.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) --- End Message --- --- Begin Message --- Source: nitime Source-Version: 0.5-3 We believe that the bug you reported is fixed in the latest version of nitime, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 802...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Hanke (supplier of updated nitime package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 30 Dec 2015 10:18:40 +0100 Source: nitime Binary: python-nitime python-nitime-doc Architecture: source all Version: 0.5-3 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team Changed-By: Michael Hanke Description: python-nitime - timeseries analysis for neuroscience data (nitime) python-nitime-doc - timeseries analysis for neuroscience data (nitime) -- documentati Closes: 802524 Changes: nitime (0.5-3) unstable; urgency=medium . * Include upstream patch for modern matplotlib versions (Closes: #802524). Checksums-Sha1: 58317d36e1ea88b5fed56191ba9d5c2235abf9db 2068 nitime_0.5-3.dsc 3ff924744bd004e05480ac2fa3e83f2c1cf4 6980 nitime_0.5-3.debian.tar.xz 2e28458f49e184c063067f4d0874f245969faa80 5873370 python-nitime-doc_0.5-3_all.deb 41e40112be3e5926ef6f54475c3b386e0af674de 2537846 python-nitime_0.5-3_all.deb Checksums-Sha256: 949e22436985d40218d96ca83a00e406404a08ee967d4171ec869a5766652d10 2068 nitime_0.5-3.dsc abaf134b7216f02d00a7cff8f759adc1e8d729d43443d2f57433d40a9eaf826f 6980 nitime_0.5-3.debian.tar.xz ed3ec63168602f3c4e52ff847c62f96aaf8042db8e77504cf8fb83194ca874fe 5873370 python-nitime-doc_0.5-3_all.deb e4044e9480354a0d7c9416d6991b23dafcda46577c58a7d67219d9a5d7251a9d 2537846 python-nitime_0.5-3_all.deb Files: 74413f2a8f4303683cd3dddcbbf671dc 2068 python extra nitime_0.5-3.dsc d4aea9ef620a3191f8c5c7d7a7b83668 6980 python extra nitime_0.5-3.debian.tar.xz aa77e57eeb464d9343fa523c498affd8 5873370 doc extra python-nitime-doc_0.5-3_all.deb f2a4fe3e4a43d54f4f9b87d121278b5b 2537846 python extra python-nitime_0.5-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWg6eGAAoJEMBz0ih/+56bFjgP/iCF9V3U2Rr/WgNa+dMkwyFy pNRQyF03T8XAnoU1cyhm5dKNK6teOoWcjz4VhqrPJG8M5MgIWPNNSaFVcmdf9L+f DCIOw5+vpEYr3QPBgl3KWzgaMR/HeOw/GSoBa8PcRWQOP2ES/FxBRs4vZYoin4VI P5l3gy3WasStBrka+kM9eapt7oB1nnmOn+l6bUyzFTmy9378ImRr6A8P3PYWfpkr 9Dh5i6yFOrnE8LR8S5Ww8BsF1B4bc3/ok3uK9h8nRk/sE3yke6Ok0Auxo4p287gj P2grjgxvkYBmFdYiG4cqGottVbwHWuJ9YDDmCjoD83BjqzOXm0uWeHq+jUga4yyn krJQrcvsg/cMuVqPIQxFqxB85BnpcuMLKciALtFmqMnGaqBqS23VDwkC8KVRIGJ0 eQyacExuP3jlg6ewG5zKqcSOwUZraddcpNF0/4eobnK7Pqse8z3O2YauxT5rMUFi TDv88hAGenz9Vz/XeiE/TCnN5CG8G+CPTNP7+Bu2dJ4WkCLEvb9TY3CpzB6Im4eR BkBpD6JWMsL8yuF3IAyACDTc56N7HUVdsYmm0AB35THYehPE1hthf/GBJVJraV4E o7iI
Bug#809401: marked as done (RFS: node-isarray/1.0.0-1)
Your message dated Wed, 30 Dec 2015 10:15:50 + (UTC) with message-id <1174918293.7512110.1451470550203.javamail.ya...@mail.yahoo.com> and subject line Re: Bug#809401: RFS: node-isarray/1.0.0-1 has caused the Debian Bug report #809401, regarding RFS: node-isarray/1.0.0-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "node-isarray" * Package name: node-isarray Version : 1.0.0-1 Upstream Author : Julian Gruber (http://juliangruber.com) * URL : https://github.com/juliangruber/isarray * License : Expat Section : web It builds this binary package: node-isarray - JavaScript Array#isArray for older browsers To access further information about this package, please visit the following URL: http://mentors.debian.net/package/node-isarray Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/node-isarray/node- isarray_1.0.0-1.dsc The Debian packaging is available here: http://anonscm.debian.org/cgit/pkg-javascript/node-isarray.git Changes since the last upload: * New upstream release * Override dh_auto_build & test targets Regards, Ross Gammon -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-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 Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Hi, Signed&Uploaded, thanks for your contribution to Debian! cheers, G. Il Mercoledì 30 Dicembre 2015 10:51, Ross Gammon ha scritto: Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "node-isarray" * Package name: node-isarray Version : 1.0.0-1 Upstream Author : Julian Gruber (http://juliangruber.com) * URL : https://github.com/juliangruber/isarray * License : Expat Section : web It builds this binary package: node-isarray - JavaScript Array#isArray for older browsers To access further information about this package, please visit the following URL: http://mentors.debian.net/package/node-isarray Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/node-isarray/node- isarray_1.0.0-1.dsc The Debian packaging is available here: http://anonscm.debian.org/cgit/pkg-javascript/node-isarray.git Changes since the last upload: * New upstream release * Override dh_auto_build & test targets Regards, Ross Gammon -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-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 Init: systemd (via /run/systemd/system)--- End Message ---
Processed: Re: Bug#770350: rsync: the CONFIG DIRECTIVES include and merge don't work
Processing commands for cont...@bugs.debian.org: > merge 770350 770351 Bug #770350 [rsync] rsync: the CONFIG DIRECTIVES include and merge don't work Bug #770351 [rsync] rsync: the CONFIG DIRECTIVES include and merge don't work Merged 770350 770351 > close 770350 Bug #770350 [rsync] rsync: the CONFIG DIRECTIVES include and merge don't work Bug #770351 [rsync] rsync: the CONFIG DIRECTIVES include and merge don't work Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 770350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770350 770351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#809100: marked as done (libmarc-lint-perl: FTBFS with newer Business::ISBN: test failures)
Your message dated Wed, 30 Dec 2015 10:48:56 + with message-id and subject line Bug#809100: fixed in libmarc-lint-perl 1.49-2 has caused the Debian Bug report #809100, regarding libmarc-lint-perl: FTBFS with newer Business::ISBN: test failures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 809100: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libmarc-lint-perl Version: 1.49-1 Severity: serious User: debian-p...@lists.debian.org Usertags: autopkgtest This package fails to build on current sid/amd64. Looks like the module should be using the 'version' module to compare version numbers; this was presumably broken by libbusiness-isbn-perl 2.010-1, which entered unstable recently. # Failed test 'Checking expected messages, 020: Subfield a has bad checksum, 1548794743.' # at t/check020.t line 88. # got: 'Business::ISBN version must be below 2 or above 2.02_02.' # expected: '020: Subfield a has bad checksum, 1548794743.' [...] Test Summary Report --- t/check020.t (Wstat: 2560 Tests: 31 Failed: 11) Failed tests: 7, 16, 18, 21, 23-24, 26-27, 29-31 Non-zero exit status: 10 Parse errors: Bad plan. You planned 28 tests but ran 31. t/lint.t (Wstat: 2304 Tests: 40 Failed: 9) Failed tests: 5, 7, 11, 13, 15, 17, 19, 21, 23 Non-zero exit status: 9 -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: libmarc-lint-perl Source-Version: 1.49-2 We believe that the bug you reported is fixed in the latest version of libmarc-lint-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Niko Tyni (supplier of updated libmarc-lint-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 30 Dec 2015 12:34:39 +0200 Source: libmarc-lint-perl Binary: libmarc-lint-perl Architecture: source Version: 1.49-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Niko Tyni Description: libmarc-lint-perl - Perl extension for checking validity of MARC records Closes: 809100 Changes: libmarc-lint-perl (1.49-2) unstable; urgency=medium . * Team upload. * Fix test failures due to Business::ISBN version mess (Closes: #809100) Checksums-Sha1: cc6591432a12ccc5f5b13a4348fbed57d2ec9013 2295 libmarc-lint-perl_1.49-2.dsc 531d91f389757526cf694fe7d97f8d4ff7746cd3 3972 libmarc-lint-perl_1.49-2.debian.tar.xz Checksums-Sha256: de5ff96d32fddafb01b56fac7f10ef763ca04cfaaade53d3a0f4cb3d4c440c16 2295 libmarc-lint-perl_1.49-2.dsc cb356f408ec3a71127a5027be5b3132705a88f27687ad000fe06ae2be6266906 3972 libmarc-lint-perl_1.49-2.debian.tar.xz Files: ca2a4e0973d64251378f4193156942c5 2295 perl optional libmarc-lint-perl_1.49-2.dsc 22e47e80ca09debcf8e6a4b317ebd081 3972 perl optional libmarc-lint-perl_1.49-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWg7PSAAoJEC7A/7O3MBsfJBwP/ive8rtjFGSc/mLhWsNg3FfL dMGK10EhlertKFFKH8sxPEbFC0FHTeBqrcVVug72pa7of5Frol16Cho7jhoKMixx NTtTFAPETwLqhckAfcJv8SGF2JxiB6ewZxB8wmDdA1R8cDb59erRROzn3uKdTIkq zrszd5Gi3FcdvODcdBuHjZkZqhbjoUbQLhsLKrYjszgOtvI0B37fZX3ObO7T/u4L B2CmtZFPO8Ec3ZAlTXtkwK5WFwtnPCuizGOyuWU/N9aY9rVjCDpSWvRQm5E3Ry7g sncK8CgvmYmWflGqH+0X4NIpVen471ShTEFNT2BeEyk42q9CROLO7YvPxuLv680X HXCgVGaMt6EzOIoVZtI/08D/TTBcROlHRpalS9VFa2X8+H3k2k2oOdaLmOFTFLUB dGg/Ssp8JObxS9lbd1yjeEL6hYsfGlsyl0kBp4ejM0GfgGMDgLZ0YPa2thFlADIg UQOK9nkEw4w9jER3gZnWwFXAj0Vw0at0cA7XWmnVKSXnrwhenXJOeDlpcmsqkjSD 0RoKzNP16OaYRx5CHdhAFXyde5bUeq6fCoFyjOH1Otibk4P5/TYdfEhydZ0rQ3X3 65uxV9mv68bwmDzxyPC881t44ISs8A6/ZYzSpd5s03/13cA55nBA4pLuV2v7cZIA yAGxxL2jCNlSJBfa4I67 =5Afq -END PGP SIGNATURE End Message ---
Bug#735107: marked as done (--delete fails for peer running version 3.0.7)
Your message dated Wed, 30 Dec 2015 11:34:53 +0100 with message-id <20151230103453.gc20...@msgid.wurtel.net> and subject line Re: Bug#735107: --delete fails for peer running version 3.0.7 has caused the Debian Bug report #735107, regarding --delete fails for peer running version 3.0.7 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 735107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: rsync Version: 3.1.0-2 Trying to rsync some files to my nas (dryrun mode) I got: % rsync -SHavn --delete --exclude .@__thumb /misc/data6 admin@nas1:/share/NFS/Multimedia admin@nas1's password: sending incremental file list rsync: opendir "/misc/data6/lost+found" failed: Permission denied (13) FATAL I/O ERROR: dying to avoid a --delete-during issue with a pre-3.0.7 receiver. rsync error: requested action not supported (code 4) at flist.c(1882) [sender=3.1.0] % ssh admin@nas1 rsync --version rsync version 3.0.7 protocol version 30 Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, no ACLs, xattrs, iconv, symtimes : As you can see, the peer is _not_ running "pre-3.0.7". Its exactly 3.0.7. Maybe the error message should complain about the protocol version instead (30 and older)? Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJS0udXAAoJEAqeKp5m04HLYgMH/0e8Egrfk3Z07SPq0FQSzEtX u/IFoxOYEklMPlwJdUJWwdlIs3Hqww5gwa6Zs+jWlgcIWm3hRA/mP4J6n/JUDWZd /iaLgZOX+8xm6m8M7dUS+qgtxBbJsWuFnXviDl7Lfz/D9eeKoy+OhdifOXOicDvy ogwhOXFFaUESIQtVQnTUGTqBEtQfXSTJXLYAH648QPVZDzeJH0cr7K9mGdz00oz6 2NffBu9HtkHaNl1YltD7Bn8ebdbmd3nzJHDUuNI8OUWDJYdLRNYa0rcHI62YNp1A vdEmPujBTenh+LKtarqiFr1Boe9f9SOhUWYNs4iPVwgTmUeTfdWW2tGDDaJpzIA= =xJVh -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Sorry for the extremely late response... On Sun 12 Jan 2014, Harald Dunkel wrote: > > Trying to rsync some files to my nas (dryrun mode) I got: > > % rsync -SHavn --delete --exclude .@__thumb /misc/data6 > admin@nas1:/share/NFS/Multimedia > admin@nas1's password: > sending incremental file list > rsync: opendir "/misc/data6/lost+found" failed: Permission denied (13) > FATAL I/O ERROR: dying to avoid a --delete-during issue with a pre-3.0.7 > receiver. > rsync error: requested action not supported (code 4) at flist.c(1882) > [sender=3.1.0] When rsync can't get the complete list of all files on both sides, deletion is disabled to prevent catastrophic errors (e.g. deleting all files). You should exclude unreadable directories from the transfer, in this case at least: rsync -SHavn --delete --exclude .@__thumb --exclude /lost+found/ /misc/data6 admin@nas1:/share/NFS/Multimedia > % ssh admin@nas1 rsync --version > rsync version 3.0.7 protocol version 30 > Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others. > Web site: http://rsync.samba.org/ > Capabilities: > 64-bit files, 64-bit inums, 32-bit timestamps, 64-bit long ints, > socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, > append, no ACLs, xattrs, iconv, symtimes > : > > > As you can see, the peer is _not_ running "pre-3.0.7". Its > exactly 3.0.7. Maybe the error message should complain about > the protocol version instead (30 and older)? The protocol version was still 30 in 3.0.8, so I suspect it was a bug in pre-3.0.7 versions. Perhaps the rsync on your NAS is not really a 3.0.7 but is lying? Anyway, as there is a simple workaround for this, I'm closing this bug report. Thanks, Paul--- End Message ---
Bug#734508: marked as done (rsync does not become aware if rsync server goes down)
Your message dated Wed, 30 Dec 2015 11:39:45 +0100 with message-id <20151230103945.gd20...@msgid.wurtel.net> and subject line Re: Bug#734508: rsync does not become aware if rsync server goes down has caused the Debian Bug report #734508, regarding rsync does not become aware if rsync server goes down to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 734508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rsync Version: 3.1.0-2 Severity: normal Hello, server1 with rsync server, server2 with rsync client. I doing a script that notify the transfer, problem: while rsync client sync all, if I stop rsync server, rsync client does not become aware if it and does not notify any error. Thanks for help Pol -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.10-3-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rsync depends on: ii base-files 7.2 ii libacl1 2.2.52-1 ii libc6 2.17-97 ii libpopt01.16-8 ii lsb-base4.1+Debian12 ii zlib1g 1:1.2.8.dfsg-1 rsync recommends no packages. Versions of packages rsync suggests: ii openssh-client 1:6.4p1-2 ii openssh-server 1:6.4p1-2 -- no debconf information --- End Message --- --- Begin Message --- Package: rsync Version: 3.1.0-1 On Wed 08 Jan 2014, Pol Hallen wrote: > > Hi Paul and thanks for your reply, it was a bug of this version: after > updated to 3.1.x that's issue has solved. Sorry for the late reply, and thanks for your feedback. Now closing this bug report. Paul--- End Message ---
Processed: closing 780852
Processing commands for cont...@bugs.debian.org: > # Fixed upstream in 57be7b743fbd7afb86edaac3ac86ef34182f86b9 and > 9a369d39e13787c376c57713ab8c14e5c0f4bfb8 > close 780852 5.0.8-test-3-1 Bug #780852 [zsh-common] zsh: vcs-info produces errors for git rebase -m Marked as fixed in versions zsh/5.0.8-test-3-1. Bug #780852 [zsh-common] zsh: vcs-info produces errors for git rebase -m Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 780852: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#788723: marked as done ([src:icinga] Some sources are not included in your package)
Your message dated Wed, 30 Dec 2015 12:04:20 + with message-id and subject line Bug#788723: fixed in icinga 1.13.3-2 has caused the Debian Bug report #788723, regarding [src:icinga] Some sources are not included in your package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 788723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:icinga Version: 1.13.2-1 user: lintian-ma...@debian.org usertags: source-is-missing severity: serious X-Debbugs-CC: ftpmas...@debian.org Hi, Your package includes some files that seem to lack sources in prefered forms of modification: html/jquery-ui/ui/jquery.ui.widget.js html/jquery-ui/ui/jquery.ui.slider.js html/jquery-ui/ui/jquery.ui.position.js html/jquery-ui/ui/jquery.ui.mouse.js html/jquery-ui/ui/jquery.ui.menu.js html/jquery-ui/ui/jquery.ui.effect.js html/jquery-ui/ui/jquery.ui.effect-blind.js html/jquery-ui/ui/jquery.ui.datepicker.js html/jquery-ui/ui/jquery.ui.core.js html/jquery-ui/ui/jquery.ui.button.js html/jquery-ui/ui/jquery.ui.autocomplete.js Please add an override for: html/docs/js/jquery-min.js According to Debian Free Software Guidelines [1] (DFSG) #2: "The program must include source code, and must allow distribution in source code as well as compiled form." In some cases this could also constitute a license violation for some copyleft licenses such as the GNU GPL. (While sometimes the licence allows not to ship the source, the DFSG always mandates source code.) In order to solve this problem, you could: 1. add the source files to "debian/missing-sources" directory. 2. repack the origin tarball and add the missing source files to it. Both way satisfy the requirement to ship all source code. The second option might be preferable due to the following reasons [2]: - Upstream can do it too and you could even supply a patch to them, thus full filling our social contract [3], see particularly §2. - If source and non-source are in different locations, ftpmasters may miss the source and (needlessly) reject the package. - The source isn't duplicated in every .diff.gz/.debian.tar.* (though this only really matters for larger sources). You could also ask debian...@lists.debian.org or #debian-qa for more guidance. [1] https://www.debian.org/social_contract.en.html#guidelines [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8 [3] https://www.debian.org/social_contract signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Source: icinga Source-Version: 1.13.3-2 We believe that the bug you reported is fixed in the latest version of icinga, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 788...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Frosch (supplier of updated icinga package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 30 Dec 2015 12:50:51 +0100 Source: icinga Binary: icinga-common icinga-cgi icinga-cgi-bin icinga-idoutils icinga icinga-core icinga-doc icinga-dbg Architecture: source amd64 all Version: 1.13.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Nagios Maintainer Group Changed-By: Markus Frosch Description: icinga - host and network monitoring system - metapackage icinga-cgi - host and network monitoring system - CGI scripts icinga-cgi-bin - host and network monitoring system - CGI scripts icinga-common - host and network monitoring system - support files icinga-core - host and network monitoring system - core files icinga-dbg - host and network monitoring system - debug files icinga-doc - host and network monitoring system - documentation icinga-idoutils - host and network monitoring system - icinga-dataobjects support Closes: 788723 Changes: icinga (1.13.3-2) unstable; urgency=medium . * [9f7081e] Add myself as uploader * [4877e88] Add missing sources for jquery-ui (Closes: #788723) * [8522150] Override mis-detected missing source Checksums-Sha1: 18eaa3201bba06384024e2c45428a866783a0d98
Bug#799674: marked as done (Properly document l/ll length modifier for double/long double argument)
Your message dated Wed, 30 Dec 2015 13:08:48 +0100 with message-id and subject line Re: Bug#799674: Properly document l/ll length modifier for double/long double argument has caused the Debian Bug report #799674, regarding Properly document l/ll length modifier for double/long double argument to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 799674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: manpages-dev Version: 3.65-1 Severity: wishlist Currenly the man page for *printf family is difficult to read with regards to float, double and long double printing. The man page for *scanf family is much clearer. AFAIK there is a confusion with an old C89 behavior, since C99 the actual way to print a double is "lf" and "llf" for long double. Right now it reads as: l (ell) A following integer conversion corresponds to a long int or unsigned long int argument, or a following n conversion corresponds to a pointer to a long int argument, or a following c conversion corresponds to a wint_t argument, or a following s conversion corresponds to a pointer to wchar_t argument. Accordingly 'll' and 'L' may need to be updated. --- End Message --- --- Begin Message --- Control: tags -1 wontfix On Tue, Dec 29, 2015 at 1:32 PM, Michael Kerrisk (man-pages) wrote: > On 12/28/2015 08:39 AM, Mathieu Malaterre wrote: >> On Sat, Dec 26, 2015 at 4:54 PM, Michael Kerrisk (man-pages) >> wrote: >>> (Upstream mainatiner here.) >>> >>> On 09/21/2015 03:08 PM, Mathieu Malaterre wrote: >>>> Package: manpages-dev >>>> Version: 3.65-1 >>>> Severity: wishlist >>>> >>>> Currenly the man page for *printf family is difficult to read with >>>> regards to float, double and long double printing. The man page for >>>> *scanf family is much clearer. AFAIK there is a confusion with an old >>>> C89 behavior, since C99 the actual way to print a double is "lf" and >>>> "llf" for long double. >>>> >>>> Right now it reads as: >>>> >>>> l (ell) A following integer conversion corresponds to a >>>> long int or unsigned long int argument, or a following n conversion >>>> corresponds to a pointer to a long int argument, or a following c >>>> conversion corresponds to a wint_t argument, or a >>>> following s conversion corresponds to a pointer to wchar_t argument. >>>> >>>> Accordingly 'll' and 'L' may need to be updated. >>> >>> So, I looked at this report, and I can't understand what the problem >>> is that is being reported. What precisely do you think needs fixing? >> >> It should be clear from the documentation that one should use "lf" to >> print/scan to/from a double. >> >> I'll copy/paste a better written comment from SO >> >> [...] >> Since С99 the matching between format specifiers and floating-point >> argument types in C is consistent between printf and scanf. It is >> >> %f for float >> %lf for double >> %Lf for long double >> >> However, when arguments of type float are passed to variadic functions >> (as variadic parameters) such arguments are implicitly converted to >> type double. This is the reason why in printf format specifiers %f and >> %lf are equivalent and interchangeable. In printf you can "cross-use" >> %lfwith float or %f with double. >> >> But there's no reason to actually do it in practice. Don't use %f to >> printf arguments of type double. It is a widespread habit born back in >> C89/90 times, but it is a bad habit. Use %lf in printffor double and >> keep %f reserved for float arguments. >> >> >> http://stackoverflow.com/a/28222471/136285 >> [...] > > I'm still puzzled. In the spec for fprintf(), I see: > >l (ell) Specifies that a following d, i, o, u, x, or X conversion >specifier applies to a long or unsigned long argument; >that a following n conversion specifier applies to a >pointer to a long argument; that a fo
