Re: systemd-fsck?
]] Steve Langasek The maintainer may disagree, in which case one is free to escalate it to the release team precisely as Tollef has suggested. But there's nothing inappropriate about having this discussion directly with the maintainer first. Right, and I didn't complain about the initial severity, but once people start getting into severity ping-pong it gets tedious. We certainly shouldn't insist that anyone who spots something they think is a release-critical bug be personally responsible for providing a patch and getting it accepted in the narrow window before the package automatically migrates to testing. They're not responsible for it, no. That doesn't mean they can take an update hostage by saying «this must be fixed or I'll continue raising the severity of this bug» either. (I'm not saying you said or implied that.) -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87d2fjms7c@xoog.err.no
Re: systemd-fsck?
Le 11 mai 2014 23:06, Michael Biebl bi...@debian.org a écrit : Am 11.05.2014 19:37, schrieb Helmut Grohne: I trust you to be technically right on this. Still the number of packages getting this wrong is stunning[1]. Therefore I'd argue that [1] http://codesearch.debian.net/search?q=su+-c+path%3Adebian%2F+path%3Ainit If I counted correctly, there are 5 packages using su in their init script, dirmngr being one of them. Considering that we have ~1200 SysV init scripts in Debian, I don't consider this number stunning at all. And yes, we should fix those init scripts. Could you open a bug against lintian asking to detect such case (su use) and with description of problem ans solution. Bastien Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Re: Guile language support in make
On Sun, May 11 2014, Marco d'Itri wrote: I do this for the inn2 package and it has worked well for years. Another (much simpler) example is kmod, which build a deb and a udeb. If ./configure is not buggy and works when called from a build directory then building two binary packages from the same source is trivial. Thanks for all the pointers. I have used a combination of stuff I found in the example to create a make-guile package, now in NEW processing. Since it is installed on so many systems, I believe that a lean make package is still worthwhile. make remains lean; make-guile is identical exept for the added guile support. manoj -- Trespassers will be shot. Survivors will be SHOT AGAIN! Manoj Srivastava sriva...@debian.org http://www.debian.org/~srivasta/ 4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20 05B6 CF48 9438 C577 9A1C signature.asc Description: PGP signature
Re: systemd-fsck?
Le dimanche 11 mai 2014 à 15:53 +0200, Marc Haber a écrit : On Sun, 11 May 2014 13:47:39 +0200, Laurent Bigonville bi...@debian.org wrote: For other distributions (and other Unix based OS) most of (all?) the initscripts are already different anyway. Is it right to force that? No, this is why we are migrating to systemd, which allows to use the same service file across distributions. -- .''`.Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1399884634.5437.796.camel@dsp0698014
Re: systemd-fsck?
Le vendredi 09 mai 2014 à 21:13 +0200, Bas Wijnen a écrit : I think it would be good for libpam-systemd to list systemd-shim first. Certainly not. Systemd is the default init system for jessie, and it should be listed as the first alternative. The fact that an alternative codepath exists for users with specific needs is nice for them, but it is not what we should focus our efforts on. As far as GDM is concerned, any bug reported with systemd-shim installed will be ignored. The bug script should probably be updated to that effect, BTW. -- .''`.Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1399888483.5437.804.camel@dsp0698014
Re: systemd-fsck?
Hello, On 12 May 2014 11:54, Josselin Mouette j...@debian.org wrote: Systemd is the default init system for jessie, and it should be listed as the first alternative. The fact that an alternative codepath exists for users with specific needs is nice for them, but it is not what we should focus our efforts on. As far as GDM is concerned, any bug reported with systemd-shim installed will be ignored. The bug script should probably be updated to that effect, BTW. This sort of behaviour is precisely why so many people not only dislike systemd, but also it's maintainers. -- Cheers, Andrew -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cacujmdnyzegyrwxzo0y38_zwdenfwcspbcwduvqo9n9kn8+...@mail.gmail.com
[OT] Re: systemd-fsck?
Le Mon, May 12, 2014 at 12:16:48PM +0200, Andrew Shadura a écrit : On 12 May 2014 11:54, Josselin Mouette j...@debian.org wrote: Systemd is the default init system for jessie, and it should be listed as the first alternative. The fact that an alternative codepath exists for users with specific needs is nice for them, but it is not what we should focus our efforts on. As far as GDM is concerned, any bug reported with systemd-shim installed will be ignored. The bug script should probably be updated to that effect, BTW. This sort of behaviour is precisely why so many people not only dislike systemd, but also it's maintainers. Hi Andrew, this is the tragedy of the commons: the time and patience of maintainers can be equally spent by anybody who thinksthat his opinion on systemd ought to be listened, and therefore by the time one has a valid criticism to make, the maintainers time and patience has been spent up by others. Message filters are a solution to this. Cheers, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512105016.gi7...@falafel.plessy.net
custom malloc implementations vs. valgrind
(Context: a thread about OpenSSL's custom malloc wrapper on a non-public mailing list; I'm only quoting bits that are explicitly non-private, which is why this mail might seem rather disjointed) Steinar H. Gunderson wrote: No malloc() sends a syscall for every malloc()/free(), except for big allocations. They all allocate larger chunks and carve out from them. Of course, some malloc()s do a poor job nevertheless, and there's also things like arena allocators which need to augment malloc() simply because the entire pattern is so different. and Angus Lees replied: Indeed, valgrind intercepts the malloc/free/new/delete _library_ calls since these (often) don't turn into syscalls. I presume valgrind can be taught to treat other custom-arena functions in the same way, but I haven't looked that closely at the valgrind docs. (Custom allocators / arenas are quite common for some valid performance reasons - particularly for repeated allocations of the same size. A witch hunt to track down every such example and waggle a disapproving finger at it won't be useful) valgrind can certainly be taught to treat custom malloc wrappers like a plain malloc, by using its memcheck.h and valgrind.h headers. libdbus uses a memory pool for DBusList (linked list) links (and possibly a couple of other small structures) for exactly the reasons Angus describes. I taught valgrind about it in commits http://cgit.freedesktop.org/dbus/dbus/commit/?id=b3f2ee5c6bade555630e52b8aa18fd639e047a80 and http://cgit.freedesktop.org/dbus/dbus/commit/?id=01e3c41d75c1b31f0d2fac972b3ea2723dbde06e. http://cgit.freedesktop.org/dbus/dbus/commit/?id=13c1292150c4f5d57527d11f5b92f5b955f9906e, http://cgit.freedesktop.org/dbus/dbus/commit/?id=e516a31f59abbbf7cbfcc3396ef41162188a7f5c, http://cgit.freedesktop.org/dbus/dbus/commit/?id=57dc720b9f25dec999fcc53da982114098cefae9 are useful follow-ups if you're doing something similar. GLib also has a memory-pool subsystem (g_slice_new() and friends) which can be configured as a trivial pass-through to malloc() via G_SLICE=always-malloc in the environment. I believe recent GLib versions also support the same sort of valgrind instrumentation as libdbus. For cryptographic code, there are various extras that can be considered, particularly if you don't care too much about portability; gnome-keyring has a secure memory subsystem which uses mlock() and explicit zeroing, which seems like a useful thing for private keys. I think GNUTLS has something similar. S -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5370b054.10...@debian.org
Re: systemd-fsck?
On Sun, 11 May 2014, Marc Haber wrote: On Sat, 10 May 2014 22:13:01 +0200, Matthias Urlichs matth...@urlichs.de wrote: I also would not expect an end user to add su foo -c /do/whatever to /etc/rc.local. Your opinion may differ, that's OK. Especially people who are not as Debian-centric as we are tend to do exactly this. Simply because they don't know any better. I’ve been doing so for ages, from a BSD PoV (not su -l though¹). Sometimes su -c, sometimes chroot, sometimes both, rarely dchroot. But so are my coworkers who are *not* experienced with BSD. I’ve barely (not even completely) got our admins and systems running Debian/LSB init scripts by now. Piling even more change on top of what is currently needed for administration (ever since insserv…) will not work; people will end with partially broken systems and blame Debian and go back to use CentOS 5… On Sun, 11 May 2014, Cyril Brulebois wrote: Marc Haber mh+debian-de...@zugschlus.de (2014-05-11): Just curious as the maintainer of another package using su in an init script since 2001, how am I supposed to start a non-root process from an init script? start-stop-daemon has: -c, --chuid username|uid[:group|gid] But the start-stop-daemon documentation seems to imply (please correct me if I’m wrong) that it’s for starting (and stopping) specific executables, as dæmons, with pidfiles, etc. – not for just running some shell code (which may or may not start other processes and/or dæmons) as another user. Taking dirmngr as example again: output=$(su -c . /lib/lsb/init-functions umask 027 start_daemon -p $PIDFILE $DAEMON --daemon --sh dirmngr) || return 1 eval $output || return 1 Before preparing the NMU¹, I searched long and wide for something using start-stop-daemon which could replace this piece of code, and found it not. ① Note I did NMU dirmngr to remove the -l from the su call, which was causing problems. bye, //mirabilos -- «MyISAM tables -will- get corrupted eventually. This is a fact of life. » “mysql is about as much database as ms access” – “MSSQL at least descends from a database” “it's a rebranded SyBase” “MySQL however was born from a flatfile and went downhill from there” – “at least jetDB doesn’t claim to be a database” ‣‣‣ Please, http://deb.li/mysql and MariaDB, finally die! -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.deb.2.10.1405121316410.25...@tglase.lan.tarent.de
Re: Avoiding system d
Hi Carlos and Marc, At Mon, 12 May 2014 04:21:10 +0200, Carlos Alberto Lopez Perez wrote: On 11/05/14 09:18, Marc Haber wrote: Something along the lines of systemd is technically needed and a good idea, but the people behind it do not come along nice. Completely agree. While I also agree with that having read some responses of systemd developers developers that could have been nicer, I think it is ironic to call out the systemd developers for not being nice and then post statements like this: The systemd developers are responding to upstart and launchd and android init as things they must _defeat_, an establish a new standard by crushing all the competing implementations. This means developers who want gradual staged transitions, and thus ask questions like what if I don't want to switch yet, or how do I get the old behavior out of the new thing, are enemies of systemd. Those questions are anathema to the systemd plan for world domination, if you're not using their stuff already you're the enemy, a relic of history to be buried. We can't opt out and see how it goes, we must fight to stay where we are. The systemd developers are basically taking the Microsoft approach to development: they don't want you to have the option of NOT using their stuff. http://www.landley.net/notes.html#23-04-2014 Or this: At Sun, 11 May 2014 15:55:48 +0200, Marc Haber wrote: On Sun, 11 May 2014 14:50:55 +0200, Florian Lohoff f...@zz.de wrote: There is no way to avoid the userspace.exe blob Debian is soon made of. To be fair, the major Linuxes will soon be made of that. Red Hat wants it that way. Maybe you should think about how your fellow Debian developers who have no association with Red Hat but just think systemd is technically better and who are working hard to get systemd working right in Debian feel when reading such statements. And while we as Debian can't do much about upstream maintainers not being nice, we can at least try to set a good example by being nice ourself... Kind regards, Jeroen Dekkers -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87oaz39qaj.wl%jer...@dekkers.ch
Thankfully My Last Post
On Mon, 12 May 2014 12:00:48 +0200 A debian dev wrote: Nobody cares. Please go away. You apparently don't care that an official debian document is making sweeping incorrect statements even though I have told you I have professional experience in this area and pointed debian to a buildroot link multiple times that at the very least shows your page to be inaccurate. Devices are getting smaller and smaller and mhz aren't equivelent at all for any idiots out there, systemd is not even close to a Universal init. Perhaps it is still under consideration but you also don't seem to have given nearly enough consideration to su breakage and ploughed ahead with su eradication despite rc.local likely being used under systemd. Users not having read this thread will quite rightly from learning from much more authoritative sources than debian continue to use su in /etc/rc.local. Is there any danger to security of those users from doing that; unanswered and unconsidered? This is important as I guarantee users will continue to do so and likely forever and no amount of website writing will change that. The tech-ctte decision was 50/50 and the final statements largely ignored the crux of the issues, an obviously significant part??? of systemds 50% was based on licensing and not technical arguments that you keep insisting on whilst ignoring pro systemd non technical and incorrect statements. I have no preference for Upstart beyond over systemd but if Ubuntu did decide to inhouse it then how is that an issue. You still have a license to continue to use that code and develop it. It is quite rediculous when the technical consequences are far reaching and even affect Linux beyond debian that this should be a major factor especially when /sbin/init has been undeveloped for so long or do you want pid1 to be re-developed for ever. It has also been said that a fork may be required anyway due to the belligerent nature of upstream. Good intentions to develop for the good of the task itself for shared benefit is the main thing that counts outside of legal nonsense like patents. Perhaps there should have been tech-ctte decisions on the various points. Having just looked it up I am surprised Matthias Urlichs actually is a debian dev and suggest he qualifies his statements much more before making them? The Tech-Ctte output was rather poor largely due to the obfuscation systemd places on the crux of what it deals with and that is primarily why I tried to correct debian developers statements. Perhaps debian simply inherited the changes to su but no-one spoke against it in 1999 or 2000. I am sure Theo among others would have spotted that fundamental default behaviour change and the potential future danger and not allowed it to happen and this makes me appreciate OpenBSD even more. (I know PAM would thankfully have no chance of getting into OpenBSD but that is not the point) A major part of why I am leaving and investigating my options is because I see major management problems and do not believe debian is anywhere near as stable or universal as it purports to be, though much more than Fedora. ___ There are two ways of constructing a software design. One is to make it so simple that there are OBVIOUSLY no deficiencies. And the other is to make it so complicated that there are no OBVIOUS deficiencies Professor C. A. R. Hoare The 1980 Turing award lecture ___ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/372796.30485...@smtp141.mail.ir2.yahoo.com
Re: systemd-fsck?
On Fri, 9 May 2014, Steve Langasek wrote: ii systemd 204-10 ii systemd-sysv 204-10 You can purge them. Install sysvinit-core at the same time. This is unconstructive advice. No, it is not, for someone who wants systemd gone from their system. The systemd binary package contains logind, which is the de facto desktop seat manager for jessie and beyond, What *is* a “desktop seat manager”? I’d not want it on servers (and some coworkers are even running N-M on some of them…), and Linux desktops (and nōn-Linux ones) have not needed those until now either. So, I (still) question this change. environment with seat management on your own systems; but advising people to purge the systemd package from their systems is just wrong. No. Another mistake you likely did is that, after the initial installation, you did not add APT::Install-Recommends 0; to /etc/apt/apt.conf, which is a must-have to be able to run Debian without something unwanted being run all the time. This is also unconstructive. This is unconstructive towards Recommends: package relationships but constructive towards people who want their Debian system working more cleanly and without unwanted software installed that is not even necessary for the software one does want to function. I’m not alone considering --install-recommends being the default as broken, even today. On Sat, 10 May 2014, Marc Haber wrote: We definetely should have a -unstable-user mailing list. -user is Full ACK! And it should definitely target nōn-newbies. On Sat, 10 May 2014, Dimitri John Ledkov wrote: Thus, interim, until we have a mechanism to ask what to do on upgrades, maybe sysvinit/sysvinit-core should gain a (bogus) dependency on systemd-shim? Eh, *no*! There is no need for systemd-shim on the vast majority of Debian systems *either*. (Although my systemd-must-die pak- kage conflicting with it is probably not right either – I’ll keep it for now though, until it’s something that is major blocking.) bye, //mirabilos -- Sometimes they [people] care too much: pretty printers [and syntax highligh- ting, d.A.] mechanically produce pretty output that accentuates irrelevant detail in the program, which is as sensible as putting all the prepositions in English text in bold font. -- Rob Pike in Notes on Programming in C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.deb.2.10.1405121321390.25...@tglase.lan.tarent.de
Re: systemd-fsck?
At Mon, 12 May 2014 12:16:48 +0200, Andrew Shadura wrote: On 12 May 2014 11:54, Josselin Mouette j...@debian.org wrote: Systemd is the default init system for jessie, and it should be listed as the first alternative. The fact that an alternative codepath exists for users with specific needs is nice for them, but it is not what we should focus our efforts on. As far as GDM is concerned, any bug reported with systemd-shim installed will be ignored. The bug script should probably be updated to that effect, BTW. This sort of behaviour is precisely why so many people not only dislike systemd, but also it's maintainers. Why are you blaming the systemd maintainers for decisions made by the GNOME maintainers about GNOME? Kind regards, Jeroen Dekkers -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87ppjj9qsn.wl%jer...@dekkers.ch
Re: systemd-fsck?
On Sat, 10 May 2014, Bas Wijnen wrote: So please get dirmngr fixed instead of blaming systemd/logind. This is the part you should _NEVER_ do. It is YOUR responsibitiliy, as a maintainer (you are the maintainer, right?), to make sure that a bug that is reported in the wrong place gets sent to the right place. It is GOOD that a user reports it (it is a real bug), and it isn't a problem if technically it isn't in your package; you just fix that. Isn’t this how Google works (according to a friend who got hired by them)? If you are the last one to touch something, you get to fix the bugs, even if you didn’t cause them. (Where fix does not necessarily mean to do it themselves; getting others to fix them is also okay, but they have to track them down and ping them and so on.) bye, //mirabilos -- 15:41⎜Lo-lan-do:#fusionforge Somebody write a testsuite for helloworld :-) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.deb.2.10.1405121045200.12...@tglase.lan.tarent.de
Re: systemd-fsck?
]] Andrew Shadura Hello, On 12 May 2014 11:54, Josselin Mouette j...@debian.org wrote: Systemd is the default init system for jessie, and it should be listed as the first alternative. The fact that an alternative codepath exists for users with specific needs is nice for them, but it is not what we should focus our efforts on. As far as GDM is concerned, any bug reported with systemd-shim installed will be ignored. The bug script should probably be updated to that effect, BTW. This sort of behaviour is precisely why so many people not only dislike systemd, but also it's maintainers. Are you aware that Joss isn't a systemd maintainer? (He's one of the GNOME maintainers.) -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/874n0vkz64@xoog.err.no
Re: systemd-fsck?
Hello, On 12 May 2014 13:35, Tollef Fog Heen tfh...@err.no wrote: This sort of behaviour is precisely why so many people not only dislike systemd, but also it's maintainers. Are you aware that Joss isn't a systemd maintainer? (He's one of the GNOME maintainers.) I am. I never claimed he is. -- Cheers, Andrew -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cacujmdn6vpjd1c1xest-xxwhkn413cz+k6jsg2wsksjy8tn...@mail.gmail.com
Re: systemd-fsck?
Le lundi 12 mai 2014 à 13:26 +0200, Thorsten Glaser a écrit : What *is* a “desktop seat manager”? I’d not want it on servers (and some coworkers are even running N-M on some of them…), and Linux desktops (and nōn-Linux ones) have not needed those until now either. So, I (still) question this change. We have had a desktop seat manager since, if my memory serves right, the lenny release: ConsoleKit. Lenny was the first release with proper (non-hackish) graphical user switching. Not a coincidence. There is no need for systemd-shim on the vast majority of Debian systems *either*. Good luck making any package relying on a PolicyKit-wrapped interface to work on your “majority of systems”, then. -- .''`.Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1399895690.5437.824.camel@dsp0698014
Re: systemd-fsck?
Le lundi 12 mai 2014 à 12:16 +0200, Andrew Shadura a écrit : As far as GDM is concerned, any bug reported with systemd-shim installed will be ignored. The bug script should probably be updated to that effect, BTW. This sort of behaviour is precisely why so many people not only dislike systemd, but also it's maintainers. Thank you so much for volunteering to contribute to GNOME packaging and to make it work on configurations nobody will actually ever use. We are eagerly waiting for your patches. -- .''`.Josselin Mouette : :' : `. `' `- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1399895911.5437.827.camel@dsp0698014
Re: Thankfully My Last Post
___ There are two ways of constructing a software design. One is to make it so simple that there are OBVIOUSLY no deficiencies. And the other is to make it so complicated that there are no OBVIOUS deficiencies Professor C. A. R. Hoare The 1980 Turing award lecture ___ Thanks thanks thanks for this... may it be a guiding light for those advertising systemd? But they maybe don't know who Hoare is :-(. Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512124303.gd18...@auth.logic.tuwien.ac.at
Re: Nftables in jessie?
On Fri, 2014-05-09 at 09:18 +0200, Arturo Borrero Gonzalez wrote: On 8 May 2014 19:16, Frank Bauer frank.c.ba...@gmail.com wrote: Hi, Jessie currently contains linux 3.13, which includes the successor of iptables - nftables. Unfortunately, the userspace tools (nftables) are still missing even in sid/experimental. As Vincent Bernat said, is in NEW. Has been in NEW for a month or so. Is there a general plan to support nftables in jessie? As the release managers reminded us recently, the freeze will be here in no time. I believe it is essential for users to be able to test this new technology in jessie before fully switching to it in jessie+1. Unfortunately, there isn't a 'general plan'. I mean, the package will be uploaded and maintained. But no talk happened about what means having nftables in Debian. I think the following points may be interesting: * in which state/shape is the nftables framework? * what about the iptables and the compat layer? The next upstream release of iptables will, by default, use the nf_tables kernel subsystem. What about it? Is there a problem? * what about a standard firewall service (like other distros do). iptables also lacks of it. I think there should be a standard host firewall that supports simple high-level configuration and is installed by default (whether it blocks anything would have to be a debconf question). For firewall routers, I don't think we need to pick a default. * Some bugs happened in the Debian kernel package, and the kernel currently in Jessie comes without nf_tables enabled [0]. [...] Well it's fixed in unstable and will be fixed in jessie RSN. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
Re: systemd-fsck?
[..] configurations nobody will actually ever use. There you are plainly *wrong*... unless you on purpose make it to not work so that nobody can use it ... which I don't hope!!! Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512125211.ge18...@auth.logic.tuwien.ac.at
Re: systemd-fsck?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 05/12/2014 08:52 AM, Norbert Preining wrote: [..] configurations nobody will actually ever use. There you are plainly *wrong*... unless you on purpose make it to not work so that nobody can use it ... which I don't hope!!! Not to mention that, unless we assume bad faith (i.e. trolling or otherwise anti-constructive bug reports), if someone files a bug report about a configuration it presumably means they're wanting to use it... - -- The Wanderer Secrecy is the beginning of tyranny. A government exists to serve its citizens, not to control them. -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJTcMhtAAoJEASpNY00KDJrqMYP/1HTK5kRxtmOXq/L1NX8yfgm P5qNV/HQJCd3PTOwxwM7V8f6Vva7iKYSmAex1gUWHLVx/awfTKUL+gW60h0x VXAA+/30WgRAPxx8ysBt5X6ZcWVjpUE4X+YMRoXF9MQLGaK6vc/8d1Of1xNpoFyX tSRTFMHs77rPl0Fnqs31lPqQ4+UogobWryKe2qKWCucpnT+LTPvcWao2pHPDAv/z jekpwKI1ixx84K7W2mSXW5ln9zp07FkNNJVTHDwz4ck2J7Z4XaEFGAuGBWYYRwEQ lUb47No5u6VenR/RYYh5SKYpoWBYlLrsAPJ3xnNFx09gEc5cdFAquWFDffWGqG3Z BRI05BXmrV6MdqNkS8cMA7+qs69oU5CVJ6KIVH2yHj2ZVb3j5sjOVe04w7FKlI0d 9xpWu+U/zIvjwaxramqB4k2jPVZGRLgg1C2q/JR7W0JrVvkEVqaZ0DAk/aFHoXhh FevDg31wO4pqjt0GQXXYx8dvw26qp6s/TG2kSooZf7R/rg7HeDpTDv2p3t/xnBMt 6yt6YT4QlC89T0QJ+ttd89P0zOEqtsooV3FQsGw/iaKKRjao92j1C/0nr6w1jdqw Y2jNcTmVwL4W8Mrf93E35B2197huKSgqa7fcOlcePfMWdVWqlWsEjjRQcAcgRFLq gAlt9lATKzymvStFOoeo =I0Nx -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5370c86d.4060...@fastmail.fm
Re: Alioth tracker
On May 12, 2014, at 07:57 AM, Charles Plessy wrote: For mailing lists, I read in the thread that it may not be a problem anyway, but I just wanted to add one thing: in many cases the lists to be created are a maintainer list and a commit list, and this could be replaced completely by the “new PTS” (see http://dep.debian.net/deps/dep2/ and http://pts.debian.net/). People who have time to give but do not have the right skill set to work on Alioth or Mailman may consider helping the new PTS instead. I don't have time to work on Alioth, but JFTR, we (the GNU Mailman development team) recently announced the first full-suite beta release for Mailman 3. It's possible that even with the usual beta-quality issues, that MM3 would make a decent mailing list framework for this Debian use case. It has some interesting features that might make integration easier, and I would be highly motivated to help others adapt and extend MM3 for Debian's use. Contact me personally off-list or via IRC, or start the discussion on the mailman-develop...@python.org list. Cheers, -Barry signature.asc Description: PGP signature
Re: Nftables in jessie?
On 12 May 2014 14:56, Ben Hutchings b...@decadent.org.uk wrote: I think the following points may be interesting: * in which state/shape is the nftables framework? * what about the iptables and the compat layer? The next upstream release of iptables will, by default, use the nf_tables kernel subsystem. What about it? Is there a problem? No, just pointing it out. * what about a standard firewall service (like other distros do). iptables also lacks of it. I think there should be a standard host firewall that supports simple high-level configuration and is installed by default (whether it blocks anything would have to be a debconf question). I think there is no an easy (direct) choice. The nftables syntax is kind of higher level than iptables. Readable keywords vs classic switches. For firewall routers, I don't think we need to pick a default. * Some bugs happened in the Debian kernel package, and the kernel currently in Jessie comes without nf_tables enabled [0]. [...] Well it's fixed in unstable and will be fixed in jessie RSN. Ok, thanks. -- Arturo Borrero González -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAOkSjBjO+XcmF_d2xHt=8jhar4s6z2hjwwsq1c1hpnfysso...@mail.gmail.com
Re: systemd-fsck?
On Mon, May 12, 2014 at 11:54:43AM +0200, Josselin Mouette wrote: Systemd is the default init system for jessie, and it should be listed as the first alternative. Can you please explain what is wrong with my reasoning? A default is only relevant at the time the functionality is first installed. After that, whatever was installed should stay until the user requests to change it (or there is a technical reason that it can no longer be installed). In the case of an init system, installation happens in d-i. Also, this dependency isn't about an init system. That's not the functionality you're depending on. If it would be, sysv init and upstart should be in the list of alternatives as well, and the whole dependency could be dropped (since an init system is Essential). Instead, you're depending on a very limited part of systemd, and say I want people to switch as soon as possible, so I don't have to care about bug reports. Therefore I sneak systemd on their system when they're not watching and if they complain, I tell them 'you clicked the I Agree button, so it's your own fault.' Or that's what you seem to say anyway. But I sincerely hope this is not your attitude, and I welcome you to correct any misunderstanding. The fact that an alternative codepath exists for users with specific needs is nice for them, but it is not what we should focus our efforts on. That is reasonable, but forcing anyone who doesn't carefully watch their system to convert is not the sort of behaviour I expect or want from Debian. One of the reasons I like Debian so much is that I believe we, as developers, are dedicated to allowing our users to do what they want, without forcing things on them unless there's no other way. Your responses put a big dent in that belief. As far as GDM is concerned, any bug reported with systemd-shim installed will be ignored. The bug script should probably be updated to that effect, BTW. Please don't do that. If your priorities are elsewhere, that is obviously acceptable. But then tell this to the reporter. Ignoring bugs is never a good idea. Thanks, Bas -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512142030.gw10...@fmf.nl
Re: Bug#747535: systemd-fsck?
On 2014-05-12, Bas Wijnen wij...@debian.org wrote: A default is only relevant at the time the functionality is first installed. After that, whatever was installed should stay until the user requests to change it (or there is a technical reason that it can no longer be installed). In the case of an init system, installation happens in d-i. I'd be dissapointed if we don't migrate the vast majority of the users to the default init system. I think my support-burden will be lot smaller if all 'non-power-users' systems are approximately the same. /Sune -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/lkqm56$dt7$1...@ger.gmane.org
mailman3 in Debian [was Re: Alioth tracker]
On Mon, May 12, 2014 at 10:02:35AM -0400, Barry Warsaw wrote: I don't have time to work on Alioth, but JFTR, we (the GNU Mailman development team) recently announced the first full-suite beta release for Mailman 3. It's possible that even with the usual beta-quality issues, that MM3 would make a decent mailing list framework for this Debian use case. It has some interesting features that might make integration easier, and I would be highly motivated to help others adapt and extend MM3 for Debian's use. Are there plans to upload packages to experimental? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512150028.ga15...@scru.org
Re: systemd-fsck?
On Mon, May 12, 2014 at 10:50:34AM +0200, Josselin Mouette wrote: Le dimanche 11 mai 2014 à 15:53 +0200, Marc Haber a écrit : On Sun, 11 May 2014 13:47:39 +0200, Laurent Bigonville bi...@debian.org wrote: For other distributions (and other Unix based OS) most of (all?) the initscripts are already different anyway. Is it right to force that? No, this is why we are migrating to systemd, which allows to use the same service file across distributions. That's a minor theoretical benefit of using systemd units. It remains to be seen whether systemd units are actually portable in practice. I certainly don't agree that it's the reason for migrating to systemd. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Re: howto handle jquery embedding by build-depends
On Thu, May 08, 2014 at 11:45:24AM +0200, Thorsten Glaser wrote: This is a bug in doxygen. Replacing the embedded jquery copy in the Debian package shipping it with a link to the jquery version in Debian should be the right thing to do. Maybe this Your criticism is unconstructive. I agree that this is wrong, but sometimes wrong is the right thing to do. This is even acknowledged by our policy which discourages embedded copies rather than forbidding them. I am not opposed to fixing this embedding, but I will not be doing the work. I tried and figured that it is not worth the effort. Apparently, you didn't even read the reasons I gave for not fixing it. Otherwise you might have given actual arguments. entire technology behind doxygen needs gentle kicking, like people such as Torsten Werner did to Java??? stuff, to get it to conform to our expectations. Please stop useless ranting already. For changing the status quo, your options are: * Explain what parts of the reasoning in Doxygen's README.jquery you consider wrong and why. * Provide patches that do not break existing use cases. * Maintain new packages that contain the Javascript libraries used by Doxygen. * Make Arch:all autobuilding work. Helmut -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512154022.ga16...@alf.mars
Re: mailman3 in Debian [was Re: Alioth tracker]
On Mon, May 12, 2014 17:00, Clint Adams wrote: On Mon, May 12, 2014 at 10:02:35AM -0400, Barry Warsaw wrote: I don't have time to work on Alioth, but JFTR, we (the GNU Mailman development team) recently announced the first full-suite beta release for Mailman 3. It's possible that even with the usual beta-quality issues, that MM3 would make a decent mailing list framework for this Debian use case. It has some interesting features that might make integration easier, and I would be highly motivated to help others adapt and extend MM3 for Debian's use. Are there plans to upload packages to experimental? Some considerations on behalf of the current Mailman for Debian 'team' which maintains the mailman 2.x packages in Debian. The current mailman 2.x packaging is dated and in maintenance mode, updating to the infrequent new upstreams of this branch and fixing the occasional bug, and having not much manpower to do much else. Mailman 3 is completely different from Mailman 3 and I see no synergy in basing anything on the existing package. As of now, to my knowledge no migration or upgrade scenarios exist from MM 2 to MM 3, and I'm not sure if such code will be there in time for jessie. It would therefore make most sense to me if MM 3 packaging was started fresh with a new mailman3 package, allowing for both MM3 and the legacy release to coexist while MM3 matures. When reliable upgrade or migration scenarios exist, the mailman3 package could take over the mailman package, but I expect that to be the case only after jessie. People interested in MM 3 are therefore very much invited to just start packaging it under the mailman3 name, in any way they judge best. Cheers, Thijs -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/d47c67ad31ddbafccab5a96782a02618.squir...@aphrodite.kinkhorst.nl
Re: copyrighted embedded ICC profiles in images
JS == Jonas Smedegaard d...@jones.dk writes: JS I believe it does not violate DFSG to ship e.g. JFIF or GIF files JS which was upstream distributed with copyright-protected but not JS freely licensed ICC profiles, if repackaged to strip those ICC JS profiles. Note that you cannot just strip colour profiles from image containers. Doing so changes the output. You'd have to replace the profile with a Free equivilent. Or, if no free equivilent is available, edit the image to match a Free profile. Such changes should be documented in the package's README.Debian, and probably in the image's metadata. -JimC -- James Cloos cl...@jhcloos.com OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/m3ha4v3sld@carbon.jhcloos.org
Re: systemd-fsck?
Bas Wijnen wrote: On my system, I see systemd-sysv being pulled in by libpam-systemd, which is required by network-manager and policykit-1. libpam-systemd will accept systemd-shim instead of systemd-sysv as well, but it's listed later, so the user has to manually select it if they want to keep their init system. In a long list of this needs to be changed to make the upgrade work, it's very easy to miss that it happens at all, and even if a user does see it, I don't think we can expect them to understand what it means, and go check if there is an alternative. I think it would be good for libpam-systemd to list systemd-shim first. That way, installations that already have systemd for some other reason (like it being the default from d-i) will still work, but it won't switch existing installations to a new init system unexpectedly. Having libpam-systemd depend on systemd-shim | systemd-sysv will not properly handle systems that already have systemd installed but not systemd-sysv. That being said, I don't really care much about the init system; sysv worked fine for me, and now I apparently have systemd and it doesn't seem to cause problems either. Given the lack of a massive number of new bug reports against either systemd packages or the desktop packages depending on them, I suspect that's the general result, as well: uneventful upgrade to a system that's still sysvinit-compatible, where we can deal with bugs as they come up. - Josh Triplett -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512161727.GA5829@jtriplet-mobl1
Re: copyrighted embedded ICC profiles in images
Le 12 mai 2014 17:51, James Cloos cl...@jhcloos.com a écrit : JS == Jonas Smedegaard d...@jones.dk writes: JS I believe it does not violate DFSG to ship e.g. JFIF or GIF files JS which was upstream distributed with copyright-protected but not JS freely licensed ICC profiles, if repackaged to strip those ICC JS profiles. Note that you cannot just strip colour profiles from image containers. Doing so changes the output. You'd have to replace the profile with a Free equivilent. Or, if no free equivilent is available, edit the image to match a Free profile. ImageMagick could make the conversion easily to sRGB. Bastien Such changes should be documented in the package's README.Debian, and probably in the image's metadata. -JimC -- James Cloos cl...@jhcloos.com OpenPGP: 0x997A9F17ED7DAEA6 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/m3ha4v3sld@carbon.jhcloos.org
Re: systemd-fsck?
On Mon, May 12, 2014 at 09:19:40AM -0700, Josh Triplett wrote: Having libpam-systemd depend on systemd-shim | systemd-sysv will not properly handle systems that already have systemd installed but not systemd-sysv. I don't think I understand what you mean. What does having systemd installed mean, if not that it's being used as the init system? And if it isn't used as the init system (presumably because the user chose no to do that), why is it a good idea to change that? In other words: what isn't handled properly? What should happen, and what does happen? That being said, I don't really care much about the init system; sysv worked fine for me, and now I apparently have systemd and it doesn't seem to cause problems either. Given the lack of a massive number of new bug reports against either systemd packages or the desktop packages depending on them, I suspect that's the general result, as well: uneventful upgrade to a system that's still sysvinit-compatible, where we can deal with bugs as they come up. Yes, and it's good that upgrades are generally smooth, but I don't like the idea to migrate people by default. As long as the other init systems are supported, there's no reason that we should push our users away from them. If there are problems with them that aren't fixed, then we should stop supporting them. As long as that hasn't happened, users should be free to use the other init systems and not be treated as second class. As with any other program that gets installed by default, new users will come with new installations. And in particular, systemd maintainers aren't in a position to tell existing users that they shouldn't be using other init systems. Thanks, Bas -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512165614.gx10...@fmf.nl
Re: mailman3 in Debian [was Re: Alioth tracker]
On May 12, 2014, at 05:46 PM, Thijs Kinkhorst wrote: Mailman 3 is completely different from Mailman 3 and I see no synergy in basing anything on the existing package. As of now, to my knowledge no migration or upgrade scenarios exist from MM 2 to MM 3, and I'm not sure if such code will be there in time for jessie. We do have code in the core to do updates from 2.1 to 3. It's well unit tested, but not battle tested. It would therefore make most sense to me if MM 3 packaging was started fresh with a new mailman3 package, allowing for both MM3 and the legacy release to coexist while MM3 matures. When reliable upgrade or migration scenarios exist, the mailman3 package could take over the mailman package, but I expect that to be the case only after jessie. People interested in MM 3 are therefore very much invited to just start packaging it under the mailman3 name, in any way they judge best. Agreed. The MM3 core is a well-behaved setuptools-based project so its packaging should be relatively easy. Hyperkitty and Postorius are Django-based applications. We (upstream) very definitely expect that people will want to run existing MM2.1 installations in parallel with MM3, at least for a while or while they're testing out the transition. I may not have time in the immediate future to do the packaging myself, but I will assist others in any way I can. -Barry signature.asc Description: PGP signature
Re: systemd-fsck?
On 2014-05-12 18:19 +0200, Josh Triplett wrote: Having libpam-systemd depend on systemd-shim | systemd-sysv will not properly handle systems that already have systemd installed but not systemd-sysv. Could you please elaborate what exactly does not work properly in such a situation? I haven't noticed it. Cheers, Sven -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87fvkedi7q@turtle.gmx.de
Re: copyrighted embedded ICC profiles in images
At Sun, 11 May 2014 19:04:07 -0400, David Prévot wrote: Q. Are profiles copyrighted? A. ICC has no formal position on the use of profiles. It is really up to the software vendor. However, since the software vendor effectively holds copyright on the profile (which is specified in a tag) the licence to use their software permits them to prohibit public posting of profiles. One of their motivations could be that if such profiles could be freely exchanged it would limit the number of sales of their software. Also, from a technical perspective it is dangerous to publish such profiles for many devices. A profile for a printer, for example, is only valid for the substrate and inks for which it was made and it is for this reason that few device manufacturers publish profiles for their devices. Any ICC profile is produced using proprietary software. All ICC define is the nature of the tags, which tags are mandatory and which are optional, and how the data should be defined in them. The contents of the tables are vendor specific and each uses different algorithms. It is this that gives the vendor something which they can copyright. That isn't really a clear and useful answer, but what I read is that: - Algorithms to generate ICC profiles can be copyrighted. (More precise would be to a specific implementation of such algorithm can be copyrighted) - Proprietary software vendors could prohibit public posting of included profiles in their software license. But if profiles are copyrightable they would not have to explicitely prohibit such action. According to wikipedia (http://en.wikipedia.org/wiki/ICC_profile) an ICC profile is set of data that characterizes a color input or output device, or a color space. It looks like an ICC profile contains just facts and mere facts aren't copyrightable. Kind regards, Jeroen Dekkers -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87lhu6ao0k.wl%jer...@dekkers.ch
Re: copyrighted embedded ICC profiles in images
Quoting James Cloos (2014-05-12 17:48:53) JS == Jonas Smedegaard d...@jones.dk writes: JS I believe it does not violate DFSG to ship e.g. JFIF or GIF files JS which was upstream distributed with copyright-protected but not JS freely licensed ICC profiles, if repackaged to strip those ICC JS profiles. Note that you cannot just strip colour profiles from image containers. Doing so changes the output. I believe this is the part you really wanted to quote: In many (but not all - need active decision by package maintainer) cases, ICC profiles can simply be stripped with no practical loss of functionality or quality. You are right that you cannot just strip ICC profiles. You'd have to replace the profile with a Free equivilent. Or, if no free equivilent is available, edit the image to match a Free profile. For most images targeted web browsers you can be more lax. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: systemd-fsck?
Bas Wijnen wrote: On Mon, May 12, 2014 at 09:19:40AM -0700, Josh Triplett wrote: Having libpam-systemd depend on systemd-shim | systemd-sysv will not properly handle systems that already have systemd installed but not systemd-sysv. I don't think I understand what you mean. What does having systemd installed mean, if not that it's being used as the init system? And if it isn't used as the init system (presumably because the user chose no to do that), why is it a good idea to change that? In other words: what isn't handled properly? What should happen, and what does happen? Consider a system which has systemd installed, systemd-sysv *not* installed, and systemd used as PID 1 via init=/bin/systemd. Since systemd-sysv is not already installed, systemd-shim | systemd-sysv will pull in systemd-shim instead, which will atttempt to supply services that conflict with systemd's. It might be possible to make an installed systemd-shim play nice with an installed and running systemd, and that'd be needed to allow sysvinit-core and systemd to coexist on the same system as something the user can select. That being said, I don't really care much about the init system; sysv worked fine for me, and now I apparently have systemd and it doesn't seem to cause problems either. Given the lack of a massive number of new bug reports against either systemd packages or the desktop packages depending on them, I suspect that's the general result, as well: uneventful upgrade to a system that's still sysvinit-compatible, where we can deal with bugs as they come up. Yes, and it's good that upgrades are generally smooth, but I don't like the idea to migrate people by default. As long as the other init systems are supported, there's no reason that we should push our users away from them. If there are problems with them that aren't fixed, then we should stop supporting them. As long as that hasn't happened, users should be free to use the other init systems and not be treated as second class. There *is* a reason we should push our users away from the non-default init: we want to make sure that only the users who specifically *want* a non-default init run one, and those are exactly the users prepared to deal with the additional challenges and support issues with doing so. Uers who don't care should end up running the default init system. It's easy enough for any user who *does* care to select a different set of installed packages. - Josh Triplett -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512182113.GA8374@jtriplet-mobl1
Re: systemd-fsck?
On Mon, May 12, 2014 at 11:54:43AM +0200, Josselin Mouette wrote: Le vendredi 09 mai 2014 à 21:13 +0200, Bas Wijnen a écrit : I think it would be good for libpam-systemd to list systemd-shim first. Certainly not. Systemd is the default init system for jessie, and it should be listed as the first alternative. The fact that an alternative codepath exists for users with specific needs is nice for them, but it is not what we should focus our efforts on. As far as GDM is concerned, any bug reported with systemd-shim installed will be ignored. The bug script should probably be updated to that effect, BTW. A better solution would be for you to step down as maintainer, since you clearly are not interested in proper integration of your packages with the rest of Debian. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
cppcheck, does nobody really care about it?
Hi debian developers, cppcheck [1] has been removed from testing [2] because of a sourceless javascript file [3]. Because of this I packaged (with patch and thanks from Octavio) a new dfsg version and uploaded on mentors [4] some time ago. (I'm uploading it again right now since I forgot to put the bug reference into the changelog) Also packaging the new release [5], give a gui [6] and html reporter [7] would be nice and I think easy to achieve, but it requires a go through the new queue and it is almost out of the scope of an NMU. I personally consider cppcheck a great package, that helped so far me in spotting many possible vulnerabilities in packages I comaintain, helping me in providing more secure packages in debian repositories (as well as sending security fixes upstream). So, please, can anybody sponsor this package and upload or just reject it from mentors? Great tools shouldn't just disappear from debian IMAO. I really would like to comaintain this package, but this is out of the scope of this mail. cheers, Gianfranco [1] http://packages.qa.debian.org/c/cppcheck.html [2] http://packages.qa.debian.org/c/cppcheck/news/20140227T163912Z.html [3] bugs.debian.org/735502 [4] http://mentors.debian.net/package/cppcheck [5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734617 [6] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619297 [7] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671757 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1399920426.5693.yahoomail...@web171806.mail.ir2.yahoo.com
Re: systemd-fsck?
On Mon, May 12, 2014 at 11:21:15AM -0700, Josh Triplett wrote: I don't think I understand what you mean. What does having systemd installed mean, if not that it's being used as the init system? And if it isn't used as the init system (presumably because the user chose no to do that), why is it a good idea to change that? In other words: what isn't handled properly? What should happen, and what does happen? Consider a system which has systemd installed, systemd-sysv *not* installed, and systemd used as PID 1 via init=/bin/systemd. Since systemd-sysv is not already installed, systemd-shim | systemd-sysv will pull in systemd-shim instead, which will atttempt to supply services that conflict with systemd's. systemd-shim is bus-activated-only. The dbus name will already be claimed by systemd itself on startup, so systemd-shim will be a no-op on such a system. Stop spreading FUD. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Re: systemd-fsck?
On Mon, May 12, 2014 at 11:21:15AM -0700, Josh Triplett wrote: In other words: what isn't handled properly? What should happen, and what does happen? Consider a system which has systemd installed, systemd-sysv *not* installed, and systemd used as PID 1 via init=/bin/systemd. Since systemd-sysv is not already installed, systemd-shim | systemd-sysv will pull in systemd-shim instead, which will atttempt to supply services that conflict with systemd's. Sounds like those packages should conflict with each other. It isn't a reason to uninstall anything. More generally, the order of dependencies doesn't matter for what options the user can choose. If one of those options is buggy, it shouldn't be an option. we want to make sure that only the users who specifically *want* a non-default init run one, I, as a user, did not expect to be moved over to systemd, and given the discussions about it and the older TC decisions about network manager getting its dependencies right (to stop forcing all of gnome onto the user's system), it felt to me as something that was sneaked past me. I don't want Debian to do that. I don't really care about what init system I use, but I do care that I can trust my system. When this happened, I was thinking what else are they going to force onto my system when I'm not watching closely enough? That's my default attitude towards any install or upgrade on a proprietary system, and I most certainly don't want to grow it for Debian users. It's easy enough for any user who *does* care to select a different set of installed packages. It's not so much about caring which init system to use. It's about being in control over your own computer. There are many packages that I use and while I like them being upgraded to new versions, I don't like them to be replaced with different programs. Not unless I ask for it. The exception is when the program I use is no longer supported. When that happens, I'll need something else, and using whatever is default on new installs is a good choice in that case. But again, as long as other init systems are supported, I don't want to do anything to continue using them. Not even something easy. Thanks, Bas -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512191649.gz10...@fmf.nl
Re: cppcheck, does nobody really care about it?
On 12/05/14 11:47, Gianfranco Costamagna wrote: Hi debian developers, cppcheck [1] has been removed from testing [2] because of a sourceless javascript file [3]. Hi, Gianfranco. Not a DD here, but: There are mixed opinions about cases like this. cppcheck doesn't need jQuery to work (or to do anything at all, even): it's just that a copy of the documentation website is included in the upstream package, and thus, the Debian source package, but nothing from this is actually included in the binary, not even used for compilation. So, just to get back in sync: currently, Debian's cppcheck is (was) upstream's 1.61. There was a 1.64 version available [*] but there was a problem with tinyxml2 versioning (and therefore, packaging). I commented on tinyxml2 issue #31 [1] regarding this and upstream accepted to tag future releases. This helped tinyxml2 packaging [2] to make it easier for cppcheck to Depend: libtinyxml2-2 and 2.0.2-1 is now on testing [3]. I got asked privately to test 1.64 directly, but I've been out of town for almost a month now and unable to contribute. Just today I returned, so I should have some spare time during this week to try a package for 1.64 with Depend: libtinyxml2-2 and most probably without the jQuery file altogether, given that jQuery cases and correct inclusion discussion have still not completely settled down. [*] 2 days ago 1.65 was released [4], so I may try 1.65 instead. [1] https://github.com/leethomason/tinyxml2/issues/31 [2] http://packages.qa.debian.org/t/tinyxml2.html [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734617 [4] https://github.com/danmar/cppcheck/releases Because of this I packaged (with patch and thanks from Octavio) a new dfsg version and uploaded on mentors [4] some time ago. (I'm uploading it again right now since I forgot to put the bug reference into the changelog) Personally, I'd rather see 1.61+dfsg uploaded before attempting to package 1.65, but has its own set of implications. For example, the patch uses the Files-Excluded: facility on debian/watch, and this includes repackaging the same version of upstream, which I'm not exactly sure how this would work. So, if 1.65 works now, we should kill two big birds with one shot and hopefully we will all be happy. I personally consider cppcheck a great package, that helped so far me in spotting many possible vulnerabilities in packages I comaintain, helping me in providing more secure packages in debian repositories (as well as sending security fixes upstream). I use it on a regular basis, and most of my build scripts use it, so I'm interested it having it included. However, not being a DD, I still need sponsorship. My two cents. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53712dc7.2020...@alvarezp.ods.org
Bug#747912: ITP: golang-uuid --
Package: wnpp Severity: wishlist Owner: Sergio Schvezov sergio.schve...@canonical.com * Package name: golang-uuid Version : 0.0~hg20140512-1 Upstream Author : Paul Borman bor...@google.com * URL : https://code.google.com/p/go-uuid/ * License : BSD-3-Clause Programming Lang: Go Description : Go bindings to work with UUIDs Generates and inspects UUIDs based on RFC 4122 and DCE 1.1: Authentication and Security Services. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512203921.1903.8255.reportbug@rivendell
Re: systemd-fsck?
On Mon, 2014-05-12 at 21:16 +0200, Bas Wijnen wrote: It's easy enough for any user who *does* care to select a different set of installed packages. It's not so much about caring which init system to use. It's about being in control over your own computer. There are many packages that I use and while I like them being upgraded to new versions, I don't like them to be replaced with different programs. Not unless I ask for it. +100++ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1399928030.10012.0.ca...@g3620.my.own.domain
Re: systemd-fsck?
Le Mon, May 12, 2014 at 11:21:15AM -0700, Josh Triplett a écrit : There *is* a reason we should push our users away from the non-default init: we want to make sure that only the users who specifically *want* a non-default init run one, and those are exactly the users prepared to deal with the additional challenges and support issues with doing so. Uers who don't care should end up running the default init system. It's easy enough for any user who *does* care to select a different set of installed packages. Hi Josh and everybody, how about the following heuristic: on systems where appropriate task-desktop metapackages are installed, migrate automatically; on other systems, ask. I think that it would minimise the total number of people who a) break their desktop systems or block their upgrade by being afraid to migrate and b) break their server with an unsupervised migration. Said differently, judging from what is written in the long threads here, people who do not want systemd seem to be running servers or exotic desktop systems, so how about only sending a debconf prompt in these cases ? Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512224849.ga7...@falafel.plessy.net
Bug#747920: ITP: libdatabase-dumptruck -- document-oriented interface to a SQLite database
Package: wnpp Severity: wishlist Owner: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org * Package name: libdatabase-dumptruck Version : 1.2 Upstream Author : Lubomir Rintel lkund...@v3.sk * URL : https://metacpan.org/release/Database-DumpTruck * License : Artistic or GPL-1+ Programming Lang: Perl Description : document-oriented interface to a SQLite database Database::DumpTruck is a simple document-oriented interface to a SQLite database, modelled after Scraperwiki's Python dumptruck module. It allows for easy (and maybe inefficient) storage and retrieval of structured data to and from a database without interfacing with SQL. The module attempts to identify the type of the data you're inserting and uses an appropriate SQLite type. I am packaging this so that it's conventiently available for use with Morph http://morph.io/ web scraping engine. It will be maintained by the perl packaging team and needs a sponsor. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512225634.12318.48836.report...@odvarok.lan
Re: systemd-fsck?
El Mon, 12 de May 2014 a las 3:48 PM, Charles Plessy ple...@debian.org escribió: Le Mon, May 12, 2014 at 11:21:15AM -0700, Josh Triplett a écrit : There *is* a reason we should push our users away from the non-default init: we want to make sure that only the users who specifically *want* a non-default init run one, and those are exactly the users prepared to deal with the additional challenges and support issues with doing so. Uers who don't care should end up running the default init system. It's easy enough for any user who *does* care to select a different set of installed packages. Hi Josh and everybody, how about the following heuristic: on systems where appropriate task-desktop metapackages are installed, migrate automatically; on other systems, ask. I think that it would minimise the total number of people who a) break their desktop systems or block their upgrade by being afraid to migrate and b) break their server with an unsupervised migration. Said differently, judging from what is written in the long threads here, people who do not want systemd seem to be running servers or exotic desktop systems, so how about only sending a debconf prompt in these cases ? Is it not possible to tell if the sysvinit or upstart packages were installed manually, and give a prompt then (in addition to something like you described) ? Best, -- Cameron Norman
Re: [OT] Re: systemd-fsck?
Charles Plessy ple...@debian.org writes: Le Mon, May 12, 2014 at 12:16:48PM +0200, Andrew Shadura a écrit : On 12 May 2014 11:54, Josselin Mouette j...@debian.org wrote: Systemd is the default init system for jessie, and it should be listed as the first alternative. The fact that an alternative codepath exists for users with specific needs is nice for them, but it is not what we should focus our efforts on. As far as GDM is concerned, any bug reported with systemd-shim installed will be ignored. The bug script should probably be updated to that effect, BTW. This sort of behaviour is precisely why so many people not only dislike systemd, but also it's maintainers. Hi Andrew, this is the tragedy of the commons: the time and patience of maintainers can be equally spent by anybody who thinks that his opinion on systemd ought to be listened, and therefore by the time one has a valid criticism to make, the maintainers time and patience has been spent up by others. Message filters are a solution to this. I hate to post a simple me too message, but this is so well put that I just have to. This, exactly. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87ha4ud20s@windlord.stanford.edu
Re: Re: systemd-fsck?
Thorsten Glaser wrote: On Sun, 11 May 2014, Marc Haber wrote: [...] On Sun, 11 May 2014, Cyril Brulebois wrote: Marc Haber mh+debian-de...@zugschlus.de (2014-05-11): Just curious as the maintainer of another package using su in an init script since 2001, how am I supposed to start a non-root process from an init script? start-stop-daemon has: -c, --chuid username|uid[:group|gid] But the start-stop-daemon documentation seems to imply (please correct me if I’m wrong) that it’s for starting (and stopping) specific executables, as dæmons, with pidfiles, etc. – not for just running some shell code (which may or may not start other processes and/or dæmons) as another user. Taking dirmngr as example again: output=$(su -c . /lib/lsb/init-functions umask 027 start_daemon -p $PIDFILE $DAEMON --daemon --sh dirmngr) || return 1 eval $output || return 1 Before preparing the NMU¹, I searched long and wide for something using start-stop-daemon which could replace this piece of code, and found it not. I've prepared a NMU to replace su by start-stop-daemon and the change was pretty straightforward: output=$(start-stop-daemon --start --quiet --exec $DAEMON --oknodo --pidfile $PIDFILE --umask 027 --chuid dirmngr -- --daemon --sh) || return 1 eval $output || return 1 Cheers, Laurent Bigonville ① Note I did NMU dirmngr to remove the -l from the su call, which was causing problems. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140513011414.0dad6...@fornost.bigon.be
Re: systemd-fsck?
Steve Langasek wrote: On Mon, May 12, 2014 at 11:21:15AM -0700, Josh Triplett wrote: I don't think I understand what you mean. What does having systemd installed mean, if not that it's being used as the init system? And if it isn't used as the init system (presumably because the user chose no to do that), why is it a good idea to change that? In other words: what isn't handled properly? What should happen, and what does happen? Consider a system which has systemd installed, systemd-sysv *not* installed, and systemd used as PID 1 via init=/bin/systemd. Since systemd-sysv is not already installed, systemd-shim | systemd-sysv will pull in systemd-shim instead, which will atttempt to supply services that conflict with systemd's. systemd-shim is bus-activated-only. The dbus name will already be claimed by systemd itself on startup, so systemd-shim will be a no-op on such a system. I appreciate the clarification; thanks. In that case, as one possible option, given that systemd-shim exists to run the systemd helpers, which the systemd package provides (logind, etc), how crazy would it be for systemd-shim to depend on systemd rather than providing its own (currently binary-identical) copy of /etc/dbus-1/system.d/org.freedesktop.systemd1.conf? If it did so, then there should be approximately zero danger of the two conflicting in any way, and it should be zero risk to have the two coexisting on the same system. (I realize that that inverts the dependency relationship a bit, but nonetheless it seems potentially sensible for maintainability and risk-reduction.) I'd still argue that systemd-sysv | systemd-shim is the right way around, but nonetheless the above seems helpful from the point of view of making sure sysvinit-core+systemd-shim and systemd can coexist on the same system to allow runtime selection. Stop spreading FUD. Please consider assuming good faith; I appreciate you providing a correction and participating in the discussion. - Josh Triplett -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140512232122.GA14816@jtriplet-mobl1
Re: Bug#747920: ITP: libdatabase-dumptruck -- document-oriented interface to a SQLite database
On Tue, May 13, 2014 at 12:56:34AM +0200, Lubomir Rintel wrote: Package: wnpp Severity: wishlist Owner: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org * Package name: libdatabase-dumptruck Version : 1.2 Upstream Author : Lubomir Rintel lkund...@v3.sk * URL : https://metacpan.org/release/Database-DumpTruck * License : Artistic or GPL-1+ Programming Lang: Perl Description : document-oriented interface to a SQLite database Database::DumpTruck is a simple document-oriented interface to a SQLite What does document-oriented interface mean? I am packaging this so that it's conventiently available for use with Morph ^ Shouldn't the package name be libdatabase-dumptruck-perl? -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140513001321.GA1787@tal
Re: correct use of su
On Sat, May 10, 2014 at 11:11:10PM -0700, Steve Langasek wrote:
On Sun, May 11, 2014 at 11:12:08AM +1000, Brian May wrote:
The name start-stop-daemon would suggest this is inappropriate for cron
jobs, is that an invalid assumption I made?
Perhaps a better name could have been chosen, in hindsight. But in
practice, s-s-d is the best available tool for uid switching in any
noninteractive scripts.
There are situations where start-stop-daemon is disabled to avoid
daemons starting up in inappropriate contexts (such as during d-i), yet
we still need to switch uids because the task at hand is not one of
those that should be disabled in such contexts. The example of this I'm
familiar with is in man-db.postinst, which has this code:
run_mandb () {
db_get man-db/auto-update
[ $RET = true ] || return 0
# start-stop-daemon isn't available when running from debootstrap.
perl -e '@pwd = getpwnam(man); $( = $) = $pwd[3]; $ = $ = $pwd[2];
exec /usr/bin/mandb, @ARGV' -- $@ || true
}
(This is not relevant for Brian's cron job case, of course, but I still
think it's worth mentioning as any noninteractive scripts is quite a
sweeping statement.)
It's a shame that there is, as far as I know, no low-level tool for this
in an Essential package.
--
Colin Watson [cjwat...@debian.org]
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140513002108.ga10...@riva.ucam.org
Re: correct use of su
On Tue, May 13, 2014 at 01:21:08AM +0100, Colin Watson wrote:
On Sat, May 10, 2014 at 11:11:10PM -0700, Steve Langasek wrote:
On Sun, May 11, 2014 at 11:12:08AM +1000, Brian May wrote:
The name start-stop-daemon would suggest this is inappropriate for cron
jobs, is that an invalid assumption I made?
Perhaps a better name could have been chosen, in hindsight. But in
practice, s-s-d is the best available tool for uid switching in any
noninteractive scripts.
There are situations where start-stop-daemon is disabled to avoid
daemons starting up in inappropriate contexts (such as during d-i), yet
we still need to switch uids because the task at hand is not one of
those that should be disabled in such contexts. The example of this I'm
familiar with is in man-db.postinst, which has this code:
run_mandb () {
db_get man-db/auto-update
[ $RET = true ] || return 0
# start-stop-daemon isn't available when running from debootstrap.
perl -e '@pwd = getpwnam(man); $( = $) = $pwd[3]; $ = $ = $pwd[2];
exec /usr/bin/mandb, @ARGV' -- $@ || true
}
(This is not relevant for Brian's cron job case, of course, but I still
think it's worth mentioning as any noninteractive scripts is quite a
sweeping statement.)
It's a shame that there is, as far as I know, no low-level tool for this
in an Essential package.
AFAIK, d-i disabling of s-s-d is a historical workaround for packages not
using invoke-rc.d (back in the days before it was a Policy must). Maybe
it's time to drop this diversion of s-s-d?
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
Re: systemd-fsck?
On Mon, May 12, 2014 at 04:21:56PM -0700, Josh Triplett wrote: Consider a system which has systemd installed, systemd-sysv *not* installed, and systemd used as PID 1 via init=/bin/systemd. Since systemd-sysv is not already installed, systemd-shim | systemd-sysv will pull in systemd-shim instead, which will atttempt to supply services that conflict with systemd's. systemd-shim is bus-activated-only. The dbus name will already be claimed by systemd itself on startup, so systemd-shim will be a no-op on such a system. I appreciate the clarification; thanks. In that case, as one possible option, given that systemd-shim exists to run the systemd helpers, which the systemd package provides (logind, etc), how crazy would it be for systemd-shim to depend on systemd rather than providing its own (currently binary-identical) copy of /etc/dbus-1/system.d/org.freedesktop.systemd1.conf? If it did so, then there should be approximately zero danger of the two conflicting in any way, and it should be zero risk to have the two coexisting on the same system. (I realize that that inverts the dependency relationship a bit, but nonetheless it seems potentially sensible for maintainability and risk-reduction.) Such a dependency probably wouldn't be terribly harmful, but it does seem to me that it would be a hack. Since the main impact of the duplication is that systemd-shim has to be updated each time the systemd dbus security policy changes, I prefer to wait and see whether this becomes a problem in practice (in terms of either maintenance overhead, or impact to users). I'd still argue that systemd-sysv | systemd-shim is the right way around, but nonetheless the above seems helpful from the point of view of making sure sysvinit-core+systemd-shim and systemd can coexist on the same system to allow runtime selection. It's not the right way around until we've decided that we're ready to make the switch to systemd as default, which is a decision that should be made collectively, and not as a result of libpam-systemd pulling it in automatically on some (desktop) systems while other systems continue with sysvinit. Even after making the switch to systemd by default in unstable, listing systemd-shim first arguably gives less surprising results to users who try to install a desktop environment on top of an existing system: if they've already picked up the dependency on systemd-sysv via sysvinit (once the default has been changed), then the dependency will be satisfied as-is; and if the user has deliberately avoided the selection of systemd-sysv, there's no technical reason that gdm3-libpam-systemd should be the thing that pulls it in. Stop spreading FUD. Please consider assuming good faith; I appreciate you providing a correction and participating in the discussion. Good faith doesn't enter into it. You made a claim, clearly not based on any first-hand knowledge, that the software didn't work. That's inappropriate regardless of any good intentions you might hold, and especially on a highly contentious topic like this one. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140513002643.gb32...@virgil.dodds.net
Re: systemd-fsck?
On Fri, May 09, 2014 at 08:30:22PM +0200, Michael Biebl wrote: Am 09.05.2014 19:56, schrieb Steve Langasek: I don't think systemd integration is in a state today that this is ready to become the default. What are you missing? Bug #746587 is a prime example. But more generally, I'm looking for evidence that we're being systematic about making sure the packages that hook into early boot, either via /etc/rcS.d or /etc/network/if-up.d, will still work correctly after the transition. Maybe we won't have all of these packages fixed ahead of time, but the information should at least be available about which packages do or don't work so that we can make an informed decision. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140513003006.gc32...@virgil.dodds.net
Re: correct use of su
Steve Langasek vor...@debian.org writes: AFAIK, d-i disabling of s-s-d is a historical workaround for packages not using invoke-rc.d (back in the days before it was a Policy must). Maybe it's time to drop this diversion of s-s-d? Yeah, that's just what I was thinking. Any software that doesn't honor an invoke-rc.d policy is RC-buggy anyway, and it would be good to catch and fix that. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87oaz2a46e@windlord.stanford.edu
MBF (Re: correct use of su)
Am 13.05.2014 02:54, schrieb Russ Allbery: Steve Langasek vor...@debian.org writes: AFAIK, d-i disabling of s-s-d is a historical workaround for packages not using invoke-rc.d (back in the days before it was a Policy must). Maybe it's time to drop this diversion of s-s-d? Yeah, that's just what I was thinking. Any software that doesn't honor an invoke-rc.d policy is RC-buggy anyway, and it would be good to catch and fix that. Given the responses so far, I might consider doing a MBF based on the list I posted at [0]. I think this list is pretty complete wrt SysV init scripts. I could extend that to cronjobs etc if there is interest. Is there some general agreement that such a MBF would be worthwile/appreciated? Steve, Bigon, in such a case, would you be willing to help draft the MBF text? Michael [0] https://lists.debian.org/debian-devel/2014/05/msg00459.html -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: systemd pulled in automatically
Am 12.05.2014 05:09, schrieb Russ Allbery: Bas Wijnen wij...@debian.org writes: If the order of the dependencies of libpam-systemd is switched, so it becomes systemd-shim | systemd-sysv, the result will be: - If systemd is not installed, systemd-shim will be installed and the original init system will continue functioning. - If systemd is installed, it will satisfy this dependency and systemd-shim will not be installed. Sounds like exactly what I would expect when upgrading random other packages such as Network Manager. Will systemd-shim work once logind is upgraded to 208? My understanding is that 208 will be going into unstable soon. We certainly want to have 208 (and, actually, something later than that) for jessie. It won't, at least not with the current version of systemd-shim. systemd-shim as currently available, doesn't provide the necessary functionality to make systemd-logind v205+ work standalone . I added a small section regarding this issue to the systemd / GNOME sprint summery [0] posted by Jordi and I also followed up on that on debian-devel [1]. Does that answer your question, Russ? Michael [0] https://lists.debian.org/debian-devel-announce/2014/05/msg1.html [1] https://lists.debian.org/debian-devel/2014/05/msg00104.html -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: systemd-fsck?
On Mon, 12 May 2014, Steve Langasek wrote: Bug #746587 is a prime example. But more generally, I'm looking for evidence that we're being systematic about making sure the packages that hook into early boot, either via /etc/rcS.d or /etc/network/if-up.d, will still work correctly after the transition. Maybe we won't have all of these #743265: systemd: booting with init=/bin/systemd drops into emergency mode If a device is not available but listed without noauto or nofail in /etc/fstab, systemd drops into emergency mode. If this happens on a remote server the system is practically hosed and needs intervention from a local technician. This can happen on *any* server that has been booting happily since many many years. Thus, systemd is *not* a drop-in replacement for now. The usual response is the fstab is wrong, systemd is right, and in the bug report I first subscribed to it. But I changed my mind thinking about servers (e.g., mine, across in a different continent). If a system happens to be automatically and *without* interaction to be switched to systemd and become unbootable without local access, then this is a serious degradation. Norbert PS: There might even me relevant use cases of the above - imagine a early boot script that checks for a special mounted directory and if it is present boots into a special USB mode, thing Tails or gpg signing or similar. PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140513011130.gc31...@auth.logic.tuwien.ac.at
Re: systemd-fsck?
On 13 May 2014 11:11, Norbert Preining prein...@logic.at wrote: #743265: systemd: booting with init=/bin/systemd drops into emergency mode If a device is not available but listed without noauto or nofail in /etc/fstab, systemd drops into emergency mode. Maybe I am mistaken, however I thought this was standard behaviour for SYSV boot systems too That bug is closed and archived, BTW. -- Brian May br...@microcomaustralia.com.au
Re: systemd-fsck?
Norbert Preining prein...@logic.at writes: This can happen on *any* server that has been booting happily since many many years. Thus, systemd is *not* a drop-in replacement for now. We should be realistic about this: it's not going to be, either, at least for a definition of drop-in replacement that involves no changes in behavior. Completely identical behavior is a very high bar that hasn't been met by any other transition of this type that we've made in the past. Dependency-based boot, the change to /bin/sh, and UUID-based mounting were all not drop-in replacements by that criteria. We *are* going to uncover latent bugs in packages, in system configurations, and in other things, and in some cases there will just be differences, which are not obviously bugs anywhere. We should do what we can to diagnose and fix or warn about those, but we also shouldn't be surprised that they exist (and should let users know via at least the release notes that this is a fairly significant change to the boot process). In this case, maybe we can add some transitional smarts to the same package that takes responsibility for upgrade prompting. What comes to mind is scanning /etc/fstab and look for filesystems that aren't set noauto or nofail but that aren't mounted and warn the user with debconf that behavior may change. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87ppji8mj9@windlord.stanford.edu
Re: MBF (Re: correct use of su)
On Tue, May 13, 2014 at 03:01:10AM +0200, Michael Biebl wrote: Am 13.05.2014 02:54, schrieb Russ Allbery: Steve Langasek vor...@debian.org writes: AFAIK, d-i disabling of s-s-d is a historical workaround for packages not using invoke-rc.d (back in the days before it was a Policy must). Maybe it's time to drop this diversion of s-s-d? Yeah, that's just what I was thinking. Any software that doesn't honor an invoke-rc.d policy is RC-buggy anyway, and it would be good to catch and fix that. Given the responses so far, I might consider doing a MBF based on the list I posted at [0]. I think this list is pretty complete wrt SysV init scripts. I could extend that to cronjobs etc if there is interest. Is there some general agreement that such a MBF would be worthwile/appreciated? Sounds appropriate to me. Steve, Bigon, in such a case, would you be willing to help draft the MBF text? Sure. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Re: systemd-fsck?
On Mon, 12 May 2014, Russ Allbery wrote: In this case, maybe we can add some transitional smarts to the same package that takes responsibility for upgrade prompting. What comes to mind is scanning /etc/fstab and look for filesystems that aren't set noauto or nofail but that aren't mounted and warn the user with debconf that behavior may change. Good idea, agreed upon. What I want to say: If we switch during an upgrade to systemd and there is no warning and no asking, and then the system does not boot anymore, sysadms could get quite angry. sysv did allow it for many years, so we have to be careful here. Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140513024503.gg31...@auth.logic.tuwien.ac.at
Re: systemd-fsck?
If a device is not available but listed without noauto or nofail in /etc/fstab, systemd drops into emergency mode. Maybe I am mistaken, however I thought this was standard behaviour for SYSV boot systems too No, it is not standard behaviour. It warns you, but continues booting. That bug is closed and archived, BTW. Yes, that is true, because at that time it was about booting with init=/bin/systemd and *not* about automatic upgrade to systemd without any checking back. If a sysamd boots with init=/bin/systemd then he should know that there might be troubles. If he just made dist-upgrade and suddently the system does not boot, then this is a different things. So yes, should be unearthed. Norbert PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140513024706.gh31...@auth.logic.tuwien.ac.at
Re: systemd-fsck?
On 13 May 2014 12:47, Norbert Preining prein...@logic.at wrote: Yes, that is true, because at that time it was about booting with init=/bin/systemd and *not* about automatic upgrade to systemd without any checking back. No, the title of the bug was changed to systemd drops into emergency mode if devices from /etc/fstab are missing. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743265 -- Brian May br...@microcomaustralia.com.au
Re: cppcheck, does nobody really care about it?
Hi Gianfranco, On Mon, May 12, 2014 at 11:47 AM, Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote: Hi debian developers, cppcheck [1] has been removed from testing [2] because of a sourceless javascript file [3]. [...] So, please, can anybody sponsor this package and upload or just reject it from mentors? I don't see a bug filed against the sponsorship-requests pseudo-package, nor do I see any recent cppcheck RFS requests on debian-mentors@l.d.o (where this mail should've been sent to in the first place, not debian-devel). Please follow the correct sponsorship procedure as outlined on mentors.debian.net [1]; I can assure you that there actually are DDs who track debian-mentors and RFS requests (e.g. yours truly), and you'll get a fairly quick response from me if it deals with a RC bug. The diff looks fine for a NMU, so I'll go ahead and upload this. Thanks! I really would like to comaintain this package, but this is out of the scope of this mail. Again, debian-devel is not the right place for this. You'll want to contact the current maintainer, or if he/she's unresponsive, then contact the MIA team [2] instead. Regards, Vincent [1] http://mentors.debian.net/intro-maintainers [2] https://wiki.debian.org/Teams/MIA -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CACZd_tA1qrcqm=30JGDaDJ_jsDdcpwyCD9UKng6Lj=vzxz7...@mail.gmail.com
Re: MBF (Re: correct use of su)
El Mon, 12 de May 2014 a las 6:01 PM, Michael Biebl bi...@debian.org escribió: Am 13.05.2014 02:54, schrieb Russ Allbery: Steve Langasek vor...@debian.org writes: AFAIK, d-i disabling of s-s-d is a historical workaround for packages not using invoke-rc.d (back in the days before it was a Policy must). Maybe it's time to drop this diversion of s-s-d? Yeah, that's just what I was thinking. Any software that doesn't honor an invoke-rc.d policy is RC-buggy anyway, and it would be good to catch and fix that. Given the responses so far, I might consider doing a MBF based on the list I posted at [0]. I think this list is pretty complete wrt SysV init scripts. I could extend that to cronjobs etc if there is interest. I found another use of su that may need to be added to your list. rabbitmq (oddly) wraps itself up in a shell script, /usr/sbin/rabbitmq-server, which asserts the user is root or rabbitmq, and drops down to rabbitmq if it is root (using su), then starts the actual binary. The problem with this one is that it is upstream code and cannot use s-s-d for obvious reasons. If I am wrong in thinking this usage would be buggy, then carry on. Best, -- Cameron Norman
Re: MBF (Re: correct use of su)
On 13 May 2014 15:44, Cameron Norman camerontnor...@gmail.com wrote: I found another use of su that may need to be added to your list. rabbitmq (oddly) wraps itself up in a shell script, /usr/sbin/rabbitmq-server, which asserts the user is root or rabbitmq, and drops down to rabbitmq if it is root (using su), then starts the actual binary. The problem with this one is that it is upstream code and cannot use s-s-d for obvious reasons. I would imagine that the init.d script just needs to be modified to use the -c option of start-stop-daemon, and that way /usr/sbin/rabbitmq-server will be called with the correct user and won't run su. I assume that the init.d script could also call the actual binary directly. Do wonder how many packages call su in this manner though. -- Brian May br...@microcomaustralia.com.au
Re: MBF (Re: correct use of su)
Le 13 mai 2014 03:01, Michael Biebl bi...@debian.org a écrit : Am 13.05.2014 02:54, schrieb Russ Allbery: Steve Langasek vor...@debian.org writes: AFAIK, d-i disabling of s-s-d is a historical workaround for packages not using invoke-rc.d (back in the days before it was a Policy must). Maybe it's time to drop this diversion of s-s-d? Yeah, that's just what I was thinking. Any software that doesn't honor an invoke-rc.d policy is RC-buggy anyway, and it would be good to catch and fix that. Could you also open a big against Lintian: - describing how to detect this problem - a tag description with reference and solution It will help to avoid to reintroduce this kind of problem. Thank you Given the responses so far, I might consider doing a MBF based on the list I posted at [0]. I think this list is pretty complete wrt SysV init scripts. I could extend that to cronjobs etc if there is interest. Is there some general agreement that such a MBF would be worthwile/appreciated? Steve, Bigon, in such a case, would you be willing to help draft the MBF text? Michael [0] https://lists.debian.org/debian-devel/2014/05/msg00459.html -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Accepted soundscaperenderer 0.4.1~dfsg-2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 May 2014 11:49:11 +0200 Source: soundscaperenderer Binary: soundscaperenderer-nox soundscaperenderer soundscaperenderer-common Architecture: source all amd64 Version: 0.4.1~dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: IOhannes m zmölnig (Debian/GNU) umlae...@debian.org Description: soundscaperenderer - tool for real-time spatial audio reproduction soundscaperenderer-common - tool for real-time spatial audio reproduction (common-files) soundscaperenderer-nox - tool for real-time spatial audio reproduction (without X support) Changes: soundscaperenderer (0.4.1~dfsg-2) unstable; urgency=medium . * export BOOST_LIB_DIR (Closes #747540, #747811) Checksums-Sha1: 5017e0ec70901a7bf5c2710fefa6b15042bd27f0 2548 soundscaperenderer_0.4.1~dfsg-2.dsc d049fdbfddb01a745b481316796cc80585f297e4 9192 soundscaperenderer_0.4.1~dfsg-2.debian.tar.xz 74a825cac43e06ede45415cd4874f9fc43c2431a 680988 soundscaperenderer-common_0.4.1~dfsg-2_all.deb bbfbc2accd10295425c2f0c017990d8a0939fb75 459180 soundscaperenderer-nox_0.4.1~dfsg-2_amd64.deb cd8980d4738e579156bfbf3e5ffd860606cbff7c 609306 soundscaperenderer_0.4.1~dfsg-2_amd64.deb Checksums-Sha256: 846d52023d9128187dcdb6606ca3d6b063dd4b2e6a1fafff61d0f71828bba399 2548 soundscaperenderer_0.4.1~dfsg-2.dsc d1321ae5fe3f08210da024742fff0214f67d7b176097651509c22b87594c8077 9192 soundscaperenderer_0.4.1~dfsg-2.debian.tar.xz 180c5bf87c5a141399beca8d879f8268b6dbf9aa99e5d7a471959d1fbcb7872d 680988 soundscaperenderer-common_0.4.1~dfsg-2_all.deb 9ed6ac0bbfe9dc2189a547cc34aa94bc3f67ed5a2b5b80acff31dde3c4513536 459180 soundscaperenderer-nox_0.4.1~dfsg-2_amd64.deb 2ef8a31bb96f344f9082e90ad52dc5982c57a557e5bb582ef7650e708b604506 609306 soundscaperenderer_0.4.1~dfsg-2_amd64.deb Files: d68b0d01329b27c813ab1f6126164937 680988 sound optional soundscaperenderer-common_0.4.1~dfsg-2_all.deb fc472dde2506a7c871cea69dd30c 459180 sound optional soundscaperenderer-nox_0.4.1~dfsg-2_amd64.deb 69412bf7414c4a0824b6a63488bbd64c 609306 sound optional soundscaperenderer_0.4.1~dfsg-2_amd64.deb aaac59e9bfdd5e1ce073da57e3998af5 2548 sound optional soundscaperenderer_0.4.1~dfsg-2.dsc b3d5e86b4d6cc599e79478aafbd9c6e5 9192 sound optional soundscaperenderer_0.4.1~dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTcJx7AAoJELZQGcR/ejb4VosP/1bZj9Xt4JlNKhNWP8qW+gR3 twGIOakoIwYdS4jTzMjMQx4RYM2T4qeESBa3VI55eI25oPJ3+YX5GGtevkgOlNb7 YlRJxnER4Jyqc/vN3Xjo6KN5OHoSnDUCPfXheOyOtaLnl+b4KT1Cd3lJ9okWlmEW RdRZVzA5Y3SXKAYtfjEMgZ8R2hqA5zc/Wn08spg6UVLtWbvfV5d+5Sx7QC0HI+6C PJmz5vwhdri4qjMAvdaJp/Zv0QBfLW/tb1IweQZ7r8S8VI7CseXE1MoeCCJQTfpu 1N/NtBnBoJEPngKLYcdlsEkyb33q9u2/L/VDWkjCwPD357+Gg3waq7896SOSUsmU e27oasCSg0tGPI1gAJY7rpeE4pSIJmhj8yBK9AhgBLtk2jSS9Qta57ePp/h5+nFu Cvrx3O7Bqa0e0dhte4vafSrirENXCt8hk3m62JdVAkNMxGJJ6JYVfsvfR64bpDfC krpVWxA7UvfIEdq2HoRZlHl1/yNkd54GWKvl4QnjKFgrUdhw9nVWgazkivXTN8Ae XNC69N4lK5btl7YyitpIk789/F/DVfRdr6I7aByBVb6kAQ9/J/lGxCpcK6vVAgX4 cwXETPnKElOgPpaiM4+DpNsGtX58IC/7hnoAIcHPZwKFttlYs8C9oiZW+5swoKaD 4MMjNHdfGiMy2u2Ocm2N =olpT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjnzx-00024x...@franck.debian.org
Accepted proj 4.8.0-4 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 10 May 2014 11:30:06 +0200 Source: proj Binary: proj-data libproj0 libproj-dev proj-bin libproj-java Architecture: source amd64 Version: 4.8.0-4 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org Changed-By: Bas Couwenberg sebas...@xs4all.nl Description: libproj-dev - Cartographic projection library (development files) libproj-java - Cartographic projection library (JNI bindings) libproj0 - Cartographic projection library proj-bin - Cartographic projection library (tools) proj-data - Cartographic projection filter and library (datum package) Changes: proj (4.8.0-4) unstable; urgency=medium . * proj-data is arch any because of architecture specific datumgrids. Checksums-Sha1: 64b477e2a52c7d4fe61f5b6fe6894bcf4690396c 2187 proj_4.8.0-4.dsc b42187e7ce6d3365adc24623e0a5376a807275e4 4385392 proj_4.8.0-4.debian.tar.xz 12bc87dada46a1d10186a93a4d91b5ce9dffa79b 2094256 proj-data_4.8.0-4_amd64.deb f01d3806add9bb1316247f9861454297c8570d11 144400 libproj0_4.8.0-4_amd64.deb e0c116f34f8ebd8603a6ae82d659477bff12e564 173646 libproj-dev_4.8.0-4_amd64.deb 62c731ea3bcd93738dfa736b28bb08396b825129 54404 proj-bin_4.8.0-4_amd64.deb c33fee7d1c9f7ae23a0a250d4b153607e60cb4c4 145326 libproj-java_4.8.0-4_amd64.deb Checksums-Sha256: 9f00ce6156d335ae54b62d85503d0c824547a60b773771bc5ef82510bf1ed08e 2187 proj_4.8.0-4.dsc 5f39d004d2318847094dca8f007985c2cf8d3010ccca58c0f670d64fe81940d2 4385392 proj_4.8.0-4.debian.tar.xz 03c0196c7823f45a57984f28c4229cdf1d32550fecb4767b164c8ac2bf2fd882 2094256 proj-data_4.8.0-4_amd64.deb 2c20dcdab7b614e8aa33c85e774c07ae8151f8ef6488a991923083f366ca79a7 144400 libproj0_4.8.0-4_amd64.deb 676b10f3b4f00936782538165bed476f173430f381505fd99bc932f135ccad4e 173646 libproj-dev_4.8.0-4_amd64.deb 255b298335bd07daa05eb502befcef8a8435a57aca51e8920b64f71fa22d9601 54404 proj-bin_4.8.0-4_amd64.deb 047d8e5cd7a8d3de9ea4e249f5cb9ce0ac974563bbd9b66d78c2a1c312a36318 145326 libproj-java_4.8.0-4_amd64.deb Files: b10d8d246f7e0c36e0e05e86e7a6f63a 2094256 libs optional proj-data_4.8.0-4_amd64.deb 32e119e57146b740470b956a4144 144400 libs optional libproj0_4.8.0-4_amd64.deb ad59257bc2d9908e5596548fe085d5cd 173646 libdevel optional libproj-dev_4.8.0-4_amd64.deb 359a6db64788f4471b0ee05a32cad048 54404 science optional proj-bin_4.8.0-4_amd64.deb 21893c39cc70e5247c6b464c711191fd 145326 java optional libproj-java_4.8.0-4_amd64.deb 7b537e890bd5756bdc6632bb6834bfac 2187 science optional proj_4.8.0-4.dsc 2f1611d049564b80c9fe80814b997637 4385392 science optional proj_4.8.0-4.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTcK6hAAoJEFeKBJTRxkbR1BMQAJGHLaF9HffXxomV0qPmFCsh RzSVkrFtwMfV6QO5Fwkw/GhxTtB510OMe+P0cvb5WevZMtbG11bhVUBnlbLbhSkn Dfe7/xIwnlcVtm6iWtu38q3HAuK9wqQjXQNxQXYqoinltmzdAPtgFmvhrjPVmHYu aa42Z2+1zFwEcMa53ieXjDNdCenUsHxEGNOtbEffu3ddj3Vbv+8uT1RUAxDpxBMI qpodLfHYeCSQPBAROxy4L/Evq5mw3rQfuqLqeDfI+2Jf4IXFKq9xigfmJHllceD4 zOe3R4TWF1e8eCRoajmQqFrbH1vI/1C/f//GFaq7xVrTHlH7+Tz4bCQwc4T1Iob2 4/dMjQHTMhLY+WDPUdFVFKS6Qb6SBBo5Jh2onGPDd9gkNjsIyGKBqTKkO9c1BU0k rK0A81TZeJKMPJIu8tOuRvtRBlTVXngVKSiRRYzeTYkr03w7wUjsdnc8aj8b7ECG AxXF4hrio7Dp54169c38rG8bEaALUYH+irjxtwYX1qqNY0hAd+FCimHqXK5046Y+ X8ZdSEmmG8EcSOKRj9rj2do0ztBZLQsDnpPFSHDnhOZEke82UXo1gjJ0ToSZkbWf L//8z7oN48AsGqjCWiV201S+LSxAxlW1ogWx+kaJjIZCD0HMlTnBzZ3km6DePAm5 llGy3Pq31LzYtGoxadEX =8tOK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjoyz-0005ha...@franck.debian.org
Accepted srf 0.1+dfsg-4 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 May 2014 12:49:56 +0200 Source: srf Binary: srf-doc libsrf-dev Architecture: source all amd64 Version: 0.1+dfsg-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Andreas Tille ti...@debian.org Description: libsrf-dev - C++ implementation of the SRF format for DNA sequence data srf-doc- specification documents for the SRF format DNA sequence data Closes: 747776 Changes: srf (0.1+dfsg-4) unstable; urgency=medium . * Add zlib1g-dev to Build-Depends Closes: #747776 Checksums-Sha1: be7f09c869605e1d063054d19fe7796282fe58f3 2075 srf_0.1+dfsg-4.dsc 422f2004a55e102e958a500c34c217f2a9f16e04 4736 srf_0.1+dfsg-4.debian.tar.xz 4ab50fef43875f421027e239e2853251bd244edc 164562 srf-doc_0.1+dfsg-4_all.deb 1715b49cb39b57103101068d0eba3bdd1e3ba1be 15328 libsrf-dev_0.1+dfsg-4_amd64.deb Checksums-Sha256: 23a520f640fdb2500974a3bf5cebec0b5ccd18e5a285f8e0d98bbf1c1c199df3 2075 srf_0.1+dfsg-4.dsc 1ada1e5397186bf48bf368e2f746ba680f71292c46fce5955b52d580664ba12b 4736 srf_0.1+dfsg-4.debian.tar.xz b630a7a650f2549839de874c9f8891abf9571ad109e2ecc6f1945f02a27834d0 164562 srf-doc_0.1+dfsg-4_all.deb ff3e7783ed4f22444cd65658fe9b714aa30e2dc5450384fc7f88c356523ea28f 15328 libsrf-dev_0.1+dfsg-4_amd64.deb Files: c083403a84fa6c8e3efc8c42de7b100d 164562 doc optional srf-doc_0.1+dfsg-4_all.deb 1d066b9d3246697b62485ea52414950d 15328 libdevel optional libsrf-dev_0.1+dfsg-4_amd64.deb 3089bea0f4421061853bc21b9b77d6cb 2075 science optional srf_0.1+dfsg-4.dsc 62ccf0467cbdd18d0d070515c42da411 4736 science optional srf_0.1+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTcKuiAAoJEFeKBJTRxkbRi8gP/3SuXLNjDQKYiZW/dRSqhGE8 Ri0sfxjePDkso7doJiMeGQZRCuf/uNsI+tYJCBDAppLT0Y+9QG1uTkDaoC67GXGP q06W3Ut2LFnxJgKyKBDHapcQZ4We1PeuYvA5B4XNFSJ5RFCkOf23BZmKQ9zXd87N a0xdiOvx+uNKLB8jcVazGrIqymkzHrToAaHltXC8/vYBLUQXWmpBo+afvk2lumYt sU5rzAuJwwG3C2elHBq7hq4NOBOIal9Ai8mZBv302cYTiWa8Q1qku628p3bSHQZH 9yl8rgDzE43jLXVXIekvBAPuLuoRV4wdZE59AKXmaClniPig+Lkn9U11EU/P79bs o97lNWXIop4bVQ/XS0UMeJJ4TEkK9WadGYTzZKht23+SW0VxzKqe1TVcoGTMU17O Baa0FPLJ1QT8psc3G+aeglekNAnNCcaKEVWKwvkqdgkncLw6UeoMcBf/MXuLoTOU Guu34kUwsEszhnJeq8G15gNSpkDrgPMgFUnYUbyuagJVOgsKg/XsjtKZKkrsvuiD TPNqjCepEmoHcjxFblFadOg7COriHJJbByTxFXQtjbwNhXe11mws3qn4c1gZrMDd v/mWFXREVpRoA5xKwL1XNwuBUcotDj8DUd4nXsqQthMswR6a29Rp3G6XcxKavPd/ qbz6VVmMz4FqUWnq4vBI =aDN4 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjoaw-00069v...@franck.debian.org
Accepted alsa-plugins 1.0.27-2.1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 May 2014 07:33:19 -0400 Source: alsa-plugins Binary: libasound2-plugins Architecture: source amd64 Version: 1.0.27-2.1 Distribution: unstable Urgency: medium Maintainer: Reinhard Tartler siret...@debian.org Changed-By: Reinhard Tartler siret...@tauware.de Description: libasound2-plugins - ALSA library additional plugins Closes: 739209 Changes: alsa-plugins (1.0.27-2.1) unstable; urgency=medium . * Non-maintainer upload. * Add libav10.patch to allow compilation against Libav10 (Closes: #739209) Checksums-Sha1: e2c451cabe8670fa9bd3da42e42313eb919d10a7 2115 alsa-plugins_1.0.27-2.1.dsc 3bd93450bc21cd487b26cceaa47b9e255729a43d 13624 alsa-plugins_1.0.27-2.1.debian.tar.xz 29e529bc1cf04d46da5acacc4b34335681cf57f9 69476 libasound2-plugins_1.0.27-2.1_amd64.deb Checksums-Sha256: 6360ff2b7ec01da46d34943a22d2191245360e476a36563f089640f4bd913e6f 2115 alsa-plugins_1.0.27-2.1.dsc f7008ea86afca2e3c226e528a370bb15a56d2fbc80caedb3f4dc640e97b25af4 13624 alsa-plugins_1.0.27-2.1.debian.tar.xz d40d1110b2387168159d3c202e26cd221f0a5a3af828b9e7b9da7896673ff8fb 69476 libasound2-plugins_1.0.27-2.1_amd64.deb Files: 82779f1209df5248d350783d8783a84d 69476 libs optional libasound2-plugins_1.0.27-2.1_amd64.deb 2fd5b44d218441a2a900f30a7caf65b7 2115 libs optional alsa-plugins_1.0.27-2.1.dsc 0f62dc71b660bd1fb927a74ad030ccf0 13624 libs optional alsa-plugins_1.0.27-2.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQGcBAEBCAAGBQJTcLK+AAoJEIuAbIZKeKRFl30MALU0S24Olts8Tdlvdju7Kxk7 12dG/IScNb0bsfKT76X4Z/4WB8RqaZ6g6CqSgRN6aJZBtoNl/Apf5slc9RkGmtRK m6oojPwnXJoK41dJZWtZBBurNJzOr2NXBI7NOzN5D6h4th+HHJr+FQIZu1eT4FZG 5+8OoYewBykG0q1zs25zJ+YXBLjWyHGO/whmDz6vL5dQMlbplORKNok/7apTUG7W wAPv/KkE2of9BUIBfTm0kup0bYA0bnf8cxFiHfI6pW5GajqHyY+DrkmoACRgCIT+ pD9XXYbAsDjKr0jheVlCqiz9Lm9oeXASPotySO+l0g8r/AKkvL8AB1HNFupzRe58 V6Wgch/b8nL7bR29IqrdBBzF+avMkmo6dT9j0jBdvgWFj2yX5ijD2WINXPnzKmS8 HiR8OGjyFevkmKstetrBd7wao0OgP90F7M/VlaLUHl+fgg/b7VgCi6TdMpHhT6UY KYKx609faHIgpFG9QoqyZj5lGUL5iGnxWqviLVTBxA== =feCg -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjoir-cd...@franck.debian.org
Accepted alberta 3.0.0-1 (amd64 source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 23 Apr 2014 21:42:15 +0200 Source: alberta Binary: libalberta-dev libalberta4 libalberta-dbg libalberta2-dev Architecture: amd64 source Version: 3.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Ansgar Burchardt ans...@debian.org Closes: 731839 742013 Description: libalberta-dbg - adaptive finite element library (debug symbols) libalberta-dev - adaptive finite element library (development files) libalberta2-dev - adaptive finite element library (transitional package) libalberta4 - adaptive finite element library (library) Changes: alberta (3.0.0-1) unstable; urgency=medium . * New upstream release. (Closes: #742013) * New maintainer. (Closes: #731839) * Source package renamed to alberta (from libalberta2). * Packaging redone from scratch. Checksums-Sha1: b712025ae46aef8adf7542489fb93b2e17b3956e 2118 alberta_3.0.0-1.dsc 63e4b7c5d3ad923d1f4f56729deb4731de24fafb 812604 alberta_3.0.0.orig.tar.xz 6a7425ef85054cead001c9335841803f7825da45 3744 alberta_3.0.0-1.debian.tar.xz 857ab243728949a86177e023c0a29c79e3c56f0f 163730 libalberta-dev_3.0.0-1_amd64.deb 87056ed27844ce4c3ff81060be6e2b94bd32fe7c 802040 libalberta4_3.0.0-1_amd64.deb d986304590778ed8b99b15c37cacc1bb4e1bf777 2833614 libalberta-dbg_3.0.0-1_amd64.deb 6b6b94e6f5c4d3b7424428218444912fc3fc1f18 91176 libalberta2-dev_3.0.0-1_amd64.deb Checksums-Sha256: 5519b0a712efaec8785b441aaecd0aaf153fc6ca3a4e851b048ec977874fed56 2118 alberta_3.0.0-1.dsc 8faa2fe28f8172549e03df5fc5ad6e97540b777bfbfc88f0d16f953c39b80156 812604 alberta_3.0.0.orig.tar.xz e02c2c8f7d95740281e22ad54c29d25f277f442c80292e960fe2b4131f1209e7 3744 alberta_3.0.0-1.debian.tar.xz be3fb35580b37e0fe7db9c144c172cb19990f204c184a1034ad9d20ee233926f 163730 libalberta-dev_3.0.0-1_amd64.deb 6284e9732e0bb792c722dcde1b3585634ef824eb7837b43f8b361edc6b0f9a19 802040 libalberta4_3.0.0-1_amd64.deb 9daf9065ea0937bf805456c062de2f5bc36728bc7382af4a8a77a10c667fb39c 2833614 libalberta-dbg_3.0.0-1_amd64.deb f4cdb09696391eecb78331d430d121007dab83efa74561d4b4446e75807955d2 91176 libalberta2-dev_3.0.0-1_amd64.deb Files: c0ac95f4befe086b8d5f90b0d24b83a8 2118 libs optional alberta_3.0.0-1.dsc caa8e073f03424727c62b0d41f1f41d7 812604 libs optional alberta_3.0.0.orig.tar.xz a5d0c7c36f20cc1ba4048ef126dcd8eb 3744 libs optional alberta_3.0.0-1.debian.tar.xz 524eeec87195eeb361c80c21ae7dc266 163730 libdevel optional libalberta-dev_3.0.0-1_amd64.deb 45fad36a6a8c0d55be829e3c69b45262 802040 libs optional libalberta4_3.0.0-1_amd64.deb 8391611489136e090f3e93e11b51bb38 2833614 debug extra libalberta-dbg_3.0.0-1_amd64.deb 100e0d8eb277fb870f812b374c8ee9a7 91176 oldlibs extra libalberta2-dev_3.0.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTWDvFAAoJEIATJTTdNH3IUHsP/RdEq+O8nTTgamENm+Xg+PeL Axy+7F0ec2rBjAa53Lx0MlGVbVcKGLHSHm9tvRYulvdXG0Xt7pVsB2NxwszIwY2g pjSRZxLOxCUYE5DccBvDWcxFq6pVMLW+I5RJ1hOzo1p1DY38r+HVHPLgybSeVlWT MR5e5RoGSsuBhn5LKSeQuR8IVLSN3lqIW57sjLMujF3mmCwoL+4WgZGegh9xFYWw /3Y/R44k3yzclQqsBCH47ubYemR6UWzWNjKQ4qxSGYm4X3EHW47oI6fT6Hhe2jzD 3CNNhzEWHogFDwsdZjTuvHQYm05gCNyCiZSg7jmzi6xTEAXqQZw6suDRrPf8STUT h8BLWuIINz1WKeB106TVDmX3/yddMH4OFSuA4Alpn2DVPwIT/PSUCvM+C9MQijpC AEDehDksKpOCLC4IniLY87Rta3T8OKbcV1iRnAxX6qE1fpVtHQCB7Z8S1cpHFKfk N4Nh7aGJOEqm7KDwcnKCAJWCPSch1+UY8vOIbzjDO7vWAenw9Lp/s1LQNm6CCQRC mZNFFtgKh9ZIHz1htgEkkpj0gb6bcURnJHZ9X+43zSbpwHdVr/iBqOQOBIMYlFzk ZcPPUBEXN6yijIaGc1tCSRGPecY43hAIDPXLxouJV79B+ulmg0wAqTlMLck4vq7g vspxvnRq7RLVwaSX1VNP =6J+p -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjotp-00043r...@franck.debian.org
Accepted weechat 0.4.3-3 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 12 May 2014 12:49:14 +0200 Source: weechat Binary: weechat weechat-curses weechat-core weechat-plugins weechat-doc weechat-dev weechat-dbg Architecture: source all amd64 Version: 0.4.3-3 Distribution: unstable Urgency: medium Maintainer: Emmanuel Bouthenot kol...@debian.org Changed-By: Emmanuel Bouthenot kol...@debian.org Description: weechat- Fast, light and extensible chat client weechat-core - Fast, light and extensible chat client - core files weechat-curses - Fast, light and extensible chat client - console client weechat-dbg - Fast, light and extensible chat client - debugging symbols weechat-dev - Fast, light and extensible chat client - developement headers weechat-doc - Fast, light and extensible chat client - documentation weechat-plugins - Fast, light and extensible chat client - plugins Closes: 747708 Changes: weechat (0.4.3-3) unstable; urgency=medium . * Add patch (backported from upstream) to fix a FTBFS while building against ruby 2.1 (Closes: #747708) Checksums-Sha1: 629b6cc2ddf685d7e3bfae0f22f110db1a905d76 2391 weechat_0.4.3-3.dsc e045e3923d67bf61894495fc89eb59c7d0eec92b 14880 weechat_0.4.3-3.debian.tar.xz ea8313012db4a73dbbca45a5db737a180915195e 44428 weechat_0.4.3-3_all.deb 182792449120d21df6e651e64653dbec2bb864e9 341816 weechat-curses_0.4.3-3_amd64.deb b2cb9ee240befe90ac8dee9f9b3688db80bf832c 587658 weechat-core_0.4.3-3_amd64.deb 44eab7ac50622541908768b910babb965d5e0087 343172 weechat-plugins_0.4.3-3_amd64.deb 47a6c6bb39bbe4aa3f1a45b4af605b186aa87298 721890 weechat-doc_0.4.3-3_all.deb 618dbb0ae78d7a6f23b7199c714d6487906119ed 55340 weechat-dev_0.4.3-3_all.deb 51393bd7f5784ce431f98ece7577575f09b68f6f 2597192 weechat-dbg_0.4.3-3_amd64.deb Checksums-Sha256: 13cdb6d54181eb745040b0b1f1c93bd0048a74eba80ed6a678c05ad2f22430c8 2391 weechat_0.4.3-3.dsc fe5c9996cc4c2a284c2aced7449816ef32a89fb2d035c404d5274cb5b8811fd3 14880 weechat_0.4.3-3.debian.tar.xz e4a8f9200fda39b2ff986eb4dd453760162e340427f239f79780053bd6986087 44428 weechat_0.4.3-3_all.deb 6a0cef97c744f12e0113031457208d7ee716e78f594a250772634c82474ae5fe 341816 weechat-curses_0.4.3-3_amd64.deb c47a68508b34324196bc345d8fd412d375eaa8e2a27b819cff8a199bd26de6f9 587658 weechat-core_0.4.3-3_amd64.deb 97261b826429159d1f11487736e080e17417e2f451535b3d4f2d0415e415a163 343172 weechat-plugins_0.4.3-3_amd64.deb 2340b36357f3bd8df4495d1cf6d6bfe80ad1cf9f12d25e63ea446550f8809ae2 721890 weechat-doc_0.4.3-3_all.deb 9bb7eda93c17dc53d8ef96b1011c17ec50111fef135a46f332e5c67845590ac8 55340 weechat-dev_0.4.3-3_all.deb 347c0fd3ea58db922c773e3e764a8d90c2b5ff2c48b75e9988083d4c9c61c673 2597192 weechat-dbg_0.4.3-3_amd64.deb Files: 34aa6585731270a06735fea2ccdd0894 44428 net optional weechat_0.4.3-3_all.deb 1205f109dfb562072b3c3af2ea86b603 341816 net optional weechat-curses_0.4.3-3_amd64.deb 4dbe4af2fe452be3ffb35de12fe6b90d 587658 net optional weechat-core_0.4.3-3_amd64.deb 70ebfa465bc40ad19b462b413a6cf216 343172 net optional weechat-plugins_0.4.3-3_amd64.deb 8af4a66249ea7d6837d9c406c5355902 721890 doc optional weechat-doc_0.4.3-3_all.deb ed3f6da04abcb6bd5fdaa33809996961 55340 devel optional weechat-dev_0.4.3-3_all.deb 43d63be00f1e0829b097f27ff9b7cde6 2597192 debug extra weechat-dbg_0.4.3-3_amd64.deb 5132fd6eacb2654cb0d3f47d0c7882c2 2391 net optional weechat_0.4.3-3.dsc 5c516f27c2403c0de8d3bd99d1edd3a8 14880 net optional weechat_0.4.3-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTcLX/AAoJEEsHdyOSnULDi+0QAJUheUz8H4Ou346W69IWZrbi QyoLTaxsjPRGNOhRe6ImkhoV1MXFVskgyln4vUlQ1Q4yyHXqamreJYCBR2YXGbhh QZBa0bslIQwm7+Wk9WYhi3S0UB9VKuL9J30m3BhirhrKEz32tFxJN85rP34tgZ00 0dL14u8vaOIN8MdiVqLgfozewHJxBSZs3rItPzwAFVUij0njNsS9HdfHPlV5zzvh /McKFhIKbvSAl9HByft547csGLgdkVH6f02+i3q1lpazXELToI253AyG10HRr3N+ w+lupqVPLJ6cpNb/H6VhX2MWHpoy3DzfenCCMIm6AJ1yUOSllZx5JhhkEAf98A7L q2AOm3Hy1UawjdbmBq1Q6Utjj6M5ffLhGNZ+7X0/aSzC0hsWtIVltRejnnpBRBuC JlBnILvdLtpAG1TVQXcXgjscDmpgaPtct/vZ0sj2RfX4pDfKG2GDQJGQYhXAYQSz iy5wqEjZjhhO94M1Wa0THBdoCA6yjcv3x357o9H8nG9ofwMeJ2RcCY7FmCcBwahu 0/TIqqsCQKYxH7p7RCHjr0ByTc8O/+dk/enj2MwolbTx/Z9Y53OmmmSu7DbRyXU2 u98AwOFutdPomPJQeNH5rPfDY0/E/MFgv4XjjxgCen2JCGpg7M29YvMVBC1W2ONa VlMKB0swufD1hZggvyXF =qAw1 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjozg-0006fw...@franck.debian.org
Accepted jmagick 6.6.9~20130201-svn99-2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 May 2014 13:32:28 +0200 Source: jmagick Binary: libjmagick6-java jmagick6-docs libjmagick6-jni Architecture: source all amd64 Version: 6.6.9~20130201-svn99-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Sylvestre Ledru sylves...@debian.org Description: jmagick6-docs - java interface to ImageMagick - api documentation libjmagick6-java - java interface to ImageMagick - java classes libjmagick6-jni - java interface to ImageMagick - native library Closes: 747856 Changes: jmagick (6.6.9~20130201-svn99-2) unstable; urgency=medium . * Team upload * Standards-Version updated to 3.9.5 * Use pkg-config for the imagemagick transition. Thanks to Bastien Roucaries (Closes: #747856) Checksums-Sha1: 932dcd4c6fb8d9512474c59e0d4d05307e5e43f9 2259 jmagick_6.6.9~20130201-svn99-2.dsc 538744f65a73d1d0d34828181fe7104a5d2e218e 7748 jmagick_6.6.9~20130201-svn99-2.debian.tar.xz c7b1a33117a47b84b44121877a43854de0c88acc 36150 libjmagick6-java_6.6.9~20130201-svn99-2_all.deb 5868365e91254fa15db69879fd8737e5d9d27b03 131838 jmagick6-docs_6.6.9~20130201-svn99-2_all.deb 16e270b9f77236b48c74da162175723b6fd92e08 37166 libjmagick6-jni_6.6.9~20130201-svn99-2_amd64.deb Checksums-Sha256: 43050cae0eedf1d7fcf551417295cdb7ecfcc23b5151911b8d2a8126522a8d12 2259 jmagick_6.6.9~20130201-svn99-2.dsc 7d50b16c77c08b0520705d7da0b472c8247e279d963060dd6263ce8c5ea36762 7748 jmagick_6.6.9~20130201-svn99-2.debian.tar.xz 864fcb4c1b65e04f21c3366a1429400d8d19556ba92c432183ad67b16292fc45 36150 libjmagick6-java_6.6.9~20130201-svn99-2_all.deb 06fb6cceed60c83e2782d79009e5aa237b62d1507d3e4bcc77945d301fc99f2e 131838 jmagick6-docs_6.6.9~20130201-svn99-2_all.deb 5a232778a5a1852eb980862bf36805591e6a0601ed2143d8dde4d7a82591d1d1 37166 libjmagick6-jni_6.6.9~20130201-svn99-2_amd64.deb Files: c06a439434ef21fbb3f490df6310e9e2 36150 java optional libjmagick6-java_6.6.9~20130201-svn99-2_all.deb ef162c4ed997722c8704535199f6e4c0 131838 doc optional jmagick6-docs_6.6.9~20130201-svn99-2_all.deb 7d9b5e9f81f6f7646cd3bb5b0c7df278 37166 graphics optional libjmagick6-jni_6.6.9~20130201-svn99-2_amd64.deb 78d502ffbdb9d318d224eff828c8e5be 2259 graphics optional jmagick_6.6.9~20130201-svn99-2.dsc 64093b933112db46de9a5700449e9252 7748 graphics optional jmagick_6.6.9~20130201-svn99-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTcL5AAAoJEH5lKNp1Lxvhc24P/j2n8Rp8NQWL/GpAC47q23GE xmlbMJ+oTYBDND9yqwuFWdbtZSiPXDY5oJk0V5p+5bYfweY/rdeaQJeRy56WgFYg yjNcq0iEWFyUH6t+rjQJAd6e+UUfsrug9dpRgeeM/ANLysX/1pQCCQSCix0jikWf 7eBQDIauKt2muFlQIrJJ9N0IiwjSsa1UpD2eBrID7yMZLh996hb14emH3/VTzsIy PwK5xBW7pWZqFtZm7NzwvwIYiz5eP2Kt0Pjo+jOIJvOFfAwoe9UsF+TRJFrFtq49 aS+HLgmtEdlJE9r9xaF22s5XLB805ObefUgubOoQnW4XPygtP2qMxtNiZ/3ahovK hBE1cset9/LLso7zLkdfsshtgVLICQKee7pbyJd7xRo6SHTAfX7WiEJkPwhX2mRO UNmXydbfkxp+0+wCY+OQdg0yLhlPsdp4+xI4vuzGrMVCsH0YCfPkC3rwiHgCtBJD +OqCVs9nDAnRWWq+iwb5EdRqQJZ7HNZraJk4vBWmoSyBvD9KENDF0dMWnIofytyI xeQ0gq2njepl7jmR5NjBaYospeyTzYhtWytCCu+3jN++tasdgISG0WuYLuu/7Ouc Bcb1jtu1TQqtPMYdXItgs243pBL9ZWYEb0Z5uk6LyA8sE48+UJcicMCrbvVkbFE+ tG2e8a0U3mWtBaRcPlV8 =6Ba+ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjpfm-0004y8...@franck.debian.org
Accepted mandos 1.6.5-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 11 May 2014 22:16:33 +0200 Source: mandos Binary: mandos mandos-client Architecture: source all amd64 Version: 1.6.5-1 Distribution: unstable Urgency: medium Maintainer: Mandos Maintainers man...@recompile.se Changed-By: Teddy Hogeborn te...@recompile.se Description: mandos - server giving encrypted passwords to Mandos clients mandos-client - do unattended reboots with an encrypted root file system Changes: mandos (1.6.5-1) unstable; urgency=medium . * New upstream release. * debian/copyright: Change year to 2014. * debian/control (Build-Depends, Build-Depends-Indep): Moved build dependencies of mandos package to Build-Depends-Indep. * debian/upstream/signing-key.asc: New; upstream source public key. * debian/control (Standards-Version): Updated to 3.9.5. * debian/control (mandos/Depends): Remove the dependency on avahi-daemon (= 0.6.31-3) | systemd-sysv. It is unnecessary since we have a workaround in debian/mandos.postinst anyway. Checksums-Sha1: 9ae5eef6db9f5d086c87a04f220d8035f80f7672 1865 mandos_1.6.5-1.dsc c6f0e01eae44ab5473362077d6dfa3c7835c4504 162094 mandos_1.6.5.orig.tar.gz 62cfe538146592db3883e8b9d19655933564a119 12684 mandos_1.6.5-1.debian.tar.xz 60123bf3816309dc81a8ccc9b47c8da96232d9eb 78210 mandos_1.6.5-1_all.deb b00f9a089f32560bde74feccd5d66366d0351a25 89554 mandos-client_1.6.5-1_amd64.deb Checksums-Sha256: c302b44b3896412988daa620031cf1a4ebdee16bb1405ebbad82980c1eedb7ba 1865 mandos_1.6.5-1.dsc e7007c61c34f3bb640311e00d50e74736289c748d0c688765c28cff72710b637 162094 mandos_1.6.5.orig.tar.gz d4d46d08977e559cb979520bc573a1642caa27ecae63f30660201554b54125e4 12684 mandos_1.6.5-1.debian.tar.xz 037e4bc2a9f83ba6d8c5875538c28fbd9430885fd327022c0ba16df28f0a1f15 78210 mandos_1.6.5-1_all.deb abe11c930877f8ad7dedb916e8e954987436bf54f168b7a98dc1d402efb0e80c 89554 mandos-client_1.6.5-1_amd64.deb Files: b83067558867a165cfff001994160e7a 78210 admin extra mandos_1.6.5-1_all.deb 1aa4b48b41ed3310f43cbc87d2163943 89554 admin extra mandos-client_1.6.5-1_amd64.deb a399b2ebec61219bf16353be55788828 1865 admin extra mandos_1.6.5-1.dsc 124a352bac747dd4a1c2915fff97e56b 162094 admin extra mandos_1.6.5.orig.tar.gz 32dec7c3f145ff8f913eecac6149a791 12684 admin extra mandos_1.6.5-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCgAGBQJTcL0DAAoJEPfuYW7gwgz/XBYH/2W0zyaGNXSHrtnwCK4fBTyc iWU52B+VGldeJZqI/cEMLuBjUCuZoDMOp6vD9ggAnjLgspJGqCtIb0JG5WtFM4Jd dzrJth1i0zHKYHuAqHF/6uzndrypZDUFGFkUZg+Q7i6LBnMXSXtil4CDqsZEEWzn M+mBP6evdAMlalbFCSpnbiHGWX7MfcLPZAaIDDeqBGqn57vzMALhGWZccoX3FOXd PqQKy9RGBXhrqJe8olKJ7qN8w2bEK4ZJcsd0sCYHoyPtUVcqHrMYlDjrZQRcks/g s1VyhkXt9p6EGmIVTcLbRIg7P05+dSqHcV433Ay3r9OK1SV3FqpdUSHcXKnyXGE= =JTRQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjpfw-00052e...@franck.debian.org
Accepted fusionforge 5.3+20140506-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 06 May 2014 15:20:39 +0200 Source: fusionforge Binary: fusionforge-standard fusionforge-minimal fusionforge-full gforge gforge-common gforge-web-apache2 gforge-web-apache2-vhosts gforge-db-postgresql gforge-db-remote gforge-mta-exim4 gforge-mta-postfix gforge-shell-postgresql gforge-ftp-proftpd gforge-dns-bind9 gforge-lists-mailman gforge-plugin-extratabs gforge-plugin-globalsearch gforge-plugin-mediawiki gforge-plugin-projectlabels gforge-plugin-scmgit fusionforge-plugin-admssw fusionforge-plugin-authcas fusionforge-plugin-authhttpd fusionforge-plugin-authldap fusionforge-plugin-blocks fusionforge-plugin-compactpreview fusionforge-plugin-contribtracker fusionforge-plugin-doaprdf fusionforge-plugin-extsubproj fusionforge-plugin-foafprofiles fusionforge-plugin-globalsearch fusionforge-plugin-gravatar fusionforge-plugin-headermenu fusionforge-plugin-hudson fusionforge-plugin-mediawiki fusionforge-plugin-message fusionforge-plugin-moinmoin fusionforge-plugin-projectlabels fusionforge-plugin-scmarch fusionforge-plugin-scmbzr fusionforge-plugin-scmcvs fusionforge-plugin-scmdarcs fusionforge-plugin-scmgit fusionforge-plugin-scmhg fusionforge-plugin-scmhook fusionforge-plugin-scmsvn Architecture: source all Version: 5.3+20140506-1 Distribution: unstable Urgency: medium Maintainer: Roland Mas lola...@debian.org Changed-By: Roland Mas lola...@debian.org Description: fusionforge-full - FusionForge collaborative development tool - full metapackage fusionforge-minimal - FusionForge collaborative development tool - minimal metapackage fusionforge-plugin-admssw - collaborative development tool - ADMS.SW plugin fusionforge-plugin-authcas - collaborative development tool - CAS authentication plugin fusionforge-plugin-authhttpd - collaborative development tool - HTTPD authentication plugin fusionforge-plugin-authldap - collaborative development tool - LDAP authentication plugin fusionforge-plugin-blocks - collaborative development tool - Blocks plugin fusionforge-plugin-compactpreview - collaborative development tool - Compact Preview plugin fusionforge-plugin-contribtracker - Contribution tracker plugin for FusionForge fusionforge-plugin-doaprdf - collaborative development tool - DOAP RDF plugin fusionforge-plugin-extsubproj - collaborative development tool - extsubproj plugin fusionforge-plugin-foafprofiles - collaborative development tool - FOAF Profiles plugin fusionforge-plugin-globalsearch - Globalsearch plugin for FusionForge fusionforge-plugin-gravatar - collaborative development tool - Gravatar plugin fusionforge-plugin-headermenu - Headermenu plugin for FusionForge fusionforge-plugin-hudson - collaborative development tool - Hudson plugin fusionforge-plugin-mediawiki - Mediawiki plugin for FusionForge fusionforge-plugin-message - Message plugin for FusionForge fusionforge-plugin-moinmoin - MoinMoinWiki plugin for FusionForge fusionforge-plugin-projectlabels - Projectlabels plugin for FusionForge fusionforge-plugin-scmarch - collaborative development tool - GNU Arch plugin fusionforge-plugin-scmbzr - collaborative development tool - Bazaar plugin fusionforge-plugin-scmcvs - collaborative development tool - CVS plugin fusionforge-plugin-scmdarcs - collaborative development tool - Darcs plugin fusionforge-plugin-scmgit - collaborative development tool - Git plugin fusionforge-plugin-scmhg - collaborative development tool - Mercurial (Hg) plugin fusionforge-plugin-scmhook - collaborative development tool - SCM Hook plugin fusionforge-plugin-scmsvn - collaborative development tool - Subversion plugin fusionforge-standard - FusionForge collaborative development tool - standard metapackage gforge - Dummy upgrade package for FusionForge gforge-common - collaborative development tool - shared files gforge-db-postgresql - collaborative development tool - database (using PostgreSQL) gforge-db-remote - collaborative development tool - database (remote) gforge-dns-bind9 - collaborative development tool - DNS management (using Bind9) gforge-ftp-proftpd - collaborative development tool - FTP management (using ProFTPd) gforge-lists-mailman - collaborative development tool - mailing-lists (using Mailman) gforge-mta-exim4 - collaborative development tool - mail tools (using Exim 4) gforge-mta-postfix - collaborative development tool - mail tools (using Postfix) gforge-plugin-extratabs - Headermenu plugin for FusionForge (transitional package) gforge-plugin-globalsearch - Globalsearch plugin for FusionForge (transitional package) gforge-plugin-mediawiki - Mediawiki plugin for FusionForge (transitional package) gforge-plugin-projectlabels - Projectlabels plugin for FusionForge (transitional package) gforge-plugin-scmgit - Git plugin for FusionForge (transitional package) gforge-shell-postgresql - collaborative development tool - shell accounts (using PostgreSQL
Accepted admesh 0.97.3~git~3518914-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 09 May 2014 23:05:05 +0200 Source: admesh Binary: admesh libadmesh1 libadmesh-dev libadmesh1-dbg Architecture: source amd64 Version: 0.97.3~git~3518914-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Anton Gladky gl...@debian.org Description: admesh - Tool for processing triangulated solid meshes. Binary libadmesh-dev - Tool for processing triangulated solid meshes. Development files libadmesh1 - Tool for processing triangulated solid meshes. Shared library libadmesh1-dbg - Tool for processing triangulated solid meshes. Debugging symbols Changes: admesh (0.97.3~git~3518914-1) unstable; urgency=medium . * [171e567] Imported Upstream version 0.97.3~git~3518914 * [ac88834] Remove old patch. * [2a8af4e] Update regression test. * [7edae5f] Use autoreconf. * [7b699ba] Update copyright. * [0a4fbaa] Set Standards-Version: 3.9.5. No changes. * [eb7f6b3] Change homepage of admesh to GitHub. * [81f7590] Add libadmesh1, libadmesh-dev and libadmesh1-dbg binaries. * [9350e91] Update debian/watch. * [d0719ec] Add autopkgtest. Checksums-Sha1: 4e51d0c6f359bf057294f6e23d53f4d1181064b6 2211 admesh_0.97.3~git~3518914-1.dsc 4816d3cae09943041aa7062ea39158fc1574c166 33472 admesh_0.97.3~git~3518914.orig.tar.xz b49e6addf330004beb4e65e9bb4e8ce9e5137ee8 5784 admesh_0.97.3~git~3518914-1.debian.tar.xz 040531370e6426b903174acf14289c4463d73bac 21960 admesh_0.97.3~git~3518914-1_amd64.deb d8ac17bfcc5d4b62906f268199f49b44ae1a6106 21602 libadmesh1_0.97.3~git~3518914-1_amd64.deb c54b0ff967a882a67796ac74b4d309c336f1303d 6012 libadmesh-dev_0.97.3~git~3518914-1_amd64.deb f4550167781d9b38fe04de9f7cd273c8afb13f1b 47484 libadmesh1-dbg_0.97.3~git~3518914-1_amd64.deb Checksums-Sha256: 4354bd8fad6939336314325581b0172c6d08dce2bbcf4500dec754f45a87295b 2211 admesh_0.97.3~git~3518914-1.dsc 17de6af2e4fc7d268b15d0e669a6c55e080557fd5def8ffd04d4e40365d2d99b 33472 admesh_0.97.3~git~3518914.orig.tar.xz 938ace3a87b48a401b86e4d2f2568164559a230e800c84fd377aad487793c94e 5784 admesh_0.97.3~git~3518914-1.debian.tar.xz b5f9c099b4983ca1ba534d43a28ce60201a68bda0f7fc77e81c19905d00dcb88 21960 admesh_0.97.3~git~3518914-1_amd64.deb 23e517fea63b01107feb2f654e13de86193ac668c2c266e5bda57cc7531ac48d 21602 libadmesh1_0.97.3~git~3518914-1_amd64.deb e18d5e6c6b060259f9ac9a0bac3dab5d40cc0a69b49eda2f395e3208bb955126 6012 libadmesh-dev_0.97.3~git~3518914-1_amd64.deb 03d889c74dc2f225a43488a58a9bf06070e8a40041718694bdc30c9b777db851 47484 libadmesh1-dbg_0.97.3~git~3518914-1_amd64.deb Files: 13d1537b2d04db47fe2eea761b52a72e 21960 math optional admesh_0.97.3~git~3518914-1_amd64.deb bf75cf74bb8b27c7b6691b7585f141b3 21602 math optional libadmesh1_0.97.3~git~3518914-1_amd64.deb a8a1e98d5c539815b3cc7c858265fa7f 6012 libdevel optional libadmesh-dev_0.97.3~git~3518914-1_amd64.deb 7824cb8f49476b7de5b53052e47365d4 47484 debug extra libadmesh1-dbg_0.97.3~git~3518914-1_amd64.deb 27526feebcdd93d69d20f2efe52c13ad 2211 math optional admesh_0.97.3~git~3518914-1.dsc 625e6a901193b70d43fd61a2a4f4645f 33472 math optional admesh_0.97.3~git~3518914.orig.tar.xz da27c841845c1f29e4b8214153b23b4a 5784 math optional admesh_0.97.3~git~3518914-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJTbUs/AAoJENPhc4PPp/8GV4kP/RGlrXOzRxHI0sZwK3aj/KFY zxzn2bCzFdMr8aJhxLMX3irXJ6yBozArMth5MsywsAyM23+0aqYQvFBfV/3Sa0CN uBTRIlt30BRt/j5lRs0T5XtCw4E22aOGwy7lhiraEacKkHcdVmUiIz3VuDS+M3HN kWUY7cGp/H8Y+Lfpw5qJvl4wLR8y0cucIHDbP0OHjikIZU8IrmfDlIxFOoHWWxDF lSNmu1ekbS3xLs+SQRSEoR+7Xjq7Xcw53kQ3tzpHUz6ceun4RN4Q7fOtch7IYLvo rhFMF0lupqRtCrSms2LIzxMz+tqQQy8+EIKuXuSFI1RWDfhBWdHud4wetOYSF4pL 78KISj3XxZQAYwOsCEdsvoQeHDDbDto5Vhmx5lLbggGDKO9TLIFTV3yW8XJif1uA +dn4ZN0EUepP1od6EzNp/zwhLZwQ3thp7ZDo93xymv4MpTb1+TqZfEToJZiFQEMt lnn+vOELhcnDW0YRCJK7v0PYDgaK9Y1IgXnZgikO4hlniLkW3bWxawpS3hPondxz fQNCVJR1aGfmbbJijXD5OEoyG7BPsLihQ5aPUdF+3gVxEkkLXR9JAOAhZ4ju+uA3 aFArDJi0P+ekFEi5XTogsQn2wiFtXMurSjAZYMRwVDuHGf4Z+E6vB1iDEeXmfjmM ze8gBGU+wa6MCIJumCnS =/0o9 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjppt-0006k9...@franck.debian.org
Accepted tanglet 1.2.2-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 04 May 2014 12:10:14 +0200 Source: tanglet Binary: tanglet tanglet-data Architecture: source amd64 all Version: 1.2.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Dariusz Dwornikowski dariusz.dwornikow...@cs.put.poznan.pl Description: tanglet- single player word finding game based on Boggle tanglet-data - single player word finding game based on Boggle - data files Closes: 617539 738038 746458 Changes: tanglet (1.2.2-1) unstable; urgency=medium . * Imported Upstream version 1.2.2 * Added keywords to desktop file and menu entry (Closes: #738038) * Updated copyright to DEP-5 * Added VCS fields to d/control * Watch file fixed * Migrated to dh * Compat changed to 9, bump standards to 3.9.5 * Updated manpage (Closes: #617539) * New maintainer (Closes: #746458) * Split packages to tanglet-data and tanglet Checksums-Sha1: 9fa8c729deffb4ad213a8b79320efe2c45436ae9 2018 tanglet_1.2.2-1.dsc a2fea31a483097d1a6c745c6ec774ff082f28792 8102968 tanglet_1.2.2.orig.tar.bz2 719eb85fb2763c36ed32c890eef6b61fc860e3f1 3292 tanglet_1.2.2-1.debian.tar.xz 3309bf4936a6c17cca8292cd779c168e730804ce 213846 tanglet_1.2.2-1_amd64.deb f502f14d389fe44860e45d70cc9caa6e8108ef07 7299622 tanglet-data_1.2.2-1_all.deb Checksums-Sha256: 29d6093f551434cbb2b7a50db98a7a79d94e906d3dcb4def2f774e1bcb702b5f 2018 tanglet_1.2.2-1.dsc c90d5c36b7e6cca54cdc001c7eecfb333795add16e6ae01f100026c61f4a84da 8102968 tanglet_1.2.2.orig.tar.bz2 6347a942f121f73891df9182925ad4cb0224ae459122db2fe6253b1f11d25882 3292 tanglet_1.2.2-1.debian.tar.xz 6b0b7d1582779317b7bb84f3d84ee69708fba60466e5b03b1d9dd0727899a6c5 213846 tanglet_1.2.2-1_amd64.deb a0e95839c4563ea94954c13396f429deb20de64ea9c6c3103502dd8cc313b781 7299622 tanglet-data_1.2.2-1_all.deb Files: 8b6ee64eeb9ff93e16f04507d24736de 213846 games optional tanglet_1.2.2-1_amd64.deb c19f5c21536ed167b4e3a849dc5706c8 7299622 games optional tanglet-data_1.2.2-1_all.deb 94ff7b431798981a92307220b985ebb6 2018 games optional tanglet_1.2.2-1.dsc 584e50d01323c0686ff094195eba4341 8102968 games optional tanglet_1.2.2.orig.tar.bz2 bbee7600bea369b38f3b80cc9d1d5f0d 3292 games optional tanglet_1.2.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTaIKNAAoJEI7tzBuqHzL/GPcP/iSkIRMIkSApf6qLCUSZS7jU BE1QCvF5cGJS8CWrQJPqTucKUAuSeeyukhIrZnJZZn6GaTPFJardeY3a6qc1FG5F NiA1PLqN1evSP4DLc+lGyPrwQEjzqAKLqnRYn0B5UGjT/xrychCYDC4DwGSX8hX+ 9noawu4Yz37IKj+lulz8iB6AuSGzYrlMPNPvCDnXp8Pe8XRkOml9oXlSjnJucP0A 0q5DXcaCyw+OSDIHtX6Xu14qB/AehFpQvjcm6CfTSYtEZjs2UFW1pMa8n5Z+Bbdu px3cNWBRBSaGlGVZl8zXQ6THDSwAUwnLGmvuiSZ2cEAM/vadxPrhhfydrw834nbE CSfyX4REz0lih9L7ufRN3mrN2idNU3jWXgK+YQoabDxWWY+UsT2+dDzTGrBxCV56 AGbD3rqGb+0sO9cfVRkENOYH3onSRvnrYl64eWkM26qC7RNOZTGMR7iluB/xJoFt aaqLKQV4zJkOm1AswraP9NjxtB8laymejxdRPIVvjABnhERzFr8qK5+7vAvpsEco 4qhSzzxOnrBex28UIt62WV/t68RChMl3wtyFVaV0J6VH2ZaoYau40w3iVW9m2d2y aH4lCLS0lave5QHLRnb/dEc0aVS1Z1V1yv/Jfr+C/YxghfetDZFbXny6aWY8CIq+ ak0DNr4J6VFA6zvgrMum =jU5r -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjppz-0006lh...@franck.debian.org
Accepted python-neuroshare 0.9.1-2 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 22 Apr 2014 15:12:14 +0200 Source: python-neuroshare Binary: python-neuroshare python-neuroshare-doc Architecture: source amd64 all Version: 0.9.1-2 Distribution: unstable Urgency: low Maintainer: G-Node Debian Team debian-t...@g-node.org Changed-By: Christian Kellner c...@xatom.net Description: python-neuroshare - Python interface and tools for Neuroshare python-neuroshare-doc - Python interface and tools for Neuroshare Closes: 684746 Changes: python-neuroshare (0.9.1-2) unstable; urgency=low . * debian/watch: - update to point to GitHub release page . * debian/rules: - add get-orig-source target to fetch org. tarball . python-neuroshare (0.9.1-1) UNRELEASED; urgency=low . * New upstream release (0.9.1) . * debian/patches: - Drop all patches (fixed upstream) - Add a patch to remove sphinx-pipy-upload - Clean _capi.so from neuroshare (inline extension building) . * debian/rules: Fix building of documentation . python-neuroshare (0.9-1) unstable; urgency=low . * New upstream release (0.9) . * debian/control: - Add python-neuroshare-doc package - Switch to dh-python - Depend on dh-python instead of python-support - Remove XB-Python-Version and replace with X-Python-Version - Binary package depends on python-h5py (Closes: #684746) . * debian/rules: - Changes for dh-python support - Build sphix documentation . * debian/patches: - Add patches to fix doc package building . * debian/source/options: - Ignore *.egg/ directories Checksums-Sha1: 7960dd7db5522103b86c3994ddacd8453d0c6d5d 2158 python-neuroshare_0.9.1-2.dsc 64a219bbb2664a771d5c8e5883e3273581ee92d0 114366 python-neuroshare_0.9.1.orig.tar.gz 8ef617adfb3da4a71778e05fb34365061f31b5f7 4112 python-neuroshare_0.9.1-2.debian.tar.xz f00dfe6381e5e98879c109674e9e22f3f49bf2bd 19390 python-neuroshare_0.9.1-2_amd64.deb e913958731c0e6f613842418d6a217db92b95108 94506 python-neuroshare-doc_0.9.1-2_all.deb Checksums-Sha256: c82e9491c8542ff82b857f2e8a05d28e495426fe6f7b76bd4e6869c1046b015d 2158 python-neuroshare_0.9.1-2.dsc c425373b836151221383289ffd17e85ce3e12541b58aaacd14133e1fa8cdd9b9 114366 python-neuroshare_0.9.1.orig.tar.gz 225c86900560d792cc374fcac6429b42efbdb9fc00feb22678418e289a6665f2 4112 python-neuroshare_0.9.1-2.debian.tar.xz 6b890c192dbcdd153a5ff7f2d3ebc174030eaf0c1d9e46f087635c98bfd4e410 19390 python-neuroshare_0.9.1-2_amd64.deb 07de72b200fa40de88ca36ab810fb1c7b5d7395d0f5d60b3e1d7f0bb37229977 94506 python-neuroshare-doc_0.9.1-2_all.deb Files: 89ded5cd0ae4f233da04985b034b792b 19390 python extra python-neuroshare_0.9.1-2_amd64.deb f7eeb267af53850dcd742ada7a45db2b 94506 doc extra python-neuroshare-doc_0.9.1-2_all.deb f797e1f0ecae7e81ccaedba4ac799015 2158 science extra python-neuroshare_0.9.1-2.dsc 2ad28d90fd3dbd41b4a320e6e456a5cb 114366 science extra python-neuroshare_0.9.1.orig.tar.gz b74d862212c3db16afe1bea9f3ffe19b 4112 science extra python-neuroshare_0.9.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJTaSndAAoJEMBz0ih/+56bDIkQAIGI3ENj7IPeWkVpx66gnJcV j7+JE9MK+rbaId8+xSaKc1Fq3l6AGqFluelSpGRh5fn3Rl7s9k/PHCJDEjDDEsRI uSm187/FpI/8stzTKAQ1x68B6J3bb8gZXFbvunwDj2gX0oDpO7Nzz68aSmjUyKkW Vvw1pSbRis/7Vulek+3/7BV8P9uON+7gTANEsJfSrKyNGNZvc1It8SGK4fD+KFfj uTO8y00kbVU1v1DqSXUE7+Jmf8kMBbzdwSQ9HDNbnK0l9oOHaq1Xw1t2Cu0xlkuu LZn/69T4GFW/acojAjWV1Wf0f2Jhy6JhzUfZ6AHzgzKqXz97XPt1RHaVLk5zcrrV C77NEeqZEjZf4I+cVyNJ8ADb1Ys5EnFgxN+eBc3LGWfE+svZJw7u+ZyAMJ5K4FDd MJX7x0NWrehB+EBmcWDl36voQvmFLhYHuwl6DkJmIWn/1htJ0mlnuJh1u1eS/eDT a1HyDp5jSCsH+couJ9DMxU1O/PnH2KBedVTmb28TIO74ifiDGXNbB3PZ5zJpF7CH 6koxJdF8gm3foQlt2bOlhoojVggcny+Eo/CL5c0wjSXTlOxJ8uK/1rqKyNhZgnLT 1FH0F/s895V3JJMvDYMTbz1dmdtkj1sfpKIrCNoZrftcykz8HLLK9wszgnLWYP5x EK5DYn9DwZA86kmSRfSq =s08p -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjppy-0006lo...@franck.debian.org
Accepted hardinfo 0.5.1-1.4 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 07 May 2014 21:12:18 +0900 Source: hardinfo Binary: hardinfo Architecture: source amd64 Version: 0.5.1-1.4 Distribution: unstable Urgency: medium Maintainer: Agney Lopes Roth Ferraz ag...@debian.org Changed-By: HIGUCHI Daisuke (VDR dai) d...@debian.org Description: hardinfo - Displays system information Closes: 747059 Changes: hardinfo (0.5.1-1.4) unstable; urgency=medium . * Non-maintainer upload. * fix FTBFS ld: cannot find -lselinux by adding a build-dep on libselinux1-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386] (Closes: #747059). Checksums-Sha1: d9652cc81660aa77b94fe087f4abe184c235d9f0 1791 hardinfo_0.5.1-1.4.dsc 60f88c5c75f86c0fed3324d83567421183fd6f61 9707 hardinfo_0.5.1-1.4.diff.gz a7c5085cc51c0b9c9afee547bc0cfedb907bd6e1 225520 hardinfo_0.5.1-1.4_amd64.deb Checksums-Sha256: d3ae13c5f3be321e55cda17700838d0485661cbda08e4539b808bbb9b8b9005f 1791 hardinfo_0.5.1-1.4.dsc 2ae3f3f54f8c5c2a2f9b25fcb5ded5b8f861d52a0aacc192a5e9181a05a9e578 9707 hardinfo_0.5.1-1.4.diff.gz 3014a25d2682834bf814f7d6ed4143e5e06b0b6a91bd15f3314ecf400ed6af19 225520 hardinfo_0.5.1-1.4_amd64.deb Files: fb19ada2f088d5375217efc639dfdf17 225520 x11 optional hardinfo_0.5.1-1.4_amd64.deb 537f13946dca58b3178244bac1c43358 1791 x11 optional hardinfo_0.5.1-1.4.dsc 0a194b720e1fff6c437e972d098c76fe 9707 x11 optional hardinfo_0.5.1-1.4.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTaij+AAoJEHg5YZ3UOWaOhJQP/3ahresrWvuK8BF2Tbg6QCzT rdeIrRqbF+77SJNw9PxTwSLmtdcOfx88A39YSkRV3SdO+SGlaUCJdRC1DZ4ZcITJ hYIlnuQ139o3oL8+Bqc4/tdpp9m5wEmbb6vgPOgsEYdr5BLQGO84jjpKrfsD2heD OtC2+obwNOnt4gp/+r8TRDgGHInKGQxvue4ACniPbOdpd6bBRvK6DbAsHieZLW4V S0cSNI493WRfxm1iOUvDxPEDRakwDuN8+XavUCrV5uwsO3iNGwBvA9jcjiP4YSeg /wcWUXlTaxwoWntsAd6E2cs6Vah3aglX8YBy3J4cTQBFkMNypwrZ6r7JOTkzx7xd O/rDFjWjNAV2DcMC4rkKbc5skwB2vFGOhN9d+62aD6nsXA+hchbyDXCj90uvlYXp 6KY+DQfpZbuLU56iT2Dz2CaPwa8bT9yU7Z9sJLT3XhulsErudiy/VoGiWjxy8tLZ MMSu19/7lSZuPp3k9132G5zLf56sCETLz3GaNwQB1ZtIJTOsBZzJ0Ad59WjqYqDR 4qKCf+t3+jt0Q5KRrqz2ZZ7X8SGjQnBKcjlwqPCtoAK2rPlR+ZQ7JUf5ltylq8LU crsQJHJ+Pzn92dy5lfxudr8pnVff9/Vy7PAgsaeTDQ+0V3q6a2Uyr2UEOWz89LJq WCgrorxdH64Rscdeb576 =BZwe -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjpu1-0007mt...@franck.debian.org
Accepted connectagram 1.1.2-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 02 May 2014 20:02:56 +0200 Source: connectagram Binary: connectagram connectagram-data Architecture: source amd64 all Version: 1.1.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Dariusz Dwornikowski dariusz.dwornikow...@cs.put.poznan.pl Description: connectagram - word unscrambling game connectagram-data - word unscrambling game - data files Closes: 643082 726101 737849 746459 Changes: connectagram (1.1.2-1) unstable; urgency=medium . * Imported Upstream version 1.1.2 (Closes: #726101) * Bump standards to 3.9.5 and compat to 9 * New maintainer (Closes: #746459) * Split packages to connectagram and connectagram-data, containing word list files * Removed unneeded patch (Closes: #643082) * Migrated to dh * debian/copyright formatted according to DEP-5 * Fixed watch file * Added menu file and keyword to desktop file (Closes: #737849) Checksums-Sha1: b8302f9d018e788ed1481adafced6f29cedb6114 2067 connectagram_1.1.2-1.dsc de9e5ba66c62fbf953f91a6fa5baba06bc119695 1415066 connectagram_1.1.2.orig.tar.bz2 540c103a24b4d8c437e25f33581a5a62cb44d3aa 3044 connectagram_1.1.2-1.debian.tar.bz2 672bdaaaf2cadb3201294e348a8c9e8ca2207b13 113392 connectagram_1.1.2-1_amd64.deb 82ee9beca14e43308bb030d9aa3b8cf205212678 930598 connectagram-data_1.1.2-1_all.deb Checksums-Sha256: 5eac0fb53c08d49002b0e89fe7800f48bd367ba37d7f8827c0d954832d83e578 2067 connectagram_1.1.2-1.dsc 06e03fed6d7651383cf8d771d0e89e09bb149c0aef431c1374296e62319087c4 1415066 connectagram_1.1.2.orig.tar.bz2 ea81310e8e0ea752616a189945c76996df2aad1c4133ebc05cba86a4d4ab6d97 3044 connectagram_1.1.2-1.debian.tar.bz2 d04cc401dba379f85e7e1855be69243d27518f557544727553189d399be8d611 113392 connectagram_1.1.2-1_amd64.deb bc3ea4ae32847538eecc0b6ea14ebd799d06808b35df77301bb93f5192d3493a 930598 connectagram-data_1.1.2-1_all.deb Files: 1a2071f5bd226c847413dc7f2b8dda9b 113392 games optional connectagram_1.1.2-1_amd64.deb 2ce33e90e62844df2a6d4ae734c4a173 930598 games optional connectagram-data_1.1.2-1_all.deb 09a11b472feb71e7cd7c73bb5896f8fc 2067 games optional connectagram_1.1.2-1.dsc 036b0ab02274d6c9bed75c437513baeb 1415066 games optional connectagram_1.1.2.orig.tar.bz2 94b25cf63120368e040564bd63febe86 3044 games optional connectagram_1.1.2-1.debian.tar.bz2 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTaISRAAoJEI7tzBuqHzL/ix8P/RLePk3R7A80quo2otSIc4// 85fmkDSSudZyCD+gjIPmHZcKjSpSQAWPVH2cqGal7K192aNRMYU+T3sdIgTHxlho /AM1tSfrX7wd4bttXzrc0AidZzot5OVJa2bYoXKYOJPjrJVqGrkyvGlT6jJXRaY0 GZxKCGQLRgrHPFVXxKAVEUFVSuBAaVPNGdIjCX+MNC+wOcNPrJcemoSIfZBU6KdF ojBi2C/VjTe+UhgCrD0/o8+Hfpcyn1pThpzjLI3AWf0Z+Fe+tNkEGv5cAo+qa5iI P9k62rnVuvELCzq27JqFKgrQ6UByP2PoerB/pYOrSQ6qGKMQl86i5lkYzrLggjyA h+jDqUQvWJmaEgi48u6pTqzt8QXlDg/TpAXQoIuGenmmVGIAwO0wv31sDc4X3e7W Il+L++/nMZ7566eVR81HrkLZ/bNqR/0TUJr+XTDz0Z+xo0zLa+SFr25D/XKpgAT5 UIEUhanNvptS69FJsUKYa6f5LjHT8u7h3di/bfuMQNhxvh9lfywogckG+4bMlGFT fyx5LCIUaQPyXNbyiWk8SuoJE8sY+g9VrcNI8pYBJ7LriRJmMl69AMOupMg+IrWa a5PjaMyQ/DgBgWYQjWSNg9U2mDi/6hqQoeKeH9nuci/1nHXkbVBr48TLz1mV+LoW f+mkJtG5UDkRMiGvpIX2 =T2+n -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjppu-0006ko...@franck.debian.org
Accepted webkitgtk 2.4.2-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 May 2014 12:07:00 +0300 Source: webkitgtk Binary: libjavascriptcoregtk-1.0-0 libjavascriptcoregtk-1.0-dev libjavascriptcoregtk-1.0-0-dbg gir1.2-javascriptcoregtk-1.0 libwebkitgtk-1.0-0 libwebkit-dev libwebkitgtk-dev libwebkitgtk-1.0-common libwebkitgtk-1.0-0-dbg gir1.2-webkit-1.0 libjavascriptcoregtk-3.0-0 libjavascriptcoregtk-3.0-dev libjavascriptcoregtk-3.0-0-dbg libjavascriptcoregtk-3.0-bin gir1.2-javascriptcoregtk-3.0 libwebkitgtk-3.0-0 libwebkitgtk-3.0-dev libwebkitgtk-3.0-common libwebkitgtk-3.0-0-dbg gir1.2-webkit-3.0 libwebkit2gtk-3.0-25 libwebkit2gtk-3.0-dev libwebkit2gtk-3.0-25-dbg gir1.2-webkit2-3.0 libwebkitgtk-common-dev Architecture: source all amd64 Version: 2.4.2-1 Distribution: unstable Urgency: medium Maintainer: Debian WebKit Maintainers pkg-webkit-maintain...@lists.alioth.debian.org Changed-By: Alberto Garcia be...@igalia.com Description: gir1.2-javascriptcoregtk-1.0 - JavaScript engine library from WebKitGTK+ - GObject introspection gir1.2-javascriptcoregtk-3.0 - JavaScript engine library from WebKitGTK+ - GObject introspection gir1.2-webkit-1.0 - Web content engine library for GTK+ - GObject introspection data gir1.2-webkit-3.0 - Web content engine library for GTK+ - GObject introspection data gir1.2-webkit2-3.0 - WebKit2 API layer for WebKitGTK+ - GObject introspection data libjavascriptcoregtk-1.0-0 - JavaScript engine library from WebKitGTK+ libjavascriptcoregtk-1.0-0-dbg - JavaScript engine library from WebKitGTK+ - debugging symbols libjavascriptcoregtk-1.0-dev - JavaScript engine library from WebKitGTK+ - development files libjavascriptcoregtk-3.0-0 - JavaScript engine library from WebKitGTK+ libjavascriptcoregtk-3.0-0-dbg - JavaScript engine library from WebKitGTK+ - debugging symbols libjavascriptcoregtk-3.0-bin - JavaScript engine library from WebKitGTK+ - command-line interpre libjavascriptcoregtk-3.0-dev - JavaScript engine library from WebKitGTK+ - development files libwebkit-dev - Transitional package for the development files of WebKitGTK+ libwebkit2gtk-3.0-25 - WebKit2 API layer for WebKitGTK+ libwebkit2gtk-3.0-25-dbg - WebKit2 API layer for WebKitGTK+ - debugging symbols libwebkit2gtk-3.0-dev - WebKit2 API layer for WebKitGTK+ - development files libwebkitgtk-1.0-0 - Web content engine library for GTK+ libwebkitgtk-1.0-0-dbg - Web content engine library for GTK+ - debugging symbols libwebkitgtk-1.0-common - Web content engine library for GTK+ - data files libwebkitgtk-3.0-0 - Web content engine library for GTK+ libwebkitgtk-3.0-0-dbg - Web content engine library for GTK+ - debugging symbols libwebkitgtk-3.0-common - Web content engine library for GTK+ - data files libwebkitgtk-3.0-dev - Web content engine library for GTK+ - development files libwebkitgtk-common-dev - Web content engine library for GTK+ - common development files libwebkitgtk-dev - Web content engine library for GTK+ - development files Closes: 732095 746959 Changes: webkitgtk (2.4.2-1) unstable; urgency=medium . * New upstream release (Closes: #732095). * debian/rules: + Enable parallel builds again (Closes: #746959). * debian/control: + Require make 4.0, which is the version that can make parallel builds of webkitgtk. * debian/patches/fix-jsc-crash.patch: + Removed, this is already included in this release. Checksums-Sha1: 2c4d172029ed1cd780584b0ab742cdfa82aacc61 4770 webkitgtk_2.4.2-1.dsc 74faecd6b0a82cd8f92b571e593c95c5afae5e2c 9837440 webkitgtk_2.4.2.orig.tar.xz 2c508e3633d82dae056efd01844f4364bfb97b0e 50484 webkitgtk_2.4.2-1.debian.tar.xz 6b79de07712a96d8ca6cad2ba119265c575961a6 446694 libwebkitgtk-1.0-common_2.4.2-1_all.deb 8694a6cd4d0bf9c62705cde85448d72ce0194c2d 446696 libwebkitgtk-3.0-common_2.4.2-1_all.deb 9b0e600b7acc7169bab67a8041f672642b0feab2 1947736 libjavascriptcoregtk-1.0-0_2.4.2-1_amd64.deb 699caefd31132d64cf714865eb1638383d137f63 125900 libjavascriptcoregtk-1.0-dev_2.4.2-1_amd64.deb 4919462f345256fe21ead65e6ad6c34ab5fa7da2 78345768 libjavascriptcoregtk-1.0-0-dbg_2.4.2-1_amd64.deb 5df488b3bb5837b8e1926ad8fb8568cea1cbdb6c 115054 gir1.2-javascriptcoregtk-1.0_2.4.2-1_amd64.deb c093b3f71081349e9e9233393b14df4948b0ff9b 6598006 libwebkitgtk-1.0-0_2.4.2-1_amd64.deb eef4572560ee24370059557bfd108cafac11db72 114482 libwebkit-dev_2.4.2-1_amd64.deb f8513303bde55fe8ac2e3cc461d08d8dd38acf03 343470 libwebkitgtk-dev_2.4.2-1_amd64.deb 242e479db06dc49c01b648666476201a90e8074a 314661640 libwebkitgtk-1.0-0-dbg_2.4.2-1_amd64.deb 94d26ca6975f2b86b0b5562ba5e0231187e801ae 164664 gir1.2-webkit-1.0_2.4.2-1_amd64.deb fdbe26e7ac2260c764e0263d040bad15e4f8ade7 1950220 libjavascriptcoregtk-3.0-0_2.4.2-1_amd64.deb 1db44067b8cebfaae200987f847adc7ca8c946ff 125902 libjavascriptcoregtk-3.0-dev_2.4.2-1_amd64.deb 828e917d547006efa6c2b7472cfce003389c14ea 78345066 libjavascriptcoregtk-3.0-0-dbg_2.4.2-1_amd64.deb
Accepted php5 5.5.12+dfsg-2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 12 May 2014 14:22:52 +0200
Source: php5
Binary: php5 php5-common libapache2-mod-php5 libapache2-mod-php5filter php5-cgi
php5-cli php5-fpm libphp5-embed php5-dev php5-dbg php-pear php5-curl
php5-enchant php5-gd php5-gmp php5-imap php5-interbase php5-intl php5-ldap
php5-mcrypt php5-readline php5-mysql php5-mysqlnd php5-odbc php5-pgsql
php5-pspell php5-recode php5-snmp php5-sqlite php5-sybase php5-tidy php5-xmlrpc
php5-xsl
Architecture: source all amd64
Version: 5.5.12+dfsg-2
Distribution: unstable
Urgency: high
Maintainer: Debian PHP Maintainers pkg-php-ma...@lists.alioth.debian.org
Changed-By: Ondřej Surý ond...@debian.org
Description:
libapache2-mod-php5 - server-side, HTML-embedded scripting language (Apache 2
module)
libapache2-mod-php5filter - server-side, HTML-embedded scripting language
(apache 2 filter mo
libphp5-embed - HTML-embedded scripting language (Embedded SAPI library)
php-pear - PEAR - PHP Extension and Application Repository
php5 - server-side, HTML-embedded scripting language (metapackage)
php5-cgi - server-side, HTML-embedded scripting language (CGI binary)
php5-cli - command-line interpreter for the php5 scripting language
php5-common - Common files for packages built from the php5 source
php5-curl - CURL module for php5
php5-dbg - Debug symbols for PHP5
php5-dev - Files for PHP5 module development
php5-enchant - Enchant module for php5
php5-fpm - server-side, HTML-embedded scripting language (FPM-CGI binary)
php5-gd- GD module for php5
php5-gmp - GMP module for php5
php5-imap - IMAP module for php5
php5-interbase - interbase/firebird module for php5
php5-intl - internationalisation module for php5
php5-ldap - LDAP module for php5
php5-mcrypt - MCrypt module for php5
php5-mysql - MySQL module for php5
php5-mysqlnd - MySQL module for php5 (Native Driver)
php5-odbc - ODBC module for php5
php5-pgsql - PostgreSQL module for php5
php5-pspell - pspell module for php5
php5-readline - Readline module for php5
php5-recode - recode module for php5
php5-snmp - SNMP module for php5
php5-sqlite - SQLite module for php5
php5-sybase - Sybase / MS SQL Server module for php5
php5-tidy - tidy module for php5
php5-xmlrpc - XML-RPC module for php5
php5-xsl - XSL module for php5
Closes: 747195
Changes:
php5 (5.5.12+dfsg-2) unstable; urgency=medium
.
* Set default listen.{owner,group} to www-data:www-data (Closes: #747195)
Checksums-Sha1:
dbc88ff66738f695f0e699557bdb95461cd10019 4980 php5_5.5.12+dfsg-2.dsc
ccb93a09c89eee95ea08c6da83e4203c624012d6 108696
php5_5.5.12+dfsg-2.debian.tar.xz
441f707609d1493bd91c08ed4f97f18a23fb38b1 1324 php5_5.5.12+dfsg-2_all.deb
8098063c6b06c2efa6a7bc2b222e498345bac359 267258 php-pear_5.5.12+dfsg-2_all.deb
ce9c9233b0856323c46697dd571075159964c1d7 357628
php5-common_5.5.12+dfsg-2_amd64.deb
b295c9774917f70e7d1bbcbc16552b181a23dea1 2141360
libapache2-mod-php5_5.5.12+dfsg-2_amd64.deb
c626adb3ad601214cd8aace55732337e37d915e0 2132624
libapache2-mod-php5filter_5.5.12+dfsg-2_amd64.deb
2f7a81a4d1d3bcd12d7675e4c402299ce507782d 4114584
php5-cgi_5.5.12+dfsg-2_amd64.deb
68111de7cec7c89f2d20d3d6c67d53155bf1cd03 2092290
php5-cli_5.5.12+dfsg-2_amd64.deb
22868980042bf6a5ed6dc9cfe93662247162e993 2121236
php5-fpm_5.5.12+dfsg-2_amd64.deb
ba6a616a0a5c34e8520996437ae1b4c3c6a1ee32 2136880
libphp5-embed_5.5.12+dfsg-2_amd64.deb
9d65f61e0352cb3acbb97d6eb8f386143233178d 346458
php5-dev_5.5.12+dfsg-2_amd64.deb
98300d4797dbd0b9f802d5acfe3076bdfdb6643b 30323738
php5-dbg_5.5.12+dfsg-2_amd64.deb
d5c087914e1a26b50f3ef885dd1027b5bb8978d2 27490
php5-curl_5.5.12+dfsg-2_amd64.deb
35dc827e4abd026898eaac399e7644516bfaab44 9294
php5-enchant_5.5.12+dfsg-2_amd64.deb
8632d123b1e76c5a19f34fc736a89009c4e2d5c0 27950 php5-gd_5.5.12+dfsg-2_amd64.deb
9f1b31a9897b56805ff4aec74e9692c8c6b0cb25 14784 php5-gmp_5.5.12+dfsg-2_amd64.deb
f7b6b4ae140b463bfc5f9dcf8b71a8aa03ffdeac 30258
php5-imap_5.5.12+dfsg-2_amd64.deb
8b02cbd2e4f4525c5fc36c701bc1445ff7bcffd4 41730
php5-interbase_5.5.12+dfsg-2_amd64.deb
01dc25ad7a34198c112b7295cc43b004d7e9ae28 109220
php5-intl_5.5.12+dfsg-2_amd64.deb
8ffc697f06ca1b8e45f1f9b59a9348a9bd905b61 20924
php5-ldap_5.5.12+dfsg-2_amd64.deb
78bc66232f95b8c43d32ceea270b91b696dab426 14198
php5-mcrypt_5.5.12+dfsg-2_amd64.deb
6ce71092233f30b0dbdcf5be036f613fdae0aae1 12240
php5-readline_5.5.12+dfsg-2_amd64.deb
08b9385b143591c5c477d076e7654650b269e773 63406
php5-mysql_5.5.12+dfsg-2_amd64.deb
e0cd8abf5b2b28c775ab475109a00617b6aba6a8 135040
php5-mysqlnd_5.5.12+dfsg-2_amd64.deb
24a1030008a5ebb88e3586ec5992f8db21a8c158 30396
php5-odbc_5.5.12+dfsg-2_amd64.deb
204569da2253d43a0db74d04ab58c51c4368142e 52330
php5-pgsql_5.5.12+dfsg-2_amd64.deb
fa047588e98fa5940012c96b9d9a2b4d65112ee7 8236
php5-pspell_5.5.12+dfsg-2_amd64.deb
5609e7d30a8c1386ee3397b62b078f0fb76b43d7 5604
php5-recode_5.5.12+dfsg-2_amd64.deb
Accepted xmms2 0.8+dfsg-10 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 May 2014 06:57:32 +0200 Source: xmms2 Binary: libaudio-xmmsclient-perl libxmmsclient++-dev libxmmsclient++-glib-dev libxmmsclient++-glib1 libxmmsclient++4 libxmmsclient-dev libxmmsclient-glib-dev libxmmsclient-glib1 ruby-xmmsclient libxmmsclient6 python-xmmsclient xmms2 xmms2-client-avahi xmms2-client-cli xmms2-client-medialib-updater xmms2-client-nycli xmms2-core xmms2-dev xmms2-icon xmms2-plugin-airplay xmms2-plugin-all xmms2-plugin-alsa xmms2-plugin-ao xmms2-plugin-apefile xmms2-plugin-asf xmms2-plugin-asx xmms2-plugin-avcodec xmms2-plugin-cdda xmms2-plugin-cue xmms2-plugin-curl xmms2-plugin-daap xmms2-plugin-faad xmms2-plugin-flac xmms2-plugin-flv xmms2-plugin-gme xmms2-plugin-gvfs xmms2-plugin-html xmms2-plugin-ices xmms2-plugin-icymetaint xmms2-plugin-id3v2 xmms2-plugin-jack xmms2-plugin-karaoke xmms2-plugin-m3u xmms2-plugin-mad xmms2-plugin-mms xmms2-plugin-modplug xmms2-plugin-mp4 xmms2-plugin-mpg123 xmms2-plugin-musepack xmms2-plugin-normalize xmms2-plugin-ofa xmms2-plugin-oss xmms2-plugin-pls xmms2-plugin-pulse xmms2-plugin-rss xmms2-plugin-sid xmms2-plugin-smb xmms2-plugin-sndfile xmms2-plugin-speex xmms2-plugin-tta xmms2-plugin-vocoder xmms2-plugin-vorbis xmms2-plugin-wavpack xmms2-plugin-xml xmms2-plugin-xspf Architecture: source amd64 all Version: 0.8+dfsg-10 Distribution: unstable Urgency: low Maintainer: Benjamin Drung bdr...@debian.org Changed-By: Rémi Vanicat vani...@debian.org Description: libaudio-xmmsclient-perl - XMMS2 - Perl client library libxmmsclient++-dev - XMMS2 - client library for c++ - development files libxmmsclient++-glib-dev - XMMS2 - glib client library for c++ - development files libxmmsclient++-glib1 - XMMS2 - glib client library for c++ libxmmsclient++4 - XMMS2 - client library for c++ libxmmsclient-dev - XMMS2 - client library development files libxmmsclient-glib-dev - XMMS2 - glib client library - development files libxmmsclient-glib1 - XMMS2 - glib client library libxmmsclient6 - XMMS2 - client library python-xmmsclient - XMMS2 - Python bindings ruby-xmmsclient - XMMS2 - Ruby bindings xmms2 - Client/server based media player system xmms2-client-avahi - XMMS2 - avahi client xmms2-client-cli - XMMS2 - cli client xmms2-client-medialib-updater - XMMS2 - medialib-updater client xmms2-client-nycli - XMMS2 - new cli client xmms2-core - XMMS2 - core package xmms2-dev - XMMS2 - plug-in development files xmms2-icon - XMMS2 - icon package xmms2-plugin-airplay - XMMS2 - airplay output plug-in xmms2-plugin-all - XMMS2 - all plug-ins xmms2-plugin-alsa - XMMS2 - ALSA output xmms2-plugin-ao - XMMS2 - libao output plug-in xmms2-plugin-apefile - XMMS2 - Monkey's Audio decoder plug-in xmms2-plugin-asf - XMMS2 - ASF plug-in xmms2-plugin-asx - XMMS2 - ASX playlist plug-in xmms2-plugin-avcodec - XMMS2 - avcodec decoder xmms2-plugin-cdda - XMMS2 - CDDA plug-in xmms2-plugin-cue - XMMS2 - CUE playlist plug-in xmms2-plugin-curl - XMMS2 - curl transport for HTTP xmms2-plugin-daap - XMMS2 - daap plug-in xmms2-plugin-faad - XMMS2 - faad decoder xmms2-plugin-flac - XMMS2 - FLAC decoder xmms2-plugin-flv - XMMS2 - Flash Video plug-in xmms2-plugin-gme - XMMS2 - gme plug-in xmms2-plugin-gvfs - XMMS2 - gvfs plug-in xmms2-plugin-html - XMMS2 - HTML playlist plug-in xmms2-plugin-ices - XMMS2 - Ogg streaming output xmms2-plugin-icymetaint - XMMS2 - shoutcast metadata plug-in xmms2-plugin-id3v2 - XMMS2 - ID3v2 plug-in xmms2-plugin-jack - XMMS2 - JACK output xmms2-plugin-karaoke - XMMS2 - karaoke plug-in xmms2-plugin-m3u - XMMS2 - M3U playlist plug-in xmms2-plugin-mad - XMMS2 - libmad based mp3 decoder xmms2-plugin-mms - XMMS2 - MMS transport xmms2-plugin-modplug - XMMS2 - modplug decoder xmms2-plugin-mp4 - XMMS2 - MPEG-4 plug-in xmms2-plugin-mpg123 - XMMS2 - libmpg123 based mp3 decoder xmms2-plugin-musepack - XMMS2 - mpc decoder xmms2-plugin-normalize - XMMS2 - Normalize plug-in xmms2-plugin-ofa - XMMS2 - Open Fingerprint Architecture plug-in xmms2-plugin-oss - XMMS2 - OSS output xmms2-plugin-pls - XMMS2 - PLS playlist plug-in xmms2-plugin-pulse - XMMS2 - PulseAudio output plug-in xmms2-plugin-rss - XMMS2 - RSS podcast plug-in xmms2-plugin-sid - XMMS2 - libsidplay2 based decoder xmms2-plugin-smb - XMMS2 - Server Message Block (SMB) transport xmms2-plugin-sndfile - XMMS2 - sndfile decoder xmms2-plugin-speex - XMMS2 - Speex decoder xmms2-plugin-tta - XMMS2 - TTA decoder plug-in xmms2-plugin-vocoder - XMMS2 - vocoder plug-in xmms2-plugin-vorbis - XMMS2 - vorbis decoder xmms2-plugin-wavpack - XMMS2 - WavPack decoder plug-in xmms2-plugin-xml - XMMS2 - XML plug-in xmms2-plugin-xspf - XMMS2 - XSPF playlist plug-in Closes: 739455 747709 Changes: xmms2 (0.8+dfsg-10) unstable; urgency=low . * Add a build dependency on libssl-dev (Closes: #747709). * Acknowledge NMU. Thanks Reinhard. * compile against libav10 (Closes: #739455)
Accepted acl2 6.4-3 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 09 May 2014 15:38:15 + Source: acl2 Binary: acl2 acl2-source acl2-emacs acl2-infix acl2-infix-source acl2-books acl2-books-source acl2-books-certs acl2-doc Architecture: source all amd64 Version: 6.4-3 Distribution: unstable Urgency: low Maintainer: Camm Maguire c...@debian.org Changed-By: Camm Maguire c...@debian.org Description: acl2 - Computational Logic for Applicative Common Lisp: main binary acl2-books - Computational Logic for Applicative Common Lisp: compiled librari acl2-books-certs - Computational Logic for Applicative Common Lisp: library certific acl2-books-source - Computational Logic for Applicative Common Lisp: library sources acl2-doc - Computational Logic for Applicative Common Lisp: documentation acl2-emacs - Computational Logic for Applicative Common Lisp: emacs interface acl2-infix - Computational Logic for Applicative Common Lisp: infix interface acl2-infix-source - Computational Logic for Applicative Common Lisp: infix source acl2-source - Computational Logic for Applicative Common Lisp: source files Closes: 747286 Changes: acl2 (6.4-3) unstable; urgency=low . * set HOME in rule to build saved_acl2.c * Bug fix: not buildable on buildds on some architectures, thanks to Ivo De Decker (Closes: #747286). Checksums-Sha1: abb9fef90499dac10ec5668c2111c26da39ba93d 1814 acl2_6.4-3.dsc d8f1cc125e08bd20721b0ee8b2a3ec69d75cc2bb 126628 acl2_6.4-3.debian.tar.xz 5c6fd7c1308d19efb27b75d07b0cf167ce103624 2730514 acl2-source_6.4-3_all.deb 4fb48432ae099fe1aa5bbb19e9295e02239514a7 59826 acl2-emacs_6.4-3_all.deb 2e2a341ff124a002a621d54d4be5707fe78689cf 78106 acl2-infix-source_6.4-3_all.deb 9a27ecb953b3fcec90e4a06aa6d2fa437d3a59bf 6499790 acl2-books-source_6.4-3_all.deb a724d5917b7eb0e994ffc85ede507c5c7f6d 4268440 acl2-books-certs_6.4-3_all.deb 4f7738fc88c9775ce43f837c562f43983d345de8 1639260 acl2-doc_6.4-3_all.deb 64593efc8c64e390ad3c9c4ca07766222cdeff4b 15263470 acl2_6.4-3_amd64.deb cb46d981f2415c1a187cb410ba85a470ce294391 151120 acl2-infix_6.4-3_amd64.deb 69cad5a5ee7449d23fbc10d0f6a0d804faf6ec90 19621762 acl2-books_6.4-3_amd64.deb Checksums-Sha256: 5d3cd23d4db3199234671764d350685aff341678bad45c8ae105c7823de207e1 1814 acl2_6.4-3.dsc 6141a3f5c8696a697e96c2650ea1b9be688861f2caa80a0950cffa8c32b526d1 126628 acl2_6.4-3.debian.tar.xz a39fe1e00ea677e4498f14288fc5ec46d049a8c1c9a287287e8b67e879daf640 2730514 acl2-source_6.4-3_all.deb d536608c385735fb8e8eac0dd33ba60c11c9dc3ac0fb71142e8c44979cea6dec 59826 acl2-emacs_6.4-3_all.deb 7a8fdd72e9608653ed7ea8508437f280d1f8e822ab99294a613988299cca989f 78106 acl2-infix-source_6.4-3_all.deb 4a35804ab2b5db7fa5f1579d71f85780adeca34e4e0cac9b23f8b5517feb7812 6499790 acl2-books-source_6.4-3_all.deb 861af255aa989373e4e9750a65c47d0fab0621f7d45b12c12b78a745b26fa184 4268440 acl2-books-certs_6.4-3_all.deb d387940becad67b90dc38bd68a181cd39b7d82915515fbd1e0b358e6abe470b4 1639260 acl2-doc_6.4-3_all.deb a0054bda41d12625565d4bacc64facc81e1892e36e4e1a7e4328052313adda03 15263470 acl2_6.4-3_amd64.deb 1c541cb3b84dfe8aff968ea6aeb09e7526c83009f01731590c1cbba9f3783950 151120 acl2-infix_6.4-3_amd64.deb c81749bde4023103c2d6d0fe9cf3613a774084ba42112b5593b98d3bb185ac65 19621762 acl2-books_6.4-3_amd64.deb Files: bc186c65fe8f93ac82f7556690d4010f 2730514 math optional acl2-source_6.4-3_all.deb 903b09f89184d7b626738f696660658d 59826 math optional acl2-emacs_6.4-3_all.deb fb44aca4588a54ffa7c3d727c505f6f0 78106 math optional acl2-infix-source_6.4-3_all.deb 00bf1dce38daba73cff1fde8fb161482 6499790 math optional acl2-books-source_6.4-3_all.deb 91b98064443f4a6c44c9c403a5d55c12 4268440 math optional acl2-books-certs_6.4-3_all.deb a3c25e47ca259f362fa8a146eec986f1 1639260 doc optional acl2-doc_6.4-3_all.deb 648b53cea6fe636425eac7c5630e6cd0 15263470 math optional acl2_6.4-3_amd64.deb 3e3a1ba6fb0aef485302de074a6d423a 151120 math optional acl2-infix_6.4-3_amd64.deb 3c78f522281df651e257adb2b74a4a3f 19621762 math optional acl2-books_6.4-3_amd64.deb 30d28162208847f16cb84e70d26944a1 1814 math optional acl2_6.4-3.dsc a2741a86484eaad83a9cccfb9c4a2256 126628 math optional acl2_6.4-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlNwI30ACgkQczG1wFfwRdzh+QCePXud49PPNcJMs65dCREoFh8i oeUAn2VmcKrmCt8wtKffwbyhVPz7RMb0 =AhId -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjsgf-0001mo...@franck.debian.org
Accepted bisonc++ 4.09.01-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 11 May 2014 09:13:23 +0200 Source: bisonc++ Binary: bisonc++ bisonc++-doc Architecture: source amd64 all Version: 4.09.01-1 Distribution: unstable Urgency: low Maintainer: Frank B. Brokken f.b.brok...@rug.nl Changed-By: Frank B. Brokken f.b.brok...@rug.nl Description: bisonc++ - Bison-style parser generator for C++ bisonc++-doc - Bison-style parser generator for C++ Changes: bisonc++ (4.09.01-1) unstable; urgency=low . * New upstream release adds option --no-decoration to generate a parser w/o performing actions when rules are matched, and adds new skeleton files containing a substantial amount of code previously hard-coded inside bisonc++ itself. Checksums-Sha1: 43875d25441cf453ef0c78a587daf5f06bab2b16 2106 bisonc++_4.09.01-1.dsc 9cd220e1591112692a514347f99dec4bf69e3c78 654635 bisonc++_4.09.01.orig.tar.gz b0eea8f1ffc428901305b6ba8e6195379884eead 11552 bisonc++_4.09.01-1.debian.tar.xz 5c55a562f854d8a4718c334a7eac882b20bb94f4 184246 bisonc++_4.09.01-1_amd64.deb 42a80bea4dea6b3e66ea3abef103a421f56927ba 404136 bisonc++-doc_4.09.01-1_all.deb Checksums-Sha256: e93b21ff8d9545e44b7f4874e556df8012ee526f036e3d7e82a7e52c3dbe1cbf 2106 bisonc++_4.09.01-1.dsc 447cb90975251e4b6de51ccafe637184859f1ea4ad38ddb3b5988eebda42603c 654635 bisonc++_4.09.01.orig.tar.gz 257256b1273d238abf3d9daae92c85dc2956959e7361f934cacb335d6b46f37f 11552 bisonc++_4.09.01-1.debian.tar.xz 1ee423f7cd8aa05e14e6287f528c5ed6eff7da31f73202acd8fd62c47bbeaa40 184246 bisonc++_4.09.01-1_amd64.deb 57739af7587141a320c2043ed3febc5ecd0c61cc51d50fa5c51ed1987e9b4dd7 404136 bisonc++-doc_4.09.01-1_all.deb Files: c9d733f8e330280d894e1ea91d12dc14 184246 devel optional bisonc++_4.09.01-1_amd64.deb 15b86bc69f4cc2156ee934c575755ff8 404136 doc optional bisonc++-doc_4.09.01-1_all.deb 96d30738d570cc92a5116dd58bcf1417 2106 devel optional bisonc++_4.09.01-1.dsc b2e0f95ed897b0a02aff700150355f83 654635 devel optional bisonc++_4.09.01.orig.tar.gz e73d6c068565a1bef4b0a8a1746bf343 11552 devel optional bisonc++_4.09.01-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTcNjqAAoJECHSBYmXSz6WvFIP/2BW5szyFtXmbP+EMw+mzU3g Vy2DfnZoNHi6SukPr2M4YkFA3JKRxGe3xApKRw5hJjAGKacT+KIaE8DYSy3SblqC pKHBR48KiSM5OU6LL88z6h8kQ8Ytx40z0SVd5C5ZqOhLTN2L88GFOIdAZBoqHRcH TyGruJucsTjwio/uCoYA1acgNOl6ntv+lo1xYUKhcC05052JLbpcl3gPeMoluvpH nHRtvpO9yP963zFPXYTimecfWtw2WFK8zWL7NqT1LLhvZDmdmvs/Iymhqv5ti0Vp BD3iC4B4LPrgr6xNvLZBLE5dSkrhzEsEISlYrP4snExmmRy4cquwOkQkKnjzKK1Q NIQxh7QbgmqrNdlqe+tfM9jM6CccqTsl8+TPBMQG1HYBM3s/LAbpq3d2ZN9d81DU BptC6na3AzNoTtGqluBcQkMikiSY64h9B0wr3J/dvD5Y3fO7ZtVSq/ePpRelC0+X Z1zXicrw3FZ/GhmbLrXC6kGqz/EYH8P4HGvIL5aZk2jvDG565u2bXBu/3VhtM2WG ElEXgjeK6Epj4S4xZ1zONAj6QMK+AhMH9kUdXdpiOzg1ytEXyzo3RhmDQUHPTs67 KYoNjg6nm7Gi6c4rFUFCroaaYOPcU/Ei+gvUIdAWCi5N8RMhuma/mikDWIgkHKTP 65GnizehD+xlPJ0Kw5Bd =9Oe6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjsib-00024l...@franck.debian.org
Accepted asio 1:1.10.2-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 12 May 2014 13:20:45 +0200 Source: asio Binary: libasio-dev libasio-doc Architecture: source all Version: 1:1.10.2-1 Distribution: unstable Urgency: low Maintainer: Markus Wanner mar...@bluegap.ch Changed-By: Markus Wanner mar...@bluegap.ch Description: libasio-dev - cross-platform C++ library for network programming libasio-doc - documentation for asio C++ library for network programming Closes: 718478 Changes: asio (1:1.10.2-1) unstable; urgency=low . * New upstream release. (Closes: #718478) * Fast-forward to the former 1.10.1-1, again. Checksums-Sha1: 5f612d9cfd9c5044903a933c9fde0c974e030888 2659 asio_1.10.2-1.dsc 538c3b770e52d3e036fea4909dd1b88e3ed68f45 1269462 asio_1.10.2.orig.tar.bz2 f7206d2f7c3391281d6e2276a75cc5752a195b95 4620 asio_1.10.2-1.debian.tar.xz 9c8dd649a157837b5c8ed280e84dce8145c1b811 240328 libasio-dev_1.10.2-1_all.deb ae4d6255cd6d88ae7420cee4d4e90df9354822aa 36969434 libasio-doc_1.10.2-1_all.deb Checksums-Sha256: 42c21c06218291663db22339d7e0933a79ff63751082570856b4ff80ec75bcdf 2659 asio_1.10.2-1.dsc 815c839883b3c8e0f3d5a5567d605c62f0f55e2a7410540196ff67c4dea81dd3 1269462 asio_1.10.2.orig.tar.bz2 aba5215592162bf95cdd4b8fdd75eb37189b728d1f9f75cece00b7a001c12d57 4620 asio_1.10.2-1.debian.tar.xz 2669fbd220a3d11e709dc904ac2c605870fdb553ecf7262caebc8c9f49aaff51 240328 libasio-dev_1.10.2-1_all.deb 6c05975d1352af14455fe52ea9fcd20375a16df2295b381aafb5b93e8b0c644d 36969434 libasio-doc_1.10.2-1_all.deb Files: c4f2824cb6a446638a78f2bbc49d7260 240328 libdevel optional libasio-dev_1.10.2-1_all.deb 546d1c0f307e314ed51a7d5c6ea452e1 36969434 doc optional libasio-doc_1.10.2-1_all.deb 38cfb3495f689933cc2baeab8c0846da 2659 devel optional asio_1.10.2-1.dsc cf518ce6978b525b69a8f543f8fe419f 1269462 devel optional asio_1.10.2.orig.tar.bz2 bbe824be19a0295e3a5d515f9b157970 4620 devel optional asio_1.10.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQQcBAEBCgAGBQJTcN6vAAoJEOhoLRs/MemzRXUf/RITLEKJTZJBec16NCCoOKzA Fyu8v0FxzxaxF0yxeMYVf88hWvKTPu8LhWA6Kbbpn+HjSBIYM6ahSHQyxDmFRFxw MAjE1K1PiCNJsJWF7CHeak58L3ohhZ1dtCrOIEylfCpoVja/jXAyDnYBARNO9d/7 4ifZoiT88o2peE/X4w0cEn9Y8YgAVJCZWtuNar/B91f8oCe22cMgN1AynBddnXAg MFs0o3hZaxxDSjgu1pc0p0cco811ARZVroUDsTS+7ipddU6TeZe9MraVBvN9FEa9 QUIxtxUwfPTOtp/Jv+t9VqLimlbZIhRqQcK+W6TThkyIEKvIyquaaEDKhMcIiUgx uvZiDQbFQiQ9PcKkeYhmWrxJ8Hq8m5O5EI2cXkyFNqzeO8nQsWX4Y+KuOzp+Wp3L fUUqz/ZmHGfgJo1gfoaa/pHrW4YZRF2Ub5eqVitqOpE/WJ6ix42IyFMP+wtPry/B gAUXXd76XkUBxX2UvStdirs/snOrSY95IlOEEMdCHrIG/+bRZv6QVqmHez4olzTf rNnQu6GpNHX/R1DgAHCiW9CsDUa2ga4VxMGuQl1cAvVWEvuRvvN9LgYJF5UL45Qd YFAB2F9QlvJlBl+MFP8QxCbdBYskHkhMFnuxkqy6/aXqVA5zv/y8WdtCXxUxAAPx CSLV+q72BTB51YZPjb4HwyyXIs5lVBFaluKkO1aKj3JGd55qt/+DXDBC99nH7Sym cmQWJQRCoowqmDzw97tisslRVS63NJAHDeerJYlwZkKmmYZpdnqu+KmCAQ3wwkab o7tPpCDWWTa3IGPaPMKa1OUHZ8ywF8xctr5rtD0xJveWhvBlushJC0Qz2GuigIME M0XiIl3Cne1gzzlXv+SOPLMXDfUlFVbxpOWlhh6TNJT40q9eOL75f3IoMjOAsQ0C 5ByiMVGdSwClNyK7Ehsp1MLUCuSA/9zIOyUETeh6WGnOWzOKUAEqp3jYgjFq2ISd a/znqqFs2nWDxMh7cdLbh6korxytAZcVpzTSZ7WYC2+aYQS4CEQC7gl14yDGNHT1 4reOFGTXEfxfYN/StAd4WywDqO2Q9fgOThWLCa67SeJvKIN/DgOKzopl7NUb990p 4e6WphjgYVQ7JtQ+s+lGYkvqTMMFAfpHxcbzaDLHSTKiNIco3/3tIO/tecvi2UKB pg1VsW4041xkBek1STVGC+i3CJou6klI6pT+xVMZ62eOdqa6URMuD+k5zynExKm4 Fk8Eyq1ABIkTsCLB82y2wEjopiCaA6Xpjf+6AnX1ct96kdoYFj5oHdh/jQMSapZa wtx6PmGppMFaADldk6qFDiPpTCYQ0kIBduPcrdpFPUgNhI5hoGIXdZeeLP8LtdQ= =Y3PK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjsht-00020r...@franck.debian.org
Accepted gridsite 2.0.4-3 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 12 May 2014 14:31:04 +0200 Source: gridsite Binary: gridsite libgridsite2 gridsite-clients libgridsite-dev gridsite-doc gridsite-dbg Architecture: source all amd64 Version: 2.0.4-3 Distribution: unstable Urgency: medium Maintainer: Mattias Ellert mattias.ell...@fysast.uu.se Changed-By: Mattias Ellert mattias.ell...@fysast.uu.se Description: gridsite - Grid Security for the Web, Web platforms for Grids gridsite-clients - Clients to gridsite: htcp, htrm, htmv gridsite-dbg - Debugging symbols for gridsite gridsite-doc - Developers Documentation for gridsite libgridsite-dev - Developers tools for gridsite libgridsite2 - Run time libraries for mod_gridsite and gridsite-clients Closes: 743318 747768 Changes: gridsite (2.0.4-3) unstable; urgency=medium . * Add missing Build-Requires on pkg-config (Closes: #747768) * Fix wrong return type (Closes: #743318) Checksums-Sha1: 14c5c62153576ae34f0bf3792e63a7284aff3793 2270 gridsite_2.0.4-3.dsc 4cb697fc8947a887139c202650de21b179910950 19528 gridsite_2.0.4-3.debian.tar.xz fd29657a628ae6d69682758d6f85bc56de6c702b 148002 gridsite-doc_2.0.4-3_all.deb 43b8100ee54f399ee5812ff1e7f3e8f89a5a9fca 88724 gridsite_2.0.4-3_amd64.deb 9d01d2775b274b3d37980790f514774bd20d6786 34126 libgridsite2_2.0.4-3_amd64.deb 6e723815e3a654c278d87ec558f2c12f98b927b1 42270 gridsite-clients_2.0.4-3_amd64.deb 44c3b2092957ce85040dffd9440469fb9fb980c4 38024 libgridsite-dev_2.0.4-3_amd64.deb 1f597283f3ede222730c7c32a8bf0fadef98c986 283358 gridsite-dbg_2.0.4-3_amd64.deb Checksums-Sha256: 20868a85e5e4c3910ea59f2aa7782f17baebd7616f6f593820f9c7bf456144b0 2270 gridsite_2.0.4-3.dsc 21d274829e9a4628dd07fd63eb7122fef4146f201aad870c598e41a115240383 19528 gridsite_2.0.4-3.debian.tar.xz a29fa460921580e241223fba0a2b975211c408977c9068ec9aeda18288fd673b 148002 gridsite-doc_2.0.4-3_all.deb 77796f5bc35209a8e521f01fbc89672c68b6bdd048785a9b24596f5aac8b9ebf 88724 gridsite_2.0.4-3_amd64.deb 41594bd33c82d4e2580b967a11eaf323c0e8adf4385ea11fe0c55058e3210ba6 34126 libgridsite2_2.0.4-3_amd64.deb aafbeba7520578ece4fc4f6e3367596e025dc885fef5e2c123395a4ab265b267 42270 gridsite-clients_2.0.4-3_amd64.deb 6e354d627dc8cc6f7065b3fde03c1e773ec66d26f675941a2da102c6d7d7cfea 38024 libgridsite-dev_2.0.4-3_amd64.deb 7d59975c331e8a95ce9b9ddd71571b552dfc41dfb29d58f15d78ca27fdec752c 283358 gridsite-dbg_2.0.4-3_amd64.deb Files: d33b87ec922c2e851df7c84463a93f02 148002 doc optional gridsite-doc_2.0.4-3_all.deb 17f042bced02cc5d1409d9071ae85453 88724 net optional gridsite_2.0.4-3_amd64.deb 9d74340e494697f1da34af50451c7132 34126 libs optional libgridsite2_2.0.4-3_amd64.deb c48bdf6314938777e087f7960a041aef 42270 net optional gridsite-clients_2.0.4-3_amd64.deb 636d8f41aced4318ebd788fb13aebc6e 38024 libdevel optional libgridsite-dev_2.0.4-3_amd64.deb ec2a18cde6b65539d2fd5bb6cf754ec1 283358 debug extra gridsite-dbg_2.0.4-3_amd64.deb cfa0b7c728fd6555ca135bac2383d340 2270 net optional gridsite_2.0.4-3.dsc b942eb49d4dceb72defae005c3337b96 19528 net optional gridsite_2.0.4-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJTcOEXAAoJEOiuwv874alLDCYQAIRXOhlDR83+Igt0nZiMnT/C mtvNMYBDJjj2fKm1X8/nTHFj7VWYzYyS6z7aKw+J+HtfajHIDY/fVe7Il92EB/RP +4ldnrNibHZlK4i3ZPEX8aItzdxqCDh5LdYYCn/e8IfhC5qggdhNO0ph9vGg3Dt5 B8WRq0Mlrf65n08XPpBLYxpz/qUy90rljMovdtBGAtEDuAvKd9dOdH65O9B3mTMO lueIz6nNoqcXcKttP97yX+ipuCAROmSZv36++/VlO0EYwx/AxsXP7bo0c6gLiFZq bPcHJn371+R27TeHSHTU2K7fWiVSQTsRugdhZEubtryjOmhSZzT51nwaMFYs50tk zesr7BAgZE0WAKRS/NYMD8+sfn2dTRzCexfiX7YGq4rukDkdqA0aJrIh80VsIKac gCPfCWS1/O7zqzG0law9hWGmpKPvoPm3HWzlN0xOrPFzyO7vzl7Bv7L8WP6NdZfV lb//EjTSYSxRUwKsm1uQffUU2swRWRE7/CCrQ4HKS+8PqyoXKExj5oGw112baPgT yKia/fpyUmOtfLkT8hqK23Ww/rTgFU4Gqx2G5Y3srhUiwlBcuIiI6tYA2jXEk4C2 SjscVFJ/9+vmGE2QjBssVhfMp14K+PbjWomfjkGyg9W0qX745am9szSs5961WbUq 1d0FroGFq/wL7rxovGu3 =mX/K -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjsju-0002lr...@franck.debian.org
Accepted libpam-abl 0.6.0-3 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 May 2014 13:38:18 +0200 Source: libpam-abl Binary: libpam-abl Architecture: source amd64 Version: 0.6.0-3 Distribution: unstable Urgency: medium Maintainer: Alexandre Mestiashvili a...@biotec.tu-dresden.de Changed-By: Alexandre Mestiashvili a...@biotec.tu-dresden.de Description: libpam-abl - blocks hosts attempting a brute force attack Closes: 725141 742024 Changes: libpam-abl (0.6.0-3) unstable; urgency=medium . * d/control: fixed with help of cme! Closes: #725141,#742024, upload to unstable * d/NEWS: describe the new way of configuration Checksums-Sha1: 3fbd8ec57cf42d599656aba634e2e1102d21a586 1924 libpam-abl_0.6.0-3.dsc 5e8d1b133de70f6ce3a5dbcc5dda4c92658b4557 5336 libpam-abl_0.6.0-3.debian.tar.xz 770eb4543e04c232842709d94bbee9702c1a67d6 42622 libpam-abl_0.6.0-3_amd64.deb Checksums-Sha256: 67807a13be8ed58e1172c669f47475d38277c5003e3dd33222ce00b840c52dd2 1924 libpam-abl_0.6.0-3.dsc e250d203ee20fc4833ff27dcb2d01adaae74c90b551f08f6994b46d6b7bd757e 5336 libpam-abl_0.6.0-3.debian.tar.xz b82f7a574aadc7841296911363d22edaa43924877a75befa590c9e041f21e67b 42622 libpam-abl_0.6.0-3_amd64.deb Files: d5c997b8c4af9a30af1d63ff1cedd46f 42622 admin extra libpam-abl_0.6.0-3_amd64.deb 862d552cef7bf78c58a98928ab238ea3 1924 admin extra libpam-abl_0.6.0-3.dsc 4d1c90cb5258b9d27754cb1bd9e7d559 5336 admin extra libpam-abl_0.6.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTcNDRAAoJEBz3khEbUiiwUrkP/1qyRrMNzRn8j6+cOypopiPM K+oY9x8uEwTWFpQyNduhZhlhlNMyJvKkhXbogvziZ2xCVIUKX5g23W8WIVgENn0w TH0yAwQBOmeEkVeTxCfgloHJqhVi7wOjyILTh+ltHwNUAvjJlgwkMpdbzEu8Hm5t T2YhiBH13aOTquFKPwHVmpKwLOUIrk6duy5McPuiVwlmUIBAtXf8GSlxX2TtmGT/ p4noveTgqD8EPXruWMqgU0tpNgm8K661Dk64s29X5KoQ9qJIjaE5+kDoUPgytx1f qNFz7ECGFEDRYkCVkX75HFE4RJmi5nYEBWHkQKU6RnkPKmJHyUn63qAV8/9BE73S XPw5h5BSTPMkLEDNyZ0VKwe70nTnqcrea0RZv+VlWqbARA3amVOvzjd6eWv2yukU 0VaMCCC5YoO9o3TEz9CKKpySEjmnY9wUtWb/cV2y85wVCBhqW1pqvjYX3D9sD7ht x5nGszB73e+E9HnRv2t+f0zw4Py+uptU4pPZWkswNdAbqObZbR7hgcmMxHUU2/5f EMUhPJMZvT4vgfzsCbQ7cih/TqLcPgDMDOxQ0tWWbgpnUJZBMXkjmERMnXVBQxO4 bt76Gg9tQLWLtNJ3Ho0RbOYKed55Wilu3C13s/IzhskbnYXGRHph6YAUC/FzTkYX GNs2udT65gBpso7GW7bj =C7Ke -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjskw-0002v6...@franck.debian.org
Accepted python-gdata 2.0.18+dfsg1-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 May 2014 17:43:24 +0400 Source: python-gdata Binary: python-gdata python-gdata-doc Architecture: source all Version: 2.0.18+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Dmitry Shachnev mity...@gmail.com Description: python-gdata - Google Data Python client library python-gdata-doc - Google Data Python client library, documentation and examples Closes: 729389 747849 Changes: python-gdata (2.0.18+dfsg1-1) unstable; urgency=medium . * Remove Gustavo from Uploaders (closes: #729389). Thanks for the previous work! * Add handle_redirects.patch to fix issues with Google forcing HTTPS URIs (closes: #747849). * Replace build directory with real files paths in docs. * Remove minified JS without source from the tarball. * Get rid of debian/clean and debian/get-orig-source.sh in favor of Files-Excluded field in debian/copyright. * Remove references to Crypto library from setup.py. * Bump Standards-Version to 3.9.5, no changes needed. Checksums-Sha1: c2826985d135691f1736f1f41ee4caaf095639d4 2138 python-gdata_2.0.18+dfsg1-1.dsc 40897b27209db233bde1a94c6acb6784ce96a36b 1146816 python-gdata_2.0.18+dfsg1.orig.tar.gz 95f7992a799eb9010037f1d862d16336e9e9c6e4 8100 python-gdata_2.0.18+dfsg1-1.debian.tar.xz 608028df49cb8b9550ad2efbba4ad9e4be2475d6 361306 python-gdata_2.0.18+dfsg1-1_all.deb ba5365db2cc8ed185e17322a65723af9c288f7fb 775296 python-gdata-doc_2.0.18+dfsg1-1_all.deb Checksums-Sha256: fe56dc3abe607ac9486d08b9db6eef169dc9bedb84c36f90381e56772b5178a6 2138 python-gdata_2.0.18+dfsg1-1.dsc a8d7a0d3a6d7cf4d72df8fa03df0c41b19c3174c36ab141213b8528c467f116c 1146816 python-gdata_2.0.18+dfsg1.orig.tar.gz b087f31cc91a5d683f471f2d733acdc510fedbb2de061ada5a6703194671a10a 8100 python-gdata_2.0.18+dfsg1-1.debian.tar.xz cfc939d1b279744a4798d77ab7ce6bc17cf2bd68cff81753ec37e3fd06c4f9f2 361306 python-gdata_2.0.18+dfsg1-1_all.deb 445ba9afe7818c2e16025c8d7e569977aeadd2088c907e1c4c62d504fe25f5c7 775296 python-gdata-doc_2.0.18+dfsg1-1_all.deb Files: 668869d7ad2583b6fb9131327011f57c 361306 python optional python-gdata_2.0.18+dfsg1-1_all.deb 3606c643f0595144d4c6d44f016f602d 775296 doc optional python-gdata-doc_2.0.18+dfsg1-1_all.deb 38268547341bc782ada6b5ea8d926e53 2138 python optional python-gdata_2.0.18+dfsg1-1.dsc e38bdc1d36eaa0c7ea85e12b8e1a1a97 1146816 python optional python-gdata_2.0.18+dfsg1.orig.tar.gz f2f0bc7f083dd0d826680acdda9f2a5e 8100 python optional python-gdata_2.0.18+dfsg1-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTcNc2AAoJEGAmk20vHIrg/58P/j1Ux2oyfKMhnMXSOzuYpEXU lzBm3EbWqJpsHKokfDqO4SvsUUEVztpwG+H2JfQLr9KhnhA6Z0NBWmBJbbTrd5RK XwDsf050nuQUrXay1kSeYXKGBv0oQk+bVc6jMF8OhcActokfVnW5vZv10rUWxS+c tnWLNnl7FHjr3Q8ZNuBGWGB3qU8Hg7/JSxdIK0RO46pKcGrmMXZElNQjgm7CklEp +ZctkFN/ImevHOdz5MLwaxJk8oLt2Qx/yUbuO/ABjQSXLz35bpUvkwZPNLa260XV FYmRNEhpznSUT0aAoY7duKV2vgf35zPmMCPYNVP0Ejo0toDfGide1ywtTJ+GedR2 B8nnf1J3uXgrb9lvmPwCJvqSOVAXKunwekmw9GJlJurCH97fyfLT/X3TuYDI6lBn zk0K6YFaBD8a+8+wKPpjUWgZG3Yjte+kzfu8s8b3VcJ3gD8rl/YByTAErk8vP4wN TpouOmU5cXAE5tJCrjZNwlVwWiljOz9yuFsYjubD0c6f/HWPeUCWzD7jdqHtY5La aP3TPvn0o4KGhAciyg/MpiGqU0/h3NDwcaTjZ0bQ7/f7zlZG4umHrLFTZVKLpXgk zVmF+aS5Ig3QKqXDh4evmGKiPN/p9Dcm1p2T0sJI/6xf/krgblcBaN4Y9yupnESx iuddcjRL+F/BgBJPUPc+ =xLoB -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjsol-00039j...@franck.debian.org
Accepted screen-message 0.21-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 May 2014 16:18:31 +0200 Source: screen-message Binary: sm Architecture: source amd64 Version: 0.21-2 Distribution: unstable Urgency: medium Maintainer: Joachim Breitner nome...@debian.org Changed-By: Joachim Breitner nome...@debian.org Description: sm - Displays a short text fullscreen Closes: 747772 Changes: screen-message (0.21-2) unstable; urgency=medium . * Fix build-depends (Closes: #747772) Checksums-Sha1: 1efa764fd9993ad5a00af599d281271fd90633b0 1896 screen-message_0.21-2.dsc 96bd37670274a155cda5e1581dbc38f703732608 3052 screen-message_0.21-2.debian.tar.xz aebe2d9afc6e95bdd93e440d163e5e4c761d57a7 15214 sm_0.21-2_amd64.deb Checksums-Sha256: 23558d32d89a8c0274b44d8f54dde51d5223c33263946f3b2a9f3db2c4efd87c 1896 screen-message_0.21-2.dsc 4b987071bb17cc015180ae30e6521e8bfa08d0ac3a1473b138aed02bb8ec8b4e 3052 screen-message_0.21-2.debian.tar.xz 5847d10764db85dfb12a8f98dc6afc18c349b1223467cf127bd242d4680c1d64 15214 sm_0.21-2_amd64.deb Files: 1403a04e2f85524e87fa993889616e70 15214 games optional sm_0.21-2_amd64.deb afca56d4902bd8cb2414e05bb3336fdc 1896 games optional screen-message_0.21-2.dsc d481a624d6624a829b0400ff986f8135 3052 games optional screen-message_0.21-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTcNh3AAoJED2QirPw+/UfX0AP/RppcGG3u8cMc3gNzrBh56oE R+gnyo1Nj3AXbiEAEyOvrYbLI7iMjqaC00DXtsrf4+7RiNhkVqQLAU+Td4xampaG y1nNtyXRRWH84QbxQxrXbNWegS1NIyfV5hK4Ins0xKsTy0URFG4g7DRi5fsiwZcz Et2/0CkVvpJRELWw8uRsJYHm9cQG9KOsAERbtXU0mRS14ble+LibcEbuXZL3pRWs /rRSpE9PJ9f0pFZ9AcD/LWghM7POyR5V1Wgs64ea7vMKYYzGPmzAAZFRVadZjwyN 0B57/GBJwtgdIwEKC4vtKUsyOldm3w79dVKJYti5FttQ99X5ez5RF7jzdQutbZuj vbPOmDd+Me6lDsRH+tg62E4DeWQi1AHN7Tt/eHf71Var8IQP3C0/qvAQAeqw9rB/ RIt/sE+R1snBXtXr4DpV2c0IJBI3/QMD2NxU71P46+TqFWe/iMgy3bvLUyi82zML 0l2kdb5ilSijWM7CHyC+PQfmJiXCFBQ6sgOqogFiGBvGT3PgA+SyXU/U6NZYNN/f dStLoWLsVXQCsbb5Ukovs1EyMoh5ztMJJNa8kfSM7eqxnAsSg0umBGoGBv2RcUrQ yZGxQ8XOZKGXgkEHCcKPGUciJBxBF9OhJNMFT6HMA8hT0Hl5P6WIa5hKkXdcoRjK HmcpV5KxNkO1yJnJe6ty =zrv/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjspw-0003m4...@franck.debian.org
Accepted rosegarden 1:14.02-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 May 2014 23:51:02 +1000 Source: rosegarden Binary: rosegarden rosegarden-dbg Architecture: source amd64 Version: 1:14.02-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Stuart Prescott stu...@debian.org Description: rosegarden - music editor and MIDI/audio sequencer rosegarden-dbg - Debugging symbols for Rosegarden Closes: 747770 Changes: rosegarden (1:14.02-2) unstable; urgency=medium . * Add libz-dev to build-dependencies (Closes: #747770) Checksums-Sha1: 4ae652c5900d9278bff77d3e06f42c7bc9649279 2318 rosegarden_14.02-2.dsc 4a645e82f66813c2fb3a8c7439bb663ed36864f1 14432 rosegarden_14.02-2.debian.tar.xz 8f698a84b033addc2012ddba03c500878bfc4732 8000230 rosegarden_14.02-2_amd64.deb 537d25dcb7c92943467c2b54b5f348b5db5664f1 55824926 rosegarden-dbg_14.02-2_amd64.deb Checksums-Sha256: e4ff3508c0d5568a5c3082b5aefd2a040e46be4c49b17d641166ff8b40c32f5c 2318 rosegarden_14.02-2.dsc f58670dd6a13fdcb3f37f6f0cc30914c39d5ca7536b28aad90457e6dc0481272 14432 rosegarden_14.02-2.debian.tar.xz 273261861514de26d9914b3b97ad579f52ff0b9234b266403b25bed53fb56a01 8000230 rosegarden_14.02-2_amd64.deb e6694f2afa8b5a042711dd2f49ccb084f907bb6bb3daca8083daf195bef46b2f 55824926 rosegarden-dbg_14.02-2_amd64.deb Files: eee785c36359425e3d9236c51f3ef807 8000230 sound optional rosegarden_14.02-2_amd64.deb 961e02f6f2fc6f5c2bb2159d68ff8504 55824926 debug extra rosegarden-dbg_14.02-2_amd64.deb 22ada6d5547f823887dfa2d3f88dad0e 2318 sound optional rosegarden_14.02-2.dsc 2b687ddf9129047f583184d22c6abc08 14432 sound optional rosegarden_14.02-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJTcNKLAAoJELvBfrsTlvL3Qx0QAJn/htE7nMA0KWc+Z/ezSQDb LeX0jtpypXY5PioDefIekT0m4vSVHUAGCwQfXyTtR0dM37FMqpO30tJNosLoYrGl SqAZHuKIrI93FvN02/wQb0nLQbu/FUddaQ9K9NAEs6U6FDefXNSKMpECQMCUhOY5 K7r9OcmSyrlejKGovXHxbV6O8BdHAcBn01XusiiBaObhPQ0ILnFHp8M1G025nc0N 2fs+tlyxKA/ebKXfZ5BNCFM0WPmLBTYkruBzt5NlvyMmTVkaIlpxRAgFxhqsgOZ3 vssNy6GFxQ3EJCv0lAnc5SYxi7HW60CY+ZVK8SqfZBQVrgNsZc8Ck/hS8kHUO+R1 us/YGeYlWBb5jJtMWMSJf4KX0GxUTDck6SqSyoVBdeNhrYARkdbvIHjMXbYdUtJ1 1vV6a+zzMUNW9Rcpe4H6LKPaRYEH2Ei+7ojYOe45C7uEPGEdqWxX8G5vTGxN2BBv Z7tJWeCmcHY8U/dzaWrnjGzrZOKx140cCYzKKGOTtKzzFDLcQK9AU3MLG04udnP4 +b5ex/9w3B+++q1V7a5eHu22hQ3m0Mai1YxAV0Pp1Ox5qbIkVjsxbFrafGwovNom c1Ft8eZHNHtw+BjicxkpYAKhzCB/MdRaJKZL8o7is5RXg57DRDtd4gJcLiQqDgVZ qrQANTjfoP0K3bDvIcMg =QNrI -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjspj-0003hp...@franck.debian.org
Accepted ruby-bacon 1.2.0-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 May 2014 11:25:02 -0300 Source: ruby-bacon Binary: ruby-bacon Architecture: source all Version: 1.2.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Antonio Terceiro terce...@debian.org Description: ruby-bacon - Small RSpec clone Closes: 747728 Changes: ruby-bacon (1.2.0-4) unstable; urgency=medium . * Team upload. * Rebuild against gem2deb (= 0.7.0~) to install gemspec in shared location for all Ruby versions. * debian/ruby-tests.rb: run tests against Ruby interpreter being tested (Closes: #747728) Checksums-Sha1: 0ffe41afffe7314d90a456de05829823ea8ef24d 2015 ruby-bacon_1.2.0-4.dsc cff8610374e6e4e86723fed5f4d56055b3acbc16 3240 ruby-bacon_1.2.0-4.debian.tar.xz cf1b61250ba9be55235ba01ed411af6c01355d80 14868 ruby-bacon_1.2.0-4_all.deb Checksums-Sha256: 1098a61d47028a6cfd832891af69f1ca3ffe65147788bdb0f3512b35337ea434 2015 ruby-bacon_1.2.0-4.dsc 3a444b5e074668f87926c7bc24b53a12b1d11ce318229ea4136807baec9ba2da 3240 ruby-bacon_1.2.0-4.debian.tar.xz 18374f27d1ad75b55c7860f4ab483fefb5c8e0b54da13129b0f21bbf4cff3e3b 14868 ruby-bacon_1.2.0-4_all.deb Files: d15d8ba665c1f350635de1ce4b19170a 14868 ruby optional ruby-bacon_1.2.0-4_all.deb e28423e582303063e5fc90fe80e681de 2015 ruby optional ruby-bacon_1.2.0-4.dsc 151cb80d26abd0f3999c7940f9b53845 3240 ruby optional ruby-bacon_1.2.0-4.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTcOC3AAoJEPwNsbvNRgveiOoQAN7/FB6NnD5r0O2x+lMwdMpA dRRo1alIeqiNCILDk8ETk173I8146uIW96piiD/Y9UKvN8r1ejzLWPLavt1vauh5 KK7ocdSJFRD4VhnSyTydyd/3xkrLC4Po8B+XgEXPZwTKhscqpL77PmKwEXAGK2w4 NY0fzN11IYqnuBxs3mppHosPx+K7DKzcOMGh4icu7mYEV2M3/HVf+y+y0ng0Q/Oj A4z6di9SDQyyw7U/Y/LBTRFCUMfgR4ogEv+KIu3MRcmvcZDJs7LwJvwmMN/JMJF4 VmzoZYxgj6xWIeAcBYHhkes+4YpkBKhylePIYLWbZtHjCljM9h633EqMeX4i+w0R sV+f1iXM/ah3oUCzTv9LDjteqPTa3Ab+ge9cp1mmfC9ZQHIanMC9ugE7ld/ZOgqu k0PLefV1jjjMGbwX+reFpNEDoV3Qi+VIyDj5iBxjjw5Egh55v732So2Qwixh5oQJ 0L64yXCE/0HNKsolHK8Omnn9jc0w+9XXIyXJPttj5RaiZcIM2YspTQINNbRHB6u2 vkLWCSwfLln/BMLmHsqS2B98ksvoSN7LMto+DRBd+WXJVXfRwb2LGAUwW35SnBth Aa6Ke7yvxgSjxRA1wK18udE3sVTaTP3uNp4JUwvs2wrRUTen+zPCfxqpn2vrv/TQ Jt10zykJ6caW6HuVdK2t =8Wdo -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjspp-0003jq...@franck.debian.org
Accepted vagrant 1.4.3-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 12 May 2014 11:50:35 -0300 Source: vagrant Binary: vagrant Architecture: source all Version: 1.4.3-2 Distribution: unstable Urgency: medium Maintainer: Laurent Bigonville bi...@debian.org Changed-By: Antonio Terceiro terce...@debian.org Description: vagrant- Tool for building and distributing virtualized development enviro Closes: 744033 Changes: vagrant (1.4.3-2) unstable; urgency=medium . * Use the default Ruby interpreter instead of hardcoding ruby1.9.1 (Closes: #744033) * Add myself to Uploaders: Checksums-Sha1: 669e3f3632ca01256b5b83d66d5ec1135c386a83 1939 vagrant_1.4.3-2.dsc e1c5a545be2506acca6fa02be1cc29ed519dab6a 4924 vagrant_1.4.3-2.debian.tar.xz 9ac3fa31099e2e237764e33007303e67c511c129 218280 vagrant_1.4.3-2_all.deb Checksums-Sha256: fd0e37f59c70eae0864f44f02af562bf9739a8c24b711d82f185a5c019432a7a 1939 vagrant_1.4.3-2.dsc 46704e8c88a8b8aa3ab3d19fe42f02de3c8db553e553ccd1997272189f357400 4924 vagrant_1.4.3-2.debian.tar.xz 61d2df44bbcb7092eeac5e17f5445b347a573354c4d249c62a9b5f216dbe9fdf 218280 vagrant_1.4.3-2_all.deb Files: 8d6d88ebfe717a141392bee34e8af2ba 218280 admin optional vagrant_1.4.3-2_all.deb c775da081edcf47dcf1ab37d3d895b00 1939 admin optional vagrant_1.4.3-2.dsc c742ca827f523a73eb3f242c366ddc43 4924 admin optional vagrant_1.4.3-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTcOKVAAoJEPwNsbvNRgveN+sP/j4QTZ4FNjqD63I6vDNNYAuU BaLaHXhiW60qLLMmZvS0rKCF3AK4Ljo3+D+RGXWPC2CgFRD8lPzqpY3hACv7XTM2 BOlnHe6SnCwoq2vc1Aj+Rz13bz5h+7uAKZ+yQeOo963uN+3iF6SZ9VoubW2rSo/N pyL5jFx6f4qfI7lvL35qhT5M4nJV7Q6cIHWX39euOTLoGzTezAMHWF24nRBdk+Dt LTE+zLAAwx7366ReRijtWk5TRuT2CmECZbexd3PZ6QZRO1n9HnzVqPRIYzOAdM19 lV/g+BNWidqzmXNVgyLpIB+PxXyEHKyG8oD56EWtWxutLtsMVHIUvHbeRK6g 0q+WX9iHn0qw71hMI5sc4c4ZVstyn887p+Wg/ogiw8IpS7ull4anVDFgSeMFoydF VDQsFEkiTW/Niwm8AaFFDQXNpb3sa704AZu2b3D/AdFPrtm7baXjFdAjkoApmvxd 9TmFjCsE1E4TyLHrk+09labzJ8m8SaMS4k0uHlcg194Yyy/0Tm9vLavs9+CjkPF0 5MoehsXQ41feDwuy6vASJ8cCwAM2ajTbv6wIHxQFIHZGVmYYvM7aiiTjt9tjU+N8 D6WsrNYCxPn6MYF9Ieo1Ecq1nj09g3HplLlNtmktkP10d6cAZGJruAEFGLnICSXs 5nE81Kfv/WW0eoyQiq5b =RKtc -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjsqb-0003gv...@franck.debian.org
Accepted bcrypt 1.1-8.1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 08 May 2014 11:46:38 +0200 Source: bcrypt Binary: bcrypt Architecture: source amd64 Version: 1.1-8.1 Distribution: unstable Urgency: low Maintainer: Kevin Coyner kcoy...@debian.org Changed-By: Agustin Martin Domingo agmar...@debian.org Description: bcrypt - Cross platform file encryption utility using blowfish (Decrypt on Closes: 700758 Changes: bcrypt (1.1-8.1) unstable; urgency=low . * Non-maintainer upload. * Disable RC broken encryption support (Closes: #700758). Make this a decrypt-only package for already created files. Checksums-Sha1: bb31f8e9b64a91af8254eacfa4a733bbfb3b0171 1021 bcrypt_1.1-8.1.dsc 4acbaa65b827a96d1d6b2d5a681b04a70fe6532f 7857 bcrypt_1.1-8.1.diff.gz 97bd79e949123e225e6192c974ce0cf296034843 18480 bcrypt_1.1-8.1_amd64.deb Checksums-Sha256: 16b36eb90f343e236fef95110a886e89c02968d07032eb3c7b84b435c0d74dd3 1021 bcrypt_1.1-8.1.dsc c3ec02e25d2eb1a9baa6d545b3193bd418c69f352eedd2f0c22163c156adc63e 7857 bcrypt_1.1-8.1.diff.gz 6f1cd53f3d84136284ab64d8794dde736b55a33b3445dd9150ea6c2f37d0adf4 18480 bcrypt_1.1-8.1_amd64.deb Files: 9c889ff6a6bc45ac02ecf56d4231bb94 18480 utils optional bcrypt_1.1-8.1_amd64.deb dd6914e40875c304ed48e5a398624a1f 1021 utils optional bcrypt_1.1-8.1.dsc f4adb033c3113a8be8b4914770451430 7857 utils optional bcrypt_1.1-8.1.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlNwrM0ACgkQTShHqj72Dpz8AwCdGds1NSrSYhklE5Qt8HnTTSvY DYsAoJSvPqa+cdYGWjZenET+CrnzRSYx =Rbaa -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjsxb-0007sj...@franck.debian.org
Accepted commons-jci 1.1-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 12 May 2014 17:21:17 +0200 Source: commons-jci Binary: libcommons-jci-java libcommons-jci-rhino-java libcommons-jci-groovy-java libcommons-jci-janino-java libcommons-jci-eclipse-java libcommons-jci-java-doc Architecture: source all Version: 1.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Emmanuel Bourg ebo...@apache.org Description: libcommons-jci-eclipse-java - common Java interface for various compilers - Eclipse JDT libcommons-jci-groovy-java - common Java interface for various compilers - Groovy libcommons-jci-janino-java - common Java interface for various compilers - Janino libcommons-jci-java - common Java interface for various compilers - Core and FAM libcommons-jci-java-doc - common Java interface for various compilers - documentation libcommons-jci-rhino-java - common Java interface for various compilers - Javascript Changes: commons-jci (1.1-2) unstable; urgency=medium . * Transition to libasm4-java * Standards-Version updated to 3.9.5 (no changes) Checksums-Sha1: 76ace4f0053e2ae9d2606fd83fa826c0627e56b6 2630 commons-jci_1.1-2.dsc db7f547c11a572b6a9f0124e9ae36420c68b7c10 4336 commons-jci_1.1-2.debian.tar.xz 6683f6aaf2df2481e9b57099e75e427c456ec94e 44376 libcommons-jci-java_1.1-2_all.deb 49b2e1885c93bd49ccdd9fea5f050629bdfa1342 16950 libcommons-jci-rhino-java_1.1-2_all.deb b6f41f51ceef89283e142398469d146fbf177bb9 14038 libcommons-jci-groovy-java_1.1-2_all.deb d77cb6cbe634bde0586b05019745ff6f30563b65 19138 libcommons-jci-janino-java_1.1-2_all.deb 6483976ba5dc864f12272295b552bc89452516a0 21618 libcommons-jci-eclipse-java_1.1-2_all.deb 2b221f64c4ec1540b215601492aa9830eb4d300a 53736 libcommons-jci-java-doc_1.1-2_all.deb Checksums-Sha256: f7dcce43d14433968678cbbfa36e9a128820690f42cc3fae3543e7023c912aea 2630 commons-jci_1.1-2.dsc a2290fd9e86d544c5af9ac16bbac98692da5685534335ddbd4459ea5a387c547 4336 commons-jci_1.1-2.debian.tar.xz 9191ef83c3de6f7d971c86cfe14d5b2372bf30533e8946916ad6e43b8fbe49d1 44376 libcommons-jci-java_1.1-2_all.deb 596ad76e5262ede1a97be89d0aa61ce870b79cb1b608c6216872beec6076be76 16950 libcommons-jci-rhino-java_1.1-2_all.deb 749d51a9ddcad744bf10f3e284e04c9834572c30cc8d89b87a9bb9af73d383df 14038 libcommons-jci-groovy-java_1.1-2_all.deb 4ab611709ddcc6c47b5152b027466500a0321edbbb5bf67fb71d82d0ceb153e8 19138 libcommons-jci-janino-java_1.1-2_all.deb 47679c502f5d7fb28271fe48ec3f897511ef8c0027b91ec9cabe41689f8a6537 21618 libcommons-jci-eclipse-java_1.1-2_all.deb d532cc9ec58d1e4ba905d61dbbfd852854eec59beb3be6a060776edd4d6edbff 53736 libcommons-jci-java-doc_1.1-2_all.deb Files: a58555b98550e9e0288e10b21e5cfca2 44376 java optional libcommons-jci-java_1.1-2_all.deb 2cf41bdf96518d75aa00eb16b6d990bd 16950 java optional libcommons-jci-rhino-java_1.1-2_all.deb 0f418c6d064a25e13ca581bf85a0e996 14038 java optional libcommons-jci-groovy-java_1.1-2_all.deb 858b37b94cd6c7d352b6d94b34d6133b 19138 java optional libcommons-jci-janino-java_1.1-2_all.deb 93835ee06f7031a56bf7bba7c5df6299 21618 java optional libcommons-jci-eclipse-java_1.1-2_all.deb e24fc455f74115c5970e82345df4708f 53736 doc optional libcommons-jci-java-doc_1.1-2_all.deb 98aa8c9dbb8c604b9a492ad3ea349b3b 2630 java optional commons-jci_1.1-2.dsc e9d70fe8a8d270a3b26f3e0bfd62dc4c 4336 java optional commons-jci_1.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJTcOndAAoJEPUTxBnkudCsya4P/3012I5OcRJeHd/XOPb9hVwP LAoWdz1Ws9PosWUNinJ/6XVK81zx8OOoyIqUsbYQNSkejwv8rUw9lmlVM5Kf9LBU s9vjlfTqeC4KCZNsmHWz/EtYmgC4cLT7y5R+4jmte3sHwDguPUAj4w3k2/Ey9yH4 y3RPJKqtUtSW1JrO70Er78Gv6WCYSVY00VoKbN7MeZQ32Fw+93IeNmWpNayUzhAJ F4Ky+SwzzqsbpsUtJSymgINSbJcv6ykVkHnszAg/d0DAKNBLH4OB9jbanT+HamF6 w0OMB7PEhoHVC0HLjX05URYWFwKGngOkc9h5NUza7yIELqvwErsm7cMji73nwFt/ eGKTTR6VWE2c1Sly1AnmexlNSYiRuoGQE0b/SJXmLj8Mse44ir1Se2i4bD/XqENX uBZfFrbaRrwN3o6HhID01HM3XooRc/H4DV3hatt/jctBdbGb22Dqbn5pMWnrYA9D TYzOrlFJ5/DkPpaiDyz3aJqitRHqjpxZdgjadyPyYRrhu3VLbi1uWTfZ9sjfefYv Y6hmRLXf/rBg5zyKevjdMUaefPjtgqpWxLk2XxE04wNjteOwv7FK9CqS4HlK54+A S7kViFir9MvdZFXFCqmrUjjoF5tgNFZnlX5aSxPSGUgP9rRuH2CcxmQkpVH1N0xU dKcvrEey+0EzjCIbBZYs =w7Pj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1wjsxu-0007az...@franck.debian.org
