Bug#735529: RM: cpushare -- ROM; dead upstream, not maintained, RC buggy
Package: ftp.debian.org Severity: normal Hi, I was inspecting packages of the pkg-scicomp team which is merged with Debian Science. I noticed that the package cpushare did not had uploads since 2008 nor changes in VCS since 2009-03-14 (which only added a watch file to a now not existing web page). The most visible trace of this project in the internet is http://www.rechenkraft.net/wiki/index.php?title=CPUShare_%28beendet%29 which is a German page saying that the cpushare project is dead. Since it has an RC bug (#734715) I'm requesting the deletion from the Debian mirrors. Kind regards Andreas. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650035: os-prober: Please enable quiet operation
+1 to this ticket. It's so frustrating it's more that 2 years old, has a trivial fix (that doesn't affect default operation) and still wasn't fixed. Log levels were invented long ago. But os-prober thinks that it's OK to log debug output with notice priority (I'd be fine with that if it at least allowed to disable this stupid behavior). If there is any way I can help with getting this fixed I'd be glad to help. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: Xfce logind
On Thu, Jan 16, 2014 at 08:38:47AM +0100, Emilio Pozuelo Monfort wrote: On 15/01/14 22:17, Yves-Alexis Perez wrote: Now, as far as I understand it, PolicyKit/ConsoleKit are unmaintained, and the recommended alternative is to use logind. That means in the future, it's likely that upstream Xfce will have to move away from consolekit. That's not something they really like, considering the support was added not so long ago, but there's not much choice, unless someone wants to maintain consolekit in the long run. And it seems that the only choice right now is to go with logind. No patch have already been merged for that, but there are patches for various components (xfce4-power-manager and xfce4-session mostly, since for Thunar it's actually done in gvfs and/or udisks, so we won't have a choice anyway). Maybe I've misunderstood what you mean there, but xfce4-session had logind support merged[1] a while ago, though consolekit support is still there and you can choose to build one or the other. Yeah actually it was mostly about xfpm. Also note that it's not yet released, and that the upload issue still stands. Unless there's a runtime detection (like some of the proposed patches for xfpm), logind support is not something I can really upload until the tech-ctte has made its decision. Regards, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650035: os-prober: Please enable quiet operation
+1 to this ticket. It's so frustrating it's more that 2 years old, has a trivial fix (that doesn't affect default operation) and still wasn't fixed. Log levels were invented long ago. But os-prober thinks that it's OK to log debug output with notice priority (I'd be fine with that if it at least allowed to disable this stupid behavior). If there is any way I can help with getting this fixed I'd be glad to help. Regards, Dmitry -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635659: libdbi{,-drivers} maintenance
Hi, I'm the maintainer of sqlite and sqlite3 and back then I was the only syslog-ng maintainer. Thus when I saw libdbi and libdbi-drivers is up for adoption, started working on them. It was March, last year. When almost finished, I put it down, I don't know the reason. Still, yesterday I've made the last bits. Both build fine with pbuilder. You can grab them[1][2] for testing. May I be their maintainers, adding whoever wants it as uploader or is there anyone else to continue the packaging? The only one change that pending, is the removal of sqlite and thus libdbd-sqlite will be gone with that. Regards, Laszlo/GCS [1] dget -x http://www.barcikacomp.hu/gcs/libdbi_0.9.0-1.dsc [2] dget -x http://www.barcikacomp.hu/gcs/libdbi-drivers_0.9.0-1.dsc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722084: [lintian] Obsolete ruby 1.8
Hello Bastien, Package: lintian Version: 2.5.19 2.5.21 will obsolete ruby 1.8 as discussed at Ruby Sprint Paris, we would also obsolete Ruby 1.9.1. Could you please add in the next Lintian version the following packages: ruby1.9.1 ruby1.9.1-dev libruby1.9.1 Thanks, Jonas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720419: decrease severity
severity 720419 normal thanks ia64 is no longer a release arch. No need to make this bug RC. Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712841: qcontrol: Fan error reported on TS109
Thanks for the info, I'll figure some way to integrate that.
Unless we can determine how to distinguish a 209 from a 109 it might
still have to be something which is enabled locally. Martin -- still no
word from QNAP I take it?
I do have some code (in experimental) to ask via debconf when the system
can't be probed (I intended this for use on x86 QNAP boxes), I'd really
much prefer to keep autodetecting on ARM though.
Ian.
On Wed, 2014-01-15 at 23:13 +, Dermot O'Dwyer wrote:
The following appears to work OK in ts209.c:
case 0x73:
/* call_function(fan_error, ); */
{
unsigned char code = 0x30;
serial_write(code, 1);
}
break;
No errors in logs.
The rest of qcontrol continues working OK (manual led/buzzer commands).
Dermot
On 9 January 2014 20:04, Ian Campbell i...@hellion.org.uk wrote:
On Thu, 2014-01-09 at 09:46 +, Dermot O'Dwyer wrote:
On 3 January 2014 00:19, Ian Campbell i...@hellion.org.uk wrote:
Dermon, does commenting out the content of temp_high and temp_low in
qcontrol.conf and rebooting still end up with fan_error getting called
lots?
Yes, fan_error still gets called when there are empty temp_high and
temp_low functions.
I suppose there are few other things which could be tried if you are
able, there are some #defines for PIC commands relating to fans in the
QNAP kernel headers which are not currently used by qcontrol:
include/qnap/pic.h:#define QNAP_PIC_FAN_STOP0x30
include/qnap/pic.h:#define QNAP_PIC_FAN_ENABLE 0x71
include/qnap/pic.h:#define QNAP_PIC_FAN_DISABLE 0x72
(these aren't used elsewhere in the kernel, so I can't see how qnap's
firmware uses them -- I guess this header is consumed by their
userspace)
Probably the easiest way to test these is to edit ts219.c and where
there is:
call_function(fan_error, );
instead add (untested):
{
unsigned char code = 0x30;
serial_write(code, 1);
}
Try this for 0x72 as well. I don't imagine 0x71 would be much use.
Hrm... qcontrol could really use a way to send arbitrary bytes to the
PIC from LUA code.
Ian.
signature.asc
Description: This is a digitally signed message part
Bug#712841: qcontrol: Fan error reported on TS109
On Thu, 2014-01-16 at 08:29 +, Ian Campbell wrote: Unless we can determine how to distinguish a 209 from a 109 it might still have to be something which is enabled locally. It took me about 2s from pressing send to wake up and realise that stopping the fan in the fan error hook might be the right thing to do on the 209 as well. Although on the 209 you'd probably want some sort of loud warning, while on the 109 you would want it to happen silently. So maybe it is still worth detecting... Ian. signature.asc Description: This is a digitally signed message part
Bug#735530: samhain: FTBFS on amd64 and kfreebsd
package: samhain version: 3.1.0-2 severity: serious Hi, The latest samhain upload doesn't build on amd64. This was also the case with the previous upload (3.1.0-1). Also, the audit build-dep doesn't exist on kfreebsd, so the build can't be started there. The previous upload also failed on kfreebsd-amd64 (but it did build fine on kfreebsd-i386). https://buildd.debian.org/status/package.php?p=samhain Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735522: ITP: python-pyxenstore -- Access XenStore from Python
On Thu, 2014-01-16 at 14:16 +0800, Thomas Goirand wrote: Package: wnpp Severity: wishlist Owner: Thomas Goirand z...@debian.org * Package name: python-pyxenstore Version : 0.0.2 Upstream Author : Chris Behrens cbehr...@codestud.com * URL : https://pypi.python.org/pypi/pyxenstore * License : Apache-2.0 Programming Lang: C, Python Description : Access XenStore from Python This package contains the Python bindings to access the XenStore filesystem. It may be useful from the dom0 and/or from the domU, to get / set information about runing virtual machines. Xen upstream already has a set of python bindings for libxenstore, are they not packaged or are these ones better in some way? Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727118: ccbuild: FTBFS on several architectures
On 2014-01-16 08:01, Andreas Rönnquist wrote: | Dear maintainer, | | I've prepared an NMU for ccbuild (versioned as 2.0.6-0.1) and | can upload it to DELAYED/10. Thanks for the work. I've updated the Alioth Git and will upload hopefully soon. Jari -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710981: Pending fixes for bugs in the libpod-wsdl-perl package
tag 710981 + pending thanks Some bugs in the libpod-wsdl-perl package are closed in revision 050f901ee0a9c9e23291af8a7b0bd40f4dc23468 in branch 'master' by Damyan Ivanov The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libpod-wsdl-perl.git;a=commitdiff;h=050f901 Commit message: add patch fixing bad comparison of XML strings in tests. Closes: #710981 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735440: fusionforge-plugin-scmsvn: post-commit FS processing had error 'attempt to write a readonly database'
On Wed, 15 Jan 2014, Olivier Berger wrote: This seems related to SVN's way to delegate tasks to sqlite, as per http://subversion.tigris.org/issues/show_bug.cgi?id=3437 I’ve fixed it like this: https://evolvis.org/pipermail/evolvis-platfrm-commits/2013-December/002728.html This commit takes care of all newly created repos; for existing ones, I’ve just added that line to fsfs.conf manually. (Actually, just scripted over /scmrepos/svn/*/ ofc.) bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735531: RM: ruby-kakasi -- ROM; does not work with newer rubies; upstream dead
Package: ftp.debian.org Severity: normal Hello ftp-masters, could you please remove ruby-kakasi from the archive: - does not work with 1.9/2.0 - upstream dead Thanks, Jonas Ruby Sprint Paris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722379: Updating the Ruby packaging policy for your package «libhdfeos5-ruby1.8»
severity 722379 serious thanks Hello, your package build with Ruby 1.8. Please update your package to fit to the Ruby policy and build it against Ruby 2.0 with gem2deb. If your package does not build against Ruby 2.0 and there is no newer upstream version, consider to remove that package from the archive. If use have no time for the package update, please ping to ruby PKG Extras, we will take care. Thanks, Jonas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#190162: #190162 please provide samba.schema in samba package
Hello, IMHO this bug can be closed with samba 4.x because upstream does not support the OpenLDAP backend anymore so there is no need for the samba.schema in the Debian package anymore. https://wiki.samba.org/index.php/Samba4/LDAP_Backend What do you think? Regards Noël signature.asc Description: This is a digitally signed message part
Bug#735265: [Pkg-xfce-devel] Bug#735251: lightdm: user locale tweaks are clobbered by non-default locale
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, Jan 15, 2014 at 07:29:02PM +0100, Simon Pepping wrote: On Tue, Jan 14, 2014 at 09:18:17PM +0100, Yves-Alexis Perez wrote: So I think you should use export LANG= in the above .xsessionrc and it would correctly set the LANG in the child session. Done Now, I have no idea why the saved .dmrc is not correctly loaded for you, it might help to look at lightdm and lightdm-gtk-greeters logs. I logged after having removed .dmrc and /var/cache/lightdm/dmrc/simon.dmrc. It made no difference. I logged with hide-users true and false. It made no difference. The language selector is always at Dutch, which is the second entry in the list, but the system-wide locale. It does not change when I select a different user. Ok, so actually it /does/ use the system locale by default, which is a rather good idea. Herewith a few more data, reporting the locale before and after .xsessionrc, and the lightdm logs. Action: Select english in the language selector, log in. 1) Report of locale settings in .xsessionrc: before .xsessionrc LANG=nl_NL.UTF-8 LANGUAGE= LC_CTYPE=nl_NL.UTF-8 LC_NUMERIC=nl_NL.UTF-8 LC_TIME=nl_NL.UTF-8 LC_COLLATE=nl_NL.UTF-8 LC_MONETARY=nl_NL.UTF-8 LC_MESSAGES=nl_NL.UTF-8 LC_PAPER=nl_NL.UTF-8 LC_NAME=nl_NL.UTF-8 LC_ADDRESS=nl_NL.UTF-8 LC_TELEPHONE=nl_NL.UTF-8 LC_MEASUREMENT=nl_NL.UTF-8 LC_IDENTIFICATION=nl_NL.UTF-8 LC_ALL= So the language selection from the greeter doesn't actually work here? after LANG=en_US.UTF-8 LANGUAGE=en LC_CTYPE=en_US.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_TIME=nl_NL.UTF-8 LC_COLLATE=en_US.UTF-8 LC_MONETARY=nl_NL.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=nl_NL.UTF-8 LC_NAME=nl_NL.UTF-8 LC_ADDRESS=nl_NL.UTF-8 LC_TELEPHONE=nl_NL.UTF-8 LC_MEASUREMENT=nl_NL.UTF-8 LC_IDENTIFICATION=nl_NL.UTF-8 LC_ALL= export GDM_LANG='en_US.utf8' export LANG='en_US.UTF-8' export LANGUAGE='en' Honestly, I don't want to debug anything past .xsessionrc, this is outside of lightdm scope and it's already complicated enough. 3) lightdm log file Note that this is not the first login [+244.74s] DEBUG: Seat: Active display server stopped, starting greeter [+244.74s] DEBUG: Seat: Creating greeter session [+244.74s] DEBUG: Seat: Setting XDG_SEAT=seat0 [+244.74s] DEBUG: Seat: Creating display server of type x [+244.74s] DEBUG: Seat: Starting local X display [+244.74s] DEBUG: Using VT 7 [+244.74s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log [+244.74s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0 [+244.74s] DEBUG: DisplayServer x-0: Launching X Server [+244.74s] DEBUG: Launching process 4302: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [+244.74s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0 [+244.74s] DEBUG: Releasing VT 7 [+244.86s] DEBUG: Got signal 10 from process 4302 [+244.86s] DEBUG: DisplayServer x-0: Got signal from X server :0 [+244.86s] DEBUG: DisplayServer x-0: Connecting to XServer :0 [+244.86s] DEBUG: Seat: Display server ready, starting session authentication [+244.86s] DEBUG: Session: Setting XDG_VTNR=7 [+244.86s] DEBUG: Session pid=4307: Started with service 'lightdm-greeter', username 'lightdm' [+244.88s] DEBUG: Session pid=4307: Authentication complete with return value 0: Success [+244.88s] DEBUG: Seat: Session authenticated, running command [+244.88s] DEBUG: Session pid=4307: Setting XDG_VTNR=7 [+244.88s] DEBUG: Session pid=4307: Running command /usr/sbin/lightdm-gtk-greeter [+244.88s] DEBUG: Session pid=4307: Logging to /var/log/lightdm/x-0-greeter.log [+244.90s] DEBUG: Activating VT 7 [+244.94s] DEBUG: Session pid=4307: Greeter connected version=1.8.5 [+245.31s] DEBUG: Session pid=4307: Greeter start authentication for simon [+245.31s] DEBUG: Seat: Setting XDG_SEAT=seat0 [+245.31s] DEBUG: Session: Setting XDG_VTNR=7 [+245.31s] DEBUG: Session pid=4334: Started with service 'lightdm', username 'simon' [+245.32s] DEBUG: Session pid=4334: Got 1 message(s) from PAM [+245.32s] DEBUG: Session pid=4307: Prompt greeter with 1 message(s) [+267.43s] DEBUG: Session pid=4307: Continue authentication [+267.46s] DEBUG: Session pid=4334: Authentication complete with return value 0: Success [+267.46s] DEBUG: Session pid=4307: Authenticate result for user simon: Success [+267.47s] DEBUG: Session pid=4307: User simon authorized [+267.47s] DEBUG: Session pid=4307: Greeter sets language en_US.utf8 [+267.48s] DEBUG: Writing /home/simon/.dmrc [+267.56s] DEBUG: Session pid=4307: Greeter requests session xfce [+267.57s] DEBUG: Writing /home/simon/.dmrc [+267.63s] DEBUG: Seat: Stopping greeter; display server will be re-used for user session [+267.63s] DEBUG: Session pid=4307: Sending SIGTERM [+267.65s] DEBUG: Session pid=4307: Greeter closed communication channel [+267.65s] DEBUG: Session pid=4307: Exited with return value 0
Bug#727708: Bits from linux.conf.au
On 15 January 2014 20:36, Martin Pitt mp...@debian.org wrote: It's not realistic for a maintainer to continuously test three init systems; It's not realistic for a maintainer to continuously test against 13 architectures (including three different kernel trees) either. So we don't do that and instead let maintainers make their best effort when packaging, expect them to test locally, and then rely on porters and users to report bugs when there are problems. it's not realistic for a porter to continously test startup scripts for thousands of packages. It's reasonable to semi-continuously test installation scripts for thousands of packages -- that's what piuparts does, and we have sponsored cloud resources to support that. It seems like that would be fairly straightforward to duplicate for testing packages with alternative init systems. Cheers, aj -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735503: Working on it upstream
Hi, FYI, we're working with upstream so that the minified javascript files are replaced with their full source counter-parts. This isn't a problem, because Horizon uses python-django-compressor, which minifies the javascript files on-the-fly. I'd rather not fix the package right away, and prefer wait for the upstream patch to get in the current Havana branch. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735251: [Pkg-xfce-devel] Bug#735251: lightdm: user locale tweaks are clobbered by non-default locale
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, Jan 16, 2014 at 09:28:32AM +0900, Olaf Meeuwissen wrote: Did just that. All locale variables, including LANG, are as per tweaks in ~/.xsessionrc right up to the `exec $STARTUP` in the last Xsession.d snippet. The locale output in an Xfce terminal or XTerm shows the LANG value that is in ~/.dmrc. That is, not whatever LANG value was set in ~/.xsessionrc. Ok, so in any case, lightdm is not involved here anymore. I also tried turning off all autostarted applications (in the Session and Startup configuration utility) but LANG *still* gets clobbered. At this point, no applications started automatically, Xfsettingsd is still started despite not being configured to do so. My hunch is that either that or one of xfwm4 and xfdesktop export LANG based on what is set in ~/.dmrc (or /var/cache/lightdm/dmrc/$USER.dmrc). No, that's completely unrelated. .dmrc is really only related to the DM. But in any case, setting LANG in .xsessionrc doesn't make much sense imho. Care to explain why? For me the correct LANG value is essential to get my input method editor to work correctly (or so it seems). # Of course, setting it in ~/.dmrc works for me but I'd like to know why # I should set it there too. The way I see it (as I already explained), you select the wanted locale (LANG) in the greeter language selector (and it gets saved to .dmrc for later). Then, if you need to “correct” (for LC_MESSAGES for example) you can do it un .xsessionrc. Now, nobody forces you to do that way, you can do whatever you want in .xsessionrc and completely ignore the greeter. See above. It looks like the LANG value is clobbered later, somewhere in $STARTUP, which in my case is /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/im-launch x-session-manager Then you know where to start looking. But as I said to Simon, that's pretty much outside my perimeter (well unless it happens in xfce4-session, but that's unrelated to lightdm anyway, and I need to pick my Xfce hat). With my Xfce hat on, that reminds me of something worth checking. I think xfce4-session tries to respect GDM_LANG and overwrites LANG with it. LightDM doesn't set GDM_LANG (that's a gdm thing) but I think Simon did set it manually at some point, which might then have this side effect. Maybe check that's not your case? I know nobody forces me to do so, but I parse the above as if you want to modify your locale settings or other environment variables, your ~/.xsessionrc is the place to do so. Hence, I did and it didn't work as expected. Maybe there should be some documentation that (at least) LANG should be set elsewhere because $STARTUP may override it? Well, anything can modify LANG its the child processes anyway, there's nothing the parents can do about that. In any case, I'm again just confused on all those bugs, but my feeling is just that there's no bug in lightdm/lightdm-gtk-greeter here, but later in the startup process, so those bugs should either be reassigned or just closed, in order top stop confusion. Regards, - -- Yves-Alexis Perez -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCgAGBQJS16L/AAoJEG3bU/KmdcCl6CsIAJ6+8HbEPMADO12SDPqtE4UB ZUSrb4ZuG1Bu/K7iu55O8n5soqo9f7/nx2WtRuI4MFGvay8MBwcq4qa2MtzTtesn UpHoX3t3/G3fDXF4qxyAdqN13yF/3txhRiinLdzsgIKbq9Tr3VTAtS/r4gXXItzg BuZd7h6yiPO4hehByKFno6MxWdmqwtSArfORZQDZP+G1BHUVuB2JJCF0TV1IQQD2 ca5T66m+2xtkqhUPibn/dSqVg7TMWVrnYU2MjKbG8KsHYHwmoB9g8ZYLL5eUeFfe fQruoiU8JYvL07SivpIQ1a0bUKNjslRADXc+3DhPdJpyYVvIIhuJeSkIGoCPue8= =kNYV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735442: libthrust: Why Multi-Arch allowed?
Control: tag -1 pending On 2014-01-15 13:51, Osamu Aoki wrote: Package: libthrust-dev Architecture: all Multi-Arch: allowed fixed in SVN long ago to become Package: libthrust-dev Architecture: all Multi-Arch: foreign Are you sure this Multi-Arch: is intentional one? It does not make sense. (python and cpp seems to have reasons.) And especially it does not work as intended: it does not allow to install nvidia-cuda-toolkit:i386 on amd64, but M-A: foreign would But unless someone needs this now, the fix will probably be delayed until the next upstream release ... Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#678657: eog: Cannot save large images
Sorry, I don't know where this file has gone, and I don't use eog anymore (memory-hungry, buggy) This was a 300dpi, A4 scan created with http://packages.debian.org/wheezy/simple-scan. Maybe you could try to reproduce it? Feel free to close this bug if you can't reproduce it thanks 2014/1/15 althaser altha...@gmail.com: nodiscc can you provide LaReplique-1.jpg to test ? thanks regards althaser -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735478: [Pkg-xfce-devel] Bug#735478: xfce4-weather-plugin: assertion failed on certain data from weather.com
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, Jan 15, 2014 at 06:20:54PM +0100, Christoph Biedl wrote: Package: xfce4-weather-plugin Version: 0.7.4-4 Severity: important Tags: patch Dear Maintainer, starting yesterday, xfce4-weather-plugin more or less often aborts due to an assertion failure, resulting in a pop-up box from the panel manager. Severity not set to even grave since this might happen for certain locations only. The actual message is: | weather:ERROR:weather-parsers.c:304:parse_dayf: assertion failed: (ret-hi != NULL) Responsible is a missing value in the data sent from weather.com: |lsup1/15/14 7:00 AM CET/lsup |day d=0 t=Wednesday dt=Jan 15 +hi/hi |low4/low Dropping the assertion check from the sources however does not appear to have negative impact, patch below. I don't really like this, it might have bad side effects too. But it's unlikely to be fixed upstream considering the plugin has been rewritten completely. I'll try to take a look and see if a stable upload can be made. Regards, - -- Yves-Alexis Perez -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBCgAGBQJS16R7AAoJEG3bU/KmdcCl6TIIAKfGKXv9jVJj42MuCJoFI+Ex v6qt82nM18ZB0j+cYxkBlleFq5Cj/eK8VnFjdZpk8bwxTyPHjSLGaH2YIluzpjt7 HyH5hCIC/IjHgjytaJfXtztFipzTAyCSUaXKqFAe29/v9++T3R1dq4hqSJ6mFOE2 O3QJ9hlTrFBJPRHb/flqMlmMksNm3Mxd8MP8qENCwjya/F0XB922uBA7G7Oy124r zXyOWPe+Q3yDZygAj040dpKImU39Nocn3Iu5QxBqVGiDe3/lSfLKJvkk2ip4bggh 9/l0m5COduTRjbPkpBcS1AUf8B0vKOAHhHUTTobsOLALyBmVGm91lEjAf7ltD24= =Z5O+ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730908: libio-event-perl: FTBFS: Failed tests
Control: tags -1 confirmed -=| gregor herrmann, 30.11.2013 21:17:11 +0100 |=- On Sat, 30 Nov 2013 17:33:15 +0100, David Suárez wrote: t/forked1.t . ok # Looks like you planned 115 tests but ran 111. print 26175: Connection reset by peer Compilation failed in require at t/forked2.t line 5. t/forked2.t . Dubious, test returned 255 (wstat 65280, 0xff00) Failed 4/115 subtests Now that's an intereting bug. The tests still pass for me but take quite some long. So maybe we're running into a timeout here, or some other fork problem on the amazon build machine ... I was able to reproduce this by heavily loading the machine. I used pbzip2 -p16 $bug file /dev/null on a 4-core amd64. The tests failed like this: ok 109 # CHILD closing # test paragraph mode, getlines, $/ set funny ok 110 ok 111 # SIGPIPE recevied in 5395 # Looks like you planned 115 tests but ran 111. print 5395: Прекъснат канал Compilation failed in require at t/forked2.t line 5. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 4/115 subtests Test Summary Report --- t/forked2.t (Wstat: 65280 Tests: 111 Failed: 0) Non-zero exit status: 255 Parse errors: Bad plan. You planned 115 tests but ran 111. It is not the same sub-test, suggesting that probably all subtests are fragile on overloaded hosts. Maybe even the whole module is fragile. I'll try to figure out what might be the problem, but my experience with dbd-firebird's fork events tests and arm* doesn't give me high hopes. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#712841: qcontrol: Fan error reported on TS109
* Ian Campbell i...@hellion.org.uk [2014-01-16 08:29]: Unless we can determine how to distinguish a 209 from a 109 it might still have to be something which is enabled locally. Martin -- still no word from QNAP I take it? Unfortunately, I haven't heard from QNAP. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735532: libanyevent-rabbitmq-perl: Invalid location of fixed_amqp0-9-1.xml
Package: libanyevent-rabbitmq-perl Version: 1.15~dfsg-1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, The XML spec file that is used by AnyEvent::RabbitMQ seems to be in the wrong location. Because of licensing issues the original file is removed from the package, and replaced by a symlink to a stripped version included in amqp-specs. The location of the symlink differs from the expected location though. To demonstrate the issue: $ perl -MAnyEvent::RabbitMQ -e 'AnyEvent::RabbitMQ-new-load_xml_spec();' Could not create file parser context for file /usr/share/perl5/auto/share/dist/AnyEvent-RabbitMQ/fixed_amqp0-9-1.xml: No such file or directory at /usr/share/perl5/Net/AMQP/Protocol.pm line 64. (in cleanup) close already in progress at /usr/share/perl5/AnyEvent/RabbitMQ.pm line 612. (This command is expected to give no output and no error.) The symlink is located in a subdirectory 'share', which is not expected by the library. This patch fixes the issue for me: diff --git a/debian/rules b/debian/rules index 46cd581..a86c334 100755 --- a/debian/rules +++ b/debian/rules @@ -52,8 +52,8 @@ clean:: # use separately packaged spec files DEB_DH_LINK_$(pkg) = \ /usr/share/amqp/specs/0-9-1-rabbit/amqp0-9-1.stripped.extended.xml \ - /usr/share/perl5/auto/share/dist/AnyEvent-RabbitMQ/share/fixed_amqp0-9-1.xml + /usr/share/perl5/auto/share/dist/AnyEvent-RabbitMQ/fixed_amqp0-9-1.xml common-configure-arch common-configure-indep:: - ln -sf /usr/share/amqp/specs/0-9-1-rabbit/amqp0-9-1.stripped.extended.xml share/fixed_amqp0-9-1.xml + ln -sf /usr/share/amqp/specs/0-9-1-rabbit/amqp0-9-1.stripped.extended.xml fixed_amqp0-9-1.xml clean:: - rm -rf share/fixed_amqp0-9-1.xml + rm -rf fixed_amqp0-9-1.xml -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libanyevent-rabbitmq-perl depends on: ii libanyevent-perl 7.070-1 ii libdevel-globaldestruction-perl 0.12-1 ii libfile-sharedir-perl1.03-1 ii liblist-moreutils-perl 0.33-1+b2 ii libnamespace-clean-perl 0.24-1 ii libnet-amqp-perl 0.06~dfsg-1 ii libreadonly-perl 1.04-1 ii perl 5.18.1-5 Versions of packages libanyevent-rabbitmq-perl recommends: ii amqp-specs 1-0r0-2 libanyevent-rabbitmq-perl suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735533: libwine: fonts-liberation instead of ttf-liberation in Recommends
Package: libwine Version: 1.6.2-2 Severity: minor Tags: upstream Dear Maintainer, Since the ttf-liberation was replaced by fonts-liberation, I think that's more utile to replace it in Recommends section. This replacement allows to avoid installation unneeded dummy packages. Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libwine depends on: ii libasound21.0.27.2-3 ii libc6 2.17-97 ii libexif12 0.6.21-1 ii libgl1-mesa-glx [libgl1] 9.2.2-1 ii libglu1-mesa [libglu1]9.0.0-2 ii libgphoto2-2 2.4.14-2.4 ii libgphoto2-port0 2.4.14-2.4 ii liblcms2-22.2+git20110628-2.3+b1 ii libldap-2.4-2 2.4.31-1+nmu2+b1 ii libmpg123-0 1.16.0-1 ii libopenal11:1.14-4 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxml2 2.9.1+dfsg1-3 ii multiarch-support 2.17-97 ii zlib1g1:1.2.8.dfsg-1 Versions of packages libwine recommends: ii libxcursor1 1:1.1.14-1 pn ttf-liberation none Versions of packages libwine suggests: pn wine-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720701: cqrlog: FTBFS: Fatal: Can't find unit typ used by spe
Hello, this bug has been fixed in version 1.7.0 which was released yesterday (2014-01-15). 73 Petr, OK2CQR -- http://HamQTH.com/ok2cqr http://ok2cqr.com http://cqrlog.com http://cqrtest.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732937: dpkg: fails somewhat regularly on kfreebsd-amd64
Michael Vogt m...@debian.org (2014-01-16): On Sun, Jan 12, 2014 at 08:05:06PM +, Steven Chamberlain wrote: Control: tags -1 found apt/0.9.14.2 Indeed upgrading only libapt-pkg4.12 is enough to trigger this. [..] Thanks a bunch for your bugreport and sorry for my slow reply. Its likely that this is fallout from some fairly big changes in the handling of dpkg. What is the best way for me to reproduce this? I don't have a kfreebsd system right now - is installing one from a current installer image in kvm the quickest way (I assume so)? This might be slightly quicker: http://blog.aurel32.net/153 http://people.debian.org/~aurel32/qemu/ But otherwise, that's what I'd do. Mraw, KiBi. signature.asc Description: Digital signature
Bug#690538: Isn't the submenu concept itself clashing with GRUB_DEFAULT settings != 0?
On Thu, Jan 16, 2014 at 02:25:14AM +0100, Maurizio Avogadro wrote: I didn't read this bug report before trying to understand the issue; I used to keep GRUB_DEFAULT=saved and the introduction of the submenu catched me unprepared. Going to give my 2 cents by telling my thoughts. I started to think that the creation of a submenu should be avoided in any case when GRUB_DEFAULT is not set to 0: at next boot, if the default entry is in the submenu, grub will show the submenu as selected without showing what's going to boot, which doesn't make any sense IMO. I'm concerned that this will make it harder for people to look at the menu structure and work out what they need to set GRUB_DEFAULT to, because the act of setting GRUB_DEFAULT will change the behaviour. This seems unnecessarily confusing and undesirable. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727607: Any update?
Hi, It's been quite some time already that I sent this bug report. It'd be nice if it was addressed... Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735470: [apparmor] Fwd: Bug#735470: Could be implemented centrally with a dpkg trigger instead of requiring every package shipping an apparmor file to use dh_apparmor
Hi Seth, Le mercredi, 15 janvier 2014, 11.14:07 Seth Arnold a écrit : On Wed, Jan 15, 2014 at 07:30:52PM +0100, intrigeri wrote: From: Didier Raboud o...@debian.org apparmor could have an 'interest /etc/apparmor.d/' triggers file and its postinst would then do the machinery to create (or remove) the /etc/apparmor.d/local/* files accordingly. This does sound nice, but the next part worries me.. This could also have the side benefit of only running apparmor_parser once for all files installed at the same time. When would this single apparmor_parser run happen? It needs to happen before daemons are started or restarted in their postinst scripts, otherwise the AppArmor policy won't be enforced. As far as I understand deb-triggers' manpage, this can be enforced using 'activate /etc/apparmor.d/', which will then make the trigger run at the start of the configure operation, which ensures exactly what you want. Cheers, OdyX signature.asc Description: This is a digitally signed message part.
Bug#730908: libio-event-perl: FTBFS: Failed tests
-=| Damyan Ivanov, 16.01.2014 11:25:41 +0200 |=- I was able to reproduce this by heavily loading the machine. I used pbzip2 -p16 $bug file /dev/null on a 4-core amd64. The tests failed like this: ok 109 # CHILD closing # test paragraph mode, getlines, $/ set funny ok 110 ok 111 # SIGPIPE recevied in 5395 # Looks like you planned 115 tests but ran 111. print 5395: Broken pipe Compilation failed in require at t/forked2.t line 5. Dubious, test returned 255 (wstat 65280, 0xff00) Failed 4/115 subtests Here's the output with $debug enabled in t/forked.tt: # test paragraph mode, getlines, $/ set funny # ACCEPTED CONNECTION ok 110 ok 111 # got 'go\n' # SENDING 'this is ' # SENDING 'a test\n' # SIGPIPE recevied in 6846 # Looks like you planned 115 tests but ran 111. print 6846: Broken pipe Compilation failed in require at t/forked2.t line 5. 6846 is the child PID. I tried running the test under strace -ff, but was unable to reproduce the problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#706356: closed by Torsten Landschoff t.landsch...@gmx.net (You can't delete a broadcast)
This ist very unbelievable. You can not delete my message??? SuSE can, und you not? I dont believe you. You are a liar. I am realy thing of sue you. Am 16.01.2014 01:12, schrieb Debian Bug Tracking System: Hi Mr. anacronataff, I am closing this ticket as it is not a bug in ddclient. Unfortunately, we can't really remove a posting here as it is mirrored all over the internet via mailing list repeaters, mailing list archives etc. Greetings, Torsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735534: ifupdown: support preferred-lifetime for v4tunnel
Package: ifupdown Version: 0.7.47.1 Severity: wishlist Please support preferred-lifetime for inet6 v4tunnel as well. Currently it is supported for inet6 static. Thanks Oskar -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ifupdown depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-45 ii iproute2 3.12.0-1 ii libc62.17-97 ii lsb-base 4.1+Debian12 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.2.4-7 Versions of packages ifupdown suggests: ii net-tools 1.60-25 ii ppp2.4.5+git20130610-3 ii rdnssd 1.0.1-1+b1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#734954: screenruler: diff for NMU version 0.960+bzr41-1.2
tags 734954 + patch
tags 734954 + pending
thanks
Dear maintainer,
I've prepared an NMU for screenruler (versioned as 0.960+bzr41-1.2) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru screenruler-0.960+bzr41/debian/changelog
screenruler-0.960+bzr41/debian/changelog
--- screenruler-0.960+bzr41/debian/changelog2013-06-03 18:21:19.0
+0200
+++ screenruler-0.960+bzr41/debian/changelog2014-01-16 11:09:08.0
+0100
@@ -1,3 +1,10 @@
+screenruler (0.960+bzr41-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Apply patch for Ruby 1.9 support, drop hardcoding of 1.8 (Closes: #734954)
+
+ -- Christian Hofstaedtler z...@debian.org Thu, 16 Jan 2014 11:08:20 +0100
+
screenruler (0.960+bzr41-1.1) unstable; urgency=low
* Non-maintainer upload.
diff -Nru screenruler-0.960+bzr41/debian/control
screenruler-0.960+bzr41/debian/control
--- screenruler-0.960+bzr41/debian/control 2013-06-03 18:20:23.0
+0200
+++ screenruler-0.960+bzr41/debian/control 2014-01-16 10:55:44.0
+0100
@@ -8,7 +8,7 @@
Package: screenruler
Architecture: all
-Depends: ${misc:Depends}, ruby1.8, ruby-gtk2, ruby-cairo, ruby-gettext
+Depends: ${misc:Depends}, ruby | ruby-interpreter, ruby-gtk2, ruby-cairo,
ruby-gettext
Description: measure objects on screen with a variety of metrics
ScreenRuler will display a ruler on screen which allows you to measure the
other objects that you've there. It has the following features:
diff -Nru screenruler-0.960+bzr41/debian/patches/debian-changes-0.960+bzr41-1
screenruler-0.960+bzr41/debian/patches/debian-changes-0.960+bzr41-1
--- screenruler-0.960+bzr41/debian/patches/debian-changes-0.960+bzr41-1
2012-01-25 00:34:33.0 +0100
+++ screenruler-0.960+bzr41/debian/patches/debian-changes-0.960+bzr41-1
1970-01-01 01:00:00.0 +0100
@@ -1,50 +0,0 @@
-Description: Upstream changes introduced in version 0.960+bzr41-1
- This patch has been created by dpkg-source during the package build.
- Here's the last changelog entry, hopefully it gives details on why
- those changes were made:
- .
- screenruler (0.960+bzr41-1) unstable; urgency=low
- .
- * New upstream version + modifications from trunk:
- - Port to GtkBuilder and replace GConf with a YAML file (Closes: #639437,
-#654710).
- - Handle symlinks in screenruler.rb.
- - Added a help window and internationalization support.
- - Various bug fixes.
- * debian/control:
- - Update dependencies.
- * debian/screenruler.xpm:
- - Fix typo in Catalan translation and add a German translation.
- * debian/watch:
- - Delete it (no point, upstream version numbers are inconsistent).
- * screenruler.rb:
- - Hardcode Ruby 1.8.
- * Change to source format 3.0 (quilt) and debhelper compatibility
- version 7, switch from CDBS to dh and bump Standards-Version to 3.9.2.
- .
- The person named in the Author field signed this changelog entry.
-Author: Siegfried-Angel Gevatter Pujals rai...@ubuntu.com
-Bug-Debian: http://bugs.debian.org/639437
-Bug-Debian: http://bugs.debian.org/654710
-
-The information above should follow the Patch Tagging Guidelines, please
-checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
-are templates for supplementary fields that you might want to add:
-
-Origin: vendor|upstream|other, url of original patch
-Bug: url in upstream bugtracker
-Bug-Debian: http://bugs.debian.org/bugnumber
-Bug-Ubuntu: https://launchpad.net/bugs/bugnumber
-Forwarded: no|not-needed|url proving that it has been forwarded
-Reviewed-By: name and email of someone who approved the patch
-Last-Update: -MM-DD
-
screenruler-0.960+bzr41.orig/screenruler.rb
-+++ screenruler-0.960+bzr41/screenruler.rb
-@@ -1,4 +1,4 @@
--#!/usr/bin/env ruby
-+#!/usr/bin/ruby1.8
- #coding: utf-8
-
-
###
diff -Nru screenruler-0.960+bzr41/debian/patches/hardcode-data-path.patch
screenruler-0.960+bzr41/debian/patches/hardcode-data-path.patch
--- screenruler-0.960+bzr41/debian/patches/hardcode-data-path.patch
2012-01-25 00:29:57.0 +0100
+++ screenruler-0.960+bzr41/debian/patches/hardcode-data-path.patch
2014-01-16 11:05:23.0 +0100
@@ -1,7 +1,7 @@
Index: screenruler-0.960+bzr41/screenruler.rb
===
screenruler-0.960+bzr41.orig/screenruler.rb2012-01-25
00:28:43.160859576 +0100
-+++ screenruler-0.960+bzr41/screenruler.rb 2012-01-25 00:28:39.960859677
+0100
+--- screenruler-0.960+bzr41.orig/screenruler.rb2014-01-16
11:04:00.063701352 +0100
screenruler-0.960+bzr41/screenruler.rb 2014-01-16 11:04:47.919408300
+0100
@@ -19,7 +19,7 @@
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
Bug#735535: autopkgtest fails
Package: owncloud-client Version: 1.5.0+dfsg-4 Hello, owncloud-client's autopkgtest currently fails [1]: mkdir obj-/config mkdir: cannot create directory ���obj-/config���: No such file or directory That's because debian/rules uses $DEB_HOST_GNU_TYPE without defining it. Modern dpkg-buildpackage does that, but autopkgtest doesn't use that and Debian policy also says that invoking debian/rules directly should work. After fixing that, the test fails on an invalid variable expansion: adt-run: ubtree0t-make-tests: [ /tmp/adt-run.Le8IcK/ubtree0-build/real-tree/debian/tests/make-tests: 3: /tmp/adt-run.Le8IcK/ubtree0-build/real-tree/debian/tests/make-tests: ADTTMP: not found After fixing that, the test fails on an unknown make target: ubtree0t-make-tests FAIL status: 0, stderr: make: *** No rule to make target `tests'. Stop. At this point I'm lost. make test (the usual name if you add automatic tests to cmake) doesn't exist either, nor does make check. What is the intention here? Is there some way to run the upstream tests against the installed package? Running them against the built source tree is against autopkgtest's intention -- you wouldn't actually verify that the installed package works. Also, debian/tests/make-tests creates/removes the config directory in the current dir (i. e. the source tree root), not in $ADTTMP. Attached debdiff fixes above issues, but the tests make target issue still needs to be fixed. It should run some smoketesting against the installed package. Thanks for considering, Martin [1] https://jenkins.qa.ubuntu.com/job/trusty-adt-owncloud-client/11/ARCH=i386,label=adt/console -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) diff -Nru owncloud-client-1.5.0+dfsg/debian/changelog owncloud-client-1.5.0+dfsg/debian/changelog --- owncloud-client-1.5.0+dfsg/debian/changelog 2014-01-02 14:10:09.0 +0100 +++ owncloud-client-1.5.0+dfsg/debian/changelog 2014-01-16 11:25:23.0 +0100 @@ -1,3 +1,13 @@ +owncloud-client (1.5.0+dfsg-4ubuntu2) UNRELEASED; urgency=medium + + * debian/rules: Define $DEB_HOST_GNU_TYPE as dh_auto_test is using it. Fixes +autopkgtest. + * debian/tests/make-tests: +- Fix $ADTTMP variable expansion. +- Fix path of temporary config directory. + + -- Martin Pitt martin.p...@ubuntu.com Thu, 16 Jan 2014 10:49:37 +0100 + owncloud-client (1.5.0+dfsg-4ubuntu1) trusty; urgency=medium * Update libowncloudsync0.install for multi-arch location. diff -Nru owncloud-client-1.5.0+dfsg/debian/rules owncloud-client-1.5.0+dfsg/debian/rules --- owncloud-client-1.5.0+dfsg/debian/rules 2013-12-30 23:20:02.0 +0100 +++ owncloud-client-1.5.0+dfsg/debian/rules 2014-01-16 10:49:35.0 +0100 @@ -1,8 +1,11 @@ #!/usr/bin/make -f +DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) + export CSYNC_DIR=/usr/include/ocsync export DEB_BUILD_MAINT_OPTIONS = hardening=+all,-pie + %: dh $@ --parallel --with sphinxdoc --with pkgkde_symbolshelper diff -Nru owncloud-client-1.5.0+dfsg/debian/tests/make-tests owncloud-client-1.5.0+dfsg/debian/tests/make-tests --- owncloud-client-1.5.0+dfsg/debian/tests/make-tests 2013-12-30 23:20:02.0 +0100 +++ owncloud-client-1.5.0+dfsg/debian/tests/make-tests 2014-01-16 11:25:19.0 +0100 @@ -1,4 +1,4 @@ #! /bin/sh -mkdir config -XDG_CONFIG_HOME=$(ADTTMP)/config/ make tests -rm -r config +mkdir $ADTTMP/config +XDG_CONFIG_HOME=$ADTTMP/config/ make tests +rm -r $ADTTMP/config
Bug#735536: caff: infinite loop after signing a key
Package: signing-party Version: 1.1.4-1 Severity: important After I sign a key, caff enters an infinite loop printing: Could not import $FINGERPRINT into temporary gnupg. This makes caff completely unusable to me. My config file does not have any esoteric setting. Please let me know if there is any further information I can provide to debug this. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages signing-party depends on: ii gnupg 1.4.16-1 ii libc6 2.17-97 ii libclass-methodmaker-perl 2.19-1 ii libgnupg-interface-perl0.46-3 ii libmailtools-perl 2.12-1 ii libmime-tools-perl 5.505-1 ii libterm-readkey-perl 2.31-1 ii libtext-template-perl 1.46-1 ii perl 5.18.1-5 ii qprint 1.0.dfsg.2-2 Versions of packages signing-party recommends: ii dialog 1.2-20130928-1 ii exim4-daemon-light [mail-transport-agent] 4.82-3 ii libgd-gd2-noxpm-perl 1:2.46-2.1+b1 ii libintl-perl 1.23-1 ii libpaper-utils 1.1.24+nmu2 ii libtext-iconv-perl 1.7-5+b1 ii whiptail 0.52.15-3 Versions of packages signing-party suggests: ii imagemagick8:6.7.7.10-7 ii mutt 1.5.21-6.4 ii texlive-latex-recommended 2013.20131219-1 pn wipe none -- no debconf information -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#726763: Lid close and power button suspend not working
Hi All Just installed a new laptop with Jessie testing and found that suspend events do not trigger suspend action. Looking through the threads of the included bugs reports there seems to be a bit of an overlap so I've CC'ed you all in. System Information Manufacturer: Dell Inc. Product Name: Latitude E7240 amd64 Related Packages gnome-power-manager 3.8.2-1 acpi-support-base 0.141-2 acpid 1:2.0.20-1 systemd 204-6 pm-utils 1.4.1-13 upower0.9.23-2+b1 A bit of investigation found that the acpi-support-base scripts have a small problem, With the 'su' is in place a call to CheckPolicy from a non root account prompts for a password. The following patch fixed the password prompt and allowed suspend to initiate. --- /usr/share/acpi-support/policy-funcs.orig2014-01-16 19:24:48.828610060 +1100 +++ /usr/share/acpi-support/policy-funcs2014-01-16 19:25:31.169186162 +1100 @@ -44,7 +44,7 @@ test -r /proc/$p/environ || continue DBUS_SESS=$(grep -a -z DBUS_SESSION_BUS_ADDRESS= /proc/$p/environ || :) test $DBUS_SESS != || continue -su $(ps -o user= $p) -s /bin/sh -c $DBUS_SESS dbus-send --print-reply --dest='$DEST' '$DBUS_PATH' '$METHOD' +$DBUS_SESS dbus-send --print-reply --dest='$DEST' '$DBUS_PATH' '$METHOD' done } The pacth allows the lid to initiate and complete a suspend, the problem now is the power button issues a shutdown. gnome-tweak-tool suggests that the power button is set to suspend ( this could be a problem with my gnome profile though ). Darren -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735440: fusionforge-plugin-scmsvn: post-commit FS processing had error 'attempt to write a readonly database'
Hi. On Thu, Jan 16, 2014 at 09:42:53AM +0100, Thorsten Glaser wrote: On Wed, 15 Jan 2014, Olivier Berger wrote: This seems related to SVN's way to delegate tasks to sqlite, as per http://subversion.tigris.org/issues/show_bug.cgi?id=3437 I’ve fixed it like this: https://evolvis.org/pipermail/evolvis-platfrm-commits/2013-December/002728.html This commit takes care of all newly created repos; for existing ones, I’ve just added that line to fsfs.conf manually. (Actually, just scripted over /scmrepos/svn/*/ ofc.) Thanks for the pointer and patch. Are you suggesting that this wouldn't happen if we configured the SVN repos differently, i.e. is only a side effect ? Can you elaborate on the enable-rep-sharing = false ? Thanks in advance. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635659: libdbi{,-drivers} maintenance
László Böszörményi (GCS) g...@debian.org writes: I'm the maintainer of sqlite and sqlite3 and back then I was the only syslog-ng maintainer. Thus when I saw libdbi and libdbi-drivers is up for adoption, started working on them. It was March, last year. When almost finished, I put it down, I don't know the reason. Still, yesterday I've made the last bits. Both build fine with pbuilder. You can grab them[1][2] for testing. May I be their maintainers, adding whoever wants it as uploader or is there anyone else to continue the packaging? As I said before, the less work I need to do, the better, so since the update is all done and seems to be well, I'm happy. I think the lot of you are enough to be Uploaders, I don't need to be there. So as far as I'm concerned, go ahead and upload! -- |8] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732013: closed by Dominic Hargreaves d...@earth.li (Bug#732013: fixed in request-tracker4 4.0.18-1)
On Fri, Jan 03, 2014 at 05:02:44PM +0100, Bastian Blank wrote: There is still 4.2 missing. I've finished the import and made my changes available via git://anonscm.debian.org/git/users/waldi/request-tracker4.git I added the db upgrade stuff. There are four new perl packages needed: - libdate-extract-perl Bastian -- Bastian BlankDurchwahl: +49 21 61 / 46 43 -194 credativ GmbH, HRB Mönchengladbach 12080 Zentrale: +49 21 61 / 46 43 0 Hohenzollernstr. 133 Fax: +49 21 61 / 46 43 -100 D-41061 Mönchengladbach www: http://www.credativ.de Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#407047: -n option is documented, handled but not parsed
On Mon, 13 Jan 2014 19:26:36 +0100, Laurent Declercq l.decle...@nuxwin.com writes: Package: vlogger Version: 1.3-3.1 Followup-For: Bug #407047 Dear Maintainer, This bug affect all vlogger version in Debian and Ubuntu. It's so simple to fix this bug that I'm wondering what the maintainer of this package is doing... I'm doing well, thanks for asking. Apart from reading these kind of hatemail comments in Debian bug reports... :) In this package there are two other bugs since 1.3 which never went upstream: - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302176, - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645623. There are no new upstream releases since 1.3 to fix these issues, so even if we continue patching this in Debian, folks will have to duplicate the work in all other systems, like Fedora or BSDs. If you really want to help instead of just sending around opinionated rude emails to folks who work on stuff in their free time, you should take ownership of upstream maintenance of the code. Maybe you should email the guy who already started this 4 years ago: https://github.com/halfdan/vlogger (google search for vlogger github). Or you can just fork 1.3 and add these three bugfixes, call it 1.3.1 (or 1.4) and then ask the distributions to use your source code version. This is not to say that I'll not fix this by patching it in Debian. I'd just like to ask you that in the future you either: - ask _nicely_, - and/or be constructive and do your part of work where you can. There is also some debugging task to do: - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506246 Just have to replicate the environment on a machine and try it out with a lot of requests to see if we can reproduce at least. Or some little, easy issues: - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299796, - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299872, - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299873, - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569786, - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735195. Thank you. Cheers, Gergely -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661154: Bug#712050: aa-status does not show loaded profiles / aa-genprof is unusable
fixed 712050 2.8.0-1 fixed 661154 2.8.0-1 fixed 712050 2.8.0-5 fixed 661154 2.8.0-5 thanks On 15/01/14 19:24, intrigeri wrote: Control: tag -1 + moreinfo Carlos Alberto Lopez Perez wrote (15 Jan 2014 18:12:36 GMT) : I'm running apparmor=2.8.0-5 on Debian/sid AMD64 with Debian's 3.9 kernel. I notice you're running an ancient kernel (as far the current development of Debian is concerned). This is likely to cause the problem: IIRC the missing bits entered Linux at some point around 3.10 or 3.12. May you please retry with current sid's kernel? I have updated the kernel to 3.12 and the problem went away. Now all is working fine :) Thanks for the help, and sorry for the noise. Regards! signature.asc Description: OpenPGP digital signature
Bug#735116: apt-listbugs: […]/debian.rb:24:in `require': no such file to load -- debian_version (LoadError)
On Wed, Jan 15, 2014 at 09:48:57PM +0100, Francesco Poli wrote: On Wed, 15 Jan 2014 16:38:17 +0100 Antonio Terceiro wrote: On Wed, Jan 15, 2014 at 12:20:36AM +0100, Francesco Poli wrote: [...] As I have already said, I think there's one last aspect to fix: ruby1.8 should remove itself from the list of possible alternatives for /usr/bin/ruby. Dear ruby1.8 maintainers, do you agree? Hello Antonio, thanks for your reply. The only case I can think of where ruby1.8 stays as /usr/bin/ruby after ruby1.9.1 is installed is the case where the user explicitly requested ruby1.8 to be the default alternative. That is exactly the situation I was thinking about. As long as ruby1.8 stays installed and is manually configured as the system-wide alternative for /usr/bin/ruby, many programs requiring architecture-dependent Ruby libraries will fail to work. This is why I was suggesting that ruby1.8 should remove itself from the list of available alternatives for /usr/bin/ruby ... Also, doing this will not fix upgrades from wheezy sinde there will be no new ruby1.8 that does not provides the alternatives entry to upgrade to. This is true, but I was thinking about continuously upgraded unstable/testing systems... I indent to fix this situation by making `ruby` conflict with `ruby1.8`. What if both ruby1.8 and ruby1.9.1 are already installed and ruby1.8 was previously (manually) configured as the system-wide alternative for /usr/bin/ruby? Which package will pull in ruby, thus forcing the removal of ruby1.8? All packages depending on ruby | ruby-interpreter will be satisfied by ruby1.9.1, if I understand correctly... Is there a way to fix this scenario too? You are right! I will do another last upload of ruby1.8 dropping the alternatives entries ... :-/ -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#735538: Should suggest portaudio19-doc
Package: portaudio19-dev Version: 19+svn2021-2 Severity: wishlist It would be nice if portaudio19-dev could Suggest portaudio19-doc. Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735532: Pending fixes for bugs in the libanyevent-rabbitmq-perl package
tag 735532 + pending thanks Some bugs in the libanyevent-rabbitmq-perl package are closed in revision 20f8603fed151aafc71b85cf869bd69fd440bf35 in branch 'master' by Damyan Ivanov The full diff can be seen at http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libanyevent-rabbitmq-perl.git;a=commitdiff;h=20f8603 Commit message: fix symlink to fixed_amqp0-9-1.xml. Closes: #735532 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735537: autopkgtest fails on missing runit and stderr (with patch)
Package: r-bioc-xvector Version: 0.2.0-1 Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch trusty Hello, r-bioc-xvector's autopkgtest currently fails [1]: Error in BiocGenerics:::testPackage(XVector) : RUnit package not found After adding it (r-cran-runit), it fails because the test produces a lot of stderror. Attached debdiff fixes both, the autopkgtest succeeds now. Thanks for considering, Martin [1] https://jenkins.qa.ubuntu.com/job/trusty-adt-r-bioc-xvector/9/ARCH=i386,label=adt/console -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) diff -Nru r-bioc-xvector-0.2.0/debian/changelog r-bioc-xvector-0.2.0/debian/changelog --- r-bioc-xvector-0.2.0/debian/changelog 2013-11-05 17:23:01.0 +0100 +++ r-bioc-xvector-0.2.0/debian/changelog 2014-01-16 11:54:05.0 +0100 @@ -1,3 +1,10 @@ +r-bioc-xvector (0.2.0-1ubuntu1) trusty; urgency=medium + + * debian/tests/control: Add missing r-cran-runit test dependency, and allow +stderr output. + + -- Martin Pitt martin.p...@ubuntu.com Thu, 16 Jan 2014 11:47:25 +0100 + r-bioc-xvector (0.2.0-1) unstable; urgency=low * Initial release (closes: #728799) diff -Nru r-bioc-xvector-0.2.0/debian/tests/control r-bioc-xvector-0.2.0/debian/tests/control --- r-bioc-xvector-0.2.0/debian/tests/control 2013-11-05 09:42:06.0 +0100 +++ r-bioc-xvector-0.2.0/debian/tests/control 2014-01-16 11:53:56.0 +0100 @@ -1 +1,3 @@ Tests: run-unit-test +Depends: @, r-cran-runit +Restrictions: allow-stderr signature.asc Description: Digital signature
Bug#735539: RM: scilab-scimax -- ROM; Not maintained upstream
Package: ftp.debian.org Severity: normal Hello, Could you remove scilab-scimax from Debian? The package is not maintained upstream. There are several issues (including tracking of the maxima changes). I no longer have any interest in it. Thanks, Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735540: RM: scilab-overload -- ROM; Mainly useless
Package: ftp.debian.org Severity: normal Hello, Could you remove scilab-overload ? It is only used by scilab-scimax and I just asked for a removal of it (See bug #735539) Thanks, Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735541: Should suggest libfftw3-doc
Package: libfftw3-dev Version: 3.3.3-7 Severity: wishlist It would be nice if libfftw3-dev would Suggest: libfftw3-doc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735542: Should Suggest: python-pyparsing-doc
Package: python-pyparsing Version: 2.0.1+dfsg1-1 Severity: wishlist It would be nice if the package would Suggest: python-pyparsing-doc -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-pyparsing depends on: ii python 2.7.5-5 python-pyparsing recommends no packages. python-pyparsing suggests no packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735543: autopkgtest fails on missing runit, stderr, and test failures
Package: r-bioc-rtracklayer
Version: 1.22.0-1
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch trusty
Hello,
r-bioc-rtracklayer's autopkgtest currently fails [1]:
Error in BiocGenerics:::testPackage(rtracklayer) :
RUnit package not found
After adding it (r-cran-runit), it fails because the test produces a
lot of stderror. Attached debdiff fixes these two, but now the test
encounters some actual failures:
Error in seqlevels(seqinfo(x)) :
error in evaluating the argument 'x' in selecting a method for function
'seqlevels': Error in (function (classes, fdef, mtable) :
unable to find an inherited method for function 'seqinfo' for signature
'NULL'
Calls: seqinfo - Anonymous
(it repeats that a few times). I attach the full test log for
reference. Do you have an idea what's wrong there?
Thanks for considering,
Martin
[1]
https://jenkins.qa.ubuntu.com/job/trusty-adt-r-bioc-rtracklayer/6/ARCH=i386,label=adt/console
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
diff -Nru r-bioc-rtracklayer-1.22.0/debian/changelog
r-bioc-rtracklayer-1.22.0/debian/changelog
--- r-bioc-rtracklayer-1.22.0/debian/changelog 2013-12-28 01:59:48.0
+0100
+++ r-bioc-rtracklayer-1.22.0/debian/changelog 2014-01-16 12:06:12.0
+0100
@@ -1,3 +1,10 @@
+r-bioc-rtracklayer (1.22.0-1ubuntu1) UNRELEASED; urgency=medium
+
+ * debian/tests/control: Add missing r-cran-runit test dependency, and allow
+stderr output.
+
+ -- Martin Pitt martin.p...@ubuntu.com Thu, 16 Jan 2014 12:00:35 +0100
+
r-bioc-rtracklayer (1.22.0-1) unstable; urgency=low
* Initial release (closes: #733283).
diff -Nru r-bioc-rtracklayer-1.22.0/debian/tests/control
r-bioc-rtracklayer-1.22.0/debian/tests/control
--- r-bioc-rtracklayer-1.22.0/debian/tests/control 2013-11-05
09:42:06.0 +0100
+++ r-bioc-rtracklayer-1.22.0/debian/tests/control 2014-01-16
12:00:33.0 +0100
@@ -1 +1,3 @@
Tests: run-unit-test
+Depends: @, r-cran-runit
+Restrictions: allow-stderr
adt-run1: options: {'set_lang': False, 'timeout_install': None,
'binaries_fortests': 'auto', 'actions': [Action ubtree ubtree0 .],
'VSERVER_DUMMY': None, 'unbuilt_tree': None, 'summary':
'/home/ubuntu/adt-log/summary.log', 'timeout_test': None, 'binary': None,
'logfile': '/home/ubuntu/adt-log//log', 'timeout_short': None, 'vserver':
['adt-virt-null'], 'source': None, 'output_dir': '/home/ubuntu/adt-log/',
'debuglevel': 1, 'gainroot': None, 'timeout_build': None,
'built_binaries_filter': None, 'user': 'ubuntu', 'timeout_factor': 1.0,
'gnupghome': '~/.autopkgtest/gpg', 'quiet': False, 'timeout_copy': 1000,
'built_tree': None, 'binaries': 'auto', 'binaries_forbuilds': 'auto'};
timeouts: {'test': 1, 'copy': 1000, 'short': 100, 'build': 10,
'install': 3000}
adt-run1: ** init
adt-run1: ** start
adt-run: $ vserver: adt-virt-null
adt-run1: ** open, scratch=None
adt-run1: ** cmdl = ['sh', '-c', 'exec $@', 'x']
adt-run1: * initialising
adt-run1: * preparing for key generation
adt-run: $ genkey: sh -ec SCRIPT x /home/ubuntu/.autopkgtest/gpg
adt-run1: $
adt-run1: $ exec 2
adt-run1: $ cd $1
adt-run1: $ cat END key-gen-params
adt-run1: $ Key-Type: DSA
adt-run1: $ Key-Length: 1024
adt-run1: $ Key-Usage: sign
adt-run1: $ Name-Real: autopkgtest per-run key
adt-run1: $ Name-Comment: do not trust this key
adt-run1: $ Name-Email: autopkgt...@example.com
adt-run1: $ END
adt-run1: $ set -x
adt-run1: $ gpg --homedir=$1 --batch --gen-key key-gen-params
+ gpg --homedir=/home/ubuntu/.autopkgtest/gpg --batch --gen-key key-gen-params
gpg: keyring `/home/ubuntu/.autopkgtest/gpg/secring.gpg' created
gpg: keyring `/home/ubuntu/.autopkgtest/gpg/pubring.gpg' created
+..+++..+...+++.+.+..+++.+.++..+.+
gpg: /home/ubuntu/.autopkgtest/gpg/trustdb.gpg: trustdb created
gpg: key 6B36EE88 marked as ultimately trusted
adt-run1: * reset
adt-run: builds ...
adt-run: ubtree ubtree0
adt-run1: ** blame += arg:.
adt-run1: ** prepare1, modified=False, deps_processed=[], deps_new=[]
adt-run1: ** needs_reset, previously=False
adt-run: $ ubtree0-extract: sh -ec SCRIPT x
/tmp/adt-run.sMCbhA/ubtree0-build/tmpdir
/tmp/adt-run.sMCbhA/ubtree0-build/real-tree
adt-run1: $ exec 31 2
adt-run1: $ set -x
adt-run1: $ spec=$2
adt-run1: $ origpwd=/tmp/adt-run.sMCbhA/ubtree0-ubtree
adt-run1: $ mkdir -p /tmp/adt-run.sMCbhA/ubtree0-build
adt-run1: $ cd /tmp/adt-run.sMCbhA/ubtree0-build
adt-run1: $ chown ubuntu . ..
adt-run1: $ TMPDIR=$1
adt-run1: $ rm -rf -- $TMPDIR
adt-run1: $ export TMPDIR
adt-run1: $ su -s /bin/sh ubuntu -c 'mkdir -m 1777 -- $TMPDIR'
adt-run1: $
Bug#735545: Should also Suggest: gmp-doc
Package: libgmp-dev Version: 2:5.1.3+dfsg-1 Severity: wishlist The info documentation of GNU MP is located in gmp-doc. It would be nice if gmp-doc was also suggested by libgmp-dev. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735544: bluetooth: Incompatible conection with Windows Phone
Package: bluetooth Version: 4.99-2 Severity: normal Tags: patch Dear Maintainer, I have cell phone with Windows Phone version 7.10 and other with 8.0 version and i cant conect Windows Phone (all version) with my Debian 7 , i follow all step to conect (PIN, etc) but the fianl dont work nothing -- System Information: Debian Release: 7.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.utf8, LC_CTYPE=pt_BR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bluetooth depends on: ii bluez 4.99-2 Versions of packages bluetooth recommends: ii bluez-alsa 4.99-2 ii bluez-cups 4.99-2 ii bluez-gstreamer 4.99-2 bluetooth suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#407047: -n option is documented, handled but not parsed
Hello ; First, sorry for my previous report.. It was too much sarcastic for you as I see. Well, I can provide you a patch for all the bugs linked here. It's not a problem for me since we are using our own vlogger version for our control panel. Therefor, I would be happy to help as long you accept those patches. I can also add some improvements. For the record, when using the DBI tracker feature, Apache will fail miserably if the MySQL connnection is failing for any reason. Well, in our version I've revisited that part to make vlogger more safe. Eg, if the MySQL connection fail for any reason, vlogger will simply turn off that feature and continue its main job. Of course, an option should be added to let the admin decide whether or not the script should follow such a behavior. Another thing is about how vlogger is reading traffic data from mod_logio. A sample line should be added to warn the admin that the logio variables should be added just after the %v variable. Or even better, vlogger should simply search for those variables in the whole logFormat string instead of just make assumption on their position... As you can see, I'm ready to help you because I support Debian like you cannot ever imagine. The fact is that I suprised to see such bug reported since a while, which is not fixed yet. Even if the upstream author doesn't works much for a new release, it's not our problem. As long the vlogger is part of the Debian repository, it should be fixed. I know that you prefer warn the upstream author about such a bug and wait for a new release but this do not work as you can see. Thank you. -- Laurent Declercq iHMS/i-MSCP Project Lead -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735049: nvidia-support: Debconf prompts are misleading for NVIDIA Optimus users
On 2014-01-14 14:05, Vincent Cheng wrote: On Sun, Jan 12, 2014 at 4:15 AM, Andreas Beckmann a...@debian.org wrote: Or can we somehow detect Optimus systems and show an entirely different template there? Ack, probably a better idea than just assuming the user knows how to determine if their laptop uses optimus or not. How Canonical does this in their nvidia-prime package can be found at [1], which requires nothing more than lspci (not sure if we can just assume pciutils is available). That looks pretty easy, and having a dependency on pci-utils can be arranged (we might already have this). So what possible combinations should we handle: * no nvidia: no debconf * nvidia + intel + laptop: * bumblebee installed: no debconf * bumblebee not installed: new debconf recommending bumblebee * remaining nvidia: old debconf prompt: you need to configure manually Could you suggest some wording for the template? Also we should update README.Debian for Optimus systems - could you suggest some paragraphs? I guess we could check for optimus systems in a similar manner somewhere in postinst, and then just avoid triggering the nvidia-support/create-nvidia-conf template? create-nvidia-conf is not active, it was a test from me, but never activated. (First email ever using my @debian.org address, yippee! ;) Welcome! Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735291: Now chinese chars displayed with some chinese supported fonts
Hi, It was a scaling problem. Could you please test it again with the new file? Cheers, Balint 2014/1/16 张敬强 godfrey.pub...@gmail.com: Here's the screenshots xbmc_chs_arial_new.png (460 K) xbmc_chs_arial_orig.png (452 K) xbmc_chs_wqy_zenhei.png (487 K) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735440: fusionforge-plugin-scmsvn: post-commit FS processing had error 'attempt to write a readonly database'
On Thu, 16 Jan 2014, Olivier Berger wrote: Are you suggesting that this wouldn't happen if we configured the SVN repos differently, i.e. is only a side effect ? Can you elaborate on the enable-rep-sharing = false ? Basically, setting “enable-rep-sharing = false” disables that SQLite crap, AFAICT from my duckduckgoïng around. The true bug is in SQLite. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735546: autopkgtest fails on missing runit, stderr, and test failures
Package: r-bioc-iranges Version: 1.20.6-1 Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu ubuntu-patch trusty Hello, r-bioc-iranges's autopkgtest currently fails [1]: Error in BiocGenerics:::testPackage(IRanges) : RUnit package not found After adding it (r-cran-runit), it fails because the test produces a lot of stderror. Attached debdiff fixes these two, but now the test encounters some actual failures: Error in .CompressedIRangesList.range(x) : the XVector package is required by the range method for CompressedIRangesList objects (it repeats that a few times). Attached debdiff fixes all these issues, the autopkgtest succeeds now. Thanks for considering, Martin [1] https://jenkins.qa.ubuntu.com/job/trusty-adt-r-bioc-iranges/8/ARCH=i386,label=adt/console -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) diff -Nru r-bioc-iranges-1.20.6/debian/changelog r-bioc-iranges-1.20.6/debian/changelog --- r-bioc-iranges-1.20.6/debian/changelog 2013-12-03 11:42:42.0 +0100 +++ r-bioc-iranges-1.20.6/debian/changelog 2014-01-16 12:21:24.0 +0100 @@ -1,3 +1,10 @@ +r-bioc-iranges (1.20.6-1ubuntu1) trusty; urgency=medium + + * debian/tests/control: Add missing r-cran-runit and r-bioc-xvector test +dependencies, and allow stderr output. + + -- Martin Pitt martin.p...@ubuntu.com Thu, 16 Jan 2014 12:11:17 +0100 + r-bioc-iranges (1.20.6-1) unstable; urgency=low * New upstream version diff -Nru r-bioc-iranges-1.20.6/debian/tests/control r-bioc-iranges-1.20.6/debian/tests/control --- r-bioc-iranges-1.20.6/debian/tests/control 2013-11-05 09:42:06.0 +0100 +++ r-bioc-iranges-1.20.6/debian/tests/control 2014-01-16 12:16:28.0 +0100 @@ -1 +1,3 @@ Tests: run-unit-test +Depends: @, r-cran-runit, r-bioc-xvector +Restrictions: allow-stderr signature.asc Description: Digital signature
Bug#734401: postfix: debconf settings don't reflect main.cf if altered manually (e.g. relay_host)
On Mon, Jan 06, 2014 at 04:37:15PM -0500, Daniel Dickinson wrote: Setting relay_host in /etc/postfix/main.cf manual and the doing dpkg-reconfigured results in debconf setting (unless you set it back) the relay_host previously configured in debconf, not the one from main.cf through manual editing. Correct. How would you suggest that I determine which one was set last? lamont -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735547: autopkgtest fails on missing runit, stderr, and non-packaged reactome.db and hom.Hs.inp.db
Package: r-bioc-annotationdbi Version: 1.24.0-1 Hello, r-bioc-annotationdbi's autopkgtest currently fails [1]: Error in BiocGenerics:::testPackage(AnnotationDbi) : RUnit package not found After adding it (r-cran-runit), it fails because the test produces a lot of stderror. Attached debdiff fixes these, but the autopkgtest then fails with: Error in library(org.TguttataTestingSubset.eg.db) : there is no package called 'org.TguttataTestingSubset.eg.db' Loading required package: hom.Hs.inp.db Error in eval(expr, envir, enclos) : object 'hom.Hs.inp.db' not found In addition: Warning message: In library(package, lib.loc = lib.loc, character.only = TRUE, logical.return = TRUE, : there is no package called 'hom.Hs.inp.db' Loading required package: reactome.db Error in eval(expr, envir, enclos) : object 'reactome.db' not found In addition: Warning message: In library(package, lib.loc = lib.loc, character.only = TRUE, logical.return = TRUE, : there is no package called 'reactome.db' It seems these aren't packaged yet? Thanks for considering, Martin [1] https://jenkins.qa.ubuntu.com/job/trusty-adt-r-bioc-annotationdbi/1/ARCH=i386,label=adt/console -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) diff -Nru r-bioc-annotationdbi-1.24.0/debian/changelog r-bioc-annotationdbi-1.24.0/debian/changelog --- r-bioc-annotationdbi-1.24.0/debian/changelog2013-12-28 16:31:26.0 +0100 +++ r-bioc-annotationdbi-1.24.0/debian/changelog2014-01-16 12:25:12.0 +0100 @@ -1,3 +1,10 @@ +r-bioc-annotationdbi (1.24.0-1ubuntu1) UNRELEASED; urgency=medium + + * debian/tests/control: Add missing r-cran-runit test dependency, and allow +stderr output. + + -- Martin Pitt martin.p...@ubuntu.com Thu, 16 Jan 2014 12:24:53 +0100 + r-bioc-annotationdbi (1.24.0-1) unstable; urgency=medium * New upstream version diff -Nru r-bioc-annotationdbi-1.24.0/debian/tests/control r-bioc-annotationdbi-1.24.0/debian/tests/control --- r-bioc-annotationdbi-1.24.0/debian/tests/control2013-11-05 09:42:06.0 +0100 +++ r-bioc-annotationdbi-1.24.0/debian/tests/control2014-01-16 12:24:51.0 +0100 @@ -1 +1,3 @@ Tests: run-unit-test +Depends: @, r-cran-runit +Restrictions: allow-stderr signature.asc Description: Digital signature
Bug#722382: Updating the Ruby packaging policy for your package «libstfl-ruby»
severity 722382 serious
thanks
Hello stfl-Maintainer,
during Ruby Sprint in Paris, we have created an patch for your package to fit
the Ruby
Debian policy.
This patch removes Ruby 1.8 dependency and moves that package to gem2deb helper.
Pleas include the patch to fix your package. Otherwise we can't remove ruby 1.8
from the
archive.
Thanks,
Jonasdiff --git a/debian/control b/debian/control
index 02573f0..3a94ecb 100644
--- a/debian/control
+++ b/debian/control
@@ -1,10 +1,11 @@
Source: stfl
Priority: optional
Maintainer: Nico Golde n...@debian.org
-Build-Depends: debhelper (= 7), libncursesw5-dev, swig, python-all-dev (= 2.6.6-3~), ruby1.8, ruby1.8-dev, ruby1.9.1, ruby1.9.1-dev, spl-dev
+Build-Depends: debhelper (= 7), libncursesw5-dev, swig, python-all-dev (= 2.6.6-3~), spl-dev, gem2deb
Standards-Version: 3.9.2
Section: libdevel
X-Python-Version: all
+XS-Ruby-Versions: all
Vcs-Svn: svn://svn.debian.org/svn/collab-maint/deb-maint/stfl/trunk/
Vcs-Browser: http://svn.debian.org/wsvn/collab-maint/deb-maint/trunk/
Homepage: http://www.clifford.at/stfl/
@@ -50,36 +51,47 @@ Description: python bindings for the structured terminal forms language/library
.
This package contains the Python bindings to libstfl.
-Package: libstfl-ruby1.8
+Package: ruby-stfl
+XB-Ruby-Versions: ${ruby:Versions}
+X-DhRuby-Root: ruby
Section: ruby
Architecture: any
-Depends: ruby1.8, ${shlibs:Depends}, ${misc:Depends}
-Description: Ruby 1.8 bindings for the structured terminal forms language/library
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Replaces: libstfl-ruby1.8 ( 0.22-2~), libstfl-ruby1.9.1 ( 0.22-2~), libstfl-ruby ( 0.22-2~)
+Breaks: libstfl-ruby1.8 ( 0.22-2~), libstfl-ruby1.9.1 ( 0.22-2~), libstfl-ruby ( 0.22-2~)
+Provides: libstfl-ruby1.8, libstfl-ruby1.9.1, libstfl-ruby
+Description: Ruby bindings for the structured terminal forms language/library
stfl is a library which implements a curses-based widget set for text
terminals.
.
- This package contains the ruby1.8 bindings to libstfl.
+ This package contains the ruby bindings to libstfl.
+
+Package: libstfl-ruby1.8
+Section: oldlibs
+Priority: extra
+Architecture: all
+Depends: ${misc:Depends}, ruby-stfl
+Description: Transitional package libstfl-ruby1.8 for ruby-stfl
+ This is a transitional package libstfl-ruby1.8 to ease upgrades to the
+ ruby-stfl package. It can safely be removed.
Package: libstfl-ruby1.9.1
-Section: ruby
-Architecture: any
-Depends: ruby1.9.1, ${shlibs:Depends}, ${misc:Depends}
-Description: Ruby 1.9.1 bindings for the structured terminal forms language/library
- stfl is a library which implements a curses-based widget set for text
- terminals.
- .
- This package contains the ruby1.9 bindings to libstfl.
+Section: oldlibs
+Priority: extra
+Architecture: all
+Depends: ${misc:Depends}, ruby-stfl
+Description: Transitional package libstfl-ruby1.9.1 for ruby-stfl
+ This is a transitional package libstfl-ruby1.9.1 to ease upgrades to the
+ ruby-stfl package. It can safely be removed.
Package: libstfl-ruby
-Section: ruby
+Section: oldlibs
+Priority: extra
Architecture: all
-Depends: libstfl-ruby1.8, ${misc:Depends}
-Description: Ruby bindings for the structured terminal forms language/library
- stfl is a library which implements a curses-based widget set for text
- terminals.
- .
- This is a dependency package which depends on Debian's default Ruby version
- (currently 1.8.x).
+Depends: ${misc:Depends}, ruby-stfl
+Description: Transitional package libstfl-ruby for libstfl0
+ This is a transitional package libstfl-ruby to ease upgrades to the ruby-stfl
+ package. It can safely be removed.
Package: libstfl-spl
Section: devel
diff --git a/debian/libstfl-ruby1.8.dirs b/debian/libstfl-ruby1.8.dirs
deleted file mode 100644
index 709e902..000
--- a/debian/libstfl-ruby1.8.dirs
+++ /dev/null
@@ -1 +0,0 @@
-/usr/lib/ruby/1.8/x86_64-linux
diff --git a/debian/libstfl-ruby1.8.examples b/debian/libstfl-ruby1.8.examples
deleted file mode 100644
index 96a062f..000
--- a/debian/libstfl-ruby1.8.examples
+++ /dev/null
@@ -1 +0,0 @@
-ruby/example.rb
diff --git a/debian/libstfl-ruby1.8.install b/debian/libstfl-ruby1.8.install
deleted file mode 100644
index 19a6a02..000
--- a/debian/libstfl-ruby1.8.install
+++ /dev/null
@@ -1 +0,0 @@
-debian/tmp/usr/lib/ruby/1.8/*/stfl.so
diff --git a/debian/libstfl-ruby1.9.1.dirs b/debian/libstfl-ruby1.9.1.dirs
deleted file mode 100644
index 0cceba8..000
--- a/debian/libstfl-ruby1.9.1.dirs
+++ /dev/null
@@ -1 +0,0 @@
-/usr/lib/ruby/1.9.1/x86_64-linux
diff --git a/debian/libstfl-ruby1.9.1.examples b/debian/libstfl-ruby1.9.1.examples
deleted file mode 100644
index 96a062f..000
--- a/debian/libstfl-ruby1.9.1.examples
+++ /dev/null
@@ -1 +0,0 @@
-ruby/example.rb
diff --git a/debian/libstfl-ruby1.9.1.install b/debian/libstfl-ruby1.9.1.install
deleted file mode 100644
index e6aec7b..000
--- a/debian/libstfl-ruby1.9.1.install
+++ /dev/null
@@ -1 +0,0 @@
Bug#735440: fusionforge-plugin-scmsvn: post-commit FS processing had error 'attempt to write a readonly database'
Thorsten Glaser t.gla...@tarent.de writes: On Thu, 16 Jan 2014, Olivier Berger wrote: Are you suggesting that this wouldn't happen if we configured the SVN repos differently, i.e. is only a side effect ? Can you elaborate on the enable-rep-sharing = false ? Basically, setting “enable-rep-sharing = false” disables that SQLite crap, AFAICT from my duckduckgoïng around. OK, but it is unclear to me what exactly enable-rep-sharing is controlling... I haven't yet found a piece of docs explaining that :-/ Still searching... The true bug is in SQLite. OK. Hence #735446 ;-) Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635659: libdbi{,-drivers} maintenance
On Thu, Jan 16, 2014 at 3:11 PM, László Böszörményi (GCS) g...@debian.org wrote: Hi, I'm the maintainer of sqlite and sqlite3 and back then I was the only syslog-ng maintainer. Thus when I saw libdbi and libdbi-drivers is up for adoption, started working on them. It was March, last year. When almost finished, I put it down, I don't know the reason. Still, yesterday I've made the last bits. Both build fine with pbuilder. You can grab them[1][2] for testing. May I be their maintainers, adding whoever wants it as uploader or is there anyone else to continue the packaging? The only one change that pending, is the removal of sqlite and thus libdbd-sqlite will be gone with that. I have update libdbi[1],but libdbi-drivers[2] is not yet finished. [1] http://anonscm.debian.org/gitweb/?p=collab-maint/libdbi.git [2] http://anonscm.debian.org/gitweb/?p=collab-maint/libdbi-drivers.git Regards, Prach -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735549: pu: package nvidia-graphics-drivers/304.117-1
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu Hi, I'd like to update nvidia-graphics-drivers [non-free] in wheezy to fix CVE-2013-5987 - Unprivileged GPU access vulnerability (#735271) This requires switching to a new upstream release from the 304.xx legacy branch (wheezy currently has 304.88). The same upstream release is available in sid as nvidia-graphics-drivers-legacy-304xx, while sid already has a 319.xx release for nvidia-graphics-drivers. At the same time I merged some important bugfixes from sid. I intentionally want to use the version 304.117-1 for wheezy-pu to avoid getting a seriously inflated version number for the updated kernel module packages built from src:nvidia-graphics-modules. nvidia-graphics-modules will need a followup update for wheezy. Andreas Index: debian/libgl1-nvidia-alternatives-ia32.lintian-overrides === --- debian/libgl1-nvidia-alternatives-ia32.lintian-overrides (revision 3887) +++ debian/libgl1-nvidia-alternatives-ia32.lintian-overrides (revision 4631) @@ -1,2 +1,3 @@ # The diversions are placed here. package-contains-empty-directory usr/lib32/nvidia/diversions/ +non-multi-arch-lib-dir usr/lib32/ Index: debian/libcuda1.postinst.in === --- debian/libcuda1.postinst.in (revision 3887) +++ debian/libcuda1.postinst.in (revision 4631) @@ -1,6 +1,7 @@ #!/bin/sh set -e +. /usr/share/debconf/confmodule if [ $1 = configure ] then Index: debian/libgl1-nvidia-glx.lintian-overrides.in === --- debian/libgl1-nvidia-glx.lintian-overrides.in (revision 3887) +++ debian/libgl1-nvidia-glx.lintian-overrides.in (revision 4631) @@ -1,7 +1,8 @@ # The NVIDIA license does not allow any form of modification. +[!amd64]: binary-file-built-without-LFS-support +shlib-calls-exit [i386]: shlib-with-non-pic-code spelling-error-in-binary -shlib-calls-exit hardening-no-fortify-functions hardening-no-relro hardening-no-stackprotector @@ -12,8 +13,8 @@ # other libraries). shlibs-declares-dependency-on-other-package libgl1-mesa-glx | libgl1 -# This package is a strange special case since it overrides standard -# libraries and diverts them, so the package name won't ever be able to +# This package is a strange special case since it provides an alternative +# implementation of libGL.so.1, so the package name won't ever be able to # match the library names it provides. package-name-doesnt-match-sonames Index: debian/bug-script === --- debian/bug-script (revision 3887) +++ debian/bug-script (revision 4631) @@ -83,9 +83,9 @@ done echo Kernel modules: nvidia.ko -find /lib/modules -name nvidia.ko +find /lib/modules -name nvidia*.ko echo -find /lib/modules -name nvidia.ko | xargs -r modinfo | grep -v ^parm: +find /lib/modules -name nvidia*.ko | xargs -r modinfo | grep -v ^parm: echo exit 0 Index: debian/control === --- debian/control (revision 3887) +++ debian/control (revision 4631) @@ -5,8 +5,8 @@ Uploaders: Russ Allbery r...@debian.org, Andreas Beckmann a...@debian.org, -Vcs-Svn: svn://svn.debian.org/svn/pkg-nvidia/packages/nvidia-graphics-drivers/trunk -Vcs-Browser: http://svn.debian.org/wsvn/pkg-nvidia/packages/nvidia-graphics-drivers/ +Vcs-Svn: svn://anonscm.debian.org/pkg-nvidia/packages/nvidia-graphics-drivers/trunk +Vcs-Browser: http://anonscm.debian.org/viewvc/pkg-nvidia/packages/nvidia-graphics-drivers/ Build-Depends: debhelper (= 9), bzip2, Index: debian/libxvmcnvidia1.lintian-overrides.in === --- debian/libxvmcnvidia1.lintian-overrides.in (revision 3887) +++ debian/libxvmcnvidia1.lintian-overrides.in (revision 4631) @@ -1,4 +1,5 @@ # The NVIDIA license does not allow any form of modification. +[!amd64]: binary-file-built-without-LFS-support [i386]: shlib-with-non-pic-code hardening-no-fortify-functions hardening-no-relro Index: debian/nvidia-opencl-icd.lintian-overrides.in === --- debian/nvidia-opencl-icd.lintian-overrides.in (revision 3887) +++ debian/nvidia-opencl-icd.lintian-overrides.in (revision 4631) @@ -1,6 +1,8 @@ # The NVIDIA license does not allow any form of modification. +[!amd64]: binary-file-built-without-LFS-support shlib-with-executable-stack [i386]: shlib-with-non-pic-code +[i386]: spelling-error-in-binary unstripped-binary-or-object hardening-no-fortify-functions hardening-no-relro Index: debian/libgl1-nvidia-glx.postinst.in === --- debian/libgl1-nvidia-glx.postinst.in (revision 3887) +++ debian/libgl1-nvidia-glx.postinst.in (revision 4631) @@ -1,6 +1,7 @@
Bug#735548: autopkgtest fails on missing runit and stderr, missing TxDb.Hsapiens.UCSC.hg19.knownGene
Package: r-bioc-genomicfeatures
Version: 1.14.2-1
Hello,
r-bioc-genomicfeatures' autopkgtest currently fails [1]:
Error in BiocGenerics:::testPackage(GenomicFeatures) :
RUnit package not found
After adding it (r-cran-runit), it fails because the test produces a
lot of stderror.
Attached debdiff fixes both, but the autopkgtest now fails on missing
packages:
GenomicFeatures RUnit Tests - 29 test functions, 5 errors, 0 failures
ERROR in
/usr/lib/R/site-library/GenomicFeatures/unitTests/test_TranscriptDb_seqinfo.R:
Error while sourcing
/usr/lib/R/site-library/GenomicFeatures/unitTests/test_TranscriptDb_seqinfo.R :
Error in library(TxDb.Hsapiens.UCSC.hg19.knownGene) :
there is no package called 'TxDb.Hsapiens.UCSC.hg19.knownGene'
(this repeats a number of times). It seems this isn't packaged? The
closest match seems to be r-bioc-bsgenome [2] but it doesn't have
exactly this. I tried adding it as a test dependency, but it didn't
help much. I attach the full test log with this additional dependency
(which isn't in the debdiff, though).
Thanks for considering,
Martin
[1]
https://jenkins.qa.ubuntu.com/job/trusty-adt-r-bioc-genomicfeatures/1/ARCH=i386,label=adt/console
[2] http://packages.debian.org/sid/i386/r-bioc-bsgenome/filelist
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
adt-run1: options: {'set_lang': False, 'timeout_install': None,
'binaries_fortests': 'auto', 'actions': [Action ubtree ubtree0 .],
'VSERVER_DUMMY': None, 'unbuilt_tree': None, 'summary':
'/home/ubuntu/adt-log/summary.log', 'timeout_test': None, 'binary': None,
'logfile': '/home/ubuntu/adt-log//log', 'timeout_short': None, 'vserver':
['adt-virt-null'], 'source': None, 'output_dir': '/home/ubuntu/adt-log/',
'debuglevel': 1, 'gainroot': None, 'timeout_build': None,
'built_binaries_filter': None, 'user': 'ubuntu', 'timeout_factor': 1.0,
'gnupghome': '~/.autopkgtest/gpg', 'quiet': False, 'timeout_copy': 1000,
'built_tree': None, 'binaries': 'auto', 'binaries_forbuilds': 'auto'};
timeouts: {'test': 1, 'copy': 1000, 'short': 100, 'build': 10,
'install': 3000}
adt-run1: ** init
adt-run1: ** start
adt-run: $ vserver: adt-virt-null
adt-run1: ** open, scratch=None
adt-run1: ** cmdl = ['sh', '-c', 'exec $@', 'x']
adt-run1: * initialising
adt-run1: * preparing for key generation
adt-run: $ genkey: sh -ec SCRIPT x /home/ubuntu/.autopkgtest/gpg
adt-run1: $
adt-run1: $ exec 2
adt-run1: $ cd $1
adt-run1: $ cat END key-gen-params
adt-run1: $ Key-Type: DSA
adt-run1: $ Key-Length: 1024
adt-run1: $ Key-Usage: sign
adt-run1: $ Name-Real: autopkgtest per-run key
adt-run1: $ Name-Comment: do not trust this key
adt-run1: $ Name-Email: autopkgt...@example.com
adt-run1: $ END
adt-run1: $ set -x
adt-run1: $ gpg --homedir=$1 --batch --gen-key key-gen-params
+ gpg --homedir=/home/ubuntu/.autopkgtest/gpg --batch --gen-key key-gen-params
gpg: keyring `/home/ubuntu/.autopkgtest/gpg/secring.gpg' created
gpg: keyring `/home/ubuntu/.autopkgtest/gpg/pubring.gpg' created
.++.+..+++.++.+++.++.
gpg: /home/ubuntu/.autopkgtest/gpg/trustdb.gpg: trustdb created
gpg: key 3318799D marked as ultimately trusted
adt-run1: * reset
adt-run: builds ...
adt-run: ubtree ubtree0
adt-run1: ** blame += arg:.
adt-run1: ** prepare1, modified=False, deps_processed=[], deps_new=[]
adt-run1: ** needs_reset, previously=False
adt-run: $ ubtree0-extract: sh -ec SCRIPT x
/tmp/adt-run.zUMSTM/ubtree0-build/tmpdir
/tmp/adt-run.zUMSTM/ubtree0-build/real-tree
adt-run1: $ exec 31 2
adt-run1: $ set -x
adt-run1: $ spec=$2
adt-run1: $ origpwd=/tmp/adt-run.zUMSTM/ubtree0-ubtree
adt-run1: $ mkdir -p /tmp/adt-run.zUMSTM/ubtree0-build
adt-run1: $ cd /tmp/adt-run.zUMSTM/ubtree0-build
adt-run1: $ chown ubuntu . ..
adt-run1: $ TMPDIR=$1
adt-run1: $ rm -rf -- $TMPDIR
adt-run1: $ export TMPDIR
adt-run1: $ su -s /bin/sh ubuntu -c 'mkdir -m 1777 -- $TMPDIR'
adt-run1: $ spec=$spec origpwd=$origpwd su -s /bin/sh ubuntu -c '
adt-run1: $ rm -rf $spec
adt-run1: $ mkdir $spec
adt-run1: $ cp -rP --preserve=timestamps,links -- $origpwd/. $spec/.
adt-run1: $ '
adt-run1: $ cd [a-z0-9]*-*/.
adt-run1: $ pwd 3
adt-run1: $ set +e; test -f debian/tests/control; echo $? 3
+ spec=/tmp/adt-run.zUMSTM/ubtree0-build/real-tree
+ origpwd=/tmp/adt-run.zUMSTM/ubtree0-ubtree
+ mkdir -p /tmp/adt-run.zUMSTM/ubtree0-build
+ cd /tmp/adt-run.zUMSTM/ubtree0-build
+ chown ubuntu . ..
+ TMPDIR=/tmp/adt-run.zUMSTM/ubtree0-build/tmpdir
+ rm -rf -- /tmp/adt-run.zUMSTM/ubtree0-build/tmpdir
+ export TMPDIR
+ su -s /bin/sh ubuntu -c mkdir -m 1777 -- $TMPDIR
+
Bug#735550: RFS: proot/3.2.2-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package proot * Package name: proot Version : 3.2.2-1 Upstream Author : Cédric Vincent cedric.vinc...@st.com * URL : http://proot.me * License : GPL Section : utils It builds those binary packages: proot - emulate chroot, bind mount and binfmt_misc for non-root users To access further information about this package, please visit the following URL: http://mentors.debian.net/package/proot Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/proot/proot_3.2.2-1.dsc More information about proot can be obtained from http://proot.me. Changes since the last upload: * Only build for supported architectures (closes: #733247) * Upgrade to latest PRoot version (Closes: #730363) * Fix copyright holders * Build with hardening * Print the full command line while building * Add a watch file Regards, -- Rémi Duraffort http://ivoire.dinauz.org/blog -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722382: Updating the Ruby packaging policy for your package «libstfl-ruby»
Hi, * Jonas Genannt jonas.gena...@capi2name.de [2014-01-16 12:39]: Hello stfl-Maintainer, during Ruby Sprint in Paris, we have created an patch for your package to fit the Ruby Debian policy. This patch removes Ruby 1.8 dependency and moves that package to gem2deb helper. Pleas include the patch to fix your package. Otherwise we can't remove ruby 1.8 from the archive. Will include in the next upload. Thanks! Nico -- Nico Golde - XMPP: n...@jabber.ccc.de - GPG: 0xA0A0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735440: fusionforge-plugin-scmsvn: post-commit FS processing had error 'attempt to write a readonly database'
Hi. Olivier Berger olivier.ber...@telecom-sudparis.eu writes: Thorsten Glaser t.gla...@tarent.de writes: On Thu, 16 Jan 2014, Olivier Berger wrote: Are you suggesting that this wouldn't happen if we configured the SVN repos differently, i.e. is only a side effect ? Can you elaborate on the enable-rep-sharing = false ? Basically, setting “enable-rep-sharing = false” disables that SQLite crap, AFAICT from my duckduckgoïng around. OK, but it is unclear to me what exactly enable-rep-sharing is controlling... I haven't yet found a piece of docs explaining that :-/ Still searching... Responding to myself as I have finally found relevant information, I think : - http://subversion.apache.org/docs/release-notes/1.6.html#rep-sharing Sharing multiple common representations (issue 2286, server) When using many branches and merging between them often, it is common to have files with similar lines of history which contain the exact same content. In the past, Subversion has stored these files as deltas against previous versions of the file. Subversion 1.6 will now use existing representations in the filesystem for duplicate storage. Depending on the size of the repository, and the degree of branching and merging, this can cause an up to 20% space reduction for Berkeley DB repositories and a 15% reduction for FSFS repositories. - http://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_fs_fs/structure When representation sharing is enabled, the filesystem tracks representation checksum and location mappings using a SQLite database in rep-cache.db. The database has a single table, which stores the sha1 hash text as the primary key, mapped to the representation revision, offset, size and expanded size. This file is only consulted during writes and never during reads. Consequently, it is not required, and may be removed at an abritrary time, with the subsequent loss of rep-sharing capabilities for revisions written thereafter. You just had to figure out that rep-sharing stands for representation sharing and not repo sharing ;-) So what I understand is that the default is representation sharing is activated (even if the fsfs.conf isn't clear about the default value, but there are bug reports upstream on that particular issue, I think), which is supposed to be a good thing disk-space wise, in which case, the DB file ought to be used for performance reason, unless it becomes too big and creates other issues otherwise... So... I'm not sure the right fix is to set enable-rep-sharing to false, but I'd probably prefer to touch an empty file with proper rights before creating the repo, until svn fixes the issue with its sqlite sub-component. Hope this makes sense. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#732937: dpkg: fails somewhat regularly on kfreebsd-amd64
On 16/01/2014 07:42, Michael Vogt wrote: What is the best way for me to reproduce this? I don't have a kfreebsd system right now - is installing one from a current installer image in kvm the quickest way (I assume so)? The development version of D-I for kfreebsd tends to break a lot more often than the linux counterpart (just recently it had one major issue caused by grub and another one by zfsutils). If you just want a sid system to debug apt, it's probably quicker to install wheezy and dist-upgrade. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: Bits from linux.conf.au
On 16/01/14 06:09, Martin Pitt wrote: There's no practical way to drop sysv of course, at least as long as we have non-Linux ports. If maintainers are particularly keen to drop support for SysV, that encourages porters to go with either OpenRC or a port of Upstart. Then you could drop SysV support as long as your package has a native init definition for whichever of those is used on ports. Porters could test or even write that for you. On 16/01/14 09:03, Anthony Towns wrote: It's reasonable to semi-continuously test installation scripts for thousands of packages -- that's what piuparts does The modern init systems likely have a clearer idea of whether the daemon started successfully or not, so this seems to make sense. If tests can be run on every port, that would also catch daemon startup bugs that are not even due to the init script. A really nice dashboard may also show a diff of changes in the default init script, to keep track of when the others might need updating. Maybe that's similar to how translators' work is done. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700841: (no subject)
Control: fixed -1 2012.12.30 Control: found -1 2012.01.08 Fixed in testing but not stable. Will need updating soon too by the looks of things. gpg --list-keys --keyring /usr/share/keyrings/debian-ports-archive-keyring.gpg --no-default-keyring /usr/share/keyrings/debian-ports-archive-keyring.gpg pub 4096R/A92F9FF4 2012-01-08 [expired: 2013-01-31] uid Debian Ports Archive Automatic Signing Key (2012) ftpmas...@debian-ports.org pub 4096R/2FF7A9F4 2012-12-30 [expires: 2014-01-31] uid Debian Ports Archive Automatic Signing Key (2013) ftpmas...@debian-ports.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725758: LedgerSMB 1.3.x and Apache v2.4?
On Thu, Jan 9, 2014 at 3:57 AM, Robert J. Clay rjc...@gmail.com wrote: On Tue, Jan 7, 2014 at 4:51 AM, Chris Travers chris.trav...@gmail.com wrote: Speaking of which, anything I can do to help with the Apache 2.4 issues? Well, I don't know how many people are already using LedgerSMB v1.3.x with Apache v2.4, but it seems to me that there will be; had you all considered splitting off the 1.3.x LedgerSMB ledger-httpd.conf file into Apache version specific files, like has already been done for LedgersSMB v1.4? In the mean time, I'm using a 2.4 compatible version of the file kept in packaging directory; still need to get that to work, though... I am now working on the packaging for 1.3.36; need to get it working for both upgrades and and new installs... I will confess it is somewhat difficult as I am currently running Apache 2.2, and haven't had time to upgrade my dev environment. Something I've found that seems to be true, at least if the access_compat module is available (like it appears to be in Debian Testing); if the v2.2 compatible file is left in conf.d and no 2.2 compatible version is enabled in conf-available, it does appear to work. This I found on a test system that was updated from wheezy to jessie, which also updated the ledgersmb install to 1.3.25. As I've not yet been able to get a working v2.4 compatible ledgersmb httpd config file; I don't know if such a file was enabled, if that automatically overrides such an existing v2.2 compatible file.. -- Robert J. Clay rjc...@gmail.com j...@rocasa.us -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724469: Fwd: Bug#724469: FTBFS on all big-endian architectures
Hi, since 0.015, some of the Glib-Object-Introspection tests fail on all big-endian architectures supported by Debian. I am attaching the original bug report. More info can be found at http://bugs.debian.org/724469, including a patch that apparently fixes the problem on 32-bit big endian architectures: http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=12;filename=gperl-i11n-invoke-c_big_endian_32.patch;att=1;bug=724469 The patch author says that more work will be needed for 64-bit big endian architectures. Is upstream interested in supporting these architectures, or is the ball in the Debian porters' court? ---BeginMessage--- Package: libglib-object-introspection-perl Version: 0.015-1 Severity: important libglib-object-introspection-perl fails to build on all big-endian architectures with the following test failures: # Failed test at t/00-basic-types.t line 15. # got: '-1' # expected: '-127' # Failed test at t/00-basic-types.t line 16. # got: '0' # expected: '255' # Failed test at t/00-basic-types.t line 17. # got: '-1' # expected: '-32767' # Failed test at t/00-basic-types.t line 18. # got: '0' # expected: '65535' # Looks like you failed 4 tests of 34. t/00-basic-types.t Dubious, test returned 4 (wstat 1024, 0x400) Failed 4/34 subtests # Failed test at t/arg-checks.t line 11. # got: '-1' # expected: '-127' # Failed test at t/arg-checks.t line 21. # got: '0' # expected: '127' # Looks like you failed 2 tests of 5. t/arg-checks.t Dubious, test returned 2 (wstat 512, 0x200) Failed 2/5 subtests Given both the nature of the results of the tests, and the selection of architectures where the failures happen, it's fairly clearly an endian issue, though I haven't looked into where. More logs can be found at: https://buildd.debian.org/status/package.php?p=libglib-object-introspection-perl ... Adam -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11.0-8-generic (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- -- intrigeri
Bug#735291: Now chinese chars displayed with some chinese supported fonts
It works. Thanks 在 2014年1月16日 星期四 12:19:40，您写道： Hi, It was a scaling problem. Could you please test it again with the new file? Cheers, Balint 2014/1/16 张敬强 godfrey.pub...@gmail.com: Here's the screenshots xbmc_chs_arial_new.png (460 K) xbmc_chs_arial_orig.png (452 K) xbmc_chs_wqy_zenhei.png (487 K)
Bug#735552: debian-ports-archive-keyring is out-of-date
Package: debian-ports-archive-keyring Version: 2012.12.30 Found: 2012.01.0 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu trusty It would appear that debian-ports-archive-keyring is out-of-date and needs updating: debootstrap --arch sh4 --foreign --include=locales,localepurge,git,build-essential,htop,bash-completion sid debian-sh4-sid2 http://ftp.debian-ports.org/debian I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature E: Release signed by unknown key (key id 1C466F272FF7A9F4) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735551: nginx does not start at installation
Package: nginx Version: 1.4.4-4 Severity: minor Dear Maintainer, nginx does not start at the moment of installation, like all the servers do on Debian. Bye -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.10-3-amd64 (SMP w/8 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nginx depends on: ii nginx-full 1.4.4-4 nginx recommends no packages. nginx suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730437: network-manager: Still getting this in 0.9.8.8
Package: network-manager Version: 0.9.8.8-3 Followup-For: Bug #730437 Dear Maintainer, I am still unable to launch the program: ~# /usr/sbin/NetworkManager --no-daemon NetworkManager[18781]: info NetworkManager (version 0.9.8.8) is starting... NetworkManager[18781]: info Read config file /etc/NetworkManager/NetworkManager.conf NetworkManager[18781]: info WEXT support is enabled Error getting login monitor: -2NetworkManager[18781]:SCPlugin-Ifupdown: init! NetworkManager[18781]:SCPlugin-Ifupdown: update_system_hostname NetworkManager[18781]:SCPluginIfupdown: guessed connection type (eth0) = 802-3-ethernet NetworkManager[18781]:SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e NetworkManager[18781]:SCPlugin-Ifupdown: addresses count: 1 NetworkManager[18781]:SCPlugin-Ifupdown: No dns-nameserver configured in /etc/network/interfaces NetworkManager[18781]:SCPlugin-Ifupdown: adding eth0 to connections NetworkManager[18781]:SCPlugin-Ifupdown: adding iface eth0 to eni_ifaces NetworkManager[18781]:SCPluginIfupdown: guessed connection type (wlan0) = 802-11-wireless NetworkManager[18781]:SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:wlan0, type:802-11-wireless, id:Ifupdown (wlan0), uuid: 5391eba4-6426-faca-338e-5828034ff9d1 NetworkManager[18781]:SCPlugin-Ifupdown: update wireless settings (wlan0). NetworkManager[18781]:SCPlugin-Ifupdown: setting wpa ssid = 7 NetworkManager[18781]:SCPlugin-Ifupdown: update wireless security settings (wlan0). NetworkManager[18781]:SCPlugin-Ifupdown: setting wpa security key: psk=omitted NetworkManager[18781]:SCPlugin-Ifupdown: addresses count: 1 NetworkManager[18781]:SCPlugin-Ifupdown: No dns-nameserver configured in /etc/network/interfaces NetworkManager[18781]: nm-ifupdown-connection.c.100 - invalid connection read from /etc/network/interfaces: (2) key-mgmt NetworkManager[18781]:SCPlugin-Ifupdown: adding iface wlan0 to eni_ifaces NetworkManager[18781]:SCPluginIfupdown: guessed connection type (tap0) = 802-3-ethernet NetworkManager[18781]:SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:tap0, type:802-3-ethernet, id:Ifupdown (tap0), uuid: 8e977656-6fc5-6b10-bff2-f63f618d213d NetworkManager[18781]:SCPlugin-Ifupdown: addresses count: 1 NetworkManager[18781]:SCPlugin-Ifupdown: No dns-nameserver configured in /etc/network/interfaces NetworkManager[18781]:SCPlugin-Ifupdown: adding tap0 to connections NetworkManager[18781]:SCPlugin-Ifupdown: adding iface tap0 to eni_ifaces NetworkManager[18781]:SCPlugin-Ifupdown: autoconnect NetworkManager[18781]:SCPluginIfupdown: management mode: unmanaged NetworkManager[18781]:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.8/net/wwan0, iface: wwan0) NetworkManager[18781]:SCPlugin-Ifupdown: device added (path: /sys/devices/pci:00/:00:14.0/usb3/3-4/3-4:1.8/net/wwan0, iface: wwan0): no ifupdown configuration found. NetworkManager[18781]:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:19.0/net/eth0, iface: eth0) NetworkManager[18781]:SCPluginIfupdown: locking wired connection setting NetworkManager[18781]:SCPlugin-Ifupdown: devices added (path: /sys/devices/pci:00/:00:1c.1/:03:00.0/net/wlan0, iface: wlan0) NetworkManager[18781]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo) NetworkManager[18781]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. NetworkManager[18781]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/tap0, iface: tap0) NetworkManager[18781]:SCPluginIfupdown: locking wired connection setting NetworkManager[18781]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/tun0, iface: tun0) NetworkManager[18781]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found. NetworkManager[18781]:SCPlugin-Ifupdown: end _init. NetworkManager[18781]: info Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. NetworkManager[18781]: info Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager[18781]:Ifupdown: get unmanaged devices count: 3 NetworkManager[18781]:SCPlugin-Ifupdown: (20326560) ... get_connections. NetworkManager[18781]:SCPlugin-Ifupdown: (20326560) ... get_connections (managed=false): return empty list. NetworkManager[18781]:keyfile: parsing velcom ... NetworkManager[18781]:keyfile: read connection 'velcom' NetworkManager[18781]:keyfile: parsing DTAC ... NetworkManager[18781]:keyfile: read connection 'DTAC'
Bug#731922: open-font-design-toolkit: hardcoded depends on shared libraries
Hi, your package has a number of hardcoded dependencies on shared library packages. That doesn't seem like a reasonable thing to do in an arch:all package. Shared libraries should be pulled in by things linking against them, so there shouldn't be a need to hardcode these dependencies in a metapackage. Agreed. And this package depends on fontforge, that's dependency is Depends: fontforge-common (= 20120731.b-5), libfontforge1 (= 20120731.b-5), libgdraw4 (= 20120731.b-5), libc6 (= 2.14), libcairo2 (= 1.2.4), libfontconfig1 (= 2.11), libfreetype6 (= 2.2.1), libgif4 (= 4.1.4), libglib2.0-0 (= 2. 12.0), libice6 (= 1:1.0.0), libjpeg8 (= 8c), libpango-1.0-0 (= 1.14.0), libpangocairo-1.0-0 (= 1.14.0), libpangoft2-1.0-0 (= 1.14.0), libpangoxft-1.0-0 (= 1.14.0), libpng12-0 (= 1.2.13-4), libpython2.7 (= 2.7), libsm6, libspiro0 (= 20071029), libtiff5 (= 4.0.3), libuninameslist0, libx11-6, libxft2 ( 2.1.1), libxml2 (= 2.6.27), zlib1g (= 1:1.1.4) fontforge already pulls libsipro0, libfreetype6, libjpeg8, libgif4, libuninameslist0 and libtiff5. So, we don't need those hardcoded one. libfont-ttf-perl is just perl library so probably it's okay. libotf0 can switch to libotf-bin, and once liblais0 can be dropped. I'll upload it. -- Regards, Hideki Yamane henrich @ debian.or.jp/org http://wiki.debian.org/HidekiYamane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735553: packages.debian.org: unreleased, debports architectures make packages.d.o confusing
Package: www.debian.org Severity: normal Hi! packages.debian.org lists packages from a variety of architectures that aren't actually in Debian. packages.debian.org has three main audiences who come to it to look for information: * end-users -- they aren't using debports ports so they don't want to see this information * debian develoeprs -- they are more likely to look at packages.qa.d.o for information about packages and porting * debports porters -- they have much better tools than packages.d.o to assess their porting efforts The current infrastructure sets up packages.d.o as being for end users while packages.qa.d.o is for developers. Information about work-in-progress architectures that aren't even available from the Debian project is at best irrelevant to the end-user; unfortunately, is actively confusing in many cases. A FAQ in #debian has become (in infinte variants): Hi! I'm trying to install postgresql-9.0. packages.debian.org/sid/postgresql-9.0 lists it but apt can't find it. http://packages.debian.org/sid/tspc lists a binary package but no source, isn't Debian distributing the source? Now if you look at these pages for long enough, you eventually find, down the bottom in the last place you will look in the download links that there are only download links for m68k. But because you know that Debian has a sophisticated package management system and you always use apt to install packages because that's what you've been trained to do, you don't even look at download links and you remain confused... The other common variation on this theme is where a package has been removed from Debian but has not been decrufted from debports yet. Even for those not confused by the stray entries for packages that don't exist any more, these entries are effectively noise that makes the site less useful. If the work-in-progress, dead, being-revived or otherwise progressing well ports from debports were keeping up with all packages in the archive, this wouldn't be a problem but then again, if these ports were keeping up, they could be official ports in any case. Concretely, my suggestion is: (a) remove architectures from packages.d.o that are not official Debian architectures. not in dak, not looked after by our ftp-masters, not considered in architecture qualification by the release team, not available from ftp.d.o would all be reasonable definitions of official Debian architectures here (and give the same set of architectures). (b) if those working on debports architectures need Debian maintainers to see information about the status of the packages and would thus be sorry to see this information disappear from view, then let's clone this bug to qa.debian.org proposing to include it in the packages.qa.d.o pages where the developer group is more likely to look for it anyway. It would be nice if this FAQ didn't need to be answered on a ~daily basis and if packages.d.o could become more useful to end-users. thanks Stuart -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735554: screen: Screen owner name too long - sorry error when attaching to multiuser screen
Package: screen Version: 4.1.0~20120320gitdb59704-7 Severity: normal Tags: patch Dear Maintainer, when attaching to a screen that is owned by a different user with a long name ( 20 characters), I get the following error: host ~ # screen -x this-is-a-very-long-username/ Screen owner name too long - sorry. screen originally had a limit of 20 characters for usernames and wouldn't work at all if your username was longer, but this was mostly fixed in a Debian patch. Apparently the patch overlooked this specific situation so that this issue still occurs. I've attached a patch that resolved this issue for me. -- System Information: Debian Release: 7.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.10-0.bpo.3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages screen depends on: ii dpkg 1.16.12 ii install-info 4.13a.dfsg.1-10 ii libc6 2.13-38 ii libncurses5 5.9-10 ii libpam0g 1.1.3-7.1 ii libtinfo5 5.9-10 screen recommends no packages. Versions of packages screen suggests: pn iselect | screenie | byobu none -- Configuration Files: /etc/screenrc changed [not included] -- debconf information excluded Description: fix Screen owner name too long - sorry error The patch 49long-usernames.patch increases the maximum user name length that screen supports from 20 to 50 characters. Unfortunately, the limit still applies when trying to attach to a multiuser screen: . host ~ # screen -x verylongusername/ Screen owner name too long - sorry. . This patch raises the length limit for owner names too. . screen (4.1.0~20120320gitdb59704-7) unstable; urgency=low . * Extend 60-644788-screen-4.1.0-4.0.3-interoperability.patch: + Add support for detaching (Closes: #684342) + Document remaining issues in debian/NEWS Author: Axel Beckert a...@debian.org Bug-Debian: http://bugs.debian.org/684342 --- The information above should follow the Patch Tagging Guidelines, please checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here are templates for supplementary fields that you might want to add: Author: Martin von Wittich martin.von.witt...@iserv.eu Last-Update: 2014-01-16 --- screen-4.1.0~20120320gitdb59704.orig/screen.c +++ screen-4.1.0~20120320gitdb59704/screen.c @@ -1000,7 +1000,7 @@ char **av; if (strlen(LoginName) MAX_USERNAME_LEN) Panic(0, LoginName too long - sorry.); #ifdef MULTIUSER - if (multi strlen(multi) 20) + if (multi strlen(multi) MAX_USERNAME_LEN) Panic(0, Screen owner name too long - sorry.); #endif if (strlen(home) MAXPATHLEN - 25)
Bug#733733: wrong complaint about missing python b-d when python*:any is given.
Package: lintian Version: 2.5.21 Followup-For: Bug #733733 lintian is confused by additional :any added to the package name of dependency check logic. Please allow additional :any to be added. Here is my case: After realizing python3-all is one of the few new M-A:allowed packages, I put python3-all:any as build dependency for my arch:all package which does not have any fancy architecture specific bits, lintian started to complaining as: E: debmake source: missing-build-dependency-for-dh-addon python3 = python3 | python3-all | python3-dev | python3-all-dev N: N:The source package appears to be using a dh addon but doesn't build N:depend on the package that actually provides it. If it uses it, it must N:build depend on it. N: N:Severity: important, Certainty: possible N: N:Check: debhelper, Type: source N: E: debmake source: missing-python-build-dependency N: N:The package appears to use Python as part of its build process in N:debian/rules but doesn't depend on Python. N: N:Normally, packages that use Python as part of the build process should N:build-depend on one of python, python-all, python-dev, or python-all-dev N:depending on whether they support multiple versions of Python and N:whether they're building modules or only using Python as part of the N:package build process. Packages that depend on a specific version of N:Python may build-depend on the appropriate pythonX.Y or pythonX.Y-dev N:package instead. N: N:Refer to Debian Policy Manual section 4.2 (Package relationships) for N:details. N: N:Severity: important, Certainty: certain N: N:Check: rules, Type: source N: by changing python3-all:any to python3-all stops above false positive messages. Regards, Osamu PS: Only python* and cpp packages are the MA:allowed packages. You may also check cpp related check logic. There is only one package having cpp:any at this moment. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lintian depends on: ii binutils 2.24-2 ii bzip2 1.0.6-5 ii diffstat 1.58-1 ii file 1:5.14-2 ii gettext0.18.3.1-2 ii hardening-includes 2.5 ii intltool-debian0.35.0+20060710.1 ii libapt-pkg-perl0.1.29+b1 ii libarchive-zip-perl1.30-7 ii libclass-accessor-perl 0.34-1 ii libclone-perl 0.36-1 ii libdpkg-perl 1.17.5 ii libemail-valid-perl1.192-1 ii libfile-basedir-perl 0.03-1 ii libipc-run-perl0.92-1 ii liblist-moreutils-perl 0.33-1+b2 ii libparse-debianchangelog-perl 1.2.0-1 ii libtext-levenshtein-perl 0.06~01-2 ii libtimedate-perl 2.3000-1 ii liburi-perl1.60-1 ii man-db 2.6.5-3 ii patchutils 0.3.2-3 ii perl [libdigest-sha-perl] 5.18.2-2 ii t1utils1.37-2 Versions of packages lintian recommends: ii libautodie-perl 2.22-1 ii libperlio-gzip-perl 0.18-1+b3 ii perl-modules [libautodie-perl] 5.18.2-2 Versions of packages lintian suggests: pn binutils-multiarch none ii dpkg-dev 1.17.5 ii libhtml-parser-perl3.71-1+b1 ii libtext-template-perl 1.46-1 ii libyaml-perl 0.84-1 ii xz-utils 5.1.1alpha+20120614-2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735555: missing license in debian/copyright
Package: liblivemedia Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing license of ./liveMedia/rtcp_from_spec.h ./liveMedia/rtcp_from_spec.c to debian/copyright. According to http://tools.ietf.org/html/draft-ietf-avt-rtp-new-11 it is not LGPL ... Thanks! Thorsten -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735530: samhain: FTBFS on amd64 and kfreebsd
On 16 January 2014 09:33, Ivo De Decker ivo.dedec...@ugent.be wrote: The latest samhain upload doesn't build on amd64. This was also the case with the previous upload (3.1.0-1). (...) Thanks. I'll take a more detailed look but, reviewing this fast: - the amd64 FTBFS issue seem to be an upstream issue. I will report it to them - the build-dep regarding the audit library can be removed for those architectures, it is not an essential library for the program to work Best regards Javier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735543: autopkgtest fails on missing runit, stderr, and test failures
Hi Martin,
thanks for your bug report. I have tested this with latest upstream
(1.22.1) without any better result. So I put upstream Michael Lawrence
in CC and hope he might be able to sort this out.
Michael, are we doing something wrong when running the test suite script
#!/bin/sh -e
LC_ALL=C R --no-save EOT
require(rtracklayer)
rtracklayer:::.test()
EOT
?
Kind regards
Andreas.
On Thu, Jan 16, 2014 at 12:09:17PM +0100, Martin Pitt wrote:
Package: r-bioc-rtracklayer
Version: 1.22.0-1
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch trusty
Hello,
r-bioc-rtracklayer's autopkgtest currently fails [1]:
Error in BiocGenerics:::testPackage(rtracklayer) :
RUnit package not found
After adding it (r-cran-runit), it fails because the test produces a
lot of stderror. Attached debdiff fixes these two, but now the test
encounters some actual failures:
Error in seqlevels(seqinfo(x)) :
error in evaluating the argument 'x' in selecting a method for function
'seqlevels': Error in (function (classes, fdef, mtable) :
unable to find an inherited method for function 'seqinfo' for signature
'NULL'
Calls: seqinfo - Anonymous
(it repeats that a few times). I attach the full test log for
reference. Do you have an idea what's wrong there?
Thanks for considering,
Martin
[1]
https://jenkins.qa.ubuntu.com/job/trusty-adt-r-bioc-rtracklayer/6/ARCH=i386,label=adt/console
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
diff -Nru r-bioc-rtracklayer-1.22.0/debian/changelog
r-bioc-rtracklayer-1.22.0/debian/changelog
--- r-bioc-rtracklayer-1.22.0/debian/changelog2013-12-28
01:59:48.0 +0100
+++ r-bioc-rtracklayer-1.22.0/debian/changelog2014-01-16
12:06:12.0 +0100
@@ -1,3 +1,10 @@
+r-bioc-rtracklayer (1.22.0-1ubuntu1) UNRELEASED; urgency=medium
+
+ * debian/tests/control: Add missing r-cran-runit test dependency, and allow
+stderr output.
+
+ -- Martin Pitt martin.p...@ubuntu.com Thu, 16 Jan 2014 12:00:35 +0100
+
r-bioc-rtracklayer (1.22.0-1) unstable; urgency=low
* Initial release (closes: #733283).
diff -Nru r-bioc-rtracklayer-1.22.0/debian/tests/control
r-bioc-rtracklayer-1.22.0/debian/tests/control
--- r-bioc-rtracklayer-1.22.0/debian/tests/control2013-11-05
09:42:06.0 +0100
+++ r-bioc-rtracklayer-1.22.0/debian/tests/control2014-01-16
12:00:33.0 +0100
@@ -1 +1,3 @@
Tests: run-unit-test
+Depends: @, r-cran-runit
+Restrictions: allow-stderr
adt-run1: options: {'set_lang': False, 'timeout_install': None,
'binaries_fortests': 'auto', 'actions': [Action ubtree ubtree0 .],
'VSERVER_DUMMY': None, 'unbuilt_tree': None, 'summary':
'/home/ubuntu/adt-log/summary.log', 'timeout_test': None, 'binary': None,
'logfile': '/home/ubuntu/adt-log//log', 'timeout_short': None, 'vserver':
['adt-virt-null'], 'source': None, 'output_dir': '/home/ubuntu/adt-log/',
'debuglevel': 1, 'gainroot': None, 'timeout_build': None,
'built_binaries_filter': None, 'user': 'ubuntu', 'timeout_factor': 1.0,
'gnupghome': '~/.autopkgtest/gpg', 'quiet': False, 'timeout_copy': 1000,
'built_tree': None, 'binaries': 'auto', 'binaries_forbuilds': 'auto'};
timeouts: {'test': 1, 'copy': 1000, 'short': 100, 'build': 10,
'install': 3000}
adt-run1: ** init
adt-run1: ** start
adt-run: $ vserver: adt-virt-null
adt-run1: ** open, scratch=None
adt-run1: ** cmdl = ['sh', '-c', 'exec $@', 'x']
adt-run1: * initialising
adt-run1: * preparing for key generation
adt-run: $ genkey: sh -ec SCRIPT x /home/ubuntu/.autopkgtest/gpg
adt-run1: $
adt-run1: $ exec 2
adt-run1: $ cd $1
adt-run1: $ cat END key-gen-params
adt-run1: $ Key-Type: DSA
adt-run1: $ Key-Length: 1024
adt-run1: $ Key-Usage: sign
adt-run1: $ Name-Real: autopkgtest per-run key
adt-run1: $ Name-Comment: do not trust this key
adt-run1: $ Name-Email: autopkgt...@example.com
adt-run1: $ END
adt-run1: $ set -x
adt-run1: $ gpg --homedir=$1 --batch --gen-key key-gen-params
+ gpg --homedir=/home/ubuntu/.autopkgtest/gpg --batch --gen-key key-gen-params
gpg: keyring `/home/ubuntu/.autopkgtest/gpg/secring.gpg' created
gpg: keyring `/home/ubuntu/.autopkgtest/gpg/pubring.gpg' created
+..+++..+...+++.+.+..+++.+.++..+.+
gpg: /home/ubuntu/.autopkgtest/gpg/trustdb.gpg: trustdb created
gpg: key 6B36EE88 marked as ultimately trusted
adt-run1: * reset
adt-run: builds ...
adt-run: ubtree ubtree0
adt-run1: ** blame += arg:.
adt-run1: ** prepare1, modified=False, deps_processed=[], deps_new=[]
adt-run1: ** needs_reset, previously=False
Bug#735440: fusionforge-plugin-scmsvn: post-commit FS processing had error 'attempt to write a readonly database'
On Thu, 16 Jan 2014, Olivier Berger wrote: So... I'm not sure the right fix is to set enable-rep-sharing to false, but I'd probably prefer to touch an empty file with proper rights before creating the repo, until svn fixes the issue with its sqlite sub-component. You can’t do that nōn-racily. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735440: fusionforge-plugin-scmsvn: post-commit FS processing had error 'attempt to write a readonly database'
Hi.
Thorsten Glaser t.gla...@tarent.de writes:
On Thu, 16 Jan 2014, Olivier Berger wrote:
So... I'm not sure the right fix is to set enable-rep-sharing to false,
but I'd probably prefer to touch an empty file with proper rights before
creating the repo, until svn fixes the issue with its sqlite
sub-component.
You can’t do that nōn-racily.
I'm not sure what you mean.
I think the following patch does solve the issue :
root@fusionforge:/usr/share/gforge/plugins/scmsvn/common# diff -u
SVNPlugin.class.php.orig SVNPlugin.class.php
--- SVNPlugin.class.php.orig2014-01-16 13:33:29.0 +0100
+++ SVNPlugin.class.php 2014-01-16 14:09:35.0 +0100
@@ -260,6 +260,8 @@
if ($ret != 0) {
return false;
}
+ // Add fix for
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735440
+ system (touch $repo/db/rep-cache.db);
if (forge_get_config('use_ssh', 'scmsvn')) {
$unix_group = 'scm_' . $project-getUnixName() ;
system (find $repo -type d | xargs -I{} chmod
g+s {}) ;
However, what seems tricky is how to fix repos where revisions have
already been committed and where the cache DB wasn't writable. There
doesn't seem to be anything (yet) in svnadmin verify or svnadmin revover
that would reconstruct the cache DB :-/
I wonder which side effects there would be in such cases... Probably
would deserve asking at SVN's... but I'm not sure I have a real taste
for it ;)
Other opinions ?
Best regards,
--
Olivier BERGER
http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735556: libnet-subnets-perl: New version available with IPv6 support
Package: libnet-subnets-perl Version: 1.0-1 Severity: wishlist Tags: ipv6 Dear Maintainer, There is a new libnet-subnets-perl available on the cpan site with IPv6 support. Could you package it ? http://search.cpan.org/~juerd/Net-Subnets-1.03/ Thanks a lot -- System Information: Debian Release: 7.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnet-subnets-perl depends on: ii perl 5.14.2-21+deb7u1 libnet-subnets-perl recommends no packages. libnet-subnets-perl suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731602: gnome-power-manager: Suspend whed lid closes option disappeared with gnome 3.8 update
Hello, Sorry for the really late response. I tested your solution and now is suspending when the lid is closed. Thank you! However I think the option still is missing in deconf... On Sat, Dec 7, 2013 at 9:55 AM, Andreas Cadhalpun andreas.cadhal...@googlemail.com wrote: Hi, On 07.12.2013 15:12, José David wrote: In Debian Testing, after gnome update to 3.8, the suspend when lid closes options dissapeared from the configuration GUI and from the dconf options. Now when the lid closes, the system does nothing. Gnome needs systemd as PID 1 for suspend on lid close to work. (see Bug #726763) So you either have to use the 'init=/bin/systemd' boot parameter or install systemd-sysv. Best regards, Andreas -- David
Bug#703439: H5Cpp.h missing in libhdf5-openmpi-dev and libhdf5-mpich2-dev?
I had a quick look at the package, since the hdf5 FAQ says: If the build completes properly and the tests pass, then the installation should be okay. You need two options for 'configure': --enable-unsupported and --enable-cxx. Somewhat surprisingly, the first one is already set in debian/rules. I added --enable-cxx and tried to build the package on my Debian Jessie machine. The build fails with make[2]: Entering directory `/home/sander/hdf5/hdf5-1.8.12/debian/build-openmpi/c++' Making all in src make[3]: Entering directory `/home/sander/hdf5/hdf5-1.8.12/debian/build-openmpi/c++/src' CXX H5Exception.lo In file included from ../../../../src/hdf5.h:24:0, from ../../../../c++/src/H5Include.h:17, from ../../../../c++/src/H5Exception.cpp:18: ../../../../src/H5public.h:63:20: fatal error: mpi.h: No such file or directory # include mpi.h ^ compilation terminated. make[3]: *** [H5Exception.lo] Fehler 1 make[3]: Leaving directory `/home/sander/hdf5/hdf5-1.8.12/debian/build-openmpi/c++/src' make[2]: *** [all-recursive] Fehler 1 make[2]: Leaving directory `/home/sander/hdf5/hdf5-1.8.12/debian/build-openmpi/c++' make[1]: *** [all-recursive] Fehler 1 make[1]: Leaving directory `/home/sander/hdf5/hdf5-1.8.12/debian/build-openmpi' make: *** [build-stamp-openmpi] Fehler 2 dpkg-buildpackage: Fehler: Fehler-Exitstatus von debian/rules build war 2 Any ideas? signature.asc Description: OpenPGP digital signature
Bug#735440: Bug#735446: subversion: rep-cache.db created without group write bit
On Wed, Jan 15, 2014 at 02:49:37PM +0100, Olivier Berger wrote: Hi. At repository creation, the db/rep-cache.db isn't created respecting the current umask. This leads to producing warnings at commit time. See http://subversion.tigris.org/issues/show_bug.cgi?id=3437 for details. This seems to be fixed post 1.8.5. AFAIU, the file may be touched before the first commit is made, so that sqlite will not try to create it with wrong mask, and we are safe. This is the workaround I'll suggest for fusionforge (see #735440). However, if repositories have received commits whereas the bug was already present, then I fear some inconsistency if the perms are restored as writable for committers, and some later commits are the only ones in the cache. I haven't found a mention of a tool that'd rebuild the cache, and the removing the file just postpones the problem (it will be recreated, with wrong mask, and will only contain the later commits). Note that the upstream docs seem to be wrong in this respect (http://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_fs_fs/structure) mentioning that This file is only consulted during writes and never during reads. Consequently, it is not required, and may be removed at an abritrary time, with the subsequent loss of rep-sharing capabilities for revisions written thereafter. Or maybe if the rep-cache.db isn't complete doesn't do harm ? I'll try and ask upstream for what to do for existing repositories that exhibited the problem. Hope this helps. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735556: Wrong URL !
Sorry Wrong URL ! The right : http://search.cpan.org/~juerd/Net-Subnet-1.03/ attachment: dominique_fournier.vcf
Bug#735556: libnet-subnets-perl: New version available with IPv6 support
-=| Dominique Fournier, 16.01.2014 14:12:47 +0100 |=- Package: libnet-subnets-perl Version: 1.0-1 Severity: wishlist Tags: ipv6 Dear Maintainer, There is a new libnet-subnets-perl available on the cpan site with IPv6 support. Could you package it ? http://search.cpan.org/~juerd/Net-Subnets-1.03/ That's not available (yet)? $ HEAD http://search.cpan.org/~juerd/Net-Subnets-1.03/ | head -1 404 Not Found -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688801: Re: Re: Bug#688801: kde-window-manager: Incorrect Build-conflict against libgles2-mesa-dev
tag 688801 pending thanks This change will be included in our next upload. Sorry for the long delay, but we really lack man power to dig trough the enormous pile of bugs we have and keep KDE as updated as possible at the same time :-/ Kinds regards, Lisandro. -- Outside of a dog, a book is man's best friend. Inside of a dog, it's too dark to read. -- Groucho Marx Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#735556: libnet-subnets-perl: New version available with IPv6 support
On Thu, 16 Jan 2014 14:12:47 +0100, Dominique Fournier wrote: Package: libnet-subnets-perl Version: 1.0-1 Severity: wishlist Tags: ipv6 Dear Maintainer, There is a new libnet-subnets-perl available on the cpan site with IPv6 support. Could you package it ? http://search.cpan.org/~juerd/Net-Subnets-1.03/ This page doesn't exists. What _does_ exist is http://search.cpan.org/~juerd/Net-Subnet-1.03/ and https://metacpan.org/release/Net-Subnet Note the Subnet_s_ vs. Subnet. Net::Subnet_s_ seems to be inexistant on both search.cpan.org and metacpan.org. We'll have to check if Net::Subnet is the same or a successor or whatever. (I'm a bit skeptical: d/copyright and d/changelog in http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libnet-subnets-perl.git;a=tree;f=debian;hb=HEAD have a different copyright holder and older versions, https://metacpan.org/source/JUERD/Net-Subnet-1.03/Changes starts at 1.00) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- BOFH excuse #88: Boss' kid fucked up the machine -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735557: transition: octave3.8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-CC: pkg-octave-de...@lists.alioth.debian.org Dear Release Team, Please schedule a transition for octave 3.8. The new package is already in experimental. The transition should mostly consist of a few dozens binNMUs. We (the Debian Octave Group) are going to determine if some sourceful uploads are needed, and file bugs if needed. Thanks! Ben file: title = octave3.8; is_affected = .depends ~ liboctave1 | .depends ~ liboctave2; is_good = .depends ~ liboctave2; is_bad = .depends ~ liboctave1; -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594 signature.asc Description: Digital signature
Bug#650601: libpng update to 1.6.x
On Sat, Jan 11, 2014 at 11:38 AM, Aníbal Monsalve Salazar ani...@debian.org wrote: On Thu, Jan 02, 2014 at 10:57:26AM +0100, László Böszörményi wrote: Any plans to package libpng 1.6.8, would it need a transition? I can help if you need a helping hand. Please refer to #650601 at: http://bugs.debian.org/650601 Nobuhiro and Norbert are working on the libpng transition currently and your help will also be appreciated. Cool! May I get the package (either in source or Git format) that's in the NEW queue? Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728486: Current patch for resolving lvm/systemd compatibility
On Mon, Dec 02, 2013 at 03:11:03PM -0800, Don Armstrong wrote: On Mon, 02 Dec 2013, Bastian Blank wrote: On Sun, Dec 01, 2013 at 05:49:13PM -0800, Don Armstrong wrote: Bastian: Would such a patch be acceptable in principle? After systemd was fixed, yes. Can you let me know which part of systemd needed to be fixed? [What bug# is this?] It is #720850. systemd breaks backward compatibility. Can you also clarify for me why the patch needs to wait for systemd to be fixed? Because the lvm2 service would fail the same way then the init script. Bastian -- We have found all life forms in the galaxy are capable of superior development. -- Kirk, The Gamesters of Triskelion, stardate 3211.7 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
