Bug#785281: [pkg-php-pear] Bug#785281: php-seclib and php-math-biginteger: error when trying to install together
Le 14/05/2015 03:42, Ralf Treinen a écrit : Package: php-math-biginteger,php-seclib Version: php-math-biginteger/1.0.2-2 Version: php-seclib/0.3.10-2 automatic installation tests of packages that share a file /usr/share/php/Math/BigInteger.php It’s even the same file (the one from php-seclib seems to be a more recent version). Mathieu, I assume you introduced php-math-biginteger as a php-horde-mapi dependency, would it be OK to directly depend on php-seclib instead? php-seclib is a bit bigger (since it ships all secure communication library [0]), but is already a dependency of a few packages (collabtive, dokuwiki, owncloud, and spotweb), so “simply” declaring a conflict may prevent a Horde user to install a bunch of thing (and vice versa). I could also split php-math-biginteger from php-seclib if size is really an issue. I’m not sure that moving the common file in another directory would be worth it (since Debian would be shipping two copies of the same files, in different versions…), I was on the contrary already bugging packages shipping their own (partial) embedded copy of php-seclib to use the packaged one. [0] http://phpseclib.sourceforge.net/pear.htm Regards David signature.asc Description: OpenPGP digital signature
Processed: Cmake 3.2 uploaded
Processing commands for cont...@bugs.debian.org: severity 784767 serious Bug #784767 [libeigen3-dev] libeigen3-dev: Transition to cmake 3.2 Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 784767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785305: keepass2: option to lock workspace on suspend does not work
Package: keepass2 Version: 2.28+dfsg-1 Severity: grave Tags: security Justification: user security hole Dear Maintainer, The two options Lock workspace when locking the computer and Lock workspace when the computer is about to be suspended do not function. This makes possible reading user's secrets from memory if, for example, a laptop is stolen while suspended and the software is running. The two options are specifically designed to prevent this from happening and a user who has enabled them will expect to be protected from such an attack. I am using Gnome on Debian Jessie. -- System Information: Debian Release: 8.0 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages keepass2 depends on: ii libmono-corlib4.5-cil3.2.8+dfsg-10 ii libmono-system-drawing4.0-cil3.2.8+dfsg-10 ii libmono-system-security4.0-cil 3.2.8+dfsg-10 ii libmono-system-windows-forms4.0-cil 3.2.8+dfsg-10 ii libmono-system-xml4.0-cil3.2.8+dfsg-10 ii libmono-system4.0-cil3.2.8+dfsg-10 ii libx11-6 2:1.6.2-3 ii mono-runtime 3.2.8+dfsg-10 Versions of packages keepass2 recommends: ii xsel 1.2.0-2 Versions of packages keepass2 suggests: ii keepass2-doc 2.28+dfsg-1 pn mono-dmcs none pn xdotool none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785248: wxhexeditor: Fails to run, suggesting download of new version
Hello Peter,
(not being the maintainer I tried to reproduce)
By removing from ~/.wxHexEditor the line
LastUpdateCheckTime=1.4316e+09 I could reproduce the opening of the
update checking window.
But in Jessie/KDE I am able to simply close this window with the X in
the window bar and then the regular wxHexEditor window opens.
Therefore really renders package unusable?
If debian packaging just requires to disable the upstream version check
then attached patch would do this.
Kind regards,
Bernhard
Description: Disable check for newer upstream version
Author: Bernhard Ãbelacker bernha...@vr-web.de
---
Bug-Debian: https://bugs.debian.org/785248
Last-Update: 2015-05-14
--- wxhexeditor-0.22+repack.orig/src/HexEditorFrame.cpp
+++ wxhexeditor-0.22+repack/src/HexEditorFrame.cpp
@@ -176,6 +176,7 @@ HexEditorFrame::HexEditorFrame( wxWindow
MyNotebook-Connect( wxEVT_COMMAND_AUINOTEBOOK_PAGE_CHANGED, wxAuiNotebookEventHandler( HexEditorFrame::OnNotebookTabSelection ), NULL,this );
MyNotebook-Connect( wxEVT_COMMAND_AUINOTEBOOK_TAB_MIDDLE_UP, wxAuiNotebookEventHandler( HexEditorFrame::OnNotebookTabClose ), NULL,this );
+#if 0 /* Debian bug #785248 */
bool update_enable = false;
if ( not wxConfigBase::Get()-Read(_T(UpdateCheck), update_enable )){
update_enable = true;
@@ -196,6 +197,7 @@ HexEditorFrame::HexEditorFrame( wxWindow
}
+#endif
}
HexEditorFrame::~HexEditorFrame(){
#if defined( _DEBUG_ ) defined( __WXMSW__ )
Bug#784655: closed by Matthias Klose d...@debian.org (Bug#784655: fixed in gcc-5 5.1.1-5)
Hi again Doko, is it acceptable to use g++-5 or should I reopen this RC? I don't know if there is another hidden bug here or not thanks Gianfranco Il Lunedì 11 Maggio 2015 23:28, Gianfranco Costamagna costamagnagianfra...@yahoo.it ha scritto: Hi Doko, yes, I had to force g++5 to make them run successfully thanks, (sorry for top posting) Gianfranco Sent from Yahoo Mail on Android From:Matthias Klose d...@debian.org Date:Mon, 11 May, 2015 at 22:34 Subject:Re: Bug#784655: closed by Matthias Klose (Bug#784655: fixed in gcc-5 5.1.1-5) On 05/11/2015 10:36 AM, Gianfranco Costamagna wrote: does this mean that I need to b-d on g++-5 and export CXX=g++-5? It seems to be failing to build when mixing g++-4.9 and new libstdc++... thanks a lot for the fix! Now with gcc-5 I can build it correctly! no, please continue to build with the default gcc-4.9 for the near future. Are these tests still failing when you rebuild with 5.1.1-5? Matthias -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: CMake 3.2 uploaded
Processing commands for cont...@bugs.debian.org: severity 784769 serious Bug #784769 [libqcustomplot-dev] libqcustomplot-dev: Transition to cmake 3.2 Severity set to 'serious' from 'normal' severity 784768 serious Bug #784768 [libhiredis-dev] libhiredis-dev: Transition to cmake 3.2 Severity set to 'serious' from 'normal' severity 784766 serious Bug #784766 [libadios-dev] libadios-dev: Transition to cmake 3.2 Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 784766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784766 784768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784768 784769: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785304: libparmap-ocaml-dev: missing libparmap_stubs.a on bytecode architectures
Package: libparmap-ocaml-dev Version: 1.0~rc4-4 Severity: serious Parmap package does not install libparmap_stubs.a file on bytecode architectures. This makes it impossible to build depending packages, like now coccinelle, on those architectures. I assume that is was just a mistake not to install that file, because other -dev packages (pcre, pycaml) contain such files even on bytecode-only architectures. -- 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.0.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libparmap-ocaml-dev depends on: ii libparmap-ocaml [libparmap-ocaml-8kg90] 1.0~rc4-4 ii ocaml-nox [ocaml-nox-4.01.0] 4.01.0-5 libparmap-ocaml-dev recommends no packages. libparmap-ocaml-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784215: marked as done (strongswan-nm: network-manager-strongswan unavailable)
Your message dated Thu, 14 May 2015 16:09:19 +0200 with message-id 1431612559.14305.14.ca...@debian.org and subject line Re: [Pkg-swan-devel] Bug#784215: Bug#784215: strongswan-nm: network-manager-strongswan unavailable has caused the Debian Bug report #784215, regarding strongswan-nm: network-manager-strongswan unavailable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 784215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: strongswan-nm Version: 5.2.1-6 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I am trying to use strongswan IPsec VPN through Network-Manager. The plugin package network-manager-strongswan is not available, but listed as dependency for strongswan-nm. * What exactly did you do (or not do) that was effective (or ineffective)? I tried to install network-manager-strongswan * What was the outcome of this action? root@jessie:~# apt-get install network-manager-strongswan Reading package lists... Done Building dependency tree Reading state information... Done Package network-manager-strongswan is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'network-manager-strongswan' has no installation candidate * What outcome did you expect instead? Installation of the strongswan plugin for Network-Manager. *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ---End Message--- ---BeginMessage--- On mar., 2015-05-12 at 21:26 +0200, Yves-Alexis Perez wrote: So what's the status on this now that #759826 is fixed? Looks installable to me, closing. -- Yves-Alexis signature.asc Description: This is a digitally signed message part ---End Message---
Bug#741798: any update on the resolution of the bug ?
Hi all, Any update on this bug. Upstream i.e. launchpad has made several releases after that. Looking forward to know. -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 784647 is not forwarded
Processing commands for cont...@bugs.debian.org: notforwarded 784647 Bug #784647 [libopencv-imgproc2.4] libav-tools: avconv fails with Illegal Instruction Unset Bug forwarded-to-address thanks Stopping processing here. Please contact me if you need assistance. -- 784647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785297: aria2: FTBFS with linux-libc-dev 4.0.2-1
Source: aria2 Version: 1.18.10-2 Severity: serious Hi. I just tried to build aria2 in sid (using cowbuilder) in preparation of the transition of nettle. I don't have much more detail, but something seems amiss with regards to the detection, declaration, and/or invocation of the getrandom syscall (in the current builds, the syscall interface was not detected at all). checking for getrandom... no [...] checking for getrandom linux syscall interface... yes [...] CC getrandom_linux.lo getrandom_linux.c: In function 'getrandom_linux': getrandom_linux.c:56:20: error: 'SYS_getrandom' undeclared (first use in this function) read = syscall(SYS_getrandom, p, buflen, 0); ^ -- Magnus Holmgrenholmg...@debian.org Debian Developer signature.asc Description: This is a digitally signed message part.
Processed: [bts-link] source package torbrowser-launcher
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package torbrowser-launcher # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #783922 (http://bugs.debian.org/783922) # Bug title: Newest TBB does not start with provided AppArmor profile in enforce mode # * https://github.com/micahflee/torbrowser-launcher/issues/177 # * remote status changed: open - closed # * closed upstream tags 783922 + fixed-upstream Bug #783922 [torbrowser-launcher] Newest TBB does not start with provided AppArmor profile in enforce mode Added tag(s) fixed-upstream. usertags 783922 - status-open Usertags were: status-open. Usertags are now: . usertags 783922 + status-closed There were no usertags set. Usertags are now: status-closed. # remote status report for #784041 (http://bugs.debian.org/784041) # Bug title: exceptions.OSError: [Errno 2] No such file or directory # * https://github.com/micahflee/torbrowser-launcher/issues/176 # * remote status changed: (?) - closed # * closed upstream tags 784041 + fixed-upstream Bug #784041 [torbrowser-launcher] exceptions.OSError: [Errno 2] No such file or directory Added tag(s) fixed-upstream. usertags 784041 + status-closed There were no usertags set. Usertags are now: status-closed. thanks Stopping processing here. Please contact me if you need assistance. -- 783922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783922 784041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reassign 785265 to xserver-xorg-video-modesetting, severity of 785265 is important
Processing commands for cont...@bugs.debian.org: reassign 785265 xserver-xorg-video-modesetting Bug #785265 [xorg] xorg: SEG FAULT! CANNOT USE X! Bug reassigned from package 'xorg' to 'xserver-xorg-video-modesetting'. No longer marked as found in versions xorg/1:7.7+9. Ignoring request to alter fixed versions of bug #785265 to the same values previously set severity 785265 important Bug #785265 [xserver-xorg-video-modesetting] xorg: SEG FAULT! CANNOT USE X! Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 785265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785265: xorg: SEG FAULT! CANNOT USE X!
On Thu, May 14, 2015 at 07:45:26 +0800, Dan Jacobson wrote: Package: xorg Version: 1:7.7+9 Severity: grave Justification: renders package unusable Starting today I cannot use X windows, thus cannot do almost anything anymore! Furthermore it is not clear which package I need to revert to its previous version to be able to hardly use my computer anymore! Please provide a backtrace from gdb. See http://x.debian.net/howto/use-gdb.html Cheers, Julien signature.asc Description: Digital signature
Bug#785322: chkrootkit: Should depend on openssh-client
Package: chkrootkit Version: 0.50-3 Severity: serious Justification: Policy 7.2 Dear Maintainer, If ssh isn't in the system chkrootkit fails with chkrootkit: can't find `ssh'. The shell script reads: ### check the external commands needed cmdlist= [...] ssh [...] but ssh isn't included in any essential package and the packages it belongs (openssh-client) isn't listed in the chkrootkit depends field. Best Regards, Manolo Díaz -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.0.3 (SMP w/2 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages chkrootkit depends on: ii binutils 2.25-7 ii debconf [debconf-2.0] 1.5.56 ii libc6 2.19-18 ii net-tools 1.60-26+b1 ii procps 2:3.3.9-9 chkrootkit recommends no packages. chkrootkit suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package gobby-infinote
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package gobby-infinote # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #783601 (http://bugs.debian.org/783601) # Bug title: gobby silently accepts expired certificates # * https://github.com/gobby/gobby/issues/61 # * remote status changed: (?) - closed # * closed upstream tags 783601 + fixed-upstream Bug #783601 [gobby] gobby silently accepts expired certificates Added tag(s) fixed-upstream. usertags 783601 + status-closed There were no usertags set. Usertags are now: status-closed. thanks Stopping processing here. Please contact me if you need assistance. -- 783601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: [bts-link] source package evolution
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package evolution # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #784625 (http://bugs.debian.org/784625) # Bug title: evolution: crash on start [Arithmetic exception in e_day_view_convert_position_in_main_canvas at e-day-view.c:8158] # * http://bugzilla.gnome.org/show_bug.cgi?id=740370 # * remote status changed: NEW - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream forwarded 784625 https://bugzilla.gnome.org/show_bug.cgi?id=749059, merged-upstream: http://bugzilla.gnome.org/show_bug.cgi?id=740370 Bug #784625 [evolution] evolution: crash on start [Arithmetic exception in e_day_view_convert_position_in_main_canvas at e-day-view.c:8158] Changed Bug forwarded-to-address to 'https://bugzilla.gnome.org/show_bug.cgi?id=749059, merged-upstream: http://bugzilla.gnome.org/show_bug.cgi?id=740370' from 'https://bugzilla.gnome.org/show_bug.cgi?id=749059' tags 784625 + fixed-upstream Bug #784625 [evolution] evolution: crash on start [Arithmetic exception in e_day_view_convert_position_in_main_canvas at e-day-view.c:8158] Added tag(s) fixed-upstream. usertags 784625 - status-NEW Usertags were: status-NEW. Usertags are now: . usertags 784625 + status-RESOLVED resolution-FIXED There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. -- 784625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785326: libavcodec56: CVE-2014-7937 - Multiple off-by-one errors in libavcodec/vorbisdec.c
Package: libavcodec56 Version: 6:11.3-2 Severity: grave Tags: security Justification: user security hole Hi, as far as I can see this has not yet been reported or fixed: CVE-2014-7937 : Multiple off-by-one errors in libavcodec/vorbisdec.c in FFmpeg before 2.4.2, as used in Google Chrome before 40.0.2214.91, allow remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted Vorbis I data [1] I marked this as grave as the impact is unclear and might include arbitrary code execution. Feel free do downgrade if this can be ruled out. (Actually I would like to have a look at the test case to check a bit more thoroughly, but AFAICS I would need to talk to google for this.) [1] https://security-tracker.debian.org/tracker/CVE-2014-7937 https://lists.libav.org/pipermail/libav-devel/2015-January/066433.html cu AW -- System Information: Debian Release: stretch/sid APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.7-ckt9 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libavcodec56 depends on: ii libavresample2 6:11.3-2 ii libavutil546:11.3-2 ii libc6 2.19-18 ii libgsm11.0.13-4 ii libmp3lame03.99.5+repack1-7 ii libopenjpeg5 1:1.5.2-3 ii libopus0 1.1-2 ii libschroedinger-1.0-0 1.0.11-2.1 ii libspeex1 1.2~rc1.2-1 ii libtheora0 1.1.1+dfsg.1-6 ii libva1 1.5.1-2 ii libvorbis0a1.3.4-2 ii libvorbisenc2 1.3.4-2 ii libvpx11.3.0-3 ii libx264-1422:0.142.2431+gita5831aa-1+b2 ii libx265-43 1.5-1 ii libxvidcore4 2:1.3.3-1 ii multiarch-support 2.19-18 ii zlib1g 1:1.2.8.dfsg-2+b1 libavcodec56 recommends no packages. libavcodec56 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785304: marked as done (libparmap-ocaml-dev: missing libparmap_stubs.a on bytecode architectures)
Your message dated Thu, 14 May 2015 16:02:27 + with message-id e1ysvad-0003kg...@franck.debian.org and subject line Bug#785304: fixed in parmap 1.0~rc4-5 has caused the Debian Bug report #785304, regarding libparmap-ocaml-dev: missing libparmap_stubs.a on bytecode architectures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 785304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libparmap-ocaml-dev Version: 1.0~rc4-4 Severity: serious Parmap package does not install libparmap_stubs.a file on bytecode architectures. This makes it impossible to build depending packages, like now coccinelle, on those architectures. I assume that is was just a mistake not to install that file, because other -dev packages (pcre, pycaml) contain such files even on bytecode-only architectures. -- 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.0.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libparmap-ocaml-dev depends on: ii libparmap-ocaml [libparmap-ocaml-8kg90] 1.0~rc4-4 ii ocaml-nox [ocaml-nox-4.01.0] 4.01.0-5 libparmap-ocaml-dev recommends no packages. libparmap-ocaml-dev suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: parmap Source-Version: 1.0~rc4-5 We believe that the bug you reported is fixed in the latest version of parmap, 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 785...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu glo...@debian.org (supplier of updated parmap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 14 May 2015 16:24:16 +0200 Source: parmap Binary: libparmap-ocaml libparmap-ocaml-dev Architecture: source amd64 Version: 1.0~rc4-5 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers debian-ocaml-ma...@lists.debian.org Changed-By: Stéphane Glondu glo...@debian.org Description: libparmap-ocaml - small OCaml library allowing to exploit multicore architectures libparmap-ocaml-dev - small OCaml library allowing to exploit multicore architectures Closes: 785304 Changes: parmap (1.0~rc4-5) unstable; urgency=medium . * Team upload * Install libparmap_stubs.a on bytecode architectures (Closes: #785304) * Update Vcs-* * Fix debian/watch Checksums-Sha1: 4981d1d499184732cde8852356171af38329b540 2072 parmap_1.0~rc4-5.dsc 38a18141b4a02fb503f0630a327ba50d9f1221c5 3964 parmap_1.0~rc4-5.debian.tar.xz 8dc8433e8086366832731c9a8c3482c168c379dc 31474 libparmap-ocaml_1.0~rc4-5_amd64.deb f6613c1f08d31974a2f2b6ff4b10d5cb0629603d 29564 libparmap-ocaml-dev_1.0~rc4-5_amd64.deb Checksums-Sha256: fdeb37c7d8008a9c8a3f10cffddbfe8f747a52898fce3768ab576485837d8c04 2072 parmap_1.0~rc4-5.dsc f41f5fa43a21eec7c3c074b149a847271aa418e6c3cc6533f5f47121a803247f 3964 parmap_1.0~rc4-5.debian.tar.xz a0ed33f2aae48d34b755db991d4dd2db8c7dce693940a66b54b67070cbbb0327 31474 libparmap-ocaml_1.0~rc4-5_amd64.deb 7c29c9ab651b451e4c0e657d6c35d3b725e95748e8957c18520275ab8fcc7c22 29564 libparmap-ocaml-dev_1.0~rc4-5_amd64.deb Files: 5d6ae13eb93ee6c3a33cbaf886b286fe 2072 ocaml optional parmap_1.0~rc4-5.dsc e20e5140501109f0648fe0013375652a 3964 ocaml optional parmap_1.0~rc4-5.debian.tar.xz 272032caec356d79c6ab436fb5852711 31474 ocaml optional libparmap-ocaml_1.0~rc4-5_amd64.deb 85ac1e1518c8388dae6af467466e7acc 29564 ocaml optional libparmap-ocaml-dev_1.0~rc4-5_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJVVLDwAAoJEHhT2k1JiBrTKjwQAI+yEMTtqFdVxpWWWcm2Bdh1 FLIxaONOuazY+MkmN4Dp0DASjzJYlY9RTV8aPVp/rt7ONrv7SfZGIevpeggFI9nc FwEC60Tdfkr4ujv2ga7yFiAIRaM+0g4tg2y0ROfw4g8inhOmhpDsahRNCcKw20Z0 qFu3MHlpEzJ2Nhx27lJQKUMfbnvQzPQMXn6XQ9ocHiFfnrYIWIQKRr70Y69nVlcf EbkZQtLm2nkVoUX1fxE2VT76WdhAekYWFi3GeOZaDQ7xG+VKsdMNYdAGCCy/qdzP
Processed: Re: [Pkg-mozext-maintainers] Bug#785300: xul-ext-pentadactyl: pentadactyl not compatible with iceweasel 38.0-1
Processing control commands: severity -1 serious Bug #785300 [xul-ext-pentadactyl] xul-ext-pentadactyl: pentadactyl not compatible with iceweasel 38.0-1 Severity set to 'serious' from 'important' tags -1 confirmed Bug #785300 [xul-ext-pentadactyl] xul-ext-pentadactyl: pentadactyl not compatible with iceweasel 38.0-1 Added tag(s) confirmed. -- 785300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785300 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784256: marked as done (usemod-wiki: Undefined subroutine CGI::startform)
Your message dated Thu, 14 May 2015 16:23:05 +
with message-id e1ysvub-0006mj...@franck.debian.org
and subject line Bug#784256: fixed in usemod-wiki 1.0.5-4
has caused the Debian Bug report #784256,
regarding usemod-wiki: Undefined subroutine CGI::startform
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
784256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: usemod-wiki
Version: 1.0.5-3
Severity: grave
Tags: upstream patch
Justification: renders package unusable
Dear Maintainer,
I upgraded my system to Jessie (Debian 8.0) and now my wiki is no more
working :-(
I get this error as an HTML page:
« Software error:
Undefined subroutine CGI::startform
at /usr/lib/cgi-bin/wiki.pl line 1503.
For help, please send mail to the webmaster (webmaster@localhost), giving this
error message and the time and date of the error. »
Line 1503 of /usr/lib/cgi-bin/wiki.pl is:
sub GetFormStart {
return $q-startform(POST, $ScriptName,
application/x-www-form-urlencoded);
}
The problem is similar to #767960 and is very easy to fix.
I hope the problem will be fixed in the next update of stable.
Proposed patch:
--- wiki.pl 2015-05-04 15:29:26.0 +0200
+++ /usr/lib/cgi-bin/wiki.pl2015-05-04 15:43:16.781540995 +0200
@@ -1471,7 +1471,7 @@
$result .= 'brb' . T('Config file error:') . '/b '
. $ConfigError . 'br';
}
- $result .= $q-endform;
+ $result .= $q-end_form;
if ($FooterNote ne '') {
$result .= T($FooterNote);
}
@@ -1500,7 +1500,7 @@
}
sub GetFormStart {
- return $q-startform(POST, $ScriptName,
+ return $q-start_form(POST, $ScriptName,
application/x-www-form-urlencoded);
}
-- System Information:
Debian Release: 8.0
APT prefers stable
APT policy: (990, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages usemod-wiki depends on:
ii apache2 [httpd] 2.4.10-10
ii apache2-mpm-prefork [httpd] 2.4.10-10
ii perl 5.20.2-3
Versions of packages usemod-wiki recommends:
ii apache2 [httpd] 2.4.10-10
ii apache2-mpm-prefork [httpd] 2.4.10-10
Versions of packages usemod-wiki suggests:
ii exim4-daemon-light [mail-transport-agent] 4.84-8
-- System Information:
Debian Release: 8.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
---End Message---
---BeginMessage---
Source: usemod-wiki
Source-Version: 1.0.5-4
We believe that the bug you reported is fixed in the latest version of
usemod-wiki, 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 784...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christoph Berg m...@debian.org (supplier of updated usemod-wiki 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: Thu, 14 May 2015 17:47:09 +0200
Source: usemod-wiki
Binary: usemod-wiki
Architecture: source all
Version: 1.0.5-4
Distribution: unstable
Urgency: medium
Maintainer: Christoph Berg m...@debian.org
Changed-By: Christoph Berg m...@debian.org
Description:
usemod-wiki - Perl-based Wiki clone
Closes: 784256
Changes:
usemod-wiki (1.0.5-4) unstable; urgency=medium
.
* Depend on libcgi-pm-perl and adjust startform/endform to
start_form/end_form. (Closes: #784256)
Checksums-Sha1:
691cd3151307f6ba49fa1787099de595a552670c 1762 usemod-wiki_1.0.5-4.dsc
c9958a13664a25d1ebf95887417219e97a45fe72 14376
usemod-wiki_1.0.5-4.debian.tar.xz
7d8ec84960c6098f7eff9d90279a68cb75af8b63 56926 usemod-wiki_1.0.5-4_all.deb
Checksums-Sha256:
a930f04e360a753dafb83265c915d17605f917f8031c725b51ff35678e5121e9 1762
usemod-wiki_1.0.5-4.dsc
Bug#785269: drupal7: Can't setup: Unicode library Error. Check php.ini mbstring.http_input setting
Hi,
Your report strikes me as quite weird, as I recently did the same
without any trouble. Does your Apache installation allow for
directives to be specified via .htcaccess? (look for AllowOverride
in your Apache configurations)
You mention:
Tried everything under the sun:
modified /etc/php5/cli/php.ini (input_encoding, mbstring.http_input others)
modified /etc/drupal/7/htaccess
kept restarting apache and update.php ing.
How do you have configured the Apache↔PHP interface? You most likely
do so via libapache2-mod-php5; if so, editing /etc/php5/cli/php.ini
will have no effect, you have to edit /etc/php5/apache2/php.ini
instead. The directives that should be added there are:
ini_set('mbstring.http_input', 'pass');
ini_set('mbstring.http_output', 'pass');
You might want to refer to the following Drupal issues — Quite old
(2006 and 2008), but relevant to the issue at hand:
https://www.drupal.org/node/87138
https://www.drupal.org/node/211648
Particularly, there's one extra line one user mentions as useful to
him (and that's part of the .htaccess we ship):
php_value mbstring.encoding_translation 0
One further comment (#40) comments about this problem while using
Debian Jessie, and mentions the problem having disappeared after
adding the ini_set(...) lines in the
[drupal_folder]/sites/default/settings.php file.
Please do confirm if any of the above fix the problem for you!
signature.asc
Description: Digital signature
Processed: Re: Please update the plugins to the latest version
Processing commands for cont...@bugs.debian.org: retitle 783679 needs update for roundcube 1.1 Bug #783679 [roundcube-plugins-extra] [roundcube-plugins-extra] Please update the plugins to the latest version Changed Bug title to 'needs update for roundcube 1.1' from '[roundcube-plugins-extra] Please update the plugins to the latest version' severity 783679 serious Bug #783679 [roundcube-plugins-extra] needs update for roundcube 1.1 Severity set to 'serious' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 783679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784256: usemod-wiki: Undefined subroutine CGI::startform
Re: Ludovic Rousseau 2015-05-04 20150504153158.27553.98664.report...@linutop.apdu.fr I upgraded my system to Jessie (Debian 8.0) and now my wiki is no more working :-( I get this error as an HTML page: « Software error: Undefined subroutine CGI::startform at /usr/lib/cgi-bin/wiki.pl line 1503. Hi Ludovic, I've just fixed this for unstable, thanks for the report! For jessie, the problem is only there when you have libcgi-pm-perl installed. If you remove that, the CGI.pm version bundled with perl works. Is that workaround good enough, or should we look into preparing a package for proposed-updates? Christoph -- c...@df7cb.de | http://www.df7cb.de/ signature.asc Description: Digital signature
Bug#784009: Segmentation fault
torsdagen den 14 maj 2015 07.56.56 skrev Andreas Metzler: On 2015-05-10 Magnus Holmgren holmg...@debian.org wrote: måndagen den 4 maj 2015 19.32.52 skrev Andreas Metzler: [...] I think GnuTLS being listed as part of the guile-1.8 removal is an error in the reporting script, GnuTLS has moved to guile-2.0 in 2013. OTOH I hope we can have gnutls linked against nettle 3.x without needing to update to 3.4.x. (Which would couple together two transitions. And 3.4 ist still a development release.) http://lists.gnutls.org/pipermail/gnutls-devel/2015-May/007583.html A rather significant patch, but since someone has already done it, will you use it? 3.1-1 has entered experimental, as you may have seen. Should I upload 3.1.1-1 to unstable or to experimental for now? Given that it originates from GnuTLS' author I will try to use it. Could you upload 3.1.1-1 to experimental? I have done so. Have you already opened a transition tracker, BTW? Not yet. I've been testing building depending packages all day, and most builds cleanly although some failed for other reasons, but lsh-utils needs some work. I'd like to see if I can patch it or have to ask upstream. -- Magnus Holmgrenholmg...@debian.org Debian Developer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785229: marked as done (sqitch: FTBFS: new warnings)
Your message dated Thu, 14 May 2015 21:42:34 +
with message-id e1yt0tm-0003ip...@franck.debian.org
and subject line Bug#785229: fixed in sqitch 0.9991-1
has caused the Debian Bug report #785229,
regarding sqitch: FTBFS: new warnings
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
785229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: sqitch
Version: 0.996-1
Severity: serious
Tags: stretch sid
As noticed by the reproducible builds project, this package
fails to build on current sid.
not ok 242 - no warnings
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/242 subtests
# Failed test 'no warnings'
# at /usr/share/perl5/Test/NoWarnings.pm line 45.
# There were 1 warning(s)
# Previous test 0 ''
# Overwriting existing sub 'App::Sqitch::extends' with sub 'extends'
exported by Type::Utils at /«PKGBUILDDIR»/blib/lib/App/Sqitch.pm line 18.
# at /usr/share/perl5/Exporter/Tiny.pm line 269.
# Exporter::Tiny::_exporter_install_sub(Type::Utils, extends,
HASH(0x2784dd8), HASH(0x2e5bbf0), CODE(0x2ccee68)) called at
/usr/share/perl5/Exporter/Tiny.pm line 61
# Exporter::Tiny::import(Type::Utils, -all) called at
/«PKGBUILDDIR»/blib/lib/App/Sqitch.pm line 18
# App::Sqitch::BEGIN() called at /«PKGBUILDDIR»/blib/lib/App/Sqitch.pm
line 18
# eval {...} called at /«PKGBUILDDIR»/blib/lib/App/Sqitch.pm line 18
# require App/Sqitch.pm called at t/blank.t line 12
# main::BEGIN() called at /«PKGBUILDDIR»/blib/lib/App/Sqitch.pm line 18
# eval {...} called at /«PKGBUILDDIR»/blib/lib/App/Sqitch.pm line 18
#
# Looks like you failed 1 test of 34.
[...]
Test Summary Report
---
t/base.t (Wstat: 256 Tests: 242 Failed: 1)
Failed test: 242
Non-zero exit status: 1
t/blank.t (Wstat: 256 Tests: 34 Failed: 1)
Failed test: 34
Non-zero exit status: 1
t/change.t(Wstat: 256 Tests: 85 Failed: 1)
Failed test: 85
Non-zero exit status: 1
t/changelist.t(Wstat: 256 Tests: 351 Failed: 1)
Failed test: 351
Non-zero exit status: 1
t/config.t(Wstat: 256 Tests: 344 Failed: 1)
Failed test: 344
Non-zero exit status: 1
t/linelist.t (Wstat: 256 Tests: 28 Failed: 1)
Failed test: 28
Non-zero exit status: 1
t/pragma.t(Wstat: 256 Tests: 10 Failed: 1)
Failed test: 10
Non-zero exit status: 1
t/tag.t (Wstat: 256 Tests: 27 Failed: 1)
Failed test: 27
Non-zero exit status: 1
Files=40, Tests=5541, 45 wallclock secs ( 1.65 usr 0.16 sys + 41.75 cusr
2.17 csys = 45.73 CPU)
Result: FAIL
--
Niko Tyni nt...@debian.org
---End Message---
---BeginMessage---
Source: sqitch
Source-Version: 0.9991-1
We believe that the bug you reported is fixed in the latest version of
sqitch, 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 785...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann gre...@debian.org (supplier of updated sqitch package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 14 May 2015 22:28:40 +0200
Source: sqitch
Binary: sqitch
Architecture: source all
Version: 0.9991-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org
Changed-By: gregor herrmann gre...@debian.org
Description:
sqitch - Sane database change management
Closes: 785229
Changes:
sqitch (0.9991-1) unstable; urgency=medium
.
* Team upload.
* Add debian/upstream/metadata
* Import upstream version 0.9991
Fixes FTBFS: new warnings (Closes: #785229)
* debian/watch: add uversionmangle in case upstream goes back from 4
minor digits to less.
* Update fix-bad-whatis-man.patch.
* Move libmodule-build-perl to Build-Depends (needed during clean).
* Make (build) dependency on libpath-class-perl versioned.
* Drop a couple of version constraint from (build) dependencies.
They are all satisfied in (old)oldstable.
* Update years of upstream
Processed: Re: Bug#785091: spatialite-bin: spatialite gives a Segmentation fault.
Processing control commands: fixed -1 spatialite-bin/4.2.1~rc1-3 Bug #785091 [spatialite-bin] spatialite-bin: spatialite gives a Segmentation fault. The source spatialite-bin and version 4.2.1~rc1-3 do not appear to match any binary packages Marked as fixed in versions spatialite-bin/4.2.1~rc1-3; no longer marked as fixed in versions spatialite-bin/4.2.1~rc1-3. -- 785091: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#785091: spatialite-bin: spatialite gives a Segmentation fault.
Processing control commands: fixed -1 spatialite-bin/4.2.1~rc1-3 Bug #785091 [spatialite-bin] spatialite-bin: spatialite gives a Segmentation fault. The source spatialite-bin and version 4.2.1~rc1-3 do not appear to match any binary packages Marked as fixed in versions spatialite-bin/4.2.1~rc1-3. -- 785091: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785091 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785091: spatialite-bin: spatialite gives a Segmentation fault.
Control: fixed -1 spatialite-bin/4.2.1~rc1-3 On 05/13/2015 01:42 AM, Sebastiaan Couwenberg wrote: I'll try spatialite 4.2.x in experimenal to see if that also breaks now. spatialite-tools (4.2.1~rc1-3) in experimental still works fine. I'll need to find the change(s) between 4.1.1 and 4.2.1 responsible so I can backport them for the package in unstable. The 4.2.1 release candidate in experimental is not ready to move to unstable yet. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769354: marked as done (dar-static: statically linked against libc6 without a Built-Using: field)
Your message dated Thu, 14 May 2015 22:19:14 + with message-id e1yt1tg-0007gy...@franck.debian.org and subject line Bug#769354: fixed in dar 2.4.17-1 has caused the Debian Bug report #769354, regarding dar-static: statically linked against libc6 without a Built-Using: field to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769354: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dar-static Version: 2.4.15-1 Severity: serious Tags: jessie-ignore Justification: Policy 7.8 dar-static provides /usr/bin/dar_static which is statically linked against libc6. According to Debian Policy §7.8 such a package MUST list the glibc source package (and possibly others) in the Built-Using: field. Note: While this is a serious policy violation, it has been agreed with the release team that this is not a blocker bug for the Jessie release. That's why the jessie-ignore tag is added. This makes this bug non RC. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: dar Source-Version: 2.4.17-1 We believe that the bug you reported is fixed in the latest version of dar, 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 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) g...@debian.org (supplier of updated dar 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: Thu, 14 May 2015 17:53:59 + Source: dar Binary: libdar-dev libdar64-5000 dar-static dar dar-docs Architecture: source all amd64 Version: 2.4.17-1 Distribution: unstable Urgency: low Maintainer: Laszlo Boszormenyi (GCS) g...@debian.org Changed-By: Laszlo Boszormenyi (GCS) g...@debian.org Description: dar- Disk ARchive: Backup directory tree and files dar-docs - Disk ARchive: Backup directory tree and files dar-static - Disk ARchive: Backup directory tree and files libdar-dev - Disk ARchive: Development files for shared library libdar64-5000 - Disk ARchive: Shared library Closes: 751968 769354 Changes: dar (2.4.17-1) unstable; urgency=low . * New upstream release. * Specify libraries dar-static linked with (closes: #769354). * Install darrc config file (closes: #751968). * Install localization files. Checksums-Sha1: e70af4f2f3c8e494ae1ef35cfea95d77ffc11609 2003 dar_2.4.17-1.dsc b0a5b87ead362baf21190899d34766aa65d76bba 1800050 dar_2.4.17.orig.tar.gz adc24647ee17d0438af8359168de8c028e656d96 5680 dar_2.4.17-1.debian.tar.xz b3c43f2ca90120900c8e5a45fd4c35e17bfe565e 917138 dar-docs_2.4.17-1_all.deb b45bf239ee091fe04ab925c275a6177e73d3661c 765304 libdar-dev_2.4.17-1_amd64.deb ae2a406163558ef22dd4632f63e2f791c419b229 552028 libdar64-5000_2.4.17-1_amd64.deb 282fbfb86578f2746d7ded71a36cba70689fd0b5 1364076 dar-static_2.4.17-1_amd64.deb 6904e17b51badd39134eca30dec8561954a1c850 335934 dar_2.4.17-1_amd64.deb Checksums-Sha256: 223f0bacb5f53fad8aee99dd111919f01449f5279d923415a7f2e86d4487ea4e 2003 dar_2.4.17-1.dsc 5d861c39698b77124680914741e1e40e7e9bedb3fcedc6df8d468e619479833c 1800050 dar_2.4.17.orig.tar.gz ccf38a7d7156d16df8ad3db061e762f9b419aba0c7c4465b2a8bfb8a8cbbd486 5680 dar_2.4.17-1.debian.tar.xz 7aca034bff1bd510e68892269ccba3577fa3f17067b1dae66b49f20c701032ce 917138 dar-docs_2.4.17-1_all.deb 889f88cce6ab1061ac0a06ed95f5adba039ad1eb73c4539403fd4928cebe8e71 765304 libdar-dev_2.4.17-1_amd64.deb 84982de9842db5955f43cc85cfd4f5745ce474ac3f3ffd54a938dc3df4f4964b 552028 libdar64-5000_2.4.17-1_amd64.deb 97e6f25da86f849a63ceaef6493bf1b12e9bbee7a216acdf5891183b83ec4eaf 1364076 dar-static_2.4.17-1_amd64.deb f849154e45fb0ed3df60cea1dc5693dabc0288abf45ed59ce13c16d742aaeca6 335934 dar_2.4.17-1_amd64.deb Files: de47eba39d8aba6519a4a33211ffa10c 2003 utils optional dar_2.4.17-1.dsc b8986a75539a901f70854d7068e898af 1800050 utils optional
Bug#784859: Uninstallable in Sid: too strict php-version constraints
Control: retitle -1 Uninstallable in Sid: too strict version constraints Control: tags -1 sid stretch On Sat, May 09, 2015 at 12:57:29PM -0400, David Prévot wrote: Package: ampache-common Version: 3.6-rzb2752+dfsg-5 The version constraint for php-getid3 ( 1.9.8.0~) is too strict for no good reason. Ditto for libphp-phpmailer (and potentially every other dependency, since they all have the same kind of constraints), since the packages depend on libphp-phpmailer (= 5.2.9+dfsg) while 5.2.10+dfsg-1 is in Sid. Tagging it for sid + stretch in the hope none of the dependencies will be updated to a new upstream release à la Mozilla during Jessie’s life time. Maybe dh_linktree is not as useful as it looks. signature.asc Description: Digital signature
Processed: Re: Bug#784859: Uninstallable in Sid: too strict php-version constraints
Processing control commands: retitle -1 Uninstallable in Sid: too strict version constraints Bug #784859 [ampache-common] Uninstallable in Sid: too strict php-getid3 version constraint Changed Bug title to 'Uninstallable in Sid: too strict version constraints' from 'Uninstallable in Sid: too strict php-getid3 version constraint' tags -1 sid stretch Bug #784859 [ampache-common] Uninstallable in Sid: too strict version constraints Added tag(s) sid and stretch. -- 784859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784565: [X2Go-Dev] [pkg-x2go-devel] Bug#784565: Bug#784565: nx-libs-lite: parts are derived from non-free code
Hi again, On Do 14 Mai 2015 07:55:42 CEST, Mike Gabriel wrote: [...] (The mail address I have from Zachary may be outdated, so any current contact address is highly welcome, in case the mail address being used will bounce back). As it seems, the publicly known mail address of Zachary Vonler at austin.utexas.edu is outdated. @Brian: if you happen to have a recent mail address of Zachary, could you please provide it to me privately? Thanks. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpBAyDoNQwRu.pgp Description: Digitale PGP-Signatur
Bug#775760: marked as done (openjdk-8 rejected due to wrong lintian warning)
Your message dated Thu, 14 May 2015 06:34:04 +
with message-id e1ysmia-0007ky...@franck.debian.org
and subject line Bug#775760: fixed in lintian 2.5.31
has caused the Debian Bug report #775760,
regarding openjdk-8 rejected due to wrong lintian warning
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
775760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: lintian,ftp.debian.org,openjdk-8
Severity: serious
Tags: sid
openjdk-8 is rejected due to wrong a wrong (?) lintian warning, complaining
about
openjdk-8-dbg: lintian output:
'library-in-debug-or-profile-should-not-be-stripped
usr/lib/debug/.build-id/06/06a3353ef3b92e2624bdf24b2a1aa5216a7975dd.debug',
automatically rejected package.
openjdk-8-dbg: lintian output:
'library-in-debug-or-profile-should-not-be-stripped
usr/lib/debug/.build-id/d8/d820d9eaa9f677d3ae4505419dd779adaecaae2e.debug',
automatically rejected package.
This is for the file libjvm.so, which is only partially stripped, not calling
--strip-unneeded, because some data is needed for reflection stuff.
See [1] (search for dh_strip). I don't see anything wrong with this, however
now it is not possible to override the error, and the package cannot be uploaded
anymore. I assume this is a bad lintian check, so please fix it, and maybe
revert the auto-reject until it is resolved. An alternative workaround would be
to not strip libjvm.so at all.
The current openjdk-8-dbg package in unstable shows the same issue.
Matthias
[1]
https://buildd.debian.org/status/fetch.php?pkg=openjdk-8arch=i386ver=8u40~b09-1stamp=1413300379
---End Message---
---BeginMessage---
Source: lintian
Source-Version: 2.5.31
We believe that the bug you reported is fixed in the latest version of
lintian, 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 775...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Niels Thykier ni...@thykier.net (supplier of updated lintian 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: Thu, 14 May 2015 08:11:27 +0200
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.31
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers lintian-ma...@debian.org
Changed-By: Niels Thykier ni...@thykier.net
Description:
lintian- Debian package checker
Closes: 732246 749103 751949 756128 764015 765344 766118 767107 768884 769036
769679 769845 770068 771054 771113 774729 775467 775760 776267 776480 776535
776954 778323 778556 778558 778820 780474 781235 781396 781397 782902 783327
784012 784277 784639
Changes:
lintian (2.5.31) unstable; urgency=medium
.
* checks/binaries.pm:
+ [BR] Do not tag with
library-in-debug-or-profile-should-not-be-stripped
when file add not stripped, too many notes to its
output. Thanks to Jakub Wilk. (Closes: #775760).
+ [AB] Ignore tEH and tEh for spelling-error-in-binary. (Closes:
#782902; bug report and patch by Tomasz Buchert, thanks!)
* checks/changelog-file.{desc,pm}:
+ [BR] Correct a typo on tag name and do not raise
bad-intended-distribution if distribution is still
set to UNRELEASED. (Closes: #765344).
+ [NT] Apply patches from Ben Finney to permit quotes around
the distribution name in the to unstable entries.
(Closes: #784012)
* checks/control-file.{desc,pm}:
+ [BR] Apply patch from Johannes Schauer in order
to detect obsolete XS-Testsuite header.
(Closes: #770068).
+ [AB] New check for multiline architecture fields in debian/control.
(Closes: #780474)
+ [NT] Apply patch from Guillem Jover to update the description
of the xs-testsuite-header-in-debian-control tag.
(Closes: #781397)
* checks/copyright-file.pm:
+ [NT] Permit the use of pkg:arch dependencies when packages use
symlinked doc-dirs.
* checks/cruft.{desc,pm}:
+ [NT] Import d/pycompat is deprecated check from
lintian4python.
* checks/dbus.{desc,pm}:
+ [NT] Apply patch series from Simon McVittie to
improve the
Bug#784009: Segmentation fault
On 2015-05-10 Magnus Holmgren holmg...@debian.org wrote: måndagen den 4 maj 2015 19.32.52 skrev Andreas Metzler: [...] I think GnuTLS being listed as part of the guile-1.8 removal is an error in the reporting script, GnuTLS has moved to guile-2.0 in 2013. OTOH I hope we can have gnutls linked against nettle 3.x without needing to update to 3.4.x. (Which would couple together two transitions. And 3.4 ist still a development release.) http://lists.gnutls.org/pipermail/gnutls-devel/2015-May/007583.html A rather significant patch, but since someone has already done it, will you use it? 3.1-1 has entered experimental, as you may have seen. Should I upload 3.1.1-1 to unstable or to experimental for now? Given that it originates from GnuTLS' author I will try to use it. Could you upload 3.1.1-1 to experimental? Have you already opened a transition tracker, BTW? cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744115: codeblocks: diff for NMU version 13.12-3.1
Hi Olly, On Wed, May 13, 2015 at 5:55 PM, Olly Betts o...@survex.com wrote: It's high time we actually got rid of wxwidgets2.8, so I took another look at this bug. Upstream have yet to make a release from trunk, so I tried to make minimal changes to get 13.12 working rather than packaging a VCS snapshot. Olly Betts wrote: On Thu, Apr 10, 2014 at 04:59:25AM -0700, Vincent Cheng wrote: My understanding is that upstream is working towards porting codeblocks for wx 3.0, but it's currently not fully stable yet (e.g. #736368). The issue there is most likely because wx 3.0 enables WXDEBUG mode by default which includes checks for incorrect API usage, whereas with wx 2.8 you had to specify it explicitly when you built the library. In other words, codeblocks is misusing the wx API, but with 2.8 this gets quietly ignored by default, whereas 3.0 reports it by default. I bet if you rebuilt codeblocks using the WXDEBUG build of 2.8 (available in Debian in package libwxgtk2.8-dbg - despite the name, this isn't debug symbols, but a separate build of the library) you'd see this assertion too. The simplest way to address this is to build codeblocks with -DNDEBUG (pass it in CPPFLAGS usually), which makes wx 3.0 behave as a default build of 2.8 would. I tested this workaround and I can't reproduce #736368 in a build with -DNDEBUG defined. It's a shame we didn't actually test that before jessie - sorry about that. Running cleanly without disabling the WXDEBUG checks would be better, but these checks are off by default in wx2.8, so it's no worse than the current situation, and it doesn't seem worth investing time trying to track down the relevant fixes from trunk. Ack; sorry on my side for dropping the ball on this. Vincent Cheng vch...@debian.org writes: In case I haven't made it clear previously, you're more than welcome to NMU codeblocks; I doubt David and/or Michael would object. Thanks, I've prepared an NMU for codeblocks (versioned as 13.12-3.1) and uploaded it. Thanks, I've committed your changes to collab-maint as well. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783683: marked as done (restarting cron kills running jobs)
Your message dated Thu, 14 May 2015 07:34:04 + with message-id e1ysnee-0006ok...@franck.debian.org and subject line Bug#783683: fixed in cron 3.0pl1-128 has caused the Debian Bug report #783683, regarding restarting cron kills running jobs to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 783683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cron Version: 3.0pl1-127 Severity: normal Dear Maintainer, on Debian Jessie the cron daemon is being started with the parameter -f (for running in foreground). Now, when restarting the daemon using systemctl restart cron.service all running processes *initiated* by the cron daemon will be killed. I think the culprit is in this file: /lib/systemd/system/cron.service sol3@leeds:~$ ps auxww | grep '[c]ron' root 8694 0.0 0.0 27464 2644 ?Ss Apr28 0:00 /usr/sbin/cron -f sol3@leeds:~$ In the past (with Squeeze, Wheezy etc.) cron was always daemonized and that behaviour never(!) happened, I think this -f is a pretty dangerous thing. Kind regards, Joerg Morbitzer -- Package-specific info: --- EDITOR: --- /usr/bin/editor: /usr/bin/vim.gtk --- /usr/bin/crontab: -rwxr-sr-x 1 root crontab 36008 Oct 26 2014 /usr/bin/crontab --- /var/spool/cron: drwxr-xr-x 5 root root 4096 Jan 28 11:44 /var/spool/cron --- /var/spool/cron/crontabs: drwx-wx--T 2 root crontab 4096 Mar 27 09:37 /var/spool/cron/crontabs --- /etc/cron.d: drwxr-xr-x 2 root root 4096 Jan 28 11:45 /etc/cron.d --- /etc/cron.daily: drwxr-xr-x 2 root root 4096 Apr 20 07:03 /etc/cron.daily --- /etc/cron.hourly: drwxr-xr-x 2 root root 4096 Jan 28 11:40 /etc/cron.hourly --- /etc/cron.monthly: drwxr-xr-x 2 root root 4096 Jan 28 11:45 /etc/cron.monthly --- /etc/cron.weekly: drwxr-xr-x 2 root root 4096 Jan 28 11:45 /etc/cron.weekly -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages cron depends on: ii adduser 3.113+nmu3 ii debianutils 4.4+b1 ii dpkg 1.17.25 ii init-system-helpers 1.22 ii libc62.19-18 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii lsb-base 4.1+Debian13+nmu1 Versions of packages cron recommends: ii exim4 4.84-8 ii exim4-daemon-light [mail-transport-agent] 4.84-8 Versions of packages cron suggests: ii anacron2.3-23 pn checksecurity none ii logrotate 3.8.7-1+b1 Versions of packages cron is related to: pn libnss-ldap none pn libnss-ldapd none pn libpam-ldap none pn libpam-mount none ii nis 3.17-33 pn nscd none -- no debconf information ---End Message--- ---BeginMessage--- Source: cron Source-Version: 3.0pl1-128 We believe that the bug you reported is fixed in the latest version of cron, 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 783...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Kastner deb...@kvr.at (supplier of updated cron package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 03 May 2015 15:25:18 +0200 Source: cron Binary: cron Architecture: source i386 Version: 3.0pl1-128 Distribution: unstable Urgency: medium Maintainer: Javier Fernández-Sanguino Peña j...@debian.org Changed-By: Christian Kastner deb...@kvr.at Description: cron - process scheduling daemon Closes: 783683 Changes: cron (3.0pl1-128) unstable; urgency=medium . * d/cron.service: Use KillMode=process to kill only the daemon. The default of KillMode=control-group kills all the processes in the control group, for example when restarting the daemon. This is a deviation from past behavior we do not want. Thanks, Alexandre Detiste!
Bug#784070: Workaround
This is the workaround to boot the system. In busybox manually start raid volumes: mdadm --run /dev/md0 mdadm --run /dev/md1 mdadm --run /dev/md2 mdadm --run /dev/md close busybox with exit system will now boot on next reboot everything is fine because the arry was in state: active, degraded and the faulty member is now detached. If you have lvm the system will not boot on first close of busybox. You can try to close the second busybox (with exit) and then reboot the system. Now lvm should start correctly.
Bug#785281: php-seclib and php-math-biginteger: error when trying to install together
Package: php-math-biginteger,php-seclib Version: php-math-biginteger/1.0.2-2 Version: php-seclib/0.3.10-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2015-05-14 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Preconfiguring packages ... Selecting previously unselected package libperl4-corelibs-perl. (Reading database ... 10939 files and directories currently installed.) Preparing to unpack .../libperl4-corelibs-perl_0.003-1_all.deb ... Unpacking libperl4-corelibs-perl (0.003-1) ... Selecting previously unselected package lsof. Preparing to unpack .../lsof_4.86+dfsg-1_amd64.deb ... Unpacking lsof (4.86+dfsg-1) ... Selecting previously unselected package ucf. Preparing to unpack .../archives/ucf_3.0030_all.deb ... Moving old data out of the way Unpacking ucf (3.0030) ... Selecting previously unselected package psmisc. Preparing to unpack .../psmisc_22.21-2_amd64.deb ... Unpacking psmisc (22.21-2) ... Selecting previously unselected package php5-common. Preparing to unpack .../php5-common_5.6.7+dfsg-1_amd64.deb ... Unpacking php5-common (5.6.7+dfsg-1) ... Selecting previously unselected package php-math-biginteger. Preparing to unpack .../php-math-biginteger_1.0.2-2_all.deb ... Unpacking php-math-biginteger (1.0.2-2) ... Selecting previously unselected package php-seclib. Preparing to unpack .../php-seclib_0.3.10-2_all.deb ... Unpacking php-seclib (0.3.10-2) ... dpkg: error processing archive /var/cache/apt/archives/php-seclib_0.3.10-2_all.deb (--unpack): trying to overwrite '/usr/share/php/Math/BigInteger.php', which is also in package php-math-biginteger 1.0.2-2 Processing triggers for man-db (2.7.0.2-5) ... Errors were encountered while processing: /var/cache/apt/archives/php-seclib_0.3.10-2_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/share/php/Math/BigInteger.php This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://qa.debian.org/dose/file-overwrites.html. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#785263: gpsd: ignores serial devices
Processing control commands: severity 785263 normal Bug #785263 [gpsd] gpsd: ignores serial devices Severity set to 'normal' from 'grave' tags 785263 unreproducible moreinfo Bug #785263 [gpsd] gpsd: ignores serial devices Added tag(s) unreproducible and moreinfo. -- 785263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785263: gpsd: ignores serial devices
control: severity 785263 normal control: tags 785263 unreproducible moreinfo hi, On 05/14/2015 01:17 AM, Folkert van Heusden wrote: gpsd in jessie no longer works for serial devices. In /etc/default/gpsd I usually configure /dev/ttyS1 with the -n flag but since jessie this is ignored. The device is not openend at start, and also not if I explicitly start a client (e.g. gpsmon). Tried the version of experimental as well but that version doesn't work either. What you are seing is probably a permission issue. You might want to check if the user gpsd is able to access that device. Also check if something is being reported in the logs. To see if gpsd is working at all, please stop gpsd.service and gpsd.socket and run gpsd -n -N -D 1024 /dev/ttyS1 cheers, Bernd -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-trunk-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gpsd depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.22 ii libbluetooth35.23-2+b1 ii libc62.19-18 ii libdbus-1-3 1.8.16-1 ii libgps22 3.12-1 ii libusb-1.0-0 2:1.0.19-1 ii lsb-base 4.1+Debian13+nmu1 ii netbase 5.3 ii systemd-sysv 215-17 Versions of packages gpsd recommends: ii python 2.7.9-1 ii udev215-17 Versions of packages gpsd suggests: ii dbus 1.8.16-1 ii gpsd-clients 3.12-1 -- Configuration Files: /etc/default/gpsd changed: START_DAEMON=true USBAUTO=false DEVICES=/dev/ttyS1 GPSD_OPTIONS=-n -- debconf information: gpsd/daemon_options: -n gpsd/socket: /var/run/gpsd.sock gpsd/device: /dev/ttyS1 gpsd/start_daemon: true gpsd/autodetection: false -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug#785214 marked as pending
Processing commands for cont...@bugs.debian.org: tag 785214 pending Bug #785214 [src:sitesummary] sitesummary: postinst hangs after exit Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 785214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug#785215 marked as pending
Processing commands for cont...@bugs.debian.org: tag 785215 pending Bug #785215 [src:sitesummary] sitesummary: breaks apache2.4 after uninstall Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 785215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785214: marked as pending
tag 785214 pending thanks Hello, Bug #785214 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=debian-edu/upstream/sitesummary.git;a=commitdiff;h=2ee3660 --- commit 2ee36603d4e1985bed1d9724f3cb3d3b068e01a9 Author: Dominik George n...@naturalnet.de Date: Wed May 13 16:38:02 2015 +0200 Changelog for two bugfixes diff --git a/debian/changelog b/debian/changelog index 231a412..a1a720d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +sitesummary (0.1.17+nmu1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix hanging postinst script (Closes: #785214). + * Fix dangling symlink in apache config after removal (Closes: #785215). + + -- Dominik George n...@naturalnet.de Wed, 13 May 2015 16:36:20 +0200 + sitesummary (0.1.17) unstable; urgency=high * Fix installation problem when sitesummary is preseeded to update -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785215: marked as pending
tag 785215 pending thanks Hello, Bug #785215 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=debian-edu/upstream/sitesummary.git;a=commitdiff;h=2ee3660 --- commit 2ee36603d4e1985bed1d9724f3cb3d3b068e01a9 Author: Dominik George n...@naturalnet.de Date: Wed May 13 16:38:02 2015 +0200 Changelog for two bugfixes diff --git a/debian/changelog b/debian/changelog index 231a412..a1a720d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +sitesummary (0.1.17+nmu1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix hanging postinst script (Closes: #785214). + * Fix dangling symlink in apache config after removal (Closes: #785215). + + -- Dominik George n...@naturalnet.de Wed, 13 May 2015 16:36:20 +0200 + sitesummary (0.1.17) unstable; urgency=high * Fix installation problem when sitesummary is preseeded to update -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784070: Update
The issue seems to be in udev scripts as Pascal Hambourg said. In debian 7 there is one script in intramfs to manage md devices: /lib/udev/rules.d/64-md-raid.rules In debian 8 there are two different scripts: /lib/udev/rules.d/63-md-raid-arrays.rules /lib/udev/rules.d/64-md-raid-assembly.rules The issue has been introduced here. These files are in package mdadm.
