Bug#745835: lynx-cur: certificate revocation is not checked
Control: unmerge -1 Control: reopen -1 Control: found -1 2.8.9dev5-2 This problem still occurs. For a new testcase URL: lynx https://www.vinc17.net:4434/ does not give an error, contrary to Firefox. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725284: proper resume hooks
In the face of the race condition with systemd unit files, reported by Michael Biebl, there seem to exist different alternatives. Lennart Poettering: https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=nobug=744753#40 a service which needs to be restarted on cases like this sounds wrong. Thats a hack really. The service should just watch time changes and react correctly to that. i.e. use TFD_TIMER_CANCEL_ON_SET. THis will report wallclock changes relative to monotonic time, which is what you want to watch for this. All system resumes will trigger this, of course. and Since a long time we had on our TODO list to support timer units that are triggered when the system clock changes, based on TFD_TIMER_CANCEL_ON_SET. Hasn't been implemented yet, should be fairly easy though. OnClockChange=yes And in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780956 the dev showed that udev already has proper hooks for resume events. So these may be proper mechanisms for packages to ship with a resume hook. And the last one is already tried and proven by laptop-mode-tools. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783374: last NMU patch breaks gparted completely (on my system)
On Sun, 26 Apr 2015 12:09:16 -0400 Michael Gilbert mgilb...@debian.org wrote: control: tag -1 confirmed control: severity -1 serious On Sun, Apr 26, 2015 at 9:46 AM, Felix Zielcke wrote: Just tried out the newest upload of gparted. Which fails completely The one before which is in jessie works fine. I.e. 0.19.0-2 without the NMU fix gparted needs a newer udisks2, see #782838. Proposed patch attached. Best wishes, Mike Thanks for the quick answer. Now it works. Didn't see that bug cause it's already marked done. So the affects doestn't show it in gparted bug list. Just saw the new udisks2 is now uploaded to unstable -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745835: lynx-cur: certificate revocation is not checked
Control: severity -1 serious Setting same severity as bug 752610 (which is also about certificate checking). -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: lynx-cur: certificate revocation is not checked
Processing control commands: severity -1 serious Bug #745835 [lynx-cur] lynx-cur: certificate revocation is not checked Severity set to 'serious' from 'grave' -- 745835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745835 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#783430: Useless in Debian
On Sun, 26 Apr 2015, David Prévot wrote:
Raphaël (X-D-CC) requested this package (#678093) as a Tuleap
dependency, but tuleap is not in Debian (not even {IT,RF)P’ed AFAICT).
Thomas’ concerns raised over two years ago in the RFP are still valid
(upstream package is not maintained, and “the package is marked as
quality beta and there has been no upstream release since end of
2009”).
Furthermore, the package has a very low popcon.
For the record, Tuleap still uses this PHP library. It would be
interesting to document in this bug report what alternative PHP
library people are expected to use in Debian...
It's true that the Tuleap packaging never reached a state where
it was ready to be integrated into Debian. That said there are
likely some Tuleap users who are running it on top of Debian (albeit
in a non-packaged way).
I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).
No objection from me if there is another PHP library providing similar
features available in Debian. But I also don't see a pressing need to
drop that code since it seems to be working well.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: notfound 774171 in 1:4.1.4-1
Processing commands for cont...@bugs.debian.org:
notfound 774171 1:4.1.4-1
Bug #774171 {Done: Felix Geyer fge...@debian.org} [unrar] unrar: symlink
directory traversal
Ignoring request to alter found versions of bug #774171 to the same values
previously set
notfound 774171 1:3.9.10-1
Bug #774171 {Done: Felix Geyer fge...@debian.org} [unrar] unrar: symlink
directory traversal
Ignoring request to alter found versions of bug #774171 to the same values
previously set
thanks
Stopping processing here.
Please contact me if you need assistance.
--
774171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774171
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#783543: miscompile of _mm256_permutevar8x32_epi32
Package: llvm-toolchain-3.6
Version: 1:3.6-2
Severity: serious
clang 3.6 in debian miscompiles _mm256_permutevar8x32_epi32
it swaps the two first arguments:
$ apt-cache policy clang-3.6
clang-3.6:
Installed: 1:3.6-2
Candidate: 1:3.6-2
Version table:
*** 1:3.6-2 0
500 http://ftp.de.debian.org/debian/ unstable/main amd64
$ cat test.c
#include immintrin.h
__m256i fun (__m256i a, __m256i o) {
return _mm256_permutevar8x32_epi32(a, o);
}
$ clang-3.6 test.c -mavx2 -c -O2
$ objdump -d test.o
test.o: file format elf64-x86-64
Disassembly of section .text:
fun:
0: c4 e2 7d 36 c1 vpermd %ymm1,%ymm0,%ymm0
5: c3 retq
the correct result is:
vpermd %ymm0,%ymm1,%ymm0
clang 3.5 seems to produce the right result so this is a 3.6 regression
--
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#783537: important tools missing
Processing control commands: severity -1 normal Bug #783537 [git-buildpackage] important tools missing Severity set to 'normal' from 'serious' -- 783537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783537 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#783537: important tools missing
Control: severity -1 normal Hi Michael, Michael Biebl wrote: Since the latest update, some important tools are missing. E.g. all git-import-* tools are gone. That's on purpose. Please read the changelog, e.g. https://packages.qa.debian.org/g/git-buildpackage/news/20150220T194850Z.html Citing from there: * [e3a8666] Drop all gbp-* and git-* commands as announced in the deprecation notice from June 2013. From now on only gbp command is supported. Since the man pages for those tools are still shipped in the package, I think that's the real bug. :-) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782996: smsd: 'reload' function of initscript broken if used by systemd
Am 21.04.2015 um 15:15 schrieb Jonas Meurer:
I consider this bug as release-critical for Jessie, as it renders
smmstools unusable on Jessie installations whenever logrotate is
installed. Thus I suggest to push the fix into Jessie within the next
days. I'll gladly do an NMU if the maintainer(s) don't have the time
to push this fix into Jessie in time.
According to release managers, this update won't make it into Jessie,
which is already in the quiet period (shortly before release). Instead,
a fixed package should be uploaded to stable-proposed-updates in order
to make it into the first point release of Jessie (8.1).
If nobody speaks up, then I intend to upload the NMU to unstable next
week, wait one or two weeks and upload to stable-proposed-updates
afterwards.
I just uploaded the NMU to unstable now. You find the final NMU diff
attached to this mail. Only difference to my last patch is that the
changelog entry contains the number of this bugreport now.
I'll go ahead with an upload to stable-proposed-updates within the next
days.
Cheers,
jonas
diff -u smstools-3.1.15/debian/changelog smstools-3.1.15/debian/changelog
--- smstools-3.1.15/debian/changelog
+++ smstools-3.1.15/debian/changelog
@@ -1,3 +1,17 @@
+smstools (3.1.15-1.2) unstable; urgency=high
+
+ * NMU by Jonas Meurer to push the fix into Jessie.
+ * Fix initscript (debian/init.d):
+* drop action 'reload' as it does not what policy demands it to do. Use
+ 'force-reload' in logrotate post-rotate action. This fixes 'force-reload'
+ action when used through systemd tools and prevents the smsd daemon
+ process from being killed at every log rotation. (closes: #782996)
+* source /lib/lsb/init-functions in order to make systemd tools aware of
+ status changes to the daemon that have been caused by invoking the
+ initscript directly.
+
+ -- Jonas Meurer m...@debian.org Mon, 27 Apr 2015 20:45:40 +0200
+
smstools (3.1.15-1.1) unstable; urgency=low
* NMU - preventing smstools from entering jessie.
diff -u smstools-3.1.15/debian/init.d smstools-3.1.15/debian/init.d
--- smstools-3.1.15/debian/init.d
+++ smstools-3.1.15/debian/init.d
@@ -25,6 +25,8 @@
test -x $DAEMON || exit 0
+. /lib/lsb/init-functions
+
if [ ! -f /etc/default/$PACKAGE ]
then
exit 1
@@ -218,17 +220,6 @@
echo $NAME.
;;
- reload)
- echo -n Reloading $DESC:
- status
- if [ $? = 0 ]; then
- stop restart
- start
- else
- echo $NAME is not running.
- fi
-
- ;;
restart|force-reload)
echo -n Restarting $DESC:
@@ -237,7 +228,7 @@
;;
*)
- echo Usage: /etc/init.d/$NAME {start|stop|force-stop|reload|force-reload|restart|status}
+ echo Usage: /etc/init.d/$NAME {start|stop|force-stop|force-reload|restart|status}
exit 3
;;
esac
diff -u smstools-3.1.15/debian/logrotate smstools-3.1.15/debian/logrotate
--- smstools-3.1.15/debian/logrotate
+++ smstools-3.1.15/debian/logrotate
@@ -5,5 +5,5 @@
missingok
postrotate
-invoke-rc.d smstools reload /dev/null
+invoke-rc.d smstools force-reload /dev/null
endscript
}
Bug#783537: important tools missing
On Mon, Apr 27, 2015 at 09:59:53PM +0200, Michael Biebl wrote: Am 27.04.2015 um 21:54 schrieb Axel Beckert: Control: severity -1 normal Hi Michael, Michael Biebl wrote: Since the latest update, some important tools are missing. E.g. all git-import-* tools are gone. That's on purpose. Please read the changelog, e.g. https://packages.qa.debian.org/g/git-buildpackage/news/20150220T194850Z.html Citing from there: * [e3a8666] Drop all gbp-* and git-* commands as announced in the deprecation notice from June 2013. From now on only gbp command is supported. Could we at least have a big fat NEWS entry about this. See my mail: it's coming. I had the various gbp tools embedded in several scripts, which are now all broken. Since the man pages for those tools are still shipped in the package, I think that's the real bug. :-) Well, even if this change was intentional, the way it was executed/announced was less then ideal. So I'm not sure severity normal qualifies here. That this will happen was announced in a NEWS entry back in June 2013. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783537: important tools missing
Hi, Michael Biebl wrote: * [e3a8666] Drop all gbp-* and git-* commands as announced in the deprecation notice from June 2013. From now on only gbp command is supported. Well, apparently that doesn't work $ gbp import-orig --uscan bash: git-buildpackage: command not found Worked for me (gbp import-orig called via the fixed dpt import-orig) about an hour ago. Any chance that uscan calls git-buildpackage via debian/watch for that package? Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783537: important tools missing
Am 27.04.2015 um 22:17 schrieb Axel Beckert: Hi, Michael Biebl wrote: * [e3a8666] Drop all gbp-* and git-* commands as announced in the deprecation notice from June 2013. From now on only gbp command is supported. Well, apparently that doesn't work $ gbp import-orig --uscan bash: git-buildpackage: command not found Worked for me (gbp import-orig called via the fixed dpt import-orig) about an hour ago. Any chance that uscan calls git-buildpackage via debian/watch for that package? $ cat debian/watch version=3 http://ftp.gnome.org/pub/GNOME/sources/gnome-disk-utility/([\d\.]+\d)/ \ gnome-disk-utility-(.*)\.tar\.xz $ gbp imTABbash: git-buildpackage: Kommando nicht gefunden. bash: git-buildpackage: Kommando nicht gefunden. $ gbp import-orig --uscan bash: git-buildpackage: Kommando nicht gefunden. Something looks completely borked here. I've restarted all my shell, even tried that with a fresh login on tty1. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#783174: tlsdate: Time retrieved from default host (www.ptb.de) jumping all over the place?
On 4/27/15, Rian Hunter r...@thelig.ht wrote: Hi, This totally hosed all of my systems!! Sorry to hear that this issue has caused you problems. :( I think relying on the internal server_random member of the ssl data structure is error prone and to me it's not unexpected that a server would randomize the timestamp part of their random ssl seed. The erroroneous code is in src/tlsdate-helper.c line 1207. That isn't a bug - code upstream in other proejcts has changed since this was implemented. At the time of creating tlsdate, the TLS spec specifically that it must not be randomized but rather a time stamp. My suggestion is that instead of changing the default server, instead default to using the HTTP Date header. This header is intended to contain the current time. That's a nice thing to do but realistically - you need to pick a server that you trust. I achieved this by changing the DAEMON_OPTS in /etc/default/tlsdated DAEMON_OPTS=-- /usr/bin/tlsdate -w That is a fine way to set it, yes. You also have to change how DAEMON_ARGS is set in /etc/init.d/tlsdated. Add this line after the line that sourced /etc/default/tlsdated: [ -r /etc/default/$NAME ] . /etc/default/$NAME DAEMON_ARGS=-f /etc/tlsdate/tlsdated.conf $DAEMON_OPTS If you think there is a different bug, please open another bug? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783545: Doesn’t work, abandonned upstream
Package: xul-ext-automatic-save-folder Version: 1.0.4-3 Severity: serious Hi, I was updating this package (to at least fix the watch file, but went a bit further, see the wip branch I just pushed), but was not able to make it work (even on a Jessie system with iceweasel 31.6.0esr-1). The (annoyingly ever displayed) extra tab explains very well what should be done, but I don’t get the Automatic Save Folder menu under the “What should Firefox do with this file?” box. Am I missing something? There are similar complaints on the amo review page [1], so maybe it’s “just” an incompatibility with recent iceweasel versions. Since upstream maintenance ended [2], I’m not sure there is much to do to fix the issue. 1: https://addons.mozilla.org/en-US/firefox/addon/automatic-save-folder/reviews/ 2: http://asf.mangaheart.org/?menu=5f=1t=167 I even tried to fetch the latest version from the upstream VCS to see if it works but didn’t get any further. Maybe the em:maxVersion29.* from install.rdf is to take seriously. Please, do follow up if the extension works for you. Unless someone objects, I’ll request a removal of this package in a few months (or sooner depending on the feedback). Regards David -- System Information: Debian Release: 8.0 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (100, 'buildd-unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-trunk-amd64 (SMP w/1 CPU core) 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) xul-ext-automatic-save-folder depends on no packages. Versions of packages xul-ext-automatic-save-folder recommends: ii iceweasel 37.0.2-1 xul-ext-automatic-save-folder suggests no packages. -- no debconf information signature.asc Description: Digital signature
Bug#783537: important tools missing
Package: git-buildpackage Version: 0.6.25 Severity: serious Since the latest update, some important tools are missing. E.g. all git-import-* tools are gone. Since the man pages for those tools are still shipped in the package, I assume something went wrong and those binaries were dropped by accident. Therefor the RC severity. Michael -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages git-buildpackage depends on: ii devscripts2.15.4 ii git 1:2.1.4-2.1 ii man-db2.7.0.2-5 ii python2.7.9-1 ii python-dateutil 2.2-2 ii python-pkg-resources 5.5.1-1 ii python-six1.9.0-2 Versions of packages git-buildpackage recommends: ii cowbuilder 0.73 ii pristine-tar 1.33 ii python-requests 2.4.3-6 Versions of packages git-buildpackage suggests: ii python-notify 0.1.1-4 ii unzip 6.0-16 -- 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
Processed: Re: Bug#783537: important tools missing
Processing control commands: severity -1 serious Bug #783537 [git-buildpackage] important tools missing Severity set to 'serious' from 'normal' -- 783537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783537 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#783537: important tools missing
Am 27.04.2015 um 22:15 schrieb Axel Beckert: Hi Michael, Michael Biebl wrote: * [e3a8666] Drop all gbp-* and git-* commands as announced in the deprecation notice from June 2013. From now on only gbp command is supported. Could we at least have a big fat NEWS entry about this. We have. Citing from /usr/share/doc/git-buildpackage/NEWS.Debian.gz: Sure, but please add another NEWS entry *when* the tools have actually been dropped. You know how people are, warning them in advance is nice, most people will only react when stuff actually happens (me included, at least in this case.) -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#783537: important tools missing
Hi Michael, Michael Biebl wrote: * [e3a8666] Drop all gbp-* and git-* commands as announced in the deprecation notice from June 2013. From now on only gbp command is supported. Could we at least have a big fat NEWS entry about this. We have. Citing from /usr/share/doc/git-buildpackage/NEWS.Debian.gz: git-buildpackage (0.6.0) unstable; urgency=low In order to provide a more consistent and git like interface a new gbp super command was added as a front end to all git-* and gbp-* commands. So what was either git-command or gbp-command is now gbp command The old commands are still provided for backward compatibility but will be removed in a future release so please update any scripts and tools relying on it. -- Guido Günther a...@sigxcpu.org Wed, 26 Jun 2013 13:38:16 +0200 IMHO that's a clear and precise statement and at the right place. I had the various gbp tools embedded in several scripts, which are now all broken. BTDT (https://bugs.debian.org/783521) and fixed it (http://deb.li/igDs0). Wasn't a big deal. Since the man pages for those tools are still shipped in the package, I think that's the real bug. :-) Well, even if this change was intentional, the way it was executed/announced was less then ideal. I think it was ok. At least I was fully aware (and unhappy) about git-buildpackage's git-* commands going away. I didn't really remember that also the gbp-* variants will go away, too, but it really wasn't a big deal to fix that, at least not in pkg-perl-tools. Had to touch like five files, but still. So I'm not sure severity normal qualifies here. For the superfluous man pages, normal is surely the highest severity it can deserve. And the remainder is a non-issue IMHO as it was announced for a long enough time. But I've set it to normal (and not to minor) as normal is the default severity and I primarily wanted to remove the RC severity without deciding about the real severity. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 783537 is grave
Processing commands for cont...@bugs.debian.org: severity 783537 grave Bug #783537 [git-buildpackage] important tools missing Severity set to 'grave' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 783537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783537 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#783174: tlsdate: Time retrieved from default host (www.ptb.de) jumping all over the place?
Hi, This totally hosed all of my systems!! I think relying on the internal server_random member of the ssl data structure is error prone and to me it's not unexpected that a server would randomize the timestamp part of their random ssl seed. The erroroneous code is in src/tlsdate-helper.c line 1207. My suggestion is that instead of changing the default server, instead default to using the HTTP Date header. This header is intended to contain the current time. I achieved this by changing the DAEMON_OPTS in /etc/default/tlsdated DAEMON_OPTS=-- /usr/bin/tlsdate -w You also have to change how DAEMON_ARGS is set in /etc/init.d/tlsdated. Add this line after the line that sourced /etc/default/tlsdated: [ -r /etc/default/$NAME ] . /etc/default/$NAME DAEMON_ARGS=-f /etc/tlsdate/tlsdated.conf $DAEMON_OPTS Thanks, Rian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783537: important tools missing
Hi Michael, Michael Biebl wrote: Well, apparently that doesn't work $ gbp import-orig --uscan bash: git-buildpackage: command not found Worked for me (gbp import-orig called via the fixed dpt import-orig) about an hour ago. Any chance that uscan calls git-buildpackage via debian/watch for that package? $ cat debian/watch version=3 http://ftp.gnome.org/pub/GNOME/sources/gnome-disk-utility/([\d\.]+\d)/ \ gnome-disk-utility-(.*)\.tar\.xz Ok. $ gbp imTABbash: git-buildpackage: Kommando nicht gefunden. bash: git-buildpackage: Kommando nicht gefunden. That looks like #783541 which you recently reported, too. Interestingly I've found no occurrence of git-buildpackage in /etc/bash_completion.d/git-buildpackage outside comments. Didn't dig deeper, though. $ gbp import-orig --uscan bash: git-buildpackage: Kommando nicht gefunden. Works fine here: → gbp import-orig --uscan gbp:info: Launching uscan... gbp:error: Uscan failed: uscan warning: In debian/watch, [...] (That error is expected and package-specific.) Something looks completely borked here. I've restarted all my shell, even tried that with a fresh login on tty1. Sounds like a valid way to get an uptodate shell. So no idea here. gbp's zsh completion as well as the above commmand work fine for me. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783174: tlsdate: Time retrieved from default host (www.ptb.de) jumping all over the place?
I think relying on the internal server_random member of the ssl data structure is error prone and to me it's not unexpected that a server would randomize the timestamp part of their random ssl seed. The erroroneous code is in src/tlsdate-helper.c line 1207. That isn't a bug - code upstream in other proejcts has changed since this was implemented. At the time of creating tlsdate, the TLS spec specifically that it must not be randomized but rather a time stamp. Yeah my bad, I was in a bit of a WTF-mood when I ran into this and I ignored that this is actually how tlsdate is supposed to work. I saw something called random being copied into something called timestamp and my WTF-meter went to 11. I understand that a silent interface change occurred. My suggestion is that instead of changing the default server, instead default to using the HTTP Date header. This header is intended to contain the current time. That's a nice thing to do but realistically - you need to pick a server that you trust. Yeah, trust is top of line, second is shared semantics. In this case I trusted www.ptb.de, we just had different ideas about how to interpret some bytes. I expect this will happen more and more. On the other hand, I expect the meaning of the Date: header to be more consistent across servers. So maybe the the most sane default is to tie it to a Debian-maintained server and use the Date header to defend against an accidentally incompatible SSL configuration. In the absence of an available Debian server in the short-to-medium term, I think -w would be an effective and easy-to-make change *today*. You also have to change how DAEMON_ARGS is set in /etc/init.d/tlsdated. Add this line after the line that sourced /etc/default/tlsdated: [ -r /etc/default/$NAME ] . /etc/default/$NAME DAEMON_ARGS=-f /etc/tlsdate/tlsdated.conf $DAEMON_OPTS If you think there is a different bug, please open another bug? Yeah this is a different little bug, I'll file. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: affects 776330
Processing commands for cont...@bugs.debian.org: # Drop incorrect affects for a useless bug that can’t be fixed in the package it is filled against… affects 776330 = Bug #776330 [php-kdyby-console] php-kdyby-console: uninstallable in sid: php-symfony-console (= 2.5) is not available anywhere Removed indication that 776330 affects php-kdyby-console and php-kdyby-events thanks Stopping processing here. Please contact me if you need assistance. -- 776330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776330 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#783420: [pkg-php-pear] Bug#783420: Useless in Debian
On 04/27/2015 12:02 AM, David Prévot wrote: Package: php-mime-type Version: 1.3.1-1 Severity: serious [Filled as RC by a team member to see it autoremoved from testing if nobody disagrees. Please, do downgrade it with an explanation if you disagree.] php-mime-type is only used by extplorer (removed from testing over a year ago), and is not maintained upstream anymore (the version in Debian even predates the latest upstream version). I intend to follow up with an RM request in a few months if nobody objects (but feel free to beat me to it). Regards David Hi, I do object. I may attempt to re-upload extplorer if I have time to work on it. Cheers, Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783451: libmodule-signature-perl: CVE-2015-3406 CVE-2015-3407 CVE-2015-3408 CVE-2015-3409
Source: libmodule-signature-perl Version: 0.73-1 Severity: grave Tags: security upstream fixed-upstream Hi, the following vulnerabilities were published for libmodule-signature-perl. CVE-2015-3406[0]: unsigned files interpreted as signed in some circumstances CVE-2015-3407[1]: arbitrary code execution during test phase CVE-2015-3408[2]: arbitrary code execution when verifying module signatures CVE-2015-3409[3]: arbitrary modules loading in some circumstances If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2015-3406 [1] https://security-tracker.debian.org/tracker/CVE-2015-3407 [2] https://security-tracker.debian.org/tracker/CVE-2015-3408 [3] https://security-tracker.debian.org/tracker/CVE-2015-3409 Please adjust the affected versions in the BTS as needed. p.s.: for the pkg-perl team: I planned to look into it for all needed versions, but if somebody beats me to it, just go ahead! Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783388: ganeti - No verification for master status
Control: severity -1 serious Control: user pkg-ganeti-de...@lists.alioth.debian.org Control: usertags -1 jessie-pu Hi and thanks for the report. On 18:41 Sun 26 Apr , Bastian Blank wrote: Package: ganeti Version: 2.12.0-3 Severity: grave ganeti 2.12.0 lacks any verification that it is in master mode. This leads to errors from all command line tools, the watcher and other parts. This problem is most likely fixed with b7b036723a65d20054425190e47d4dd82278e0e7 I know this is an annoying bug, but I doubt it warrants a grave severity, as it doesn't make Ganeti mostly unusable. I'm downgrading to serious since it's a regression from the behaviour of earlier versions. I'll queue this up for 8.1. Regards, Apollon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 2 errors): Re: Bug#783388: ganeti - No verification for master status
Processing control commands: severity -1 serious Bug #783388 [ganeti] ganeti - No verification for master status Severity set to 'serious' from 'grave' user pkg-ganeti-de...@lists.alioth.debian.org Unknown command or malformed arguments to command. usertags -1 jessie-pu Unknown command or malformed arguments to command. -- 783388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783388 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#783388: ganeti - No verification for master status
On Mon, Apr 27, 2015 at 09:40:13AM +0300, Apollon Oikonomopoulos wrote: I'll queue this up for 8.1. While you are at it: - Config reading slow-down, mostly cluster verify: 01b52c6fc43ca7bcf1e5745133aa82abcb96375b^..38692c5c3a6900ec1b813e971dbef0f8e132c0f9 - Master voting: 5e641d0a518636007c2b9d6d96a18d383b2958ab Bastian -- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725284: proper resume hooks
And in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780956 the dev showed that udev already has proper hooks for resume events. So these may be proper mechanisms for packages to ship with a resume hook. And the last one is already tried and proven by laptop-mode-tools. Looking through the report you linked, it seems the laptop-mode-tools hook is actually unreliable when using asynchronous suspens/resume power management, which is the default (?) on newer kernels. So that doesn't really sound like a proper mechanism. I agree though that udev is probably the right place to fix this. I should add that there already is a bug open against udev for this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779412 Also, the anacron issue is different IMHO - there, the reason we care about suspend/resume is really because the time jumps, so whatever has been written above about this should work fine. Not so for hdparm, where the problem is HW losing some of its state. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725284: proper resume hooks
Am Mon, 27 Apr 2015 14:21:01 +0200 schrieb Ralf Jung p...@ralfj.de: OnClockChange=yes This does not sound to me like it applies to hdparm. We are not caring about the clock here, we are caring about devices re-appearing after suspend-resume and hence needing reconfiguration. All system resumes should trigger a clock change, but the feature is not implemented anyway and would add a depends on systemd. And in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780956 the dev showed that udev already has proper hooks for resume events. So these may be proper mechanisms for packages to ship with a resume hook. And the last one is already tried and proven by laptop-mode-tools. Looking through the report you linked, it seems the laptop-mode-tools hook is actually unreliable when using asynchronous suspens/resume power management, which is the default (?) on newer kernels. So that doesn't really sound like a proper mechanism. I don't know how much hardware fails with async suspend/resume. I'd suggest reopening/moving bug #780956 to the kernel or udev package, for a workaround/fix or to disable the async default from a package? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783490: ReferenceError: exports is not defined (embed.dev.js line 1306)
Package: isso Version: 0.9.9-1 Severity: grave Justification: renders package unusable I am using isso via uWSGI and nginx but the comment form is not displayed on my site and the browser console shows: `ReferenceError: exports is not defined (embed.dev.js line 1306)` By contrast installing isso via pip in a virtualenv using the same configuration for nginx and uWSGI solves the issue. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (900, 'stable'), (500, 'stable-updates'), (400, 'testing') Architecture: armhf (armv7l) Kernel: Linux 3.16.0-4-armmp-lpae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages isso depends on: ii libjs-sphinxdoc 1.2.3+dfsg-1 ii python 2.7.9-1 ii python-configparser 3.3.0r2-2 ii python-html5lib 0.999-3 ii python-ipaddr2.1.11-2 ii python-itsdangerous 0.24+dfsg1-1 ii python-misaka1.0.2-3+b1 ii python-werkzeug 0.9.6+dfsg-1 pn python:any none Versions of packages isso recommends: pn gunicorn none isso 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
Processed: Re: [pkg-lynx-maint] Bug#745835: lynx-cur: certificate revocation is not checked
Processing control commands: tag -1 + moreinfo Bug #745835 [lynx-cur] lynx-cur: certificate revocation is not checked Added tag(s) moreinfo. -- 745835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745835 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#745835: [pkg-lynx-maint] Bug#745835: lynx-cur: certificate revocation is not checked
Control: tag -1 + moreinfo Hi, Vincent Lefevre wrote: This problem still occurs. For a new testcase URL: lynx https://www.vinc17.net:4434/ does not give an error, contrary to Firefox. JFTR: Works fine (i.e. without revocation warning) in Chromium (42.0.2311.90-2), too. But I don't see such a bug report at https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=chromium-browser Can you please elaborate over which methods you expect lynx to check the revocation or over which methods it can be checked, i.e. CRL or OCSP? Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777341: marked as done (qtbase-opensource-src: libopenvg1-mesa-dev is no longer built by mesa)
Your message dated Mon, 27 Apr 2015 11:22:11 + with message-id e1ymh75-0007co...@franck.debian.org and subject line Bug#777341: fixed in qtbase-opensource-src 5.3.2+dfsg-5 has caused the Debian Bug report #777341, regarding qtbase-opensource-src: libopenvg1-mesa-dev is no longer built by mesa 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.) -- 777341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: qtbase-opensource-src Version: 5.3.2+dfsg-4 Severity: serious Tags: sid Justification: fails to build from source (but built successfully in the past) From https://ftp-master.debian.org/cruft-report-daily.txt: * source package mesa version 10.4.2-2 no longer builds binary package(s): libegl1-mesa-drivers-dbg libopenvg1-mesa libopenvg1-mesa-dbg libopenvg1-mesa-dev on amd64,arm64,armel,armhf,i386,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,ppc64el,s390x,sparc - suggested command: dak rm -m [auto-cruft] NBS (no longer built by mesa) -s unstable -a amd64,arm64,armel,armhf,i386,kfreebsd-amd64,kfreebsd-i386,mips,mipsel,powerpc,ppc64el,s390x,sparc -p -R -b libegl1-mesa-drivers-dbg libopenvg1-mesa libopenvg1-mesa-dbg libopenvg1-mesa-dev - broken Build-Depends: qtbase-opensource-src: libopenvg1-mesa-dev qtbase-opensource-src will FTBFS in sid once that cruft was removed. Please stop B-D: libopenvg1-mesa-dev Andreas ---End Message--- ---BeginMessage--- Source: qtbase-opensource-src Source-Version: 5.3.2+dfsg-5 We believe that the bug you reported is fixed in the latest version of qtbase-opensource-src, 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 777...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev mity...@debian.org (supplier of updated qtbase-opensource-src package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 27 Apr 2015 11:54:20 +0300 Source: qtbase-opensource-src Binary: libqt5core5a libqt5gui5 libqt5network5 libqt5opengl5 libqt5sql5 libqt5sql5-mysql libqt5sql5-odbc libqt5sql5-psql libqt5sql5-sqlite libqt5sql5-tds libqt5xml5 libqt5dbus5 libqt5test5 libqt5concurrent5 libqt5widgets5 libqt5printsupport5 qtbase5-dev qtbase5-private-dev libqt5opengl5-dev qtbase5-dev-tools qt5-qmake qtbase5-examples qtbase5-dbg qtbase5-dev-tools-dbg qtbase5-examples-dbg qt5-default qtbase5-doc-html Architecture: source all Version: 5.3.2+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Changed-By: Dmitry Shachnev mity...@debian.org Description: libqt5concurrent5 - Qt 5 concurrent module libqt5core5a - Qt 5 core module libqt5dbus5 - Qt 5 D-Bus module libqt5gui5 - Qt 5 GUI module libqt5network5 - Qt 5 network module libqt5opengl5 - Qt 5 OpenGL module libqt5opengl5-dev - Qt 5 OpenGL library development files libqt5printsupport5 - Qt 5 print support module libqt5sql5 - Qt 5 SQL module libqt5sql5-mysql - Qt 5 MySQL database driver libqt5sql5-odbc - Qt 5 ODBC database driver libqt5sql5-psql - Qt 5 PostgreSQL database driver libqt5sql5-sqlite - Qt 5 SQLite 3 database driver libqt5sql5-tds - Qt 5 FreeTDS database driver libqt5test5 - Qt 5 test module libqt5widgets5 - Qt 5 widgets module libqt5xml5 - Qt 5 XML module qt5-default - Qt 5 development defaults package qt5-qmake - Qt 5 qmake Makefile generator tool qtbase5-dbg - Qt 5 base library debugging symbols qtbase5-dev - Qt 5 base development files qtbase5-dev-tools - Qt 5 base development programs qtbase5-dev-tools-dbg - Qt 5 base binaries debugging symbols qtbase5-doc-html - Qt 5 base HTML documentation qtbase5-examples - Qt 5 base examples qtbase5-examples-dbg - Qt 5 base examples debugging symbols qtbase5-private-dev - Qt 5 base private development files Closes: 777341 779580 Changes: qtbase-opensource-src (5.3.2+dfsg-5) unstable; urgency=medium . [ Lisandro Damián Nicanor Pérez Meyer ] * Remove libopenvg1-mesa-dev as a build dependency because mesa does not build it anymore (Closes: #777341). Thanks Andreas Beckmann for the report. . [ Dmitry
Bug#773768: pandoc upload
Hi Joachim, Quoting Joachim Breitner (2015-04-27 13:31:02) I’ve just uploaded 7.8.4 to unstable. Can you check if you still have problems with this release? So far, none else has complained. Yes: Pandoc has a minor new upstream release which I will try package when that new ghc emerge in unstable. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#725284: proper resume hooks
Am Mon, 27 Apr 2015 14:26:46 +0200 schrieb Ralf Jung p...@ralfj.de: I should add that there already is a bug open against udev for this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779412 That links to a systemd bug, not a udev bug about async supend/resume, as I had expected from your messages. Did I misunderstood you? Kind regards, Chris -- 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#773768: pandoc upload
Processing control commands: tag -1 + moreinfo unreproducible Bug #773768 [ghc] ghc: fails to install: cannot open shared object file: No such file or directory Added tag(s) unreproducible and moreinfo. -- 773768: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773768 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#773768: pandoc upload
Control: tag -1 + moreinfo unreproducible Hi Jonas, I’ve just uploaded 7.8.4 to unstable. Can you check if you still have problems with this release? So far, none else has complained. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Bug#725284: proper resume hooks
Hi, In the face of the race condition with systemd unit files, reported by Michael Biebl, there seem to exist different alternatives. Lennart Poettering: https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=nobug=744753#40 a service which needs to be restarted on cases like this sounds wrong. Thats a hack really. The service should just watch time changes and react correctly to that. i.e. use TFD_TIMER_CANCEL_ON_SET. THis will report wallclock changes relative to monotonic time, which is what you want to watch for this. All system resumes will trigger this, of course. and Since a long time we had on our TODO list to support timer units that are triggered when the system clock changes, based on TFD_TIMER_CANCEL_ON_SET. Hasn't been implemented yet, should be fairly easy though. OnClockChange=yes This does not sound to me like it applies to hdparm. We are not caring about the clock here, we are caring about devices re-appearing after suspend-resume and hence needing reconfiguration. And in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780956 the dev showed that udev already has proper hooks for resume events. So these may be proper mechanisms for packages to ship with a resume hook. And the last one is already tried and proven by laptop-mode-tools. Looking through the report you linked, it seems the laptop-mode-tools hook is actually unreliable when using asynchronous suspens/resume power management, which is the default (?) on newer kernels. So that doesn't really sound like a proper mechanism. I agree though that udev is probably the right place to fix this. Kind regards, Ralf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775733: closed by Mark Brown broo...@debian.org (Bug#775733: fixed in xemacs21 21.4.22-12)
On 2015-04-26 10:43, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the src:xemacs21,xemacs21-gnome-mule,xemacs21-gnome-nomule,xemacs21-gnome-mule-canna-wnn package: #775733: xemacs21-gnome-*: hangs during upgrade from squeeze - wheezy - jessie It has been closed by Mark Brown broo...@debian.org. Thanks for getting this fixed in sid, please fix this in jessie, too. If you need help there, please let me know. Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783503: mediawiki: not suitable for Stretch
Package: mediawiki Version: 1:1.19.20+dfsg-2.3 Severity: serious Tags: stretch sid Mediawiki as it currently stands is not suitable for a stable release. This blocker bug is to ensure it does not migrate to testing. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745835: [pkg-lynx-maint] Bug#745835: lynx-cur: certificate revocation is not checked
Hi, On 2015-04-27 14:49:15 +0200, Axel Beckert wrote: Vincent Lefevre wrote: This problem still occurs. For a new testcase URL: lynx https://www.vinc17.net:4434/ does not give an error, contrary to Firefox. JFTR: Works fine (i.e. without revocation warning) in Chromium (42.0.2311.90-2), too. But I don't see such a bug report at https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=chromium-browser Chromium is just crap and its maintainers do not care. See my bug report here (which is a part of the problem): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745646 The bug was closed without being fixed. Can you please elaborate over which methods you expect lynx to check the revocation or over which methods it can be checked, i.e. CRL or OCSP? CRL might be OK if Debian has a way to get a complete CRLset. But I haven't seen one. So, OCSP (possibly OCSP must-staple) should really be implemented. -- Vincent Lefèvre vinc...@vinc17.net - Web: https://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: https://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Move to udisks2, udisks 1 is deprecated
Processing control commands: severity -1 serious Bug #740841 [scolasync] Move to udisks2, udisks 1 is deprecated Severity set to 'serious' from 'important' -- 740841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740841 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: Move to udisks2, udisks 1 is deprecated
Processing control commands: severity -1 serious Bug #740845 [basenji] Move to udisks2, udisks 1 is deprecated Severity set to 'serious' from 'important' -- 740845: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740845 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: Move to udisks2, udisks 1 is deprecated
Processing control commands: severity -1 serious Bug #740842 [libpam-usb] Move to udisks2, udisks 1 is deprecated Severity set to 'serious' from 'important' -- 740842: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740842 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#783553: numdiff: debian/copyright file is not complete
Package: numdiff Version: 5.8.1-1 Severity: serious Justification: Policy 4.5 Hello and thanks for maintaining this interesting package in Debian! After taking a look at bug #709492, I noticed that the debian/copyright file for numdiff/5.8.1-1 [1] seems to be incomplete, as it does not mention the GFDL-licensed files. There are at least some files under the GFDL [2]. [1] https://tracker.debian.org/media/packages/n/numdiff/copyright-5.8.1-1 [2] for instance: https://sources.debian.net/src/numdiff/5.8.1-1/docs/numdiff.txi/ Please update the debian/copyright file to correctly document the licensing status of the package. Or, even better, could the upstream developer(s) be persuaded to re-license the documentation under the same terms as the rest of the package (GPL)? This would be an optimal solution, since, for example, it would allow any contributor to use material copied from the program source code, when improving the documentation. Moreover, it would simplify the debian/copyright file! ;-) Bye and thanks for your time. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742689: check-mk: more CVE info
Disappointing to see Jessie was released with the check-mk package missing. This is the third package I've found to be missing since Jessie was released - I get the feeling the release was perhaps rushed? Anyway, grievances aside - is there any progress with getting this packaged for backports? -- Sam McLeod
Bug#783537: important tools missing
Control: severity -1 normal Am 27.04.2015 um 22:40 schrieb Axel Beckert: Michael Biebl wrote: $ gbp import-orig --uscan bash: git-buildpackage: Kommando nicht gefunden. Works fine here: → gbp import-orig --uscan gbp:info: Launching uscan... gbp:error: Uscan failed: uscan warning: In debian/watch, [...] (That error is expected and package-specific.) Something looks completely borked here. I've restarted all my shell, even tried that with a fresh login on tty1. Sounds like a valid way to get an uptodate shell. So no idea here. gbp's zsh completion as well as the above commmand work fine for me. Turns out, this was a classical case of PEBKAC. /o\ I had this sourced in my .bashrc: alias gbp=git-buildpackage I think this was from the early days of git-buildpackage, when there was no gbp command. Dropping that line, and oh magic, gbp import-orig and sorts works as expected. Sorry again for the noise. Might still be worth to add the NEWS entry about the actual removal of the tools and adjusting the man pages, though. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#783537: important tools missing
Processing control commands: severity -1 normal Bug #783537 [git-buildpackage] important tools missing Severity set to 'normal' from 'grave' -- 783537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783537 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: libogre-perl: Please upgrade OGRE dependency to 1.9 when upstream ready
Processing control commands: severity -1 serious Bug #732725 [src:libogre-perl] libogre-perl: Please upgrade OGRE dependency to 1.9 when upstream ready Severity set to 'serious' from 'important' -- 732725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732725 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: cegui-mk2: Please upgrade OGRE dependency to 1.9 when upstream ready
Processing control commands: severity -1 serious Bug #732723 [src:cegui-mk2] cegui-mk2: Please upgrade OGRE dependency to 1.9 when upstream ready Severity set to 'serious' from 'important' -- 732723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732723 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#756573: Useless in Jessie
Processing control commands: retitle -1 Useless in Debian Bug #756573 [php-mssql-bundle] Useless in Jessie Changed Bug title to 'Useless in Debian' from 'Useless in Jessie' -- 756573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756573 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#756573: Useless in Jessie
Control: retitle -1 Useless in Debian On Wed, Jul 30, 2014 at 10:19:33PM -0400, David Prévot wrote: Package: php-mssql-bundle [Filled as an RC-bug by the maintainer to exclude packages from testing] php-mssql-bundle has recently been introduced as an owncloud dependency, but proper MsSQL support has been postponed to owncloud 8 Actually, it’s becoming less realistic to see proper support of MsSQL in the community version of ownCloud. Furthermore, MsSQL support may not be a feature worth providing in Debian anyway. I intend to follow up with an RM request before Stretch gets released if the situation doesn’t evolve and nobody objects. In the mean time, I’m keeping this RC bug open to prevent migration to testing. Regards David signature.asc Description: Digital signature
Processed: Re: Will Ogre 1.8 remain in Jessie? (Was: The other packages)
Processing control commands: severity -1 serious Bug #760058 [src:ember] ember: Please upgrade OGRE dependency to 1.9 Severity set to 'serious' from 'important' -- 760058: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760058 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#783552: Useless (superseded by native features)
Package: xul-ext-fullscreen Version: 1.0.4-1 Severity: serious [Filled as RC by a team member to see it autoremoved from testing if nobody disagrees. Please, do downgrade it with an explanation if you disagree.] As far as I can tell, the native fullscreen feature (F11) of current iceweasel versions provides the actual fullscreen this extension used to provide (I was an happy user of it with my 9” screen eeepc a few years ago). There hasn’t been any upstream release since almost four years, and the popcon is very low. I intend to follow up with an RM request in a few months if nobody objects (but feel free to beat me to it). Regards David signature.asc Description: Digital signature
Bug#756580: Useless in Jessie
Control: retitle -1 Useless in Debian On Thu, Jul 31, 2014 at 12:23:06AM -0400, David Prévot wrote: Package: php-irods-prods [Filled as an RC-bug by the maintainer to exclude package from testing] php-irods-prods […] is a beta version (last activity upstream was about one year ago), so there is little point to release it On Fri, Jul 25, 2014 at 05:59:23PM +0200, Roman Valls Guimera wrote: I just noticed the following RFA: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748608 And your comment: I recently packaged it because it was used by owncloud, but that won’t be true anymore with the upcoming version 7 currently available in experimental. It might not be in core, but it’s still shipped as an app: https://github.com/owncloud/files_irods If someone intends to package owncloud-files-irods in Debian, of course it would be useful to keep php-irods-prods in the archive. In the mean time, I still advocate keeping this RC bug open to prevent migration to testing. Since there has only been a very low activity on files_irods upstream (only 4 commits, the last one being almost a year ago), I’m not sure it’s currently realistic to see it packaged in the near future. If the status doesn’t change until Stretch gets released, I would probably advocate a removal from the archive, but we can delay such decision until then. Regards David signature.asc Description: Digital signature
Processed: Re: Bug#756580: Useless in Jessie
Processing control commands: retitle -1 Useless in Debian Bug #756580 [php-irods-prods] Useless in Jessie Changed Bug title to 'Useless in Debian' from 'Useless in Jessie' -- 756580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756580 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: Move to udisks2, udisks 1 is deprecated
Processing control commands: severity -1 serious Bug #750511 [udisks-glue] Move to udisks2, udisks 1 is deprecated Severity set to 'serious' from 'important' -- 750511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750511 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
Processing commands for cont...@bugs.debian.org:
close 779888 4.0.2-1.1
Bug #779888 [live-tools] wheezy: live-tools should depend on initramfs-tools
Bug #781725 [live-tools] wheezy: live-tools should depend on initramfs-tools
Marked as fixed in versions live-tools/4.0.2-1.1.
Marked as fixed in versions live-tools/4.0.2-1.1.
Bug #779888 [live-tools] wheezy: live-tools should depend on initramfs-tools
Bug #781725 [live-tools] wheezy: live-tools should depend on initramfs-tools
Marked Bug as done
Marked Bug as done
close 781725 4.0.2-1.1
Bug #781725 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[live-tools] wheezy: live-tools should depend on initramfs-tools
Bug #779888 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[live-tools] wheezy: live-tools should depend on initramfs-tools
Ignoring request to alter fixed versions of bug #781725 to the same values
previously set
Ignoring request to alter fixed versions of bug #779888 to the same values
previously set
Bug #781725 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[live-tools] wheezy: live-tools should depend on initramfs-tools
Bug #779888 {Done: Daniel Baumann daniel.baum...@progress-technologies.net}
[live-tools] wheezy: live-tools should depend on initramfs-tools
Bug 781725 is already marked as done; not doing anything.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
779888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779888
781725: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781725
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#783579: epiphany-browser: leaks DNS queries when used with Tor
Package: epiphany-browser Version: 3.14.1-1 Severity: grave Tags: security Hi. Apparently it seems that even when configured to use Tor as proxy, epiphany is so smart to send DNS queries directly to the wire, thus making any effort of Tor useless. Just check with wireshark and one can see it. Marking this as grave so that people get notified about this inadequacy... actually people in many contries who need to rely on Tor, can get into severe troubles when their anonymity is compromised. Chris. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DE.utf8, LC_CTYPE=en_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages epiphany-browser depends on: ii dbus-x11 1.8.16-1 ii epiphany-browser-data3.14.1-1 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic3.12.0-1 ii gsettings-desktop-schemas3.14.1-1 ii iso-codes3.57-1 ii libatk1.0-0 2.14.0-1 ii libavahi-client3 0.6.31-5 ii libavahi-common3 0.6.31-5 ii libavahi-gobject00.6.31-5 ii libc62.19-18 ii libcairo-gobject21.14.0-2.1 ii libcairo21.14.0-2.1 ii libgcr-base-3-1 3.14.0-2 ii libgcr-ui-3-13.14.0-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgnome-desktop-3-103.14.1-1 ii libgtk-3-0 3.14.5-1 ii libjavascriptcoregtk-4.0-18 2.6.2+dfsg1-4 ii libnotify4 0.7.6-2 ii libnspr4 2:4.10.8-1 ii libnspr4-0d 2:4.10.8-1 ii libnss3 2:3.17.2-1.1 ii libnss3-1d 2:3.17.2-1.1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libsecret-1-00.18-1+b1 ii libsoup2.4-1 2.48.0-1 ii libsqlite3-0 3.8.7.4-1 ii libwebkit2gtk-4.0-37 2.6.2+dfsg1-4 ii libwnck-3-0 3.4.9-3 ii libx11-6 2:1.6.2-3 ii libxml2 2.9.2+dfsg1-3 ii libxslt1.1 1.1.28-2+b2 Versions of packages epiphany-browser recommends: ii ca-certificates 20141019 ii evince 3.14.1-2 ii yelp 3.14.1-1 epiphany-browser 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#783576: banshee: crashes on startup - System.ArgumentNullException: Argument cannot be null
Package: banshee
Version: 2.6.2-3
Severity: grave
Justification: renders package unusable
When I try to starup banshee, it just crashes. I looked at the other banshee
crashes on startup type bugs and I am pretty sure, but not 100% sure this is
yet another way of it crashing.
$ banshee --debug
** Running Mono with --debug **
[1 Debug 13:04:06.831] Bus.Session.RequestName ('org.bansheeproject.Banshee')
replied with PrimaryOwner
[1 Info 13:04:06.844] Running Banshee 2.6.2: [Debian GNU/Linux 8.0 (jessie)
(linux-gnu, x86_64) @ 2015-01-23 13:22:58 SGT]
[1 Debug 13:04:06.850] Initializing GTK
[1 Debug 13:04:07.479] Post-Initializing GTK
[1 Debug 13:04:07.486] Configuration client extension loaded
(Banshee.GnomeBackend.GConfConfigurationClient)
[1 Debug 13:04:07.487] Using default gconf-base-key
[1 Debug 13:04:07.546] Core service started (DBusServiceManager, 0.000839)
[1 Debug 13:04:07.548] Registering remote object
/org/bansheeproject/Banshee/DBusCommandService
(Banshee.ServiceStack.DBusCommandService) on org.bansheeproject.Banshee
[1 Debug 13:04:07.554] Core service started (DBusCommandService, 0.007773)
[1 Debug 13:04:07.579] Opened SQLite (version 3.8.7.4) connection to
/home/csmall/.config/banshee-1/banshee.db
[1 Debug 13:04:07.579] Core service started (DbConnection, 0.024851)
[1 Debug 13:04:07.583] Database version 45 is up to date
[1 Debug 13:04:07.608] Core service started (PreferenceService, 0.014946)
[1 Debug 13:04:07.612] Core service started (Network, 0.004347)
[1 Debug 13:04:07.613] Registering remote object
/org/bansheeproject/Banshee/SourceManager (Banshee.Sources.SourceManager) on
org.bansheeproject.Banshee
[1 Debug 13:04:07.613] Core service started (SourceManager, 0.000475)
[1 Debug 13:04:07.616] Core service started (MediaProfileManager, 0.00014)
[1 Debug 13:04:07.618] Registering remote object
/org/bansheeproject/Banshee/PlayerEngine
(Banshee.MediaEngine.PlayerEngineService) on org.bansheeproject.Banshee
[1 Debug 13:04:07.619] Core service started (PlayerEngine, 0.003057)
[1 Debug 13:04:07.628] Registering remote object
/org/bansheeproject/Banshee/PlaybackController
(Banshee.PlaybackController.PlaybackControllerService) on
org.bansheeproject.Banshee
[1 Debug 13:04:07.628] Core service started (PlaybackController, 0.001624)
[1 Debug 13:04:07.631] Starting - Startup Job
[1 Debug 13:04:07.632] Core service started (JobScheduler, 0.003606)
[1 Debug 13:04:07.639] IO provider extension loaded (Banshee.IO.Gio.Provider)
[1 Debug 13:04:07.688] Loaded HardwareManager backend: Banshee.Hardware.Gio
[1 Debug 13:04:07.689] Core service started (HardwareManager, 0.057105)
[1 Debug 13:04:07.690] Bus.Session.RequestName
('org.bansheeproject.CollectionIndexer') replied with PrimaryOwner
[1 Debug 13:04:07.691] Registering remote object
/org/bansheeproject/Banshee/CollectionIndexerService
(Banshee.Collection.Indexer.CollectionIndexerService) on
org.bansheeproject.CollectionIndexer
[1 Debug 13:04:07.692] Core service started (CollectionIndexerService,
0.002941)
[1 Debug 13:04:07.693] Core service started (SaveTrackMetadataService,
0.000752)
[1 Debug 13:04:07.696] Adding icon theme search path: /usr/share/banshee/icons
[1 Debug 13:04:07.697] Core service started (GtkElementsService, 0.003858)
[1 Debug 13:04:07.697] Core service started (InterfaceActionService, 0.00063)
[1 Debug 13:04:07.757] Extension actions loaded: MetadataFixActions
[1 Debug 13:04:07.757] Registering remote object
/org/bansheeproject/Banshee/GlobalUIActions (Banshee.Gui.GlobalActions) on
org.bansheeproject.Banshee
[1 Debug 13:04:07.758] Album artwork path set to /home/csmall/.cache/media-art
[1 Debug 13:04:07.767] Core service started (ArtworkManager, 0.010298)
[1 Debug 13:04:07.768] Core service started (BookmarksService, 9.9E-05)
[1 Debug 13:04:07.858] Adding context page lastfm-recommendations
[1 Debug 13:04:07.871] Adding context page wikipedia
(Banshee:1553): GLib-GObject-WARNING **: attempting to add an interface
(AtkComponent) to class (__gtksharp_49_Hyena_Gui_BaseWidgetAccessible) after
class_init
(Banshee:1553): GLib-GObject-WARNING **: attempting to add an interface
(AtkTable) to class
(__gtksharp_50_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_TrackInfo+2c+20Banshee_Core+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d)
after class_init
(Banshee:1553): GLib-GObject-WARNING **: attempting to add an interface
(AtkSelection) to class
(__gtksharp_50_Hyena_Data_Gui_Accessibility_ListViewAccessible+601+5b+5bBanshee_Collection_TrackInfo+2c+20Banshee_Core+2c+20Version+3d2_6_0_0+2c+20Culture+3dneutral+2c+20PublicKeyToken+3dnull+5d+5d)
after class_init
[1 Warn 13:04:07.920] Initialization of accessibility support for ListView
widgets failed - System.ArgumentException: Invalid signal name: model_changed
(in `glib-sharp')
at GLib.Signal.Emit (GLib.Object instance, System.String detailed_signal,
System.Object[] args) [0x0] in filename unknown:0
at
Bug#745835: lynx-cur: certificate revocation is not checked
Control: tag -1 - moreinfo + upstream Control: severity -1 important Hi Vincent, Vincent Lefevre wrote: On 2015-04-27 14:49:15 +0200, Axel Beckert wrote: Vincent Lefevre wrote: This problem still occurs. For a new testcase URL: lynx https://www.vinc17.net:4434/ does not give an error, contrary to Firefox. JFTR: Works fine (i.e. without revocation warning) in Chromium (42.0.2311.90-2), too. But I don't see such a bug report at https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=chromium-browser Chromium is just crap and its maintainers do not care. See my bug report here (which is a part of the problem): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745646 The bug was closed without being fixed. Depends likely on the point of view. Can you please elaborate over which methods you expect lynx to check the revocation or over which methods it can be checked, i.e. CRL or OCSP? CRL might be OK if Debian has a way to get a complete CRLset. But I haven't seen one. So, OCSP (possibly OCSP must-staple) should really be implemented. So this is basically an upstream feature request. I don't think a feature request which you yourself phrase with should validates RC-severity, even if it's a security related feature. Hence downgrading the severity to important. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- 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#745835: lynx-cur: certificate revocation is not checked
Processing control commands: tag -1 - moreinfo + upstream Bug #745835 [lynx-cur] lynx-cur: certificate revocation is not checked Removed tag(s) moreinfo. Bug #745835 [lynx-cur] lynx-cur: certificate revocation is not checked Added tag(s) upstream. severity -1 important Bug #745835 [lynx-cur] lynx-cur: certificate revocation is not checked Severity set to 'important' from 'serious' -- 745835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745835 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: unarchiving 771163, closing 771163, archiving 771163
Processing commands for cont...@bugs.debian.org:
unarchive 771163
Bug #771163 {Done: Rene Engelhard r...@debian.org} [libreoffice] libreoffice:
CVE-2014-9093
Unarchived Bug 771163
close 771163 1:3.5.4+dfsg2-0+deb7u3
Bug #771163 {Done: Rene Engelhard r...@debian.org} [libreoffice] libreoffice:
CVE-2014-9093
Marked as fixed in versions libreoffice/1:3.5.4+dfsg2-0+deb7u3.
Bug #771163 {Done: Rene Engelhard r...@debian.org} [libreoffice] libreoffice:
CVE-2014-9093
Bug 771163 is already marked as done; not doing anything.
archive 771163
Bug #771163 {Done: Rene Engelhard r...@debian.org} [libreoffice] libreoffice:
CVE-2014-9093
archived 771163 to archive/63 (from 771163)
thanks
Stopping processing here.
Please contact me if you need assistance.
--
771163: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771163
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 libpdl-stats-perl
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package libpdl-stats-perl # 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 #752026 (http://bugs.debian.org/752026) # Bug title: libpdl-stats-perl: FTBFS on arm* # * http://rt.cpan.org/Public/Bug/Display.html?id=98873 # * remote status changed: open - resolved # * closed upstream tags 752026 + fixed-upstream Bug #752026 [libpdl-stats-perl] libpdl-stats-perl: FTBFS on arm* Added tag(s) fixed-upstream. usertags 752026 - status-open Usertags were: status-open. Usertags are now: . usertags 752026 + status-resolved There were no usertags set. Usertags are now: status-resolved. thanks Stopping processing here. Please contact me if you need assistance. -- 752026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752026 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#783511: openstreetmap-client crashes on startup
Ciao Francesco, Thanks for your report. On Mon, Apr 27, 2015 at 5:18 PM, Francesco Ariis fa...@ariis.it wrote: Traceback (most recent call last): File /usr/bin/openstreetmap-client, line 46, in module import maps File /usr/share/openstreetmap-client/maps/__init__.py, line 24, in module from maps.map_application import MapApplication File /usr/share/openstreetmap-client/maps/map_application.py, line 17, in module from gi.repository import Gtk, Gio, GtkClutter, Clutter ImportError: No module named gi.repository Seems caused by a missing package in the Depends field. A quick fix should be installing python-gi. Cheers! -- Alessio Treglia | www.alessiotreglia.com Debian Developer | ales...@debian.org Ubuntu Core Developer| quadris...@ubuntu.com 0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783511: openstreetmap-client crashes on startup
Package: openstreetmap-client Version: 14.03.1~ds0-1 Severity: grave Justification: renders package unusable Dear Maintainer, I installed openstreetmap-client, this is what happens when I invoke it: Traceback (most recent call last): File /usr/bin/openstreetmap-client, line 46, in module import maps File /usr/share/openstreetmap-client/maps/__init__.py, line 24, in module from maps.map_application import MapApplication File /usr/share/openstreetmap-client/maps/map_application.py, line 17, in module from gi.repository import Gtk, Gio, GtkClutter, Clutter ImportError: No module named gi.repository -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openstreetmap-client depends on: ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gir1.2-champlain-0.120.12.9-1 ii gir1.2-clutter-1.0 1.20.0-1 ii gir1.2-gdkpixbuf-2.0 2.31.1-2+b1 ii gir1.2-glib-2.0 1.42.0-2.2 ii gir1.2-gtk-3.0 3.14.5-1 ii gir1.2-gtkchamplain-0.12 0.12.9-1 ii gir1.2-gtkclutter-1.01.6.0-1 ii python-lxml 3.4.0-1 pn python:any none openstreetmap-client recommends no packages. openstreetmap-client 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#782996: marked as done (smsd: 'reload' function of initscript broken if used by systemd)
Your message dated Mon, 27 Apr 2015 22:23:40 +
with message-id e1ymrre-0005mt...@franck.debian.org
and subject line Bug#782996: fixed in smstools 3.1.15-1.2
has caused the Debian Bug report #782996,
regarding smsd: 'reload' function of initscript broken if used by systemd
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.)
--
782996: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: smstools
Version: 3.1.15-1.1
Severity: serious
Hello,
the smstools initscript has a wrong implementation of the 'reload'
function which breaks if used through systemd tools. In fact, the 'reload'
function in smstools initscript doesn't reload the configuration of the
service without actually stopping and restarting the service. Instead, it
stops the service if it runs and restarts it afterwards. This is, what
'force-reload' is for.
As a result, 'invoke-rc.d smstools reload', 'service smstools reload' and
'systemctl reload smstools.service' all result in the smsd daemon being
killed and not restarted afterwards.
The smstools logrotate script runs 'invoke-rc.d smstools reload' as post-
rotate action, which leads to the smsd daemon process being killed
The bug can be fixed by renaming the 'reload' function to 'force-reload'
and dropping the original 'force-reload' alias for 'restart'. Please note,
that fixing the 'Usage:' line by dropping 'reload' from the list of
supported actions is important as well. Otherwise, systemd tools try to
invoke 'reload' even if 'force-reload' is given as argument.
See the attached patch for a proper fix.
I consider this bug as release-critical for Jessie, as it renders
smmstools unusable on Jessie installations whenever logrotate is
installed. Thus I suggest to push the fix into Jessie within the next
days. I'll gladly do an NMU if the maintainer(s) don't have the time
to push this fix into Jessie in time.
Cheers,
jonas
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/20 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 smstools depends on:
ii adduser 3.113+nmu3
ii debconf 1.5.56
ii libc62.19-18
ii libmm14 1.4.2-5
ii ucf 3.0030
smstools recommends no packages.
smstools suggests no packages.
-- debconf information:
smstools/devicepin: (password omitted)
smstools/modems/devicepin1: (password omitted)
smstools/configureanothermodem: false
smstools/eventhandler:
smstools/modems/devicenode1: /dev/ttyS0
smstools/configure: true
smstools/modems/deviceinit1:
smstools/modems/devicename1: GSM1
smstools/devicebaudrate: 19200
smstools/deviceinit:
smstools/devicenode:
smstools/configureanothermodem1: false
smstools/devicename: GSM1
smstools/modems/deviceincoming1: true
smstools/devicenodeother:
smstools/devicebaudrateother:
smstools/modems/devicebaudrate1: 19200
smstools/deviceincoming: true
diff -rNu smstools-3.1.15.orig/debian/changelog smstools-3.1.15/debian/changelog
--- smstools-3.1.15.orig/debian/changelog 2015-04-20 11:46:00.0 +0200
+++ smstools-3.1.15/debian/changelog 2015-04-20 11:52:23.746207040 +0200
@@ -1,3 +1,14 @@
+smstools (3.1.15-1.2) unstable; urgency=high
+
+ * NMU by Jonas Meurer to push the fix into Jessie.
+ * Fix initscript: rename action 'reload' to 'force-reload' and drop 'reload'
+from supported actions. Use 'force-reload' in logrotate post-rotate action.
+This fixes 'force-reload' function when used through systemd tools and
+prevents the smsd daemon process from being killed at every log rotation.
+(closes: #XX)
+
+ -- Jonas Meurer jo...@freesources.org Mon, 20 Apr 2015 11:46:53 +0200
+
smstools (3.1.15-1.1) unstable; urgency=low
* NMU - preventing smstools from entering jessie.
diff -rNu smstools-3.1.15.orig/debian/init.d smstools-3.1.15/debian/init.d
--- smstools-3.1.15.orig/debian/init.d 2015-04-20 11:46:00.0 +0200
+++ smstools-3.1.15/debian/init.d 2015-04-20 11:46:38.266199428 +0200
@@ -218,7 +218,7 @@
echo $NAME.
;;
- reload)
+ force-reload)
echo -n Reloading $DESC:
status
if [ $? = 0 ]; then
@@ -230,14 +230,14 @@
;;
- restart|force-reload)
+ restart)
echo -n Restarting $DESC:
stop restart
start
;;
*)
- echo Usage: /etc/init.d/$NAME {start|stop|force-stop|reload|force-reload|restart|status}
Bug#783523: FTBFS due to missing build-depends
Package: amoeba Version: 1.1-27 Severity: serious Justification: fails to build from source (but built successfully in the past) Filing for my own tracking, and so that whoever porter gets to see it first doesn't have to. In file included from main/linux-config/linux-config.cpp:34:0: ./audio/linux_alsa.h:9:28: fatal error: alsa/asoundlib.h: No such file or directory #include alsa/asoundlib.h Probably just a missing build-dependency on libasound-dev. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (750, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.4 (SMP w/40 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783511: openstreetmap-client crashes on startup
On Mon, Apr 27, 2015 at 06:08:15PM +0100, Alessio Treglia wrote: Seems caused by a missing package in the Depends field. A quick fix should be installing python-gi. That did the trick! Everything works flawlessly now, thanks Alessio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718148: marked as done (arpon: FTBFS: Could not find libnet-1.1)
Your message dated Mon, 27 Apr 2015 19:02:14 +0100 with message-id 553e79a6.2090...@p10link.net and subject line Re: arpon: FTBFS: Could not find libnet-1.1 has caused the Debian Bug report #718148, regarding arpon: FTBFS: Could not find libnet-1.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 718148: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718148 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: arpon Version: 2.0-2.1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130726 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): debian/rules build mkdir -p debian/build cd /«PKGBUILDDIR»/debian/build \ cmake -DCMAKE_INSTALL_PREFIX=/usr -DRESOURCEDIR=/usr/share/arpon -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS_RELEASE=-O2 -g -DNDEBUG -Wall -Werror -DCMAKE_C_FLAGS_DEBUG=-O2 -g -Wall -Werror ../.. -- The C compiler identification is GNU 4.8.1 -- The CXX compiler identification is GNU 4.8.1 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Operating System: GNU/Linux -- Linux Distro: Debian CMake Warning (dev) at CMakeLists.txt:46 (find_package): A logical block opening on the line /«PKGBUILDDIR»/cmake_modules/FindPthread.cmake:19 (if) closes on the line /«PKGBUILDDIR»/cmake_modules/FindPthread.cmake:34 (endif) with mis-matching arguments. This warning is for project developers. Use -Wno-dev to suppress it. -- Found Libphtread. CMake Warning (dev) at CMakeLists.txt:46 (find_package): A logical block opening on the line /«PKGBUILDDIR»/cmake_modules/FindPthread.cmake:27 (if) closes on the line /«PKGBUILDDIR»/cmake_modules/FindPthread.cmake:30 (endif) with mis-matching arguments. This warning is for project developers. Use -Wno-dev to suppress it. -- Found Libdnet. CMake Error at cmake_modules/FindNET.cmake:33 (message): Could not find libnet-1.1! Please Visit: http://libnet.sourceforge.net/ or see in the arpon 'INSTALL' file Call Stack (most recent call first): CMakeLists.txt:48 (find_package) -- Configuring incomplete, errors occurred! make: *** [debian/build/CMakeCache.txt] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2013/07/26/arpon_2.0-2.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Version: 2.7.2-1 This appears to have been fixed with the upload of 2.7.2-1---End Message---
Bug#710321: marked as done (task: didn't handle conffile rename correctly)
Your message dated Tue, 28 Apr 2015 05:50:40 + with message-id e1ymypo-0004km...@franck.debian.org and subject line Bug#710321: fixed in task 2.4.3+dfsg-1 has caused the Debian Bug report #710321, regarding task: didn't handle conffile rename correctly 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.) -- 710321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: task Version: 2.1.2-1 Severity: serious Justification: Policy 10.7.3 task_2.0.0-1 ships this conffile: /etc/bash_completion.d/task task_2.1.2-1 ships it as: /etc/bash_completion.d/task.sh Unfortunately, I forgot to add maintainer scripts to deal with this rename. As a consequence, users who upgraded the package have now both of the files on disk. :( My current plan how to fix this: 1) Revert to the original filename: /etc/bash_completion.d/task 2) rm_conffile /etc/bash_completion.d/task.sh It's not ideal, but I don't think any extra complexity is worth the effort, given that the broken package has been in unstable for less than 3 weeks. If anybody has a better idea, please speak up! -- Jakub Wilk ---End Message--- ---BeginMessage--- Source: task Source-Version: 2.4.3+dfsg-1 We believe that the bug you reported is fixed in the latest version of task, 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 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Badia s...@sebian.fr (supplier of updated task 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, 21 Apr 2015 17:59:33 +0200 Source: task Binary: taskwarrior task Architecture: source amd64 Version: 2.4.3+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Sebastien Badia s...@sebian.fr Changed-By: Sebastien Badia s...@sebian.fr Description: task - feature-rich console based todo list manager - transitional packa taskwarrior - feature-rich console based todo list manager Closes: 710321 Changes: task (2.4.3+dfsg-1) experimental; urgency=medium . [ Gordon Ball ] * New upstream release: 2.4.3 * d/patches: Refresh for new release. . [ Sebastien Badia ] * Fix version number in the maint script; Thanks Jakub! (Closes: #710321) Checksums-Sha1: 36d8250e36177f0685c666cedadc982861b75b38 2018 task_2.4.3+dfsg-1.dsc 61f217ded533cb9e9633071a73860edad5ab0e67 842992 task_2.4.3+dfsg.orig.tar.xz 9d87fcacab71c0c008afdc9f2cbec479ac53dd64 16356 task_2.4.3+dfsg-1.debian.tar.xz Checksums-Sha256: 40fd0a56361ecc3b68abd064a2660ed93a124edfba9756c8efa1f670c0903793 2018 task_2.4.3+dfsg-1.dsc 578d60a7dff8d21dea10da6ef5e45049191b023ff9ae9a04421539a842231e55 842992 task_2.4.3+dfsg.orig.tar.xz 3651fe49542a972d278ee2c08a005a4fe0ea6d69adf41207c34adca4dbf95191 16356 task_2.4.3+dfsg-1.debian.tar.xz Files: 79e12ac658777c68fcc6e9d6fb7d6c68 2018 utils optional task_2.4.3+dfsg-1.dsc 830054caf5f4be268432db36c301766e 842992 utils optional task_2.4.3+dfsg.orig.tar.xz d45aa7f3f567382f98384577466d2643 16356 utils optional task_2.4.3+dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJVPx2QAAoJEJFk+h0XvV02Sw4P/2OKLc3LQNk4Vq0VUls1L83X fNqa6fLkuz9EJwDXlml74+ZboA2Wa2mA3fP724KW/UgfHTzojbZc7ueBuEoKZ6vX MpeDDfDIMNO075aqSrG4tS301M19y8+sn4M7INnnwxGWiM0/wzGOVwyn62sWYpU5 TLAdwdyLtdYH7yFbySGvfGOzKnDCHM0tHTseeGPPDtc2NEtetLOoClHjeshAFycy WNI5c3ECtaRYaaSPFPuHl9TuGFAmnQ95pc18BmtFyHkIV4UEUgyIiHqvYeR53qVP ISTqBXUxWuqQiJ8Vcq1O3aY760PSCNE+TGBAOMkOApHD3LzAef2C+EUvZhmQSj2A it1AcBFueyMS1lPX4/VSc/SagB8GnHSyzXFw7/jlGgIRrnIcpoDB3r2uMC1auE/5 LVy5HF+kReKxFJVMK9yeGidJ0sPBkPd0wx1DNrrvFQKUMIBJJQ+fN1USvFn50A4N u/cctEHVo1s8RCNY1Vfb2kaqcWvAmxQ9L+mpeKIHhW/HtAE2NRyL+x9OM2J2z+ul 2i9hVmcNtEwYLewytiRhN+NFl3Hi/0SiwVmcbO4dDFH3ZRngMHteLULUwwQ+Vc30 jkhYh7tDB3/Fz6EzilBlWgW5L+xFNJsO5ZdVTnq8qQhfjK0rZxHoT2YHaFjfXE9R iMhK8uUzV0aVa2xKvWHk =x7V1 -END PGP SIGNATUREEnd Message---
Processed: corosync build-depends
Processing commands for cont...@bugs.debian.org: tags 705023 + pending Bug #705023 [corosync] corosync-2.3.0 source package missing build-dep on libdbus-1-dev Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 705023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705023 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#783389: hbro segfaults
Hello,
tried to reproduce the issue:
Without debug symbols installed this stack is visible:
(gdb) bt
#0 0x083b6518 in ?? ()
#1 0x083ae0ed in ?? ()
#2 0xb4dda944 in __gmpz_init () from /usr/lib/i386-linux-gnu/libgmp.so.10
#3 0xac38b11c in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#4 0xac2e7783 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#5 0xac2e7c65 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#6 0xac315be4 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#7 0xac32095b in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#8 0xac313590 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#9 0xac339697 in gnutls_x509_crt_get_pk_algorithm () from
/usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#10 0xac2fa693 in gnutls_pubkey_import_x509 () from
/usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#11 0xac2f9a29 in gnutls_pcert_import_x509 () from
/usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#12 0xac2f9b60 in gnutls_pcert_import_x509_raw () from
/usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#13 0xac356a18 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#14 0xac2ddb79 in ?? () from /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#15 0xac2da579 in gnutls_handshake () from
/usr/lib/i386-linux-gnu/libgnutls-deb0.so.28
#16 0xac442591 in ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgiognutls.so
#17 0xac442a26 in ?? () from /usr/lib/i386-linux-gnu/gio/modules/libgiognutls.so
#18 0xb509eb2f in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#19 0xb4f0ce64 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#20 0xb4f0c3da in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#21 0xb4e54efb in start_thread (arg=0xad458b40) at pthread_create.c:309
#22 0xb4cb062e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129
After installing libgnutls28-dbg glib-networking-dbg libglib2.0-0-dbg,
locally building libgmp.so.10 and hbro the stack looks like this:
export
LD_LIBRARY_PATH=/home/benutzer/libgmp10/gmp-6.0.0+dfsg/build/tests/cxx/.libs
gdb --args /home/benutzer/hbro/hbro-1.1.2.2/dist-ghc/build/hbro/hbro
...
(gdb) b __gmp_set_memory_functions
Breakpoint 1, __gmp_set_memory_functions (alloc_func=0x83ae180
stgAllocForGMP, realloc_func=0x83ae1c0 stgReallocForGMP,
free_func=0x83ae170 stgDeallocForGMP) at ../mp_set_fns.c:39
39 {
(gdb) bt
#0 __gmp_set_memory_functions (alloc_func=0x83ae180 stgAllocForGMP,
realloc_func=0x83ae1c0 stgReallocForGMP, free_func=0x83ae170
stgDeallocForGMP) at ../mp_set_fns.c:39
#1 0x0805a697 in initAllocForGMP ()
#2 0x083da152 in __libc_csu_init ()
#3 0xb4bdf9fa in __libc_start_main (main=0x805f8d1 main, argc=1,
argv=0xb6f4, init=0x83da100 __libc_csu_init, fini=0x83da170
__libc_csu_fini, rtld_fini=0xb7fedc90 _dl_fini, stack_end=0xb6ec) at
libc-start.c:246
#4 0x0805f752 in _start ()
(gdb) cont
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xacc56b40 (LWP 23824)]
0x083b65b8 in rts_unsafeGetMyCapability ()
(gdb) bt
#0 0x083b65b8 in rts_unsafeGetMyCapability ()
#1 0x083ae18d in stgAllocForGMP ()
#2 0xb4dd9b54 in __gmpz_init (x=0xb15100b0) at ../../mpz/init.c:38
#3 0xac38a11c in wrap_nettle_mpi_init (w=0xacc55738) at mpi.c:82
#4 0xac2e6783 in _gnutls_mpi_init_scan (ret_mpi=0xacc55980, buffer=0xb150a108,
nbytes=257) at gnutls_mpi.c:118
#5 0xac2e6c65 in __gnutls_x509_read_int (node=optimized out,
value=0xac3925ef modulus, ret_mpi=0xacc55980, overwrite=0) at gnutls_mpi.c:306
#6 0xac2e71dd in _gnutls_x509_read_int (node=optimized out, value=optimized
out, ret_mpi=0xacc55980) at gnutls_mpi.c:324
#7 0xac314be4 in _gnutls_x509_read_rsa_pubkey (params=0xacc55980, dersize=270,
der=0xb150d9e8 0\202\001\n\002\202\001\001) at key_decode.c:73
#8 _gnutls_x509_read_pubkey (algo=GNUTLS_PK_RSA, der=0xb150d9e8
0\202\001\n\002\202\001\001, dersize=270, params=0xacc55980) at
key_decode.c:242
#9 0xac31f95b in _gnutls_get_asn_mpis (asn=0xb1501038, root=0xac3931d0
tbsCertificate.subjectPublicKeyInfo, params=0xacc55980) at mpi.c:102
#10 0xac312590 in _gnutls_x509_get_pk_algorithm (src=0xb1501038,
src_name=0xac3931d0 tbsCertificate.subjectPublicKeyInfo, bits=0xb1503a3c) at
common.c:1502
#11 0xac338697 in gnutls_x509_crt_get_pk_algorithm (cert=0xb1501000,
bits=0xb1503a3c) at x509.c:1094
#12 0xac2f9693 in gnutls_pubkey_import_x509 (key=0xb1503a38, crt=0xb1501000,
flags=0) at gnutls_pubkey.c:162
#13 0xac2f8a29 in gnutls_pcert_import_x509 (pcert=0xb1500fd8, crt=0xb1501000,
flags=0) at gnutls_pcert.c:71
#14 0xac2f8b60 in gnutls_pcert_import_x509_raw (pcert=0xb1500fd8,
cert=0xacc55bbc, format=GNUTLS_X509_FMT_DER, flags=0) at gnutls_pcert.c:191
#15 0xac355a18 in _gnutls_proc_x509_server_crt (data_size=optimized out,
data=optimized out, session=optimized out) at cert.c:
#16 _gnutls_proc_crt (session=0xb1501986, data=0xb1500fd8
8:P\261\360\233P\261\023\005, data_size=2479) at cert.c:1375
#17 0xac2dcb79 in _gnutls_recv_server_certificate (session=0x857aff0) at
