Bug#769866: ITP: argparse4j -- a command-line argument parser for Java based on Python's argparse module
Package: wnpp Severity: wishlist Owner: Tim Potter t...@hp.com * Package name: argparse4j Version : 0.4.4 Upstream Author : Tatsuhiro Tsujikawa tatsuhir...@gmail.com * URL : http://argparse4j.sourceforge.net * License : MIT Programming Lang: Java Description : a command-line argument parser for Java based on Python's argparse module Argparse4j is a command line argument parser library for Java based on Python's argparse module. Here is a summary of features: * Supported positional, optional and variable number of arguments. * Generates well formatted line-wrapped help message. * Suggests optional arguments/sub-command if unrecognized arguments/sub-command were given. * Takes into account East Asian Width ambiguous characters when line-wrap. * And many others. -- 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/20141117045101.7.93046.reportbug@02ed91797728
Re: Being part of a community and behaving
On Nov 17, Steve Langasek vor...@debian.org wrote: This is what many still (retorically) wonder about: we the systemd maintainers did not reject that change, https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;bug=746578 Please try to be less selective in your quoting: the issue was still being discussed. -- ciao, Marco pgpeZJ47GHahw.pgp Description: PGP signature
Re: Being part of a community and behaving
m...@linux.it (Marco d'Itri) writes: On Nov 17, Steve Langasek vor...@debian.org wrote: This is what many still (retorically) wonder about: we the systemd maintainers did not reject that change, https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;bug=746578 Please try to be less selective in your quoting: the issue was still being discussed. I see. So any systemd bug with a 'wontfix' tag is still considered open for discussion? That's good to know. Thanks. Bjørn -- 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/87bno6f8h2@nemi.mork.no
Re: RFC: DEP-14: Recommended layout for Git packaging repositories
On Mon, 17 Nov 2014, Ron wrote: Anything that doesn't store the full debian version (be it a git tag or a filename) will have a colision risk. Consider a package that has versions 1:2.3.5-1 and 5:2.3.5-1. Right, that was one of the first cases I mentioned. When you upload 5:2.3.5-1, dak will reject it exactly because they will collide. :) Yes, you're right. Our archive is braindead re. epochs since basically day one, and blocking colisions in dak was deemeed the lesser evil when compared to the fallout of fixing the archive filenames. fwiw, I don't consider that a compelling reason alone to not include the epoch in tags - but you appear to have just confirmed that not many people know this, even when it's explicitly mentioned in a thread they just replied to! So I think *that* is probably worthy of a mention if we do recommend including the epoch in tags :) Ah, sorry about that... If the answer is instead something like I want automated tools to be able to assume they can perfectly reverse the mangling and assume some semantic meaning to the text in the tag, then we're into Broken By Design territory and we really need to look more closely at *exactly* Well, we can have a perfect, reversible transformation between the debian version namespace and the debian git-tag version namespace, where debian means a vendor that uses dpkg and the deb format. No. I don't believe you can. Mangle this version in a way that's legal to git: 0:1.2:3..4-1~~2..3.lock True. Getting git to accept .. and a .lock suffix in a tag.. urk. Point taken. Yeah, that'd call for %-encoding or something equivalent, and those always require also the definition of a canonical form. Yes, it's a corner case you've probably never seen, but the troublesome parts of that are all legal debian versions. Yes, just like 1:1.2.3-4 versus 5:1.2.3-4, that dak rejects because the Debian archive doesn't preserve epochs in its storage layer (filenames). One interesting detail is that at least apt _DOES_ restore the epoch information in the deb filenames (it uses URL-like %-encoding, though, so : becomes %3a). I'd say we should get the epoch-in-tags detail documented in DEP-14. And the archive restriction re. epochs really should have been documented in debian policy. It is not even in the developer's reference... but this is offtopic for this thread. Henrique, would you care to elaborate on your definition of safer? Sure. I consider safer a design that loses no information when translating between the debian version namespace and debian version git-tag namespace, because you won't have permanent colisions among debian versions that differ only on the epoch. Ok, I can agree with that definition, but as I showed above, this plan doesn't satisfy it. You'd need to fully URL encode them or similar to have that, and I don't think we should do that. I agree that a full encoding that requires canonical forms is way too painful, and that we should not go there. You can still semi-meaningfully encode the epoch in a way that is a clue to humans, but you *can't* guarantee the version is reversible from the necessary mangling. If we mangle by removing whatever git objects to, yes, it won't be reversible, at which point we might as well not bother with epochs. I'd still allow epochs as optional, but that would cause a headache when you have something like 1:1:4-1 for a debian version... best to recommend that they be removed when tagging, instead. So I retract any objections I had against epoch-less tagging. But I feel DEP-14 should document this stuff. Are there actually already existing tools that rely on reversing this? I sure hope there aren't any. If there aren't we certainly shouldn't be encouraging creating new ones with this flaw in the future. I agree. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- 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/20141117114929.ga14...@khazad-dum.debian.net
Re: Pre-Depends: init-system-helpers
On Mon, 17 Nov 2014, Anthony Towns wrote: Having a single tool that does the basic stuff admins and maintainers need independent of init system seems like the right approach to me. *-rc.d is a terrible name for such a tool, though :( Err, yes. There were complains about the -rc.d prefix way back in Debconf2, but the truth is the ship had sailed already (due to update-rc.d). Migrating to a new tool with a less obnoxious name isn't a problem, but this needs to be planned carefully as it is going to span at least two stable releases. And invoke-rc.d and update-rc.d compatibility interfaces will have to be kept around for a *long* time, probably for at least two more stable releases, to avoid breaking things for third-party packages that don't use the LSB compatibility layer. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- 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/20141117121058.gb14...@khazad-dum.debian.net
Re: Pre-Depends: init-system-helpers
Hi, Henrique de Moraes Holschuh: On Mon, 17 Nov 2014, Anthony Towns wrote: Having a single tool that does the basic stuff admins and maintainers need independent of init system seems like the right approach to me. *-rc.d is a terrible name for such a tool, though :( Err, yes. There were complains about the -rc.d prefix way back in Debconf2, but the truth is the ship had sailed already (due to update-rc.d). The (author of the) document might want to mention that yes, this name is stupid – and no, we can't easily change it. -- -- Matthias Urlichs -- 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/20141117122946.ge16...@smurf.noris.de
Re: Bug#769851: ITP: puppetlabs-spec-helper -- Ruby library for puppet module testing
Jordan Metzmeier jmetzmeie...@gmail.com writes: * Package name: puppetlabs-spec-helper This is already packaged as https://packages.debian.org/sid/ruby-puppetlabs-spec-helper -- Stig Sandbeck Mathisen -- 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/87fvdhyl7f@dagon.fnord.no
Re: Being part of a community and behaving
On Thu, Nov 13, 2014 at 11:02:53AM +0100, Bálint Réczey wrote: Dear Josselin, I have just noticed your blog post on planet.debian.org: https://np237.livejournal.com/34598.html I would like to ask you to resist the temptation of publishing similar posts. It makes fun of part of our community which you are well aware of and it also shows corpses which probably did not ring a bell in you. Skeletons are *not* corpses. -- 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/20141117141322.GI20978@tal
Re: Pre-Depends: init-system-helpers
On Mon, Nov 17, 2014 at 10:10:58AM -0200, Henrique de Moraes Holschuh wrote: On Mon, 17 Nov 2014, Anthony Towns wrote: Having a single tool that does the basic stuff admins and maintainers need independent of init system seems like the right approach to me. *-rc.d is a terrible name for such a tool, though :( Err, yes. There were complains about the -rc.d prefix way back in Debconf2, but the truth is the ship had sailed already (due to update-rc.d). Migrating to a new tool with a less obnoxious name isn't a problem, Heh, isn't a problem seems a bit understated... but this needs to be planned carefully as it is going to span at least two stable releases. And invoke-rc.d and update-rc.d compatibility interfaces will have to be kept around for a *long* time, probably for at least two more stable releases, to avoid breaking things for third-party packages that don't use the LSB compatibility layer. If deb-systemd-* were to get merged in, it might be worth doing a name change at the same time, I guess. Changing either before jessie doesn't seem remotely plausible. I wonder if it would make sense to just merge it all into the service command; ie: # service --use-policy ssh start # service --use-policy ssh restart # service ssh enable # service acpid.socket mask-for-upgrade in place of: # invoke-rc.d ssh start # invoke-rc.d ssh restart # update-rc.d ssh enable # deb-systemd-helper mask acpid.socket I wonder a bit if it wouldn't make even more sense to just make the common command be systemctl, with Debian-specific patches for --use-policy and the various extra behaviours where necessary. Maybe just having a systemctl script with mostly compatible syntax provided for alternative inits would be a better approach. (The disadvantage to that would be that systemctl's a C program, so patching Debian specific options would be harder than with sh/perl scripts like service/deb-systemd-*/*-rc.d) Cheers, aj -- 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/20141117143624.ga4...@master.debian.org
Bug#769907: general: non-sysvinit init systems are made of fail
Package: general Severity: important Dear Debian Maintainers, I tried the alternative init systems (namely upstart and systemd) and while I think there is some potential in these systems I don't think they are ready for Jessie. As basic system component the init system needs to be very realiable which cannot be guaranteed for a piece of software that is introduced and installed by default as core system component in the same release cycle. There was some possibility to install alternative init system in wheezy but as the support for switching between the various systems was not in place it was not very practical and the packaging tools discouraged such use. I tried to install an alternative init system on like half a dozen of systems and I am disappointed. I stumbled upon two serious problems with these new systems. 1) the problem with new feature in systemd which considers all filesystems in fstab vital for system boot and stops boot if they fail. It's been decided that although it is a change in behaviour that might render some systems unbootable it's technically correct implementation and only enforces that non-vital filesystems are marked as such in fstab which should have been the case from the start. 2) other problem is 'mystery meat init' - you see some initial bootloader or kernel messages and when init starts .. nothing. When init decides a filesystem needs to be checked or that it has to stop due to error .. nothing. To be a reasonable sysvinit replacement systemd and upstart must output messages to consoles(s) to which sysvinit did output messages, even on systems with multiple consoles (eg. serial, vga, kms). Note that this is on systems where sysvinit does give messages on the console so if the system was upgraded to systemd as part of release upgrade it would lose console as the result or upgrading to new release. I am wondering what other subtle bugs are lurking in these new init systems. I am not completely against switching to a new init system but imho that should be done only once that init system was avaialble for at least one release as routinely installable and uninstallable package. Otherwise the core system component cannot possibly have been tested for suitability in general and for good integration into Debian in particular. Thanks Michal -- System Information: Distributor ID: Ubuntu Description:Ubuntu GNU/Linux testing (jessie) Release:testing Codename: jessie Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20141117144143.9935.25763.reportbug@iscsi
Re: Being part of a community and behaving
On Mon, Nov 17, 2014 at 11:05:13AM +0100, Bj??rn Mork wrote: m...@linux.it (Marco d'Itri) writes: On Nov 17, Steve Langasek vor...@debian.org wrote: This is what many still (retorically) wonder about: we the systemd maintainers did not reject that change, https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;bug=746578 Please try to be less selective in your quoting: the issue was still being discussed. I see. So any systemd bug with a 'wontfix' tag is still considered open for discussion? That's good to know. Thanks. Isn't any (open) bug tagged wontfix still open for discussion? If you've got new information, or a new approach that the maintainer might prefer, you can post it to the bug and discuss it with the maintainer... (That said, I didn't see any discussion in that bug from people listed in the systemd Uploaders line other than Michael Biebl's complaint about a systemd-shim bug two months after the wontfix tag was added. That doesn't *look* like it was still being discussed to me. Maybe that just means someone summarising irc/list discussions to the bug would have been helpful) Cheers, aj -- 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/20141117144829.gb4...@master.debian.org
Bug#769907: marked as done (general: non-sysvinit init systems are made of fail)
Your message dated Mon, 17 Nov 2014 15:55:49 +0100 with message-id 201411171555.56561.hol...@layer-acht.org and subject line Re: Bug#769907: general: non-sysvinit init systems are made of fail has caused the Debian Bug report #769907, regarding general: non-sysvinit init systems are made of fail to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 769907: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: general Severity: important Dear Debian Maintainers, I tried the alternative init systems (namely upstart and systemd) and while I think there is some potential in these systems I don't think they are ready for Jessie. As basic system component the init system needs to be very realiable which cannot be guaranteed for a piece of software that is introduced and installed by default as core system component in the same release cycle. There was some possibility to install alternative init system in wheezy but as the support for switching between the various systems was not in place it was not very practical and the packaging tools discouraged such use. I tried to install an alternative init system on like half a dozen of systems and I am disappointed. I stumbled upon two serious problems with these new systems. 1) the problem with new feature in systemd which considers all filesystems in fstab vital for system boot and stops boot if they fail. It's been decided that although it is a change in behaviour that might render some systems unbootable it's technically correct implementation and only enforces that non-vital filesystems are marked as such in fstab which should have been the case from the start. 2) other problem is 'mystery meat init' - you see some initial bootloader or kernel messages and when init starts .. nothing. When init decides a filesystem needs to be checked or that it has to stop due to error .. nothing. To be a reasonable sysvinit replacement systemd and upstart must output messages to consoles(s) to which sysvinit did output messages, even on systems with multiple consoles (eg. serial, vga, kms). Note that this is on systems where sysvinit does give messages on the console so if the system was upgraded to systemd as part of release upgrade it would lose console as the result or upgrading to new release. I am wondering what other subtle bugs are lurking in these new init systems. I am not completely against switching to a new init system but imho that should be done only once that init system was avaialble for at least one release as routinely installable and uninstallable package. Otherwise the core system component cannot possibly have been tested for suitability in general and for good integration into Debian in particular. Thanks Michal -- System Information: Distributor ID: Ubuntu Description:Ubuntu GNU/Linux testing (jessie) Release:testing Codename: jessie Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Hi, On Montag, 17. November 2014, Michal Suchanek wrote: Package: general I'm sorry but this is not a general bug in Debian. Also your description of these two serious problems lack any specific problems you encountered, for a start you failed to say whether you encountered these problem with systemd or upstart. Thus closing. cheers, Holger signature.asc Description: This is a digitally signed message part. ---End Message---
Bug#769910: ITP: fnordmetric -- write SQL queries that return SVG charts rather than tables
Package: wnpp Severity: wishlist Owner: Sebastien Delafond s...@debian.org * Package name: fnordmetric Version : 1.0~alpha Upstream Author : Paul Asmuth * URL : http://fnordmetric.io/ * License : GPL3 Programming Lang: C++ Description : write SQL queries that return SVG charts rather than tables FnordMetric has two components: . FnordMetric ChartSQL allows you to write SQL queries that return charts instead of tables. The charts are rendered as SVG vector graphics and can easily be embedded into any website and customized with css in order to build beautiful dashboards. You can execute ChartSQL queries from the command line against a number of external sources like CSV files or a MySQL database . Fnordmetric Server is a standalone HTTP server application. It exposes a web UI and a HTTP API to run ChartSQL queries and collect timeseries data. You can use fnordmetric-server as a one-stop solution for metric collection and charting. Since fnordmetric-server aims to be a StatsD+graphite competitor, it implements a wire compatible StatsD API. FnordMetric Server can store the collected timeseries data on local disk or in external storage (HBase) -- 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/20141117145926.8698.76769.report...@hetz1.mine.nu
Re: Bug#769851: ITP: puppetlabs-spec-helper -- Ruby library for puppet module testing
close 769851 thanks On Mon, Nov 17, 2014 at 8:07 AM, Stig Sandbeck Mathisen s...@debian.org wrote: Jordan Metzmeier jmetzmeie...@gmail.com writes: * Package name: puppetlabs-spec-helper This is already packaged as https://packages.debian.org/sid/ruby-puppetlabs-spec-helper Thanks. I probably only searched stable by mistake when checking to see if it was already packaged. Regards, Jordan Metzmeier -- 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/cad758ritp-f9o3eondxkqj4wcbhdeawvm00rzg8_8mbnii7...@mail.gmail.com
Re: Being part of a community and behaving
Bjørn Mork bj...@mork.no writes: I see. So any systemd bug with a 'wontfix' tag is still considered open for discussion? I can't speak to the maintenance practices of systemd maintainers, but if the bug isn't open to discussion, I close it. I think that's fairly common across Debian. If it's tagged wontfix but still open, that generally means one of two things: either it's still open for discussion, but the maintainers are indicating their current thinking on it, or it's a commonly-reported false positive (from the maintainer's perspective) and they're leaving it open so that people will see it in the bug list and see that someone else already reported it. In this particular case, it's going to be hard for someone who isn't following the discussion closely to know which meaning was intended, so probably better to read the thread or ask, rather than making an assumption one way or the other. -- 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/87zjbpyf2p@hope.eyrie.org
Re: RFC: DEP-14: Recommended layout for Git packaging repositories
Simon McVittie writes (Re: RFC: DEP-14: Recommended layout for Git packaging repositories): I agree that the expected contents of the branches are far more important than their names. Unfortunately, while acting as the Debian expert for Debian derivatives at $day_job, I keep finding that the answer to OK, I've cloned a package's git repository, I know what code change I want, now do I change the upstream source or drop a patch into debian/patches or what? is ... I can't actually answer that until you tell me which source package you're working on. This is indeed a very big problem. It is why I am working on dgit. I don't think this problem, of a mass of different branch structures, is going to go away any time soon. Simply because people don't seem able to agree. My answer is to create a parallel universe in which the branch structure is known. The maintainers of each package choose whether to use the dgit `universe', in which case certain basic assumptions can be relied on, or run their own `universe' in which case they can structure it however they like. Luckily git makes it fairly easy to transport changes from one universe into another. Ian. -- 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/21610.8498.518053.339...@chiark.greenend.org.uk
Re: RFC: DEP-14: Recommended layout for Git packaging repositories
Simon McVittie writes (Re: RFC: DEP-14: Recommended layout for Git packaging repositories): gbp-pq and git-dpm are the other way round: the tree can be built with dpkg-buildpackage, but the cost is that you have to commit in a way that isn't the normal git thing (either using a specific tool, or for the gbp-pq layout, dropping in pre-prepared patches and hoping they don't have conflicts, in the same way you might for svn-buildpackage). dgit is capable of tacking a git tree that came from dpkg-source, and which you have committed to in the normal way (eg as part of an NMU), and turning it into one that dpkg-source can represent. The latest version I have (unreleased, sadly, as there are a few more things that needs finishing off) is capable of converting the git commits individually into quilt patches, provided the extra history you have added is `linear enough'. Ian. -- 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/21610.8733.41862.987...@chiark.greenend.org.uk
Re: Pre-Depends: init-system-helpers
On Mon, 17 Nov 2014, Anthony Towns wrote: If deb-systemd-* were to get merged in, it might be worth doing a name change at the same time, I guess. Changing either before jessie doesn't seem remotely plausible. I wonder if it would make sense to just merge it all into the service command; ie: # service --use-policy ssh start # service --use-policy ssh restart # service ssh enable # service acpid.socket mask-for-upgrade service is an user interface, while deb-systemd-*, invoke-rc.d, and update-rc.d are first and foremost to be used by a package's maintainer scripts (postinst, etc). They have different design goals. IMHO it is best that we keep system interfaces separate from user interfaces like service, although I certainly have nothing against extending service with more user functionality. Just have service call into the system interfaces when required if you extend it. in place of: # invoke-rc.d ssh start # invoke-rc.d ssh restart # update-rc.d ssh enable # deb-systemd-helper mask acpid.socket I wonder a bit if it wouldn't make even more sense to just make the common command be systemctl, with Debian-specific patches for --use-policy I'd advise against that. We really should have Debian be the upstream of the interface layer used by maintainer scripts of deb packages. This is also part of the reason I don't like the idea of folding this stuff into service. service is somewhat compatible across distros, you don't mess with that lightly. and the various extra behaviours where necessary. Maybe just having a systemctl script with mostly compatible syntax provided for alternative inits would be a better approach. (The disadvantage to that would be that systemctl's a C program, so patching Debian specific options would be harder than with sh/perl scripts like service/deb-systemd-*/*-rc.d) Let's just avoid this whole can of worms, please. I have no strong feelings about these utilities being implemented in perl, shell or C, as long as they don't make a mess of the base system or become fragile during a worst-case dpkg breakage party. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- 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/20141117163804.ga24...@khazad-dum.debian.net
Re: Being part of a community and behaving
On Fri, 14 Nov 2014, Ralf Jung wrote: I was specifically talking about interfaces (as in, dbus signatures), Meh… I don’t even have dbus installed at home. (It is, on the work system, due to… virt-manager and iceweasel(?).) So, no need for anything systemd-ish. Well, even better for you :) . Then you are even less affected by what the git commit you referenced announces, than I am. Right. I just see a direction. After some years, you tend to recognise certain “hypes” and trends… 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.11.1411171738030.1...@tglase.lan.tarent.de
Re: Pre-Depends: init-system-helpers
On Mon, Nov 17, 2014 at 02:38:04PM -0200, Henrique de Moraes Holschuh wrote: On Mon, 17 Nov 2014, Anthony Towns wrote: If deb-systemd-* were to get merged in, it might be worth doing a name change at the same time, I guess. Changing either before jessie doesn't seem remotely plausible. I wonder if it would make sense to just merge it all into the service command; ie: # service --use-policy ssh start # service --use-policy ssh restart # service ssh enable # service acpid.socket mask-for-upgrade service is an user interface, while deb-systemd-*, invoke-rc.d, and update-rc.d are first and foremost to be used by a package's maintainer scripts (postinst, etc). They have different design goals. My understanding is that update-rc.d is the recommended way for admins to enable/disable services. Is that incorrect? (It's what I've documented in my proposed init guide/policy) Obvious alternative idea, provide a maintainer script oriented tool under a different name: service-maintscript ssh start service-maintscript ssh enable service-maintscript acpid.socket mask-for-upgrade But if we did that how would we recommend admins enable/disable services? Just use the native stuff (rm /etc/rc?.d/S*ssh; systemctl disable ssh)? IMHO it is best that we keep system interfaces separate from user interfaces like service, Yeah, I see where you're coming from. My intuition goes the other way; that it's better to have a single tool for both uses if that's feasible. We don't have anything special for doing cron jobs via packages compared to what admins might do to add a cron job, eg. Maybe that's a bad intuition though. BTW, it occured to me that it seems like a wart that update-rc.d doesn't respect policy-rc.d -- as it stands, policy-rc.d can prevent a service from (re)starting during install/upgrade, but it'll still start on the next boot. Is that just something that never got thought of / done, or does it actually make sense? Cheers aj -- 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/20141117170715.ga13...@master.debian.org
Re: Pre-Depends: init-system-helpers
On 11/17/2014 10:36 PM, Anthony Towns wrote: I wonder if it would make sense to just merge it all into the service command; ie: # service --use-policy ssh start # service --use-policy ssh restart # service ssh enable # service acpid.socket mask-for-upgrade in place of: # invoke-rc.d ssh start # invoke-rc.d ssh restart # update-rc.d ssh enable # deb-systemd-helper mask acpid.socket I agree that the service command is the way to go, as it became the standard everywhere, where invoke-rc.d didn't evolve. I wonder a bit if it wouldn't make even more sense to just make the common command be systemctl, with Debian-specific patches for --use-policy and the various extra behaviours where necessary. Maybe just having a systemctl script with mostly compatible syntax provided for alternative inits would be a better approach. I don't think so, because of the existing code base in maintainer's scripts. (The disadvantage to that would be that systemctl's a C program, so patching Debian specific options would be harder than with sh/perl scripts like service/deb-systemd-*/*-rc.d) And there's that too, yes... Plus we'd have to make it upstreamed too. Thomas -- 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/546a2c14.6070...@debian.org
Re: Being part of a community and behaving
Anthony Towns writes (Re: Being part of a community and behaving): Steve, as long as bugs like [1] are not fixed in systemd-shim, I'm not going to make it the first alternative. Installing a half-broken logind whould be a disservice to our users. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746578#27 I'm sorry that the TC decision here has caused the social fallout that it has. It's a shame that the init system many of our users are going to be relying on will be lacking Tollef's excellent contributions. But: A criticism seems to be that the TC getting involved, or deciding, was premature, because the systemd maintainers would have applied this patch themselves if they had been asked nicely, or something ? I think that after a refusal from the maintainers, with the bug tagged wontfix, anyone is entitled to refer the matter to the TC. It has often happened that someone has referred a bug to the TC and after some discussion it turns out that the maintainers were convinced, and made the proposed change. Indeed, after the unequivocal messages from the systemd maintainers, I think badgering them might have been inappropriate. If you don't like a decision someone else has made, and it doesn't appear that there is much more room for discussion, you should either live with the decision, or escalate it. We would like to avoid browbeating. During the discussion of the TC bug no-one from the systemd team suggested that they might review their decision in the light of the arguments that were presented in the TC. And indeed there is no requirement that a maintainer should do so. However, I think the TC is entitled to assume, during its deliberations, that maintainers' previously stated decisions and opinions continue to stand until the maintainers withdraw or contradict them. (I think the TC is also entitled to assume that the maintainers, once made aware that an issue has been referred to the TC, will provide any technical input that they feel is necessary.) As the TC discussions go through the various stages of fact-finding, to tentative conclusions, to draft resolutions, the maintainers continue to have the opportunity to see the facts and arguments being presented in the discussion, and to avoid a formal decision by providing a satisfactory solutions to the problem at hand. The bug referenced as [1] above was #756076 which was set as grave on 18th September, with a fix developed upstream on the 5th Nov, which was then uploaded to Debian on the same day (by Martin Pitt): This seems to be a different question. The criticism here would be that TC decision was technically incorrect, because at the time we voted (or at least at the time we called for votes) #756076 was still outstanding and ought to have been a blocker for changing the dependencies ? My understanding is that installing systemd-shim and indeed cgmanager is supposed to be harmless under systemd. So while swapping the dependencies would mean that some users who are going to be using systemd would get cgmanager installed, cgmanager would not (by default) be started, and those users would therefore not experience #756076. Therefore ISTM that #756076 was not a reason not to swap the dependencies. Serge Hallyn corroborates that here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755977#32 which we discussed here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746578#239 which was immediately before the TC CFV. Ian. -- 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/21610.11364.98070.231...@chiark.greenend.org.uk
Bug#769907: general: non-sysvinit init systems are made of fail
On 11/17/2014 10:41 PM, Michal Suchanek wrote: To be a reasonable sysvinit replacement systemd and upstart must output messages to consoles(s) to which sysvinit did output messages, even on systems with multiple consoles (eg. serial, vga, kms). Not really... Or at least, not until last summer when I uploaded a patched version of bootlogd to Sid. To this date, sysv-rc can't log to multiple consoles, unless the release team agrees that I fix Wheezy (see the release.debian.org corresponding bug: #767202). Cheers, Thomas Goirand (zigo) -- 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/546a2d33.20...@debian.org
Re: Pre-Depends: init-system-helpers
Anthony Towns a...@erisian.com.au writes: BTW, it occured to me that it seems like a wart that update-rc.d doesn't respect policy-rc.d -- as it stands, policy-rc.d can prevent a service from (re)starting during install/upgrade, but it'll still start on the next boot. Is that just something that never got thought of / done, or does it actually make sense? I thought that was intentional behavior, that policy-rc.d changes nothing except whether the service is actually started at the point at which it should or shouldn't be started. Consider, for example, bootstrapping a new system in a local chroot that will then be deployed as a virtual image. You want policy-rc.d to prevent starting any daemons from the chroot while you're installing and configuring packages, but you still want all the service management links and policy installed as normal so that, after you turn this into a cloud image, everything will run properly. -- 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/87h9xxyc68@hope.eyrie.org
Re: Being part of a community and behaving
Shachar Shemesh shac...@shemesh.biz writes: Please try to refrain from jokes other will find offending. That joke is in very poor taste, sir. -- Stig Sandbeck Mathisen -- 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/87d28ln3av@dagon.fnord.no
Re: Being part of a community and behaving
On 11/17/2014 at 12:12 PM, Ian Jackson wrote: Anthony Towns writes (Re: Being part of a community and behaving): The bug referenced as [1] above was #756076 which was set as grave on 18th September, with a fix developed upstream on the 5th Nov, which was then uploaded to Debian on the same day (by Martin Pitt): This seems to be a different question. The criticism here would be that TC decision was technically incorrect, because at the time we voted (or at least at the time we called for votes) #756076 was still outstanding and ought to have been a blocker for changing the dependencies ? My understanding is that installing systemd-shim and indeed cgmanager is supposed to be harmless under systemd. So while swapping the dependencies would mean that some users who are going to be using systemd would get cgmanager installed, cgmanager would not (by default) be started, and those users would therefore not experience #756076. Therefore ISTM that #756076 was not a reason not to swap the dependencies. My understanding is that the systemd maintainers' objection to swapping the dependencies was not about what would happen to users who are running systemd-sysv, but what would happen to users who are *not* - that they felt that automatically switching people from sysvinit-core to systemd-sysv was preferable to automatically giving them a known-partially-broken configuration based on systemd-shim and cgmanager. Again, if that's not correct, I'd be interested to be corrected on that point. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Pre-Depends: init-system-helpers
Am 2014-11-17 18:07, schrieb Anthony Towns: BTW, it occured to me that it seems like a wart that update-rc.d doesn't respect policy-rc.d -- as it stands, policy-rc.d can prevent a service from (re)starting during install/upgrade, but it'll still start on the next boot. Is that just something that never got thought of / done, or does it actually make sense? From a purely user-centric perspective: I would like to keep it that way. I have a couple of scripts lying around that automatically create LXC containers: debootstrap, install configuration management system, use that to change configuration and fetch list of packages to be installed and then use aptitude to install that list of packages. During the runtime of that script, I drop in a /usr/sbin/policy-rc.d in the target directory that just contains 'exit 101' (in addition to a shebang) in order to make sure that during the installation no system service gets started (this is especially the case under wheezy with sysvinit, I haven't tested this yet with jessie and systemd). But once the container is built properly, and I want to boot it, I actually DO want it to be the case that the services installed in those containers actually start. For example, if the list of packages for that specific container contains Apache, I want httpd to start once I boot the container. So to me, the current behavior of policy-rc.d is _immensely_ useful. Christian -- 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/7c3f39561c7a80a64948c34a8b727...@iwakd.de
Re: Pre-Depends: init-system-helpers
On Mon, 17 Nov 2014, Anthony Towns wrote: On Mon, Nov 17, 2014 at 02:38:04PM -0200, Henrique de Moraes Holschuh wrote: On Mon, 17 Nov 2014, Anthony Towns wrote: If deb-systemd-* were to get merged in, it might be worth doing a name change at the same time, I guess. Changing either before jessie doesn't seem remotely plausible. I wonder if it would make sense to just merge it all into the service command; ie: # service --use-policy ssh start # service --use-policy ssh restart # service ssh enable # service acpid.socket mask-for-upgrade service is an user interface, while deb-systemd-*, invoke-rc.d, and update-rc.d are first and foremost to be used by a package's maintainer scripts (postinst, etc). They have different design goals. My understanding is that update-rc.d is the recommended way for admins to enable/disable services. Is that incorrect? (It's what I've documented in my proposed init guide/policy) I don't think anyone ever wrote an initsystem-agnostic user interface for this, so people have been using update-rc.d. It caused a lot of problems before we forced the use of insserv. But I could easily be wrong about this. Obvious alternative idea, provide a maintainer script oriented tool under a different name: service-maintscript ssh start service-maintscript ssh enable service-maintscript acpid.socket mask-for-upgrade I have nothing against service-maintscript, although service-debmaintscript is likely safer since we are not likely to make any effort to make it usable by SuSE, RedHat, Gentoo, etc. But if we did that how would we recommend admins enable/disable services? Just use the native stuff (rm /etc/rc?.d/S*ssh; systemctl disable ssh)? Maybe extend service... BTW, neither rm /etc/rc?.d/S*ssh nor systemctl disable will do the right thing: both have pitfalls. No link is an undefined state for sysvinit rc when a runlevel switch happens (the correct way to disable something is to have a K link in all normal runlevels), and systemctl disable does not block socket activation automatically (refer to Debian bug #736258). IMHO it is best that we keep system interfaces separate from user interfaces like service, Yeah, I see where you're coming from. My intuition goes the other way; that it's better to have a single tool for both uses if that's feasible. We don't have anything special for doing cron jobs via packages compared to what admins might do to add a cron job, eg. Maybe that's a bad intuition though. The package maintainer mode interfaces expose a lot of user-unfriendly details which are easy to misuse *and* which are not going to be changed to become more userfriendly once in the field, since the package maintainer mode must NEVER break the backwards-compatibility of the ABI. BTW, it occured to me that it seems like a wart that update-rc.d doesn't respect policy-rc.d -- as it stands, policy-rc.d can prevent a service from (re)starting during install/upgrade, but it'll still start on the next boot. Is that just something that never got thought of / done, or does it actually make sense? policy-rc.d is an internal detail of the invoke-rc.d policy layer, which was designed only with package maintainer scripts starting or stopping services during install/upgrades/downgrades/removal in mind. It was not meant to be used for anything else. Therefore, policy-rc.d was never designed to set policy when administratively enabling or disabling services. We could extend policy-rc.d to be usable also by update-rc.d, but I would not go there unless there is an important usecase for this that is related to maintainer script use of update-rc.d. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- 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/20141117174741.gc24...@khazad-dum.debian.net
Re: Pre-Depends: init-system-helpers
On Mon, Nov 17, 2014 at 09:22:39AM -0800, Russ Allbery wrote: Anthony Towns a...@erisian.com.au writes: BTW, it occured to me that it seems like a wart that update-rc.d doesn't respect policy-rc.d -- as it stands, policy-rc.d can prevent a service from (re)starting during install/upgrade, but it'll still start on the next boot. Is that just something that never got thought of / done, or does it actually make sense? Consider, for example, bootstrapping a new system in a local chroot that will then be deployed as a virtual image. You want policy-rc.d to prevent starting any daemons from the chroot while you're installing and configuring packages, but you still want all the service management links and policy installed as normal so that, after you turn this into a cloud image, everything will run properly. Thanks, that makes sense. I was thinking more along the lines of: - do the install with policy-rc.d overriding which services are active - once you change your policy (once you've finished bootstrapping), you change or remove policy-rc.d, and continue on your merry way But having update-rc.d obey policy-rc.d would stop that from working right; having /init/ obey policy-rc.d would work fine, but that's just crazy complicated. Followup question: does anyone actually use the detailed features of policy-rc.d or is always used in practice to turn all init scripts off? Cheers, aj -- 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/20141117183719.ga2...@master.debian.org
Technical committee acting in gross violation of the Debian constitution
Le samedi 15 novembre 2014 à 16:16 -0800, Don Armstrong a écrit : The technical committe was asked in #746578 to override the ordering of the alternative dependencies on systemd-sysv and systemd-shim to prefer the installation of systemd-shim in cases where sysvinit-core was already installed. This decision has been made in gross violation of constitution §6.3.6, being summoned to override a maintainer’s choice while the solution was still under discussion. I urge the systemd maintainers not to take it into account. -- .''`. 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/1416249514.4599.15.ca...@kagura.malsain.org
Re: Bug#769911: RFP: variety -- wallpaper changer
Control: reassign -1 wnpp Control: retitle -1 RFP: variety -- wallpaper changer On Lu, 17 nov 14, 16:02:30, Nenad Latinović wrote: Package: variety Version: variety Severity: wishlist Dear Maintainer, If it's possible, I'd like to suggest packaging this wallpaper changer for Debian. http://peterlevi.com/variety/ It currently isn't listed in the repositories. Kind regards, -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=sl_SI.utf8, LC_CTYPE=sl_SI.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: Pre-Depends: init-system-helpers
On Mon, 17 Nov 2014, Anthony Towns wrote: On Mon, Nov 17, 2014 at 09:22:39AM -0800, Russ Allbery wrote: Anthony Towns a...@erisian.com.au writes: BTW, it occured to me that it seems like a wart that update-rc.d doesn't respect policy-rc.d -- as it stands, policy-rc.d can prevent a service from (re)starting during install/upgrade, but it'll still start on the next boot. Is that just something that never got thought of / done, or does it actually make sense? Consider, for example, bootstrapping a new system in a local chroot that will then be deployed as a virtual image. You want policy-rc.d to prevent starting any daemons from the chroot while you're installing and configuring packages, but you still want all the service management links and policy installed as normal so that, after you turn this into a cloud image, everything will run properly. Thanks, that makes sense. I was thinking more along the lines of: - do the install with policy-rc.d overriding which services are active - once you change your policy (once you've finished bootstrapping), you change or remove policy-rc.d, and continue on your merry way But having update-rc.d obey policy-rc.d would stop that from working right; having /init/ obey policy-rc.d would work fine, but that's just crazy complicated. Followup question: does anyone actually use the detailed features of policy-rc.d or is always used in practice to turn all init scripts off? I think I heard of someone using them *once*. It is very rare, AFAIK. However, if there is one thing I learned the hard way, is that people who use the advanced features don't make themselves or that fact known unless you ask. They often don't show up even when you break things for them :-( -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- 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/20141117184905.gf24...@khazad-dum.debian.net
Re: Being part of a community and behaving
On 16/11/14 17:16, Scott Kitterman wrote: The cure for inappropriate speech is more speech. Calling people on things that are inappropriate or that cause problems in the project is exactly the right thing to do. I was trying to point out the futility of trying to ask people to show restraint, as calling a (subjectively) innocent joke offensive is every bit as offensive as the original joke. Refrain from stirring the fire by saying it's wrong is backwards. Over a decade ago I worked for a company I will not name. Suffice it to say it is a company producing firewalls. In the course of debugging one feature, I managed to create a RST storm. It is the same as an ACK storm[1], only with RST packets. The discussion here reminds me of those times. I am not telling anyone to shut up. Everyone are free to criticize whatever and wherever. I am merely suggesting that shutting up might be a smarter course of action. Of course, I'm sure there are those who will find my mail offensive, and will be most prudent in letting me, and everyone else, know about it. As such, I promise to henceforth accept my own advice. This is my last email on this thread. Shachar 1 - http://security.stackexchange.com/questions/49827/how-are-ack-storms-created-and-whats-a-good-mitigation-strategy-for-them
Re: Technical committee acting in gross violation of the Debian constitution
On Mon, 17 Nov 2014, Josselin Mouette wrote: Le samedi 15 novembre 2014 à 16:16 -0800, Don Armstrong a écrit : The technical committe was asked in #746578 to override the ordering of the alternative dependencies on systemd-sysv and systemd-shim to prefer the installation of systemd-shim in cases where sysvinit-core was already installed. This decision has been made in gross violation of constitution §6.3.6, being summoned to override a maintainer’s choice while the solution was still under discussion. §6.3.6 does not prevent the CTTE from being presented an issue early. It stops the CTTE from deciding an issue before a consensus approach has been attempted. In this particular case, I felt that a consensus approach had been attempted when this issue came up for a vote. This particular bug has been open since May, and was discussed at length. In retrospect, the CTTE may not be working consensus hard enough, and for that, I'm sorry. Working to achieve consensus is very difficult, time consuming, and fraught. It takes a huge time commitment, and even after spending the time, the CTTE may still have to make a decision. I had naïvely assumed that making what I thought were technically defensible decisions was good enough. Clearly, enough people in the project disagree, and want the CTTE to work harder on consensus first before deciding. I'm already working to rectify that in the case of #766708, and I'm certain we could use more help finding consensus with #750135, and maybe even #741573. If this is something you (or anyone else in the project) feels strongly about, please, work with the CTTE to help find consensus on these issues, so we don't actually have to decide. -- Don Armstrong http://www.donarmstrong.com Quite the contrary; they *love* collateral damage. If they can make you miserable enough, maybe you'll stop using email entirely. Once enough people do that, then there'll be no legitimate reason left for anyone to run an SMTP server, and the spam problem will be solved. -- Craig Dickson in 20020909231134.GA18917@linux700.localnet -- 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/20141117191508.gl4...@rzlab.ucr.edu
Re: Pre-Depends: init-system-helpers
Henrique de Moraes Holschuh h...@debian.org writes: I think I heard of someone using them *once*. It is very rare, AFAIK. However, if there is one thing I learned the hard way, is that people who use the advanced features don't make themselves or that fact known unless you ask. They often don't show up even when you break things for them :-( Back when we were arguing over the right way to disable an init script so that the state was preserved across package upgrades, I remember several people saying policy.d was the right way to disable a specific service. Presumably a few people were using it based on 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/874mtxy6l5@hope.eyrie.org
Bug#769907: general: non-sysvinit init systems are made of fail
On 17 November 2014 18:15, Thomas Goirand z...@debian.org wrote: On 11/17/2014 10:41 PM, Michal Suchanek wrote: To be a reasonable sysvinit replacement systemd and upstart must output messages to consoles(s) to which sysvinit did output messages, even on systems with multiple consoles (eg. serial, vga, kms). Not really... Or at least, not until last summer when I uploaded a patched version of bootlogd to Sid. To this date, sysv-rc can't log to multiple consoles, unless the release team agrees that I fix Wheezy (see the release.debian.org corresponding bug: #767202). Hello, I just tried in qemu after bootstrapping a fresh system in /tmp/zero. qemu-system-x86_64 -hda /tmp/zero -serial stdio -append root=UUID=f1e068b6-253f-4b8d-9a8c-9df9b671787f ro console=tty0 console=ttyS0,115200n8 -kernel /tmp/vmlinuz -initrd /tmp/initrd Indeed, both consoles are used to some extent with systemd. However, the serial console is way more verbose in this configuration. For one, I did not notice any disk check messages on the VGA console hence the black screen on system which has disks of non-trivial size. With current sysvinit the serial console is also used as main but sysvinit-core does not produce any messages on tty0 whatsoever and so does not mislead the user into thinking that useful boot progress feedback can be obtained on that terminal. systemd on the other hand prints selected messages on both terminals but most messages go only to the main serial terminal. For completeness I tried upstart and it produces two error messages on both terminals and 6 progress messages on serial terminal never giving a login prompt on either. This is unexpected as it used to work on wheezy. Thanks Michal -- 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/CAOMqctTaNkcWmzj0ueZjOuEmMCqdkoCHyHskf=heh0d9o00...@mail.gmail.com
Re: Technical committee acting in gross violation of the Debian constitution
First, Don, I’d like to thank you for keeping the discussion civil. I have made a serious accusation, and I don’t want it to be an excuse for a mudfight. Le lundi 17 novembre 2014 à 11:15 -0800, Don Armstrong a écrit : §6.3.6 does not prevent the CTTE from being presented an issue early. It stops the CTTE from deciding an issue before a consensus approach has been attempted. In this particular case, I felt that a consensus approach had been attempted when this issue came up for a vote. This particular bug has been open since May, and was discussed at length. There have been discussions, specifically on the debian-ctte mailing lists, about upgrading to systemd only if the system is not at risk of breaking sysadmin changes (inittab, custom init scripts). It strikes me that this possibility has not even been included in the call for votes for this bug. In retrospect, the CTTE may not be working consensus hard enough, and for that, I'm sorry. Working to achieve consensus is very difficult, time consuming, and fraught. It takes a huge time commitment, and even after spending the time, the CTTE may still have to make a decision. I don’t think it is wrong to want to have a decision at some point, if the attempts at consensus have failed. Keeping issues in the open for months, even years, is not going to magically solve them. It’s not because the resolution is wrong, either. Of course, my opinion is that it is wrong, and that it is going to rain fire on us when upgraded systems do not behave like freshly installed ones. But the point of making decisions is that sometimes they are wrong, and we should be able to deal with whatever fixing is required later. The problem here is that the CTTE gives the feeling of having been played. The same person escalated the problem to the CTTE, framed it into a fake dichotomy, proposed a resolution that ignored the ongoing discussions and alternative proposals, and rushed a vote. Maybe this feeling is unfounded. Maybe all members of the CTTE genuinely believe that there were no other acceptable proposal, after carefully examining the issue and the consequences of all scenarios. If this is the case, we might have a serious communication problem. Because either way, we have a problem of trust that #746578 is not going to improve. I had naïvely assumed that making what I thought were technically defensible decisions was good enough. Clearly, enough people in the project disagree, and want the CTTE to work harder on consensus first before deciding. I don’t think it has to be the CTTE’s role to build consensus from nothing. But when genuine attempts are being made, constitution §6.3.6 should be honored. I'm already working to rectify that in the case of #766708, and I'm certain we could use more help finding consensus with #750135, and maybe even #741573. If this is something you (or anyone else in the project) feels strongly about, please, work with the CTTE to help find consensus on these issues, so we don't actually have to decide. #741573 is a clear-cut case where consensus has been achieved and a single maintainer is deliberately acting against it. After that, what should have been an obvious CTTE decision has been derailed into a lengthy debate on the philosophy of menu systems. When a trivial request takes so much time to decide on, and a complex one is rushed into a hasty resolution, well, maybe that explains the trust issue I was talking about. Cheers, -- .''`. 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/1416255656.6444.34.ca...@kagura.malsain.org
Re: Technical committee acting in gross violation of the Debian constitution
Le lundi 17 novembre 2014 à 21:20 +0100, Josselin Mouette a écrit : It’s not because the resolution is wrong, either. Of course, my opinion is that it is wrong, and that it is going to rain fire on us when upgraded systems do not behave like freshly installed ones. Ansgar pointed to me on IRC that there is another dependency chain taking care of upgrades, making the “raining fire” comment an obvious overstatement. -- .''`. 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/1416257119.6444.41.ca...@kagura.malsain.org
Re: Technical committee acting in gross violation of the Debian constitution
Hi, Le lundi 17 novembre 2014 à 11:15 -0800, Don Armstrong a écrit : §6.3.6 does not prevent the CTTE from being presented an issue early. It stops the CTTE from deciding an issue before a consensus approach has been attempted. In this particular case, I felt that a consensus approach had been attempted when this issue came up for a vote. This particular bug has been open since May, and was discussed at length. There have been discussions, specifically on the debian-ctte mailing lists, about upgrading to systemd only if the system is not at risk of breaking sysadmin changes (inittab, custom init scripts). I do not see why this issue even had to be discussed. It looks obvious to me that a package should avoid changing or breakign anything outside it if it is not necessary. The CTTE's decision therefore is the only reasonable one, and I wonder why realising this needed the CTTE. That said, good job, technical committee, for saving users from touching a running system :)! Cheers, Nik signature.asc Description: OpenPGP digital signature
Re: Technical committee acting in gross violation of the Debian constitution
On Mon, Nov 17, 2014 at 09:20:56PM +0100, Josselin Mouette wrote: In retrospect, the CTTE may not be working consensus hard enough, and for that, I'm sorry. Working to achieve consensus is very difficult, time consuming, and fraught. It takes a huge time commitment, and even after spending the time, the CTTE may still have to make a decision. I don’t think it is wrong to want to have a decision at some point, if the attempts at consensus have failed. Keeping issues in the open for months, even years, is not going to magically solve them. It’s not because the resolution is wrong, either. Of course, my opinion is that it is wrong, and that it is going to rain fire on us when upgraded systems do not behave like freshly installed ones. How do you arrive at the conclusion that this in any way causes upgraded systems to be have differently from freshly-installed ones? The only thing this dependency swap affects is whether installing a DE on top of an existing system which has deliberately opted for a non-default init causes a different init to be chosen. This is not about the choice of init for upgraded systems, /at all/. -- 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: Technical committee acting in gross violation of the Debian constitution
On Monday, 17 de November de 2014 20:20:56 Josselin Mouette escribió: First, Don, I’d like to thank you for keeping the discussion civil. I have made a serious accusation, and I don’t want it to be an excuse for a mudfight. The point is not that you have made a serious accusation. It is your right to do so, if you feel something is wrong. I would even say that it is your duty. The point is that you requested (you 'urged') maintainers to ignore a CTTE decision that has not been overturned. This is not being civil. I strongly support the CTTE decision of systemd being our default, as well as this one. In fact, any CTTE decision. And if I someday find that a specific CTTE decision is wrong, I'll work to overturn it, either by providing further evidence or by convincing somebody of some aspect that they may not have seen. But not by requesting maintainers ignore a decision. I have had a hard moment while writing this, because what I really wanted to write was in a very different mood, but I do not want (another) mudfight. Keep Debian civil. Do what the CTTE has ruled, and if you feel it is wrong, raise the case again, or try to overturn the CTTE decision by the correct means. Have you tried to grab the Secretary's opinion about if the Constitution has really been ignored? I think it has not been, and you think it has, and we can agree that we disagree, but The Right Thing here is not what you did. Regards er Envite signature.asc Description: This is a digitally signed message part.
Re: Technical committee acting in gross violation of the Debian constitution
Hi Josselin, On Mon, Nov 17, 2014 at 07:38:34PM +0100, Josselin Mouette wrote: Le samedi 15 novembre 2014 à 16:16 -0800, Don Armstrong a écrit : The technical committe was asked in #746578 to override the ordering of the alternative dependencies on systemd-sysv and systemd-shim to prefer the installation of systemd-shim in cases where sysvinit-core was already installed. This decision has been made in gross violation of constitution §6.3.6, being summoned to override a maintainer’s choice while the solution was still under discussion. I urge the systemd maintainers not to take it into account. This list is for technical discussions of the Debian distribution, your mail is off-topic here. If you have issues with the technical committe and/or want to reach the systemd maintainers, let me know off-list and I can provide you with contact details. Cheers, Michael -- 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/20141117220157.ge30...@raptor.chemicalconnection.dyndns.org
Re: Pre-Depends: init-system-helpers
On Mon, 17 Nov 2014, Russ Allbery wrote: Henrique de Moraes Holschuh h...@debian.org writes: I think I heard of someone using them *once*. It is very rare, AFAIK. However, if there is one thing I learned the hard way, is that people who use the advanced features don't make themselves or that fact known unless you ask. They often don't show up even when you break things for them :-( Back when we were arguing over the right way to disable an init script so that the state was preserved across package upgrades, I remember several people saying policy.d was the right way to disable a specific service. Presumably a few people were using it based on that. Yes... that's probably where I heard about some more advanced uses of policy-rc.d other than the usual one-liner exit 101 for use inside chroots :-) -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- 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/20141117230342.ga2...@khazad-dum.debian.net
New pre-depends: python pre-depends python-minimal
It appears that the appropriate resolution of #769106 [1] is to add a new pre-depends on python-minimal in python. This issue at hand is that at the time python2.7-minimal is configured, python is unpacked, but python-minimal is not. Since python-2.7-minimal doesn't have a direct depends on python-minimal, this is allowable (policy 7.2, Depends). In order for python2.7-minimal to configure, python-minimal needs to be at least unpacked to provide /usr/bin/pycompile. The only way for python to ensure this is the case is to declare a pre-depends relation (also policy 7.2). Since nothing outside python-defaults should depend on python-minimal this should have a minimal impact on upgrade ordering or dependency resolution complexity. One might argue that the python/python-minimal split is obsolete and ought to be dropped, but I think that's a discussion to have (if at all) for Stretch. Adding the pre-depends is the least invasive solution to this RC bug. Comments/concurrence/etc? Scott K [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769106 -- 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/2336109.MRqKsDn39K@kitterman-optiplex-9020m
Re: Being part of a community and behaving
On Mon, Nov 17, 2014 at 10:21:13AM +0100, Marco d'Itri wrote: On Nov 17, Steve Langasek vor...@debian.org wrote: This is what many still (retorically) wonder about: we the systemd maintainers did not reject that change, https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;bug=746578 Please try to be less selective in your quoting: the issue was still being discussed. May I gently suggest that tagging a bug wontfix has the unfortunate tendency to perpetuate the perception that the systemd proponents don't really care about any fallout that systemd might cause on the rest of Debian --- ESPECIALLY if it's still open for discussion? Especially without any discussion or explanation by any other systemd maintainer? It may not be accurate, but right now, given the feeling of hurt on all sides of the issue, a bit more communication instead of a blunt tags + wontfix without any word of explanation might have contributed to a more productive amount of discussion. Best regards, - Ted -- 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/20141117232416.ga8...@thunk.org
Re: RFC: DEP-14: Recommended layout for Git packaging repositories
On 17/11/14 16:24, Ian Jackson wrote: I don't think this problem, of a mass of different branch structures, is going to go away any time soon. Simply because people don't seem able to agree. My answer is to create a parallel universe in which the branch structure is known. As far as I can see, in effect, Kali's answer can be described by the same sentence, except that Kali's parallel universe doesn't have the same known branch structure you do, presumably because Raphael's preferences are different; Kali's known branch structure is what git-import-dsc does whereas yours is based on what dpkg-source -x produces, resulting in different trees in the repository for 3.0 (quilt) packages. As far as I can see from what you've said elsewhere, for source format 3.0 (quilt), you're aiming for the patches applied and also serialized in debian/patches/ state (matching git-dpm I think?), whereas Kali ends up with the patches serialized in debian/patches/ but not applied state (matching gbp-pq). Is that a fair characterization? Is your current work-in-progress on teaching dgit better 3.0 (quilt) handling available anywhere? I'd be interested in trying out the new way while comparing the same package in different repository layouts. 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/546a871e.80...@debian.org
Re: Being part of a community and behaving
Hi, First of all, sorry in advance if the beginning of this post looks more like a bug report discussion than a debian-devel post. try this instead: $ journalctl _SYSTEMD_UNIT=systemd-journald.service which will (most likely) also show messages like Suppressed 1927 messages from /PATH/FOO.slice. You can then use $ journalctl _SYSTEMD_SLICE=FOO.slice to display the non-suppressed part of the spew that's responsible for this overrun. (intentional disabling of word-wrapping just for the few lines of logs) raph@arche:~$ journalctl _SYSTEMD_UNIT=systemd-journald.service -- Logs begin at lun. 2014-11-10 20:14:11 CET, end at lun. 2014-11-17 23:31:22 CET. -- nov. 10 20:14:11 arche systemd-journal[207]: Runtime journal is using 8.0M (max allowed 79.2M, trying to leave 118.8M free of 784.0M available → current limit 79.2M). nov. 10 20:14:11 arche systemd-journal[207]: Runtime journal is using 8.0M (max allowed 79.2M, trying to leave 118.8M free of 784.0M available → current limit 79.2M). nov. 10 20:14:11 arche systemd-journal[207]: Journal started nov. 10 20:14:19 arche systemd-journal[207]: Runtime journal is using 8.0M (max allowed 79.2M, trying to leave 118.8M free of 783.3M available → current limit 79.2M). nov. 10 20:14:34 arche systemd-journal[207]: Forwarding to syslog missed 42 messages. nov. 14 01:02:44 arche systemd-journal[207]: Forwarding to syslog missed 1 messages. nov. 14 01:25:31 arche systemd-journal[207]: Forwarding to syslog missed 2 messages. nov. 14 01:26:36 arche systemd-journal[207]: Forwarding to syslog missed 2 messages. nov. 15 18:22:24 arche systemd-journal[207]: Forwarding to syslog missed 9 messages. nov. 15 18:22:54 arche systemd-journal[207]: Forwarding to syslog missed 3 messages. nov. 16 22:27:37 arche systemd-journal[207]: Forwarding to syslog missed 1 messages. nov. 16 22:28:13 arche systemd-journal[207]: Forwarding to syslog missed 1 messages. nov. 17 15:13:45 arche systemd-journal[207]: Forwarding to syslog missed 18 messages. As you can see, no syslog-filler slice to investigate in particular. I'm quite happy though, because after you and Ben emitted the idea that I may have ran with messed up logs long before I upgraded to systemd, I was quite worried, even if it's a sid desktop that I moderately care about (after all, if that's the case, it could happen on my production servers as well); but the small number of missed messages (less than 50, very different from the thousands you suspected) make me think that my logs on this machine are a lot less likely to have been crippled for a long time without my knowledge than both of you initially thought, aren't they ? drop the message (IIRC it was even more condescending, like we don't have to wait for this or something). Really ? The very piece of code which is supposed to talk to syslog... doesn't wait for syslog ? Do you want to buffer an unbounded number of messages in RAM instead, hoping that syslog will catch up eventually? Thanks, but no thanks. (Implementing a _bounded_ message buffer in systemd doesn't make sense, because you can get the exact same effect by simply doing (a), above.) Now for the interesting part (for debian-devel, anyway :) ). Maybe as a sysadmin I lack some C arcane knowledge and it may sound like a silly question to you, but why would that be such a bad idea ? Rsyslog (debian default since lenny) does this; if it's configured to send messages to a remote server via TCP, and if the server is unreachable for whatever reason, it stores the messages in a buffer until they can be sent; it even stores them to the disk if the case it's terminated. Why journald using some more KB or MB of RAM to store the messages it couldn't forward in time, and waiting for syslog to catch up, would be such a bad thing to do ? It's likely (though not certain) that your logs have been crippled in the past, albeit in a different way, and you simply didn't notice because the logging program didn't tell you. The standard syslog(3) code doesn't. Like I said, it doesn't look that way (at least I hope it doesn't) but correct me if I'm wrong. Regards, -- Raphaël Halimi signature.asc Description: OpenPGP digital signature
Re: Technical committee acting in gross violation of the Debian constitution
This decision has been made in gross violation of constitution §6.3.6, being summoned to override a maintainer’s choice while the solution was still under discussion. I urge the systemd maintainers not to take it into account. I fully agree. This whole vote has been a farce and the result should not be adopted. We haven't even waited for the results of the GR. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- 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/546a8809.6070...@physik.fu-berlin.de
Bug#769907: general: non-sysvinit init systems are made of fail
On 11/18/2014 03:50 AM, Michal Suchanek wrote: With current sysvinit the serial console is also used as main but sysvinit-core does not produce any messages on tty0 whatsoever and so does not mislead the user into thinking that useful boot progress feedback can be obtained on that terminal. This is because bootlogd only supports a single output at a time, and therefore only outputs on the *last* occurrence of the console= boot parameter. The patch that I pointed to resolves this by adding support for outputting to multiple consoles. If you want it for Wheezy, I have it here (as I use it for my unofficial OpenStack backport repo, it's in that repository): http://archive.gplhost.com/debian/pool/juno-backports/main/s/sysvinit/ On 11/18/2014 03:50 AM, Michal Suchanek wrote: systemd on the other hand prints selected messages on both terminals but most messages go only to the main serial terminal. Yet another WTF, and probably if you ask upstream, they'll find a good reason for that, and will tag +wontfix if you submit a bug... I'd be curious to know what's the (twisted) reasoning behind. Maybe because upstream considers that ttyS0 is for debugging, which IMO is wrong (it should be considered as a normal console, just like tty0, and debug messages should also be printed to tty0 anyway). BTW, it's good to know that we have a way to debug things with systemd, thanks for the tip! :) On 11/18/2014 03:50 AM, Michal Suchanek wrote: For completeness I tried upstart and it produces two error messages on both terminals and 6 progress messages on serial terminal never giving a login prompt on either. This is unexpected as it used to work on wheezy. I would strongly suggest that you file bugs against both systemd and upstart then! (and *not* using the general pseudo-package...) Cheers, Thomas Goirand (zigo) -- 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/546a8a4e.8010...@debian.org
Re: Technical committee acting in gross violation of the Debian constitution
On Tue, 2014-11-18 at 00:43 +0100, John Paul Adrian Glaubitz wrote: This decision has been made in gross violation of constitution §6.3.6, being summoned to override a maintainer’s choice while the solution was still under discussion. I urge the systemd maintainers not to take it into account. I fully agree. This whole vote has been a farce and the result should not be adopted. Just had to wonder... what happens to DDs who intentionally and clearly break the constitution or who publicly state to no longer feel bound by it? Cheers. smime.p7s Description: S/MIME cryptographic signature
Re: Technical committee acting in gross violation of the Debian constitution
Hi Christoph, On Tue, Nov 18, 2014 at 01:24:13AM +0100, Christoph Anton Mitterer wrote: Just had to wonder... what happens to DDs who intentionally and clearly break the constitution or who publicly state to no longer feel bound by it? This mailing list is a technical list and your message/question is off-topic. Kindly reask it on another list, or another forum altogether. Michael -- 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/20141118002654.gg30...@raptor.chemicalconnection.dyndns.org
Re: Technical committee acting in gross violation of the Debian constitution
On Tue, 2014-11-18 at 01:26 +0100, Michael Banck wrote: This mailing list is a technical list and your message/question is off-topic. Kindly reask it on another list, or another forum altogether. I wouldn't say that the two posts I was particularly replying to were in any way more technical. Or is publicly asking to break the constitution is more technical than asking what happens if someone intentionally does so? Plus, d-d is described as Development of Debian, not as technical only development of debian) and it seems to be pretty common to have lengthy political discussions here. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Re: RFC: DEP-14: Recommended layout for Git packaging repositories
Simon McVittie writes (Re: RFC: DEP-14: Recommended layout for Git packaging repositories): As far as I can see from what you've said elsewhere, for source format 3.0 (quilt), you're aiming for the patches applied and also serialized in debian/patches/ state (matching git-dpm I think?), whereas Kali ends up with the patches serialized in debian/patches/ but not applied state (matching gbp-pq). That is a correct characterisation of dgit's view of history. But dgit will also cope with some patches applied and also serialised but some further commits made to git but not serialised in debian/patches. Is your current work-in-progress on teaching dgit better 3.0 (quilt) handling available anywhere? I'd be interested in trying out the new way while comparing the same package in different repository layouts. http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=dgit.git;a=shortlog;h=refs/heads/wip.rebasing aka git://git.chiark.greenend.org.uk/~ianmdlvl/dgit.git#wip.rebasing But DO NOT USE THAT VERSION TO UPLOAD. It generates git trees that existing dgits cannot cope with. Thanks, Ian. -- 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/21610.38337.477993.49...@chiark.greenend.org.uk
Bug#769979: ITP: r-cran-rneos -- GNU R package with XML-RPC interface to NEOS
Package: wnpp Owner: Dirk Eddelbuettel e...@debian.org Severity: wishlist * Package name: r-cran-rneos Version : 0.2-7-1 Upstream Author : Bernhard Pfaff * URL or Web page : http://cran.r-project.org/web/packages/rneos/index.html * License : GPL (= 2) Description : GNU R package with XML-RPC interface to NEOS This is a very small package -- which is now a (Build-)Depends of the r-cran-fportfolio package which has been in Debian for many years. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@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/8761ednx9k@max.nulle.part
Re: Pre-Depends: init-system-helpers
Henrique de Moraes Holschuh wrote: Anthony Towns wrote: Russ Allbery wrote: Anthony Towns writes: BTW, it occured to me that it seems like a wart that update-rc.d doesn't respect policy-rc.d -- as it stands, policy-rc.d can prevent a service from (re)starting during install/upgrade, but it'll still start on the next boot. Is that just something that never got thought of / done, or does it actually make sense? Initially that caught me offguard. I had disabled a service using policy-rc.d but it still started on the next boot. Discussion with parties involved exposed me to the fact of implementation that policy-rc.d is observed only by invoke-rc.d which was designed for use within package postinst et al scripts. (Although anything that exists will be used outside of the original context and therefore there are people using invoke-rc.d instead of service.) It feels strange to me that policy-rc.d only prevents starting from within package actions but not otherwise. Here it is said update-rc.d does not respect policy-rc.d but I think maybe that should have been invoke-rc.d since update-rc.d just sets things up to start while it is invoke-rc.d that actually does it. Consider, for example, bootstrapping a new system in a local chroot that will then be deployed as a virtual image. You want policy-rc.d to prevent starting any daemons from the chroot while you're installing and configuring packages, but you still want all the service management links and policy installed as normal so that, after you turn this into a cloud image, everything will run properly. Thanks, that makes sense. For me it feels strange to leave policy-rc.d in place for a real boot. Wouldn't it be better to remove the policy-rc.d when converting it from a chroot to a full booting system? Otherwise one boots and policy-rc.d is ignored. Everything starts. But then upgrades later and nothing is (re)started? That doesn't feel good. I think it would need to be removed for correct continuing operation. (And if so then it would be fine to respect it during boot too.) I was thinking more along the lines of: - do the install with policy-rc.d overriding which services are active - once you change your policy (once you've finished bootstrapping), you change or remove policy-rc.d, and continue on your merry way But having update-rc.d obey policy-rc.d would stop that from working right; having /init/ obey policy-rc.d would work fine, but that's just crazy complicated. Followup question: does anyone actually use the detailed features of policy-rc.d or is always used in practice to turn all init scripts off? I think I heard of someone using them *once*. It is very rare, AFAIK. Is there any other way to do it? I am not aware of any other way. If that is the only way then it must be in use by everyone who needs it. Maybe I am missing a better alternative? However, if there is one thing I learned the hard way, is that people who use the advanced features don't make themselves or that fact known unless you ask. They often don't show up even when you break things for them :-( (Chuckle!) Agreed. But here I am showing up to be one of those unrepresented people! Here is an actual live production policy-rc.d from a system where the web server is being run inside of a chroot. I think the intention is obvious. Is there any other way to accomplish this other than using the policy-rc.d? Trying to manage the startup with update-rc.d doesn't work until after a package is installed. Bob #!/bin/sh # See /usr/share/doc/sysv-rc/README.policy-rc.d.gz for documentation. while [ $# -gt 0 ]; do case $1 in --list) exit 101 ;; --quiet) shift ;; -*) shift ;; apache2) exit 0 ;; cron) exit 0 ;; nullmailer) exit 0 ;; *) break ;; esac done exit 101 signature.asc Description: Digital signature
Re: Being part of a community and behaving
On Mon, Nov 17, 2014 at 02:48:29PM +, Anthony Towns wrote: On Mon, Nov 17, 2014 at 11:05:13AM +0100, Bj??rn Mork wrote: m...@linux.it (Marco d'Itri) writes: On Nov 17, Steve Langasek vor...@debian.org wrote: This is what many still (retorically) wonder about: we the systemd maintainers did not reject that change, https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;bug=746578 Please try to be less selective in your quoting: the issue was still being discussed. I see. So any systemd bug with a 'wontfix' tag is still considered open for discussion? That's good to know. Thanks. Isn't any (open) bug tagged wontfix still open for discussion? If you've got new information, or a new approach that the maintainer might prefer, you can post it to the bug and discuss it with the maintainer... It appears to be a misnomer then. I read 'wontfix' as I'm not going to to fix it as I don't see it as a bug. Or am I confusing an open wontfix with a closed wontfix? -- 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/20141118034838.GD7745@tal
Re: Technical committee acting in gross violation of the Debian constitution
On Tue, Nov 18, 2014 at 01:24:13AM +0100, Christoph Anton Mitterer wrote: This decision has been made in gross violation of constitution §6.3.6, being summoned to override a maintainer’s choice while the solution was still under discussion. I urge the systemd maintainers not to take it into account. I fully agree. This whole vote has been a farce and the result should not be adopted. Just had to wonder... what happens to DDs who intentionally and clearly break the constitution or who publicly state to no longer feel bound by it? An email to DAM who is a DPL delegate with powers to expel people from the project. -- WBR, wRAR signature.asc Description: Digital signature
Re: Pre-Depends: init-system-helpers
Bob Proulx b...@proulx.com writes: Henrique de Moraes Holschuh wrote: Anthony Towns wrote: Followup question: does anyone actually use the detailed features of policy-rc.d or is always used in practice to turn all init scripts off? I think I heard of someone using them *once*. It is very rare, AFAIK. Is there any other way to do it? I am not aware of any other way. If that is the only way then it must be in use by everyone who needs it. Maybe I am missing a better alternative? update-rc.d service disable -- 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/87a93pw1c4@hope.eyrie.org
Re: Being part of a community and behaving
Chris Bannister cbannis...@slingshot.co.nz writes: It appears to be a misnomer then. I read 'wontfix' as I'm not going to to fix it as I don't see it as a bug. Or am I confusing an open wontfix with a closed wontfix? Yeah, this is confusing as heck, and to make it worse, every Debian maintainer has their own system. We don't have standardized detailed tag meanings. Personally (and this is also the pattern followed by Lintian and Policy maintainers), I tag bugs wontfix but don't close them while I'm still open to further discussion to change my mind. Then, I frequently forget to remove the wontfix tag even after I've changed my mind. :/ Closed is another matter entirely -- that means I'm pretty sure the bug report should just go away. -- 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/8761edw17j@hope.eyrie.org
Re: Being part of a community and behaving
Chris Bannister cbannis...@slingshot.co.nz writes: [the ‘wontfix’ tag] appears to be a misnomer then. I read 'wontfix' as I'm not going to to fix it as I don't see it as a bug. The official definition: wontfix This bug won't be fixed. Possibly because this is a choice between two arbitrary ways of doing things and the maintainer and submitter prefer different ways of doing things, possibly because changing the behaviour will cause other, worse, problems for others, or possibly for other reasons. URL:https://www.debian.org/Bugs/Developer#tags leaves open the question of whether the maintainer considers the reported behaviour a bug. There is no necessary implication to that effect. -- \ “I got an answering machine for my phone. Now when someone | `\ calls me up and I'm not home, they get a recording of a busy | _o__) signal.” —Steven Wright | Ben Finney -- 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/854mtx2jaq@benfinney.id.au
Bug#769997: ITP: 4ti2 -- algebraic, geometric and combinatorial problems on linear spaces
Package: wnpp Severity: wishlist Owner: Jerome Benoit calcu...@rezozer.net * Package name: 4ti2 Version : 1.6.2 Upstream Author : 4ti2 team * URL : http://www.4ti2.de/ * License : GPL-2+ Programming Lang: C, C++, swig Description : algebraic, geometric and combinatorial problems on linear spaces A mathematical software package for algebraic, geometric and combinatorial problems on linear spaces. -- 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/20141118050143.10045.19487.report...@nen.dnsalias.org
Re: Bug#769747: Technical committee acting in gross violation of the Debian constitution
Hello all, Josselin Mouette [2014-11-17 19:38 +0100]: This decision has been made in gross violation of constitution §6.3.6, being summoned to override a maintainer’s choice while the solution was still under discussion. I urge the systemd maintainers not to take it into account. TBH, I think this was blown way out of proportion. I already switched the dependencies around yesterday in git. It's a rather harmless change after all -- a no-op for any existing system, regardless of whether they have systemd-sysv or sysvinit installed. And on upgrades, libpam-systemd is *not* meant to be the package that decides which init system you end up with IMHO -- that should be the job of a meta-package like init or other means (and there's still a pending discussion whether and how to upgrade existing wheezy machines to systemd). If other systemd maintainers want to keep discussing this dependency issue, please do (but it seems we are just losing them in dangerous quantities!), but I see absolutely no point in this personally. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.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/20141118052952.gb3...@piware.de
Re: New pre-depends: python pre-depends python-minimal
On Mon, Nov 17, 2014 at 18:24:00 -0500, Scott Kitterman wrote: It appears that the appropriate resolution of #769106 [1] is to add a new pre-depends on python-minimal in python. This issue at hand is that at the time python2.7-minimal is configured, python is unpacked, but python-minimal is not. Since python-2.7-minimal doesn't have a direct depends on python-minimal, this is allowable (policy 7.2, Depends). In order for python2.7-minimal to configure, python-minimal needs to be at least unpacked to provide /usr/bin/pycompile. The only way for python to ensure this is the case is to declare a pre-depends relation (also policy 7.2). Can you explain why/how the python package enters into the picture here at all? Cheers, Julien signature.asc Description: Digital signature
Re: Bug#769747: Technical committee acting in gross violation of the Debian constitution
On Tue, 2014-11-18 at 06:29 +0100, Martin Pitt wrote: Hello all, Josselin Mouette [2014-11-17 19:38 +0100]: This decision has been made in gross violation of constitution §6.3.6, being summoned to override a maintainer’s choice while the solution was still under discussion. I urge the systemd maintainers not to take it into account. TBH, I think this was blown way out of proportion. I already switched the dependencies around yesterday in git. It's a rather harmless change after all -- a no-op for any existing system, regardless of whether they have systemd-sysv or sysvinit installed. And on upgrades, libpam-systemd is *not* meant to be the package that decides which init system you end up with IMHO -- that should be the job of a meta-package like init or other means (and there's still a pending discussion whether and how to upgrade existing wheezy machines to systemd). If other systemd maintainers want to keep discussing this dependency issue, please do (but it seems we are just losing them in dangerous quantities!), but I see absolutely no point in this personally. Yeah, the switch is entirely fine, thanks for doing the change. At worst it's inelegant to have to do this in order to trick the dependency systems into doing the right thing, maybe we manage to find a nicer solution for jessie+1. However I don't really the path that lead to the vote and the overruling (as i really don't think such drastic measures were needed), but that's a completely different discussion that clearly needs to be held seperately from discussing any specific technial outcome including this one. -- Sjoerd Simons sjo...@luon.net -- 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/1416295681.2480.3.ca...@luon.net
Re: New pre-depends: python pre-depends python-minimal
On Tuesday, November 18, 2014 08:28:29 AM Julien Cristau wrote: On Mon, Nov 17, 2014 at 18:24:00 -0500, Scott Kitterman wrote: It appears that the appropriate resolution of #769106 [1] is to add a new pre-depends on python-minimal in python. This issue at hand is that at the time python2.7-minimal is configured, python is unpacked, but python-minimal is not. Since python-2.7-minimal doesn't have a direct depends on python-minimal, this is allowable (policy 7.2, Depends). In order for python2.7-minimal to configure, python-minimal needs to be at least unpacked to provide /usr/bin/pycompile. The only way for python to ensure this is the case is to declare a pre-depends relation (also policy 7.2). Can you explain why/how the python package enters into the picture here at all? texlive-music grew a depends on python between wheezy and jessie, so in the upgrade test that led to the the bug it was being freshly installed (test being done in a minimal chroot. python depends (among other things) python2.7 and python-minimal. python- minimal then depends on python2.7-minimal. As part of python2.7-minimal's configuration, /usr/share/python/runtime.d/public_modules.rtinstall gets executed. It's part of the python package. Since the dependency chain was texlive-music - python - python2.7-minimal, python is already unpacked, so the script is available. The tricky part is that /usr/share/python/runtime.d/public_modules.rtinstall needs /usr/bin/pycompile in order to work. That's in (you guessed it) python- minimal. It's not available (and there's nothing in policy that says it has to be). Eventually, python-minimal will get unpacked, but it hadn't yet in this test run. Does that clarify it? Scott K signature.asc Description: This is a digitally signed message part.
Accepted mlterm 3.4.0-1 (source) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 02 Nov 2014 10:59:27 +0200 Source: mlterm Binary: mlterm mlterm-tiny mlterm-common mlterm-tools mlterm-im-uim mlterm-im-scim mlterm-im-m17nlib mlterm-im-ibus mlterm-im-fcitx Architecture: source Version: 3.4.0-1 Distribution: experimental Urgency: medium Maintainer: Kenshi Muto km...@debian.org Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) aelmahmo...@users.sourceforge.net Description: mlterm - MultiLingual TERMinal mlterm-common - MultiLingual TERMinal, common files mlterm-im-fcitx - MultiLingual TERMinal, Flexible Input Method plugin mlterm-im-ibus - MultiLingual TERMinal, IBus input method plugin mlterm-im-m17nlib - MultiLingual TERMinal, m17nlib input method plugin mlterm-im-scim - MultiLingual TERMinal, scim input method plugin mlterm-im-uim - MultiLingual TERMinal, uim input method plugin mlterm-tiny - MultiLingual TERMinal, tiny version mlterm-tools - MultiLingual TERMinal, additional tools Changes: mlterm (3.4.0-1) experimental; urgency=medium . * New upstream release. * debian/gbp.conf: added git-buildpackage configuration to set debian branch to experimental. * Remove fix_rect_slct_always_on.diff patch that is applied in new upstream. * Update symbols file Checksums-Sha1: 4b91abc8fdab6f1cfbf8721c19e8fc90f3a92601 2288 mlterm_3.4.0-1.dsc b30a1fdbdac1acbb3409218038d05d3d1c7bbb81 3630918 mlterm_3.4.0.orig.tar.gz 827affe9801c3e10070d97a6866b3778567e0116 22548 mlterm_3.4.0-1.debian.tar.xz Checksums-Sha256: 11d956ac8fffcf23fce344f7f4a272569555a497970c495f09c7c62f868a9c75 2288 mlterm_3.4.0-1.dsc 15b0060f028e15c0219e8d092353abc7186421ebb27d5677ba372a940040365b 3630918 mlterm_3.4.0.orig.tar.gz 2524930577bcbc08b2ff3189174633c45f1eac5a3cbc0f520a41446b71119851 22548 mlterm_3.4.0-1.debian.tar.xz Files: c892a8938fa86a3221eb2d8a9c72d900 2288 x11 optional mlterm_3.4.0-1.dsc fc9ac7e6032692fb2b7de1bdcb99e670 3630918 x11 optional mlterm_3.4.0.orig.tar.gz f7514e283e4cfb7225c83930104aeea0 22548 x11 optional mlterm_3.4.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUabO1AAoJELwZapTt3aG3yK8IAKAZ3aO49xXyZ+pWkzS4XJb7 az8+ZvL0Ni/SAkB+IyKw11edzXtJGKMs35h9vdjEdCisaZBsX/fUQso7cAY1fiYG JU9vZ5myzj0X+znZEqYjT/LBggKmTlE75WKx37qp5DZ/+ljf7JwOTmw4NrwTLYP1 2uAjyGqqKRBfCt0KmZgubWohZaG14x+Xxd3jym3ltj01wcpOc268fISu6fLt96sL t3BAnwmEYwzhZ6SbDPcY6qaTbBTDz/3Q9ULMqTg7sUelxH6CX65l+XUx9azxTsf1 I7Zv5054sDLriXviqpIEN2z4/eXSXwHWzC1z8eJIYrcF5v42MIF0WKmeGNu1ZCc= =uqwx -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/e1xqiuk-0004iv...@franck.debian.org
Accepted redmine-plugin-pretend 0.0.2+git20130821-3 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 17 Nov 2014 18:53:43 +1100 Source: redmine-plugin-pretend Binary: redmine-plugin-pretend Architecture: source all Version: 0.0.2+git20130821-3 Distribution: unstable Urgency: medium Maintainer: Dmitry Smirnov only...@debian.org Changed-By: Dmitry Smirnov only...@debian.org Description: redmine-plugin-pretend - Redmine plugin to allow admins to log-in as users Changes: redmine-plugin-pretend (0.0.2+git20130821-3) unstable; urgency=medium . * no_route_match.patch updated as per upstream commit. Checksums-Sha1: c66b398ba79b1e0ee8dd7c0c4381974744b9f82b 2067 redmine-plugin-pretend_0.0.2+git20130821-3.dsc 827a6d812a309978e236963f0dd8e7c684c7b0f7 4136 redmine-plugin-pretend_0.0.2+git20130821-3.debian.tar.xz ee61a7467c153328d9d379793494a1535815799c 5816 redmine-plugin-pretend_0.0.2+git20130821-3_all.deb Checksums-Sha256: f426c2cbb5f803e27a1ea7f0788f4df5f98528ee2a26a389a5afb79ba0bc5e88 2067 redmine-plugin-pretend_0.0.2+git20130821-3.dsc 04e4f6ae72e91a71dee36dbddb04bb9247d67c9a32e697c4f96dbd4c1b6a5dfb 4136 redmine-plugin-pretend_0.0.2+git20130821-3.debian.tar.xz 6815a5193f60658ab84942045a48481a5e9db7da64aff2a0be19e6bbbe4801e9 5816 redmine-plugin-pretend_0.0.2+git20130821-3_all.deb Files: c1ed70cc865108f738cf3d1722934484 2067 web optional redmine-plugin-pretend_0.0.2+git20130821-3.dsc ba2645c63c047ba9d928cdaf1f5cdc54 4136 web optional redmine-plugin-pretend_0.0.2+git20130821-3.debian.tar.xz 9bb09c53cf1031c1a43329ace63b8672 5816 web optional redmine-plugin-pretend_0.0.2+git20130821-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUaannAAoJEFK2u9lTlo0b3NoP/AjZcGmKmAr9DMj+5iDDvipe B8iIK4a6wKIhXZJTsSSVba/dQEpnoueOyJSXCzuz5zkMQ/hZiLcGeHc11OaioXcn Lo7O+aTXv0dGC66JkK2sjfEmn3TZd4crY4EMGFUrP4uk6ecMPYKVndULvn6aKjT6 IAEYvJj7wk3KziNVtIJJ2arrPqVEhST6UF8G0biC36qG5eHuWR0S1wr0feBndC3X X99XZzXR3O0LYTjyKbA95VH5bX6eaPbkq5w8ku9/BSHJu50xs4XUq7h2b8VpRb1j AUlpDzOV9BJvNIaAtEc1PlAA+ZVHLwav6GmGMZEthJDcv4ggq7mWGslAzRXmUlJ9 uxjQKxoLIcRfGySO0zZLRlVswtGx6MZXgJxIMFN+XGPN7f3davn3ys+cqwSy7TcB +izY+mzlsqZRRE/6/UZeJIr5LSzImWIfbwkIL31pQFgLWfLBpplQfrWpJM5pnp6Q dgJx7rszV0i9twTxIvOvicJWlY2amti5mkVCCaE3Ri0pDDJoufEx3U3USwz1Qruu 0469kju7eT0MsDOazv/VJJRaoWnQQi6A6OmcdswdnbJqLlR8blff50d9DlOcs3CE NPeaPrSRhCSwQ1bF/db9kb7QD6TWEkF+7f/IjbbqHKmmJXbJU4JaYlsWftmsunTs kdFqGotkVNH4XCaCI7DR =9iZO -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/e1xqiuq-0004la...@franck.debian.org
Accepted xslthl 2.1.0-4 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 16 Nov 2014 11:59:06 + Source: xslthl Binary: libxslthl-java Architecture: source all Version: 2.1.0-4 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Eugene Zhukov jevgeni...@gmail.com Description: libxslthl-java - XSLT syntax highlighting Closes: 769526 Changes: xslthl (2.1.0-4) unstable; urgency=low . * Refreshed patches * Bump Std-Vers to 3.9.6, no changes needed * Updated to debhelper 9 * Use configuration file provided by default - thanks to Vasiliy Shlykov (Closes: #769526) Checksums-Sha1: 16e7b67d3a1a10ebc8b7a7978ab6add5543b2cef 2069 xslthl_2.1.0-4.dsc 603e1d9721fd93e1432c74c4672d0409f58c452e 5260 xslthl_2.1.0-4.debian.tar.xz 574027bcef05565beb3c1d61f72663cb7845804b 71278 libxslthl-java_2.1.0-4_all.deb Checksums-Sha256: 2c222a9e3207ceac05831dd37ef697c9d0c3ad4c23e6c1090f2ad4bad4b7a5f4 2069 xslthl_2.1.0-4.dsc 15174cd026258e0eaa8db5085c0be49dcb084a55925bb64fa02d7e35d8a50ffe 5260 xslthl_2.1.0-4.debian.tar.xz 5e1568c81eb8302bc0168258229800d317d333d7f67bef658162375861a1ea90 71278 libxslthl-java_2.1.0-4_all.deb Files: 9402f4772b4de9a3d7b2c58a3b9e8bcf 2069 text optional xslthl_2.1.0-4.dsc 7dd6bd92f132cf4cb0b5748df678b313 5260 text optional xslthl_2.1.0-4.debian.tar.xz d15d848da904d04559c53443cfe9a425 71278 java optional libxslthl-java_2.1.0-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUabhPAAoJENfTQC4BBmMMYhMQAK/OYLedZqY5RGhhnBePPnxR T6vVijSvc2fEJsuZyb3WbDeWgmzQzpM+ERxmz/ejRRYhovMWFSQ/WJU0iogQ0J0s FjQqjl1SRrKqRmBul1GQrL9FjsKAqY4uKaxdxBZFDO1dYuCJkSrKMVOm/k3Ndwu2 +HJPXtxgHBHRsBnAqXbdK9qvp/N9EE9lACNA8iv/Of5qaCSWF8/9u/46om/osOnW WUC5Isw8wxxM5y+4utMnogC6n6nwRqejqUXwYJr/jlNcFVAsp26kMI0EcyCDAubb v/trf3r74crS05rYxhjZXPz5i0F72n1r8+B7tkronvjcTuwp4HQpyIeiwm+RndJa DeN4t4PnD+0jb7kKMR4i3hZ7O+HH0T6Vv47QeoOHWziFTq47tB3OSxTuuY8R77O7 ppPUzleVGE5NV09fUsGLXcD97Y2W/o9LUtkeAIGVJdJt/bFUg2IUlNOHLCVmfC15 3vGanDEsNhtydjCo2pZjLbPKMoZSSOoHejZxAvSgvZZh+avdsD4wVdd/VSxZSa8Y gZQEj81DLWsYrKn5NOrAVd0dwT6c+W6QpOABDrkm6dQ0ZOBp+20qXMtCloycoXmq 4BVhpoj/iiPvXvr6OOzHMias/FHtPc5KqxRYlbIxjcEYWWdElV0GlnH4J3W+ISVZ J1A9UUfXCdqxT5mjumh8 =AXbY -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/e1xqivb-0005hs...@franck.debian.org
Accepted gtkwave 3.3.63-1 (source) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 17 Nov 2014 09:47:55 +0200 Source: gtkwave Binary: gtkwave Architecture: source Version: 3.3.63-1 Distribution: experimental Urgency: medium Maintainer: Debian Electronics Team pkg-electronics-de...@lists.alioth.debian.org Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) aelmahmo...@users.sourceforge.net Description: gtkwave- VCD (Value Change Dump) file waveform viewer Changes: gtkwave (3.3.63-1) experimental; urgency=medium . * New upstream release. * debian/gbp.conf: set debian branch to experimental * debian/control: Update my email address. Checksums-Sha1: cd1b5d5de6eeea25d819eca469670a0ddeba7311 1767 gtkwave_3.3.63-1.dsc 1037b2862cab630d221c57518162ae3bad1b3a01 4089589 gtkwave_3.3.63.orig.tar.gz 46e2f8488130daa3080a3fff2502fb394214d32e 6704 gtkwave_3.3.63-1.debian.tar.xz Checksums-Sha256: 19c09a2c3831b22e9910acd6c2c115730eab1b458f57f086539bfbe60e9de61e 1767 gtkwave_3.3.63-1.dsc 93a9411bbbad801dae1190218db85fc7f7dfb1b614931a16cee037afe0aaa8a6 4089589 gtkwave_3.3.63.orig.tar.gz 970122cd5ed1502fbe807259fc4ae77fa10cdd0a2d1acf515643cd19f1d1e58c 6704 gtkwave_3.3.63-1.debian.tar.xz Files: ff504f88a08c577f65dc79f1b470ee97 1767 electronics optional gtkwave_3.3.63-1.dsc 94c3ece83954f1cb2e9e572b4728001c 4089589 electronics optional gtkwave_3.3.63.orig.tar.gz ab1d717492056a1988fca5608fc35796 6704 electronics optional gtkwave_3.3.63-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUaahaAAoJELwZapTt3aG3Md4H/iqNz+EQu+FAAcap+a83e8V2 1kRIwIqgW/1Npr6BMtO6dgkFugj1NTcVqlSKDoNDOfAl499RKm6imqwCk3UMc6Io cT5G16DOhSktOJVJK134tVxw/u8HE385Oo+adHpcFRLspKY/c0ZFkinYv6T/8zGx 3DR+lEKxORUMu0PBgUfHKKvqdbM7YvJmD4tTfHwsCi86SB9U+Z7hRyvm41Z4uPRU ELPKgwPRiNmQaRNA4f4cyCQIpD+r9SLn4WHq3VbkmgDfAERttFR0dzg0EV92EEpr ZoncMAQtwC9y2FpS3wTtAcsuGGgR2rD4x8RHGeVS7G6hUa5/ceFRjMisCNGp+mk= =Xepn -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/e1xqjd4-0003cv...@franck.debian.org
Accepted openjdk-7-jre-dcevm 7u60-3 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014 10:58:24 +0100 Source: openjdk-7-jre-dcevm Binary: openjdk-7-jre-dcevm Architecture: source amd64 Version: 7u60-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Emmanuel Bourg ebo...@apache.org Description: openjdk-7-jre-dcevm - Alternative VM for OpenJDK 7 with enhanced class redefinition Closes: 768715 Changes: openjdk-7-jre-dcevm (7u60-3) unstable; urgency=medium . * Backported the new JVM_FindClassFromCaller function added in Java 7u71 (Closes: #768715) * Standards-Version updated to 3.9.6 (no changes) Checksums-Sha1: f405d79ccbb3c5ee553f6d206f3bf67cdd8cd45e 2080 openjdk-7-jre-dcevm_7u60-3.dsc d2eb51db75bc3a9d5769ba592fdfc57c51554610 95736 openjdk-7-jre-dcevm_7u60-3.debian.tar.xz 669c30084916512ac1609b90d289c998b3f1e3ee 3194718 openjdk-7-jre-dcevm_7u60-3_amd64.deb Checksums-Sha256: b28b3cc148079e0ff8d2379a8f0dde7fc119c0d6cdba1c6a3506213e22e040e3 2080 openjdk-7-jre-dcevm_7u60-3.dsc bc2965e46e0ac90b2218a3903a3858402ccc924a0bc1c9996ae34bf7810bc0c3 95736 openjdk-7-jre-dcevm_7u60-3.debian.tar.xz 856c58f4760d4dc02df8ab0d252a549fc5ed7eae2c8b8493d821b86ce7cd2d20 3194718 openjdk-7-jre-dcevm_7u60-3_amd64.deb Files: 44c6c67e1dffd071ce98fa42368d30ac 2080 java optional openjdk-7-jre-dcevm_7u60-3.dsc ff60d3b5d81f2c5604ee511e88ce3457 95736 java optional openjdk-7-jre-dcevm_7u60-3.debian.tar.xz 1d90af6cdf526f29efa4ca21731f4d9a 3194718 java optional openjdk-7-jre-dcevm_7u60-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUacrIAAoJEPUTxBnkudCsbJ8P/2xRooqqf2r5sIQh9UZ1/hbC 010AeBADGUwe7RSFZjsWherpWp5mYKXQSDE2lT9uat9M7KPgfYoHjC5wzBvSZ69O 7zQbxQ9ZLgIdGtUAGJo34tAmj5/kpFm9oPgYutEGoo2Wk/qgbWx4gPeHvzE6hopS ENAFQArSeUFA5zI3EF9gASGT38bCHy9OXE4YNytjOlyV/8V4b3VK8K5GweMh6fzd 6PraL0peIhkI6FOQ/uvhvedW9YfFgKDfqxh+cFf5v3uqZbcuC9y8kp3af8Bgx110 o7byjrnzLj79lMrmBuTk7U8VpKKw01osnF8lNpMrmJaW+wVSQY2UqqzJPP5mKiKv rtlGd6Uka5ag8tuKQtfH/Jq8+vp5JZB8ar030DoNvoeNDAUuKIbmnz0tARDalKOs vO/CNHK9HScVCGZm7uVdUx10MfqAQgNUqUKZmezbVVeIW71iM31bhgI2eIOveb3q izpxxML6eMnhMi1Yhdpyf32z5uhBsMqIBEM7yZNiwQRkl0AIF8+rOBHaaWIi76Ak QHaODsslR+MOxKZoO/srTtauARJBZfMtwAJ5WVdd+/SftJ1pV/ZHvsO5OktxINIL gg6nHFdXoyI4Z9/2NraICmadvoAYIAfWJhvxGYgD2pu7hwATgSo6ti2rICgJw/YY uEM455seOukbO+Qf+wsj =yAJC -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/e1xqjdf-0003nv...@franck.debian.org
Accepted qpid-proton 0.7-2 (source amd64 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 12 Nov 2014 15:58:45 -0500 Source: qpid-proton Binary: qpid-proton-dump libqpid-proton2 libqpid-proton2-dev libqpid-proton2-dev-examples libqpid-proton2-dev-doc python-qpid-proton python-qpid-proton-doc Architecture: source amd64 all Version: 0.7-2 Distribution: unstable Urgency: low Maintainer: Debian Middleware Maintainers pkg-middleware-maintain...@lists.alioth.debian.org Changed-By: Darryl L. Pierce dpie...@redhat.com Description: libqpid-proton2 - C libraries for Qpid Proton libqpid-proton2-dev - Development libraries for writing messaging apps with Qpid Proton libqpid-proton2-dev-doc - Developer documentation for Qpid Proton libqpid-proton2-dev-examples - Example applications for writign messaging apps with Qpid Proton python-qpid-proton - Python language bindings for Qpid Proton messaging framework python-qpid-proton-doc - Documentation for the Python language bindings for Qpid Proton qpid-proton-dump - Qpid Proton messaging tools Closes: 768617 Changes: qpid-proton (0.7-2) unstable; urgency=low . * Change dependency from libsslcommon2-dev to libssl-dev. (Closes: #768617) * Bumped Standards-Version to 3.9.6. * Added support for dh_python2. Checksums-Sha1: 74a52c011ce1139d808e206412caf4f20a10f256 2577 qpid-proton_0.7-2.dsc 95d5d0b8674a4db46e07b2fad499b27dc379a0f6 3860 qpid-proton_0.7-2.debian.tar.xz d09e8aac17dfa193fcf5c70c537065bb32f94aa3 5798 qpid-proton-dump_0.7-2_amd64.deb a7aa2e2d06bfc5b46c9ff641872c72c5e063c009 99124 libqpid-proton2_0.7-2_amd64.deb 722d28bd44c94fa0c921582dfa8d60626ebe5f83 42436 libqpid-proton2-dev_0.7-2_amd64.deb fac986e7cdb84b067599e5d249c95cf97e8bf08f 7420 libqpid-proton2-dev-examples_0.7-2_all.deb 22b67c39b3906367653f75f7ae6aab5651089b52 269884 libqpid-proton2-dev-doc_0.7-2_all.deb 14317785d1bafdf8c54ffa552d16c0081d9410fb 103524 python-qpid-proton_0.7-2_amd64.deb 7f34701608d41ce42fb1de64d69b5e15deec229b 114662 python-qpid-proton-doc_0.7-2_all.deb Checksums-Sha256: d023b74dcc685d80287ddc370ee4bbffcc5f884f7928af1456449e0bda287879 2577 qpid-proton_0.7-2.dsc f31953547adda75db307a21299d4a4d2c803a9bb2378b3c906aba533cc48c2e5 3860 qpid-proton_0.7-2.debian.tar.xz 7ffe4317513575bfdc95419000ace5ea0df38bcb4b5bf835ec21b16d27a7e9b4 5798 qpid-proton-dump_0.7-2_amd64.deb 46124a1478f1e659099b4ea88805236c869fe01b94f9a1dd330246ea9799c052 99124 libqpid-proton2_0.7-2_amd64.deb 3ed15eb3009139a455f56efae8f6b92f6189babad95bd7be8d4499d3d5317355 42436 libqpid-proton2-dev_0.7-2_amd64.deb 064a998328ee0006d550e096ef988410d1779ecefce5176150e6839c1824f3cf 7420 libqpid-proton2-dev-examples_0.7-2_all.deb 2c6352aa1192ca8920101e40b49ca8c88cbfaebeee6b40cfab80df5663ff72eb 269884 libqpid-proton2-dev-doc_0.7-2_all.deb ce8b68cc9ce148eaf07273b07622b2fb41620daf4cf6f5d704d7ddfe4e03a73b 103524 python-qpid-proton_0.7-2_amd64.deb 96025c67d7834828688d06a3c8e01dfcc4af1bfab15aa144f2034721473995b7 114662 python-qpid-proton-doc_0.7-2_all.deb Files: 53f3cfd4e82403b19c586fcfe9aab815 2577 libs optional qpid-proton_0.7-2.dsc f5f33ba3e10df40444d2c25d113cb3ab 3860 libs optional qpid-proton_0.7-2.debian.tar.xz d68e593316976d12ea10b6a3c3330074 5798 libs optional qpid-proton-dump_0.7-2_amd64.deb c2957c99020d0a5a4babdf333b79ed4f 99124 libs optional libqpid-proton2_0.7-2_amd64.deb 630c1f23a873a30adf81945f60ca2406 42436 libdevel optional libqpid-proton2-dev_0.7-2_amd64.deb 56501b874433b38e234abcf666b1574b 7420 libdevel optional libqpid-proton2-dev-examples_0.7-2_all.deb ce42c0b8244322d0807337d06e2be8ec 269884 doc optional libqpid-proton2-dev-doc_0.7-2_all.deb 5cd79d47de7b361af7e80bde0a7a9796 103524 python optional python-qpid-proton_0.7-2_amd64.deb 416a338331005884b754e084c0c79f89 114662 doc optional python-qpid-proton-doc_0.7-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJUac+HAAoJEGxlgOd711bEqusQAKeY2G3o6AyCBZ4Tg4frfBDG oIe1sA9kCby0MFqyQ7QkXWSJLMV8FXBCU9B7N/zHpu+jRJU3IPnMWaCRYDwgSUIk 7QqT8cTicJvZ/zoL/fClpYswg2Oku1+TxiXC2iEVAibMB/1jDTdAXyT1FrOtFaVA 9HXRBNlmiJS/hI0WCkaKUV9+xyhihLAsQGWgiEftpqTziuaOm50ZFEpGeBmg0W2x lmFPD17QLqsceFdBKNRdXFS8GSFsEHrLA8tUDeyzzbaetVVZj7OJowOCqqKCD760 Kkj2gzs2Kopfl53FklZirLAs/46Nda0uwZRUpM1kcPy7tIZM35Yzki3J2RHjuXUW 3BLlYSP3cBDKGfOjhNMIOSP13sybgpRA3bk8pf2IPhskFT8MxNpCJ7Nuejx2Wo0T glZWCxAcmL926yXS5DhEJ7FXB64Y+RW5e6WZT9wuZctdeVvXHxEDBCgoX+H/I4bh q/QDS+6udziQdSMD05i1A7n9vxluX9+KLQlm3OQF48OLNeToxPmzb5SDEiPwuIRh aYmWoJepvUvl1nl2YrTyGJsEzyA9fbzg9rYWBfnES4uTjHDcikCLeiPqQWai8m8P uVEj7Xq2Ymb9j4FY4qsMwvu/REaSQWFnnbnrZ8A2ehWqYV4uEGifJQji0IpHVqoB pyt97nb0eLQyDW4Y3dKb =dKMT -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/e1xqjro-vm...@franck.debian.org
Accepted util-linux 2.25.2-3 (source amd64 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 06 Nov 2014 13:54:04 +0100 Source: util-linux Binary: util-linux util-linux-locales mount bsdutils fdisk-udeb cfdisk-udeb libblkid1 libblkid1-udeb libblkid-dev libmount1 libmount-dev libsmartcols1 libsmartcols1-udeb libsmartcols-dev libuuid1 uuid-runtime libuuid1-udeb uuid-dev util-linux-udeb Architecture: source amd64 all Version: 2.25.2-3 Distribution: unstable Urgency: medium Maintainer: Debian util-linux Maintainers ah-util-li...@debian.org Changed-By: Andreas Henriksson andr...@fatal.se Description: bsdutils - basic utilities from 4.4BSD-Lite cfdisk-udeb - Manually partition a hard drive (cfdisk) (udeb) fdisk-udeb - Manually partition a hard drive (fdisk) (udeb) libblkid-dev - block device id library - headers and static libraries libblkid1 - block device id library libblkid1-udeb - stripped down block device id library, for debian-installer (udeb) libmount-dev - device mounting library - headers and static libraries libmount1 - device mounting library libsmartcols-dev - smart column output alignment library - headers and static librar libsmartcols1 - smart column output alignment library libsmartcols1-udeb - stripped down smart column output aligment library, for debian-in (udeb) libuuid1 - Universally Unique ID library libuuid1-udeb - stripped down universally unique id library, for debian-installer (udeb) mount - Tools for mounting and manipulating filesystems util-linux - Miscellaneous system utilities util-linux-locales - Locales files for util-linux util-linux-udeb - stripped down miscellaneous system utilities, for debian-installe (udeb) uuid-dev - universally unique id library - headers and static libraries uuid-runtime - runtime components for the Universally Unique ID library Closes: 767194 Changes: util-linux (2.25.2-3) unstable; urgency=medium . * Ship fstrim timer/service units as examples only (Closes: #767194) - this works around #757891 and #767429 / #760168 Checksums-Sha1: a4a5f5bf072f43b7f1fc4793048e395b7907c0c1 3440 util-linux_2.25.2-3.dsc 91d62c10a7def1c7399455eca46988c079dbb2f5 66756 util-linux_2.25.2-3.debian.tar.xz 832b828c001767bf66591a8c6a8c246282c9d16f 93172 bsdutils_2.25.2-3_amd64.deb c04a495f26e00be3ff9c481c846d59248a6eaa20 843632 util-linux_2.25.2-3_amd64.deb 5762c949ae2b2f845159896744a438affa477596 832938 util-linux-locales_2.25.2-3_all.deb f9c29358eb7cfc5269d3f8e4ef6b4603a7f3e485 167700 mount_2.25.2-3_amd64.deb 2ed8675867146470cb2556af22613d5273eefb39 121708 fdisk-udeb_2.25.2-3_amd64.udeb 21479e01e322658957e2a4d674e35efed32e6912 908566 cfdisk-udeb_2.25.2-3_amd64.udeb 15103dd6fc9e226bbd79911abac286b8c41696f8 155488 libblkid1_2.25.2-3_amd64.deb 6e3d178c0f1355dda690018c2130969a7dafe8f6 99024 libblkid1-udeb_2.25.2-3_amd64.udeb 88afb9333f21e478cf9cf4d43ec4b323acbcb63d 179636 libblkid-dev_2.25.2-3_amd64.deb b18b4a2c06336cdd2bbc7a2712baf379b33e5389 162882 libmount1_2.25.2-3_amd64.deb fa8221069f4ef1e50b6862f6c4fbca56b5318a04 180214 libmount-dev_2.25.2-3_amd64.deb c711591b6a75e14f818594a11109bf45d6204cec 109352 libsmartcols1_2.25.2-3_amd64.deb 2ac834b80858c17f090760b5fb50296f75e76f52 52798 libsmartcols1-udeb_2.25.2-3_amd64.udeb 76bda3464bec776618c4d8ac7ade22e67b9c45f9 119274 libsmartcols-dev_2.25.2-3_amd64.deb 59081fdb3434d8889dcf59b6c685d0d5269bb629 63770 libuuid1_2.25.2-3_amd64.deb 31b6d562809826c66531083d760c2c870bfcc612 73360 uuid-runtime_2.25.2-3_amd64.deb a012430bd91b8f03b64e22578809c78038432e93 7166 libuuid1-udeb_2.25.2-3_amd64.udeb 104e04a2b35786071bebf28d70afa75a57fb9ee8 77418 uuid-dev_2.25.2-3_amd64.deb 36d9045ddb373c0bf1e8caeebbfbf1a129896a8f 27718 util-linux-udeb_2.25.2-3_amd64.udeb Checksums-Sha256: f133c35e85f489c097ddb80efd2e243e2fc4c9fe09752eed289c991605b462ed 3440 util-linux_2.25.2-3.dsc 3073f03a94750f1c6035d5062b5e85ba33f7ee63685c9005c6ff1889f105aee1 66756 util-linux_2.25.2-3.debian.tar.xz f20bc420422a9848e3a0c255b385d2adafab918c54dbd202181159621fa83d78 93172 bsdutils_2.25.2-3_amd64.deb 9ef31d55f110336c8f2a449ead3543b28eda4c3e718acc151f51b7ac2ddfc017 843632 util-linux_2.25.2-3_amd64.deb ccec2eab2d0b0c7ca534dee701c3a24d606fe84aa8844245cb73cfe7e2fa9525 832938 util-linux-locales_2.25.2-3_all.deb 6c3120dc676573940f997e9aa055a70394bb0448828d9c83c45d2d23ea3f8f94 167700 mount_2.25.2-3_amd64.deb 26daa1f8170f106156342353c2c29f10bbb80be66253444c32fc882b8d864683 121708 fdisk-udeb_2.25.2-3_amd64.udeb 94adad34cbba1e585daadca8bd496cf3d05c5acc37857a8e121bdf52a7d8936a 908566 cfdisk-udeb_2.25.2-3_amd64.udeb 084ddc32b3cb469742d9c2cbde6a4288d94f5635ccfab352a3e875b38cc3f1b6 155488 libblkid1_2.25.2-3_amd64.deb 6604cbff026e3dc2407cd0610787def1d456254b20d1ccb3bc71b42766b6 99024 libblkid1-udeb_2.25.2-3_amd64.udeb 7fc85d8bc12ddda71c8d85bbb6b8cdaf5f3806063fd57c00135b434f2b280034 179636 libblkid-dev_2.25.2-3_amd64.deb cc4cb45a0f6fa7b218860a2a6e6f596ec7a6eb2c2e42ccbbe0af7d3c69b375ab 162882
Accepted gnome-panel 3.8.1-7 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014 12:42:35 +0300 Source: gnome-panel Binary: gir1.2-panelapplet-4.0 gnome-panel gnome-panel-data gnome-panel-dbg gnome-session-fallback gnome-session-flashback libpanel-applet-4-0 libpanel-applet-4-dev libpanel-applet-4-doc Architecture: source all Version: 3.8.1-7 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Dmitry Shachnev mity...@debian.org Description: gir1.2-panelapplet-4.0 - GObject introspection for the GNOME Panel Applet library gnome-panel - launcher and docking facility for GNOME gnome-panel-data - common files for the GNOME Panel gnome-panel-dbg - GNOME Panel and library for panel applets - debugging symbols gnome-session-fallback - GNOME Session Manager - GNOME Flashback (transitional package) gnome-session-flashback - GNOME Session Manager - GNOME Flashback session libpanel-applet-4-0 - library for GNOME Panel applets libpanel-applet-4-dev - library for GNOME Panel applets - development files libpanel-applet-4-doc - library for GNOME Panel applets - documentation files Closes: 769882 Changes: gnome-panel (3.8.1-7) unstable; urgency=medium . * Fix crash when clicking on clock applet (closes: #769882). * Require gweather 3.10.1 (where BGO #708586 was fixed). Checksums-Sha1: 12008a4c7d1ce3c4d451de19da0eec48cbf90ffa 3490 gnome-panel_3.8.1-7.dsc c4e48ae1685d11e7674fe160ca2f61927a464297 36460 gnome-panel_3.8.1-7.debian.tar.xz d296c631c74e8ce3a0cb15c663925471e0ce6ca7 1176176 gnome-panel-data_3.8.1-7_all.deb c6ea75ec597f62ff21a4d4c05f24f19f494e4dd1 234972 gnome-session-fallback_3.8.1-7_all.deb 04c09f96f43cffd44ecac1c21be99de415643e71 240226 gnome-session-flashback_3.8.1-7_all.deb 0714f97f263cb571627f2f9389706b7cc9457176 259446 libpanel-applet-4-doc_3.8.1-7_all.deb Checksums-Sha256: e7a1ea51baf21297097d363fbf5e6fda1ed7d737b6b24ab29b21383db9422c25 3490 gnome-panel_3.8.1-7.dsc 41de63435810eb2c063a952f1b4a23589cc47514328fefc0f4987223a4a53665 36460 gnome-panel_3.8.1-7.debian.tar.xz ec10a4da83c9b02fbced5e6745df3c6fe9a1c557e0dc4e7dc35cd6fa9c527650 1176176 gnome-panel-data_3.8.1-7_all.deb c9260aae588a3031da25207b4c017c0a3c683d6521cca1661550917f1fbedfbf 234972 gnome-session-fallback_3.8.1-7_all.deb 1a590b39e355b381ee07935e85bcaf4627b775539596edb4b68f8ed0f6b8f705 240226 gnome-session-flashback_3.8.1-7_all.deb 960c7eb2bc89f13b5bd03c3ba90a1ba6f1b8a0fe9da9539f437af6628f35b9a5 259446 libpanel-applet-4-doc_3.8.1-7_all.deb Files: e8741eabe981eff1b017eb0532cb27e8 3490 gnome optional gnome-panel_3.8.1-7.dsc ae4dfdadaba17f85a0309539924095ef 36460 gnome optional gnome-panel_3.8.1-7.debian.tar.xz 4a260d0844baf3f7396c1e679718977e 1176176 gnome optional gnome-panel-data_3.8.1-7_all.deb b599cfdbf775833eab977c9292d44f4b 234972 oldlibs extra gnome-session-fallback_3.8.1-7_all.deb f0444a35bdd43b7f5f3de2422be62bb7 240226 gnome optional gnome-session-flashback_3.8.1-7_all.deb 1ee21eb5a8be8becb3a4e2375fc24e8a 259446 doc optional libpanel-applet-4-doc_3.8.1-7_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUadOBAAoJEGAmk20vHIrgDbwQAI5+di3hsCoC+evI/k1kxIUE KB88VaW6i5dBC4tO0N+FlIKZNWxJUxI2wJBcqkQCWSW0VWwGAmv9BZvR6dXxgvZf 5xcFM67/4PVMlmxSovitQeuLLN5/Oxe41pXFr13xWgukR857yr60WrcSXEGVJ2+N xP5xzWbiGxm5C7Pc+pdz058w504YcPBneUCEaPCkamlDbvLZZGTsaQAMgiWCzfo5 pImWZOkcWwhwXBWsfv0FOKAZeviuTqwyZOMyWS9fldFvUESnhgngDvTy8DOoKnvW vQrCO80zJVHszHkuJbHYXK2bUhVUhzHS1rHApmwBbwAE7U3kFMDmZZleMLRWFyjF dih8mQMH/wdeX0DU0+XB0+DiMhwkCDytHhGu672thaQ/n4o9oeGMv6zfaIvcSCHB v+/HDqmAS1+4vIeB0qlLQlLOvIYZZsyx9BMkACa2f0vp+HTlpAeDYjB2UrWd7XK9 mpFdlWILcceD0Vs+wYnnvTcBfiIJ9t6Gc5wf7qXp7ACh6ZyIF00x5Y3i71N3ODxy DL3hKP/VWmE0hN4Y4V3hyN2k/EUdh/mj4vm9nmy2z4Xag2VH0t1PjWGDkB0eAMn+ xCzgjEpHVJe3eDSzkZU/HABYOkzBSQ0ZVY5Sfy8KLXXC/pdCx+3b00CRRVUkVxoi GRnn2yLGe5PrdLAt4w+W =+oUX -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/e1xqk6l-0005gs...@franck.debian.org
Accepted itools 1.0-5 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 17 Nov 2014 12:54:08 +0200 Source: itools Binary: itools Architecture: source Version: 1.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Islamic Maintainers debian-islamic-maintain...@lists.alioth.debian.org Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) aelmahmo...@users.sourceforge.net Description: itools - Islamic hijri date and prayer time utilities Changes: itools (1.0-5) unstable; urgency=medium . * Revert Bumped compat level to 9 Checksums-Sha1: 3eb597e3c5777e754dfde1e97dcfdb3446142dfa 1625 itools_1.0-5.dsc 6e4702b8cbe053566d560f44c8b1e45b6621a5c3 4812 itools_1.0-5.debian.tar.xz Checksums-Sha256: 87089b9e06feeb12fef9ea30609a822d750b0d23dea9627fc72ec392c973d312 1625 itools_1.0-5.dsc 56173946b53ac1c92214fa27467d06cd910c9a2d6bd18d85a5d4888e07ec262c 4812 itools_1.0-5.debian.tar.xz Files: cf7e16e99e0182a0b0c518c166b699b1 1625 misc optional itools_1.0-5.dsc 5646845094946e19217ceec78032c819 4812 misc optional itools_1.0-5.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUadPuAAoJELwZapTt3aG3eU0IAIU/LyqOP7+tJVvxv5lydIw/ MaNAWg9KQlzkVnrd5UwRjAOLnkcgr/hGvv16wcC2KGsvdrspjG82Gw5BmsQ5qFD6 G0St4Nja1H5fysj19gR4Lc6wlFNya6qUA2FAVL7dzFo/aq5lXLdjLVDIVGatvkUN KpiOYHLLGUPGTwqSYg9rx2NczqfzzqiOfTaqUpTJ/xLGDw1qY6wshBjJFL3+X55m nG5P8s3+KR1mYa3n39RCZHaTaMxfY3Nf2f/cLyQHzSSa8ebdqPJQI6O9sTSAv8AG Jmhp9C4SuJYFIZ9BMD9abHTz2hh1xPS8Is2cUHUXSuJ2MYeo+xmtBo6vK3kKlfU= =JgEa -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/e1xqk6x-0005kc...@franck.debian.org
Accepted cglib 2.2.2+dfsg2-2 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014 14:13:01 +0100 Source: cglib Binary: libcglib-java libcglib-java-doc Architecture: source all Version: 2.2.2+dfsg2-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Emmanuel Bourg ebo...@apache.org Description: libcglib-java - code generation library for Java libcglib-java-doc - code generation library for Java - documentation Closes: 768721 Changes: cglib (2.2.2+dfsg2-2) unstable; urgency=medium . * Team upload. * Disabled the unit tests (Closes: #768721) * Set the source level to fix a build failure * Standards-Version updated to 3.9.6 (no changes) Checksums-Sha1: bb33f2d54bddcf3d1b5d9cc15c0fdb8d657db69a 2125 cglib_2.2.2+dfsg2-2.dsc 824a64bf61c4294e083223a250f4eecce35f1d02 6612 cglib_2.2.2+dfsg2-2.debian.tar.xz a9b77f4833d324561cff5dd54058e3e092e66631 696286 libcglib-java_2.2.2+dfsg2-2_all.deb 4a15396dd929825356423fc4e449ae7a53492ff1 106864 libcglib-java-doc_2.2.2+dfsg2-2_all.deb Checksums-Sha256: d103932cac23787551afa1749feb96a9ef094808eaee3f0d1e09dd49345040b8 2125 cglib_2.2.2+dfsg2-2.dsc 4951552f0216e2acfc109e3a28d38658cdc3ca54a404a21424fd286f0a9e48aa 6612 cglib_2.2.2+dfsg2-2.debian.tar.xz 0faf882b369025a8879d238fdf12e292cbc5cba49e8dd2bc3d2f23a87d30f664 696286 libcglib-java_2.2.2+dfsg2-2_all.deb c74e4e5748aab47d5cf615e541049e393d2014d11f876c7e3708e2ad2692ded1 106864 libcglib-java-doc_2.2.2+dfsg2-2_all.deb Files: 1f2f6934dc85eea6842057460353149c 2125 java optional cglib_2.2.2+dfsg2-2.dsc a8287f02bea07ae0ca623ef3973b5879 6612 java optional cglib_2.2.2+dfsg2-2.debian.tar.xz 5aaf8ba650a8b413dbfd87184b5b1cb1 696286 java optional libcglib-java_2.2.2+dfsg2-2_all.deb fda6a6d43f5ce19fad48f8a1338e35a8 106864 doc optional libcglib-java-doc_2.2.2+dfsg2-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUafTHAAoJEPUTxBnkudCsPu4QAIPlBQ1ePZ8mkNp2ICdkmNLw r986/2QkakGuf0uwB4nljzz9dmyFPMCOKZW1oFWkkYQbxltVogx53JnyffSOq4tw K+IOPf1YemNAABIqAzTfRAVRfkN6EXFU0URit0Lq+lztnXZ2OmRf8ImQeX/KQocC AQAagwzrekADhMt1PX+Y8gIllnAMBj7HWCiubfQKu1mkpCPYLAmgmIvEYIm2/rHE q0FWsLI9aWNIukuETXHemWw2HXlV3fV+On853tAHSRmkmDpgTtWxWl/f6o3LXd5G CZWh9OiVRtVDYf2dwWczMAD4pYwFGygjM4v0bEJI4dyqBL5eAuzn9B6UdVdZj6hN df3FTgueZXShDejSQ8YXGBGyCkl1Jm4am9gpIzvgAtUeJAatBtkiRqdpV9c6JyeD zgUcuhfy7+BN4iUUDAsExuTFenPjSWRUf7/3LPvrqw7b4ZnvcBGoAjIWiOuzij/6 +kMyc12IzRVNVFcb4bYv7hzKGejE+/BFJLRnV9+uXD7/ufcyCni0B+Wd0tWurJuP ik2kVcHa/hzZcXgZ9+XDZyA19QMwdRJOus1ennkX0DYw7KClY0c105Bk8KhxBxER gylh08jZHRSBxXv35YQOHsj9CPlJumwmYJ8iZ0482tRDsDymHNv54Ix2G/YLu7La r774fqaUrLKG5BL2OBDX =qWxK -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/e1xqmcl-0003ws...@franck.debian.org
Accepted testng 6.8.8-3 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 17 Nov 2014 11:43:10 + Source: testng Binary: testng Architecture: source all Version: 6.8.8-3 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Eugene Zhukov jevgeni...@gmail.com Description: testng - testing framework for Java Closes: 769831 Changes: testng (6.8.8-3) unstable; urgency=low . * Dropped orig-tar.sh in favor of jh_repack in d/watch * Added source for jquery-1.7.1.min.js (Closes: #769831) * Standards-Version updated to version 3.9.6 * Updated debhelper to version 9 in d/control Checksums-Sha1: 1b7df5386a0eed62113963bd93874fdf525ac092 2045 testng_6.8.8-3.dsc 27cc128a3d60fde9011ad8645dc464316b00a53d 66824 testng_6.8.8-3.debian.tar.xz e22ef3523532cf820a634eaf1a1b32814956c52d 752886 testng_6.8.8-3_all.deb Checksums-Sha256: 1ae2609fa84f89c74bd47231932685350c365954f308d9c424704642a0fe09b7 2045 testng_6.8.8-3.dsc 6cf66a79eb9f6aa9b6c1c76ff296a7ee65d8e551e549fdf4ac101f50bed66f70 66824 testng_6.8.8-3.debian.tar.xz f9818e38f71854436ccde541be3c26a46b117e4f05db0687b88d4eeed35f18d7 752886 testng_6.8.8-3_all.deb Files: bcf27533eef4c1722a682cbc978faf97 2045 java optional testng_6.8.8-3.dsc 56840454e854c1cc85894f2320aa4e7a 66824 java optional testng_6.8.8-3.debian.tar.xz 76e0bdd6e4167e676e223d9ba065e9a9 752886 java optional testng_6.8.8-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUaeG8AAoJENfTQC4BBmMMUFUQAJG0XzPpx/QYPLxFxH8y0EZ8 P7CIpqaNFLpztFTH7Ehr8yhV4oqexDE0RvFclxJPrHItgZ/eYvEK7VJzGUSAJA3P eM+DO2jIxgmxMdzMwwo4x56A6s7pM8re8wYnamhJLQqPXx5NSVxlsN+CVryylTyf TaxmFsZcQSdK8T+bZquXYBNxs3NRHwRijlggu0N43GsCywM4TX3oAFmfjMND/JRk LBpMEDq8w+8ax8gBSiHs/RpklgnvZaGsbMzr8NU0bqO5qIKQ5ONh45k+AV877ivT ZSh+mdSAkSA0l0OopQqGMdxUuYaPSAA26TfesN+IyAXKbYkpUQlZxIbEI1nW0zM/ nze80zYfuNdry9ftLmKu1YY9Ox2ZSzfRbhsxjJK6g9cM19dUklD3QVYGMJaRnO+M LVh32kLiU1wxUwvumXP2RRefXTfU0xcsgy0oUSqeGKb+SVjOLwHWQLftVIxuNJFM 0p77nj8hlW9qN4HUAa7VLKGjtJzFgDjvyNnT6yb3AyZiHO2rgmNy8q7u2uoQDJ9D 6bFrfqM+Ab/9c9lKpnSkuMGRSkqgFxl30cNlUq1j0JhZ2gQmcRwIJy0s19cyDrho R6pd/yZSAzsc0e/4BlR3WXESy/ZXABSGOZdCyZl9rtgDFApLSUgGtKJ6xNRB0u9d CMquRGno5yvmh5shE4/f =z6Qq -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/e1xqmct-0003ye...@franck.debian.org
Accepted llvm-py 0.12.7-3~exp1 (source amd64) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 17 Nov 2014 14:16:23 +0100 Source: llvm-py Binary: python-llvm python-llvm-dbg Architecture: source amd64 Version: 0.12.7-3~exp1 Distribution: experimental Urgency: medium Maintainer: LLVM Packaging Team pkg-llvm-t...@lists.alioth.debian.org Changed-By: Sylvestre Ledru sylves...@debian.org Description: python-llvm - Python bindings for LLVM python-llvm-dbg - Python bindings for LLVM (debug mode) Closes: 759020 Changes: llvm-py (0.12.7-3~exp1) experimental; urgency=medium . * Fix the tag issue Thanks to Reiner Herrmann to digging into this issue (Closes: #759020) Checksums-Sha1: 74efd38d8c04ff2bb232237fbd2a026e9ffb29e7 2080 llvm-py_0.12.7-3~exp1.dsc 89917e2f06cf9d09906a90f11004262425abf0c6 5536 llvm-py_0.12.7-3~exp1.debian.tar.xz ac58bf80b73b65629365a2709696265431b3e3c5 551130 python-llvm_0.12.7-3~exp1_amd64.deb 882f5f2da9735c247ab57b902ede5a0cef67ba49 1424644 python-llvm-dbg_0.12.7-3~exp1_amd64.deb Checksums-Sha256: cf59b2f9cb9526187972a5bb22751aa4e29f0a0031cb8e6480e7e3b2782d2462 2080 llvm-py_0.12.7-3~exp1.dsc 00b126fff0c06f8b39b096b8adf127c9b6c1b30408b16a28c308306bbefd7fff 5536 llvm-py_0.12.7-3~exp1.debian.tar.xz 9f243e09d2c355284bd40d662c33e86059c9b1f01821eec50494dbe1196eb3fb 551130 python-llvm_0.12.7-3~exp1_amd64.deb 20c233a39402be27d1cf414172da637f5742fcff0aef969f5bc4c16e33571275 1424644 python-llvm-dbg_0.12.7-3~exp1_amd64.deb Files: 6e3aa5697b3de518ce418074ed3ccaf5 2080 python optional llvm-py_0.12.7-3~exp1.dsc 45fa942837e719bf34589075097699fb 5536 python optional llvm-py_0.12.7-3~exp1.debian.tar.xz d0f4baaca304c21fe0fd3bf8b9d66f29 551130 python optional python-llvm_0.12.7-3~exp1_amd64.deb 824a70a50b12375c3e1b211d474a57a7 1424644 debug extra python-llvm-dbg_0.12.7-3~exp1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUafdqAAoJEH5lKNp1Lxvhmk8P/0ICA7HFdPJhfNd0UKAuTRWo jwHQx772oklevgqR50FX/4jDL5+LQE4Wk5zHUJSw1lqz9b1a2G8UHouJRdZDMhaZ zyIkWDbGxS/6zZ3r1UW+fgA+lHn+yi1angsL7D1hg068NtYq1cqsr+oiJmSqZU/N olBrniv0FbXoiv/vqRL8gHJt3dEK9WJjGpetEA5jQoX1awSGuON3po7DLA45/duX xyZQP7aFViakAPa6YIyhLyl/Q/pt0UB0UPoHdEqpNWT7EZ0AuS15OTtTha17Gn4c dMC/WfW5ClRchyrqSFMV2nxqodl4Y3rPmg70gcRJf0BrNmPFuY3FupXuII5Gefgd vGoMgCzK5p12uaEYPEnWZSSbRBdNn6GmL02pa8R9XNmvCf6uOHjPFhwugmrbcwL1 5tjuJTWI42E2HMLR15L7yIkZk8zw8ngIJmaQkkajPys6qB04Hw/91Q6n8RKAlLSi RX/fNZAq4qc/enOBXyFvDuke58vVA8/tTISROl0SX1Cw/hm8rTc3zL+UJ/VVRPtB 0/tB2vZkGouNP19fPa86jGAPwtHFWYnv3DgNtt5q2ii5n71+T9FdNYLzipwm3aCk GI+pGRaT1Y4PKRi0AHR0OUC7CD8EUh8rd4D4baJ2WXe5NMnW6T34PwSdn08hYtbo sicD/LzP+gRrQyX8ZiZ8 =WWuU -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/e1xqmr5-0005c4...@franck.debian.org
Accepted grilo-plugins 0.2.13-3 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 17 Nov 2014 15:49:31 +0200 Source: grilo-plugins Binary: grilo-plugins-0.2 grilo-plugins-0.2-dbg Architecture: source amd64 Version: 0.2.13-3 Distribution: unstable Urgency: medium Maintainer: Alberto Garcia be...@igalia.com Changed-By: Alberto Garcia be...@igalia.com Description: grilo-plugins-0.2 - Framework for discovering and browsing media - Plugins grilo-plugins-0.2-dbg - Framework for discovering and browsing media - Plugin debugging s Changes: grilo-plugins (0.2.13-3) unstable; urgency=medium . * libgom is still not available in Debian, so let's use the bookmarks plugin from 0.2.12, which does not depend on it. - old-bookmarks-plugin.patch: bring back the old code. - debian/control: add the plugin name to the package description. Checksums-Sha1: 094abae01c70510bde699fd8f30ca98b179dd2dd 2295 grilo-plugins_0.2.13-3.dsc 5792f69398e1bb91e386ada828bd26323c86a9e6 12200 grilo-plugins_0.2.13-3.debian.tar.xz f2caedd81685a5cdcafbd4aaa72f31e2943a5803 457322 grilo-plugins-0.2_0.2.13-3_amd64.deb d86d088507e8809adc312b17440d98ae0bbe92f4 866124 grilo-plugins-0.2-dbg_0.2.13-3_amd64.deb Checksums-Sha256: 5e44a4f6a1201a4b502c2285c33f7ec1528354a81dde475b10a4fe15b9707c85 2295 grilo-plugins_0.2.13-3.dsc 482bc53d2a3b32eb27db4108602839328381bf8ae9e4c5fdb6ea5cf62f97742d 12200 grilo-plugins_0.2.13-3.debian.tar.xz cad89edb4d48ec40f7a4dc6259673b1b4a56f91a31082c2195778f913baa9232 457322 grilo-plugins-0.2_0.2.13-3_amd64.deb 08d212dfd2c5fbe714fd760e85122c71e2b03229b2a403cb62794e7a43823f67 866124 grilo-plugins-0.2-dbg_0.2.13-3_amd64.deb Files: e938519b4ac3bb417f29c4a6a750d277 2295 libs optional grilo-plugins_0.2.13-3.dsc ff2fa1a3a7b3700824035e8aaa739374 12200 libs optional grilo-plugins_0.2.13-3.debian.tar.xz 84c6052542f5c807b3f5b2f510be7aeb 457322 libs optional grilo-plugins-0.2_0.2.13-3_amd64.deb 953bb8313e7bfa7614e55ca33c6ac793 866124 debug extra grilo-plugins-0.2-dbg_0.2.13-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVGoLvL4yGa8+1BNBAQiN5w/+LYZkx5/gtwTTVbYBRINe6prjuQauOORp bsQywiMpI5IK4AOKOU+Myg1B+Rug42KyfA2EiPlSaKQ2gbdrP/f3vD2xMnvUi5Ug Crt82zLTxAFnPE3f5nEaoUz8Y0tz4ETS11xV5zu76TW+tPRXACJ/IrzM9xR5Voz4 dB8Yjpik0zXU+87MKz8Wcr9mOIF1r2W4mic/OrNdXe6Xo8/Ds+7mwFR/+yIh5YyD OTsNC1Bn7HmUlND4J3nU0/GKaTHvv3z5BlmkfJrlww70ktdlwdkINB0ZbgBaGLTp eNWDW4yfvz5ZDdUCESUolGLBnQxSYk6jwAg8j/dwzTIg+AfztUL41lXdDuB+Q9Et Zlznsa9kqsdpvUJmjMdOEk2HA4FHuef/S8ferdouFyHKrD1Zw5zs++hqJWrf01jP BI/JAyNcXD6Q7d4lsP9X6ClTPXPWmiDetED5wjzzACUyMImGf01/FvHcoWq4eObS d/2t+TC5mwe2E4i6/JWTqCV73Gge4GQCqquw0utmLwN/SM0e4YAj4c8VxZT74h7V DRK1ut2tATsqNr3AI9uE7sJHBImK/PdVQ815W7zHYJA44xdvKvrh/6dQ02CbhH6q rmzcENDg6mVYlsDdLRJliA5JiE1ACNF3/5fOiJkvl6+wxgEIf73T+y/gVhnLCM68 nocXTbe4ENE= =cJuH -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/e1xqo5e-00024s...@franck.debian.org
Accepted grokevt 0.4.1-8 (source all) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014 11:42:10 -0200 Source: grokevt Binary: grokevt Architecture: source all Version: 0.4.1-8 Distribution: experimental Urgency: medium Maintainer: Debian Forensics forensics-de...@lists.alioth.debian.org Changed-By: Joao Eriberto Mota Filho eribe...@debian.org Description: grokevt- scripts for reading Microsoft Windows event log files Changes: grokevt (0.4.1-8) experimental; urgency=medium . * Team upload. * Bumped Standards-Version to 3.9.6. * debian/control: - Added python as build dependency. - Improved the long description. - Replaced the obsolete python-support by dh-python. * debian/rules: added python2 as helper. * debian/watch: added new tracking rules. Checksums-Sha1: 08101a0a3a56bf89d383ba3b6d59435da3ca2499 1910 grokevt_0.4.1-8.dsc a2fd176411d6d3dcfcb5b611c7fac5a0f107df07 3242 grokevt_0.4.1-8.diff.gz 3c29d820322973d17ed6964831550d86c02eae1b 34166 grokevt_0.4.1-8_all.deb Checksums-Sha256: 53a8b79a98d2204ad260c49fa269d44f5dc8786fe9698e57857692dfb0ad7eff 1910 grokevt_0.4.1-8.dsc aa05e83675b9653bebd87783ad365a35404e73a32a3514669c95653bcb815714 3242 grokevt_0.4.1-8.diff.gz 1ecf1c05d30b56d05e7be0288d227c04ba4c57eb21a1850fac42567b6736eeb5 34166 grokevt_0.4.1-8_all.deb Files: af9fbcb43f8553f2c7f441d56b6747e7 1910 utils optional grokevt_0.4.1-8.dsc 3a0ddb45267260f09479a3ced3937ea4 3242 utils optional grokevt_0.4.1-8.diff.gz 9e5b9b7363b90417cde1999cc15fd079 34166 utils optional grokevt_0.4.1-8_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUaf55AAoJEN5juccE6+nvcFAP/iupQZ2U242OkV6p25HbUYVt R1pei8tD+sAsGR3YfiUDteLIf54nQY1VcvGzsLWBM18/taFQq+8f+7ilgaIzlWif lfVqmCh+7grOO1MfUBk3rJBLlrcfA/QgHzv2v6hNFCbCBmA8XrNSi4pdOk4XfUkL WFF+PRugz5BybjewnWG0ZXeQjsYbRcy/7S9uRrwkZ2DhS2Hr0CEq5Sd82nKNQrxN vfjiZhJHqss8eiWj3eEJ0ra2dV8ZtyrMyECAHCND0hXIeKE6zfg0+vKfaoVw5SzT ZhSIwIrfTxfya/4FYiF3cByrx5cCW5uCY20gHkJTQ6W34h2MZ5H9lWBIAegzLDx8 LCAix/JDHcnxBAR4vmj/FFuqsMfbj23wevIinJB6wtEiNVyCiH5ImTVP5Wsgtw2Y 4/Tp4N/KnPLIhV3OwYZj6piMWsh/rl2XTLi7kmx0Rdez+UIbhGuYHqhQdymrL5Fr R3glfjk9bDaYnYzCNd3qE+UUadaDDs7gs5a81eryTeFPujAslqOkT/bCvoj0+Buw SCsMedYoQS+5cyd1LPW5coG6XUvo3843aQWWyG7lh9N5fsKi9XWWM+UBEjnHLW2o HB2No5vfjbGimDBd3ZdKN5aEDkX3v6w1Ntrn7qHQHCGH3DJ7iUDQdGcvAh3TDUpK 5Ifni0tIYkBAZe0eWUZ6 =G6Aa -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/e1xqo5k-00026b...@franck.debian.org
Accepted libapache-mod-jk 1:1.2.37-4 (source amd64 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014 14:52:23 +0100 Source: libapache-mod-jk Binary: libapache2-mod-jk libapache-mod-jk-doc Architecture: source amd64 all Version: 1:1.2.37-4 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: Emmanuel Bourg ebo...@apache.org Description: libapache-mod-jk-doc - Documentation of libapache2-mod-jk package libapache2-mod-jk - Apache 2 connector for the Tomcat Java servlet engine Closes: 759624 Changes: libapache-mod-jk (1:1.2.37-4) unstable; urgency=medium . * Team upload. * Switched to tomcat8 (Closes: #759624) * Standards-Version updated to 3.9.6 (no changes) Checksums-Sha1: 49fac6ca3b2311c11d38af3db9a8452f4bbe9f10 2164 libapache-mod-jk_1.2.37-4.dsc 302eca9017ab8bf5f7cc6d99e11b41a9748165f0 9244 libapache-mod-jk_1.2.37-4.debian.tar.xz 121629f1ef0a168d647315a8a004d30aacda1ec6 152710 libapache2-mod-jk_1.2.37-4_amd64.deb cac27e134e138ceec01becfc041430750f8c7527 167142 libapache-mod-jk-doc_1.2.37-4_all.deb Checksums-Sha256: fe44887fb8a79eddad8aa5008ecffa022e3d549b9c805237fa00875ad91bb2b3 2164 libapache-mod-jk_1.2.37-4.dsc b740fe2af05a18eae14a881b8cf62562baaea35a9313b7283a00817ee337ebd3 9244 libapache-mod-jk_1.2.37-4.debian.tar.xz e25428235f5b91f038eba861ba5ced1b20ecacf45568fc50f1f450333b4c5e2b 152710 libapache2-mod-jk_1.2.37-4_amd64.deb 8ae514dcde691c05d2a299a97ecdc62a5fb976f0a744b919cde4a962330adec1 167142 libapache-mod-jk-doc_1.2.37-4_all.deb Files: 9c3cf5e114630a8e81c8f2202666036e 2164 httpd optional libapache-mod-jk_1.2.37-4.dsc 32cbdb896ac1e45a3c96cd1c838c1ba4 9244 httpd optional libapache-mod-jk_1.2.37-4.debian.tar.xz d4cdbab3946e3ffaadaeb604baa92718 152710 httpd optional libapache2-mod-jk_1.2.37-4_amd64.deb 4584f8401a527aefccaf2aec9a23f00d 167142 doc optional libapache-mod-jk-doc_1.2.37-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUaf+iAAoJEPUTxBnkudCsbrYQAJEMMg2gvp4p+ixtHRNdepJs zihCN0sZeJ/ypMAlASTUot0ZBTw6fcw9qnaqm3ZtVuVvo2Zq3U/X8g3WS+7XRLnx Lm48S3eH6lfTxbN97t0iw0Au86Nm4kWT3iLySDU98jMQcX80vivCEjt4g44vlB61 3ClVqAticpyH2ujEH1/FNwCbE/+3IFWx8mKRiwe05ycK0tzTab1y4ijvCUsVLi5H 5DkpCAgzb5eVmQsMK7zWDbWKuGw4Y2CELzJv1XaWIMSULNaXp4HXo2dVe5dUj36p YU4TEYc89SQthnHfQJ88uM3nXFqOezyQzu/bBGciX5CD+UbJ6QgoQUy5ityn75DV b2cieZk3O+qOOmpz8lwR4ipye7MT0g0Kc+Om1bOE4y7HZL2aMjAYKrosrYwVhV0z FywJ1h483Ec12Qf8Vr+XL8S+DMTtLPey1f4bNQg/+fHP6ooQbdMjvzJvM56X7O/d Mj1uwYiXCDkyfT3pFsaeSpMg+wy3CzC71cy2vnxlQtQbK109wVj7taLpIDrTlfr3 e/yIK5F6+aUDHUZsyU4XkZrjaSM3qa6cm+RQfMcNogBjjcLNBkD3FlZoOpXDOsRX PglND39SbNJm1y7GDWM93iPURLzpCOpDMBCeXLeuvFgmmxi91Q4YOG7umT9+/0+w kysnSx3zWQUiINhMY5zo =UwP1 -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/e1xqo5t-00029z...@franck.debian.org
Accepted vnc4 4.1.1+X4.3.0-37.3 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014 11:47:55 +0100 Source: vnc4 Binary: vnc4server xvnc4viewer Architecture: source amd64 Version: 4.1.1+X4.3.0-37.3 Distribution: unstable Urgency: medium Maintainer: Ola Lundqvist o...@debian.org Changed-By: Benjamin Drung benjamin.dr...@profitbricks.com Description: vnc4server - Virtual network computing server software xvnc4viewer - Virtual network computing client software for X Closes: 769891 Changes: vnc4 (4.1.1+X4.3.0-37.3) unstable; urgency=medium . * Non-maintainer upload. * Strip vnc:// prefix from server name to support URIs (Closes: #769891) Checksums-Sha1: a21db92c42992d3bbcaec0068520b7486a7d9e8f 1801 vnc4_4.1.1+X4.3.0-37.3.dsc 64b7a6ac201657c79e2a05f01a18a656c4aa27bb 70239 vnc4_4.1.1+X4.3.0-37.3.diff.gz 745d26f74f6ab112daeeba5787b95e424df09296 1603356 vnc4server_4.1.1+X4.3.0-37.3_amd64.deb ca92812b2eacb843b57458c835daad5f87ecddc8 106522 xvnc4viewer_4.1.1+X4.3.0-37.3_amd64.deb Checksums-Sha256: cbeb3712a5f3e8b2b79f034961c10bed24eb7e79f05155a0894890ea0fe6b3e3 1801 vnc4_4.1.1+X4.3.0-37.3.dsc 2b519982eebcc37665ad9240cd79dfa48322134a691fd8f6ae46004a7c1e16f1 70239 vnc4_4.1.1+X4.3.0-37.3.diff.gz 25995aef97909e15040c4d2315bfa6ceb7d09fabcdc04afc39589c880c505302 1603356 vnc4server_4.1.1+X4.3.0-37.3_amd64.deb 9e3c4e0a7d540c12831ce19d1b14da87fccd42b21644a0f9cab782d58b96fba7 106522 xvnc4viewer_4.1.1+X4.3.0-37.3_amd64.deb Files: f8f1f5c8ef0a8a3910df0499b38604ff 1801 x11 optional vnc4_4.1.1+X4.3.0-37.3.dsc dc9aaa7de0abb4a88c4a33034bf0d5f5 70239 x11 optional vnc4_4.1.1+X4.3.0-37.3.diff.gz 963dbc72380143bb56e49d1c8fdac81f 1603356 x11 optional vnc4server_4.1.1+X4.3.0-37.3_amd64.deb ed67465d295e9c703f00492f0810c9f2 106522 net optional xvnc4viewer_4.1.1+X4.3.0-37.3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUagR8AAoJEN2M1aXejH56w1gP+gP3DPVHZTBzeRhkfk/LUYW0 KstVTt6yiGgRtHU43k2ms474312EHibcnQ/JGj7dwrkfWh7370wKIxlG4zqxMtdq VABrK8iupsmg+5bwQ8I5PAsbKQQo4FOUCymIHQk1/AQrNbdgCTCZcQw2Fq6fUQ7E ZUPlNjk297GIgeqt2tCfdPVbfJS+740Hz6W3jqyG6PK7+I4XFXZJWoSFu5xyl0pt qw2Y7YsImDf+nBahFdsJ9zm5gb9tGFXzXulG9S+G9PocKLRCYc77iMFukxstcLTl SAHhtUxiZu4C961eUH22IKaiqHTHLxgyIMpgUvRLAV0TNw/yBESZ7pyKVcvN9fRs YIc9dsraJtNLWqJLiKVNl5p9OoTbxkYFa3/por+yGAqKPGcUkLjQ0pZdloqHk9xF 8KqxQB/vmKn9lEznjhRiM78eLfP1QqRePevnT0ZsDrxXKacuBxEeHVU+ICYIWBF0 CPRyQW4H7qT905nnzjgyqIRqXm8P8gc7m9lu8PpD/Hj/YQXCFhDxa03Ij2eUGBDK aMrQy9MY77wfK9Rd1KgL2wPMs9Azk9kJ6cffNdUU8VRZkPtVLH7Zl0siew56ulbo NjStuKDDGVTH7TDgrK6HMG5aFyaSiU1mr38jmq6JeOoyGx4/LJ/VtuX/wUnWV0Ev ckWcPFTD939UXnK+0ufa =1I+F -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/e1xqo6a-0002nj...@franck.debian.org
Accepted quantlib 1.4.1-1 (source i386) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014 06:20:00 -0600 Source: quantlib Binary: libquantlib0 libquantlib0-dev quantlib-examples Architecture: source i386 Version: 1.4.1-1 Distribution: unstable Urgency: low Maintainer: Dirk Eddelbuettel e...@debian.org Changed-By: Dirk Eddelbuettel e...@debian.org Description: libquantlib0 - Quantitative Finance Library -- library package libquantlib0-dev - Quantitative Finance Library -- development package quantlib-examples - Quantitative Finance Library -- example binaries Changes: quantlib (1.4.1-1) unstable; urgency=low . * New upstream version released today . * debian/control: Update Standards-Version: to current version Checksums-Sha1: 1f6f3632edb88f8f0e89d27d60c204b07395f6bf 1883 quantlib_1.4.1-1.dsc ff7c6ceba736449335333e34d89140f861a17090 4766340 quantlib_1.4.1.orig.tar.gz 1201aeb7cdbb97dbd424540242509a15283273ef 13615 quantlib_1.4.1-1.diff.gz 8814e893422311f58e48df7fec81872ffa0fa2df 4472962 libquantlib0_1.4.1-1_i386.deb 7b8129feb5cb01c91d91df4df9bebd60d1e8d035 11957096 libquantlib0-dev_1.4.1-1_i386.deb e7480563b545bd7337584fd031a86082c8bcabfd 1029152 quantlib-examples_1.4.1-1_i386.deb Checksums-Sha256: 937fd36505424b5fdc33f96e70fb74b3a4daf6a537b6ba08d658acbc87e8bd92 1883 quantlib_1.4.1-1.dsc 47390ef0be86f034f4bc3e79b272b5d9cc3354472a175062c034c660fec64cbb 4766340 quantlib_1.4.1.orig.tar.gz c524c7ff308aa95a7756786afb928ffc8063dc69127757ec22b9fbb143f41544 13615 quantlib_1.4.1-1.diff.gz 17deedc797ab2f97407817a3c42f03ba451e077d138cc70889d0a28706e9ea69 4472962 libquantlib0_1.4.1-1_i386.deb 1c4deab828a6dcb7d15a0ed26628c4e4a82aaa69106b90eb98be9f0051c472e2 11957096 libquantlib0-dev_1.4.1-1_i386.deb 43ef0e847837d5cd044cd1cc184302a8a5d39e59879674bda373f40285255df8 1029152 quantlib-examples_1.4.1-1_i386.deb Files: 384cff5593cd289ed8f4ea4716f06aff 1883 libs optional quantlib_1.4.1-1.dsc 453aae7b601d250d91906c4b32c0a7c9 4766340 libs optional quantlib_1.4.1.orig.tar.gz aa7f0bb486a7c901b71badfe3cd905ae 13615 libs optional quantlib_1.4.1-1.diff.gz bc3b24e34575635649ea1e9a328d635f 4472962 libs optional libquantlib0_1.4.1-1_i386.deb 17e5abf04f66c58e6119bab2b521b7c0 11957096 libdevel optional libquantlib0-dev_1.4.1-1_i386.deb 3e8b64d508506f5f9f4e0525ab5e92c6 1029152 devel optional quantlib-examples_1.4.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVGoEpKFIn+KrmaIaAQLwnA//bfzpHCTcroKFEy6Ae0lO5YNkWvMTb9Z0 jlPVTqNRk/4Lr26UrmL0J3TjcwGN4DtHMfTC5ommMQXyeCSKU639Uy/R/kh1iYeF oD/3aiS1RdsBeWSlDRFXm63t4+A5kDYe9tqeTr+DlUt90uCE3Wii0wLE4I3SrzRi JDqgNnDFxj4jedU8piG+Ly+qQkuqKfJVNMJuUYnS1uC1Gp0vw/yeLLQoipsI5tmo t/ndsiIvY1aPexwoY5ihSMWWpPoHXJXWH/P/zPkQqw+fkAb9iohPVXOnP56gUs4h jw/3HzYivaNWmjMJ9nqQi3GOATYAMFwUEVogqt/lnPhb2y7pG5aSm0ccdOiduWzF t8idGmZ+wlY4bP9MF6wK9zD42JTDkc4KHoHH1/rw/2Bb1SR6E9cjt0gW+YRQqm3H TigHqjXpG1za9LY+uADwXavohPXOcIJm6nZAaMl4Yue9LgoUB2KXRekUa4QPx3XC m2mh3kCFe6WINqpqC0mVYNRltYPwIrCXJJOMWOmaunmath/CtL1z+x+m06SwxM9E FJytQ568BuqGXFQ4e02e938K6IQ0h5cNYvO3+B+Y5jU8bK5JHC2ims2I6H/FeSPF I6gcCg6QAEyZPovcH3Dju5ne8ujW22yBXdHEnLOokvga5HtRWCwXwbKeehxP8Ih4 mxg4oJ5n1DE= =ylgq -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/e1xqo6c-0002jn...@franck.debian.org
Accepted google-android-sdk-docs-installer 20.0.0.3 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 17 Nov 2014 15:43:51 +0100 Source: google-android-sdk-docs-installer Binary: google-android-sdk-docs-installer Architecture: source all Version: 20.0.0.3 Distribution: unstable Urgency: low Maintainer: Android tools Maintainer android-tools-de...@lists.alioth.debian.org Changed-By: Hans-Christoph Steiner h...@eds.org Description: google-android-sdk-docs-installer - Android SDK Documentation from Google Closes: 769809 Changes: google-android-sdk-docs-installer (20.0.0.3) unstable; urgency=low . * add missing Depends (Closes: #769809) * let dpkg handle base dirs (Closes: #769809) Checksums-Sha1: 1a66c32478271d33d3383eae2ae244561db32ca8 1972 google-android-sdk-docs-installer_20.0.0.3.dsc 158bb39ccfeec2c9f2a86a730498f93cc1ef6017 4656 google-android-sdk-docs-installer_20.0.0.3.tar.xz aa2a51577da9229c18cc41b6b0afae1e75d7c2c1 5166 google-android-sdk-docs-installer_20.0.0.3_all.deb Checksums-Sha256: 1466a9816e1f8924b4b4d7c72d1bff6c0bde6694b4064765416b05eda1031166 1972 google-android-sdk-docs-installer_20.0.0.3.dsc 68cf47fa385620506032e4bb74824822437a09f954274556a5f05901fc2fe7a5 4656 google-android-sdk-docs-installer_20.0.0.3.tar.xz 4678f99ebf61c7b7583b0bc73a274527bc65ad33a71c4af4d482dd3be788c744 5166 google-android-sdk-docs-installer_20.0.0.3_all.deb Files: c5c7529e8c592503849904544758ab8d 1972 contrib/devel optional google-android-sdk-docs-installer_20.0.0.3.dsc 76ba57e16611627f205de1d5e104f45e 4656 contrib/devel optional google-android-sdk-docs-installer_20.0.0.3.tar.xz 82ffdce7356d4151a24bb9ca12c16954 5166 contrib/devel optional google-android-sdk-docs-installer_20.0.0.3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: GPG for Android - https://guardianproject.info/code/gnupg/ iQIcBAEBCAAGBQJUahP4AAoJEJ8P5Yc3S76BcWIP/3YQp2aP0CtGiWfkxmKab+3y g53UumYE2fCvFhh+tyVizfw9mvtRjyPsgIhKLuyg1DnlkcHn2dQtpzDCHfTs91BP SyNOsH7e6qlUz/7N1OT+EAlytYLc+f7rw1cLt4AiVXuc+Bp7XFnel70AsztV2FtT RMHQQAR3VxifpL7CLJMIbYgENQh0tNgB8+NB/SU18Lwo9qjfdFHcQR2IHb9+xBcz p9h9oBDxz9y33xGpmTG14nin15PYMRjjkK3+GgctjwC0cuVSx+ePEt2TnDtCJzm4 /JiAWfaANRuQ6W8dGqFQQnvXAgWN2KVddv85X9cpEFr7M3kLJO925VzfeHpmkZGq +AH79TblRplvyj7AnR4e3LN5sONVVi/Y4nM8o14cT9zfBKGkwXeqn8B+WEgbT/0N gwMwyaxPk+eZACbwM06yxPz2awcXePS7wviFWzJN4NpMq4dz2dJTFLFL+EgY0lqr OmFnnbhSTmvxhCgOso7l+1kIK8zUhpoWI1eD+bxF154pTgpSzIdVqoAe6CBbXzGi 33mtFl2ewptxqK3baYZqb44C3jINQJ+9wHBd1St0GkVN2Tu7fx4za+4j/Lx+nF4j R9sTaxiQtx1r2Lut9wFJXvO0SZdscKaOqVWVaV5FyMVdYPQM7H7Ayk4f2bPrktAY Gyay9Ajgkh+jEt3hlb4S =8yxl -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/e1xqojc-0003zk...@franck.debian.org
Accepted ruby-activerecord-import 0.6.0-1 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 11 Nov 2014 17:29:28 +0530 Source: ruby-activerecord-import Binary: ruby-activerecord-import Architecture: source all Version: 0.6.0-1 Distribution: unstable Urgency: low Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Pirate Praveen prav...@debian.org Description: ruby-activerecord-import - Bulk-loading extension for ActiveRecord Closes: 702505 Changes: ruby-activerecord-import (0.6.0-1) unstable; urgency=low . * Initial release (Closes: #702505) Checksums-Sha1: 3140feef07a877e9fb49aea101f2bdda37e6455c 2171 ruby-activerecord-import_0.6.0-1.dsc 2f27305fb52589d40ed112b6651688e2cb0dfce0 29725 ruby-activerecord-import_0.6.0.orig.tar.gz 96bfbd4b8b06667db00c35618c0e40da04a976bc 3220 ruby-activerecord-import_0.6.0-1.debian.tar.xz cca41e51bc7e5914876907f5d1e9360b742b5ef5 14036 ruby-activerecord-import_0.6.0-1_all.deb Checksums-Sha256: 3fcd55c4a5ea40bdf55b437973e950d276837f253e26edf3eacf2a08afbcd540 2171 ruby-activerecord-import_0.6.0-1.dsc c489ee275d8646e2700c498874b878cd32c0238a83690963cbafff7350451200 29725 ruby-activerecord-import_0.6.0.orig.tar.gz 49d81b6dd5585d50aa3d5143421a912a0087f5edbf5655560b49ad3348be6106 3220 ruby-activerecord-import_0.6.0-1.debian.tar.xz 8b376f1a2b094d2960851ae8e877c15e6e030a538d861adeff5fff846f55cec4 14036 ruby-activerecord-import_0.6.0-1_all.deb Files: 3b130ff04e831be0cdb63fbc5ec2fcdb 14036 ruby optional ruby-activerecord-import_0.6.0-1_all.deb 2deb6f4f8128e14816359da135d498a0 2171 ruby optional ruby-activerecord-import_0.6.0-1.dsc 1ee91b42f0c01740033c9186b13b2845 29725 ruby optional ruby-activerecord-import_0.6.0.orig.tar.gz dae5192ed9b97f87aa52c4f2dc0a5e98 3220 ruby optional ruby-activerecord-import_0.6.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUYfqtAAoJEM4fnGdFEsIqH/YP/1ad4fWqDQ0nv3tBmGb7M8OM 4lQ0hCWThY8cGMxGIXqzutoF5Jhz5u0+d3uFsQkPsCRDSS9E8VIbjCIYWySUgK80 vD8Z6rxIpmttrBe+rzSKroRt1L2GIB6I0PW3gSAso/DkRsZnQ5aqb3S3VNt1z0KS VgWbdAt0GLxvd2O1KIH8i2ZL1tttnWiqFq1rkjXw/EJdpLItsh6gLUPv/A+k2f67 wPY0+66n0qAFpgD5dsk4x46oEKlWXgPbWEhMCTtg/80fDVUSPfOYPuIiPo3EciPV 4W/jn4givt0z/cm6aSIyXhVYT4DT4ftuJOSh9TtnMch+WHusn4wrH9On62OeI5Sj GL+kUUzDAM4Pctr7mpOabmrGsbUK0xiekolQoTtcz1eiksyazrPOR5LP265cHUUD NfALEQ6O9RUVKBg5Eq0ZgYsh63twyapK0pim5070BwhcscXyhBqLq3ly21JpESCR p97ey1NFbhDIK1VJsdQku3JFPKu8Yp+10d7Hss4zo0rYNEFhcbinQ1DpdtFwrHW8 2Eer1yYuNxFocM/3iRl1QQzixd8pJhKzeRhqzuTufDbyHLw7blOexwGPoD96K39I 6IzdETWRlMDlkMZE3k6KOxpILUKdaaVVKUcNl+MZQro6jausXFDYQ1Ui8AG0t+F0 Se/JFNBy/Bzxq9stoEhl =3dkW -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/e1xqoim-0006iy...@franck.debian.org
Accepted ruby-responders 2.0.2-1 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 13 Nov 2014 23:59:30 +0530 Source: ruby-responders Binary: ruby-responders Architecture: source all Version: 2.0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Balasankar C balasank...@autistici.org Description: ruby-responders - set of Rails responders to dry up your application Closes: 769622 Changes: ruby-responders (2.0.2-1) unstable; urgency=medium . * Initial release (Closes: #769622) Checksums-Sha1: 77d6a029fe124449b8bf7f8afb8ea0874d35ba08 2157 ruby-responders_2.0.2-1.dsc 4f4a086d17c47bc654ba95b8f5f39fad70c39623 22991 ruby-responders_2.0.2.orig.tar.gz 8be4042b5d1e268e9be13021db3acd458429fc1f 2712 ruby-responders_2.0.2-1.debian.tar.xz 8828205c06a138b9dd975577700d28c9f8102fbc 16394 ruby-responders_2.0.2-1_all.deb Checksums-Sha256: 762343a3ef5f3b6f137cd5e329ba75d4a723bd30805c8c61240d53b774655a31 2157 ruby-responders_2.0.2-1.dsc a748002138da9853603c8354995a4193efa3aa25645b85579cb8329f5ad7833c 22991 ruby-responders_2.0.2.orig.tar.gz 7a18723622d74d9c1115483324587c23f45276ce2ed6d65c05a45faaea5ed304 2712 ruby-responders_2.0.2-1.debian.tar.xz 6f4167ef250adef23b473c209fe456577eeda14f8924127dcb30e46e150fd5e2 16394 ruby-responders_2.0.2-1_all.deb Files: 213cdec734de9ebd4c2baf0e5141cea5 16394 ruby optional ruby-responders_2.0.2-1_all.deb 387cdef58728ef22f484563f63e7cb7c 2157 ruby optional ruby-responders_2.0.2-1.dsc 39e77c961d47da5cd48abe2ab45c6789 22991 ruby optional ruby-responders_2.0.2.orig.tar.gz 5a089758fc60da913fe267a4d3ac1316 2712 ruby optional ruby-responders_2.0.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUad3bAAoJEM4fnGdFEsIqiw0P/AltZn+LkrkskUJ9sUNQ10VG +ezOGghk+PJYCOyeE7sgGNY4RfQ0NJfYttzJWXPbo6Y5MuvFz+ZmDtB9B4bqwrhF Uz3Egw10WemIbGaP/lBwWWDYKM3zKvF3jxvVNF2hPZxn4SnTfO3OgdB2yu4nkpu/ BbArcRclKtHj0LdoMhovqv5jZf+oTVxoTofm+404xzO4I2QoykODgOUo6vcdGxbu enP39qlPFbhrC+UjO3T/GVQ7hqk8Nwir2BVI1NF7R61q+f9cxw05VcDktcGSxqWw FmxIuzSAFUBZBtt3SKDhglMsbHCBlgj+iA6ISiYYkoMspGE5Up8FO2HLjNZ+E8BP 03L/TMyUBRYD/N/Q1SbvHjUK4qK0j4uHhzU4/P6wu9cR/W7niF/rEp0e/cKMsIRE 1M3dDNFbhS+LyAoY9mnaeqUVJOdVOwNLY787ygIkREUTRUW2549Sx83/TggOwsZS zmDQ4/lbp7Klh6CkgS0r+tIkOa7pdQtVwDB1Xp3Oekdw06CMylLVKPOYFBSB7k8N 3KMbcgKutbwLRk47B0h741nNcZHOdFBLHUJrHpsTM4qj7gUpv2wXecd8yeCvD9qt T/mehgKaYP+PHCi+g7m5ZebxoWPb1fyTYLmBhHzgj7/eMdMnDsjJeqLNwT6svm08 h3YgIbyvjNbvFwAsW9U3 =j208 -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/e1xqoin-0006jw...@franck.debian.org
Accepted r-omegahat-xmlrpc 0.3-0-1 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 07 Nov 2014 21:17:36 -0600 Source: r-omegahat-xmlrpc Binary: r-omegahat-xmlrpc Architecture: source all Version: 0.3-0-1 Distribution: unstable Urgency: low Maintainer: Dirk Eddelbuettel e...@debian.org Changed-By: Dirk Eddelbuettel e...@debian.org Description: r-omegahat-xmlrpc - GNU R package for Remote Procedure Calls via XML Closes: 768523 Changes: r-omegahat-xmlrpc (0.3-0-1) unstable; urgency=low . * Initial Debian release (Closes: #768523) Checksums-Sha1: b1b42edb8afca75fc96d7761639f6fad8c340744 1789 r-omegahat-xmlrpc_0.3-0-1.dsc 429c75de84f324168fcc855de1aa890f2259ef24 6636 r-omegahat-xmlrpc_0.3-0.orig.tar.gz eb3120e6bb2342a358389b7048404b107adbdeeb 1990 r-omegahat-xmlrpc_0.3-0-1.diff.gz 0377b290b0ae30a04083b701a3949dced76e81c5 47966 r-omegahat-xmlrpc_0.3-0-1_all.deb Checksums-Sha256: 4af39cd108576b15f42f8a0ebad0ac29119f41a9357ca94b5be97161ecf1a0de 1789 r-omegahat-xmlrpc_0.3-0-1.dsc e84bd51532891b7845b5866025f7da84358f29297530f44208b73903cb6f9824 6636 r-omegahat-xmlrpc_0.3-0.orig.tar.gz 6ad27e4351352db8832b81564250771fc8e086eb93589c461de209cdef886efa 1990 r-omegahat-xmlrpc_0.3-0-1.diff.gz b3049218ac003a461aefacf31324a33e71c1428fe5328ffaa82161698cbcd1c9 47966 r-omegahat-xmlrpc_0.3-0-1_all.deb Files: 3b3a4979cceee44ea2bc40b243a71041 1789 gnu-r optional r-omegahat-xmlrpc_0.3-0-1.dsc 75b8cf5f2240389b36aa04bbd72cdcb7 6636 gnu-r optional r-omegahat-xmlrpc_0.3-0.orig.tar.gz 23c587e1ec96a0f2b5f7b7d6a632ae4a 1990 gnu-r optional r-omegahat-xmlrpc_0.3-0-1.diff.gz 4a9bc29077973a3412f02a9c502ecb23 47966 gnu-r optional r-omegahat-xmlrpc_0.3-0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBVF2Le6FIn+KrmaIaAQJZfRAAhKN8jM3kHIWrMDrqPhYAOTs2/tUGuRtK bSMKQvPSfrR0i/5MVCIoLmkr0siAI2ollRKgWjAB6yfWGF5uVbePos+EB+knW8rD O6c3a0beXh2HtVZ5PLlYxqGhhCOoxosPjf/TjUTmUMa9Pvphr70R19sk5FuUlFQx jq8d2fWVQHp5oIyXeuVERltqg+ThwLyS5sY6hMCZ3XL/ALwlJBy/4auuNxJhYFPv JYeYE5S6BfbADTXyIP3JQt+xtmjcWT/PvWhU8aoAQXM1E/ZiTELB+KVXYZqRaVpQ L7gz9ugnF6IAoTCXFsFFDx0b1lyQ4zz7PkHZuYDZphxThHuech45mlofbz4PZRCJ YKA5cE1/oCWJwPzrTtJiR6ZVIRHXlmrYjIq5RLayaPqqcJoIsp5flqWQ2PjSRV1j uX324TIqedW6Tp2OvO4yIZI/hVGUF2q4Ws7Y8EAd/DzMaAhYw0D1PZpvGRytlTF/ 3UUa7AauNPAd7GQywxSSWxExFMhBZwoJfwkQkWGZmrQabcCeFFkblacBcwZqhXg9 /VblSVGgkxdR1AxUNXVI7cUKm77klkzJ4j4JiPQNOyIvun+Ghx1bqHDcUsDpyog3 9FC/NAnJCUzObLmY2xJBeDGV2FMybZowl/mHhpHz+GNMi/qaWpMfbDwRxpAJ5gwW Rk/KSRAkZDc= =JQdn -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/e1xqoim-0006ib...@franck.debian.org
Accepted ruby-notifier 0.5.0-1 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 31 Oct 2014 21:41:53 +0530 Source: ruby-notifier Binary: ruby-notifier Architecture: source all Version: 0.5.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Balasankar C balasank...@autistici.org Description: ruby-notifier - send system notifications on several platforms Closes: 769373 Changes: ruby-notifier (0.5.0-1) unstable; urgency=medium . * Initial release (Closes: #769373) Checksums-Sha1: ced4d317a54acec733ed6fae3ba35f64b0715cdb 2078 ruby-notifier_0.5.0-1.dsc a72bd181cf1e4c8b08c4f5cd6baf883b79f5a76b 7542 ruby-notifier_0.5.0.orig.tar.gz 9a7f49efcb90de05f206b4d4aaea29ca542ec83f 2456 ruby-notifier_0.5.0-1.debian.tar.xz 9f3bbc90881d25ad906575372112a9c9023590a8 6930 ruby-notifier_0.5.0-1_all.deb Checksums-Sha256: 04d84e3d13894b1c96bb15e36cf516ce9d459a67c1b0030a0ebd78130ff14ee7 2078 ruby-notifier_0.5.0-1.dsc 4b0118cc0967301f4908fd49019081cf70826047fb75bea88d89896a6472ab29 7542 ruby-notifier_0.5.0.orig.tar.gz 198d494a090ea5d166c7c9a3c2f43e7369a7b73aff06c1e198bb65e727e891da 2456 ruby-notifier_0.5.0-1.debian.tar.xz 8533ee1d52c45871bafc2511a5f514de1a0b5120c2ad7c9211c43dd27c3ceafd 6930 ruby-notifier_0.5.0-1_all.deb Files: 068cbf91057d30ee8f0be63f22ac1c6f 6930 ruby optional ruby-notifier_0.5.0-1_all.deb c20caf3a05fee350faa57469f8acf107 2078 ruby optional ruby-notifier_0.5.0-1.dsc d0746981eb574735859df0c962357bf4 7542 ruby optional ruby-notifier_0.5.0.orig.tar.gz 51d45d58e51892960e4af04658a7c980 2456 ruby optional ruby-notifier_0.5.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUaeICAAoJEM4fnGdFEsIqy/8P/29lnkvX9y9oLKQriJUu8goB fVt1JPd9i9fi3mGOhlXI3cnZrpcdJZGBGpNgbGi76CnkJrmuAXvBITmHhCPJf0Yu cVPMV1JyHuuvTDYf6wCl/qOSArebtCon88BPJ1YvQ4vw+uiV4baGkxUamufUNEer 17g41JOdoYlv36oWYChoDJfkO0qXK+JsbTNutTnhKSNb4UYlREZuLO1kmjqkD3aa 6pxRhOnocQMaOB2t3Es8XbTquJvMIzZucW699csaqOgjhaUD6XlB2rPSWe78iZXd 12hGHRx0sOdebvQov+c1OmAjeVr7lHKdLOzMAgVB3DjAxLC4xRnjg1qvfXaXUUA8 SLzmg3LoQE9qjDZslXRV0JaA5CRa4RJLSOhWjHsEVKG3MtKMBzofQHmE1nLw7U9A vdUH7vSGdw5sqo0q6yxZC9wZokuFb9jDMZe4FPpKwGaX942NEMZYHDATb7w9iZdF QfiT0TGn35HhyPSImAjlZR1OjpvJdQneRtl7a+dtn2gL9NC8qvHMnjBpq6nUBG3d t//SijbtvOy+n4W+PAK3mKkPTIv6blb92yVWdRz3sWehnSiVD2O6s+FumZsSSMJY XyF/SjrTb867TXP/hllX+8dmvrwRuO4XwOrXqezmA6dr2HR3wx/Sh1WwX9xvCMKH AeZDJBSM8MMn9FeNVZkH =cqbH -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/e1xqoin-0006ji...@franck.debian.org
Accepted ruby-rails-admin 0.6.3~dfsg-1 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 10 Sep 2014 17:21:16 +0530 Source: ruby-rails-admin Binary: ruby-rails-admin Architecture: source all Version: 0.6.3~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Pirate Praveen prav...@debian.org Description: ruby-rails-admin - Admin for Rails Closes: 761059 Changes: ruby-rails-admin (0.6.3~dfsg-1) unstable; urgency=medium . * Initial release (Closes: #761059) Checksums-Sha1: b18654dfb3ea4c6224aa8b6c3a14e7d2d3da772d 2136 ruby-rails-admin_0.6.3~dfsg-1.dsc dccb1f0d6262f7a589801ab82bad7f42c44729a2 251219 ruby-rails-admin_0.6.3~dfsg.orig.tar.gz 90194bafb3415225d47d2c26f8cb7f58b6ee84f0 3232 ruby-rails-admin_0.6.3~dfsg-1.debian.tar.xz b90e540347fd960a34e94834dd22b9699e8d2a4a 50968 ruby-rails-admin_0.6.3~dfsg-1_all.deb Checksums-Sha256: e3b8eaee9ee2f538eb1bc72e2ffe27da87e514c99df8dc6152d2108e43110019 2136 ruby-rails-admin_0.6.3~dfsg-1.dsc fb3ae53726e5047b4e70d255377aa2857b6b2624a587e9757a7e61977ff101d2 251219 ruby-rails-admin_0.6.3~dfsg.orig.tar.gz 91c50a11a2f493f7444c16c047e14154e0a123fab8b35c056e78deeb11f2c1bb 3232 ruby-rails-admin_0.6.3~dfsg-1.debian.tar.xz 025323096ca816134cfca36d29a13b7c29dc26ac2871265fc2efcefedb66941d 50968 ruby-rails-admin_0.6.3~dfsg-1_all.deb Files: 6e4dbd73b4bcbcf4ae427ec20eca3348 50968 ruby optional ruby-rails-admin_0.6.3~dfsg-1_all.deb 3137de71e1e37336a7e164c79842a604 2136 ruby optional ruby-rails-admin_0.6.3~dfsg-1.dsc c89069540f77fe7537eacc8ae9e7cc1c 251219 ruby optional ruby-rails-admin_0.6.3~dfsg.orig.tar.gz a785f19fb81535b21f397368e3143084 3232 ruby optional ruby-rails-admin_0.6.3~dfsg-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUTkfSAAoJEM4fnGdFEsIqqKAQAIFJUrF61Zy/gBmNIirMS8Vt o6jchH7KFn/E4rNsh+HFBXBJUoP/UgL1qB00HRsrOVGOQ8sgvdYWXl8HM7Y66ZrC zOtOcqQVHJAaKHwB4AGJMOz1MkbeA98mngO1fm8jnZlvbZWNq3SIHk5JhidlkufV zgHm/A11Us2bNu4dyHLod+RYUbzE8MncwhTYW5wyZE1kGs/2RTXwDLLtEwRGsny5 RVXVBAKd0n3U+CaXOBvy1XPPbOoLIKYVrp0vYrsQCiE+QO67USbQ0EffSC7O+3CL AiKy7KCpSnXK96uCYmaknPNWBCHGV5SH8Id5sp/KLfgx5PCUJ1IzFMCuTbzC4eu+ VlC4gBaRxGchsm0JPBaYwz7D36/sEILrdahm/0KfKjkoFGBcIU7hPgq5wQnozN2g jvhudXsqREkZxMQFZi1jhLeaKdyLaD9uDU4c7AmlKYV+JPvCrFKBTMj9UNlcnlJ/ 3JBToDhCUOrh4IYIPdUKZBU9Cq1ZPFdk2PT7mFxB6gAiO+R77OpYn0EvwpO/z2Lz 9JcT/ilpjVVODaeZHL8iIJOtbGvGlBUTVeCcDLqOf/DeWCcfI4XJAfC/EMlb8TKq zo47VglwjIwQ1bxnXopJi9xVDh0iWUyPgZc7u2v/pJEvwcj12W3cFLAd4ouROeo1 gBsC2fq+gwzn76Q6oGHp =Lq19 -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/e1xqoin-0006jc...@franck.debian.org
Accepted libnet-dns-perl 0.81-2 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 17 Nov 2014 16:18:22 +0100 Source: libnet-dns-perl Binary: libnet-dns-perl Architecture: source amd64 Version: 0.81-2 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: libnet-dns-perl - Perform DNS queries from a Perl script Closes: 765327 Changes: libnet-dns-perl (0.81-2) unstable; urgency=medium . * Ignore link-local IPv6 resolvers (Closes: #765327) Checksums-Sha1: f8f5b6c8b31a24272d443220bb453cdce45c56b0 2240 libnet-dns-perl_0.81-2.dsc 5066e3a98866a64b2c378c37bed0c412d8669516 7464 libnet-dns-perl_0.81-2.debian.tar.xz 4242b5fd705d4b78c66c15cbd301b330e55054d4 331124 libnet-dns-perl_0.81-2_amd64.deb Checksums-Sha256: d22808d5aa074f138caa9bea8c4df4fce1ed74db6336f7fd203fe7469ef550e4 2240 libnet-dns-perl_0.81-2.dsc a797c5d6c2446142c820c2d47140390c9e8feb289d16ba7284673422b907ed58 7464 libnet-dns-perl_0.81-2.debian.tar.xz e4f48202bbd68822849495c0e6184de267e348e7f57f244114922f34d4732bfa 331124 libnet-dns-perl_0.81-2_amd64.deb Files: 4720e2d94a5f1e7f2a37190c3786 2240 perl optional libnet-dns-perl_0.81-2.dsc 97e71a35db8105039dc50fbb566df5f7 7464 perl optional libnet-dns-perl_0.81-2.debian.tar.xz 98d9cb41acff34c2081aa32df6d8b5bc 331124 perl optional libnet-dns-perl_0.81-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJUahy1XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHrXcP/ilAeD1cwtT51uCJMLEjoYV+ gYjt4+9cVPKflsGbyccTEf3sbc0taEYK109JMkAkOocmCXOTSikpQwg9SfUHeIoh npPHJrzxSzB3viy6I8VMAWFjh7BUVvf+2/NZ08OvVSWOivolXbMnl5hykpTe01GN 7FIe6WtLdnXSWY1Xz3q24i9S82WlirU97u7rye+0+XcA7NcgrEg7prJEUj0lEi/d AaVsRM61JCJTJ56voEJSqjyqOooKdXoR8rrJFOT4VRowlN3QD2lRSuBiMa8hnws+ Dfo7JkQOBRYHEr1Owj35Wa9l6JoD//vat9uN4iJfqdvakpW2kDLSjhDboxs37gAL Aim9cdaHQ88Q9uH7iQeEZb5G9sr9IZZorImEmwtPFwOv8Uzs37msZvNFFuaojZZe 6MRqaK9D6L8tZq8OXOni96Vpu+pFYJbx+XriOz7T+RtNk5KErh49JIr/JHY3Ytcp bCGrUIhs5J4o3b2NhBC4I1RiqTHkWExcQ1zZAajWWLk4iVbFAoSrJEaMOVndYVw/ QOuHcnnjUydFsOTml5vfmJrlncPO/r6Vx1mH+5UFHsmQsEUjwL5Tjh00iZ/uNAkV uFrht2PhDdAEtvNG67FnVCs78+16vS9w2NhkBWOviuRTCzG1nL79OBdzuVrYlQ7q VFA2Ai8wzKuJdFpiYZsp =0uQa -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/e1xqpfy-0002ly...@franck.debian.org
Accepted libgit2 0.21.2-2 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 16 Nov 2014 10:33:23 +0100 Source: libgit2 Binary: libgit2-dev libgit2-21 libgit2-dbg Architecture: source amd64 Version: 0.21.2-2 Distribution: unstable Urgency: medium Maintainer: Russell Sim russell@gmail.com Changed-By: Russell Sim russell@gmail.com Description: libgit2-21 - low-level Git library libgit2-dbg - libgit2 library and debugging symbols libgit2-dev - low-level Git library (development files) Closes: 768482 Changes: libgit2 (0.21.2-2) unstable; urgency=medium . * debian/control: Added missing dependencies. (Closes: #768482) Checksums-Sha1: 3a74ef4cbf3f85e8a94547ea9ab4271bc7fea929 2070 libgit2_0.21.2-2.dsc 1f1a205f0fe6233be9afdee5e3acfae16f8b055a 12076 libgit2_0.21.2-2.debian.tar.xz 5a06bab56b4cc44697255829433d4ef1b9822427 535416 libgit2-dev_0.21.2-2_amd64.deb 33b8c68314aee73a8bae290a7bba982f6feb1467 311562 libgit2-21_0.21.2-2_amd64.deb 06a39acd3cd3726d676ee0dc9fcd24f411bc6b88 1203674 libgit2-dbg_0.21.2-2_amd64.deb Checksums-Sha256: 39c4dbf538777a6b3fa37ed768b0f45a8683f1a93a89c04a52eb04ab2af0a6b6 2070 libgit2_0.21.2-2.dsc 1c6e9d56ab501bcc660148c713cd5e90b5a19f0ddfeb160edc0a309ef03a8a81 12076 libgit2_0.21.2-2.debian.tar.xz 2cfbb7437b32f26d94f844f790636357ad46c9fa19d5b96eb93b1e9d9bd5d71b 535416 libgit2-dev_0.21.2-2_amd64.deb 6c977cb55fa9da536d6402a356ddab5ababfe969e5f7a83867a1e8f4c01f47c1 311562 libgit2-21_0.21.2-2_amd64.deb 6a050804f9dc340fb5387d2a5883626eff4edfa5fd1173fadece4592fda5fa59 1203674 libgit2-dbg_0.21.2-2_amd64.deb Files: 1850509b6ad343f5218148f745e2a0b4 2070 libs extra libgit2_0.21.2-2.dsc 46deb7c2f8bceb757cf782311a974b2e 12076 libs extra libgit2_0.21.2-2.debian.tar.xz 2717b7b28250d3f9f726405e9b2942a8 535416 libdevel extra libgit2-dev_0.21.2-2_amd64.deb 217bdfd451565d64d005bee07cd4582a 311562 libs extra libgit2-21_0.21.2-2_amd64.deb f5dc497ca31c8f59093aefb01eaafdfa 1203674 debug extra libgit2-dbg_0.21.2-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUakEoAAoJEE5xYO1KyO4dMp4P/2bPdi0UgiTROKgWJsbA/HQi VVtquVufQuwTNVqRdENWQccw/AK/zCORMW/vK+ZGk3yszq9uViDwlT6a2daJqVep qIg152i9dvZtijnDn52dngMHq+CuZofB03lHgjTz7c95G5CyM65E7fE8yNBFtNro CFA9fGTNrAPx1hWGhNMNGXjATUw5IpW4fUGNu7cSUSPcfon20Un49aeOEbQ+xD9C aOOabZ6z5oDyhltQtGxKocMdtQChkNkqlmy8rxz+dE1oSRbhDwdry9C+U5HkHMzc n+qjdpXt7d5yIcvZ1SJ77tY0+oFKgoE+yVLRfvJb4oDdPyquyZFKFddBcbgkqU9x K2YXF7g7t2UTrRcdOwhS5ZslUFXs6aUB2X7F1BBNbC8v/idrwtjZEMkmbvTDRp4r j/x/d303o4wXbbs63DCBygL90dk6y7p9rjvoMFM3/rxstN8gm0gNTlRflmkB0Sg6 C8GOf8iKgQ5ZJYW1IESJTMKcuPmpIIl86KjLnYG25pHwACwhDXwwA0TnnDfs7v2U f5LsHw80I+5CBzmAXvjY5rp63ORrrl282vmWX4IpHF/a6v1PLN/VqDybAdoze+pY ifFUVdHxNEfK/S4EbOG7gcIMCVfMbK+4XehW+a6WR6mj4cgTQNjZqLEGxej8nyKZ qHH9clDUgtCeuExGE8WB =SWzx -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/e1xqrm0-h4...@franck.debian.org
Accepted reglookup 0.12.0-2 (source amd64) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014 15:39:30 -0200 Source: reglookup Binary: reglookup Architecture: source amd64 Version: 0.12.0-2 Distribution: experimental Urgency: medium Maintainer: Debian Forensics forensics-de...@lists.alioth.debian.org Changed-By: Joao Eriberto Mota Filho eribe...@debian.org Description: reglookup - utility to read and query Windows NT/2000/XP registry Changes: reglookup (0.12.0-2) experimental; urgency=medium . * Team upload. * Bumped Standards-Version to 3.9.6. * Migrated the packaging to DebSrc3.0 format. * Updated DH level to 9 to allow GCC hardening. * debian/patches/: added the fix-string-error, that fix an elementary error that causes a FTBFS with DH9. * debian/rules: added the flags to make command to provide GCC hardening. * debian/watch: - Added new tracking rules. - Removed the old (not working) rule. Checksums-Sha1: 63df199606c55db2e4b3427286b91195792daadc 1934 reglookup_0.12.0-2.dsc 1b50838846f915db3c7036b2de2f9157b65d5d98 3408 reglookup_0.12.0-2.debian.tar.xz bef631b00791173fb260f1c8b560ca05db9e7c79 63364 reglookup_0.12.0-2_amd64.deb Checksums-Sha256: 0e7a1ef9fc981ce3351838d45da024916c466048148d2e4d18bf0d01548e5438 1934 reglookup_0.12.0-2.dsc 3570836c940efd76178f944037a8db047c5214371c0cea6493844b2a337b0f9c 3408 reglookup_0.12.0-2.debian.tar.xz 87bd81685032d218003060a41e22925f73bead7d3767343458a15c996f06937a 63364 reglookup_0.12.0-2_amd64.deb Files: 707f30ae7ed27eb5e530acb4f4c61578 1934 utils optional reglookup_0.12.0-2.dsc aada3d44e4177e9ec4a879e5a62533c8 3408 utils optional reglookup_0.12.0-2.debian.tar.xz c83358313293e18d91888b2a9c5c9931 63364 utils optional reglookup_0.12.0-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUaj+0AAoJEN5juccE6+nvMFoQAJ0NDBLOH8iNNYn2BhEN+8dh nc3bXjGmVFFjc74XYvcz0t3TA4ZPzxfYisaeXwYgVFdF72I1eRwO/fGKJQH1yvSy b4oqSmUZg1kAxmwauOQYHH4ldw/7BkRJ1ctk3iWjH3PFDNQyYY73KD0R4gan6X2s 2kLVYoXEqCfU/si49Ec4pShOAQqVnUNYkXJAh3i1NVKwtDZk05p9wj0kCD1ssUNZ 7iDNfbXyzCpOlcEq/GjB6uHhHoYUdflF1O29e+aghJK/vBi4Pw6q0MtTLRRFP+8e MyzUhLvDEYvrHIr3xiwKcThxgcATx/Q4cD/h2tQhi+BEKiZxW0lvHm8ye+jElX2x qeX8vTUnujLqXEF2uKuHEu7bOiye2NA+pEId9ph0pAWfXhA1g3anXf4ga0DG/1sf EuOdLk0LjldQSz06RgSpen0Wfi8YZZuWE5GK9VGymXGtsBjjiR260/fGEZPaIo7m NXCSqIldJCsZ7antrJbapTdSW/SzSP9+oWSti/y3MW1Y+Z2ku2GYy+CDNfv5cOln t6av0fKK9AMtP9csKnkv0WbZIeLrOaLgMRYEzQ/yIioz0ukIEJ8hruEv4jybs1j6 4xs4T5J48VTSc79YM9a3ClDIRmiagQRPl4ltUIRnyJqFx368cq/tajYxWfucwP/S tyKS6pHFkEoZ0lYSpJQF =E2R7 -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/e1xqrma-jh...@franck.debian.org
Accepted python-pip 1.5.6-3 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 17 Nov 2014 11:18:13 -0800 Source: python-pip Binary: python-pip python3-pip python-pip-whl Architecture: source all Version: 1.5.6-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Stefano Rivera stefa...@debian.org Description: python-pip - alternative Python package installer python-pip-whl - alternative Python package installer python3-pip - alternative Python package installer - Python 3 version of the pa Closes: 751827 Changes: python-pip (1.5.6-3) unstable; urgency=medium . * Team upload. * Remove d/patches/format_egg_string.patch. This was worked around, upstream, in 1.0. And this patch now breaks pip uninstall in virtualenvs. (Closes: #751827) Checksums-Sha1: 08a1f26a77f86fabb67300732f670edde0a8d763 2339 python-pip_1.5.6-3.dsc fb012d019c2a2dfbf6f33a6984adb60a0de0f876 14716 python-pip_1.5.6-3.debian.tar.xz b94b158e9c5cd757c5cd9e8eb2d6057a60ac3753 113064 python-pip_1.5.6-3_all.deb 384de9f52307a38540874cab7ded9d96842d596f 96146 python3-pip_1.5.6-3_all.deb 7d13448e32e8f2e3b041c31b9521b8d1dcab2608 124854 python-pip-whl_1.5.6-3_all.deb Checksums-Sha256: 5748493dfb99a32bb236611ae7e6ee5e6548ac60162426b2a9467502af60649b 2339 python-pip_1.5.6-3.dsc c472e379391f56b956dde8183cf1662f48f142dc095a611e70e085fbd2af051b 14716 python-pip_1.5.6-3.debian.tar.xz aea59d05fffb18a534bb52f6be7abf0e85a9ef6f16f1d1de75c1bf47cb8ad35c 113064 python-pip_1.5.6-3_all.deb f13676eb8f14f539f60f5da5deabfe0e987ce445f2c2d1346b3e140dd522a5d9 96146 python3-pip_1.5.6-3_all.deb d58bd38e90d768275f7ca20b6fd16746ec528e1eda70364e310e3f03e97d230b 124854 python-pip-whl_1.5.6-3_all.deb Files: 3ebd8848d029a578f799d55cba82fb57 2339 python optional python-pip_1.5.6-3.dsc 2a8a5f2e9f32666006b44bfdb9339bf2 14716 python optional python-pip_1.5.6-3.debian.tar.xz 6407e3e69588d6609f242d88c9852336 113064 python optional python-pip_1.5.6-3_all.deb 8d7f40086d132fb9550b5f7289febe7f 96146 python optional python3-pip_1.5.6-3_all.deb 9159e30c26c4e60d55632057974a4506 124854 python optional python-pip-whl_1.5.6-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUakqvAAoJEACQ/CG1zRrM3kkP/iFpEBPt9ts5XQdbEh+eNUZB Yne4m5wYqb39LdT4+nba4ukNlK+Z8LXWV0wuH2Y6y7C8EWo6CN2W1NRDD4yr8k2n HMxQXasz1XphtJbniAF6yuJupX5gi2xL5yR534m0nBH95KD3RVITNoVdgFCrrn6m LBsreMd5p1RpxRdbdUWoMkJs4J8W2FfiQkse+pyNbiXdJYXC3aoDeut4mU0+pOIO +VUD5Cb9wdxGFNRZRt2/d/HSc9HqAEW5n2RB4ET48+G4kj+/s2KMei6bckPetEWh 9k8CC6ht4yDm5IJZfqvmdUo9eLwiRu4z5hyN6V6taRcvNGM70slhjxEA9CAxIbhd 2k9Y7AmKc4xwy0reawTBDdvFhfl/dZ99wR3NARyPc+i3E83jEuZ3R06Nzx6BXLaX UA15j/nliQCB9E6oy5YuUoYx0lf5Uzwdvgq4X4NYguoyIFUH+iiCHB7F8+Bptlq9 bxhHYr7uJaWKG0/XOKOGjK3u8Gs/s2aqX9oR7yDWi1g98Ey2HnH0zsU4XhmiCVVV u5UwR5/KK3+fH3NV9QC2zHph9aLEksOlRwnP4cLPUPNY2z/gppX+8Kn3uLriMIaw 4VvnXwj6W0FOavKrmBn7GA8L4EZHM+uOd4d/zaradV38HtPr/MEQWnZQ53b1gUN/ uE+YkC9IjnK0rDto28vQ =/8QM -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/e1xqs3b-00063e...@franck.debian.org
Accepted tvtime 1.0.2-13 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 17 Nov 2014 13:58:00 +0100 Source: tvtime Binary: tvtime Architecture: source Version: 1.0.2-13 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Guillem Jover guil...@debian.org Description: tvtime - television display application Closes: 738253 Changes: tvtime (1.0.2-13) unstable; urgency=low . * QA upload. * Switch ttf-freefont to fonts-freefont-ttf in Depends. Closes: #738253 * Assume that dpkg-statoverride exists and stop using absolute paths when calling it in maintainer scripts. Checksums-Sha1: 2217f8d37dbb838ca49b384ff363589b3e3011f2 1825 tvtime_1.0.2-13.dsc 6cf97759fcdb4e15f14b5503dcb3d5ac7d39d6fc 97088 tvtime_1.0.2-13.diff.gz Checksums-Sha256: 4c38041155d87ded2cb46f72886a054c291910502bd50a23602253592ac301f0 1825 tvtime_1.0.2-13.dsc 23d310f4886cd139956ffa71ca918f06ab3519516ff556c22b963b72d401e301 97088 tvtime_1.0.2-13.diff.gz Files: 89e0f3c9b924b48cf10e8fe406a2437a 1825 video optional tvtime_1.0.2-13.dsc 16d2acec5e45297b2e68d9119d7663cd 97088 video optional tvtime_1.0.2-13.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJUakn0AAoJELlyvz6krlejmjQQALNJiydYUDWKwfGU+EQvZLoh T8rFMwCp2cJzsRpz4X/2fBoCdMvQDQRdZkl9OkV2ZR00Lme/ImwNgNEkeiYXnkYm k+y3Gpbq6jA/US8wySG4pOi0Qwk4Ix74EutXtcJvC3GpWYjkrejY6nKl09kU3WMn /GNVcTQ6fwO0M1SoJo2rUMXH43p97yrsb6BBkPOFRq5K5qH8/OaqQusuoibS60FS yO3wmUuKz/9LTaheZWKivKscy6sWwBt+3SNd9Dyh6cXHAyxJzAsJHWSCu5+fcZQZ qSPax058kKg+4VrOipZfstA2MVOO7vH9JMZAfBKvuIGZqeSh5GvxLxTzfDzEG4X3 MOZ2hKeMBMzGBC8mVyMOBwDHf0LBb+r1dOeW5jWRWYvT4vrmyAIxkEN8pnBwCHxH KhvNw4CB7g0nKIFNNds4u1ahDiKpHkt7xxPhnXcn1011n3c/sSOF9WycIVpYPxK4 82S5c0WB3gWgPyUm/EAWjARZ/lvVIkIXiJtaVeJLO1/qm5SSu//I17cpINZF557a xGIXnR7bb2tOTr29T+x/guMvcpSkZy0nehUkEo17g0MF/DfPcwvNCbABb2a0FeDO XyEynNT8mf4FuBWTGswq5HkvbIyDvn3IVjf2NO6TQ1JWtWXTK0gnaPTYGEX5gkhP lBoJkUnK9O34fg+dTxsi =baBR -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/e1xqs3u-00067l...@franck.debian.org
Accepted tableau-parm 0.2.0-2 (source amd64) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014 16:52:10 -0200 Source: tableau-parm Binary: tableau-parm Architecture: source amd64 Version: 0.2.0-2 Distribution: experimental Urgency: medium Maintainer: Debian Forensics forensics-de...@lists.alioth.debian.org Changed-By: Joao Eriberto Mota Filho eribe...@debian.org Description: tableau-parm - tableau write-blocking bridge query/command utility Changes: tableau-parm (0.2.0-2) experimental; urgency=medium . * Team upload. * Bumped Standards-Version to 3.9.6. * Migrated the packaging to DebSrc3.0 format. * Updated DH level to 9. * debian/patches/: - 01-Makefile.patch: added flags to allow GCC hardening. - added the fix-string-error, that fix an elementary error that causes a FTBFS with DH9. * debian/rules: added the DEB_BUILD_MAINT_OPTIONS variable to fix the issues pointed by blhc. * debian/watch: added new tracking rules. Checksums-Sha1: 0e3b329ac50217543d3afc5cd2e172d2387549a9 1978 tableau-parm_0.2.0-2.dsc 688105f6c0271692f45f6d044958ee65f4f65afc 3340 tableau-parm_0.2.0-2.debian.tar.xz 0a25cc06deb7ec78c724e9d3c0513fd588383b97 10444 tableau-parm_0.2.0-2_amd64.deb Checksums-Sha256: 52f1d97269b3ab2bb9b4293f7ed68077d2e9482f03d52376c99cd881f183348d 1978 tableau-parm_0.2.0-2.dsc 06d12224e87a7a4558111d9e7ee46791798e02373712f64fdb6d898a93076266 3340 tableau-parm_0.2.0-2.debian.tar.xz 0cfcad6f8d54581c684fad8d7650b4626d969e26e357f96fd05ed101fdb9e522 10444 tableau-parm_0.2.0-2_amd64.deb Files: d924a589222fd918bcda664afc2c05bc 1978 admin optional tableau-parm_0.2.0-2.dsc 9465e39e3ecb36b99e4d5639040f040f 3340 admin optional tableau-parm_0.2.0-2.debian.tar.xz 41322e8212d7bf6410da035f2f785433 10444 admin optional tableau-parm_0.2.0-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUaknVAAoJEN5juccE6+nvOVMP/ibVVtnfatSdR4X9uERJlVOY iAzvtTY2aLDKVHoYBIEl/VTaxY63HpphmIj8bXwHnzDjyyHrww8SqjC9W3+KZj3o BBk5Rl/8gdZQ7O/rZe3ork5ADhfDSntR9dAS86DFZTjgUvqqJxaA5JF8vtzc4RkP mJkZamVt8lrknjn+L3D5thym+RwoAn0ls2QCNsSUCCRssFjirfFx2WlZVNvFAUl6 s+C1/5jEnWVuYVB2Cu1ooY1Eeo6swCqfpHKMCsNwhrzRV0Npv4/hQvbbm8evMmCn dz+vhpImwyKGFzcJtXdok/7IYx3clq6Xc0JWfkcaBSqiHGHIxC4OKzfhO84FkpoR /6oOaMpbPpgEZZJQikJcb1JAz7dtbU/cgqTTDoFuBHtl6iC5r5LO3rQWzqpBjicg TjKqhmifz14KB1FN5JDEapN4xXAJsz678Eczi3iiCoVXXZeplazVbQl91+RhIhn1 oNuCDSdT4KQqCsnBqFZ8QOsEtxlnGEwkUEFiYXfRvR3EK04wzwZinhu9LoHdrBr+ FhxvXihnH4LALqorV2bNreMoI2NHUY9X9VGwD7mDHBobtAqXqJz5vOXFqxtsfTcE Jx749WXXzao2cPuie7dHaoQORj8CRrRnRTkJKzVEgeAsk4kKdm1ZNRNVoKo/rzv3 wp7RYrQVnN3cQ9/zI+f9 =Hej0 -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/e1xqs3n-00066p...@franck.debian.org
Accepted ruby-actionpack-action-caching 1.1.1-3 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 17 Nov 2014 17:45:23 -0200 Source: ruby-actionpack-action-caching Binary: ruby-actionpack-action-caching Architecture: source all Version: 1.1.1-3 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-actionpack-action-caching - action caching for Action Pack Closes: 767842 Changes: ruby-actionpack-action-caching (1.1.1-3) unstable; urgency=medium . * Breaks/Replaces against ruby-actionpack-2.3, ruby-actionpack-3.2 to properly fix upgrades from wheezy (Closes: #767842). Checksums-Sha1: 445f394d36db114e1ed3a021e98c83cce9b22972 2295 ruby-actionpack-action-caching_1.1.1-3.dsc 8ff2f905520705eacdefb4631abc3708b3210b6c 2484 ruby-actionpack-action-caching_1.1.1-3.debian.tar.xz 7488ace076753996bb9fcfefe43e6122049235bf 8592 ruby-actionpack-action-caching_1.1.1-3_all.deb Checksums-Sha256: e4e338387dc3fb08a4faf7f408ce9055ca6fb9bb71396dd7fb578c62928def6f 2295 ruby-actionpack-action-caching_1.1.1-3.dsc 02e9cdc81119173da75e8c279615695e07d0c99410a32c5c3b07ade24d5c02b9 2484 ruby-actionpack-action-caching_1.1.1-3.debian.tar.xz 77493e07bad997043c639203f2176ebc704d467d0a1353e75d096cddd175d898 8592 ruby-actionpack-action-caching_1.1.1-3_all.deb Files: 930a7d1907827ab0be6b8f372905fd22 2295 ruby optional ruby-actionpack-action-caching_1.1.1-3.dsc d5d5a479eaa220fd437479192837095f 2484 ruby optional ruby-actionpack-action-caching_1.1.1-3.debian.tar.xz 794e5426b3bc175b8d584b01eaae3c28 8592 ruby optional ruby-actionpack-action-caching_1.1.1-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJUalFsAAoJEPwNsbvNRgve24AP/0fD74VOeoNOqfyJ5afMMdDi iTDHkKtgqVHUsU6Qh6n5sPaXM/zWMaOLCruEFBNdmj0NTrj4rTyDyl3W+I05qlS/ 0h4PCiSeRVqHRYiUdtZtts1vRbrukhEq78dRUDxBM65bElFWSQORFL+OzDf1FpuY y0FbBIOc9nJsHS2FmeZ1BO2sj1spY49ib9utI0XLdlfaag+FjIaRuEnNXHn8DV1y BMotFgA5jDYa103OBakdiHhWpfDU81GvIhMUACAgAhYNNWI0nIDID8fbyIJ66mwF aDFgB8Kqg60QdGc0NBQUeV+/tBiFyM2MjcBBddohEahm6L6n93euHBaPIeiutNkT fnbPSQiCA/YGHP/+bIj5VtN+qcqDZGAzWNt0AR+9nYhmY37Dm917vwQEALFprqFm OseW9rTO3BwPu1mKaSm+3AJ4R+72PWQLdib6HpwI7nknYdmD999RSzUoWNVdw7YV sFb5PpDKudkBys3tSCrbYcs3H4XcUme+5BrfJgBTocWWk8Wfxmj9mQjVOrj/8Us8 LXcwv5Qy6Qx58YtPW2ND5lp1EEjOwLPSZVh0ACL8p4zPxI4Du+rCML/yz05iq5/b dC/YYIwxNTAkPvwqjvZ/E3PJJXGe+DZKGcuSBCrad1LRPFZJTFDS/Mn/2siAMKF5 jBT7iR84vzXHCAB2Lytn =ln+7 -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/e1xqthb-00028s...@franck.debian.org
Accepted startupmanager 1.9.13-8 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 17 Nov 2014 20:52:00 +0100 Source: startupmanager Binary: startupmanager Architecture: source all Version: 1.9.13-8 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Guillem Jover guil...@debian.org Description: startupmanager - Grub, Usplash and Splash screen configuration Changes: startupmanager (1.9.13-8) unstable; urgency=low . * QA upload. * Do not use an absolute path when calling update-alternatives. Checksums-Sha1: 37fa1f5245c77e36586b889e12e8d6784ef592a7 1818 startupmanager_1.9.13-8.dsc 6f43cf468c8250cc166daae176bc2f4ac6013ad0 4459 startupmanager_1.9.13-8.diff.gz 7181a546ebd87ab8c3b7cec285bdaeb68787414e 87994 startupmanager_1.9.13-8_all.deb Checksums-Sha256: 8eefc1b2185e9b9252d9161d8465e91504160bd9270263682965b7bb757375ec 1818 startupmanager_1.9.13-8.dsc 0217cc18b1f7d19faa800bd43930db2afcde589c1ffea8d281232fe061b1cdfa 4459 startupmanager_1.9.13-8.diff.gz e88a12a6b08d9a14d45c154f03ff0b4dae337f3fa30a0bb64954bb4d85bf4d72 87994 startupmanager_1.9.13-8_all.deb Files: 45bf2bda0d1f14757f9e9335826d6903 1818 utils optional startupmanager_1.9.13-8.dsc 136e61d1c198ee4d1a043881ab128de6 4459 utils optional startupmanager_1.9.13-8.diff.gz cb05e75908ae988ce04ba5f8091e6ccf 87994 utils optional startupmanager_1.9.13-8_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJUamDlAAoJELlyvz6krlej8b0QAJiZfVGGgeAeawoRpsnUaiaj BnOX4/yKePN94WcRnRVDHSiPVTzJcAPl37EnXERx7XRBLG4nDa4zYLVVqHYEkxLd nnkj8dOBc4k48ZF+vcCEajO+kXIuvHdinD8ZQwSAsXvkHCGwc+fYlIn9QEgwfWwH ERL29RSnK2Bzh7DtnzeX+U1uO6jBit04NxD0I1CklzfLB4e5kX9qYMaJy81Luj7E rhkMYl2+JeoHQAVqdZoFT6yBFxS3Rg4mj+l/aoOpGT5jWgUFN+ny4/SGcxZnEAZu oh4sI8DhCgk9zZ4cKNBzR9UhHmEvZC67YrA8WiOW4uPEsy/pKQZ1fnFEriIf8dEC W/up8/mwP8oxZb/uZJ4P5Xlm+gnKZjxG2lKT31WULHZ069Hz8yGIfWG2R46xS4R3 AJqN565dLigBiQC4j5N4QMGjr9pgJdIYS/s6ZmtK1EqXSyZSI4fEnnqgOCdpPp1f Bsn93EIRz9eCON3ZgCC077BBFEKhsXPYUvdGRNx6HMfqF7umo+VLAZ8wrOUolCN4 z1WI7ACRSDevw7Nm+ek0hfcf/sh+lrIVBK5piJIVGtNwb6xDfc6tRNpxlk03AcpX kIrrGutLZvCG4KpVzb3mzLqkISo2aZv9EXjdOwcRR+VugUFsCQQNVUFC99PeJcw6 2Mmmc+TSqzT+ibBeEoGN =VUHv -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/e1xqthi-0002ar...@franck.debian.org
Accepted zope.interface 4.1.1-3 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 17 Nov 2014 13:48:08 -0500
Source: zope.interface
Binary: python-zope.interface python-zope.interface-dbg python3-zope.interface
python3-zope.interface-dbg
Architecture: source amd64
Version: 4.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian/Ubuntu Zope Team
pkg-zope-develop...@lists.alioth.debian.org
Changed-By: Barry Warsaw ba...@debian.org
Description:
python-zope.interface - Interfaces for Python
python-zope.interface-dbg - Interfaces for Python (debug extension)
python3-zope.interface - Interfaces for Python3
python3-zope.interface-dbg - Interfaces for Python3 (debug extension)
Closes: 768286
Changes:
zope.interface (4.1.1-3) unstable; urgency=medium
.
* Added d/python{,3}-zope.interface-dbg.maintscript so that the switch
from symlinks to directories in /usr/share/doc is done correctly.
Removed d/python-zope.interface-dbg.postinst which was an incomplete
way of doing this. (Closes: #768286)
* d/control: Added Pre-Depends to -dbg packages for .maintscript to
work properly.
Checksums-Sha1:
90dba9289e3f9715da36fdfe0e4f251c932df68d 2495 zope.interface_4.1.1-3.dsc
2304683c9201b494a0ae3ba3d630371d882f2465 5128
zope.interface_4.1.1-3.debian.tar.xz
2d50517f67ec18b9179462bf37a17aed0571704b 85510
python-zope.interface_4.1.1-3_amd64.deb
fffe7fc2fd5d4ca77d5dd8f7d827bc346c01c902 14778
python-zope.interface-dbg_4.1.1-3_amd64.deb
f49d2cfb40baf67f2b8a620c78b67811f51ec645 85624
python3-zope.interface_4.1.1-3_amd64.deb
eb65f56518156418813ce1483a310bffeaa62161 14782
python3-zope.interface-dbg_4.1.1-3_amd64.deb
Checksums-Sha256:
c597a349fe250dad8d64793d31cbc93e9a662bdfb9b61c29ff4da80413f64a7c 2495
zope.interface_4.1.1-3.dsc
3ae2048dc0b207136262f6256105c2465257d0442a0ce4580771b7b8266f151f 5128
zope.interface_4.1.1-3.debian.tar.xz
71778c058cb61c8362585436dab212eb5b12c928d5b8a17c09d0e4257559d0ca 85510
python-zope.interface_4.1.1-3_amd64.deb
ee7960595bcf4f7e361006cb4434b2c311361f689182b72be6912dd73e99650c 14778
python-zope.interface-dbg_4.1.1-3_amd64.deb
782c5605440abb6cb583e0e3eeb63d5db6a92cc1a06ab6da1b0349cc6bd0e511 85624
python3-zope.interface_4.1.1-3_amd64.deb
4f8327e126fe6a2563a37278491d708c90cb4b86f8d7ae2838ef6aa7f373ea53 14782
python3-zope.interface-dbg_4.1.1-3_amd64.deb
Files:
766a4019ae11a64d97315d9846f5c469 2495 zope optional zope.interface_4.1.1-3.dsc
af7c3bbc13bb56e1621d01c96ba3a092 5128 zope optional
zope.interface_4.1.1-3.debian.tar.xz
0e1e0657031e4667ee96124873e261e0 85510 zope optional
python-zope.interface_4.1.1-3_amd64.deb
07c33b81d5f9a3ec45eec94f1517589a 14778 debug extra
python-zope.interface-dbg_4.1.1-3_amd64.deb
46b262959683976788ae00b893b3bd22 85624 zope optional
python3-zope.interface_4.1.1-3_amd64.deb
53c4894d0ba3e01a5fe203627327b161 14782 debug extra
python3-zope.interface-dbg_4.1.1-3_amd64.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCAAGBQJUalr3AAoJEBJutWOnSwa/62kQAJBLYN6O/P0OBv/AYVb+d5pI
BV0SBL3vTNCuwJbP2+Ui7xiDFC922LskvsDh+YLZWPJZOTr15gOTpqHReIS9BSpc
XZ53r3dpkbgp0eyIBJX0X8HqzTk/cwElaIdGvJr3huoA8vvNll8LlZco6dx1zmCp
OGfLaXGQmEPL4b4FOIFg/H3ax8Urx+5GOAkDuHe2A5++8ivkpEPj6gBHPhzesE8H
q+Ht58h0pFcTTIiOXzn0TaQfDSzXjfPJKf7JSGmd3u8hmPDV11vVNgyMPKsFRudV
6/aCHVdHXEUfaCoiMxpRF+HUyJirx7Tqmae0+y8BZMJUxANx4PgZS3zGHfERD/52
Z6ik8XT0dJeteCNHULmPbgOP2QPCgKaJWyKa6A073q/5ERa63uRRXjkUR6OP1Sxc
CnJxm8spZppB/DM9Lr5eAlnW7UIJpwtZVZPFNAbiTy9bCZViCVOpKWPtqiOUhsiY
LlC4NELHNr3B7/jMN/6JJ1U/X59WpM8idfjQczIKvpTt/uH00dGfV+fQXFnaXHEk
gghG6w2L+uEkFWUFwuGKDgOU0aKMx5WSAit5y1wxmFOWAuUsQOZvsnjRLZQOkL7E
7BvzYopnB/NVKxrenJQqVBnHZH+D1mlF412TRqZn+TogvNtjlln8t2AyPVYiuRdZ
95iqbcoMCB8pFi7g+DWF
=kRvS
-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/e1xqti3-0002i0...@franck.debian.org
Accepted android-permissions 0.2 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 17 Nov 2014 22:40:54 +0100 Source: android-permissions Binary: android-permissions Architecture: source all Version: 0.2 Distribution: unstable Urgency: low Maintainer: Android Tools android-tools-de...@lists.alioth.debian.org Changed-By: Hans-Christoph Steiner h...@eds.org Description: android-permissions - create gids that represent Android permissions Closes: 767677 Changes: android-permissions (0.2) unstable; urgency=low . * force all groups to use Android gid (Closes: #767677) * remove inode chroot check that is failing on Android Checksums-Sha1: 7a668b321eeb1406662dc5e0c827a98562150c9e 1758 android-permissions_0.2.dsc 192f925e5270fcf452e5c74a0a52ba85eb7fc015 11720 android-permissions_0.2.tar.xz f6ce6db539093509439f758c79ec1d93e60cb96b 7118 android-permissions_0.2_all.deb Checksums-Sha256: fcedc44cd2262afea27a6e2afb7645afb2c7f54e6260dd30643578953af63cb0 1758 android-permissions_0.2.dsc 1bf9a4afb5670d8a95515e95fa17a1e48140c04326f281260b1136b54cfd6236 11720 android-permissions_0.2.tar.xz 7e230732ebd8be2f55180565c5a50710fa3db33f69b6a43e64d90b3bde27f3ad 7118 android-permissions_0.2_all.deb Files: 01575d1019f7b702a68daf4d091055ff 1758 utils extra android-permissions_0.2.dsc 9c6e040986d30076c23dda46c23997af 11720 utils extra android-permissions_0.2.tar.xz 8f17550719eb6d4dfadc96361cc05dbb 7118 utils extra android-permissions_0.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: GPG for Android - https://guardianproject.info/code/gnupg/ iQIcBAEBCAAGBQJUam0sAAoJEJ8P5Yc3S76B6EgP/RcWzC+kjseBEIpunYRZJbWW KMuxZ3R3DalM2xK7i1ThY1OsEZzjcbt0xDYQGCFogvdCio6vooI3WlujOzsA4txo UALvBBf52pUJ/AVD1D3zKSMIi1CO9Jyu6pD6eHzDvIMWY7wIeXJpuTXShkyb59nN 6xvQ5ushPZlA3IvDLRTtr1v89F7kaaFXE0aTAHCX1ZdPDKidbMr6/etS3Vj0vvQA ITPKjXrb8XQ+TEhm+4lB2eHnSqwX9qUJMIGMmLaO8tWHixVXnoAFiw5WTWxdtmXM hoY4dFw5jXw9NGpP+xpUqCJPdXkrNUN/4y0wy+THzLB/vqGqH9lFmhW5Pqg+Hl8N gjPxH3RZr6xhFRoe9syCNDCKQ+Z/CqfFsu/HJOSDBTD3fwTjAVNt6HXT0xod0raC 2Y0LsoGjOEOUnKMDLdelxMO6skiecjFsmOnrsfNeMFJCunFiEYfEUlU1hsApPMA1 YjoAE3FejVmraWlaSOx8C2WOnT0huICPe8a8Y22DhPO7V0chbL1RO6H36RIY//LS CNyF6ytf8zvexZwBlRDawYdBAMQdmPVJoJmpbKT+WqlwIIRPogugaroGxRKBeE7P GUPGZUqQn6MzbkpTCAdBe9hNPfZliR2Zdpf2n8jeRHIBqVLG1EGNJg7QVhQiTRAC MuiZ7lNkB4ZupMSDfQz1 =NZQI -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/e1xquof-0007gk...@franck.debian.org
Accepted plymouth 0.9.0-9 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014 22:42:50 +0100 Source: plymouth Binary: plymouth plymouth-x11 plymouth-dbg plymouth-dev plymouth-themes Architecture: source amd64 Version: 0.9.0-9 Distribution: unstable Urgency: medium Maintainer: Laurent Bigonville bi...@debian.org Changed-By: Sjoerd Simons sjo...@debian.org Description: plymouth - boot animation, logger and I/O multiplexer plymouth-dbg - boot animation, logger and I/O multiplexer - debug symbols plymouth-dev - boot animation, logger and I/O multiplexer - development files plymouth-themes - boot animation, logger and I/O multiplexer - themes plymouth-x11 - boot animation, logger and I/O multiplexer - X11 renderer and log Closes: 763276 767170 767937 768350 Changes: plymouth (0.9.0-9) unstable; urgency=medium . [ Laurent Bigonville ] * debian/control: Add a dependency against init-system-helpers as we are explicitly using deb-systemd-helper in the plymouth postinst script (Closes: #767937) * debian/local/plymouth.hook: Test if the plugin is present on disk before trying to copy it to the initramfs (Closes: #767170) * debian/control: Reword the package description. (Closes: #768350) Thanks to Justin B Rye justin.byam@gmail.com * debian/local/plymouth.hook: Properly copy .plymouth file into the initramfs for themes that are not shipping images, this should fix the tribar theme. . [ Sjoerd Simons ] * debian/patches/debian/patches/utils-Don-t-create-unix-sockets-non-blocking.patch: + Added. Don't open unix socket connections as non-blocking as the read function assume blocking sockets. Fixes plymouth failing to query the password from the user (Closes: #763276) Checksums-Sha1: 59fc50d5b29ad207da189019ae3eb4088922e2be 2295 plymouth_0.9.0-9.dsc 1bc09140061a6ed077540cd32025f4da6d094da7 24960 plymouth_0.9.0-9.debian.tar.xz 781fc36d3ba4a1f56a25e0e628f3830afdd254a2 188664 plymouth_0.9.0-9_amd64.deb e1bcd91606ec91db98babed1a26cdd195da6efa4 21230 plymouth-x11_0.9.0-9_amd64.deb 3cb40247c05a913d747c670765d49e652c110a86 572208 plymouth-dbg_0.9.0-9_amd64.deb c247d84d8acf00509eee22b977655ada0be4fd25 392754 plymouth-dev_0.9.0-9_amd64.deb 6f0d76d8836283a31c78b888608de5a9aeaf82e8 663512 plymouth-themes_0.9.0-9_amd64.deb Checksums-Sha256: 2cd8084ceac3e547ea957b4aac10954fcc3cc46d4db2ea0ce1680ec76466815a 2295 plymouth_0.9.0-9.dsc d80b6abc2f9b684872e76f2d2704595dc74ab7bcdb6728014557d50483ac330f 24960 plymouth_0.9.0-9.debian.tar.xz 34c05a04a352f2ecb99f9c6255caddd5602d41c96421eed3dcce425c05f2a399 188664 plymouth_0.9.0-9_amd64.deb a827a4cccef3916b87baf5009c109fd8eb005b1f86237695258dbd1b22dabe74 21230 plymouth-x11_0.9.0-9_amd64.deb 693a74b6aab8ebf32a14807405dda03a7ad5c072e3e7a233d658784c6a96a566 572208 plymouth-dbg_0.9.0-9_amd64.deb 1a7b7ecfba3bca8734de78b2716799cdeb25d07e31e9ed8fe07e85c2efeba837 392754 plymouth-dev_0.9.0-9_amd64.deb 47edb6143e0ded2464936377191f908f1c3c63b504ca57c33869bfee82e006ee 663512 plymouth-themes_0.9.0-9_amd64.deb Files: ef622d7903ff3f04728dc41f56d0a02e 2295 misc optional plymouth_0.9.0-9.dsc e7c37f2587853dd0ca0712573b5a04ca 24960 misc optional plymouth_0.9.0-9.debian.tar.xz d3f18c29caf351763b22f398cd69618e 188664 misc optional plymouth_0.9.0-9_amd64.deb a38eb11cb9a2c37f222693bf96541267 21230 misc optional plymouth-x11_0.9.0-9_amd64.deb 747acb9ec4519b363352c0046c0ded0a 572208 debug extra plymouth-dbg_0.9.0-9_amd64.deb 4f314de776d62e6371523c3b26e6c2e6 392754 misc optional plymouth-dev_0.9.0-9_amd64.deb c8488f278e6d50e8a9f9ad61e5dd044c 663512 misc optional plymouth-themes_0.9.0-9_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUamyIAAoJEMJ022TCMA97XoQP/Av9ufqj5uGSRDDs7FSQrJaC CN0K83cLsVZeFiHOE8v4SMjkDlDbCicXb80MAzSpI36D2xzWNnPM+qfdJADVM4LV sqigekSrzkBoAL/67i6CZ8TkwxYm89aRV9nyhBNNg1KlyhDKsWFEKLTc0I+5oyJZ epTob0mE5+D3BvL9/WCamYZd2u4ifikuHUZ4MRpd6AzLNSbsczdbN6lVbbdN9cuU 6EtiLK0t8dMB/055M6uDycYaUylL2BR7UnR8YcOZG1+F1rQii02dpH1tTxFNdCA/ eJQOT5OE+pd4L1aEDcG9NIhHR9g7jBJkjlW06yc+VdcVwo/AKogOAtm9hIDXWlXl PKDJAxwqlWB5TSxXu9LKkPogVxLhy+pxXvAlyJTVIj1gT3U4SHICrmc4PRNQPzBr 8qywJq24yJGd2LwfUNfM3MY1nEvUAfeOlvjcs9WsRlI38qLhRSeUHzhHP4NBp0jO 4ivO60mMAkcLsjFkUuHHE07eyDESGD9HcFUU0QcpMRo8egxRhg7cnhJ4y6uXixpE WXqfprMVYELC/wb4xyldUt0UmKMj/nYyAM3E79uvgmQDfHfTTcSQkE975WVPmQxC 0sAETkFLIHDmrdhZYWSySKbnhykcDcka0zsC3T/Po5qikt4oVI9gZephEjkaQmb9 QVljIFZQEhRQ60Th8Ed8 =WdMd -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/e1xquoq-0007pz...@franck.debian.org
Accepted pyvorbis 1.5-4 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014 22:36:50 + Source: pyvorbis Binary: python-pyvorbis python-pyvorbis-dbg Architecture: source amd64 Version: 1.5-4 Distribution: unstable Urgency: medium Maintainer: Sandro Tosi mo...@debian.org Changed-By: Sandro Tosi mo...@debian.org Description: python-pyvorbis - Python interface to the Ogg Vorbis library python-pyvorbis-dbg - Python interface to the Ogg Vorbis library (debug extension) Closes: 768285 Changes: pyvorbis (1.5-4) unstable; urgency=medium . * debian/rules - correctly link -dbg doc directory to the main package one; thanks to Andreas Beckmann for the report and to Jean-Michel Nirgal Vourgère for the first patch; Closes: #768285 Checksums-Sha1: b3196069c273e94f322e3912d8fdd903c93eec2b 1484 pyvorbis_1.5-4.dsc f3f683fe54b622ec552041bb63bd31d74852fd26 7628 pyvorbis_1.5-4.debian.tar.xz 4775bf4c91fdb2916c5b795ace46b3b96bc30fc4 31690 python-pyvorbis_1.5-4_amd64.deb 9d8ca835e12c1719d6356dedfad13a189b3157a3 102578 python-pyvorbis-dbg_1.5-4_amd64.deb Checksums-Sha256: f42812fe8b8dcdf718ae906e39b1ba78b68015323ddf607fda842976b2029e30 1484 pyvorbis_1.5-4.dsc 77e2d83be78604d867752253dfc5de29364331daf75d60bd23387c5fe16e9695 7628 pyvorbis_1.5-4.debian.tar.xz 7181d609b56978dec60d1afa61232d0b2f64f6b4044769dd12edf78c14161017 31690 python-pyvorbis_1.5-4_amd64.deb 12a47169318383777a9668bd54e7258b3adc1e66f3bc6826d9ff613512e0a449 102578 python-pyvorbis-dbg_1.5-4_amd64.deb Files: 27f9a81325ab24ba67c22ee2bcabc06d 1484 python optional pyvorbis_1.5-4.dsc 584a508145cee6beefd5c12c3b0011fa 7628 python optional pyvorbis_1.5-4.debian.tar.xz f1617b391fd7446e8927a4564f014405 31690 python optional python-pyvorbis_1.5-4_amd64.deb 9d981b3ecf622f6f981a0bfcf3ba1ec5 102578 debug extra python-pyvorbis-dbg_1.5-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlRqeQMACgkQAukwV0RN2VDw6gCfQ7V50Y0m/JiR8r3js+iQW8dN XWkAnRueYCRopU8q9h4npuCbxZwODdqb =Ag+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/e1xqv6n-0005fw...@franck.debian.org
