Bug#1057020: libgdk-pixbuf-2.0-0: Fails to load webp
Package: libgdk-pixbuf-2.0-0 Version: 2.42.10+dfsg-3 Severity: important Dear Maintainer, libgdk-pixbuf-2.0-0 fails to load webp images. This is a regression also reported in arch here -> https://bbs.archlinux.org/viewtopic.php?id=287629 PR with patch is here -> https://github.com/aruiz/webp-pixbuf-loader/pull/73 See also #1056295 -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.5.12-x64v3-xanmod1 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libgdk-pixbuf-2.0-0 depends on: ii libc62.37-12 ii libgdk-pixbuf2.0-common 2.42.10+dfsg-3 ii libglib2.0-0 2.78.1-4 ii libjpeg62-turbo 1:2.1.5-2 ii libpng16-16 1.6.40-2 ii libtiff6 4.5.1+git230720-2 ii shared-mime-info 2.2-1 Versions of packages libgdk-pixbuf-2.0-0 recommends: ii libgdk-pixbuf2.0-bin 2.42.10+dfsg-3 libgdk-pixbuf-2.0-0 suggests no packages. -- no debconf information
Bug#1056295: geeqie: webp images no longer viewable
Seems like https://bbs.archlinux.org/viewtopic.php?id=287629 On Sun, 19 Nov 2023 19:44:17 -0800 Dean Hamstead wrote: > Package: geeqie > Version: 1:2.1-1 > Severity: important > > Dear Maintainer, > > Upon recent update, webp images are no longer viewable > > > Here is a file that is webp and previously viewable, but now gives an > erro and doesnt view > > > dean@wheeljack:~/pics$ file 271366_20211213110900.webp > 271366_20211213110900.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 1333x1999, Scaling: [none]x[none], YUV color, decoders should clamp > dean@wheeljack:~/pics$ geeqie 271366_20211213110900.webp > Error reading GIF file: Unrecognized image file format > > > This may be a library rather than geeqie itself, if so then please point > me in the right direction > > > -- System Information: > Debian Release: trixie/sid > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.5.11-x64v3-xanmod1 (SMP w/16 CPU threads; PREEMPT) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages geeqie depends on: > ii geeqie-common 1:2.1-1 > ii libarchive13 3.7.2-1 > ii libc6 2.37-12 > ii libcairo2 1.18.0-1 > ii libdjvulibre21 3.5.28-2+b1 > ii libexiv2-27 0.27.6-1 > ii libffmpegthumbnailer4v5 2.2.2+git20220218+dfsg-2 > ii libgcc-s1 13.2.0-6 > ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3 > ii libglib2.0-0 2.78.1-4 > ii libgspell-1-2 1.12.2-1 > ii libgtk-3-0 3.24.38-6 > ii libheif1 1.17.1-1+b1 > ii libjpeg62-turbo 1:2.1.5-2 > ii libjxl0.7 0.7.0-10.2 > ii liblcms2-2 2.14-2 > ii liblua5.3-0 5.3.6-2 > ii libopenjp2-7 2.5.0-2 > ii libpango-1.0-0 1.51.0+ds-3 > ii libpangocairo-1.0-0 1.51.0+ds-3 > ii libpoppler-glib8 22.12.0-2+b1 > ii libraw23 0.21.1-7 > ii libstdc++6 13.2.0-6
Bug#1056295: geeqie: webp images no longer viewable
Package: geeqie Version: 1:2.1-1 Severity: important Dear Maintainer, Upon recent update, webp images are no longer viewable Here is a file that is webp and previously viewable, but now gives an erro and doesnt view dean@wheeljack:~/pics$ file 271366_20211213110900.webp 271366_20211213110900.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 1333x1999, Scaling: [none]x[none], YUV color, decoders should clamp dean@wheeljack:~/pics$ geeqie 271366_20211213110900.webp Error reading GIF file: Unrecognized image file format This may be a library rather than geeqie itself, if so then please point me in the right direction -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.5.11-x64v3-xanmod1 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages geeqie depends on: ii geeqie-common1:2.1-1 ii libarchive13 3.7.2-1 ii libc62.37-12 ii libcairo21.18.0-1 ii libdjvulibre21 3.5.28-2+b1 ii libexiv2-27 0.27.6-1 ii libffmpegthumbnailer4v5 2.2.2+git20220218+dfsg-2 ii libgcc-s113.2.0-6 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3 ii libglib2.0-0 2.78.1-4 ii libgspell-1-21.12.2-1 ii libgtk-3-0 3.24.38-6 ii libheif1 1.17.1-1+b1 ii libjpeg62-turbo 1:2.1.5-2 ii libjxl0.70.7.0-10.2 ii liblcms2-2 2.14-2 ii liblua5.3-0 5.3.6-2 ii libopenjp2-7 2.5.0-2 ii libpango-1.0-0 1.51.0+ds-3 ii libpangocairo-1.0-0 1.51.0+ds-3 ii libpoppler-glib8 22.12.0-2+b1 ii libraw23 0.21.1-7 ii libstdc++6 13.2.0-6 ii libtiff6 4.5.1+git230720-1 ii sensible-utils 0.0.20 Versions of packages geeqie recommends: ii cups-bsd [lpr] 2.4.7-1 ii exiftran 2.10-5 ii exiv20.27.6-1 ii imagemagick 8:6.9.12.98+dfsg1-4 ii imagemagick-6.q16 [imagemagick] 8:6.9.12.98+dfsg1-4 ii librsvg2-common 2.54.7+dfsg-2 ii zenity 3.44.2-1 Versions of packages geeqie suggests: ii gimp 2.10.36-1 pn libjpeg-progs pn xpaint -- no debconf information
Bug#985189: ITP: et -- Eternal Terminal (ET) is a remote shell that automatically reconnects without interrupting the session.
Hopefully this effort hasnt stalled On Sun, 14 Mar 2021 09:17:06 -0500 Jason Gauci wrote: > I'm fine with changing the name. > > On Sun, Mar 14, 2021, 8:44 AM Gard Spreemann wrote: > > > > > Jason Gauci writes: > > > > > Package name : et > > > Version : 6.1.4 > > > Upstream Author : Jason Gauci > > > URL : https://eternalterminal.dev/ > > > License : Apache > > > Programming Lang: C++ > > > Description : Eternal Terminal (ET) is a remote shell that > > automatically reconnects without interrupting the session. > > > > > > Eternal Terminal (ET) is a remote shell that automatically reconnects > > without interrupting the session. > > > > Hi, > > > > Might it be sensible to consider the full name "eternalterminal" (or > > "eternal-terminal") for this package? This would take pressure off the > > two-letter package name space, without giving up much (any?) > > discoverability. > > > > -- Gard > > > > > >
Bug#1002702: RFP: asusctl -- A control daemon, CLI tools, and a collection of crates for interacting with ASUS ROG laptops
Package: wnpp Severity: wishlist * Package name: asusctl Version : 4.0.7 Upstream Author : Asus Linux Community * URL : https://gitlab.com/asus-linux/asusctl * License : MPL Programming Lang: Rust Description : A control daemon, CLI tools, and a collection of crates for interacting with ASUS ROG laptops Asus-Linux.org is an independent community effort that works to improve Linux support for Asus notebooks. Many but not all ASUS ROG laptops work under Linux quite well. But there are always new models coming out, or older models that got missed. This project aims to solve all the issues you may have, and enable many ROG specific features. Sound issues are the most common problem , and solving these requires a little more effort and patience - see the blog post about this plus visit the discord for guidance. Do note that the root problem is almost never pulse audio or pipewire - it's the Realtek codec chip needing specific fixes in the kernel driver. The second most common issue is that of device feature enablement such as: AniMe Matrix display RGB keyboard LEDs fn+key combos and media controls G-Sync enable on capable laptops Re-enable the dGPU after setting "iGPU On" in Windows and more All of the above is either enabled in asusctl already, or is enabled via patches to the kernel (and we provide pre-built kernels with the patches applied) which are steadily upstreamed. Extra features we currently support are: Control graphics modes without reboots for switching between iGPU, dGPU, on-demand, and vfio (for VM pass-through) Set battery charge limit Fan curve control
Bug#882250: Merged upstream
Specifying the interface name as an argument to dhcpd seems to work around this issue.
Bug#882250: Merged upstream
I just experienced this bug in dhcp-server-4.3.6-45.el8.x86_64.rpm frpm centos8 The dhcommon- getifaddrs.patch patch based on https://sources.debian.org/patches/isc-dhcp/4.3.5-3+deb9u1/dhcommon-getifaddrs.patch/ was produced by redhat and appears to now be merged in to 4.3.6 i extracted the src rpm and the dhcp-4.3.6.tar.gz in turn - the changes to discover.c have been applied. so it seems that this bug is now merged upstream. So in ipv6 if there is an alias interface with no ipv6 address (i.e. eth0:0) configured the entire interface (i.e. eth0) will be silently ignored. Fun Dean
Bug#986965: request: backport to buster
Package: nzbget Version: 21.0+dfsg-2 Severity: wishlist Dear Maintainer, It would be wonderful if you would be so kind as to backport to buster. Thanks for maintaining this package -- System Information: Debian Release: 10.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-0.bpo.4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled
Bug#986964: geeqie: View in new window, new window black until zoom in/out
Package: geeqie Version: 1:1.6-8 Severity: normal Dear Maintainer, When an image is opened in a new window, the new window content are black. Zooming in or out the image appears. Not certain how to debug. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-4-amd64 (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages geeqie depends on: ii geeqie-common1:1.6-8 ii libc62.31-10 ii libcairo21.16.0-5 ii libchamplain-0.12-0 0.12.20-1 ii libchamplain-gtk-0.12-0 0.12.20-1 ii libclutter-1.0-0 1.26.4+dfsg-2 ii libclutter-gtk-1.0-0 1.8.4-4 ii libcogl201.22.8-2 ii libdjvulibre21 3.5.28-1 ii libexiv2-27 0.27.3-3 ii libffmpegthumbnailer4v5 2.1.1-0.2+b1 ii libgcc-s110.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.7-2 ii libgtk-3-0 3.24.24-3 ii libheif1 1.11.0-1 ii libjpeg62-turbo 1:2.0.6-4 ii liblcms2-2 2.12~rc1-2 ii liblirc-client0 0.10.1-6.3 ii liblua5.1-0 5.1.5-8.1+b3 ii libopenjp2-7 2.4.0-3 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-0 1.46.2-3 ii libpoppler-glib8 20.09.0-3.1 ii libstdc++6 10.2.1-6 ii libtiff5 4.2.0-1 ii libwebp6 0.6.1-2+b1 ii sensible-utils 0.0.14 Versions of packages geeqie recommends: ii cups-bsd [lpr] 2.3.3op2-3 ii exiftran 2.10-4 ii exiv20.27.3-3 ii imagemagick 8:6.9.11.60+dfsg-1 ii imagemagick-6.q16 [imagemagick] 8:6.9.11.60+dfsg-1 ii librsvg2-common 2.50.3+dfsg-1 pn ufraw-batch ii zenity 3.32.0-6 Versions of packages geeqie suggests: pn geeqie-dbg ii gimp 2.10.22-3 pn libjpeg-progs pn ufraw pn xpaint -- no debconf information
Bug#932473: (no subject)
Any update on this bug? seems like an easy fix
Bug#865881: Adding ET to debian
Hi folks, It seems that the v6 branch has been completed and merged so the blocker of shell support has been resolved. Can we move forward with this package landing in debian? I would love to not have to use a 3rd party repo Thanks Dean
Bug#975680: boxbackup-client: Postinst script generates sha1 rather than sha256 csr
Package: boxbackup-client Version: 0.13~~git20200326.g8e8b63c-1 Severity: normal bbackupd-config generates sha256 csr's but the postinst script for the package produces sha1 csr's which are unusable See https://salsa.debian.org/debian/boxbackup/-/blob/master/debian/boxbackup-client.postinst#L234 -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages boxbackup-client depends on: ii debconf [debconf-2.0] 1.5.74 ii libc6 2.31-4 ii libedit2 3.1-20191231-1 ii libgcc-s1 10.2.0-18 ii libssl1.1 1.1.1h-1 ii libstdc++6 10.2.0-18 ii lsb-base 11.1.0 ii openssl1.1.1h-1 ii perl 5.32.0-5 ii ucf3.0043 ii zlib1g 1:1.2.11.dfsg-2 boxbackup-client recommends no packages. boxbackup-client suggests no packages. -- debconf information excluded
Bug#971652: uhub: Better upstream available
Package: uhub Version: 0.4.1-3.1 Severity: wishlist Dear Maintainer, The below link might be a better upstream, it is active and has many fixes etc https://github.com/modelrockettier/uhub Dean -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.4.44-2-pve (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages uhub depends on: ii libc6 2.28-10 ii libsqlite3-0 3.27.2-3 ii libssl1.1 1.1.1d-0+deb10u3 uhub recommends no packages. uhub suggests no packages. -- no debconf information
Bug#932473: shorewall6 init script inoperational
Package: shorewall6
Version: 5.2.3.2-1
Followup-For: Bug #932473
This seems to work okay;
SRWL='/sbin/shorewall'
SRWL_OPTS="-6 -tvv"
-- System Information:
Debian Release: 10.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.44-2-pve (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages shorewall6 depends on:
ii debconf [debconf-2.0]1.5.71
ii iproute2 4.20.0-2
ii iptables 1.8.2-4
ii libio-socket-inet6-perl 2.72-2
ii lsb-base 10.2019051400
ii shorewall5.2.3.2-1
shorewall6 recommends no packages.
shorewall6 suggests no packages.
-- Configuration Files:
/etc/default/shorewall6 changed:
startup=1
OPTIONS=""
STARTOPTIONS=""
RESTARTOPTIONS=""
RELOADOPTIONS=""
STOPOPTIONS=""
INITLOG=/dev/null
SAFESTOP=0
/etc/init.d/shorewall6 changed:
. /lib/lsb/init-functions
SRWL='/sbin/shorewall'
SRWL_OPTS="-6 -tvv"
WAIT_FOR_IFUP=/usr/share/shorewall/wait4ifup
test -n ${INITLOG:=/var/log/shorewall6-init.log}
test -x $SRWL || exit 0
test -x $WAIT_FOR_IFUP || exit 0
test -n "$INITLOG" || {
echo "INITLOG cannot be empty, please configure $0" ;
exit 1;
}
if [ "$(id -u)" != "0" ]
then
echo "You must be root to start, stop or restart \"Shorewall6 firewall\"."
exit 1
fi
echo_notdone () {
if [ "$INITLOG" = "/dev/null" ] ; then
echo "not done."
else
echo "not done (check $INITLOG)."
fi
exit 1
}
not_configured () {
echo " WARNING "
echo "The firewall won't be started/stopped unless it is configured"
if [ "$1" != "stop" ]
then
echo ""
echo "Please read about Debian specific customization in"
echo "/usr/share/doc/shorewall6/README.Debian.gz."
fi
echo "#"
exit 0
}
. /usr/share/shorewall/shorewallrc
if [ -f "${SYSCONFDIR}/shorewall6" ]
then
. ${SYSCONFDIR}/shorewall6
SRWL_OPTS="$SRWL_OPTS $OPTIONS"
if [ "$startup" != "1" ]
then
not_configured
fi
else
not_configured
fi
[ "$INITLOG" = "/dev/null" ] && SHOREWALL_INIT_SCRIPT=1 ||
SHOREWALL_INIT_SCRIPT=0
export SHOREWALL_INIT_SCRIPT
wait_for_pppd () {
if [ "$wait_interface" != "" ]
then
for i in $wait_interface
do
$WAIT_FOR_IFUP $i 90
done
fi
}
shorewall6_start () {
printf "Starting \"Shorewall6 firewall\": "
wait_for_pppd
$SRWL $SRWL_OPTS start $STARTOPTIONS >> $INITLOG 2>&1 && echo "done." ||
echo_notdone
return 0
}
shorewall6_stop () {
if [ "$SAFESTOP" = 1 ]; then
printf "Stopping \"Shorewall6 firewall\": "
$SRWL $SRWL_OPTS stop >> $INITLOG 2>&1 && echo "done." || echo_notdone
else
printf "Clearing all \"Shorewall6 firewall\" rules: "
$SRWL $SRWL_OPTS clear >> $INITLOG 2>&1 && echo "done." || echo_notdone
fi
return 0
}
shorewall6_restart () {
printf "Restarting \"Shorewall6 firewall\": "
$SRWL $SRWL_OPTS restart $RESTARTOPTIONS >> $INITLOG 2>&1 && echo "done." ||
echo_notdone
return 0
}
shorewall6_refresh () {
printf "Refreshing \"Shorewall6 firewall\": "
$SRWL $SRWL_OPTS refresh >> $INITLOG 2>&1 && echo "done." || echo_notdone
return 0
}
shorewall6_status () {
$SRWL $SRWL_OPTS status && exit 0 || exit $?
}
case "$1" in
start)
shorewall6_start
;;
stop)
shorewall6_stop
;;
refresh)
shorewall6_refresh
;;
force-reload|restart)
shorewall6_restart
;;
status)
shorewall6_status
;;
*)
echo "Usage: /etc/init.d/shorewall6
{start|stop|refresh|restart|force-reload|status}"
exit 1
esac
exit 0
/etc/shorewall6/shorewall6.conf changed:
STARTUP_ENABLED=Yes
VERBOSITY=1
PAGER=
FIREWALL=
LOG_LEVEL="info"
BLACKLIST_LOG_LEVEL=
INVALID_LOG_LEVEL=
LOG_BACKEND=
LOG_VERBOSITY=2
LOG_ZONE=Both
LOGALLNEW=
LOGFILE=/var/log/messages
LOGFORMAT="%s %s "
LOGLIMIT="s:1/sec:10"
LOGTAGONLY=No
MACLIST_LOG_LEVEL="$LOG_LEVEL"
RELATED_LOG_LEVEL=
RPFILTER_LOG_LEVEL="$LOG_LEVEL"
SFILTER_LOG_LEVEL="$LOG_LEVEL"
SMURF_LOG_LEVEL="$LOG_LEVEL"
STARTUP_LOG=/var/log/shorewall6-init.log
TCP_FLAGS_LOG_LEVEL="$LOG_LEVEL"
UNTRACKED_LOG_LEVEL=
CONFIG_PATH=":${CONFDIR}/shorewall6:/usr/share/shorewall6:${SHAREDIR}/shorewall"
GEOIPDIR=/usr/share/xt_geoip/LE
IP6TABLES=
IP=
IPSET=
LOCKFILE=
MODULESDIR=
NFACCT=
PERL=/usr/bin/perl
PATH="/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin"
RESTOREFILE=restore
SHOREWALL_SHELL=/bin/sh
SUBSYSLOCK=""
TC=
ACCEPT_DEFAULT="none"
BLACKLIST_DEFAULT="AllowICMPs,Broadcast(DROP),Multicast(DROP),dropNotSyn:$LOG_LEVEL,dropInvalid:$LOG_LEVEL,DropDNSrep:$LOG_LEVEL"
DROP_DEFAULT="AllowICMPs,Broad
Bug#900739: crashing in toke.c, keyword plugin pointer is left pointing to an XS module that's been unloaded
My preference would be to apply the patch as its a genuine bug fix from upstream.
Bug#961321: RFP: finit -- Fast init for Linux systems
Package: wnpp Severity: wishlist * Package name: finit Version : 3.1 Upstream Author : Joachim Nilsson * URL : https://troglobit.com/projects/finit/ * License : MIT Programming Lang: C Description : Fast init for Linux systems Finit is a simple alternative to SysV init and systemd. It was reverse engineered from the EeePC fastinit over ten years ago by Claudio Matsuoka — "gaps filled with frog DNA …" Focus is on small and embedded systems, although Finit is fully usable on server and desktop systems as well.
Bug#915209: Info received (perl: FTBFS in the year 2020: cpan/Time-Local/t/Local.t failure)
The attached patch is for 5.24.1 old-stable and is derived from
https://rt.cpan.org/Public/Bug/Display.html?id=124787
Offered under the same license as perl
Perhaps it will help someone
On 2020-01-13 15:15, Debian Bug Tracking System wrote:
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.
Your message has been sent to the package maintainer(s):
Niko Tyni
If you wish to submit further information on this problem, please
send it to 915...@bugs.debian.org.
Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.Index: perl-5.24.1/cpan/Time-Local/t/Local.t
===
--- perl-5.24.1.orig/cpan/Time-Local/t/Local.t
+++ perl-5.24.1/cpan/Time-Local/t/Local.t
@@ -91,7 +91,7 @@ for (@time, @neg_time) {
# Test timelocal()
{
-my $year_in = $year < 70 ? $year + 1900 : $year;
+my $year_in = $year + 1900;
my $time = timelocal($sec,$min,$hour,$mday,$mon,$year_in);
my($s,$m,$h,$D,$M,$Y) = localtime($time);
@@ -107,7 +107,7 @@ for (@time, @neg_time) {
# Test timegm()
{
-my $year_in = $year < 70 ? $year + 1900 : $year;
+my $year_in = $year + 1900;
my $time = timegm($sec,$min,$hour,$mday,$mon,$year_in);
my($s,$m,$h,$D,$M,$Y) = gmtime($time);
@@ -125,7 +125,6 @@ for (@time, @neg_time) {
for (@bad_time) {
my($year, $mon, $mday, $hour, $min, $sec) = @$_;
-$year -= 1900;
$mon--;
eval { timegm($sec,$min,$hour,$mday,$mon,$year) };
@@ -134,14 +133,14 @@ for (@bad_time) {
}
{
-is(timelocal(0,0,1,1,0,90) - timelocal(0,0,0,1,0,90), 3600,
+is(timelocal(0,0,1,1,0,1990) - timelocal(0,0,0,1,0,1990), 3600,
'one hour difference between two calls to timelocal');
-is(timelocal(1,2,3,1,0,100) - timelocal(1,2,3,31,11,99), 24 * 3600,
+is(timelocal(1,2,3,1,0,2000) - timelocal(1,2,3,31,11,1999), 24 * 3600,
'one day difference between two calls to timelocal');
# Diff beween Jan 1, 1980 and Mar 1, 1980 = (31 + 29 = 60 days)
-is(timegm(0,0,0, 1, 2, 80) - timegm(0,0,0, 1, 0, 80), 60 * 24 * 3600,
+is(timegm(0,0,0, 1, 2, 1980) - timegm(0,0,0, 1, 0, 1980), 60 * 24 * 3600,
'60 day difference between two calls to timegm');
}
Bug#915209: perl: FTBFS in the year 2020: cpan/Time-Local/t/Local.t failure
Package: perl Followup-For: Bug #915209 Dear Maintainer, We have this same issue on 5.24.1 for debian 9 (yes, old stable) cpan/Time-Local/t/Local ... # Failed test 'timelocal year for 1970 1 2 0 0 0' # at t/Local.t line 104. # got: '170' # expected: '70' # Failed test 'timegm year for 1970 1 2 0 0 0' # at t/Local.t line 120. # got: '170' # expected: '70' # Looks like you failed 2 tests of 187. FAILED at test 6 Just adding this here if you would be so kind as to patch it too Dean Psst! It's possible that this email contains information that is on the super secret side of confidential. So if you received it accidentally, let the sender know straight away and delete it (and the email you sent them). Also, we should let you know that any emails that come and go through Winc™ might be scanned, stored or read by Winc™ at its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it sends, but we can't promise that it will be error free. So, please don't hold it against us.
Bug#946495: RFP: mcrouter -- a memcached protocol router for scaling memcached deployments
Package: wnpp Severity: wishlist * Package name: mcrouter Version : 41 Upstream Author : Facebook, Inc * URL : https://github.com/facebook/mcrouter * License : MIT Programming Lang: C++ Description : A memcached protocol router for scaling memcached deployments Mcrouter is a memcached protocol router for scaling memcached (http://memcached.org/) deployments. It's a core component of cache infrastructure at Facebook and Instagram where mcrouter handles almost 5 billion requests per second at peak. --- It seems the wikimedia people have debian packaging at https://github.com/wikimedia/operations-debs-mcrouter And the 'packaging' branch seems to have their ubuntu packaging https://github.com/facebook/mcrouter/tree/packaging Both of which may make packaging easier
Bug#944786: exim4-config: openspf.org gone
Package: exim4-config
Version: 4.92-8+deb10u2~bpo9+1
Severity: normal
Dear Maintainer,
jj
The message regarding openspf.org in conf.d/acl/30_exim4-config_check_rcpt is
now broken as the openspf.org domain is gone.
i.e. http://www.openspf.org/Why?scope=${if def:sender_address_domain \
See also
https://www.getmailbird.com/what-spf-resources-are-available-now-that-openspf-org-is-gone/
-- Package-specific info:
Exim version 4.92 #3 built 05-Sep-2019 16:58:28
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013)
Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS
move_frozen_messages Content_Scanning DANE DKIM DNSSEC Event OCSP PRDR PROXY
SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz
dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite
Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa tls
Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Malware: f-protd f-prot6d drweb fsecure sophie clamd avast sock cmdline
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file search path is
/etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated
Configuration file is /var/lib/exim4/config.autogenerated
-- System Information:
Debian Release: 9.11
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-0.bpo.4-cloud-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages exim4-config depends on:
ii adduser3.115
ii debconf [debconf-2.0] 1.5.61
exim4-config recommends no packages.
exim4-config suggests no packages.
-- Configuration Files:
/etc/exim4/conf.d/acl/00_exim4-config_header changed [not included]
/etc/exim4/conf.d/acl/30_exim4-config_check_mail changed [not included]
/etc/exim4/conf.d/acl/30_exim4-config_check_rcpt changed [not included]
/etc/exim4/conf.d/acl/40_exim4-config_check_data changed [not included]
/etc/exim4/conf.d/auth/30_exim4-config_examples changed [not included]
/etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs changed [not included]
/etc/exim4/conf.d/main/02_exim4-config_options changed [not included]
/etc/exim4/conf.d/router/200_exim4-config_primary changed [not included]
/etc/exim4/conf.d/router/300_exim4-config_real_local changed [not included]
/etc/exim4/conf.d/router/400_exim4-config_system_aliases changed [not included]
/etc/exim4/conf.d/router/600_exim4-config_userforward changed [not included]
/etc/exim4/conf.d/router/700_exim4-config_procmail changed [not included]
/etc/exim4/conf.d/router/800_exim4-config_maildrop changed [not included]
/etc/exim4/conf.d/router/850_exim4-config_lowuid changed [not included]
/etc/exim4/conf.d/router/900_exim4-config_local_user changed [not included]
/etc/exim4/conf.d/transport/30_exim4-config_mail_spool changed [not included]
/etc/exim4/conf.d/transport/30_exim4-config_maildir_home changed [not included]
/etc/exim4/conf.d/transport/30_exim4-config_maildrop_pipe changed [not included]
/etc/exim4/conf.d/transport/30_exim4-config_procmail_pipe changed [not included]
/etc/exim4/conf.d/transport/30_exim4-config_remote_smtp changed [not included]
/etc/exim4/conf.d/transport/35_exim4-config_address_directory changed [not
included]
-- debconf information excluded
Bug#842306: ITP: falco -- Sysdig Falco is a behavioral activity monitor designed to detect anomalous activity in your applications
Falco now has its very own website https://falco.org/ And github https://github.com/falcosecurity/falco +1 to getting this packaged On Wed, 2 Nov 2016 12:42:22 +0100 Julien Rabier wrote: > Le 01 nov. à 17:07, Evgeni Golov a écrit : > > Hi, > > > > On Mon, Oct 31, 2016 at 07:04:31PM +0100, Julien Rabier wrote: > > > > Would you like to join Harlan and me in maintaining sysdig itself too? > > > > > > Yes, that would be great ! > > > > You are "taziden-guest" on Alioth? And member of collab-maint? > > Then there is nothing more to do than to say welcome :) > > Yes, that's me indeed ! > I will start working on it some time next week. > > Julien/taziden > >
Bug#933315: sc: Maybe swap to SC-IM ?
Package: sc Version: 7.16-4+b3 Severity: wishlist Tags: upstream Dear Maintainer, This person seems to have continued developing SC adding lots of fun stuff. Perhaps its a good new base for this package? See https://github.com/andmarti1424/sc-im Just a wish. Thanks for maintaining the package Dean -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sc depends on: ii libc62.28-10 ii libncurses6 6.1+20190713-1 ii libtinfo66.1+20190713-1 sc recommends no packages. sc suggests no packages. Psst! It's possible that this email contains information that is on the super secret side of confidential. So if you received it accidentally, let the sender know straight away and delete it (and the email you sent them). Also, we should let you know that any emails that come and go through Winc™ might be scanned, stored or read by Winc™ at its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it sends, but we can't promise that it will be error free. So, please don't hold it against us.
Bug#891038: Please?
This would be very handy. Please please?
Bug#931590: linux-image-cloud-amd64: new build for 4.19.37-5 ?
Package: linux-image-cloud-amd64 Version: 4.19+105~bpo9+1 Severity: normal Dear Maintainer, In reference to this CVE https://security-tracker.debian.org/tracker/CVE-2019-11478 Will there be a build for the linux image (cloud) for 4.19.37-5? which is marked as fixing this issue ? Thanks -- System Information: Debian Release: 9.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-0.bpo.4-cloud-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages linux-image-cloud-amd64 depends on: ii linux-image-4.19.0-0.bpo.5-cloud-amd64 4.19.37-4~bpo9+1 linux-image-cloud-amd64 recommends no packages. linux-image-cloud-amd64 suggests no packages. -- no debconf information
Bug#930339: RFP: wsdd2 -- WSD/LLMNR Discovery/Name Service Daemon
Package: wnpp Severity: wishlist * Package name: wsdd2 Version : 1.8 Upstream Author : Netgear * URL :https://github.com/kochinc/wsdd2 * License : GPL Programming Lang: C Description : WSD/LLMNR Discovery/Name Service Daemon With Microsoft turning off SMB1 feature completely on Windwos 10, any Samba shares on the local network become invisible to Windwos 10 computers. That's due to the fact that SMB1 is required for Computer Browser service to function. Newer Windows systems can use WSD (Web Services for Devices) to discover shares hosted on other Windows computers while Linux systems normally utilize mNDS/DNS-SD for service discovery. Microsoft is moving to support mDNS/DNS-SD, but not yet there. The primary purpose of this project is to enable WSD on OpenMediaVault so that network shares hosted on a OMV4 box can appear in Windows File Explorer / Network. The original source code was taken from Netgear ReadyNAS OS v6.9.3 published athttps://kb.netgear.com/2649/NETGEAR-Open-Source-Code-for-Programmers-GPL. Alternative github:https://github.com/Andy2244/wsdd2 (used by openwrt) The Samba project has yet to include this now years old PR which includes the functionality natively in Sambahttps://bugzilla.samba.org/show_bug.cgi?id=11473 This stand alone daemon fills the gap
Bug#929605: courier-imap-ssl: courier-imap-ssl zombies
Package: courier-imap Version: 4.17.2+0.76.3-5+deb9u1 Severity: normal File: courier-imap-ssl Dear Maintainer, * What led up to the situation? I recently upgraded from Jessie (4.15-1.6) to stretch. This was a clean rebuild on a new VM, with mail data copied over and config changes cherry-picked over to suit the new version. * What exactly did you do (or not do) that was effective (or ineffective)? courier-imap-ssl seems to not be reaping processes properly, and zombies are floating around. I dont have non-ssl imap running exposed to the internet (its boound to localhost for webmail to use), but in its limited use it isnt generating zombie processes. Courier is being monitored by monit, it doesnt have any restarts in its logs. * What was the outcome of this action? Zombies. * What outcome did you expect instead? No Zombies. -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-0.bpo.4-cloud-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages courier-imap depends on: ii courier-authlib0.66.4-9 ii courier-base 0.76.3-5+deb9u1 ii debconf [debconf-2.0] 1.5.61 ii exim4-daemon-heavy [mail-transport-agent] 4.92-2~bpo9+1 ii init-system-helpers1.48 ii libc6 2.24-11+deb9u4 ii libcourier-unicode11.4-3+b1 ii libgamin0 [libfam0]0.1.10-5+b1 ii libgdbm3 1.8.3-14 ii libidn11 1.33-1 ii sysvinit-utils 2.88dsf-59.9 courier-imap recommends no packages. Versions of packages courier-imap suggests: pn courier-doc ii mutt [imap-client]1.7.2-1+deb9u1 ii s-nail [imap-client] 14.8.16-1 -- Configuration Files: /etc/courier/imapd-ssl changed: SSLPORT=993 SSLADDRESS=0 SSLPIDFILE=/run/courier/imapd-ssl.pid SSLLOGGEROPTS="-name=imapd-ssl" IMAPDSSLSTART=YES IMAPDSTARTTLS=YES IMAP_TLS_REQUIRED=0 COURIERTLS=/usr/bin/couriertls TLS_CERTFILE=/etc/courier/imapd.pem TLS_DHPARAMS=/etc/courier/dhparams.pem TLS_TRUSTCERTS=/etc/ssl/certs TLS_VERIFYPEER=NONE TLS_CACHEFILE=/var/lib/courier/couriersslcache TLS_CACHESIZE=524288 MAILDIRPATH=Maildir /etc/courier/imapd changed: ADDRESS=::1 PORT=143 MAXDAEMONS=40 MAXPERIP=20 PIDFILE=/run/courier/imapd.pid TCPDOPTS="-nodnslookup -noidentlookup" IMAPACCESSFILE=/etc/courier/imapaccess LOGGEROPTS="-name=imapd" IMAP_CAPABILITY="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE" IMAP_KEYWORDS=1 IMAP_ACL=1 IMAP_CAPABILITY_ORIG="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 AUTH=CRAM-SHA256 IDLE" IMAP_PROXY=0 IMAP_PROXY_FOREIGN=0 IMAP_IDLE_TIMEOUT=60 IMAP_MAILBOX_SANITY_CHECK=1 IMAP_CAPABILITY_TLS="$IMAP_CAPABILITY AUTH=PLAIN" IMAP_CAPABILITY_TLS_ORIG="$IMAP_CAPABILITY_ORIG AUTH=PLAIN" IMAP_DISABLETHREADSORT=0 IMAP_CHECK_ALL_FOLDERS=0 IMAP_OBSOLETE_CLIENT=0 IMAP_UMASK=022 IMAP_ULIMITD=131072 IMAP_USELOCKS=1 IMAP_SHAREDINDEXFILE=/etc/courier/shared/index IMAP_ENHANCEDIDLE=0 IMAP_TRASHFOLDERNAME=Trash IMAP_EMPTYTRASH=Trash:7 IMAP_MOVE_EXPUNGE_TO_TRASH=0 SENDMAIL=/usr/sbin/sendmail HEADERFROM=X-IMAP-Sender IMAPDSTART=YES MAILDIRPATH=Maildir -- no debconf information
Bug#905234: Do you need some help with the urbackup package ?
Perhaps for now, just violate debian and place in contrib? similar to gitlab packages On Tue, 13 Nov 2018 18:21:16 +0100 Roberto Lumbreras wrote: > Hi Pieter, > > The packaging process is a bit of a nightmare, as server includes and > depends on a lot of css and javascript packages. Some of them are already > available on Debian, others need to be packaged first, then all those files > have to be deleted from sources to be released with Debian. Otherwise you > will end up with the same thing you can download from urbackup.org, but > with a lot of Debian Policy violation bugs (not sure, just a wild guess). > > For the last weeks I haven't worked on the packaging (lack of time), but I > intend to do it eventually. > It will take a lot of work and time for sure, so if you can help go ahead. > > > On Sun, Nov 11, 2018 at 7:33 PM Pieter De Wit wrote: > > > Hi, > > > > I am trying to get urbackup into Ubuntu, not via a PPA. I was told that > > the easiest way is to get it in via upstream. As such, I was wondering if > > you need some help in doing this as I see you have a request going already ? > > > > Thanks, > > > > Pieter > > > > -- > Regards, > Roberto Lumbreras > Debian developer
Bug#929267: nagios-plugins-contrib: Please include check_sip
Package: nagios-plugins-contrib Version: 21.20170222 Severity: wishlist Dear Maintainer, It would be wonderful if you could include check_sip from https://github.com/bashtoni/nagios-check-sip Its a self contained basic SIP checker in perl, with a GPLv2 license. Thanks Dean
Bug#927741: exim4-config: Please add headers_remove control in transport/30_exim4-config_remote_smtp
Package: exim4-config Version: 4.89-2+deb9u3 Severity: wishlist Dear Maintainer, Would you be so kind as to add in to the transport/30_exim4-config_remote_smtp file, a control for 'headers_remove' for the remote_smtp transport. In my case i use the following line added to this transport headers_remove = "X-SA-Do-Not-Run:X-SA-Exim-Scanned:X-SA-Exim-Mail-From:X-SA-Exim-Rcpt-To:X-SA-Exim-Connect-IP:X-PHP-Originating-Script" It would be convenient to have this as a definable variable so that the file can update without complaints -- Package-specific info: Exim version 4.92 #5 built 02-Mar-2019 14:59:31 Copyright (c) University of Cambridge, 1995 - 2018 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC Event OCSP PRDR SOCKS TCP_Fast_Open Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Configure owner: 0:0 Size of off_t: 8 Configuration file search path is /etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated Configuration file is /var/lib/exim4/config.autogenerated -- System Information: Debian Release: 9.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-0.bpo.4-cloud-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages exim4-config depends on: ii adduser3.115 ii debconf [debconf-2.0] 1.5.61 exim4-config recommends no packages. exim4-config suggests no packages. -- Configuration Files: /etc/exim4/passwd.client changed [not included] -- debconf information excluded
Bug#927733: exim4-config: Please expand default 'ignore_target_hosts'
Package: exim4-config Version: 4.89-2+deb9u3 Severity: wishlist Dear Maintainer, in router/200-exim4-config_primary i would like to recommend expanding this list as follows: # Don't allow domains whose single MX (or A) record is a # "special-use IPv4 address", as listed in RFC 3330. ignore_target_hosts = <; 0::0/0 ; \ # Hosts on "this network"; RFC 1700 (page 4) states that these # are only allowed as source addresses 0.0.0.0/8 ; \ # Private networks, RFC 1918 10.0.0.0/8 ; 172.16.0.0/12 ; 192.168.0.0/16 ; \ # Carrier NAT, RFC6598 100.64.0.0/10 ; \ # Internet host loopback address, RFC 1700 (page 5) 127.0.0.0/8 ; \ # "Link local" block 169.254.0.0/16 ; \ # "TEST-NET-1" - should not appear on the public Internet 192.0.2.0/24 ; \ # "TEST-NET-2" - should not appear on the public Internet 198.51.100.0/24 ; \ # 6to4 relay anycast addresses, RFC 3068 192.88.99.0/24 ; \ # Network interconnect device benchmark testing, RFC 2544 198.18.0.0/15 ; \ # "TEST-NET-3" - should not appear on the public Internet 203.0.113.0/24 ; \ # Multicast addresses, RFC 3171 224.0.0.0/4 ; \ # Reserved for future use, RFC 1700 (page 4) 240.0.0.0/4 -- Package-specific info: Exim version 4.92 #5 built 02-Mar-2019 14:59:31 Copyright (c) University of Cambridge, 1995 - 2018 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC Event OCSP PRDR SOCKS TCP_Fast_Open Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Configure owner: 0:0 Size of off_t: 8 Configuration file search path is /etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated Configuration file is /var/lib/exim4/config.autogenerated -- System Information: Debian Release: 9.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-0.bpo.4-cloud-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages exim4-config depends on: ii adduser3.115 ii debconf [debconf-2.0] 1.5.61 exim4-config recommends no packages. exim4-config suggests no packages. -- Configuration Files: /etc/exim4/passwd.client changed [not included] -- debconf information excluded
Bug#926297: duplicity: azure dependency broken?
Package: duplicity Version: 0.7.18.2-1 Severity: normal Dear Maintainer, I installed python-azure which brings python-azure-storge with it. This doesnt seem sufficient though, running this sample command fails as follows $ duplicity full /source/dir azure://containername BackendException: Azure backend requires Microsoft Azure Storage SDK for Python (https://pypi.python.org/pypi/azure-storage/). Similarly, if i do a 'pip install azure' i get the same error. FYI $ dpkg -l | grep azure ii python-azure2.0.0~rc6+dfsg-2 all Microsoft Azure SDK for Python 2.x ii python-azure-storage0.33.0-1 all Microsoft Azure Storage Library for Python 2.x ii python-msrestazure 0.4.7-1 all Runtime library for AutoRest generated Python 2.x clients -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (99, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-cloud-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages duplicity depends on: ii gnupg 2.2.12-1 ii libc6 2.28-2 ii librsync1 0.9.7-10+b1 ii python2.7.15-3 ii python-fasteners 0.12.0-3 ii python-lockfile 1:0.12.2-2 Versions of packages duplicity recommends: ii python-oauthlib 2.1.0-1 ii python-paramiko 2.4.2-0.1 ii python-pexpect 4.6.0-1 ii python-urllib3 1.24.1-1 ii rsync3.1.3-1 Versions of packages duplicity suggests: pn lftp pn ncftp pn python-boto pn python-cloudfiles pn python-gdata pn python-pip pn python-swiftclient pn tahoe-lafs -- no debconf information Psst! It's possible that this email contains information that is on the super secret side of confidential. So if you received it accidentally, let the sender know straight away and delete it (and the email you sent them). Also, we should let you know that any emails that come and go through Winc™ might be scanned, stored or read by Winc™ at its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it sends, but we can't promise that it will be error free. So, please don't hold it against us.
Bug#926289: python-azure-storage: New upstream version
Package: python-azure-storage Version: 20181109+git-1 Severity: wishlist Dear Maintainer, Upstream continues to move ever onward, as per https://github.com/Azure/azure-storage-python/releases This is implacting me as 'duplicity' package seems to need a newer version of python-azure-storage to function Thanks -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (99, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-cloud-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python-azure-storage depends on: ii python 2.7.15-3 ii python-azure 20181112+git-2 ii python-concurrent.futures 3.2.0-2 ii python-cryptography2.6.1-3 ii python-dateutil2.7.3-3 ii python-requests2.21.0-1 python-azure-storage recommends no packages. python-azure-storage suggests no packages. -- no debconf information Psst! It's possible that this email contains information that is on the super secret side of confidential. So if you received it accidentally, let the sender know straight away and delete it (and the email you sent them). Also, we should let you know that any emails that come and go through Winc™ might be scanned, stored or read by Winc™ at its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it sends, but we can't promise that it will be error free. So, please don't hold it against us.
Bug#924532: gitlab-runner: New upstream version
Package: gitlab-runner Version: 11.2.0+dfsg-2 Severity: wishlist There is a new upstream version. 11.8.0 as of now This is desirable for me due to this bug being fixed https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1010
Bug#922184: Stretch-backports linux-image-cloud-amd64 broken
Package: linux-image-cloud-amd64 Severity: critical In stretch-backports the linux-image-cloud-amd64 package depends upon linux-image-4.19.0-0.bpo.2-cloud-amd64 however that package is not available See https://packages.debian.org/stretch-backports/linux-image-cloud-amd64 There does seem to be an unsigned version at https://packages.debian.org/stretch-backports/linux-image-4.19.0-0.bpo.2-cloud-amd64-unsigned
Bug#921530: gitlab-ci-multi-runner: New upstream version
Package: gitlab-ci-multi-runner Version: 1.11.4+dfsg-2 Severity: wishlist There is a new upstream version. 11.7.0 as of now This is desirable for me due to this bug being fixed https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/1010 Psst! It's possible that this email contains information that is on the super secret side of confidential. So if you received it accidentally, let the sender know straight away and delete it (and the email you sent them). Also, we should let you know that any emails that come and go through Winc™ might be scanned, stored or read by Winc™ at its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it sends, but we can't promise that it will be error free. So, please don't hold it against us.
Bug#911604: haveged start up fails due to apparmor denying write access to /run/haveged.pid
I have having the same issue with sysvinit-core On Sat, 1 Dec 2018 23:56:10 +0100 Gert wrote: > > What helped was adding the line > > /run/haveged.pid w, > > to /etc/apparmor.d/local/usr.sbin.haveged > > That works, thank you. > FWIW, I did not have this problem when I used systemd as init. > I just switched to openrc-init, and then I did. > I don't know why that would make a difference. > > Buster, i386, /bin/sh -> dash, init=/sbin/openrc-init > haveged 1.9.1-6 > init-system-helpers 1.56 > initscripts 2.92~beta-2 > libc6:i386 2.27-8 > libhavege1:i386 1.9.1-6 > linux-image-4.18.0-2-686-pae 4.18.10-2+b1 > lsb-base 9.20170808 > apparmor-profiles 2.13.1-3 > openrc 0.39-1 > initscripts 2.92~beta-2 > >
Bug#918661:
Its all happening tomorrow. Kind of sad there isnt a solution in the 'stable' versions? On Tue, 29 Jan 2019 23:43:58 +0100 StalkR wrote: > I also just discovered dnsflagday.net, ran edsncomp against my zone on > stretch pdns-server 4.0.3-1+deb9u2 and it complained about > "edns1=noerror,badversion,soa" (https://ednscomp.isc.org/ednscomp/1fa3f65433). > Not fatal for dnsflagday apparently, but still failures. > So I pinned https://repo.powerdns.com/ to get pdns-server > 4.1.5-1pdns.stretch and now it passes ( > https://ednscomp.isc.org/ednscomp/15a52244dd) - didn't even have to change > anything in pdns.conf. > If at all possible, consider backporting to 4.0 whatever patches fixed edns > compliance in 4.1? > > > To get a clean slate on 4.0, you need to disable the packet cache. > How do you disable it exactly? I also found > https://github.com/PowerDNS/pdns/issues/6806 saying this but it doesn't > mention a setting. > I tried disable-packetcache per > https://doc.powerdns.com/md/recursor/settings/#disable-packetcache but it > seems to be a recursor setting, not authoritative. > I couldn't find a packet cache setting on > https://doc.powerdns.com/md/authoritative/settings/ or > https://doc.powerdns.com/md/authoritative/performance/#packet-cache other > than cache-ttl/max-cache-entries. > (I'm using a bind backend, in case it matters.)
Bug#916256: [pkg-go] Bug#916256: Bug#916256: gitlab-runner fails when it tries to pull docker image gitlab-runner-helper:11.2.0
Im using hosted kubernetes (azure kubernetes in this case) which runs the actual docker machines all for me. They are ubuntu it seems but they are entirely encapsulated as part of the service. That said, this error would occur if the kubernetes cluster is external to the debian machine that runs the runner? (which is my scenario) as that docker instance running on the kubernetes node would not have that 'local' image? by manually setting the helper_image to something in the gitlab/ space - things work for me On 25/1/19 12:16 am, Dmitry Smirnov wrote: On Thursday, 24 January 2019 9:30:47 PM AEDT Dean Hamstead wrote: In my case, i am using the kubernetes executor That shouldn't matter as it failed in "executor_docker.go:166". First it tries to load helper image from local file system: ERRO[] Docker executor: prebuilt image helpers will be loaded from /var/lib/gitlab-runner. Then, in case helper image is not there, it falls back to pull from registry. So once again, do you have a "/var/lib/gitlab-runner/gitlab-runner- prebuilt.tar.xz" file? Did you try to build helper image by "sudo dpkg-reconfigure gitlab-runner"? If it fails to build a helper image, you would know what's the problem from the error. Usually this happens when Docker daemon is not running when gitlab-runner is installed...
Bug#916256: [pkg-go] Bug#916256: gitlab-runner fails when it tries to pull docker image gitlab-runner-helper:11.2.0
In my case, i am using the kubernetes executor On 24/1/19 6:39 pm, Dmitry Smirnov wrote: On Thursday, 24 January 2019 11:01:03 AM AEDT Dean Hamstead wrote: Seems to be the same as: https://gitlab.com/gitlab-org/gitlab-runner/issues/3441 Probably not the same... Debian package works very different in regards to gitlab-runner-helper image. From post-install docker build command is executed to prepare an image which is then stored into "/var/lib/gitlab-runner/". By definition, prebuilt image is local and it should never be downloaded. Do you have "/var/lib/gitlab-runner/gitlab-runner-prebuilt.tar.xz" file? I test every upload of Gitlab Runner (and I use this very version all the time) so I suspect that the problem might be somewhere in configuration... Could you try "sudo dpkg-reconfigure gitlab-runner"? There are few patches to force use of local prebuilt image -- maybe we miss one code path that should be patched but package passed Docker tests before upload so prebuilt image should work...
Bug#916256: gitlab-runner fails when it tries to pull docker image gitlab-runner-helper:11.2.0
Seems to be the same as: https://gitlab.com/gitlab-org/gitlab-runner/issues/3441
Bug#916256: gitlab-runner fails when it tries to pull docker image gitlab-runner-helper:11.2.0
This is doomed to fail with the default logic for the helper_image default Per https://docs.gitlab.com/runner/configuration/advanced-configuration.html#helper-image and https://docs.gitlab.com/runner/configuration/advanced-configuration.html#overriding-the-helper-image
Bug#918661: pdns-server: EDNS Compliance Steps
The same results are given when tested against: pdns-server (3.4.1-4+deb8u8) pdns-server (4.0.3-1~bpo8+1) pdns-server (4.0.3-1+deb9u2) On 8/1/19 8:52 pm, Chris Hofstaedtler wrote: * Dean Hamstead [190108 05:03]: Version: 3.4.1-4+deb8u8 It seems that 'certain work arounds' are being removed on the 1st of Feb 2019 according to https://dnsflagday.net/ I have generated this report https://ednscomp.isc.org/ednscomp/154f9de8ce (nothing secret about it), but am not clear what step I should/can/need to take with powerdns. Google hasnt yielded results - please prove me wrong. Upgrading to Debian 9 would be the recommended solution. Chris
Bug#918661: pdns-server: EDNS Compliance Steps
Package: pdns-server Version: 3.4.1-4+deb8u8 Severity: normal Dear Maintainer, It seems that 'certain work arounds' are being removed on the 1st of Feb 2019 according to https://dnsflagday.net/ I have generated this report https://ednscomp.isc.org/ednscomp/154f9de8ce (nothing secret about it), but am not clear what step I should/can/need to take with powerdns. Google hasnt yielded results - please prove me wrong. Your guidance is much appreciated Dean -- System Information: Debian Release: 8.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-042stab127.2 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages pdns-server depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.56+deb8u1 ii init-system-helpers 1.22 ii libboost-program-options1.55.0 1.55.0+dfsg-3 ii libboost-serialization1.55.01.55.0+dfsg-3 ii libbotan-1.10-0 1.10.8-2+deb8u2 ii libc6 2.19-18+deb8u10 ii libcrypto++95.6.1-6+deb8u3 ii libgcc1 1:4.9.2-10+deb8u2 ii libgmp102:6.0.0+dfsg-6 ii liblua5.1-0 5.1.5-7.1 ii libpolarssl71.3.9-2.1+deb8u4 ii libsqlite3-03.8.7.1-1+deb8u3 ii libstdc++6 4.9.2-10+deb8u2 ii lsb-base4.1+Debian13+nmu1 ii ucf 3.0030 pdns-server recommends no packages. Versions of packages pdns-server suggests: ii pdns-backend-pgsql [pdns-backend] 3.4.1-4+deb8u8 pn pdns-recursor -- debconf information: * pdns-server/localaddress: 0.0.0.0 * pdns-server/allowrecursion: 127.0.0.1
Bug#752563: [bash] Enable syslogging to a separate option or a package
+1 to this request, and related redhat has sent a patch that makes bash logging configuration via shopt, see https://lists.gnu.org/archive/html/bug-bash/2017-01/msg00053.html also, this person maintains a script which builds bash with syslog enabled, but also tweaks the log message to send the login user rather than uid, which stays the same when a user sudo's https://github.com/Mickaelh51/bash-autoinstaller-active-syslog On Tue, 24 Jun 2014 14:10:36 -0400 Tim Sattarov wrote: > Package: bash > Version: 4.3-7.1 > Severity: wishlist > Tags: security > X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org > > --- Please enter the report below this line. --- > Hello, > > I wonder if you can enable syslog feature in bash > i.e. uncomment line in config-top.h > #define SYSLOG_HISTORY > > and make it configurable through a separate config option in ini file or > compile it to a seperate package. > > Thanks > Tim > > --- System information. --- > Architecture: amd64 > Kernel: Linux 3.14-1-amd64 > > Debian Release: jessie/sid > 800 unstable http.us.debian.org > 800 unstable deb-multimedia.org > 500 stable dl.google.com > 1 experimental http.us.debian.org > > --- Package information. --- > Depends (Version) | Installed > ===-+- > base-files (>= 2.1.12) | 7.3 > debianutils (>= 2.15) | 4.4 > > > Recommends (Version) | Installed > ===-+- > bash-completion (>= 20060301-0) | 1:2.1-4 > > > Suggests (Version) | Installed > ===-+-=== > bash-doc |
Bug#915568: gitlab: postinst gets stuck on webpack selection
Package: gitlab Version: 11.3.11+dfsg-1 Severity: important Dear Maintainer, Install gets stuck on this output, answering doest seem to help Precompiling assets... Webpacking... One CLI for webpack must be installed. These are recommended choices, delivered as separate packages: - webpack-cli (https://github.com/webpack/webpack-cli) The original webpack full-featured CLI. - webpack-command (https://github.com/webpack-contrib/webpack-command) A lightweight, opinionated webpack CLI. We will use "yarn" to install the CLI via "yarn add -D". Which one do you like to install (webpack-cli/webpack-command): -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (99, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-3-cloud-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii asciidoctor1.5.8-1 ii bc 1.07.1-2+b1 ii bundler1.16.1-3 ii bzip2 1.0.6-9 ii dbconfig-pgsql 2.0.10 ii debconf [debconf-2.0] 1.5.69 ii exim4-daemon-light [mail-transport-agent] 4.91-8+b1 ii gitlab-common 11.3.11+dfsg-1 ii gitlab-shell 8.3.3+dfsg-2 ii gitlab-workhorse 6.1.1+debian-3 ii lsb-base 10.2018112800 ii nginx-full [nginx] 1.14.1-1 ii nodejs 8.11.2~dfsg-1 ii npm5.8.0+ds6-2 ii openssh-client 1:7.9p1-4 ii postgresql-client 11+197 ii postgresql-client-11 [postgresql-client] 11.1-1+b2 ii postgresql-contrib 11+197 ii rake 12.3.1-3 ii redis-server 5:5.0.2-1 ii ruby 1:2.5.1 ii ruby-ace-rails-ap 4.1.1-1 ii ruby-acts-as-taggable-on 5.0.0-2 ii ruby-addressable 2.5.2-1 ii ruby-akismet 2.0.0-1 ii ruby-arel 6.0.4-1 ii ruby-asana 0.6.0-1 ii ruby-asciidoctor-plantuml 0.0.8-1 ii ruby-asset-sync2.4.0-1 ii ruby-attr-encrypted3.1.0-1 ii ruby-babosa1.0.2-2 ii ruby-base320.3.2-3 ii ruby-batch-loader 1.2.1-1 ii ruby-bcrypt-pbkdf 1.0.0-2 ii ruby-bootstrap-form2.7.0-1 ii ruby-browser 2.5.3-1 ii ruby-carrierwave 1.2.3-1 ii ruby-charlock-holmes 0.7.6-1 ii ruby-chronic 0.10.2-3 ii ruby-chronic-duration 0.10.6-1 ii ruby-commonmarker 0.17.9-1 ii ruby-connection-pool 2.2.2-1 ii ruby-creole0.5.0-2 ii ruby-default-value-for 3.1.0-1 ii ruby-device-detector 1.0.1-2 ii ruby-devise4.4.3-1 ii ruby-devise-two-factor 3.0.3-1 ii ruby-diffy 3.2.1-1 ii ruby-doorkeeper4.4.2-1 ii ruby-doorkeeper-openid-connect 1.5.2-1 ii ruby-dropzonejs-rails 0.8.2-1 ii ruby-ed25519 1.2.4-1 ii ruby-email-reply-trimmer 0.1.6-1 ii ruby-escape-utils 1.2.1-1+b1 ii ruby-excon 0.60.0-1 ii ruby-faraday 0.13.1-2 ii ruby-fast-blank1.0.0-1+b1 ii ruby-flipper 0.13.0-3 pn ruby-flipper-active-record pn ruby-flipper-active-support-cache-store ii ruby-fog-aliyun0.2.0-1 ii ruby-fog-aws 2.0.1-1 ii ruby-fog-core 1.45.0-2 ii ruby-fog-google1.8.1-2 ii ruby-fog-local 0.3.0-1 ii ruby-fog-openstack 0.1.6-4 ii ruby-fog-rackspace 0.1.1-4 ii ruby-fogbugz 0.2.1-3 ii ruby-font-awesome-rails4.7.0.4-1 ii ruby-gemojione 3.3.0-1 ii ruby-gettext-i18n-rails1.8.0-
Bug#914577: RFP: dropwatch -- A tool for detecting and diagnosing packets being dropped
Package: wnpp Severity: wishlist * Package name: dropwatch Version : 1.5 Upstream Author : Neil Horman * URL : https://github.com/nhorman/dropwatch * License : GPL Programming Lang: C Description : A tool for detecting and diagnosing packets being dropped What is Dropwatch? Dropwatch is a project I started in an effort to improve the ability for developers and system administrator to diagnose problems in the Linux Networking stack, specifically in our ability to diagnose where packets are getting dropped. From my probing, I've come to the conclusion that there are four main shortcommings in our current environment: 1.Consolidation, or lack thereof. Currently, if you would like to check on the status of dropped packets in the kernel, you need to check at least 3 places, and possibly more: The /proc/net/snmp file, the netstat utility, the tc utility, and ethool. This project aims to consolidate several of those checks into one tool, making it easier for a sysadmin or developer to detect lost packets 2.Clarity of information. Dropped packets are not obvious. a sysadmin needs to be intimately familiar with each of the above tools to understand which events or statistics correlate to a dropped packet and which do not. While that is often self evident, it is also often not. Dropwatch aims to improve that clarity 3.Ambiguity. Even when a dropped packet is detected, the causes for those dropped packets are not always clear. Does a UDPInError mean the application receive buffer was full, or does it mean its checksum was bad? Dropwatch attempts to disambiguate the causes for dropped packets. 4.Performance. Utilties can be written to aggregate the data in the various other utilities to solve some of these problems, but such solutions require periodic polling of several interfaces, which is far from optimal, especially when lost packets are rare. This solution improves on the performance aspect by implementing a kernel feature which allows asyncronous notification of dropped packets when they happen.
Bug#914315: libwebp-dev: New version v1.0.1 released
Package: libwebp-dev Version: 0.6.1-2 Severity: wishlist Tags: upstream Dear Maintainer, Version v1.0.1 is released. This is a simply wishlist ticket hoping you will package it https://chromium.googlesource.com/webm/libwebp/+/v1.0.1 Thanks -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libwebp-dev depends on: ii libwebp6 0.6.1-2 ii libwebpdemux2 0.6.1-2 ii libwebpmux30.6.1-2 libwebp-dev recommends no packages. libwebp-dev suggests no packages. -- no debconf information Psst! It's possible that this email contains information that is on the super secret side of confidential. So if you received it accidentally, let the sender know straight away and delete it (and the email you sent them). Also, we should let you know that any emails that come and go through Winc™ might be scanned, stored or read by Winc™ at its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it sends, but we can't promise that it will be error free. So, please don't hold it against us.
Bug#913677: glusterfs-client: Hard link limit?
xfs in this case On 14/11/18 7:18 pm, Patrick Matthäi wrote: Am 14.11.2018 um 01:09 schrieb Dean Hamstead: Package: glusterfs-client Version: 4.1.5-1~bpo9+1 Severity: normal Dear Maintainer, I've not been able to determine if this is a fuse limit, a gluster limit, or something else entirely. Anyway, I have been rsync'ing from a $commercial NFS over to a new shiny gluster volume. However it seems there is hard link limit I have hit. From rsync: rsync: link "/opt/nximages/pi/ae/266c042d7ec532c9fb8bf9f81d1012512e86b5-26253/.full.jpg.23309" => 02/f6b1b71161fbd3900b5b04cc0eca8ba5ec5efd-26253/full.jpg failed: Too many links (31) rsync: link "/opt/nximages/pi/ae/266c042d7ec532c9fb8bf9f81d1012512e86b5-26253/.merch.jpg.23309" => 02/f6b1b71161fbd3900b5b04cc0eca8ba5ec5efd-26253/merch.jpg failed: Too many links (31) Hi, do you use xfs or ext4 as filesystem?
Bug#913677: glusterfs-client: Hard link limit?
Package: glusterfs-client Version: 4.1.5-1~bpo9+1 Severity: normal Dear Maintainer, I've not been able to determine if this is a fuse limit, a gluster limit, or something else entirely. Anyway, I have been rsync'ing from a $commercial NFS over to a new shiny gluster volume. However it seems there is hard link limit I have hit. >From rsync: rsync: link "/opt/nximages/pi/ae/266c042d7ec532c9fb8bf9f81d1012512e86b5-26253/.full.jpg.23309" => 02/f6b1b71161fbd3900b5b04cc0eca8ba5ec5efd-26253/full.jpg failed: Too many links (31) rsync: link "/opt/nximages/pi/ae/266c042d7ec532c9fb8bf9f81d1012512e86b5-26253/.merch.jpg.23309" => 02/f6b1b71161fbd3900b5b04cc0eca8ba5ec5efd-26253/merch.jpg failed: Too many links (31) >From /var/log/glusterfs/opt-nximages.log [2018-11-14 00:08:14.246446] W [MSGID: 114031] [client-rpc-fops_v2.c:2383:client4_0_link_cbk] 0-nximages1-client-2: remote operation failed: (/pi/c7/57da83670efc30e2c40fc61a84c64582ca5e79-1909762/thumb.png -> /pi/c7/8a9c2182416f9c8a3b676d842310ad75a2fde4-1909762/.thumb.png.23309) [Too many links] [2018-11-14 00:08:14.246532] W [MSGID: 114031] [client-rpc-fops_v2.c:2383:client4_0_link_cbk] 0-nximages1-client-1: remote operation failed: (/pi/c7/57da83670efc30e2c40fc61a84c64582ca5e79-1909762/thumb.png -> /pi/c7/8a9c2182416f9c8a3b676d842310ad75a2fde4-1909762/.thumb.png.23309) [Too many links] [2018-11-14 00:08:14.247201] W [fuse-bridge.c:565:fuse_entry_cbk] 0-glusterfs-fuse: 49760979: LINK() /pi/c7/8a9c2182416f9c8a3b676d842310ad75a2fde4-1909762/.thumb.png.23309 => -1 (Too many links) I can't seem to locate a mention of such a limit. I place this here hoping for assistance from those with more gluster experience than myself Thanks -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (98, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-0.bpo.1-cloud-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages glusterfs-client depends on: ii fuse 2.9.7-1+deb9u1 ii glusterfs-common 4.1.5-1~bpo9+1 ii libc6 2.24-11+deb9u3 ii libssl1.1 1.1.0f-3+deb9u2 ii python2.7.13-2 glusterfs-client recommends no packages. glusterfs-client suggests no packages. -- no debconf information Psst! It's possible that this email contains information that is on the super secret side of confidential. So if you received it accidentally, let the sender know straight away and delete it (and the email you sent them). Also, we should let you know that any emails that come and go through Winc™ might be scanned, stored or read by Winc™ at its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it sends, but we can't promise that it will be error free. So, please don't hold it against us.
Bug#913627: [pkg-uWSGI-devel] Bug#913627: Query: mountpoints and uwsgi 2.1
Ok thanks for a quick response. The absence of much response in their GH bugs makes me wonder if unbit people are looking or not Some PR seem to be actioned but thats about it On Tue, 13 Nov 2018 10:40:04 +0100 Jonas Smedegaard wrote: > Quoting Dean Hamstead (2018-11-13 09:15:19) > > I posted this here https://github.com/unbit/uwsgi/issues/1895 but > > didnt get a response. I wonder if debian maintainers know whats > > happening? > > > > According to this documentation mountpoints will be available in uwsgi > > 2.1 (see > > https://uwsgi-docs.readthedocs.io/en/latest/SubscriptionServer.html) > > > > The 2.1 milestone appears to have been met but there is no 2.1 tagged > > release. > > > > I am curious if this feature will find its way in to 2.0.x releases or > > if 2.1 has a future? > > Sorry, I have no special knowledge about uWSGI development. > > My guess is that 2.1 is the development branch, and as such it won't > ever get "released" but instead features from there will get > cherry-picked into the 2.0 branch. > > But that's just a guess... > > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private
Bug#913627: Query: mountpoints and uwsgi 2.1
Source: uwsgi Severity: wishlist Dear Maintainer, I posted this here https://github.com/unbit/uwsgi/issues/1895 but didnt get a response. I wonder if debian maintainers know whats happening? According to this documentation mountpoints will be available in uwsgi 2.1 (see https://uwsgi-docs.readthedocs.io/en/latest/SubscriptionServer.html) The 2.1 milestone appears to have been met but there is no 2.1 tagged release. I am curious if this feature will find its way in to 2.0.x releases or if 2.1 has a future? thanks Dean Psst! It's possible that this email contains information that is on the super secret side of confidential. So if you received it accidentally, let the sender know straight away and delete it (and the email you sent them). Also, we should let you know that any emails that come and go through Winc™ might be scanned, stored or read by Winc™ at its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it sends, but we can't promise that it will be error free. So, please don't hold it against us.
Bug#910926: RFP: nosh - an RC, init, process manager system
Package: wnpp Severity: /wishlist/ The |nosh| package is a suite of system-level utilities for initializing and running a BSD or Linux system, for managing daemons, for managing terminals, and for managing logging. Homepage: https://jdebp.eu/Softwares/nosh/ Source: ftp://repository.jdebp.info./debian/dists/stable/main/source/ The author provides their own Debian pacakges, it would be great to incorporate official packages in to Debian //
Bug#905158: python-msrestazure: Newer version required for ansible
Package: python-msrestazure Version: 0.4.13-1 Severity: normal Dear Maintainer, The newer version of Ansible reqire python-msrestazure to provide an MSIAuthentication object. The latest version packaged in debian is not up to date enough for this. Please update this package :) -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python-msrestazure depends on: ii python 2.7.15-3 ii python-keyring 13.1.0-1 python-msrestazure recommends no packages. python-msrestazure suggests no packages. -- no debconf information Psst! It's possible that this email contains information that is on the super secret side of confidential. So if you received it accidentally, let the sender know straight away and delete it (and the email you sent them). Also, we should let you know that any emails that come and go through Winc™ might be scanned, stored or read by Winc™ at its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it sends, but we can't promise that it will be error free. So, please don't hold it against us.
Bug#900739: crashing in toke.c, keyword plugin pointer is left pointing to an XS module that's been unloaded
Rolling it in to the official release would be much appreciated as it will spare us maintaining our own patched version, plus might help a few lonely travelers who are stumped on a segfault.
Bug#900739: perl: crashing in toke.c, keyword plugin pointer is left pointing to an XS module that's been unloaded
Package: perl Version: 5.24.1-3+deb9u3 Severity: important The keyword plugin pointer is left pointing to an unloaded XS module - resulting in a crash in toke.c. To reproduce is quite simple using mod_perl2 (pre)loading DBD::Oracle and Syntax::Keyword::Try (or other). ie. (install mod_perl2) cpanm Syntax::Keyword::Try (install Oracle SDK) cpanm DBD::Oracle create a /var/www/html/startup.pl with contents: use DBD::Oracle; use Syntax::Keyword::Try; 1; create a file /etc/apache2/conf-enabled/breakperl.conf with contents: PerlRequire /var/www/html/startup.pl (start apache) Apache will crash nearly instantly The core file can be examined and i have posted an example at https://gist.github.com/djzort/980a6a7e1241f3c4d036a6d68641b22c This bug is easily fixed by applying the patch in https://rt.perl.org/Public/Bug/Display.html?id=131786 It applies cleanly as-is This is already in newer versions of perl via commit fa2e45943e2b6ce22cf70dba5b47afe73c8c7c80 in perl's git branch Could this patch please be applied and a new release created -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (98, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages perl depends on: ii dpkg 1.18.24 ii libperl5.245.24.1-3+deb9u3 ii perl-base 5.24.1-3+deb9u3 ii perl-modules-5.24 5.24.1-3+deb9u3 Versions of packages perl recommends: ii netbase 5.4 ii rename 0.20-4 Versions of packages perl suggests: pn libterm-readline-gnu-perl | libterm-readline-perl-perl ii make4.1-9.1 ii perl-doc5.24.1-3+deb9u3 -- no debconf information Psst! It's possible that this email contains information that is on the super secret side of confidential. So if you received it accidentally, let the sender know straight away and delete it (and the email you sent them). Also, we should let you know that any emails that come and go through Winc™ might be scanned, stored or read by Winc™ at its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it sends, but we can't promise that it will be error free. So, please don't hold it against us.
Bug#823726: tora: New TOra release v3 is available.
please upgrade. this would be amazing On Sun, 08 May 2016 13:24:03 +0800 Caysho wrote: > Package: tora > Version: 2.1.3-2+b4 > Severity: normal > > Dear Maintainer, > > * What led up to the situation? > Checked the version in the debian repositories, it is v2. > > Current source is hosted at github. > Refer https://github.com/tora-tool/tora/wiki > > > > -- System Information: > Debian Release: stretch/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.3.0-1-amd64 (SMP w/1 CPU core) > Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages tora depends on: > ii libc6 2.22-7 > ii libgcc1 1:5.3.1-14 > ii libpq5 9.5.2-1 > ii libqscintilla2-12v5 2.9.2+dfsg-1 > ii libqt4-network 4:4.8.7+dfsg-6+b1 > ii libqt4-sql 4:4.8.7+dfsg-6+b1 > ii libqt4-xml 4:4.8.7+dfsg-6+b1 > ii libqtcore4 4:4.8.7+dfsg-6+b1 > ii libqtgui4 4:4.8.7+dfsg-6+b1 > ii libstdc++6 5.3.1-14 > > tora recommends no packages. > > tora suggests no packages. > > -- no debconf information > >
Bug#891704: fping broken with kernel ipv6.disable=1
Package: fping Version: 4.0-6 Severity: important Dear Maintainer, fping is broken with the kernel is given the option ipv6.disable=1 See https://github.com/schweikert/fping/issues/118 (patch being worked on) Also https://github.com/voidlinux/void-packages/issues/6456 My symptoms are exactly as above, so i wont post them redundantly -- Package-specific info: -rwxr-xr-x 1 root root 43904 Jan 2 20:13 /usr/bin/fping lrwxrwxrwx 1 root root 5 Jan 2 20:13 /usr/bin/fping6 -> fping /usr/bin/fping = cap_net_raw+ep -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fping depends on: ii libc62.26-6 ii libcap2-bin 1:2.25-1.2 ii netbase 5.4 fping recommends no packages. fping suggests no packages. -- no debconf information Psst! It's possible that this email contains information that is on the super secret side of confidential. So if you received it accidentally, let the sender know straight away and delete it (and the email you sent them). Also, we should let you know that any emails that come and go through Winc™ might be scanned, stored or read by Winc™ at its discretion. If you've got a question, please give us a buzz on +61 2 9335 0555 (Australia) or +64 9 271 7600 (NZ). Oh, and Winc™ does its best to avoid errors on emails it sends, but we can't promise that it will be error free. So, please don't hold it against us.
Bug#849111: nagios-plugins-contrib: Sensors gone with check_lm_sensors 4.1.1
Package: nagios-plugins-contrib Version: 21.20170222 Followup-For: Bug #849111 I just updated https://github.com/matteocorti/check_lm_sensors/issues/6 its simply that /sys has moved around a bit.
Bug#885905: roundcube: Update backports?
Package: roundcube Version: 1.1.5+dfsg.1-1~bpo8+5 Severity: wishlist File: roundcube Dear Maintainer, It would be amazing if you could update the backport of jessie. THanks! -- System Information: Debian Release: 8.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-042stab123.9 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages roundcube-core depends on: ii dbconfig-common1.8.47+nmu3+deb8u1 ii debconf [debconf-2.0] 1.5.56+deb8u1 ii dpkg 1.17.27 ii libapache2-mod-php55.6.30+dfsg-0+deb8u1 ii libmagic1 1:5.22+15-2+deb8u3 ii php-auth-sasl 1.0.6-1+deb8u1 ii php-mail-mime 1.8.9-1+deb8u1 ii php-net-sieve 1.3.2-4 ii php-net-smtp 1.6.2-2 ii php-net-socket 1.0.14-1 ii php-patchwork-utf8 1.1.25-1 ii php-pear 5.6.30+dfsg-0+deb8u1 ii php5 5.6.30+dfsg-0+deb8u1 ii php5-cli 5.6.30+dfsg-0+deb8u1 ii php5-common5.6.30+dfsg-0+deb8u1 ii php5-intl 5.6.30+dfsg-0+deb8u1 ii php5-json 1.3.6-1 ii php5-mcrypt5.6.30+dfsg-0+deb8u1 ii roundcube-pgsql1.1.5+dfsg.1-1~bpo8+5 ii ucf3.0030 Versions of packages roundcube-core recommends: ii apache2 [httpd-cgi] 2.4.10-10+deb8u11 ii apache2-mpm-prefork [httpd-cgi] 2.4.10-10+deb8u11 ii php5-gd 5.6.30+dfsg-0+deb8u1 ii php5-pspell 5.6.30+dfsg-0+deb8u1 Versions of packages roundcube-core suggests: pn php-crypt-gpg pn php-net-ldap2 pn php-net-ldap3 ii roundcube-plugins 1.1.5+dfsg.1-1~bpo8+5 -- Configuration Files: /etc/roundcube/htaccess changed [not included] -- debconf information excluded
Bug#882988: smokeping: Request backport
Package: smokeping Version: 2.6.9-1+deb8u1 Severity: wishlist Dear Maintainer, Please create jessie-backport for 2.6.11-3. Thanks for maintaining the package. -- System Information: Debian Release: 8.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-042stab123.9 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages smokeping depends on: ii adduser 3.113+nmu3 ii debianutils 4.4+b1 ii fping 3.10-2 ii libcgi-fast-perl1:2.04-1 ii libconfig-grammar-perl 1.10-2 ii libdigest-hmac-perl 1.03+dfsg-1 ii libjs-cropper 1.2.2-1 ii libjs-prototype 1.7.1-3 ii libjs-scriptaculous 1.9.0-2 ii librrds-perl1.4.8-1.2 ii libsnmp-session-perl1.13-1.1 ii liburi-perl 1.64-1 ii libwww-perl 6.08-1 ii lsb-base4.1+Debian13+nmu1 ii perl5.20.2-3+deb8u9 ii ucf 3.0030 Versions of packages smokeping recommends: ii apache2 [httpd-cgi] 2.4.10-10+deb8u11 ii apache2-mpm-prefork [httpd-cgi] 2.4.10-10+deb8u11 ii dnsutils 1:9.9.5.dfsg-9+deb8u14 ii echoping 6.0.2-8 ii libsocket6-perl 0.25-1+b1 Versions of packages smokeping suggests: ii curl 7.38.0-4+deb8u7 ii exim4-daemon-heavy [mail-transport-agent] 4.84.2-2+deb8u4 pn libauthen-radius-perl ii libio-socket-ssl-perl 2.002-2+deb8u2 ii libnet-dns-perl0.81-2+deb8u1 pn libnet-ldap-perl pn libnet-telnet-perl ii openssh-client 1:6.7p1-5+deb8u3 -- Configuration Files: /etc/smokeping/apache2.conf changed [not included] /etc/smokeping/config.d/General changed [not included] -- no debconf information
Bug#882987: smokeping: Add redirect to smokeping.cgi in config file
Package: smokeping Version: 2.6.9-1+deb8u1 Severity: wishlist Dear Maintainer, It would be handing if you would be so kind as to add this line to the config file, such that /smokeping will redirect to /smokeping/smokping.cgi RedirectMatch "^/smokeping/?$" /smokeping/smokeping.cgi Cheers -- System Information: Debian Release: 8.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-042stab123.9 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages smokeping depends on: ii adduser 3.113+nmu3 ii debianutils 4.4+b1 ii fping 3.10-2 ii libcgi-fast-perl1:2.04-1 ii libconfig-grammar-perl 1.10-2 ii libdigest-hmac-perl 1.03+dfsg-1 ii libjs-cropper 1.2.2-1 ii libjs-prototype 1.7.1-3 ii libjs-scriptaculous 1.9.0-2 ii librrds-perl1.4.8-1.2 ii libsnmp-session-perl1.13-1.1 ii liburi-perl 1.64-1 ii libwww-perl 6.08-1 ii lsb-base4.1+Debian13+nmu1 ii perl5.20.2-3+deb8u9 ii ucf 3.0030 Versions of packages smokeping recommends: ii apache2 [httpd-cgi] 2.4.10-10+deb8u11 ii apache2-mpm-prefork [httpd-cgi] 2.4.10-10+deb8u11 ii dnsutils 1:9.9.5.dfsg-9+deb8u14 ii echoping 6.0.2-8 ii libsocket6-perl 0.25-1+b1 Versions of packages smokeping suggests: ii curl 7.38.0-4+deb8u7 ii exim4-daemon-heavy [mail-transport-agent] 4.84.2-2+deb8u4 pn libauthen-radius-perl ii libio-socket-ssl-perl 2.002-2+deb8u2 ii libnet-dns-perl0.81-2+deb8u1 pn libnet-ldap-perl pn libnet-telnet-perl ii openssh-client 1:6.7p1-5+deb8u3 -- Configuration Files: /etc/smokeping/apache2.conf changed [not included] /etc/smokeping/config.d/General changed [not included] -- no debconf information
Bug#584768: timidty
This seems to be at the heart of the problem... sudo -u timidity timidity -Os -iA No protocol specified xcb_connection_has_error() returned true Home directory not accessible: Permission denied No protocol specified ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave Can't open pcm device 'default'. Couldn't open ALSA pcm device (`s') This seems to "fix" things chown -R timidity: /etc/timidity which allows a ~timidity/.config/pulse directory (and content) to be created after which timidity seems to start having /etc/timidity owned as timidity isnt ideal. but this is the source of the problem
Bug#847048: [pkg-lxc-devel] Bug#847048: lxc: centos6 fails to start after u/g to 2.0.6
It might be something that lxc-start needs to check based upon some config parameter. I dont know if there is a way of getting info from the ABI or if its just a matter of checking the kernel version and/or /proc/cmdline. Such a config parameter could then be placed in the centos6 template and others as needed. At start up, lxc-start could then fail gracefully with a helpful message? On 06/12/16 19:09, Evgeni Golov wrote: Hey, On Tue, Dec 06, 2016 at 05:46:58PM +1100, Dean Hamstead wrote: Yes, Solution was to use "vsyscall=emulate" on the host kernel command line (ie on my laptop). Exactly the same issue as: https://github.com/CentOS/sig-cloud-instance-images/issues/62 So I am guessing the issue was actually the kernel upgrading. See also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1018415 Yeah, I knew what it was as soon as you posted the dmesg output, but was on mobile, so was not in the mood to write a proper answer, sorry. Glad you have a solution here. Let's see if we can talk the kernel ppl into re-thinking this. Or we need a big fat warning somewhere. Thanks for debugging
Bug#847048: [pkg-lxc-devel] Bug#847048: lxc: centos6 fails to start after u/g to 2.0.6
Yes, Solution was to use "vsyscall=emulate" on the host kernel command line (ie on my laptop). Exactly the same issue as: https://github.com/CentOS/sig-cloud-instance-images/issues/62 So I am guessing the issue was actually the kernel upgrading. See also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1018415 On 05/12/16 21:42, Evgeni Golov wrote: On Mon, Dec 05, 2016 at 08:59:07PM +1100, Dean Hamstead wrote: it seems if i drop back to 2.0.5 the problem still occurs. so i am guessing some other thing upgraded and its not lxc-start's fault can you try an older lxcfs, it was updated at (almost) the same time. mind you, just downgrading the package is not enough, the daemon is not restarted automatically as this would break running containers. restart it yourself or reboot :) On 05/12/16 19:25, Evgeni Golov wrote: Hi Dean, thanks for the report, On Mon, Dec 05, 2016 at 05:58:40PM +1100, Dean Hamstead wrote: Since upgrading, centos6 containers fail to start. Is that a regression from 2.0.5? Or anything older? I am guessing that upstart is doing something crappy and lxc is now carefull enough to notice? Could totally be, but I would guess upstream would have tested with upstart (on older Ubuntu LTS releases). Well, let's see if I can reproduce tonight. Greets Evgeni
Bug#847048: [pkg-lxc-devel] Bug#847048: lxc: centos6 fails to start after u/g to 2.0.6
Seems to be the same issue: https://github.com/CentOS/sig-cloud-instance-images/issues/62 On 05/12/16 21:42, Evgeni Golov wrote: On Mon, Dec 05, 2016 at 08:59:07PM +1100, Dean Hamstead wrote: it seems if i drop back to 2.0.5 the problem still occurs. so i am guessing some other thing upgraded and its not lxc-start's fault can you try an older lxcfs, it was updated at (almost) the same time. mind you, just downgrading the package is not enough, the daemon is not restarted automatically as this would break running containers. restart it yourself or reboot :) On 05/12/16 19:25, Evgeni Golov wrote: Hi Dean, thanks for the report, On Mon, Dec 05, 2016 at 05:58:40PM +1100, Dean Hamstead wrote: Since upgrading, centos6 containers fail to start. Is that a regression from 2.0.5? Or anything older? I am guessing that upstart is doing something crappy and lxc is now carefull enough to notice? Could totally be, but I would guess upstream would have tested with upstart (on older Ubuntu LTS releases). Well, let's see if I can reproduce tonight. Greets Evgeni
Bug#847048: [pkg-lxc-devel] Bug#847048: lxc: centos6 fails to start after u/g to 2.0.6
This seems relevant from syslog: Dec 6 16:36:43 cliffjumper kernel: [22402.625004] lxcbr0: port 1(veth4KDYR9) entered blocking state Dec 6 16:36:43 cliffjumper kernel: [22402.625005] lxcbr0: port 1(veth4KDYR9) entered disabled state Dec 6 16:36:43 cliffjumper kernel: [22402.625103] device veth4KDYR9 entered promiscuous mode Dec 6 16:36:43 cliffjumper kernel: [22402.625310] IPv6: ADDRCONF(NETDEV_UP): veth4KDYR9: link is not ready Dec 6 16:36:43 cliffjumper kernel: [22402.679427] eth0: renamed from vethKOVFCJ Dec 6 16:36:43 cliffjumper kernel: [22402.697517] IPv6: ADDRCONF(NETDEV_CHANGE): veth4KDYR9: link becomes ready Dec 6 16:36:43 cliffjumper kernel: [22402.697570] lxcbr0: port 1(veth4KDYR9) entered blocking state Dec 6 16:36:43 cliffjumper kernel: [22402.697572] lxcbr0: port 1(veth4KDYR9) entered forwarding state Dec 6 16:36:43 cliffjumper kernel: [22402.811868] sh[17085] *vsyscall attempted with vsyscall=none* ip:ff600400 cs:33 sp:7ffd2b8d2078 ax:ff600400 si:7ffd2b8d3f4a di:0 Dec 6 16:36:43 cliffjumper kernel: [22402.811872] sh[17085]: segfault at ff600400 ip ff600400 sp 7ffd2b8d2078 error 15 Dec 6 16:36:43 cliffjumper kernel: [22402.812093] init[17056]*vsyscall attempted with vsyscall=none* ip:ff600400 cs:33 sp:7ffea782d3f8 ax:ff600400 si:7fd2d4b31039 di:7ffea782d4c8 Dec 6 16:36:43 cliffjumper kernel: [22402.812230] sh[17086] vsyscall attempted with vsyscall=none ip:ff600400 cs:33 sp:7fff0386f648 ax:ff600400 si:7fff03870f60 di:0 Dec 6 16:36:43 cliffjumper kernel: [22402.812233] sh[17086]: segfault at ff600400 ip ff600400 sp 7fff0386f648 error 15 Dec 6 16:36:43 cliffjumper kernel: [22402.812988] init[17056] vsyscall attempted with vsyscall=none ip:ff600400 cs:33 sp:7ffea782c9e8 ax:ff600400 si:7fd2d4b31039 di:7ffea782cab8 Dec 6 16:36:43 cliffjumper kernel: [22402.813643] lxcbr0: port 1(veth4KDYR9) entered disabled state Dec 6 16:36:43 cliffjumper kernel: [22402.816241] device veth4KDYR9 left promiscuous mode Dec 6 16:36:43 cliffjumper kernel: [22402.816244] lxcbr0: port 1(veth4KDYR9) entered disabled state On 05/12/16 21:42, Evgeni Golov wrote: On Mon, Dec 05, 2016 at 08:59:07PM +1100, Dean Hamstead wrote: it seems if i drop back to 2.0.5 the problem still occurs. so i am guessing some other thing upgraded and its not lxc-start's fault can you try an older lxcfs, it was updated at (almost) the same time. mind you, just downgrading the package is not enough, the daemon is not restarted automatically as this would break running containers. restart it yourself or reboot :) On 05/12/16 19:25, Evgeni Golov wrote: Hi Dean, thanks for the report, On Mon, Dec 05, 2016 at 05:58:40PM +1100, Dean Hamstead wrote: Since upgrading, centos6 containers fail to start. Is that a regression from 2.0.5? Or anything older? I am guessing that upstart is doing something crappy and lxc is now carefull enough to notice? Could totally be, but I would guess upstream would have tested with upstart (on older Ubuntu LTS releases). Well, let's see if I can reproduce tonight. Greets Evgeni
Bug#847048: [pkg-lxc-devel] Bug#847048: lxc: centos6 fails to start after u/g to 2.0.6
it seems if i drop back to 2.0.5 the problem still occurs. so i am guessing some other thing upgraded and its not lxc-start's fault On 05/12/16 19:25, Evgeni Golov wrote: Hi Dean, thanks for the report, On Mon, Dec 05, 2016 at 05:58:40PM +1100, Dean Hamstead wrote: Since upgrading, centos6 containers fail to start. Is that a regression from 2.0.5? Or anything older? I am guessing that upstart is doing something crappy and lxc is now carefull enough to notice? Could totally be, but I would guess upstream would have tested with upstart (on older Ubuntu LTS releases). Well, let's see if I can reproduce tonight. Greets Evgeni
Bug#847048: [pkg-lxc-devel] Bug#847048: lxc: centos6 fails to start after u/g to 2.0.6
FYI i do not have lxcfs installed after down'ng to 2.0.5 and restarting lxc, still the same issue. Dean On 05/12/16 21:42, Evgeni Golov wrote: On Mon, Dec 05, 2016 at 08:59:07PM +1100, Dean Hamstead wrote: it seems if i drop back to 2.0.5 the problem still occurs. so i am guessing some other thing upgraded and its not lxc-start's fault can you try an older lxcfs, it was updated at (almost) the same time. mind you, just downgrading the package is not enough, the daemon is not restarted automatically as this would break running containers. restart it yourself or reboot :) On 05/12/16 19:25, Evgeni Golov wrote: Hi Dean, thanks for the report, On Mon, Dec 05, 2016 at 05:58:40PM +1100, Dean Hamstead wrote: Since upgrading, centos6 containers fail to start. Is that a regression from 2.0.5? Or anything older? I am guessing that upstart is doing something crappy and lxc is now carefull enough to notice? Could totally be, but I would guess upstream would have tested with upstart (on older Ubuntu LTS releases). Well, let's see if I can reproduce tonight. Greets Evgeni
Bug#847048: [pkg-lxc-devel] Bug#847048: lxc: centos6 fails to start after u/g to 2.0.6
This seems to be the same issue: https://github.com/lxc/lxc/issues/602 Sadly, there isnt any meaningful conclusion. On 05/12/16 21:42, Evgeni Golov wrote: On Mon, Dec 05, 2016 at 08:59:07PM +1100, Dean Hamstead wrote: it seems if i drop back to 2.0.5 the problem still occurs. so i am guessing some other thing upgraded and its not lxc-start's fault can you try an older lxcfs, it was updated at (almost) the same time. mind you, just downgrading the package is not enough, the daemon is not restarted automatically as this would break running containers. restart it yourself or reboot :) On 05/12/16 19:25, Evgeni Golov wrote: Hi Dean, thanks for the report, On Mon, Dec 05, 2016 at 05:58:40PM +1100, Dean Hamstead wrote: Since upgrading, centos6 containers fail to start. Is that a regression from 2.0.5? Or anything older? I am guessing that upstart is doing something crappy and lxc is now carefull enough to notice? Could totally be, but I would guess upstream would have tested with upstart (on older Ubuntu LTS releases). Well, let's see if I can reproduce tonight. Greets Evgeni
Bug#847048: [pkg-lxc-devel] Bug#847048: lxc: centos6 fails to start after u/g to 2.0.6
yes, I was previously running 2.0.5 fwiw im using this with vagrant-lxc, although as i begun having problems i peeled a layer back and used the lxc tools directly. lxc containers of centos6 created via lxc-create also have the exact same problem. whilst debian containers are fine. On 05/12/16 19:25, Evgeni Golov wrote: Hi Dean, thanks for the report, On Mon, Dec 05, 2016 at 05:58:40PM +1100, Dean Hamstead wrote: Since upgrading, centos6 containers fail to start. Is that a regression from 2.0.5? Or anything older? I am guessing that upstart is doing something crappy and lxc is now carefull enough to notice? Could totally be, but I would guess upstream would have tested with upstart (on older Ubuntu LTS releases). Well, let's see if I can reproduce tonight. Greets Evgeni
Bug#847048: lxc: centos6 fails to start after u/g to 2.0.6
Package: lxc Version: 1:2.0.6-1 Severity: normal Dear Maintainer, Since upgrading, centos6 containers fail to start. They dont even get far enough along to get a console. I run them with the following: lxc-start -l DEBUG -F -n blah -o /tmp/lxc.log lxc-start 20161205015048.219 NOTICE lxc_start - start.c:start:1420 - Exec'ing "/sbin/init". lxc-start 20161205175048.220 NOTICE lxc_start - start.c:post_start:1431 - Started "/sbin/init" with pid "25816". lxc-start 20161205175048.220 WARN lxc_start - start.c:signal_handler:322 - Invalid pid for SIGCHLD. Received pid 25801, expected pid 25816. lxc-start 20161205175048.247 DEBUGlxc_start - start.c:signal_handler:326 - Container init process 25816 exited. lxc-start 20161205175048.247 DEBUGlxc_start - start.c:__lxc_start:1374 - Unknown exit status for container "conform_default_1480920274687_62335" init 11. lxc-start 20161205175048.247 DEBUGlxc_start - start.c:__lxc_start:1379 - Pushing physical nics back to host namespace lxc-start 20161205175048.247 DEBUGlxc_start - start.c:__lxc_start:1382 - Tearing down virtual network devices used by container "conform_default_1480920274687_62335". lxc-start 20161205175048.247 INFO lxc_conf - conf.c:lxc_delete_network:2926 - Interface "eth0" with index 33 already deleted or existing in different network namespace. lxc-start 20161205175048.312 INFO lxc_conf - conf.c:lxc_delete_network:2961 - Removed interface "vethSTER51" from host. lxc-start 20161205175048.312 INFO lxc_error - error.c:lxc_error_set_and_log:54 - Child <25816> ended on signal (11). I am guessing that upstart is doing something crappy and lxc is now carefull enough to notice? -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lxc depends on: ii init-system-helpers 1.46 ii libapparmor1 2.10.95-7 ii libc62.24-7 ii libcap2 1:2.25-1 ii liblxc1 1:2.0.6-1 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.6-3 ii lsb-base 9.20161125 ii python3-lxc 1:2.0.6-1 pn python3:any Versions of packages lxc recommends: ii bridge-utils 1.5-10 ii debootstrap 1.0.87 ii dirmngr 2.1.16-2 ii dnsmasq-base 2.76-4.1 ii gnupg 2.1.16-2 ii iptables 1.6.0-4 pn libpam-cgfs pn lxcfs ii openssl 1.1.0c-2 ii rsync 3.1.2-1 pn uidmap Versions of packages lxc suggests: pn apparmor pn btrfs-tools ii lvm2 2.02.167-1 -- Configuration Files: /etc/lxc/default.conf changed: lxc.network.type = veth lxc.network.flags = up lxc.network.link = lxcbr0 lxc.network.name = eth0 -- no debconf information
Bug#845165: vagrant-lxc: vagrant ssh key with wrong permissions, vm creation fails
Package: vagrant-lxc Version: 1.2.1-2 Severity: important Dear Maintainer, When vagrant-lxc places its authorized_keys file in to a new centos7 vm's ~vagrant/.ssh directory, it does so with too permissive ownership. As a result, the centos7 vm's ssh wont allow ssh login. I can work around this by manually running the following in another terminal, whilst the vm is being created chmod 600 /var/lib/lxc//rootfs/home/vagrant/.ssh/authorized_keys Here is the main terminal output, the "Authenticaion failure" will repeat over and over and eventually fail. The following examples shows when i perform the manual work around above. dean@cliffjumper:~/git/stash/conform-OIE-module$ vagrant up --provider=lxc Bringing machine 'default' up with 'lxc' provider... ==> default: Importing base box 'goodsmileduck/centos-7-lxc'... ==> default: Checking if box 'goodsmileduck/centos-7-lxc' is up to date... ==> default: Setting up mount entries for shared folders... default: /foo-module => /home/dean/git/stash/my-foo-module ==> default: Starting container... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 10.0.3.252:22 default: SSH username: vagrant default: SSH auth method: private key default: default: Vagrant insecure key detected. Vagrant will automatically replace default: this with a newly generated keypair for better security. default: default: Inserting generated public key within guest... default: Removing insecure key from the guest if it's present... default: Key inserted! Disconnecting and reconnecting using new SSH key... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying... ==> default: Machine booted and ready! ==> default: Running provisioner: shell... default: Running: inline script ==> default: Loaded plugins: fastestmirror ==> default: Determining fastest mirrors ==> default: * base: centos.mirror.crucial.com.au ==> default: * extras: centos.mirror.crucial.com.au ==> default: * updates: centos.mirror.crucial.com.au ==> default: Resolving Dependencies -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vagrant-lxc depends on: ii lxc 1:2.0.5-1 ii redir2.2.1-13 ii ruby 1:2.3.0+4 ii vagrant 1.8.5+dfsg-2 vagrant-lxc recommends no packages. vagrant-lxc suggests no packages. -- no debconf information
Bug#834689: exim4-config: Add more special ips to ingore_target_hosts
Package: exim4-config Version: 4.84.2-2+deb8u1 Severity: wishlist Dear Maintainer, In /etc/exim4/conf.d/router/200_exim4-config_primary, it would be terrific to expand out the special use ip addresses in the ignore_target_hosts directive >From https://github.com/Exim/exim/wiki/Q0319: ignore_target_hosts = \ # Hosts on "this network"; RFC 1700 (page 4) states that these # are only allowed as source addresses 0.0.0.0/8 : \ # Private networks, RFC 1918 10.0.0.0/8 : 172.16.0.0/12 : 192.168.0.0/16 : \ # Internet host loopback address, RFC 1700 (page 5) 127.0.0.0/8 : \ # "Link local" block 169.254.0.0/16 : \ # "TEST-NET" - should not appear on the public Internet 192.0.2.0/24 : \ # 6to4 relay anycast addresses, RFC 3068 192.88.99.0/24 : \ # Network interconnect device benchmark testing, RFC 2544 198.18.0.0/15 : \ # Multicast addresses, RFC 3171 224.0.0.0/4 : \ # Reserved for future use, RFC 1700 (page 4) 240.0.0.0/4 This is missing TEST-NET-2: 198.51.100.0 - 198.51.100.255 | 198.51.100.0/24 TEST-NET-3: 203.0.113.0 - 203.0.113.255 | 203.0.113.0/24 CGNAT: 100.64.0.0 - 100.127.255.255 | 100.64.0.0/10 Probably also Unique local addresses: fd00::/8 -- Package-specific info: Exim version 4.84_2 #1 built 25-Jul-2016 18:59:39 Copyright (c) University of Cambridge, 1995 - 2014 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2014 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS move_frozen_messages Content_Scanning DKIM Old_Demime PRDR OCSP Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Configuration file is /var/lib/exim4/config.autogenerated -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-042stab116.1 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages exim4-config depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.56 exim4-config recommends no packages. exim4-config suggests no packages. -- Configuration Files: /etc/exim4/conf.d/acl/00_exim4-config_header changed [not included] /etc/exim4/conf.d/acl/30_exim4-config_check_mail changed [not included] /etc/exim4/conf.d/acl/30_exim4-config_check_rcpt changed [not included] /etc/exim4/conf.d/acl/40_exim4-config_check_data changed [not included] /etc/exim4/conf.d/auth/30_exim4-config_examples changed [not included] /etc/exim4/conf.d/main/01_exim4-config_listmacrosdefs changed [not included] /etc/exim4/conf.d/main/02_exim4-config_options changed [not included] /etc/exim4/conf.d/rewrite/31_exim4-config_rewriting changed [not included] /etc/exim4/conf.d/router/200_exim4-config_primary changed [not included] /etc/exim4/conf.d/router/300_exim4-config_real_local changed [not included] /etc/exim4/conf.d/router/400_exim4-config_system_aliases changed [not included] /etc/exim4/conf.d/router/600_exim4-config_userforward changed [not included] /etc/exim4/conf.d/router/700_exim4-config_procmail changed [not included] /etc/exim4/conf.d/router/800_exim4-config_maildrop changed [not included] /etc/exim4/conf.d/router/850_exim4-config_lowuid changed [not included] /etc/exim4/conf.d/router/900_exim4-config_local_user changed [not included] /etc/exim4/conf.d/transport/30_exim4-config_address_file changed [not included] /etc/exim4/conf.d/transport/30_exim4-config_address_pipe changed [not included] /etc/exim4/conf.d/transport/30_exim4-config_mail_spool changed [not included] /etc/exim4/conf.d/transport/30_exim4-config_maildir_home changed [not included] /etc/exim4/conf.d/transport/30_exim4-config_maildrop_pipe changed [not included] /etc/exim4/conf.d/transport/30_exim4-config_procmail_pipe changed [not included] /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp changed [not included] /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smarthost changed [not included] /etc/exim4/conf.d/transport/35_exim4-config_address_directory changed [not included] /etc/exim4/exim4.conf.template changed [not included] -- debconf information excluded
Bug#656096: Can be fixed?
any chance this can be fixed? ubuntu has had the fix for years
Bug#808304: rancid: Rancid in backports
Source: rancid Severity: wishlist Dear Maintainer, Thank you for all your hard work in keeping this package updated in debian. Would it be possible to have 3.2 in backports? Cheers
Bug#734453: [Pkg-nagios-devel] Bug#734453: nagios3: Please package v.4
Nagios 4 seems very active and still GPL? https://github.com/NagiosEnterprises/nagioscore I would like to understand why its dead? On Tue, 7 Jan 2014 12:08:31 +0100 Alexander Wirt wrote: > On Tue, 07 Jan 2014, Tim Wootton wrote: > > > Package: nagios3 > > Version: 3 > > Severity: wishlist > > > > Dear Maintainer, > > > > please consider packaging 4.02 (latest stable at time of report) > I won't do this. Nagios is a dead horse and is far away from opensource this > days. I'll support nagios3 as long as possible and icinga(1|2) and naemon. > > You should choose one of those. > > Alex > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#783910: dsc-statistics-collector: New upstream version dsc-201502251630.tar.gz
Package: dsc-statistics-collector Version: 201203250530-2 Severity: wishlist New upstream version is available at http://dns.measurement-factory.com/tools/dsc/download/dsc-201502251630.tar.gz -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dsc-statistics-collector depends on: ii adduser3.113+nmu3 ii cron 3.0pl1-127 ii geoip-database 20150413-1 ii iproute1:3.16.0-2 ii libc6 2.19-18 ii libgcc11:4.9.2-10 ii libgeoip1 1.6.2-4 ii libpcap0.8 1.6.2-2 ii libproc-pid-file-perl 1.27-3 ii libstdc++6 4.9.2-10 dsc-statistics-collector recommends no packages. Versions of packages dsc-statistics-collector suggests: ii rsync 3.1.1-3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#780087: awstats: baiduspider not a bot
Package: awstats Version: 7.0~dfsg-7 Severity: normal Baiduspider doesnt seem to be recognised as a bot any more. here is a line from my log 220.181.108.182 - - [08/Mar/2015:12:38:12 +1100] "GET / HTTP/1.1" 301 627 "-" "Mozilla/5.0 (compatible; Baiduspider/2.0; +http://www.baidu.com/search/spider.html)" -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-042stab090.5 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages awstats depends on: ii perl 5.14.2-21+deb7u2 Versions of packages awstats recommends: ii coreutils 8.13-3.5 ii libnet-xwhois-perl 0.90-3 Versions of packages awstats suggests: ii apache2 2.2.22-13+deb7u4 ii apache2-mpm-prefork [httpd] 2.2.22-13+deb7u4 pn libgeo-ipfree-perl ii libnet-dns-perl 0.66-2+b2 ii libnet-ip-perl 1.25-3 ii liburi-perl 1.60-1 -- Configuration Files: /etc/awstats/awstats.conf.local changed: EnableLockForUpdate=1 BuildReportFormat=xhtml SiteDomain="saito.fragfest.com.au" -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#738101: Push to backports?
Would it be possible to push this to backports? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752479: Version 1.0.0 released in April; version 1.0.1 in May
perhaps the best option is to ship 'roundcube1' packages without an automatic upgrade path? this will mean that new installs can avoid 0.9.5, keen people can manually migrated and others can wait as some automated migration paths are created by the community. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#764302: shorewall: request backport
Package: shorewall Version: 4.6.3.4-1 Severity: wishlist Dear Maintainer, Thank you for your hard work in maintaining this package. I would like to request that a backport version be created to bring newer features to older releases of Debian. Thanks! Dean -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages shorewall depends on: ii bc 1.06.95-9 ii debconf [debconf-2.0] 1.5.53 ii iproute1:3.16.0-2 ii iproute2 3.16.0-2 ii iptables 1.4.21-2 ii perl-modules 5.20.1-1 ii shorewall-core 4.6.3.4-1 shorewall recommends no packages. Versions of packages shorewall suggests: ii make 4.0-8 pn shorewall-doc -- Configuration Files: /etc/shorewall/conntrack [Errno 13] Permission denied: u'/etc/shorewall/conntrack' /etc/shorewall/params [Errno 13] Permission denied: u'/etc/shorewall/params' -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756658: Fix
It seems this fixes it. But two steps are required. Firstly, i had to enable ldap again in the database via update owncloud.oc_appconfig set configvalue ='yes' where appid='user_ldap' and configkey='enabled' limit 1; At this point, the owncloud install will want to 'upgrade' again in the web interface (even if it was previously upgraded). It will fail. Secondly, as i am running via wheezy-backports i had to manually install php-doctrine-dbal_2.4.2-4_all.deb (download it and dpkg -i) The 'upgrade' via the web interface then succeed to update the schema. Hopefully the backport will be updated? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#752857: mysql-workbench: segfault
looks good now, no crashes. thanks! On 2014-09-13 19:31, Dmitry Smirnov wrote: Dear Dean, Can you reproduce this problem on 6.1.7? It looks like it may not be affected any more. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744369: Updating Java does not help
I am seeing the exact same issue. I am running 'sid' and merely installed via apt-get install --no-install-recommends netbeans dean@cliffjumper:~$ netbeans java.lang.NoClassDefFoundError: java/nio/file/InvalidPathException at org.openide.filesystems.FileUtil.normalizeFileImpl(Unknown Source) at org.openide.filesystems.FileUtil.normalizeFile(Unknown Source) at org.netbeans.core.startup.TopLogging.printSystemInfo(Unknown Source) at org.netbeans.core.startup.TopLogging.initialize(Unknown Source) at org.netbeans.core.startup.TopLogging.initialize(Unknown Source) at org.netbeans.core.startup.CLIOptions.initialize(Unknown Source) at org.netbeans.core.startup.Main.start(Unknown Source) at org.netbeans.core.startup.TopThreadGroup.run(Unknown Source) at java.lang.Thread.run(Thread.java:701) Caused by: java.lang.ClassNotFoundException: java.nio.file.InvalidPathException at java.net.URLClassLoader$1.run(URLClassLoader.java:217) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:323) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) ... 9 more dean@cliffjumper:~$ java -version java version "1.7.0_65" OpenJDK Runtime Environment (IcedTea 2.5.1) (7u65-2.5.1-4) OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) dean@cliffjumper:~$ On Sun, 13 Apr 2014 22:34:46 +0300 Victor Porton wrote: But updating to java version "1.7.0_51" OpenJDK Runtime Environment (IcedTea 2.4.6) (7u51-2.4.6-1) OpenJDK Server VM (build 24.51-b03, mixed mode) does not help (even thought I have updated /usr/bin/java to point to the correct version of Java). -- Victor Porton - http://portonvictor.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754973: fixed in blueman 1.23-git201407171232-2
Hi Christopher The file i downloaded 30588c3972ad4111acf62045f1044bfb blueman_1.23-git201407171232-2_amd64.deb Seems to want to install all these files The following extra packages will be installed: gir1.2-appindicator3-0.1 gir1.2-atk-1.0 gir1.2-freedesktop gir1.2-gconf-2.0 gir1.2-gdkpixbuf-2.0 gir1.2-gtk-3.0 gir1.2-notify-0.7 gir1.2-pango-1.0 libappindicator3-1 libdbusmenu-glib4 libdbusmenu-gtk3-4 libindicator3-7 Its possible i have leaped to a hasty conclusion Dean On 2014-08-15 19:22, Christopher Schramm wrote: Hi Dean, This new version seems to change blueman from being a gtk-only piece of software to something bound inseparably to gnome. why is that? The changes in dependencies primarily represent the switch from GTK+ 2 to GTK+ 3 and thus to GObject Introspection, since that's the preferred (or only?) GTK+ 3 Python binding. Here are the changed dependencies: python-gtk2 (>= 2.12) -> gir1.2-gtk-3.0, gir1.2-gdkpixbuf-2.0, gir1.2-glib-2.0, gir1.2-pango-1.0, python-gi-cairo (*) python-notify -> gir1.2-notify-0.7 python-gconf -> gir1.2-gconf-2.0 (**) python-appindicator -> gir1.2-appindicator3-0.1 (*) gdkpixbuf, glib, pango, and cairo were all dependencies of python-gtk2, so there's nothing new here although the list of immediate dependencies got longer (**) gconf shall be dropped in the near future upstream So I can't see any reason for your accusation, but of course you're always welcome to propose ways of avoiding specific dependencies upstream. The focus of blueman are still desktops like Xfce or MATE. Gnome is definitely not a target desktop, since it ships its own bluetooth component. Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754973: fixed in blueman 1.23-git201407171232-2
This new version seems to change blueman from being a gtk-only piece of software to something bound inseparably to gnome. Which is a real shame as it used to be excellent for use with xfce (or other) when a user wants to avoid gnome-bloat. On Tue, 05 Aug 2014 21:35:04 + Christopher Schramm wrote: Source: blueman Source-Version: 1.23-git201407171232-2 We believe that the bug you reported is fixed in the latest version of blueman, 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 754...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christopher Schramm (supplier of updated blueman 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, 05 Aug 2014 10:35:00 +0200 Source: blueman Binary: blueman Architecture: source amd64 Version: 1.23-git201407171232-2 Distribution: unstable Urgency: low Maintainer: Christopher Schramm Changed-By: Christopher Schramm Description: blueman - Graphical bluetooth manager Closes: 741961 754973 Changes: blueman (1.23-git201407171232-2) unstable; urgency=low . * Upstream snapshot for unstable (Closes: #754973, #741961) Checksums-Sha1: 9e9b5b339b4ebe80550b7a56aef5129e6c144098 2016 blueman_1.23-git201407171232-2.dsc e6af770daf16c061cfc8524aaad2dc7e9e190fe2 4324 blueman_1.23-git201407171232-2.debian.tar.xz 4b3ba5fb7b25e5694048aea28bc00643648b9ff4 449576 blueman_1.23-git201407171232-2_amd64.deb Checksums-Sha256: 6fe5fcbef0386cf170d6641058ee585da4b01a27fd4044f6ed8a7b03f8afa3cb 2016 blueman_1.23-git201407171232-2.dsc 874af5e9a5644260f03cff285bfad0689dbb0dae0fe99491c29745fa97d1ba6d 4324 blueman_1.23-git201407171232-2.debian.tar.xz a2228cf2992c773b36896f85f690a51d66e189adf09fa3956f252bd2dc58cd22 449576 blueman_1.23-git201407171232-2_amd64.deb Files: 30588c3972ad4111acf62045f1044bfb 449576 x11 optional blueman_1.23-git201407171232-2_amd64.deb 932b4abcc7157d85ebf5f9e5b7159095 2016 x11 optional blueman_1.23-git201407171232-2.dsc 0af19f3d7fe6fd0581d94f97080bec10 4324 x11 optional blueman_1.23-git201407171232-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT4TT7AAoJEDIkf7tArR+m244P/0lDD69DCk8QQOlHGSfKd5FP eIstilM+mZ/G6nMksyUsy2X3oYywDGEr91mkZVBh4IHhCpaTCL1238b7UV7R/a8v -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754830: Info received (Second part of bug not fixed)
possibly the rfcomm sections can simply be removed as they seem to be a convenience only? 'rfcomm bind all' is no longer valid, also 'rfcomm unbind' is similarly no longer a valid command as binding is now per-device, it seems this should be config option in the defaults file? On Wed, 30 Jul 2014 00:15:23 +0200 Andreas Eriksson wrote: Hi again. It seems that "rfcomm bind all" isn't a thing that works in bluez 5.x, by design, so I think that the bug here as far as debian is concerned is that the init script tries to run rfcomm at all. You now have to run rfcomm for each connection individually, the command doesn't accept 'all'. The reason my device doesn't work with 5.x seems more likely to be because it uses bluez-alsa and the bluez-alsa version in sid is still 4.x and not 5.x. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756577: awstats: XML Parsing Error: not well-formed
Package: awstats Version: 7.0~dfsg-7 Severity: normal Clicking the list of "Last visit" hosts, if you then click the "?" links which pop up the "hostinfo" plugin details - iceweasel occasionally complains something like: XML Parsing Error: not well-formed Location: http://xx/cgi-bin/awstats.pl?pluginmode=hostinfo&config=xx&host=177.45.121.203&key=177.45.121.203XXX Line Number 51, Column 27:NameTELEF�NICA BRASIL S.A Status NameServers Registrant Contact AdminARITE Contact TechARITE Contact Billing Contact Zone Contact Emails Contact HandlesARITE --^ Obviously this error isnt coming from awstats per-se, however in the whos is results the characters aren't being correctly escapted for html. This includes the title and the pre sections. It may be that html traditional vs xhtml makes a difference in terms of FF's happiness... but the text should still be escaped. -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-042stab090.5 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages awstats depends on: ii perl 5.14.2-21+deb7u1 Versions of packages awstats recommends: ii coreutils 8.13-3.5 ii libnet-xwhois-perl 0.90-3 Versions of packages awstats suggests: ii apache2 2.2.22-13+deb7u3 ii apache2-mpm-prefork [httpd] 2.2.22-13+deb7u3 pn libgeo-ipfree-perl ii libnet-dns-perl 0.66-2+b2 ii libnet-ip-perl 1.25-3 ii liburi-perl 1.60-1 -- Configuration Files: /etc/awstats/awstats.conf.local changed: EnableLockForUpdate=1 BuildReportFormat=xhtml SiteDomain="saito.fragfest.com.au" -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#750379: awstats: request backport
Package: awstats Version: 7.0~dfsg-7 Severity: wishlist Dear Maintainer, It would be teriffic if 7.2 could be added to backports. Cheers -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-348.16.1.el5.028stab108.1 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages awstats depends on: ii perl 5.14.2-21+deb7u1 Versions of packages awstats recommends: ii coreutils 8.13-3.5 ii libnet-xwhois-perl 0.90-3 Versions of packages awstats suggests: ii apache2 2.2.22-13+deb7u1 ii apache2-mpm-prefork [httpd] 2.2.22-13+deb7u1 pn libgeo-ipfree-perl ii libnet-dns-perl 0.66-2+b2 ii libnet-ip-perl 1.25-3 ii liburi-perl 1.60-1 -- Configuration Files: /etc/awstats/awstats.conf.local changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747835: uwsgi-plugin-php: http doesnt seem to work via /etc/uwsgi/app-enabled config
Package: uwsgi-plugin-php Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? This works on the cli... uwsgi --plugins http,php --http :80 --http-modifier1 14 --chdir /var/www/html -M as does... uwsgi --plugins http,0:php --http :80 --chdir /var/www/hlml -M However, the following config file as /etc/uwsgi/apps-enabled/helloworld.ini does not [uwsgi] plugins = http,0:php chdir = /var/www/html master = true master-as-root = true http = :80 nor does [uwsgi] plugins = http,php chdir = /var/www/html master = true master-as-root = true http = :80 http-modifier1 = 14 * What exactly did you do (or not do) that was effective (or ineffective)? As above * What was the outcome of this action? For the .ini based config, when a browser is pointed at the uwsgi server i get the "The connection was reset" error and nothing is logged With the cli options, things work as expected. * What outcome did you expect instead? php should work! -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2.dmz.1-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747272: uwsgi: wheezy backport
Package: uwsgi Severity: wishlist Dear Maintainer, * What led up to the situation? There are some great new features in uwsgi 2.0 * What exactly did you do (or not do) that was effective (or ineffective)? Was looking to run php applications in uwsgi * What was the outcome of this action? version 1.2 of uwsgi doesnt support php * What outcome did you expect instead? Well i wouldnt say I 'expect' anything. But it would be super cool if uwsgi 2.0 could be built as a backport for wheezy - even if not all of the plugins are immediately available. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2.dmz.1-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741902: ulatencyd: clashes with libvirt-bin
Package: ulatencyd Version: 0.5.0-9 Severity: normal Dear Maintainer, * What led up to the situation? It seems that cgroups are a'changing * What exactly did you do (or not do) that was effective (or ineffective)? If ulatencyd is running, libvirt-bin is unable to start kvm based vms * What was the outcome of this action? libvirt-bin gives the error Error starting domain: Failed to create controller cpu for group: No such file or directory * What outcome did you expect instead? vm's should start -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ulatencyd depends on: ii dbus 1.8.0-2 ii libc6 2.18-4 ii libdbus-1-31.8.0-2 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.38.2-5 ii liblua5.1-05.1.5-5 ii libpolkit-gobject-1-0 0.105-4 ii libxau61:1.0.8-1 ii libxcb11.10-2 ii lua-posix 29-7 ii lua5.1 [lua] 5.1.5-5 Versions of packages ulatencyd recommends: ii consolekit 0.4.6-4 ulatencyd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#740121: libgraphics-primitive-driver-cairo-perl: height and width being ignored?
Package: libgraphics-primitive-driver-cairo-perl
Version: 0.46-1
Severity: normal
Dear Maintainer,
here is the code i am using
#!/usr/bin/perl
use strict;use warnings;
use Graphics::Primitive::Container;
use Graphics::Color::RGB;
use Graphics::Primitive::Font;
use Graphics::Primitive::TextBox;
use Graphics::Primitive::Driver::Cairo;
use Layout::Manager::Compass;
my $black = Graphics::Color::RGB->new(red => 0, green => 0, blue => 0);
my $container = Graphics::Primitive::Container->new( width => 100, height =>
100);
$container->border->width(1);
$container->border->color($black);
$container->padding(
Graphics::Primitive::Insets->new(top => 5, bottom => 5, left => 5,
right => 5)
);
my $comp = Graphics::Primitive::Component->new;
$comp->background_color($black);
$container->add_component($comp, 'c');
my $lm = Layout::Manager::Compass->new;
$lm->do_layout($container);
my $driver = Graphics::Primitive::Driver::Cairo->new;
$driver->draw($container);
$driver->write('/tmp/foo.png');
__END__
for which i always see this error
dean@laserbeak:/tmp$ perl test.pl
Use of uninitialized value in subroutine entry at
/usr/share/perl5/Graphics/Primitive/Driver/Cairo.pm line 85.
Use of uninitialized value in subroutine entry at
/usr/share/perl5/Graphics/Primitive/Driver/Cairo.pm line 85.
Chart::Clicker works fine, so i know that its possible for
Graphics::Primitive::Driver::Cairo to output something
perhaps its a problem between the chair and the keyboard?
The minimal examples in the pod of Graphics::Primitive I am struggling with as
too minimalistic.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libgraphics-primitive-driver-cairo-perl depends on:
ii libcairo-perl 1.104-1
ii libgeometry-primitive-perl 0.24-1
ii libgraphics-primitive-perl 0.64-1
ii libmoose-perl 2.1005-1+b1
ii libtext-flow-perl 0.01-1
ii perl5.18.2-2
libgraphics-primitive-driver-cairo-perl recommends no packages.
libgraphics-primitive-driver-cairo-perl suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720373: grub-common: mask detected drives from os-probe
Package: grub-common Version: 2.00-15 Severity: wishlist Dear Maintainer, The os-prober utility is called via 30_os-prober to find operating systems. Which is handy. On the down side, LVM volumes created for KVM virtual machines are detected and added to grub- which is annoying. ie -- Found Debian GNU/Linux (jessie/sid) on /dev/mapper/VmStorage-fai Found Debian GNU/Linux (jessie/sid) on /dev/mapper/VmStorage-uwsgi1 Found Debian GNU/Linux (jessie/sid) on /dev/mapper/VmStorage-uwsgi2_snapshot Found Debian GNU/Linux (jessie/sid) on /dev/mapper/VmStorage-uwsgi3_snapshot done -- It would very handy to be able to configure a mask for drives that we dont care for grub to list. >From the example above, masking out /dev/mapper/* or /dev/mapper/VmStorage* Perhaps an entry in /etc/defaults/grub ? Dean -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages grub-common depends on: ii gettext-base0.18.3-1 ii libc6 2.17-92 ii libdevmapper1.02.1 2:1.02.77-5 ii libfreetype62.4.9-1.1 ii libfuse22.9.2-4 ii liblzma55.1.1alpha+20120614-2 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages grub-common recommends: ii os-prober 1.63 Versions of packages grub-common suggests: ii console-setup 1.94 ii desktop-base 7.0.3 pn grub-emu pn multiboot-doc pn xorriso -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#719870: Dead upstream? huh?
Compiz seems very active upstream. https://code.launchpad.net/compiz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717971: wine: New stable Wine release: 1.6 - please update package
Yes please! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#718390: xfburn: 'burn' icon broken
Package: xfburn Version: 0.4.3-6 Severity: minor The icon for the 'burn' button gives the 'broken icon' icon. I am guessing there is a dependancy missing as all other icons are aok. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfburn depends on: ii libburn4 1.2.2-2 ii libc62.17-7 ii libexo-1-0 0.10.2-2 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libglib2.0-0 2.36.3-3 ii libgstreamer-plugins-base0.10-0 0.10.36-1.1 ii libgstreamer0.10-0 0.10.36-1.2 ii libgtk2.0-0 2.24.20-1 ii libgudev-1.0-0 175-7.2 ii libisofs61.2.2-1 ii libxfce4ui-1-0 4.10.0-3 ii libxfce4util64.10.1-1 xfburn recommends no packages. xfburn suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717341: /usr/bin/lxc-clone: lxc-clone fails to clone lvm backed container
Package: lxc Version: 0.9.0~alpha3-2 Severity: important File: /usr/bin/lxc-clone Dear Maintainer, * What led up to the situation? Attempted to use lxc-clone to clone a container * What exactly did you do (or not do) that was effective (or ineffective)? lxc-clone -o uwsgi1 -n uwsgi2 or even lxc-clone -o uwsgi1 -n uwsgi2 -v VmStorage or even lxc-clone -o uwsgi1 -n uwsgi3 -v VmStorage -t xfs * What was the outcome of this action? a cloned container as it would do with a directory backed container * What outcome did you expect instead? here is the output root@batou:~# lxc-clone -o uwsgi1 -n uwsgi3 -v VmStorage -t xfs Tweaking configuration Copying rootfs... Logical volume "uwsgi3_snapshot" created UUID = cd8c7fbf-04c2-4eda-81da-408e80dd0180 Clearing log and setting UUID writing all SBs new UUID = 58c0b2f7-24fb-418a-a7b2-af3328b9ce38 mkdir: cannot create directory ‘/dev/VmStorage/uwsgi3_snapshot’: File exists root@batou:~# -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lxc depends on: ii debconf [debconf-2.0] 1.5.50 ii libapparmor1 2.8.0-1 ii libc6 2.17-7 ii libcap21:2.22-1.2 ii multiarch-support 2.17-7 Versions of packages lxc recommends: ii debootstrap 1.0.53 ii libcap2-bin 1:2.22-1.2 Versions of packages lxc suggests: pn debian-keyring ii gpgv1.4.12-7 ii live-debconfig-doc 4.0~a25-1 ii rsync 3.0.9-4 -- debconf information: lxc/shutdown: /usr/bin/lxc-halt lxc/directory: /var/lib/lxc lxc/title: lxc/auto: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717025: dh-make-perl: Incorrectly determines package name with q style quotes
On 2013-07-16 16:36, gregor herrmann wrote:
On Tue, 16 Jul 2013 16:23:08 +1000, Dean Hamstead wrote:
Attempting to build a package with this type of thing in the
Build.PL file
And no META.{json,yml} file, I presume, which should be preferred if
it exists, IIRC.
Thats correct.
my $build = Module::Build->new(
module_name=> q|Example|,
...
);
Do you have a real-life example of a CPAN module to save us the work
of constructing a test case? Sorry for the laziness :)
Alas no, as i was building an internal module at my place of employ.
Dean
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717025: dh-make-perl: Incorrectly determines package name with q style quotes
Package: dh-make-perl Version: 0.76-1 Severity: important Dear Maintainer, * What led up to the situation? Attempting to build a package with this type of thing in the Build.PL file my $build = Module::Build->new( module_name=> q|Example|, ... ); * What exactly did you do (or not do) that was effective (or ineffective)? As above. * What was the outcome of this action? The name determined was literally 'q|Example|' * What outcome did you expect instead? Should just be 'Example' *** End of the template - remove these lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dh-make-perl depends on: ii debhelper 9.20130605 ii dpkg-dev 1.16.10 ii fakeroot 1.19-2 ii libapt-pkg-perl 0.1.29 ii libarray-unique-perl 0.08-1 ii libclass-accessor-perl0.34-1 ii libdpkg-perl 1.16.10 ii libemail-address-perl 1.898-1 ii libemail-date-format-perl 1.002-1 ii libfile-which-perl1.09-1 ii liblist-moreutils-perl0.33-1+b1 ii libmodule-depends-perl0.16-1 ii libparse-debcontrol-perl 2.005-4 ii libparse-debianchangelog-perl 1.2.0-1 ii libsoftware-license-perl 0.103005-1 ii libtie-ixhash-perl1.23-1 ii libwww-mechanize-perl 1.71-1 ii libyaml-perl 0.84-1 ii make 3.81-8.2 ii perl 5.14.2-21 ii perl-modules [libcpan-meta-perl] 5.14.2-21 Versions of packages dh-make-perl recommends: ii apt-file 2.5.2 ii git 1:1.8.3.1-1 ii pristine-tar 1.28 dh-make-perl suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
