Re: Standardizing the layout of git packaging repositories
On Sat, Aug 16, 2014 at 02:03:18PM +0200, Raphael Hertzog wrote: The vast majority (all?) of git packaging repositories have the upstream sources. I think this point is not really contentious. Others have demonstrated that this is not the case. However, I believe the majority of git packaging repositories do not break out the upstream source. I also believe that doing so is painful for new contributors: people seem to have varied reasons for doing it and that's fine, but they should be aware of the cost. I see no problem in the DEP standardising on having upstream and ./debian in the repository, those who don't want to follow it aren't mandated to, but having a lot more consistency of vcs-packaging for the majority of packages will make a huge difference for new contributors and I think that's something we should encourage. -- Jonathan Dowland -- 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/20140818061837.ga20...@bryant.redmars.org
Re: [FFmpeg-devel] Reintroducing FFmpeg to Debian
On 08/16/2014 11:44 PM, wm4 wrote: This reasoning may work when you have only a small amount of information to read. When you are overwhelmed with it, having different places to do different things is a much better approach. Sending patches to a list simply doesn't scale. Also, with a list, it's not convenient at all to point out a line in a patch in a mailing list. You must extract the relevant lines, cut/past them, and comment them. Instead, double clicking on the line of the patch which is displayed on a web interface is much more convenient. What? Most patches are posted inline (with git-send-email). Even worse then! It makes it hard to copy to your local fs. Anyway, have a look here, if you want to see how the review process works: https://review.openstack.org/ click on any patch proposal, and see how nice the interaction is (see patch comments, the result of jenkins unit tests, etc.). This helps a lot with QA, for sure. There's nothing wrong with having discussion in those various areas, of course; it's probably inevitable, and it's even a good thing. It's just that it's a lot harder for someone not intimately involved with the project to follow discussion if it happens in such a variety of places, and there's value to be found in making sure that everything passes through one central (discussion-enabled) point before landing. Lists are good tools for discussing where a project should go, release goals, and so on. They aren't good tools to do patch reviews. I've used both, and I'm convinced of that. What we need is solving the FFmpeg/Libav split, not well-meant suggestions by outsiders how to change our development model. The problem, as much as I understand it, was the review process and enforcing policies. So it's natural to give advice on that, with a tool which will make sure that policies are enforced. If you don't want advices, and want to have a private discussion, then why writing to debian-devel@l.d.o? 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/53f19b3e.2080...@debian.org
Re: [FFmpeg-devel] Reintroducing FFmpeg to Debian
On 08/16/2014 11:11 PM, Nicolas George wrote: L'octidi 28 thermidor, an CCXXII, Bálint Réczey a écrit : Using Gerrit and file ownersip are not mutually exclusive. Gerrit can be configured to automatically invite the right people for review based on the changed path. We recently migrated to Gerrit at the Wireshark project and it helps a lot in coordinating the reviews. I am afraid this discussion on Gerrit or other similar tools is pointless: this is trying to solve a human problem with technical means: it never works. The problem was enforcing patch review policies. This technical solution makes it possible to enforce rules. Sure, it doesn't fix the social issue completely, but at least if you implement it, it's going to be a way more difficult to bypass the review system, and the one who does will really look bad, so it's very unlikely it will happen. [...] The fork's manifesto stated that everyone was equal amongst equals, with or without commit rights, but the people who do have the commit rights are few [...] Really, when I read commit rights, in a collaborative process, I feel like there's something wrong. It becomes bad when people not involved in the project start to suffer from the consequences of the fork. This is what is happening here, for two reasons: * distributions adopting one side of the fork for non-technical reasons; There's been a very well commented technical reason stated here: the release team don't want to deal with 2 of the same library that are doing (nearly) the same things, with potentially the same security issues that we'd have to fix twice rather than once. Now, the which side debate is a different one, which I don't think Debian people are interested in (at least, *I* am not): we are just suffering from the consequences of the fork, as you wrote, and would prefer it never happened. * one side of the fork not caring about compatibility with the other side. Of course, these reasons are interconnected. Yeah. If both were fully compatible, there would be no issue using one or the other. 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/53f19ef7@debian.org
Re: [FFmpeg-devel] Reintroducing FFmpeg to Debian
On 08/16/2014 11:30 PM, Nicolas George wrote: So what about the code? Shall the FFmpeg developers discard three years of work and start working on libav? Or shall the libav developers accept to work with the code from FFmpeg that they do not like? FFmpeg folks should rework the code to make it acceptable for the libav people, and libav people should relax their policy. With *both* sides trying to work on this, it may happen. If even *only one* of the teams find excuses to not do a step forward, it wont. 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/53f1a0d3.2070...@debian.org
How can I be informed about an open bug in my package?
Hi DD folks! recently a bug has been opened against a package I maintain (debian science is the maintainer, while I'm the only uploader), but I did not notice with a mail, because: A) I forgot to subscribe to debian-science archives B) Even if subscribed I don't think I would have seen it, because the bug report doesn't mention the package name in the topic Please revert the latest Depends from python-qt4 | python-pyside to python-qt4 and python-pyside So I ask you, how can I be sure as uploader if a bug is open (or replied) against a package I care about? Reading a ton of mail about other packages in debian-science, looking for the single one I (actually) care about seems not the best solution. AFAICS there is a simple solution [1], is this the correct one? I'm worrying if is the best one :) thanks for reading, [1] https://www.debian.org/doc/manuals/developers-reference/resources.html#pkg-tracking-system Gianfranco -- 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/1408343326.52379.yahoomail...@web171802.mail.ir2.yahoo.com
Re: [FFmpeg-devel] Reintroducing FFmpeg to Debian
On 08/17/2014 07:41 PM, Andreas Cadhalpun wrote: Michael Niedermayer already volunteered to help with all security related problems of FFmpeg in Debian. So what should he do to relieve the impact on the security and release teams? Let's say he would take the role of patching stuff in Stable, there would still be double work for the release team and security team for at least: - Checking the packages before upload of security fixes (that's security team work), or upload of bugfixes to proposed-updates (that's the release team) - Making security announces There's nothing Michael could do to reduce that work. However, as stated before, uploading to Sid or Experimental could be done (if the SONAME clash gets fixed), and I don't think anyone would oppose for more contribution in Debian, especially with correct security support! 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/53f1a270.2040...@debian.org
Re: Standardizing the layout of git packaging repositories
Hi Russ, On Sun, Aug 17, 2014 at 10:31:26AM -0700, Russ Allbery wrote: Thomas Goirand z...@debian.org writes: As Charles wrote, pristine-tar works with small tarballs, but when upstream has multi-megabytes tarballs and releases often, the Git repository quickly grows to something not manageable. This does not match my experience at all. I have packaged software like that with pristine-tar, and the pristine-tar branch is still quite small. I agree it is small but has trouble with 2GB files (see #737499). The issue was discussed on Debian Med list in connection with packaging vista-foia[1+following]. Kind regards Andreas. [1] https://lists.debian.org/debian-med/2014/02/msg8.html -- http://fam-tille.de -- 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/20140818065506.gf5...@an3as.eu
Re: [FFmpeg-devel] Reintroducing FFmpeg to Debian
❦ 18 août 2014 14:20 +0800, Thomas Goirand z...@debian.org : What? Most patches are posted inline (with git-send-email). Even worse then! It makes it hard to copy to your local fs. The whole email is a valid patch in this case. -- Follow each decision as closely as possible with its associated action. - The Elements of Programming Style (Kernighan Plauger) signature.asc Description: PGP signature
Re: Standardizing the layout of git packaging repositories
On 08/18/2014 07:47 AM, Henrique de Moraes Holschuh wrote: On Sun, 17 Aug 2014, Thomas Goirand wrote: On 08/17/2014 03:52 AM, Raphael Hertzog wrote: On Fri, 15 Aug 2014, Henrique de Moraes Holschuh wrote: - the above layout is for the traditional case of non-native packages, what would be the layout for native packages? how can be differentiate between native/non-native layout? Please don't. It would be Really Troublesome should a package need to switch from native to non-native, or the opposite. Why? Until we have defined what the layout is for a native package, you can't assume this. It's possibly a subset of the conventions for non-native packages + some common conventions in all software projects. Something like: - branches - master: main development branch Please don't use master. It's meaningless. It just happens to be the default in Git, but that's about it. It is not meaningless in the sense that it is a widely used convention in git repositories. A widely used convention to express what? The fact that you didn't bother changing the default name of the branch? 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/53f1a515.1090...@debian.org
Re: Standardizing the layout of git packaging repositories
On 08/18/2014 01:49 AM, Russ Allbery wrote: Joey took various approaches to work around this, including shipping some of the older versions of the compressors in the package. However, the issue also applies to tar, and so far has been addressed by modifying tar to add a backword-compatibility mode. And if upstream uses tar from BSD, game over... 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/53f1a661.4080...@debian.org
Re: Standardizing the layout of git packaging repositories
On 08/18/2014 03:08 PM, Thomas Goirand wrote:
On 08/18/2014 01:49 AM, Russ Allbery wrote:
Joey took various approaches to work around this, including shipping some
of the older versions of the compressors in the package. However, the
issue also applies to tar, and so far has been addressed by modifying tar
to add a backword-compatibility mode.
And if upstream uses tar from BSD, game over...
I meant of course, that the result will be different from the one
upstream. Anyway, what's all this religion about .orig.tar.{x,gz} files
about? Why should we care that much? Should I fear that I will make the
tarball gods unhappy if upstream and Debian orig files are different? I
still don't get the point... (I do understand the importance of
reproducibility of building the orig file *in Debian* though)
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/53f1a862.1050...@debian.org
Re: How can I be informed about an open bug in my package?
On Mon, Aug 18, 2014 at 07:28:46AM +0100, Gianfranco Costamagna wrote: recently a bug has been opened against a package I maintain (debian science is the maintainer, while I'm the only uploader), but I did not notice with a mail, because: A) I forgot to subscribe to debian-science archives B) Even if subscribed I don't think I would have seen it, because the bug report doesn't mention the package name in the topic So I ask you, how can I be sure as uploader if a bug is open (or replied) against a package I care about? You can subscribe to a particular package. Go to: http://packages.qa.debian.org/$PACKAGE and there's an input field on the lower left. -- // If you believe in so-called intellectual property, please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- 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/20140818071815.ga17...@angband.pl
Re: Replacement of SAMtools 0.19 by SAMtools 1.0.
Le Mon, Aug 18, 2014 at 08:53:12AM +0200, Olivier Sallou a écrit : do you know, by chance, what is the difference between samtools and the net.sf.samtools Java lib of picard-tools ? They look quite the same. The HTSlib fix an issue forigv (on SAMFileWriterFactory), but SAMFileWriterFactory class in picard-tools is not the same than the one in HTSlib. Hi Olivier, the home page of Picard (http://picard.sourceforge.net/index.shtml) has been recently updated to mention both https://github.com/broadinstitute/picard and https://github.com/samtools/htsjdk, so I guess that they work together and that the fix in HTSJDK will eventually propagate to Picard ? Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140818072029.gb25...@falafel.plessy.net
Re: Standardizing the layout of git packaging repositories
On Sat, Aug 16, 2014 at 09:51:21PM +0200, Bastien ROUCARIES wrote: On Sat, Aug 16, 2014 at 1:59 PM, Raphael Hertzog hert...@debian.org wrote: Hi, On Fri, 15 Aug 2014, Guido Günther wrote: The gbp manual has a recommended branch layout: http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html#GBP.BRANCH.NAMING which could serve as a basis. There's plenty of room for improvement, e.g. the case where one tracks upstream git isn't yet mentioned (I started to follow the above layout also in this case). Some comments on this recommended layout: 1/ I suggested vendor/master rather than vendor/unstable (or sid) because it means we don't have to know the default codename/suite used for packaging of new upstream versions (in particular for downstreams) 2/ having multiple upstream/codename is bound to never be up-to-date when I do git checkout debian/experimental git merge debian/master, upstream/experimental will get out of sync and I won't notice it because my package builds just fine However multiple upstream/* branches can be useful, they should just match real upstream branches... so things like upstream/master, upstream/4.8.x, upstream/4.9.x, etc. 3/ I don't see the need for backports/codename, I would rather use debian/wheezy-backports (which actually is just a specific case of vendor/codename since wheezy-backports is the Codename in the Release file) and security/codename is just the continuation of vendor/codename after a stable release, so again I don't see the need for a specific branch here (and if we really need a separate branch, it can again be vendor/codename-security) I use for debian patches a debian-patches/version branch. Friendly upstream could cherry pick if they need it. Agreed. I'm using something similar but as a tag not branch like patch-queue/version which is the patch-queue corresponding to Debian release version. This can also be used by others to rebase the queue for new versions (omitting the need for gbp pq --time-machine=... if the new upstream is already imported). Cheers, -- Cheers, -- 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/20140817181437.ga23...@bogon.m.sigxcpu.org
Re: How can I be informed about an open bug in my package?
On 2014-08-18 8:18, Adam Borowski wrote: On Mon, Aug 18, 2014 at 07:28:46AM +0100, Gianfranco Costamagna wrote: recently a bug has been opened against a package I maintain (debian science is the maintainer, while I'm the only uploader), but I did not notice with a mail, because: A) I forgot to subscribe to debian-science archives B) Even if subscribed I don't think I would have seen it, because the bug report doesn't mention the package name in the topic So I ask you, how can I be sure as uploader if a bug is open (or replied) against a package I care about? You can subscribe to a particular package. Go to: http://packages.qa.debian.org/$PACKAGE and there's an input field on the lower left. The bit of the mail you snipped says: On Mon, Aug 18, 2014 at 07:28:46AM +0100, Gianfranco Costamagna wrote: AFAICS there is a simple solution [1], is this the correct one? [...] [1] https://www.debian.org/doc/manuals/developers-reference/resources.html#pkg-tracking-system So, yes. Regards, Adam -- 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/c1987931e73211acd1830405090b2...@mail.adsl.funky-badger.org
Re: How can I be informed about an open bug in my package?
You can also check this page periodically: https://qa.debian.org/developer.php?login=costamagnagianfra...@yahoo.it On Sun, Aug 17, 2014 at 11:28 PM, Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote: Hi DD folks! recently a bug has been opened against a package I maintain (debian science is the maintainer, while I'm the only uploader), but I did not notice with a mail, because: A) I forgot to subscribe to debian-science archives B) Even if subscribed I don't think I would have seen it, because the bug report doesn't mention the package name in the topic Please revert the latest Depends from python-qt4 | python-pyside to python-qt4 and python-pyside So I ask you, how can I be sure as uploader if a bug is open (or replied) against a package I care about? Reading a ton of mail about other packages in debian-science, looking for the single one I (actually) care about seems not the best solution. AFAICS there is a simple solution [1], is this the correct one? I'm worrying if is the best one :) thanks for reading, [1] https://www.debian.org/doc/manuals/developers-reference/resources.html#pkg-tracking-system Gianfranco -- 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/1408343326.52379.yahoomail...@web171802.mail.ir2.yahoo.com
Bug#758511: ITP: ibus-zhuyin -- IBus Zhuyin Input Method
Package: wnpp Severity: wishlist Owner: Shih-Yuan Lee (FourDollars) fourdoll...@gmail.com * Package name: ibus-zhuyin Version : 0.1.0 Upstream Author : Shih-Yuan Lee (FourDollars) fourdoll...@gmail.com * URL : https://github.com/fourdollars/ibus-zhuyin * License : GPLv3 Programming Lang: C Description : IBus Traditional ZhuYin Input Method This traditional Chinese zhuyin input method is designed for old school users. There is no intelligent phonetic matching mechanism, so you have to select every word you type. This program is similar to the plain mode of ibus-chewing. However ibus-chewing uses intelligent phonetic matching mechanism by default. ibus-zhuyin tends not to use any intelligent phonetic matching mechanism, and keeps the program less dependencies and fast response. -- 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/20140818103225.8059.42035.reportbug@9020M
Re: systemd service and /etc/default/
On Sun, Aug 17, 2014 at 01:13:36PM +0200, Marc Haber wrote: On Sun, 17 Aug 2014 01:40:27 -0700, Josh Triplett j...@joshtriplett.org wrote: Ludovico Cavedon wrote: I am writing a systemd service file for a daemon (ntopng) and I would like to know what you think is the best way to load some configuration. The ntopng daemon takes multiple interfaces in the format of multiple -i command-line options. For example. ntopng -i eth0 -i wlan0 Currently the interfaces are stored in /etc/default/ntopng INTERFACES=eth0 wlan0 and the sysv init script takes care of adding -i for each one of them. I would like to keep the sysv compatibility and do the same in systemd. I tried in various ways, but the two solution I could think of are: 1) change the format of INTERFACES to require inclusion of -i. I.e INTERFACES=-i eth0 -i wlan0 and use EnvironmentFIle=/etc/default/ntopng. This changes the format, complicated upgrades, and is more error prone. 2) instead of doing Exec=ntopng, Exec a script that does the mangling and then execs ntopng. Because both solutions do not look great to me, and I could not find an example, I am asking your opinion. After writing this email, I start to believe 2) is the right way, but I would appreciate anybody's input. 3) Teach ntopng to understand /etc/ntopng.conf natively and migrate the settings there. 4) Teach ntopng to automatically detect the available network devices on the system (including new ones that show up dynamically) and automatically handle all of them unless configured to do otherwise, making configuration usually unnecessary. Please. The attitute of requiring Debian maintainers to modify upstream software instead of having simple two-line extension to an init script is really unfriendly. Why do only systemd friends keep recommending this? Once upon time, every distribution carried scripts to autodetect and build a XF86Config for end users. Every distribution duplicated the effort for their own scripts, each had different bugs and limitations. Some even made a selling point of having better autodetection than other distributions. Then upstream added autodection.. ..and pretty much all that duplicated work became wasted. Making upstream software better is for the benefit of all users. Making debian specific scripts (and patches) are only the benefit of debian users. Doing a few lines in initscript/postinst saves the Debian maintainer time, but only in the short term - If the upstream changes cli options, configuration files etc - the debian maintainer will have to spend time adapting. Worse, the maintainer may have to write new scripts to migrate setting from old format to new. The more scripts you wrap around the upstream codebase, the maintaince burden you have in future. This is the position where the ntop maintainer has found himself in (except it is not upstream, but another tool that has changed). Riku -- 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/20140818104413.ga15...@afflict.kos.to
Re: libfreerdp changed soname without transition - rebuilds necessary
Hi, On 18.08.2014 07:20, Dominik George wrote: the libfreerdp1 package changed its soname without a transition and without introducing a new package. That broke binary compatibility of at least remmina and libguac-client-rdp0 [0]. The bug report about this is: https://bugs.debian.org/757926 Best regards, Andreas -- 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/53f1e557.80...@googlemail.com
Re: [FFmpeg-devel] Reintroducing FFmpeg to Debian
Hi Thomas, On 18.08.2014 08:36, Thomas Goirand wrote: There's been a very well commented technical reason stated here: the release team don't want to deal with 2 of the same library that are doing (nearly) the same things, with potentially the same security issues that we'd have to fix twice rather than once. Why is it a security problem to have FFmpeg and Libav, but apparently no problem to have MySQL, MariaDB and PerconaDB? This seems quite arbitrary to me, especially since there have been already 36 CVEs in 2014 for MySQL [1], of which 26 apparently are also relevant for MariaDB [2] and PerconaDB [3], but only 7 for FFmpeg [4] and 8 for Libav [5] in the same time. Best regards, Andreas 1: https://security-tracker.debian.org/tracker/source-package/mysql-5.5 2: https://security-tracker.debian.org/tracker/source-package/mariadb-5.5 3: https://security-tracker.debian.org/tracker/source-package/percona-xtradb-cluster-5.5 4: https://security-tracker.debian.org/tracker/source-package/ffmpeg 5: https://security-tracker.debian.org/tracker/source-package/libav -- 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/53f1e5f9.4030...@googlemail.com
Re: [FFmpeg-devel] Reintroducing FFmpeg to Debian
Le primidi 1er fructidor, an CCXXII, Thomas Goirand a écrit : The problem was enforcing patch review policies. No, it never was. There's been a very well commented technical reason stated here: the release team don't want to deal with 2 of the same library that are doing (nearly) the same things That the reason for keeping only one; other have discussed the validity of the reason. The reason for switching from FFmpeg to libav in the first place just after the fork is much simpler than that. Yeah. If both were fully compatible, there would be no issue using one or the other. Are there known current cases where FFmpeg can not emulate libav? Regards, -- Nicolas George signature.asc Description: Digital signature
Re: Standardizing the layout of git packaging repositories
On Sat, 16 Aug 2014, Thomas Goirand wrote: Why would you tag the upstream release? I mean, it's upstream's job to Yeah, if upstream uses git at least it should NOT be done by the packager. If not, it depends. - shall we standardize the pristine-tar branch? As in, always use pristine-tar? No! ACK. Vendor lock-in. Yes. Producing orig.tar.xz out of upstream tag should be industrialized, and written in some tools, which we would all be using. I currently do: ./debian/rules gen-orig-xz, but that shouldn't be specific to my own packages. Then please read DevRef §6.7.8.2 and use debian/rules get-orig-source instead. It also specifies how the top-level directory of the origtgz shall be named if you repackage. As for a non-repackaged origtgz… use upstream’s if at all possible. bye, //mirabilos -- «MyISAM tables -will- get corrupted eventually. This is a fact of life. » “mysql is about as much database as ms access” – “MSSQL at least descends from a database” “it's a rebranded SyBase” “MySQL however was born from a flatfile and went downhill from there” – “at least jetDB doesn’t claim to be a database” ‣‣‣ Please, http://deb.li/mysql and MariaDB, finally die! -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.deb.2.11.1408181350091.30...@tglase.lan.tarent.de
Re: How can I be informed about an open bug in my package?
On Mon, Aug 18, 2014 at 01:19:55AM -0700, Andrew Kelley wrote: You can also check this page periodically: https://qa.debian.org/developer.php?login=costamagnagianfra...@yahoo.it Alternatively https://udd.debian.org/dmd/ Kind regards Andreas. -- http://fam-tille.de -- 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/20140818120108.gd15...@an3as.eu
Re: Standardizing the layout of git packaging repositories
On Fri, 15 Aug 2014, Russ Allbery wrote: m...@linux.it (Marco d'Itri) writes: The first step is to determine which problem you are trying to solve. Surprisingly insightful, this one. I want to be able to check out a git repository and do packaging work and an upload, without having to pull any external artifacts from somewhere else. This does not work in Debian: you always need the .orig.tar.* file, at least for the upload, for non-native packages. And that is by design in Debian. The repository is the helper. The *standard* Debian workflow operates on the .dsc file instead, which (when pulled via dget) contains everything you need to start working. Actually, most of the time when working, you don’t even really need a VCS repository, I found out… (I’m now keeping many less packages in a VCS than before). 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.1408181358340.30...@tglase.lan.tarent.de
Re: Reintroducing FFmpeg to Debian
Andreas Cadhalpun andreas.cadhal...@googlemail.com schrieb: Hi Thomas, On 18.08.2014 08:36, Thomas Goirand wrote: There's been a very well commented technical reason stated here: the release team don't want to deal with 2 of the same library that are doing (nearly) the same things, with potentially the same security issues that we'd have to fix twice rather than once. Why is it a security problem to have FFmpeg and Libav, but apparently no problem to have MySQL, MariaDB and PerconaDB? Raphael Geissert already wrote that mysql/mariadb/percona will be addressed as well; we haven't come around to since since we need to deal with a lot of stuf and being dragged into endless discussions on -devel is certainly not helpful. Cheers, Moritz -- 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/slrnlv3r0p.2f8@inutil.org
Re: Standardizing the layout of git packaging repositories
On Sun, 17 Aug 2014, Thomas Goirand wrote:
Like I wrote in another post, master doesn't express anything.
ACK.
All of this is error prone. Using upstream tags and merging them rather
than branches avoid troubles. I have yet to see a case where using
upstream tags wasn't practical.
There are cases where upstream tags are not on upstream’s development
branch (or release branch), but one or several commits removed, or even
completely separate. This mostly happens with repositories converted
from CVS or SVN, though. I’ve seen this a lot.
Charles Plessy wrote:
codename. Otherwise, people will be confused with debian/rc-buggy.
Well, just use “experimental” for experimental, but otherwise,
use lenny/squeeze/wheezy/jessie/sid as those are the names that
are going to stick, which {,old}stable and testing are not.
bye,
//mirabilos
--
15:41⎜Lo-lan-do:#fusionforge Somebody write a testsuite for helloworld :-)
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/alpine.deb.2.11.1408181406410.30...@tglase.lan.tarent.de
debian-subdir-only packaging repos (was Re: Standardizing the layout of git packaging repositories)
On Sun, 17 Aug 2014, Neil Williams wrote: The vast majority (all?) of git packaging repositories have the upstream sources. No. None of mine do, or will. I’m working with some which also don’t, and find it would be easier if there were a way to extract a .orig.tar.gz in the same way that dpkg-source does, even when no .dsc exists. (By this I mean the magic to ensure a properly named top-level directory, renaming the one from the tarball, or even moving its content into a newly created one.) Currently I have to paxtar xaf %f and then F6 (rename) the directory (in mc) most of the time… bye, //mirabilos -- 15:41⎜Lo-lan-do:#fusionforge Somebody write a testsuite for helloworld :-) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.deb.2.11.1408181411130.30...@tglase.lan.tarent.de
Re: Standardizing the layout of git packaging repositories
* Charles Plessy ple...@debian.org, 2014-08-17, 19:39: for suites that are never released, I think that it is fine to not use the codename. Otherwise, people will be confused with debian/rc-buggy. FWIW, rc-buggy is not the codename for experimental: $ wget -q -O- http://http.debian.net/debian/dists/experimental/Release | grep -m1 ^Codename: Codename: experimental See also bug #704124. -- Jakub Wilk -- 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/20140818121655.ga6...@jwilk.net
Re: How can I be informed about an open bug in my package?
Hi *, Il Lunedì 18 Agosto 2014 10:20, Andrew Kelley superjo...@gmail.com ha scritto: thanks to all for the useful replies! So I will subscribe through the PTS interface, it is the best solution (I was already wondering that) ;) You can also check this page periodically: https://qa.debian.org/developer.php?login=costamagnagianfra...@yahoo.it I already use the developer.php page, but it doesn't say the _delta_ for the newly open bugs, just the total amount (useful, but not too much) Cheers, Gianfranco On Sun, Aug 17, 2014 at 11:28 PM, Gianfranco Costamagna costamagnagianfra...@yahoo.it wrote: Hi DD folks! recently a bug has been opened against a package I maintain (debian science is the maintainer, while I'm the only uploader), but I did not notice with a mail, because: A) I forgot to subscribe to debian-science archives B) Even if subscribed I don't think I would have seen it, because the bug report doesn't mention the package name in the topic Please revert the latest Depends from python-qt4 | python-pyside to python-qt4 and python-pyside So I ask you, how can I be sure as uploader if a bug is open (or replied) against a package I care about? Reading a ton of mail about other packages in debian-science, looking for the single one I (actually) care about seems not the best solution. AFAICS there is a simple solution [1], is this the correct one? I'm worrying if is the best one :) thanks for reading, [1] https://www.debian.org/doc/manuals/developers-reference/resources.html#pkg-tracking-system Gianfranco -- 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/1408343326.52379.yahoomail...@web171802.mail.ir2.yahoo.com -- 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/1408363273.30927.yahoomail...@web171805.mail.ir2.yahoo.com
Re: Standardizing the layout of git packaging repositories
On Sun, 17 Aug 2014, Jonathan Dowland wrote: On Fri, Aug 15, 2014 at 04:16:01PM +0200, Raphael Hertzog wrote: - version encoding (due to git restrictions): : - % ~ - _ I’d rather have something that sorts like Debian versions in “git tag” output… _ - _5f : - _3a ~ - _7e Yikes! tags/foo_3a4b5c-6d No, thanks. Sure, this would reduce information loss, but… no. 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.1408181425550.30...@tglase.lan.tarent.de
Re: Standardizing the layout of git packaging repositories
On Sat, Aug 16, 2014 at 01:59:46PM +0200, Raphael Hertzog wrote: Hi, On Fri, 15 Aug 2014, Guido Günther wrote: The gbp manual has a recommended branch layout: http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html#GBP.BRANCH.NAMING which could serve as a basis. There's plenty of room for improvement, e.g. the case where one tracks upstream git isn't yet mentioned (I started to follow the above layout also in this case). Some comments on this recommended layout: 1/ I suggested vendor/master rather than vendor/unstable (or sid) because it means we don't have to know the default codename/suite used for packaging of new upstream versions (in particular for downstreams) There is no such default. Most projects I work in package release candidates on debian/experimental, sometimes (depending on e.g. the state of the freeze) also releases. Point releases on the other hand go to debian/wheezy or security/wheezy. This information can't be coded in the branch naming. 2/ having multiple upstream/codename is bound to never be up-to-date when I do git checkout debian/experimental git merge debian/master, upstream/experimental will get out of sync and I won't notice it because my package builds just fine However multiple upstream/* branches can be useful, they should just match real upstream branches... so things like upstream/master, upstream/4.8.x, upstream/4.9.x, etc. (If upstream doesn't use git) matching this to Debian releases is more clear imho. I do acknowledge that you have to keep these in sync (e.g. via git update-ref) but it helps packaging tools to match the release in the changelog to the build and upstream branch. 3/ I don't see the need for backports/codename, I would rather use debian/wheezy-backports (which actually is just a specific case of vendor/codename since wheezy-backports is the Codename in the Release file) Agreed, but... and security/codename is just the continuation of vendor/codename after a stable release, so again I don't see the need for a specific branch here (and if we really need a separate branch, it can again be vendor/codename-security) There are situations where you have an upload for stable-security and for stable. The review and acceptance of these packages happens by different teams at different points so it's nicer to have them separated. - upstream/version (note: we don't need an upstream branch, having the good tag for any release that the distros are packaging is enough, it can point to a synthetic commit built with tools like git-import-orig or to a real upstream commit) Agreed, although having a branch (and recommended naming convention) can be useful. Yes. - pkg/version (note: git-buildpackage uses debian/version but I find this confusing as we then also have the debian/ prefix for ubuntu or kali uploads, we don't need the vendor prefix as the usual versioning rules embed the downstream distribution name (e.g. 1.0-0ubuntu1) and thus there can't be any conflict on the namespace, keeping a prefix is important to easily differentiate tags created by upstream developers from tags created by packagers) The tag format is configurable in gbp and I'd expect downstreams to use a different name space (e.g. ubuntu/version). This makes it simpler to tab complete (or delete) certain groups of tags. A patch to make the tag message configurable too is waiting to be applied. pkg/ is too generic since we'll have more of the RPM support upstreamed soonish. Anything that needs to be configured is a source of error. I'd rather have gbp do the right thing and pull the information from dpkg-vendor. Good idea. We could add this as --debian-tag='auto' or similar and make it the default. Cheers, -- Guido -- 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/20140818131403.ga4...@bogon.m.sigxcpu.org
Re: Reintroducing FFmpeg to Debian
Hi Moritz, On 18.08.2014 14:05, Moritz Mühlenhoff wrote: Andreas Cadhalpun andreas.cadhal...@googlemail.com schrieb: On 18.08.2014 08:36, Thomas Goirand wrote: There's been a very well commented technical reason stated here: the release team don't want to deal with 2 of the same library that are doing (nearly) the same things, with potentially the same security issues that we'd have to fix twice rather than once. Why is it a security problem to have FFmpeg and Libav, but apparently no problem to have MySQL, MariaDB and PerconaDB? Raphael Geissert already wrote that mysql/mariadb/percona will be addressed as well; we haven't come around to since since we need to deal with a lot of stuf and being dragged into endless discussions on -devel is certainly not helpful. I don't remember Raphael Geissert writing anything about security concerns with having MySQL, MariaDB and PerconaDB, only that you wrote half a year ago, that the security team will be working with the release team to sort this out for jessie [1]. As I haven't seen any further discussion about this and the recent mail about MySQL, MariaDB and PerconaDB on debian-devel [2] indicated that the plan was to have all of them as alternatives, I assumed this was resolved. There wouldn't be any discussion about the security of FFmpeg and Libav as well, if you hadn't started it [3]. Why is FFmpeg treated differently than MariaDB/PerconaDB? Best regards, Andreas 1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729203#435 2: https://lists.debian.org/debian-devel/2014/08/msg00016.html 3: https://lists.debian.org/debian-devel/2014/02/msg00668.html -- 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/53f1fc78.7030...@googlemail.com
Re: Standardizing the layout of git packaging repositories
On Mon, 18 Aug 2014, Thorsten Glaser wrote: This does not work in Debian: you always need the .orig.tar.* file, at least for the upload, for non-native packages. You need it from somewhere, but the whole point of pristine-tar is that you can generate the orig.tar.* from information in the git repository. -- Don Armstrong http://www.donarmstrong.com The smallest quantity of bread that can be sliced and toasted has yet to be experimentally determined. In the quantum limit we must necessarily encounter fundamental toast particles which the author will unflinchingly designate here as croutons. -- Cser, Jim. Nanotechnology and the Physical Limits of Toastability. AIR 1:3, June, 1995. -- 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/20140818150347.gm22...@teltox.donarmstrong.com
Re: systemd service and /etc/default/
On 08/18/2014 01:36 AM, Russ Allbery wrote: The upstream source *can* be changed and improved for everyone. Truth, but not always practical. If I was going to fix all the defects of software I package, I don't think I'd have enough time to sleep even one hour per night. 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/53f212fe.9080...@debian.org
Why is package X not in testing yet?
Greetings, If we have a package, which doesn't migrate to testing, we usually check the Why does package X not in testing yet? page or the PTS. Usually they do a great job in telling us why our package doesn't migrate. But sometimes you have packages, which have complicated dependencies, that don't make it easy to tell why our package doesn't migrate. Usually the PTS and Why is package X not in testing yet? fail at those packages and don't give any useful explanation. For example look at the page for haskell-hgettext[1]. Those packages usually have to go into testing together with a few other packages. If it's getting worse your package needs to go into testing with a lot of other packages (usually if your package is part of a bigger transition). If your package is part of a transition you might have luck and the transition page can tell you what the problem is. But sometimes not even that pages help. For that reason I made a tool that takes a package name and tries to find out why your package doesn't migrate to testing. When run, it gathers all packages that block our given package X. Then it fetches all excuses for these packages and throws all of them away, except those that are identified as interesting. These types of excuses are identified as interesting: - out of date on arch - pkg has new bugs - Too young This takes a long time (for me 3 Minutes) depending on your internet connection. This is mostly useful for haskell packages, as they have very close dependencies. However, it might be interesting in any other transition. The source code is attached and can be found in the tools repository[2] of the Haskell Group. In order to compile it you need the following packages: - ghc - libghc-regex-pcre-dev - libpcre++-dev (This should be a dependency of libghc-regex-pcre-dev but it isn't due to a bug) Compile it with: ghc --make reasons.hs To run it you need the following packages: - devscripts - wget - ca-certificates - locales (you should use an UTF-8 encoding, otherwise its guaranteed you will have problems.) Also you must have enabled the source URIs in you sources.list. There are still some rough edges. The most notable ones are: - Most errors that can happen aren't catched. So an haskell exception will be thrown, which gives not very much information of the problem. - The excuses are fetched with grep-excuses. So the excuses file is downloaded over ad over again. There is already a bug with a patch filed against grep-excuses to fix this. - out of date excuses are all considered interesting, even though it would be better to only include those that aren't in state B-D unistallable. A bit more detail on the workflow of this tool is described in this[3] post. [1]: https://release.debian.org/migration/testing.pl?package=haskell-hgettext [2]: http://anonscm.debian.org/cgit/pkg-haskell/tools.git/ [3]: https://lists.debian.org/debian-haskell/2014/08/msg00027.html import Text.Regex.PCRE import System.Environment import System.Exit import System.Process import System.IO import Data.Maybe import Data.List import Data.Char import qualified Data.Set as S import Control.Exception import System.IO.Error import System.Directory import Debug.Trace data Excuses = Excuses String [String] isEmpty :: Excuses - Bool isEmpty (Excuses _ []) = False isEmpty (Excuses _ _) = True excuses2String :: Excuses - String excuses2String (Excuses pkg excuses) = unlines $ (pkg ++ :):(map ( ++) excuses) main = do package - getArgs = parse output - fmap lines acquireBritneyOut let bins = getBinBlockers output package result - try (fmap nub $ mapM getSrcPackage bins) :: IO (Either ErrorCall [String]) srcBlockers - case result of Left e - putStrLn packageNotFoundMsg exitFailure Right pkgs - return pkgs excuses - mapM getExcuse srcBlockers additionalExcuses - getAdditionalExcuses srcBlockers excuses let filteredExcuses = filterExcuses isInteresting $ excuses ++ additionalExcuses mapM_ putStrLn $ map excuses2String filteredExcuses acquireBritneyOut :: IO String acquireBritneyOut = do cachePath - chooseCachePath case cachePath of Nothing - readProcess /usr/bin/wget [-q, -O, -, outputUrl] Just path - do createDirectoryIfMissing False path setCurrentDirectory path readProcess /usr/bin/wget [-q, -N, outputUrl] readFile update_output.txt chooseCachePath :: IO (Maybe String) chooseCachePath = do result - tryJust shouldCatch $ getAppUserDataDirectory reasons hasHome - getHomeDirectory = doesDirectoryExist return $ case result of Right dir - if hasHome then Just dir else Nothing Left _ - Nothing where shouldCatch e = if isDoesNotExistError e then Just e else Nothing outputUrl :: String outputUrl = release.debian.org/britney/update_output.txt parse :: [String] - IO
Re: Standardizing the layout of git packaging repositories
Thomas Goirand z...@debian.org writes: On 08/18/2014 01:49 AM, Russ Allbery wrote: Joey took various approaches to work around this, including shipping some of the older versions of the compressors in the package. However, the issue also applies to tar, and so far has been addressed by modifying tar to add a backword-compatibility mode. And if upstream uses tar from BSD, game over... No, I'm pretty sure that currently works. But I don't know how much that relies on modifications to Debian's tar package. -- 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/87oavhzrvl@hope.eyrie.org
Re: Standardizing the layout of git packaging repositories
On Mon, Aug 18, 2014 at 02:27:15PM +0200, Thorsten Glaser wrote: I’d rather have something that sorts like Debian versions in “git tag” output… If that proves too hard to achieve with a mapping scheme, it would be trivial to write a filter to implement it. It does sound useful. Yikes! tags/foo_3a4b5c-6d You really have a tags/foo:4b5c-6d? Or assuming you mis-read my email, a tags/foo:K\-m? Can we please use realistic counter-examples? -- 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/20140818163537.ga32...@bryant.redmars.org
Re: systemd service and /etc/default/
Thomas Goirand z...@debian.org writes: On 08/18/2014 01:36 AM, Russ Allbery wrote: The upstream source *can* be changed and improved for everyone. Truth, but not always practical. If I was going to fix all the defects of software I package, I don't think I'd have enough time to sleep even one hour per night. I don't think anyone is advocating that it's always practical. In fact, I believe I implied that it wasn't always practical in the part of the message you were replying to that you deleted. :) More generally (and this part is not pointed at Thomas), I realize it's become de rigueur in any thread about systemd to reply to hm, you could consider getting a dog with WHY DO YOU WANT TO KILL MY KITTENS?!?!?, but seriously folks, could we tone down the assumption that people with differing preferences want to break everything you do? It's just a few additional options. If you don't think they're good options, don't follow them! It doesn't have to turn into a huge argument. People make suggestions to me all the time that I don't follow, for reasons of time, simple disagreement, or because I'm still thinking about the problem. Everyone understands this. It's not a big deal unless we go out of our way to make it one. -- 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/87k365zrme@hope.eyrie.org
Re: Standardizing the layout of git packaging repositories
2014-08-18 14:27:15 Thorsten Glaser: On Sun, 17 Aug 2014, Jonathan Dowland wrote: On Fri, Aug 15, 2014 at 04:16:01PM +0200, Raphael Hertzog wrote: - version encoding (due to git restrictions): : - % ~ - _ I’d rather have something that sorts like Debian versions in “git tag” output… Including the tilde-sorts-before-empty rule? I'm curious to see a solution to this that doesn't make the tags look ugly. Timo signature.asc Description: This is a digitally signed message part.
Re: Standardizing the layout of git packaging repositories
On Mon, 18 Aug 2014, Don Armstrong wrote: On Mon, 18 Aug 2014, Thorsten Glaser wrote: This does not work in Debian: you always need the .orig.tar.* file, at least for the upload, for non-native packages. You need it from somewhere, but the whole point of pristine-tar is that you can generate the orig.tar.* from information in the git repository. pristine-tar information bitrots. As long as you *know* this and prepare for it, that's not a problem. Arguably, pristine-tar needs to do a much better job of disclosing its shortcomings in the documentation and of marketing itself as a simple convenience tool: you must not depend on it being able to re-create the orig tarballs at some unspecified time in the future. The information pristine-tar stores bitrots when tar/gzip/xz/bzip2 changes output even slightly, because the stored deltas become useless. To work around this, you need to add a way for pristine-tar/gz/xz/bzip2... to duplicate the exact behaviour of past versions of these tools. It also bitrots when the user does any sort of edition to the tarball-base branch it uses to generate the approximate tarbal: pristine-tar stores references to the git commits it needs inside a .id file, instead of using something git actually knows about. This can be fixed by storing the base tarball commit information needed by pristine-tar in a way git itself is aware of. Since it needs to be push/fetch-safe, it will have to be done either as visible special branch (e.g. as done by stgit) or by abusing multi-parent (merge) commits. private refs won't work well for this. It is easy to deal with the two failure scenarios above, as long as you are aware they could happen. -- 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/20140818173013.ga27...@khazad-dum.debian.net
Re: Standardizing the layout of git packaging repositories
On Sun, 17 Aug 2014, Thomas Goirand wrote: Obviously, when upstream are already doing everything correctly, creating the upstream/version tag should not become some administrative chore but it could be done automatically as part of a some gbp upstream-merge upstream-tag command for example. Ah, that's an interesting topic! :) Often, upstream are using v1.2.3. Previously, I was doing, in debian/gbp.conf: upstream-tag = v%(version)s But then I decided it was really annoying, and since, I just do: git tag 1.2.3 v1.2.3 The very good thing is that, since the tag points to the same object, version 1.2.3 is also PGP signed, just like v1.2.3! :) Oooh! That's a _very_ nice trick, and very important information! Thank you for sharing it! -- 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/20140818173229.gb27...@khazad-dum.debian.net
Re: Standardizing the layout of git packaging repositories
Hi, I do think that this is quite common, and my preferred way of doing things. It is easy for newcomers to handle, easy for me to handle, no need to learn a lot of git specific tools or helpers, you can mostly ignore git if you want to. I've a couple of times tried to get myself to actually learn various of these newfangled tools like git-buildpackaeg and such, and each time I end up feeling they get much more in my way that they actually help me. Being a newcomer to packaging, I have to disagree on this. I use gbp for my packages and found, so far, no other way of dealing with packages that's even remotely as convenient. In particular, handling the upstream tarball and whatever is necessary when there's a new upstream version is an absolute no-brainer. I was not aware of got-overlay until recently, maybe that helps to make the debian/-only structure more usable. But for all I'm concerned, git is not helping at all here, it's like dealing with a raw package without any helper. Kind regards Ralf -- 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/53f23980.8080...@ralfj.de
Re: Standardizing the layout of git packaging repositories
Russ Allbery wrote: No, I'm pretty sure that currently works. But I don't know how much that relies on modifications to Debian's tar package. It doesn't matter what tar was used to create the original tarball; as long as we know the files present in it, we can use a (necessarily stable version of) tar to generate a file that is substantially similar (same files, same order), and then xdelta to get the rest of the way to the original tarball. This is what pristine-tar does. -- see shy jo signature.asc Description: Digital signature
Re: systemd service and /etc/default/
On Sun, 17 Aug 2014, Marc Haber wrote: Please. The attitute of requiring Debian maintainers to modify upstream software instead of having simple two-line extension to an init script is really unfriendly. Why do only systemd friends keep recommending this? Using my sysvinit hat, I've always recommended people to actually fix daemons so that they detach properly from stdin/stdout/stderr, do a proper setsid(), implement proper pidfile support... I don't see much difference, there ;-) -- 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/20140818173947.gc27...@khazad-dum.debian.net
Re: systemd service and /etc/default/
On Mon, Aug 18, 2014 at 09:31:37AM -0700, Russ Allbery wrote: More generally (and this part is not pointed at Thomas), I realize it's become de rigueur in any thread about systemd to reply to hm, you could consider getting a dog with WHY DO YOU WANT TO KILL MY KITTENS?!?!?, but seriously folks, could we tone down the assumption that people with differing preferences want to break everything you do? It's just a few additional options. If you don't think they're good options, don't follow them! It doesn't have to turn into a huge argument. People make suggestions to me all the time that I don't follow, for reasons of time, simple disagreement, or because I'm still thinking about the problem. Everyone understands this. It's not a big deal unless we go out of our way to make it one. Hear, hear! +1. Give the man a medal! -- http://www.cafepress.com/trunktees -- geeky funny T-shirts http://gtdfh.branchable.com/ -- GTD for hackers -- 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/20140818183548.go7...@exolobe1.liw.fi
Re: Standardizing the layout of git packaging repositories
On Sun, 2014-08-17 at 09:00 +0200, Raphael Hertzog wrote: On Sun, 17 Aug 2014, Thomas Goirand wrote: Well, I have nothing against derivative/downstream distros, but if you're about to do a new DEP, please consider Debian first. In such case, debian/unstable makes a lot more sense than just debian/master. Like I wrote in another post, master doesn't express anything. master does express something to people who are using git, it's the main development trunk. [...] For linux and linux-tools, we usually have both active branches for both unstable and experimental. The experimental branch is the one called 'trunk' (not 'master', as we're still using svn :-(). I doubt these are the only examples. If there's any question about whether master targets unstable or experimental, that's a good reason to be explicit and not use 'master' at all. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Re: systemd service and /etc/default/
On Mon, 18 Aug 2014 09:31:37 -0700, Russ Allbery r...@debian.org wrote: could we tone down the assumption that people with differing preferences want to break everything you do? It's just a few additional options. And others removed. Or do you actually claims that the systemd migration didn't actually break things? Not all of them, but a noticeable number. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fon: *49 621 72739834 -- 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/e1xjt9v-0005ih...@swivel.zugschlus.de
Re: Standardizing the layout of git packaging repositories
On 2014-08-16 16:28:40 +0800 (+0800), Thomas Goirand wrote:
[...]
If I prefer to use their git repository, and create my
own orig.tar.xz out of a signed git tag, what is the problem, as
long as I use the tag they provided by upstream?
[...]
Mainly that the checksums for your orig.tar.{g,x}z will differ from
those in upstream's signed release announcement, and also that you
may miss changes in upstream's dist-build tooling (though in general
I would hope upstreams maintain a _very_ stable interface for things
like 'make dist').
Is there some sort of religion around tarballs?
No moreso than there's a religion around git tags I suppose--but
I'm not keen on getting into religious debates. The fact of the
matter is that you're packaging software for a distribution which
uses tarballs as part of its source packaging format and has
established conventions around them.
Shouldn't it be the same stuff that git archive does? If it
isn't, why is this the case? Shouldn't one be able to use what's
in the Git repository anyway? Why can't it be fixed?
For a variety of historical and pragmatic reasons, many distribution
channels expect a release tarball to contain some information which
is more efficiently stored in VCS metadata (authorship, detailed
change information, version numbers, et cetera). As a result,
keeping that data in files within a VCS as well as in VCS metadata
is double-entry and more subject to drift/inconsistency.
In this case I think having a dist build step is a solution rather
than a problem which needs fixing. I work on some very large
projects where it was established as extremely error-prone to
maintain this information by hand in two places (not a theoretical
problem but an actual observed mistake made sufficiently often to
warrant directly addressing in our release processes and tooling).
Isn't the upstream git repository the preferred form for
modification, closer to what someone should be using when
contributing upstream?
I think this is twisting DFSG #2 pretty substantially to claim that
a tarball containing a few additional autogenerated metadata files
from a make dist step is somehow less free than one created by
tarring up files directly out of a VCS branch. If upstream's VCS
really is the preferred form for modification (which BTW is
wording borrowed from the GPL and doesn't appear in DFSG #2
directly), then Debian is effectively *not* distributing the
preferred form regardless--the currently accepted source package
formats in fact make that impossible (format 3.0-git went nowhere
due to ftp-master review concerns, and even it still used tarballs
for its underlying file archive though that was more of an
implementation detail).
Why is it the case that upstream prefers that we use something
generated from his git repository?
In some ways it's nice if multiple distributions (most of whom to
this day base their various source package formats on release
tarballs) could have consistent checksums for easier comparison, but
that's more of a nice-to-have given that a lot of them pick
different upstream releases to package long-term. The bigger reason
is that when every distribution picks a different way to regenerate
the tarball they inevitably use for their packaging, they often get
it wrong by reimplementing the source dist build step themselves
without an understanding of the original intent.
Shouldn't all what upstream generates in the release tarball also
done by the Debian package build anyway?
You're free to do so (is regenerating authors lists, changelogs, et
cetera during package build really worth the effort?), but the point
of contention is that if you're not going to use the *actual*
release tarball provided by upstream and are instead making a new
one yourself from the VCS, this is effectively the same as
repacking. If you repack an upstream tarball, isn't it convention to
annotate the version you're claiming on it to indicate it's been
repacked (and include a readme.source file or similar documenting
your repacking methodology)? I'm merely suggesting that if you're
going to generate original tarballs from VCS contents then they
should be treated in a similar fashion as a repacked tarball in that
regard.
Also, what if I need to build a Debian package out of an upstream
commit, because there's some bug fixes which I need, but there's
no upstream tarball available?
[...]
As already mentioned in my message to which you're replying here,
it's understandable that you might generate substitute tarballs
out of a VCS when there is no corresponding release tarball, for
example when packaging development snapshots. However reinventing
upstream's dist steps to make the tarball you eventually end up
using in your source package anyway seems like a duplication of
effort.
If by traditional release process you mean wasting human time,
computer CPU, and network bandwidth, to build old 80ies fashioned
tarballs (that is: with .gz compression and no PGP checksums),
Re: Standardizing the layout of git packaging repositories
On 2014-08-17 16:20:34 +0800 (+0800), Thomas Goirand wrote: But then in which way will you check that the said upstream tarball, without any upstream checksum, is valid? At least tags are signed... You keep coming back to the assumption that upstreams don't provide signed lists of checksums. I would wager that the percentage of upstreams who sign VCS tags are probably (within reasonable margin of error) roughly equivalent to the number who sign lists of file checksums or provide detached signatures of the release files themselves, so this argument seems specious. Also, why the forensic investigation wouldn't instead check that the generated tarballs are really based on the correct PGP signed tags? [...] If there is a release-time build step between the VCS tag and the tarball, then this can become nontrivial. -- Jeremy Stanley -- 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/20140818204725.gw1...@yuggoth.org
Re: systemd service and /etc/default/
Marc Haber mh+debian-de...@zugschlus.de (2014-08-18): And others removed. Or do you actually claims that the systemd migration didn't actually break things? Not all of them, but a noticeable number. (I don't think Russ claimed anything along those lines, no.) Anyway: things get broken, bugs get reported, bugs get fixed, things get usable again; sometimes they get even better than they were. But look, that's the whole point of having an unstable distribution, and a staging area to get the next stable prepared: we can iterate until stuff gets into shape. I'm not sure I see a problem here, except for the temporary inconvenience in unstable which sometimes also affects testing. Happy unstable/testing users are expected to handle such an issue though. :) Mraw, KiBi. signature.asc Description: Digital signature
Re: Why is package X not in testing yet?
From: Sven Bartscher sven.bartsc...@weltraumschlangen.de
Hi again Sven,
Greetings,
If we have a package, which doesn't migrate to testing, we usually
check the Why does package X not in testing yet? page or the PTS.
Usually they do a great job in telling us why our package doesn't
migrate.
But sometimes you have packages, which have complicated dependencies,
that don't make it easy to tell why our package doesn't migrate.
Usually the PTS and Why is package X not in testing yet? fail at
those packages and don't give any useful explanation. For example look
at the page for haskell-hgettext[1].
Those packages usually have to go into testing together with a few other
packages. If it's getting worse your package needs to go into testing
with a lot of other packages (usually if your package is part of a
bigger transition).
If your package is part of a transition you might have luck and the
transition page can tell you what the problem is. But sometimes not
even that pages help.
For that reason I made a tool that takes a package name and tries to
find out why your package doesn't migrate to testing.
When run, it gathers all packages that block our given package X.
Then it fetches all excuses for these packages and throws all of them
away, except those that are identified as interesting. These types of
excuses are identified as interesting:
- out of date on arch
- pkg has new bugs
- Too young
This takes a long time (for me 3 Minutes) depending on your internet
connection.
This is mostly useful for haskell packages, as they have very close
dependencies. However, it might be interesting in any other transition.
The source code is attached and can be found in the tools repository[2]
of the Haskell Group.
In order to compile it you need the following packages:
- ghc
- libghc-regex-pcre-dev
- libpcre++-dev (This should be a dependency of libghc-regex-pcre-dev
but it isn't due to a bug)
Compile it with:
ghc --make reasons.hs
To run it you need the following packages:
- devscripts
- wget
- ca-certificates
- locales (you should use an UTF-8 encoding, otherwise its guaranteed
you will have problems.)
Also you must have enabled the source URIs in you sources.list.
There are still some rough edges. The most notable ones are:
- Most errors that can happen aren't catched. So an haskell exception
will be thrown, which gives not very much information of the problem.
- The excuses are fetched with grep-excuses. So the excuses file is
downloaded over ad over again. There is already a bug with a patch
filed against grep-excuses to fix this.
- out of date excuses are all considered interesting, even though it
would be better to only include those that aren't in state B-D
unistallable.
A bit more detail on the workflow of this tool is described in this[3]
post.
I would just ask one (I hope little) feature, I'm not an haskell guy, so I find
rather difficult to submit a patch :)
I would like to see also this
outputUrl =
people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
(maybe with a deletion of ~/.reasons/update_output.txt)
and replace doesn't with doesn't ;)
maybe something like renaming update_output.txt.{ubuntu,debian} and passing
something like -d {debian,ubuntu} by command line will make this program
universally used and easily extensible to other debian based distros.
thanks again for the nice and useful work you did!
cheers,
Gianfranco
[1]:
https://release.debian.org/migration/testing.pl?package=3Dhaskell-hgettext
[2]: http://anonscm.debian.org/cgit/pkg-haskell/tools.git/
[3]: https://lists.debian.org/debian-haskell/2014/08/msg00027.html
--MP_/ptLm4kgDdV4o5zwF+5AjRiy
Content-Type: text/x-haskell
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; filename=reasons.hs
import Text.Regex.PCRE
import System.Environment
import System.Exit
import System.Process
import System.IO
import Data.Maybe
import Data.List
import Data.Char
import qualified Data.Set as S
import Control.Exception
import System.IO.Error
import System.Directory
import Debug.Trace
data Excuses =3D Excuses String [String]
isEmpty :: Excuses - Bool
isEmpty (Excuses _ []) =3D False
isEmpty (Excuses _ _) =3D True
excuses2String :: Excuses - String
excuses2String (Excuses pkg excuses) =3D unlines $ (pkg ++ :):(map
( =
++) excuses)
main =3D do
package - getArgs =3D parse
output - fmap lines acquireBritneyOut
let bins =3D getBinBlockers output package
result - try (fmap nub $ mapM getSrcPackage bins) :: IO (Either ErrorCal=
l [String])
srcBlockers - case result of
Left e - putStrLn packageNotFoundMsg exitFailure
Right pkgs - return pkgs
excuses - mapM getExcuse srcBlockers
additionalExcuses - getAdditionalExcuses srcBlockers excuses
let filteredExcuses =3D filterExcuses isInteresting $
Re: Standardizing the layout of git packaging repositories
Le Mon, Aug 18, 2014 at 02:16:55PM +0200, Jakub Wilk a écrit : FWIW, rc-buggy is not the codename for experimental: $ wget -q -O- http://http.debian.net/debian/dists/experimental/Release | grep -m1 ^Codename: Codename: experimental Excellent news ! So seems that I have been confused by packages.debian.org (#703237). Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140818212213.ga30...@falafel.plessy.net
Re: Bug#758124: Documenting the Testsuite field in the Policy.
Le Thu, Aug 14, 2014 at 09:36:50PM +0900, Charles Plessy a écrit : Package: debian-policy Version: 3.9.5 Severity: wishlist Hi Guillem and everybody, thanks for adding direct support for the Testsuite field in Dpkg. Here is a patch to update the Policy accordingly. Do you have comments ? Anybody wanting to see the Testsuite field documented in the Policy, please raise your hand ! Have a nice day, -- Charles diff --git a/policy.sgml b/policy.sgml index 6eac491..a8b27e2 100644 --- a/policy.sgml +++ b/policy.sgml @@ -2666,6 +2666,7 @@ Package: libc6 itemqref id=f-Standards-VersionttStandards-Version/tt/qref (recommended)/item itemqref id=f-HomepagettHomepage/tt/qref/item itemqref id=f-VCS-fieldsttVcs-Browser/tt, ttVcs-Git/tt, et al./qref/item + itemqref id=f-TestsuitettTestsuite/tt/qref/item /list /p @@ -2761,6 +2762,7 @@ Package: libc6 itemqref id=f-UploadersttUploaders/tt/qref/item itemqref id=f-HomepagettHomepage/tt/qref/item itemqref id=f-VCS-fieldsttVcs-Browser/tt, ttVcs-Git/tt, et al./qref/item + itemqref id=f-TestsuitettTestsuite/tt/qref/item itemqref id=f-DgitttDgit/tt/qref/item itemqref id=f-Standards-VersionttStandards-Version/tt/qref (recommended)/item itemqref id=sourcebinarydepsttBuild-Depends/tt et al/qref/item @@ -3863,6 +3865,24 @@ Checksums-Sha256: further details. /p /sect1 + + sect1 id=f-Testsuite + headingttTestsuite/tt/heading + + p + Simple field containing a comma-separated list of values allowing + test execution environments to discover packages which provide + tests. Currently, the only defined value is ttautopkgtest/tt. + /p + + p + This field is automatically added to Debian source control files by + prgndpkg/prgnfootnotefrom version 1.17.11./footnote when + a filedebian/tests/control/file file is present in the source + package. This field may also be used in source package control + files if needed in other situations. + /p + /sect1 /sect sect -- 2.0.1 -- 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/20140818224419.GA7618@aqwa.igloo
Re: Standardizing the layout of git packaging repositories
On Aug 17, 2014, at 11:19 AM, Thomas Goirand wrote: By the way, I try to always avoid using master as a branch name. This doesn't express anything at all. +1 In the context of Ubuntu (and when it works wink) I really like the approach taken for UDD branches. I can always branch the version of the package in any series, e.g. $ bzr branch ubuntu:utopic/python2.7 or if I want to get to the version of the package in proposed: $ bzr branch ubuntu:utopic-proposed/python2.7 with an alias for the most commonly requested version, i.e. the released version in the current development series: $ bzr branch ubuntu:python2.7 # gives me the utopic/python2.7 Of course, I can get the version in any other series. I can even get versions in Debian via: $ bzr branch debianlp:python2.7 or $ bzr branch debianlp:wheezy/python2.7 Obviously the details will be different with git and Debian, but I think it makes a lot of sense not to assume what 'master' might point to, but instead be explicit about the series name in the branch name. If it's possible to make a shorthand alias for the most common branch (unstable?) then that's fine too. Cheers, -Barry signature.asc Description: PGP signature
Re: Standardizing the layout of git packaging repositories
On Aug 16, 2014, at 01:15 AM, Thomas Goirand wrote: As in, always use pristine-tar? No! The point of using git packaging is also to be able to use upstream git repo. What about cases where upstream doesn't use git but you still want to use git for your packaging branch? Also, it makes me somewhat uncomfortable to assume that a git tag in the upstream repo will always be equivalent to their released tarball. In fact, it's often not, as is the case with Python packages containing a MANIFEST.in. -Barry signature.asc Description: PGP signature
Re: Standardizing the layout of git packaging repositories
On Aug 17, 2014, at 08:47 PM, Henrique de Moraes Holschuh wrote: It is not meaningless in the sense that it is a widely used convention in git repositories. And that's actually quite relevant. It makes more sense when you're a pure upstream, as master might be where you do all your cutting edge development, and there isn't usually a clear alternative naming scheme (e.g. code names). 'trunk' might be better anyway. But in Debian's case, all packaging work is targeted to a series, so it makes more sense to make that evident in the branch name. -Barry signature.asc Description: PGP signature
Re: Standardizing the layout of git packaging repositories
On Aug 16, 2014, at 04:28 PM, Thomas Goirand wrote: Why?!? Is there some sort of religion around tarballs? Shouldn't it be the same stuff that git archive does? If it isn't, why is this the case? Shouldn't one be able to use what's in the Git repository anyway? Why can't it be fixed? Aren't we supposed to build from source anyway? Isn't the upstream git repository the preferred form for modification, closer to what someone should be using when contributing upstream? Why is it the case that upstream prefers that we use something generated from his git repository? Shouldn't all what upstream generates in the release tarball also done by the Debian package build anyway? This all assumes very specific upstream release workflows. It might be fine in many cases, but there's such wide variety in upstream development processes that a maintainer would have to know much more about how upstream releases than they do now. I think about the typical PyPI package. I really don't have to know much about how upstream generated the tarball on PyPI (*and* signature/checksum), just that they magically did so. The upstream tarball is a shorthand and a very convenient abstraction for the upstream's magic - and perhaps not easily discovered - release process. So yes, please do generate orig.tar.xz out of PGP signed tags, and do Debian git-buildpackage based on tags repository, using the upstream git repository as source. That's the correct technical thing to do, and you wont regret it! As an upstream: please accept progress and convenience. As Debian developers, I think we generally shouldn't be dictating best practices to upstreams. Let them do whatever is most comfortable to them and let them concentrate on making good software! Upstreams have a lot more concerns then how well their branches fit into Debian's packaging machinery. Sure, most upstreams are pretty Debian friendly, but they might have to worry about how releases get made for vastly different OSes (i.e. not even Linux) so Debian can be just a blip for them. I.e. nice if they can make our lives easier but don't count on it. For better or worse, the tarball is the abstracted medium of exchange between upstreams and downstreams, and it makes good sense to have that. (I'm not arguing against using an upstream git tag when it *does* all work nice and smoothly, just saying you can't count on it, and should force our workflows onto upstreams'.) Cheers, -Barry signature.asc Description: PGP signature
Re: Standardizing the layout of git packaging repositories
Barry Warsaw ba...@python.org writes: It makes more sense when you're a pure upstream, as master might be where you do all your cutting edge development, and there isn't usually a clear alternative naming scheme (e.g. code names). 'trunk' might be better anyway. But in Debian's case, all packaging work is targeted to a series, so it makes more sense to make that evident in the branch name. I use master as the Debian branch that targets sometimes unstable and sometimes experimental. If I called it either sid or experimental, it would occasionally be inaccurate, and that would annoy me in a petty and unconsequential way that would nonetheless make working on it slightly less fun, but always branching when I start targetting experimental would be irritating in a different way. I believe that by doing packaging on the master branch, I'm using master in exactly the same way that it is normally used in the Git convention: the most recent development tip, off of which other release branches (if needed) will be cut. It's certainly fine with me if other people do other things, and I approve of the fact that the Vcs-Git header can now represent the branch information so that people can use whatever convention they wish and our tools can still interoperate. -- 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/87k365xt16@hope.eyrie.org
Re: Why is package X not in testing yet?
Hei Sven, On 18/08/14 18:10, Sven Bartscher wrote: If we have a package, which doesn't migrate to testing, we usually check the Why does package X not in testing yet? page or the PTS. Usually they do a great job in telling us why our package doesn't migrate. But sometimes you have packages, which have complicated dependencies, that don't make it easy to tell why our package doesn't migrate. Usually the PTS and Why is package X not in testing yet? fail at those packages and don't give any useful explanation. For example look at the page for haskell-hgettext[1]. you might want to have a look at comigrate [1] a tool designed to answer these kind of questions and provide explanations that are as compat as possible. For example for haskell-hgettext [2] . If you find it useful, I'm sure the authors would be happy to hear from you. [1] http://coinst.irill.org/comigrate/ [2] http://coinst.irill.org/report/p/haskell-hgettext.html pietro -- 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/20140818215143.ga2...@zed.irill.org
RFS Processing Analysis
I've been looking at the RFS process [1]. Some of this was in the debian-mentors list about a year ago, albeit using corrupt data. First the good news: - About 1000 RFS submissions have led to accepted packages since January 2012 - The package acceptance rate has consistently been about 2/3 - About 1/3 of acceptances occur within a week [2][3] The challenge - the RFS user experience degrades quickly after the first couple of days: - 1/2 of all active RFS submissions have no responses, despite a median age of 2 months [4] - 20% of all RFS acceptances happen after 3 months, often much longer than that - For all submissions, sponsorship-requests averages 1 response per RFS-month [5] Also: - For 'rejected' submissions, the first response is typically a drop message with respect to mentors.d.n, at 20 weeks out - The submission rate has been increasing at 40-50% per year The interesting insight is that added monitoring of the debian-mentors mailing list is the wrong way to address the deficiencies - the packages most in need of attention are invisible there. The best way to improve the average user RFS experience is to bypass the list and target neglected submissions more directly. That is not as easy as it could be. The mentors.d.n site shows plenty of information about the backlog, but the main page only goes back a week. The BTS summary shows all open submissions, but sorted somewhat oddly, and showing only the package name and version. Better tools may help. As a proof-of-concept, see the RFS Discovery page [6], which exposes and sorts by comment activity. I find that a better means of finding effective places to respond. mentors.d.n could be a good home for such tools. Should that site, with it's rich structured RFS data representation, grow to subsume BTS as the canonical data source for the RFS process? I used to have a story about one particular active RFS. The submitter never failed to resolve substantive raised issues on the same day, despite delays between comments of weeks, months, and even more than a year. That RFS was recently closed to 'clean the queue'. I suspect that user's opinion of the Debian development process could be improved. 1) http://davesteele.github.io/debian-rfs-stats/ 2) e.g. July 2014 - see 'accepted Packages' http://davesteele.github.io/debian-rfs-stats/getslice.html?start=140417280end=140685120state=open#accepted 3) Where 'acceptance' means that the version submitted, or newer, is present in sid or experimental. 4) http://davesteele.github.io/debian-rfs-stats/commentactivity.html 5) http://davesteele.github.io/debian-rfs-stats/mdbr.html 6) http://davesteele.github.io/debian-rfs-stats/discover.html?field=commentageorder=a -- Le mieux est l'ennemi du bien - Voltaire -- 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/CAOHcdNboSEdkBtS3ZYWaC1bkM=1Nnn+A86nmzLT+hMA9jB=q...@mail.gmail.com
Re: systemd service and /etc/default/
Marc Haber wrote: On Sun, 17 Aug 2014 23:14:33 -0500, Josh Triplett j...@joshtriplett.org wrote: Why a requirement to not improve upstream? Ideally, the Debian patches for a piece of software should trend to zero over time, as fixes make their way upstream. Imagine an upstream author having the cooperation level of the systemd team. Highly cooperative, responsive, understanding of distribution issues, and willing to work with multiple distributions to come up with a good cross-distro solution that works everywhere? This will put the Debian maintainer between a rock and a hard place. When dealing with an upstream that *isn't* cooperative or helpful, sure, you might end up effectively creating a downstream fork. It's unfortunate when that happens in the Debian packages rather than in a separate repository that then gets packaged, but *shrug*. However, the original mail that started this thread didn't suggest that the upstream in this case was uncooperative or unreceptive to patches. - Josh Triplett -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140819044821.GA1345@thin
Re: Standardizing the layout of git packaging repositories
On Mon, Aug 18, 2014 at 07:28:51PM -0400, Barry Warsaw wrote: Also, it makes me somewhat uncomfortable to assume that a git tag in the upstream repo will always be equivalent to their released tarball. In fact, it's often not, as is the case with Python packages containing a MANIFEST.in. I would even be uncomfortable assuming that an upstream tag never moves to point at a different commit. (Been there, seen that.) -- http://www.cafepress.com/trunktees -- geeky funny T-shirts http://gtdfh.branchable.com/ -- GTD for hackers -- 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/20140819055118.gp7...@exolobe1.liw.fi
Accepted billiard 3.3.0.18-2 (source i386 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 18 Aug 2014 13:51:41 +1000 Source: billiard Binary: python-billiard python3-billiard python-billiard-doc Architecture: source i386 all Version: 3.3.0.18-2 Distribution: unstable Urgency: low Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Brian May b...@debian.org Description: python-billiard - Multiprocessing Pool Extensions for Python python-billiard-doc - Multiprocessing Pool Extensions for Python (Documentation) python3-billiard - Multiprocessing Pool Extensions for Python (Python3 version) Closes: 753836 Changes: billiard (3.3.0.18-2) unstable; urgency=low . * Add patch to fix build on hurd-i386. Closes: #753836. Checksums-Sha1: 4e5ce4a848bd4c66ac2711fa1d67cb3a3c2b34f2 2408 billiard_3.3.0.18-2.dsc a3690bf6a789f4bd0aacffeb88ba90b24b80a764 150594 billiard_3.3.0.18.orig.tar.gz 9f441bcfb8939ce4be65f1c76f7f2823fdbd581b 7024 billiard_3.3.0.18-2.debian.tar.xz fc9efee2a664b01b2fa947bcd406520c59e5e4fc 78212 python-billiard_3.3.0.18-2_i386.deb 65cdbf56e5ca9b9a671958d7603f48cccebed106 70946 python3-billiard_3.3.0.18-2_i386.deb c84c937905724af868f9683de0950dcaac3e01af 79252 python-billiard-doc_3.3.0.18-2_all.deb Checksums-Sha256: a653a7ea413425e80bdd45dac581b9012bde63a9b92b2a55e85e8ad445885e1e 2408 billiard_3.3.0.18-2.dsc 59c04036f314c11632a49c15c57735ffb9e111983ee8d15e4d3e188be31583c1 150594 billiard_3.3.0.18.orig.tar.gz 94f0d4d1f437b61b3b2ce2ca331de8f699bd03ec889c25e7679ca7e84d7c3d54 7024 billiard_3.3.0.18-2.debian.tar.xz 841780b5a873534ad4e40ebf98dbff104c5b49eedd6e00f460b8582eb1c01bdf 78212 python-billiard_3.3.0.18-2_i386.deb 4951a73d2b2d9b499c6c9c5f1ba3536f4e630f776c6263da4db0affd0fc2f831 70946 python3-billiard_3.3.0.18-2_i386.deb 44b2bfde6fef95e4317506d42d4231be0fd567e44c8756f570088e48d7ab106c 79252 python-billiard-doc_3.3.0.18-2_all.deb Files: e6e800ae2ee4be9662847649b3e4001f 78212 python optional python-billiard_3.3.0.18-2_i386.deb 4b0afc094d032e4a2fc6058faabe160a 70946 python optional python3-billiard_3.3.0.18-2_i386.deb 123983d7d47d4ef9ac1c0f15dda0a73c 79252 doc optional python-billiard-doc_3.3.0.18-2_all.deb d9058e1f5c4aa4cf5faa2425bbbfce00 2408 python optional billiard_3.3.0.18-2.dsc 96700d11cb4b9d33960eb8e9b55c08c6 150594 python optional billiard_3.3.0.18.orig.tar.gz f8f56312b93e6047fd58165b5bde8be0 7024 python optional billiard_3.3.0.18-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJT8ZbLAAoJEJyE7hq50CY21BAQAM2197hWf4wgXdcqSI2sRTY2 frQu2lXnJ3/ghMPDc74RiMnQvJ6oIc/J1lUxUMC3pK7WA6hIQUY/Ay/Q86gOhBaX S1bI5NoUjv3VxpGzMlJPdt8SFidORZloHPp+EO18pQuFISyaRF5K+ykacsYwG1hU oVl12hhVTjK5etQIzN39ACLQqV9U8LRGyvWUUzvwC1V4frkznmJCSMRMUzoJjio5 w7BR4GXtw7i5Bw7VNJ7DNu4Yg5H/3Y49/BqTyL0gaf189pIzZEWSJeDWj83u6lc/ exys1dqQc/Y0ba8mw9ZN2NCPBEIn2zOPl2D7pzWtmlT4Vy1fRDGCxsMPbqLQAkls vhSbs5oJsyqPyQLD4AWvQv0RU/ppCc//mcVItLJ0DsTvr0ieiEjZs52caanF9439 0w3bOGHdeiyHphyvMjrcatVzC/wIwYEWru8lyrSvKD70Yyy41/Kf7oZODOE8Hfdg qMeiXrZcU8GSSYXDywz64e0lRwKHuPQ62gojrZ6ZD8baYvZD4zK0dVu3SWfsm9E7 HuSSy6pND6gv5GCMVcdaDHjX/eOud4fT6rY8DodzDyLx4+f/3Jgc6bSak3lagzjt SqNxWzj+Z2MNw1xAeaVJk43APKqlNM3OmdLtvB7RDRqoGOKeZNFVbxHH1Yqq2D/A vHchlKXncPq0zXcR8k5n =T/St -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/e1xjg2a-00069o...@franck.debian.org
Accepted upgrade-system 1.7.0.0 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 03 Aug 2014 11:32:34 +0300 Source: upgrade-system Binary: upgrade-system Architecture: source all Version: 1.7.0.0 Distribution: unstable Urgency: medium Maintainer: Martin-Éric Racine martin-eric.rac...@iki.fi Changed-By: Martin-Éric Racine martin-eric.rac...@iki.fi Description: upgrade-system - command for upgrading and sanitizing a Debian system Changes: upgrade-system (1.7.0.0) unstable; urgency=medium . * FLAUSCH: + Added a step to print all dpkg-[bak|old|dist] configurations found. - Removed the 'update-command-not-found' step. * upgrade-system,debian/copyright: + Updated the copyright year. * Bumped Standards-Version to 3.9.5 (no change required). Checksums-Sha1: 64b2c9eddee7385c0789c09088fa136578ed16c3 1480 upgrade-system_1.7.0.0.dsc c5ed155521a934c39a9051ea38748ad18e0f1275 12100 upgrade-system_1.7.0.0.tar.xz e05d841f3519d8188cea0267bc0f390b77d80346 15238 upgrade-system_1.7.0.0_all.deb Checksums-Sha256: 38eba34d501f502cc8b9468c7041edb61740fe8915c6705f57ae120585ddc292 1480 upgrade-system_1.7.0.0.dsc 486f0ad644365c918e7694ff661d24263fbfecb5be93b6e94bf389e93566164e 12100 upgrade-system_1.7.0.0.tar.xz 1b275ba4b0b3a148b8e5d1a881f5e61f2b72fa71349e1d2abaf87a8b58a3f339 15238 upgrade-system_1.7.0.0_all.deb Files: 50a848993d12aacb39dcb9aa195c918e 15238 admin optional upgrade-system_1.7.0.0_all.deb 419458eb0edac5d40e90f1021fd8b34c 1480 admin optional upgrade-system_1.7.0.0.dsc 5c72fcc60c45dba48dedcd91b9e83fd8 12100 admin optional upgrade-system_1.7.0.0.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8ZPfAAoJENFO8V2v4RNH4WIQAIqEMJpPkK/57IyfyW5No5yV xnrUQ9xaJGDtOigWYf54jSGRXjpw8LBSJjCsIaD1NBcgrRQjaIdCcb6+pCiItlNL ft7f9g6YNAwnprsnKvv2sCIew5rAFWwZ2z2/1FhFeTmazNZ+rIkQo/UrverrHb1c dt16bt8oCOcBCeM9xU0LJTVcDp9+Ui6Li9Kkw55l6+r5tWi4TIAUA+seFxcfyBNN fnIJxht3/GjrsTbSr19g7qMfiwr5cgCEKeWbaNq45rMvjuauohdCWdrWB/PriRqC Y18i9eZfF9erBn+u9mtRzm8b7+3daqsfnzc+QZEoSVDk+8JIcpKNPqX5S0+mgQ1K mh0Kx702FWADLhrmLik5J99BHfPohqE5w1gNt6IKEsReNztQS0y+lRLh8w7k92dd 2UdSn5FvyocNecps6zNVAJwvc1JWEWYbNGFord17vpZz168Z51Kk3Kll15GNlcsc aR3nBiJoCj5KZCFjVdZ3zgNX/Oi2XGrNGiZMtDty48TfNqIiWtZ6VXdQxIhTbiq+ p5P90QQ4I+6iN53EM00+bjm4oKLNvG0xmnlYGjRlDJRxHDLaMCscjaRgwJwYzF/3 I7HI1oVLS5I3KmtEkfZUFF045IoETkS7ZvCH4evIC1qBbTOC/wax2XihDtORG360 TFTIIAO932g6/829LkRT =bJ9J -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/e1xjg4u-0006wp...@franck.debian.org
Accepted python-dbusmock 0.11.1-2 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 08:07:59 +0200 Source: python-dbusmock Binary: python-dbusmock python3-dbusmock Architecture: source all Version: 0.11.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Martin Pitt mp...@debian.org Description: python-dbusmock - mock D-Bus objects for tests (Python 2) python3-dbusmock - mock D-Bus objects for tests (Python 3) Changes: python-dbusmock (0.11.1-2) unstable; urgency=medium . * Mark packages as Multi-Arch: foreign for cross-building. (LP: #1357388) Checksums-Sha1: 6c91ab66513f1b2cd02124d5d2b21287406dc5b3 2309 python-dbusmock_0.11.1-2.dsc 3474b56bdaaf856eedec830e2a1abdc7c8a48efd 3488 python-dbusmock_0.11.1-2.debian.tar.xz 28194099cf132b24561a32723c3c6377e1368c2f 49874 python-dbusmock_0.11.1-2_all.deb 48644042513dd5d8e1436906ea41fef3588e7de9 49816 python3-dbusmock_0.11.1-2_all.deb Checksums-Sha256: db38961621c7bf515c5672a038e0ec5bb9b486d90a05d37e1ef9ca68cbff14d0 2309 python-dbusmock_0.11.1-2.dsc 40fd78e320cbb87bb8f57293c548ea61c7218574668f7cc90cd925b52d7be5b2 3488 python-dbusmock_0.11.1-2.debian.tar.xz 5dd71e89a34f125b595f2c4446404e947b233c0c003b5da720be58acdf39673a 49874 python-dbusmock_0.11.1-2_all.deb 0c1c95d7027a42690ca7532f11a2c7bb7e3ed61bf225a271555324ce5bc9ff14 49816 python3-dbusmock_0.11.1-2_all.deb Files: fc25a18ccae10626eb2537fa5efa987f 49874 python optional python-dbusmock_0.11.1-2_all.deb 5f2b220c25dd1b9868d2f3ba9fa32d7a 49816 python optional python3-dbusmock_0.11.1-2_all.deb c59aa56d4300ca30ae4764ccd1ab816c 2309 python optional python-dbusmock_0.11.1-2.dsc efff30b7be11cb6bd0a3e2ac2bab7bcf 3488 python optional python-dbusmock_0.11.1-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8ZliAAoJENFO8V2v4RNHJDIQAJucXECAdqEKCrvEUrLz6yMa xFc0b/gPzq0Ab8TWo71/mbUHjDwLBkgk6YOB2cbQlGSeSiQrCexQCrxNGhPhFGlV hRtfOeRGUTlTusiCMPVRYvUfv7oDNeuCAnCT2bU5SO/UiULOoJQULIf7kofy8Sfq UKQX7J6A3E//W/FtOve89PXhUUYqyd8zXxyEdv/Rna2gDFerTKKexbF1FvAWypEA KfKgWnhnAInSLdHGOC+fwsv2l2sWEegnD4ul5dWX/YttvxoYYA3SqKOz2QRugTbS cRkCnHwHkwWZllBbw3RSMNravqpheug953bFcNXIvo5A2kCiZuiCpbawo2oSE3Sh 5QsJD7wMW2At7ApXKlWPbe4DUfxTfq1NwJk8KnR7UHDH9Rg+wDmTj9F3/mh60dXx WJ5XANku3womzph2sDyy0HFKrpLRiXV2e9QHIKEx3D8u8AFdDBsBepXjKCcsNW59 FHzWOin9GvHmywf6ZhVXZHSZJPF1UKE3vNAg8POMh+Z3NVSvx5RcQzYS1VEQ+MOU ZSt7YXdbJnjA08Jsi5lxIyos7KCj12gIzGmJ7DoRUzBw87t3SpSpZH7EQ87Owc+w G5N9NXhZku/b04JNcxO+kUpW23/5kHPLKiSNOL2Sa07XyLeXpIDIqdCNOGvQPY2b ZS5Eh9hGPnhZ4iUM8T28 =oRNQ -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/e1xjghw-0008iz...@franck.debian.org
Accepted celery 3.1.13-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 18 Aug 2014 13:30:19 +1000 Source: celery Binary: python-celery-common python-celery python3-celery python-celery-doc celeryd Architecture: source all Version: 3.1.13-1 Distribution: unstable Urgency: low Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Brian May b...@debian.org Description: celeryd- async task/job queue based on message passing (daemons) python-celery - async task/job queue based on message passing python-celery-common - async task/job queue based on message passing python-celery-doc - async task/job queue based on message passing (Documentation) python3-celery - async task/job queue based on message passing Changes: celery (3.1.13-1) unstable; urgency=low . * New upstream version. Checksums-Sha1: 53724a1043b8f3d2c4c0c74b49b24410ec26b01a 3050 celery_3.1.13-1.dsc d1ea223fc136298bbf1de4854ddd08be846d2afa 1292738 celery_3.1.13.orig.tar.gz ffb4d5c2006ba34940e846d042e8642d2c1432fd 17384 celery_3.1.13-1.debian.tar.xz 98be42bf1807508e03937484aed445f6a51f9f08 18442 python-celery-common_3.1.13-1_all.deb fbd71d592aa87c154c93261215a8031a4c7aced0 350794 python-celery_3.1.13-1_all.deb 2a2ebbeb9ad5897d9195ed710d4c89fead403e3c 338114 python3-celery_3.1.13-1_all.deb c9259ddfe0e8e753a6100cb8d5451c98d79d8a2a 1392350 python-celery-doc_3.1.13-1_all.deb 6a2d7e12d3d98d95e37b3112fb128883bae175f3 23068 celeryd_3.1.13-1_all.deb Checksums-Sha256: 4ace9b72c78fa5d0a4835809b0ee3308b1761c107b595e6460470a77c461d5fa 3050 celery_3.1.13-1.dsc 04b921326a64f17af5ba9c94e5189a498b36d8c01bebd215d12abeee0f55940c 1292738 celery_3.1.13.orig.tar.gz 3f5d8a0d410112c5e742b81b84296d30016a6293bda68826cfeff6943573ef65 17384 celery_3.1.13-1.debian.tar.xz 7ef9634ce48b988b85faa60d6827f351cfa7186e7621a59585f036936db22679 18442 python-celery-common_3.1.13-1_all.deb 2c19756722232fcf0eeb372a4a83b375fbef6e9d60063d0d8ea487bc96185dac 350794 python-celery_3.1.13-1_all.deb 3ec68893bd12ce0fac1feb4633b90beae9e3053c6275cdc173fa887d90e989b8 338114 python3-celery_3.1.13-1_all.deb 5e3d8497205593efbe2ac16b4aacca94d40062afeb966f772a475e657968597a 1392350 python-celery-doc_3.1.13-1_all.deb 6637859418890df102585a3e8523817d7d4e6c8472f5b279dbcaff4a9c8b5a9d 23068 celeryd_3.1.13-1_all.deb Files: c468854c7f2cc93ebe4067d3441fe38b 18442 python optional python-celery-common_3.1.13-1_all.deb 16a8917cb851ee8426f253a703bd080a 350794 python optional python-celery_3.1.13-1_all.deb a6a2701db243208456f8f0ee16475f88 338114 python optional python3-celery_3.1.13-1_all.deb ed3e163cef8e53fc5c4e5aa31f49d0bc 1392350 doc optional python-celery-doc_3.1.13-1_all.deb cc9d4abb06cf8d80d0075f4120b4940d 23068 python optional celeryd_3.1.13-1_all.deb f5a174ebf4bc9ae368ca0b3c9ca914cf 3050 python optional celery_3.1.13-1.dsc 549aa12b13f77d1363e9087d3deb4742 1292738 python optional celery_3.1.13.orig.tar.gz cadbed59535c36674b8da6ed55719ebd 17384 python optional celery_3.1.13-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJT8Zq6AAoJEJyE7hq50CY2yWYP/ROhin6QN0ovU6d5RgcxvLbZ NGb9DrT7CjwCDDvz+CoN69xL/D1gktzWUYe9bp6cW21FZ6OMwfTmF8rIOe3GVBTZ DAi/sSQEIwPZnYFXUvv13XIYCfayVZq20+IG3aNRcfto5q9kxBY/LDYHkKcnZnDE /B+UWAlH3xGx1FXiJRMYJQUEGkPcnOIfVMkyhNTG/wdwGIKwNC0UXDcgMxLleiKi 1swy+V0DOi4fzxP+pjVrzmHdEH58VUnu+Oem+2iZRtNG+gFnVvPy0pfVxjXVlFS3 e7LoLizeHc/9zOLPj7eq/EYBce+xQxgYOKK7M3eQ+0uhBVe2japPQvYvBtB3ipG5 Xm7U/yH1LpsGmv27vztIw7tFm6ee6N3YbSHWgNVF3gCfeLD6O25uVkzhYUvHoX5F DbMlgnabL0dtjPMEjhbLo48/eHyZ9hNj45osK9vTg1DzxgOFHdvmesbK6we5/FRG WVhKWcSBczpZKZMkdlzHLzwWtasuVFul2ossxpYcuxbUb9IvNmYvvGXfElLt2zYh GcKf3Oq6H7xjqSKJgehAdctfTByLbJ3NZoySMf19iqRywsqS4Ww7EuHknR72nDVk cUGpiYdffDpenMpPvVMTZM7635E2Pvi36dyJvrfXX2SfdijG9avg6og75BYpqOXx r46LwS0ES7TtycXVFW/i =a5/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/e1xjgvm-0001fo...@franck.debian.org
Accepted hgsubversion 1.6.3-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 07:55:30 +0100 Source: hgsubversion Binary: hgsubversion Architecture: source all Version: 1.6.3-1 Distribution: unstable Urgency: medium Maintainer: Qijiang Fan fqj1...@gmail.com Changed-By: Javi Merino vi...@debian.org Description: hgsubversion - Subversion client as Mercurial extension Changes: hgsubversion (1.6.3-1) unstable; urgency=medium . * New upstream release * Add myself as uploader * Remove patch from_upstream__layouts_fix_crash_when_importing_hgext_hgsubversion which is now included upstream * Run testsuite when building Checksums-Sha1: 9d4e30a984f969f6189bb0f5e76972d9694843fa 2006 hgsubversion_1.6.3-1.dsc 249117c80bdec91af7d1accd357f00c68c1a7ce3 279550 hgsubversion_1.6.3.orig.tar.gz a0ee9ef710359aed2ae782c0eb6070bc6fb9cd35 2856 hgsubversion_1.6.3-1.debian.tar.xz a72714c1e2afe400a122af89c451f51009ab4432 70226 hgsubversion_1.6.3-1_all.deb Checksums-Sha256: 94861c66b0414507b76c2412c9be0016b02bc91ea5f930b90df1df90d97d0689 2006 hgsubversion_1.6.3-1.dsc f5aab8b99dbb6ced56b4da945bb837366aadfdaf0ef9a433dc437a0f947a7d84 279550 hgsubversion_1.6.3.orig.tar.gz f0a658481b9e27ee75bba4aa72c4b34f4806d357d7fef09dbd8b4197b4f6 2856 hgsubversion_1.6.3-1.debian.tar.xz d7e09bfef010910cc31f34f4aeb0e8a8d2e6aca40a5e9d8ed9311080d84d102d 70226 hgsubversion_1.6.3-1_all.deb Files: e405a5894f5494dcd1046205b7c7f961 70226 vcs extra hgsubversion_1.6.3-1_all.deb 327751f43c6afb405ab21572cf4798b9 2006 vcs extra hgsubversion_1.6.3-1.dsc d87cab5fd74548965a5028b4c74e11d1 279550 vcs extra hgsubversion_1.6.3.orig.tar.gz 88fa5f87ee89f4c87308d9aeca920987 2856 vcs extra hgsubversion_1.6.3-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8aQ/AAoJEAe0hFJ2jTgk8KwP/3cG8ovfgBNNIrmKYHWFI34Z ZmZFMDWpqWyyGn30QdZTBbcY1QnTfUXRvnUGc4bdPsG33PgXlRCWANHb/mRJkfF3 Gkfc0U1PLdtHcvcKd5YlwXy56QzFRiyToC1G47gl55U5dIfWfCUvgye+XWkKhgBj bVqrwE9xDHpfgfpDTvFeOOgSrUCysBAgnjZZMJCmWucLkzFmzkKAVqbS6c4PC3sh z5Y7l8SAAgqiVKFRFMm18yzi1/9bXK0us7I+PCS/t5xjlQlz8ZCBdJekhE6GBco9 FAuRXyy9Iu/Bli0TzsoEUljLrXkwzyCaygcZycaV1TioVuKpDPeNK8EKHFHIBL9/ DMn2DO6+6c10VKRUsJc8qSWG06FizCnzaZwGHw6fcsusNxN1IOngk6v2/wUFA2Im LMZYZCkOHkp3vt4bzhMQMErVnAVR+5j6ZaNe90AOQT0xNOFfHI2frYvCVFwWIg01 MhYxGLI38MMzY09YutW/i5rAolGojtTBAd3sifXV0l/c9HyUIk2JBrSP3hZ3H87a Ra7a9GafsUCjiUccTlKFNYSDLuvVRjSA+Iz9jINcb8jKS189PhGH9h6YcbRHhBmU iEd1n3L66R1kHSYWbgVptCedQ7vd+E4r9iEx57u75C4cPfiYBETLMhhbN/TrTb4f p2eZ0aiVaiRYARE0n7Iw =vOBo -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/e1xjgyb-0005qv...@franck.debian.org
Accepted findimagedupes 2.18-6 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 09:07:25 +0200 Source: findimagedupes Binary: findimagedupes Architecture: source amd64 Version: 2.18-6 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Ralf Treinen trei...@debian.org Description: findimagedupes - Finds visually similar or duplicate images Closes: 758247 Changes: findimagedupes (2.18-6) unstable; urgency=medium . * Team upload. * Applied patch new-inline to handle versions of Inline = 0.67. Thanks a lot to Damyan Ivanov and Gregor Herrmann for the patch! (Closes: #758247). Checksums-Sha1: a6890fc694c54aad6cb82b239339fbb2c255c427 2150 findimagedupes_2.18-6.dsc f93afed329e07692e3b5e0e612e80d6db876d77b 6708 findimagedupes_2.18-6.debian.tar.xz 2e38bb6365a8d03cbe85005534e29c3995e8852b 32454 findimagedupes_2.18-6_amd64.deb Checksums-Sha256: 3ca724c7a8bdd660bfa7cdb2f67224d10c32733fdac090613513f3b368a65be5 2150 findimagedupes_2.18-6.dsc 6892e81a321834185cadedda84b4c7d95462c21bf76bdfb2cfd1916ef4e4883f 6708 findimagedupes_2.18-6.debian.tar.xz d0972afb1a9080c6e8ce522bb029f159b305406954520905b49699ca2f1f0967 32454 findimagedupes_2.18-6_amd64.deb Files: e17e98671f6b800a53d872f1f7208845 32454 graphics optional findimagedupes_2.18-6_amd64.deb 602e78110bbaa2898da61c44976f2b16 2150 graphics optional findimagedupes_2.18-6.dsc fea9b2c87bb2d0da4d930601d897589b 6708 graphics optional findimagedupes_2.18-6.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8amnAAoJEHRcR2bUys3/qO0P/0XU8HAoKR5dJb/TxdJTkO/q k7Ps9Yf3MFWlWUIJw3VsQ6h8Lk9KU5nTakTW5/d9BIe+vUeqtVkmXEhkuH302nGq lwuxHtDNq4whmUGAEZrEes61lO6htuGgw5e1tJG5JwDMlgczK0aXSqRSXP6WDJNn 7D0Cv1AhVL9GvyZyZ9ZDigKy9mIDgIDDxLQecuLDKXOBMPxpk0MxnEZ5wKsLbDvR bj3r8tWCdAMIRh4LXnGyPWVemp9HuuOswtajkkEYgqiMq1dmahA615TkmHy25ePw LULzhgMwX1bcoZfpqvb5XsCUKlzcgzyhgA7GNxN4dYd+SzkWSDGkOx8zpZ3xJLFN 9jlZ1TU3lbdWyZznD/HZEEd5m3IzS/L87yVMtXagveoO/bsHghrszpVyPjwhU6q1 xz98VZLJP19rAeSn8CJMJgLFPavnI3bQKAn7fu1joxrWksFix/xQzzomJZvU677N 62OomCZfT790jTdiw988Nywldoexq20ccZA13Z68vG2e+Tuw9NEnCutnsL83c2QI bbebmCg1HcaXejMX8kl22m3vIqLHgaXIq3o/l1bUCAzVXCDQ/jy6Zc8PGgn5xIf+ nkj6qxZXWEviOWFsoRB13QdlnjnYGmpi8sQupkOEMyb0/I7O3hIIOlXY4xAoiDVD ViOwFlVzLSEt3Us8BSZa =n9mB -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/e1xjhrb-mh...@franck.debian.org
Accepted scite 3.5.0-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 14 Aug 2014 17:12:34 + Source: scite Binary: scite Architecture: source amd64 Version: 3.5.0-1 Distribution: unstable Urgency: medium Maintainer: Michael Vogt m...@debian.org Changed-By: Antonio Valentino antonio.valent...@tiscali.it Description: scite - Lightweight GTK-based Programming Editor Changes: scite (3.5.0-1) unstable; urgency=medium . * New upstream release Checksums-Sha1: 33023c20beed247e6dcdd7c4326e70926650d124 1183 scite_3.5.0-1.dsc a8c240e8fb61e28ca913b1b82d41036356bf5e12 2265217 scite_3.5.0.orig.tar.gz 56019846050c9fd648e387f9e9d1584808ee4b06 14376 scite_3.5.0-1.debian.tar.xz 1d0c96945d1ed8df20a863ead0d4fede967cba44 1365862 scite_3.5.0-1_amd64.deb Checksums-Sha256: acd992e2df95c893faec69a648c6d1b72340faab9c0a46fa6c393488795d657c 1183 scite_3.5.0-1.dsc bf7260a7538a642ad008db067ddf5f1752c3326059a5a7ae4885f08431f1d0b5 2265217 scite_3.5.0.orig.tar.gz 8a24278df3b356f31bd041d5b1467e8877f9b887c49dcbc183552d966e7c600b 14376 scite_3.5.0-1.debian.tar.xz cd8b1ff163d1bb7f3b8051ec1437e3bc6e830b4292a77cd51b8d25a5406ebff0 1365862 scite_3.5.0-1_amd64.deb Files: 4f2b254c46bd8d3ba038b2650f5718a1 1365862 editors optional scite_3.5.0-1_amd64.deb 0283e50a38cafddb5ba348b1fe32b967 1183 editors optional scite_3.5.0-1.dsc 912f046bd61715b605269ee03ba9d8d3 2265217 editors optional scite_3.5.0.orig.tar.gz 128f1dd678c9826bd1bbe438d2f661ec 14376 editors optional scite_3.5.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlPxrWUACgkQliSD4VZixzTjowCeLjXH3OO1FY9YBcgt7zUVKqXU 7x0AnjbWpk29HuDp15QjTb1uyrMMv1qE =l7QY -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/e1xjhgi-0002nn...@franck.debian.org
Accepted boinctui 2.3.5-1 (source i386) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 09 Jun 2014 09:51:45 +0400 Source: boinctui Binary: boinctui Architecture: source i386 Version: 2.3.5-1 Distribution: sid Urgency: low Maintainer: Sergey Suslov suleman1...@gmail.com Changed-By: Sergey Suslov suleman1...@gmail.com Description: boinctui - Fullscreen text mode manager for Boinc client Changes: boinctui (2.3.5-1) unstable; urgency=low . * implemented human readable values in raw task info window . * bugfix: incorrect dead line time for expired tasks Checksums-Sha1: efd465ccf0e8cf126a094aa495bc3073f752eb51 1893 boinctui_2.3.5-1.dsc 104286734a9bf00b7e0b298ce0fa4c258fc87814 72871 boinctui_2.3.5.orig.tar.gz 05e7ba91c716c607ce6e70d736accee9f5485165 4220 boinctui_2.3.5-1.debian.tar.xz 9dabe5f6ef231061e75a928fd20a74ff56a58eda 84342 boinctui_2.3.5-1_i386.deb Checksums-Sha256: f4bde06506def8160c6c0425b2e4c90a88f3a7ff38fc0d50e77d59c02f8107fc 1893 boinctui_2.3.5-1.dsc d987f9fa9186f3aca6d3a14beb651708cc0e3235f1e80d9a7dbe3c1dd74b820d 72871 boinctui_2.3.5.orig.tar.gz f81ede58d3bfedb46b287b72eecdde3c6143dc7ad641cbbdc0199fed5186b849 4220 boinctui_2.3.5-1.debian.tar.xz 5d43b8680b7841c0f212e8205025e1f63f0382d08ed56b8f48003f548e582cd4 84342 boinctui_2.3.5-1_i386.deb Files: b461879db132a042da996dbe5f75162d 84342 net optional boinctui_2.3.5-1_i386.deb 22f012a71fd235deaf89271cec1b2409 1893 net optional boinctui_2.3.5-1.dsc b4285dc9027e588bd7efdec77a53c736 72871 net optional boinctui_2.3.5.orig.tar.gz 18fa9950455e146e060ee16c557860f0 4220 net optional boinctui_2.3.5-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8b12AAoJEICHjlmDK+wVTFIP/ijvjdOebdPIs+0xYbtDOd0O 1YE7tyeKROPrMjrzRvKaRiYXe/tW3hx7WqId9jWRJVH2BUhQJeL35FHYH/H5wG3B 6mt50Wr/I6FMY9qdcdHv8Ulc0OlrnbGJKuq451d6U3a1ME1LY2vgUntG7eGAsEy/ Xizy+u5iC0xXNg4zwQfQOKFKYFDEzgIEvXqjgkO4MCwVVWbmIsoRQJwK9bCtaYOA fijXLxDT+4hm1j8rYStDPLE/ZobHDDDfxcCv3/nJBtRc5NJX84jj1VW66i6k5+w3 oowD53FzVpYzNY/H6VciPg0Y0lrR5he9gNlJ5VN4LnN3dWO06N2GRvd5b13lCEjL AbkMHrrubgwJ1hwgDz4gsOGYLTfF6uT4KGJF1kZwaoWwKhBEQSFl1Bvh1Oc7U+AS /w1NwQzZQ6NP0Eo3GypXMM9caqtDT9P678z1wBeWLYnophh4v4FQ5RUiY0Bt/qx5 uKev5BaczAFsz8cY8j0Njw8ydKTMBF5LV4QP5lmLxxf1RkbVvIiXujzQ9tN5fSUW Y0aIu/PTimOHBiTQs2RbV+j1qLz6/DSXuqFWIkngw+cW5iNJvtzA5yEdirRvZD6C rPunvRw1g4hK6jcbefCkgLCfJxXBg7BI/6VQLnoDb2FkcePN7lKfFxtfRIcUiUFo kLr7uS9GmR0k9b9o/J+g =0eBu -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/e1xjiqj-0004tu...@franck.debian.org
Accepted focuswriter 1.5.3-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 17 Aug 2014 12:59:45 + Source: focuswriter Binary: focuswriter Architecture: source amd64 Version: 1.5.3-1 Distribution: unstable Urgency: medium Maintainer: Barak A. Pearlmutter b...@debian.org Changed-By: Graeme Gott gra...@gottcode.org Description: focuswriter - Fullscreen distraction-free writing program Changes: focuswriter (1.5.3-1) unstable; urgency=medium . * New upstream release Checksums-Sha1: 1530c3b4797f40c2df53f444709e796c1733985f 1997 focuswriter_1.5.3-1.dsc bee66d52733aff20379a657ec148cdcb86b68d7e 5516486 focuswriter_1.5.3.orig.tar.gz b2ddf5eda550fb54aeabf4aba1532adea03a8990 4072 focuswriter_1.5.3-1.debian.tar.xz 8b811f0c76a6f5cc7f99fe29480ddeb9b3c58a02 2430572 focuswriter_1.5.3-1_amd64.deb Checksums-Sha256: 19e686084fcdfc14acf90988e76479762cce823b34e75da8d754be82fd99ac40 1997 focuswriter_1.5.3-1.dsc 6cd4750a9ba13f8215d9c7e05fb9ad827bf089361faba45863181c656a911672 5516486 focuswriter_1.5.3.orig.tar.gz fbed42866ee7b7927a4b38c08bab51afe5c9e1ae63b6ff7a56d8d1e1f4567fc1 4072 focuswriter_1.5.3-1.debian.tar.xz ac2bbd964d6472c80f6feffd76c35e253f5b34a2d2ab833ba4f232bce2648afc 2430572 focuswriter_1.5.3-1_amd64.deb Files: 953d93975103a7b27c5ab67f586b20d7 2430572 editors optional focuswriter_1.5.3-1_amd64.deb c8784ce4355813720ebb3dd40d089b26 1997 editors optional focuswriter_1.5.3-1.dsc 6765d24108e7b4309ccc71ef063ab51e 5516486 editors optional focuswriter_1.5.3.orig.tar.gz 0c833475e2f01965e696cd5764139c5b 4072 editors optional focuswriter_1.5.3-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJT8bMGAAoJEBJbV0deGQ0Yy6UQALo7zqxtpcekHFncGeJ74ME3 WJUhfqP7qLM8XhDsJWOHDBQR35n6YlvdfTIP4hwRqG6ucLJVTfowi4l1h9Yu31WH 0frC4EzXKqO9L52ghVbJylHuj3Avc/k4wy9w7DSgCpx6xy+idrg1G2hAn5Vfvchj sNbC/ozZtfVqeX1wk28BqX2vYD50oy4WYMdtzWIj9q0+rZ8P3c9jbTJIOgpo38Hd /glWU5wEc0+2lalAEIjg5vVK5zQ7YLQ4z15kRbOOLvQPE/jJhj2IrMSJ7wULF4Zy R06M2wDdZA7jM4MxB3LGSFA1JA58zA4iv97jMIhwzTvJdxFR5073o4Q6mVTm8F9Q B4gXJ8VOMJ/rG7EpXrMlslaQz2bc5kJWd0Wy84NV3xyczjq9LhqnpZ4kQWxiBVaL vATjG9oC8mZ0dGsiKTQytSVV9N6X91mWkp+8HeAWSPAq0nmRtv2uAjaDvOIGjDCn qHjYXlf3ABRvfGpZ91p1RlcmvCZiPigKnrqblen/4bqm40Dal5pHio9YYGg0zUob yNg0z7teou8udgxMI9fylDdGY2DkTiKuSV/CBUHTcSNyVGes1nPcSHioRcPYeuJg /8r6o8Acy2Sml8xJ78313SDqYTrMjbYIqvRdT87yBCEU8wgYkSmck156MQ3Q0tgJ lJwAQExg8XABBlzEoIoH =LdWs -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/e1xjir2-0004xo...@franck.debian.org
Accepted mlpack 1.0.9-1 (source amd64 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 17 Aug 2014 10:00:19 +0200 Source: mlpack Binary: libmlpack-dev libmlpack1 mlpack-bin mlpack-doc Architecture: source amd64 all Version: 1.0.9-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Barak A. Pearlmutter b...@debian.org Description: libmlpack-dev - intuitive, fast, scalable C++ machine learning library (developme libmlpack1 - intuitive, fast, scalable C++ machine learning library (runtime l mlpack-bin - intuitive, fast, scalable C++ machine learning library (binaries) mlpack-doc - intuitive, fast, scalable C++ machine learning library (documenta Changes: mlpack (1.0.9-1) unstable; urgency=medium . * Merge NMU (thanks to Gilles Filippini) * New upstream version * Update patches; most are merged upstream * Paatch somme speling erorrs Checksums-Sha1: 7a60406d97a0bf096a27ebbe2fad4e7cf81e7a9c 2257 mlpack_1.0.9-1.dsc 54e1958fc558b55625a7a52d2064420eb88c1ac1 1234513 mlpack_1.0.9.orig.tar.gz a8817496006a4286b6281b1e34f504a78351b4eb 5428 mlpack_1.0.9-1.debian.tar.xz ad490882d31f1cf095edbb3855df30291a99ed89 202670 libmlpack-dev_1.0.9-1_amd64.deb c5f171458e3936426b8ff3deeb93ddf9ed77c501 327410 libmlpack1_1.0.9-1_amd64.deb 9bb1e8d6c0d55beda25b360d22fef77678ca2150 1002846 mlpack-bin_1.0.9-1_amd64.deb f909fc912bf855bf3e01197c81908749a540a5ba 51567252 mlpack-doc_1.0.9-1_all.deb Checksums-Sha256: eaa2083fefe409f917f357e3fc61985eaeb164348ce76bb833aa5b11c17e5720 2257 mlpack_1.0.9-1.dsc e76b3ed0e4667b6f6f003e48aa946a97c500a4b78b10721884b20e1466d64216 1234513 mlpack_1.0.9.orig.tar.gz ddb716abc16a1ba8f52ed6375dc30e77e59a4fbf245782b3be7ee68129f56095 5428 mlpack_1.0.9-1.debian.tar.xz 8bb0e16ad1f28bf1ef81ff722bff956d82855e85084a4aad799cb2aac3271a08 202670 libmlpack-dev_1.0.9-1_amd64.deb 3e067ed8919e5f26bcae2800921db84d870c92355d7962beb133baf8b18f8cc7 327410 libmlpack1_1.0.9-1_amd64.deb e0f6446041e2503c709a3bb684c8a13a097cffd31ac7e0fd492856f94f97a9d6 1002846 mlpack-bin_1.0.9-1_amd64.deb 4749ab9c3c76da4c24044b57d05aea74d742f068d58dd2b330c1f3771174b86f 51567252 mlpack-doc_1.0.9-1_all.deb Files: 48644b51c28c839dc95c804331c423ac 202670 libdevel optional libmlpack-dev_1.0.9-1_amd64.deb 25c45c1e36fb220193a8d74f8450337b 327410 libs optional libmlpack1_1.0.9-1_amd64.deb 4d78b932b623ac7b6065fb8d14609302 1002846 science optional mlpack-bin_1.0.9-1_amd64.deb ef7550551a752e04a2d0711220dceb60 51567252 doc optional mlpack-doc_1.0.9-1_all.deb 41bf3c16538b4683b2120c2196bd8e6c 2257 libs optional mlpack_1.0.9-1.dsc d32b7e3f3366e8ff06094853251f7710 1234513 libs optional mlpack_1.0.9.orig.tar.gz 216ffef6db71d6bc64106e1f88dad063 5428 libs optional mlpack_1.0.9-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJT8bAvAAoJEBJbV0deGQ0YLhEQAKDrsuioqQpEfUFh3IHHE0Xv K6P4YRk194Gml7svx9ootaTG+zfbWOD+WMDUNrI7NKN4wGxVwlgEdarWFwqt1OkT bG3r/89gfQAP6az/nBiYLsHu2kTREBtWCbWwdEMmSXG3HYVmgzzs1KWBaH9+PBY9 QcvjpIoLgZNi2yXdC64xkuB3uQbXiK35Wds0K4PrGSKbYc+A5WAiX/vMOrV8s06A wscJga4/TAxYtQKUcpzouAuGLH9N5tj/EHnOAvmpkDdEZgYt4mUgQhwWN44puThW 1anjs1rZxUTI/L1CTdpr5uPIrHH93zH42bSyhvzml35yzpG591IgFMKqVYgN0N1N JuyrAr8e00vLWkGcr9oTb4HyS9BfZXhE+qpwodJkQByuBP/pL2vxK5nvLt//xO1B 6gMCiAp8FmEFQ6PvMzv5DyVDSSE8G5nqCSX/idbHJf51TuSALzuzOPHypcy0+/vz kRwfCXv6gcP8hMnHoorJlxxMoQBwVsovCfAd4MV/V6JTAgzmXo3ZS92Kfn2/3aIM y/+UotxTn4f8KyB9G12B9f8xf/CnstgzWVYQQqIvdJ9IG0FcEW9KhfcOu4Vxz02E 6bD0uBrAyyCNhckahhbsilSVZVaVBluU3+lHIDsODisIR1PP4W8XBWnIZUu+/9di DHMQ0W1GZBD+aRXF5yiy =sm4I -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/e1xjism-0004yo...@franck.debian.org
Accepted vidalia 0.2.21-5 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 14 Aug 2014 11:32:11 +0200
Source: vidalia
Binary: vidalia
Architecture: source amd64
Version: 0.2.21-5
Distribution: unstable
Urgency: medium
Maintainer: Anonymity Tools Debian Maintainers
pkg-anonymity-to...@lists.alioth.debian.org
Changed-By: intrigeri intrig...@debian.org
Description:
vidalia- controller GUI for Tor
Changes:
vidalia (0.2.21-5) unstable; urgency=medium
.
* Put under the umbrella of the Anonymity Tools Debian Maintainers team.
* AppArmor: allow Vidalia to browse directories up to /{var/,}run/tor,
that contains the control port authentication cookie by default.
* Adjust-filename-of-the-cookie-authentication-file-to.patch:
new patch that adjusts the filename of the Tor cookie authentication file
to match Debian's default.
* Update README.Debian to match default location of the Tor authentication
cookie.
Checksums-Sha1:
58f58138c4c482dd1c7d0620e692ba08bb2a3b32 2061 vidalia_0.2.21-5.dsc
4347b09d0c0d056429f4fad79e05c1c3d19053cb 28764 vidalia_0.2.21-5.debian.tar.xz
1d12a56f6873c7a217c1882c6924b40db420b701 2500084 vidalia_0.2.21-5_amd64.deb
Checksums-Sha256:
18331c4d2d9b2f052fbe8c4f2f3d1caab8450cca7a637ada2599b9667496e65f 2061
vidalia_0.2.21-5.dsc
d67f74d0523e4e7cbc2c878c6bded542996f29ea7d25c6587c5c122fdb25f254 28764
vidalia_0.2.21-5.debian.tar.xz
82d045fe207f76f6593656d6fd6d824c7742da31a9d2522155caceeb43352949 2500084
vidalia_0.2.21-5_amd64.deb
Files:
254fe203af807c576c311d4be62407e5 2500084 net extra vidalia_0.2.21-5_amd64.deb
78fed76928e50a17418b27eb1e5d4609 2061 net extra vidalia_0.2.21-5.dsc
74aff7f23fc41c74f4fb76993b83be20 28764 net extra vidalia_0.2.21-5.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIcBAEBCgAGBQJT8bbOAAoJELrOFdKldJj/9a8QAM0+hfy/YE4C/FzQX2d0hMBK
2znX2dmto5ZyBeqwwy+ktpXx6PR5O4ddrJaykEKBMcD8BBaem6HaMYwtQLuzl1IK
5ErailHWVpBupxl2vBWoqSGf8fZstuGizERWjdacNHG9AYetj65pNRWYkeHuSIGY
Rz6zv7d96B4X2NXk3CaMBOus0uPjeTay0ZKsk+Nkn3W67WtC7Z66sK62wf6uQwKt
mIMY8wlwFvi913vUgmQ6MOogHrQeVoTRZdYlkFVqvUt8IkDxVCMh9iblkHf2nqnn
NWujXZy3dgngan73EmqxXxTjqJKpUVZDNXJtgC53Ef00ZjqVP2NTcoc7znj/3A0i
V8Jp3zgTiYilTqjR6WHDybfhXI/h5noF/mpHJPI6RTNC6T9BzNA62ergnon/s2uX
xbOnW+E6k2zx1wzLM8UTgGypxtH8cwJwaZuermvvu7qOXqm3MneSukQElQHdA1MA
QYPPzs5t1Y7lrNOjWPBciqg73xEfnrgJcMbVc96sEu86olmp1trGBl3NUs+PrG/d
qVRO1YUaa52OHbRvo84Bxye3t1aIU+WDAsz73GxTt2Tc/MnA94O54Kzs/mK70wj5
StM2hKiVBPtTSTek7OHLV6ENeHfFWlhk6Qhyr4vfJ9PwJ+TuEgTR4ExFoh7RHgL4
mSir2k2cKZmP4jqHnuoH
=xnnA
-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/e1xjitg-00053k...@franck.debian.org
Accepted python2.7 2.7.8-5 (source all i386) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 18 Aug 2014 09:43:43 +0200 Source: python2.7 Binary: python2.7 libpython2.7-stdlib python2.7-minimal libpython2.7-minimal libpython2.7 python2.7-examples python2.7-dev libpython2.7-dev libpython2.7-testsuite idle-python2.7 python2.7-doc python2.7-dbg libpython2.7-dbg Architecture: source all i386 Version: 2.7.8-5 Distribution: unstable Urgency: medium Maintainer: Matthias Klose d...@debian.org Changed-By: Matthias Klose d...@debian.org Description: idle-python2.7 - IDE for Python (v2.7) using Tkinter libpython2.7 - Shared Python runtime library (version 2.7) libpython2.7-dbg - Debug Build of the Python Interpreter (version 2.7) libpython2.7-dev - Header files and a static library for Python (v2.7) libpython2.7-minimal - Minimal subset of the Python language (version 2.7) libpython2.7-stdlib - Interactive high-level object-oriented language (standard library libpython2.7-testsuite - Testsuite for the Python standard library (v2.7) python2.7 - Interactive high-level object-oriented language (version 2.7) python2.7-dbg - Debug Build of the Python Interpreter (version 2.7) python2.7-dev - Header files and a static library for Python (v2.7) python2.7-doc - Documentation for the high-level object-oriented language Python python2.7-examples - Examples for the Python language (v2.7) python2.7-minimal - Minimal subset of the Python language (version 2.7) Changes: python2.7 (2.7.8-5) unstable; urgency=medium . * Build-depend on dpkg-dev (= 1.17.11). Checksums-Sha1: b93ca39e3903eefd203a42620e518d6d2ec86e08 2562 python2.7_2.7.8-5.dsc 22a5c788c070e6ad03aefab47f8d79d77bfb1b9c 263939 python2.7_2.7.8-5.diff.gz b55ecc6223b927dd9e9e1b8baf4b19158f06ef5c 592374 python2.7-examples_2.7.8-5_all.deb 2892cacd84a1e3279910110b78321728468a4365 2672882 libpython2.7-testsuite_2.7.8-5_all.deb cce57cc609a84ee44ba7df2d9fa19a0d208c0983 294168 idle-python2.7_2.7.8-5_all.deb bca88b43595f2e00cea6f2eb68903749ec026ec8 4290438 python2.7-doc_2.7.8-5_all.deb 95e453264e32b25bc482ec19921b9abd1c75a90f 243622 python2.7_2.7.8-5_i386.deb ccb35fb71f94f15718ea97bd7968a4735aff1cc7 1891822 libpython2.7-stdlib_2.7.8-5_i386.deb a02984aa4895ed597e2d505c34a501cdcb05b338 1366712 python2.7-minimal_2.7.8-5_i386.deb bb202a3d0f158f906c53540a312433356ac4eebf 348860 libpython2.7-minimal_2.7.8-5_i386.deb 38c332afdef8e2d4d39289197c9ff87cd53495f1 1073496 libpython2.7_2.7.8-5_i386.deb 5bc704fb2310500e72d896e1d6f0e46e484400de 276224 python2.7-dev_2.7.8-5_i386.deb 6c27d1758404f0fef7daf2ec2bfa10a13c959615 28697700 libpython2.7-dev_2.7.8-5_i386.deb f1d93b4a365c771d14d7ec853a1a29c6396fe01a 5382738 python2.7-dbg_2.7.8-5_i386.deb cd70ffdac5a87a4d19f6ab70648af3f5a22a0997 3689220 libpython2.7-dbg_2.7.8-5_i386.deb Checksums-Sha256: 13e85b77ebc98600383c33322a24be210c8cfb588fe5feb08fa8cc7540caa9ca 2562 python2.7_2.7.8-5.dsc 7d98a7cd4c9c133e53ecd59a0eaa0c2f53748f1a46fd2f0c7ae6c84f09aa04b3 263939 python2.7_2.7.8-5.diff.gz 9d8aeb731cc8de4e4e9432de8595e8296b8909ff667f0411d65a8c1ad36d4c5d 592374 python2.7-examples_2.7.8-5_all.deb 0e421163ca39e362516b37a1f98cce7df22d3c711939b2da408c40b523129c41 2672882 libpython2.7-testsuite_2.7.8-5_all.deb 276878bb36027e83de9ead63a3b1dc1e066c1d76aa09646c8acdcccb2dc5bad7 294168 idle-python2.7_2.7.8-5_all.deb 8f9f3f9e271852a4bf9dbd4dc7e9a725251ac4a917868cc2484958e8c0954d66 4290438 python2.7-doc_2.7.8-5_all.deb 879f034d59ff35874831bfef3dd7e7ef1583de4926cf4164762c9f788c814720 243622 python2.7_2.7.8-5_i386.deb a837d0acf6665404463d8e3ecb357b39b10510e3e8e976324916bc4a48540bc5 1891822 libpython2.7-stdlib_2.7.8-5_i386.deb 2dd2efa052f8982b64c75f79e522e2d1ab5911b640e5cc3144a44d441fab0744 1366712 python2.7-minimal_2.7.8-5_i386.deb 94fcd803c2a75650088553631ff8b5e34ef9d98061dad25720f118c21f2cf68b 348860 libpython2.7-minimal_2.7.8-5_i386.deb 8cdce507848e0666738ac05917a5da84dec2bba1085975246460a17293e00a10 1073496 libpython2.7_2.7.8-5_i386.deb 248a6e415a990c8c5ccdc4b4d89c979b719c16f09ed02a2973b0e3f6a386dbe9 276224 python2.7-dev_2.7.8-5_i386.deb 95c753476071bcec01629ea1fa18907712ecf5e812e8ed0e7b278597dd1ded02 28697700 libpython2.7-dev_2.7.8-5_i386.deb 4f6079687a10fd740616f4ec30892e38052c83239209d36090c31c1cad3ea4f3 5382738 python2.7-dbg_2.7.8-5_i386.deb f36afbdb7b58e9717905866abaac6c3ea5cc096f1f94664ec81c2e749e910b89 3689220 libpython2.7-dbg_2.7.8-5_i386.deb Files: f84ba9303944979dbbde15e5ef886ef9 592374 python optional python2.7-examples_2.7.8-5_all.deb f588b08ac205db98de712b743358f918 2672882 libdevel optional libpython2.7-testsuite_2.7.8-5_all.deb f9d33022956da50d16f93bbaebc03b7b 294168 python optional idle-python2.7_2.7.8-5_all.deb 32df5b9b32f1152ec9688df0865a944e 4290438 doc optional python2.7-doc_2.7.8-5_all.deb 2fc0da4d042c759dff068905258b39ba 243622 python standard python2.7_2.7.8-5_i386.deb 1c07f02b0e263ebbe4e649756c4877f9 1891822 python standard libpython2.7-stdlib_2.7.8-5_i386.deb
Accepted libdata-streamdeserializer-perl 0.06-1.1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 09:22:36 + Source: libdata-streamdeserializer-perl Binary: libdata-streamdeserializer-perl Architecture: source amd64 Version: 0.06-1.1 Distribution: unstable Urgency: medium Maintainer: Dmitry E. Oboukhov un...@debian.org Changed-By: Damyan Ivanov d...@debian.org Description: libdata-streamdeserializer-perl - non-blocking deserializer Closes: 721418 Changes: libdata-streamdeserializer-perl (0.06-1.1) unstable; urgency=medium . * Non-maintainer upload. * patch t/10_memoryleak.t to skip all tests if AUTOMATED_TESTING is in the environment. Fixes an intermittent failure during package build. (Closes: #721418) * High urgency to help the perl 5.20 transition Checksums-Sha1: 3c917875abc24907fa174e196236d5d6f0e1e893 1996 libdata-streamdeserializer-perl_0.06-1.1.dsc 6f55e2688127033e6a006108213b7eabb2e97ef8 2332 libdata-streamdeserializer-perl_0.06-1.1.debian.tar.xz Checksums-Sha256: 1c039559eddefb75374758142454a18477089a815c72f53ea6418fbc7ac70cf2 1996 libdata-streamdeserializer-perl_0.06-1.1.dsc 66df2bb397bba90cc022176a676684c09075ed97fb2020dd470223cf29ef23dc 2332 libdata-streamdeserializer-perl_0.06-1.1.debian.tar.xz Files: 7f7c1601ca604feacda2e10493021a68 1996 perl extra libdata-streamdeserializer-perl_0.06-1.1.dsc 1be9a7ffc6a19e829d6e682e05d50a01 2332 perl extra libdata-streamdeserializer-perl_0.06-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8cf3AAoJENu+nU2Z0qAEXtcP/2gFa72W0XSDrkgL3H70U5Q7 Cn7S2h9yQGQ40Q98UKkhasMMRNP6X1I5SDFRbUuZCuJ46FHgSerADGG+/npck8Ak 0y/Dh/cnRQlY0ERD6gRpQ4rqPLmirLXaUjpKe92Nz0MlVytlPx2HOEE3iuPQ9KFO zXiHN6cwP0OJYmVzN0TFbsmVNlWQHLzzAGJgBIat3WI5Z06zAWQWgfiEeW+0HmdP J9bHYbMVLnuxO/mJeCx/t/oE13zBbR2yA8b/LJggq2+QAvHOvdiM+Um/Linr/1Oh ArYyGIxsdwj8decl6VW6Sn1i+tUiyegg5k8H4yCL73Be99Zb+ZlWobShYkfZ8/iS AQsVNi+JdibkyFkP6eq8NfQl/+a1TPtoJV3zm6JHuNfwEzwbkPDAvr7clvxO18tU Cg2a1G3lW5W4PniQxVX+g6ncMnspiZCYyeCKDokreDoNrfe+5YqhfaiCJ9tY+c0N CJcIJN3HOd75fEKtBBaT2ZqBG1hXrMidZTXNdVFU67alkd5EeNck0hT5DK6tIw0D w/QYVMZ9vIYSOdQstGQUlAIut+XxYx7Jrkszs7WGPSUujelGF1NzJOnpA+kGoG6r BGXJGpyvpD4SMQqasmWr/egsIdImmIMXzG+6ZVdX1GfLSY+DbpEc8F6vSKP/mm66 IIxCrnF4W9VplVzlBgPm =blWf -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/e1xjjkq-00058y...@franck.debian.org
Accepted vidalia 0.3.3~alpha-3 (source amd64) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Aug 2014 11:08:06 +0200 Source: vidalia Binary: vidalia Architecture: source amd64 Version: 0.3.3~alpha-3 Distribution: experimental Urgency: medium Maintainer: Anonymity Tools Debian Maintainers pkg-anonymity-to...@lists.alioth.debian.org Changed-By: intrigeri intrig...@debian.org Description: vidalia- controller GUI for Tor Changes: vidalia (0.3.3~alpha-3) experimental; urgency=medium . * Merge changes from the master branch (0.2.x series, Debian unstable). * Refresh quilt patches to make them apply on Vidalia 0.3.x. Checksums-Sha1: d71705da792b36e52f7459dbf37db92dcd94662c 2096 vidalia_0.3.3~alpha-3.dsc fafa3f560c8700260f403bafe95dba31b19dbada 29340 vidalia_0.3.3~alpha-3.debian.tar.xz 8693e2c5e5d92d9fa0a442a23e01e2d0a207c5a1 2327314 vidalia_0.3.3~alpha-3_amd64.deb Checksums-Sha256: 4daab0b18f3f80f325adaa663b36df8ee886da9acb776440d9c12a95e6fe5671 2096 vidalia_0.3.3~alpha-3.dsc f0ba29f91d957644ec6fb5c740d7aee27e8fb3e30cf87098d68fdb96b5b2a18e 29340 vidalia_0.3.3~alpha-3.debian.tar.xz 7ba6026fd707a00d37ae59d4de3eec19a6eb81d03fd8608cfe44a984878487c0 2327314 vidalia_0.3.3~alpha-3_amd64.deb Files: 292db9b3e4940807439e64e50d67a284 2327314 net extra vidalia_0.3.3~alpha-3_amd64.deb a327649f90dff3f197a0970410513ed2 2096 net extra vidalia_0.3.3~alpha-3.dsc 738812ea6d1a31c24cd53ced157c52e6 29340 net extra vidalia_0.3.3~alpha-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJT8cZQAAoJELrOFdKldJj/KMUQAIlMA/hMtbDzHhQ8qqdxDsV8 nlLWP3plGGT8dmglnPRE6z9sqVqFsllUproQKDO9xtkxXxsPc9NZmPflT6IIhqOu H5npa1ub40bjrMbq4kqEOXHMH7F4Gxu0W+s4ljZiWWPTt3l+qxXRRsMYW3a3HEq1 awCfYvr01w5QcViAsnbwuSDlBXpzvC/RsjnH/0BbVHuRGW0ZARu1yZwPv5xc4Hwx X5OEK2xpP9IfabpdAEjmKOzPfFZldCw2W3O0Tn82CsBPAqBdEjAJTZvQNr8FLV+c kupyOPkd9FfhhLtK+1QS4n2sI26SelJ/zKZWLl6uNLTbn4zUH5c6ZIIYzOwj1OFE +FRxMDNzCy730KjMMLe7OGTk7eGL1BYnBcgxoN5xVCf4MW9TMjFbFay8dq4BB+Vu Y+jZO5ACENTqV+k5HqaJRqLkikNPrY6Qqs6kcktNW9rqAq/ktBtJkw+yspOT4CoJ oxTpT8KdPlRUMVr0A90BEiuZa2M9UZAeAd0XHyVdl/J6d1+2B14g7sUrnAZsPd+M Td52k87Z2wDV3FkzBYsdZ/px/mU9OVt7lLhTnaPUJYKhi4PYoFaPEJAPVpMXAbN5 TGl5z9HhRxpi9RMDlqApqGPfWgt/NVr+snTEdjaJanLfC9N8GT2UEzgeWi0Ghywp psaGQ+1XXg0rt5icDlB0 =7E1D -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/e1xjjmj-0005ny...@franck.debian.org
Accepted txtorcon 0.11.0-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 12:33:44 +0200 Source: txtorcon Binary: python-txtorcon Architecture: source all Version: 0.11.0-1 Distribution: unstable Urgency: medium Maintainer: Jérémy Bobbio lu...@debian.org Changed-By: Jérémy Bobbio lu...@debian.org Description: python-txtorcon - Twisted-based asynchronous Tor control protocol implementation Changes: txtorcon (0.11.0-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: b8dbb2e270e95c01629bd7aa9d31bd1d04e07453 2039 txtorcon_0.11.0-1.dsc cf1d395a4463e84df9c406019e08b092a03048d4 192742 txtorcon_0.11.0.orig.tar.gz a6517e51b727c7f3e6eeb23e12709f9b2cbff83a 4992 txtorcon_0.11.0-1.debian.tar.xz c3ddf42d4a3123c389942e49d1f71f01dcb0d34a 126182 python-txtorcon_0.11.0-1_all.deb Checksums-Sha256: 28f6bcbe9263d45af60c1f3b7d29c07480911fe1c098deeca6773a2bb2be8369 2039 txtorcon_0.11.0-1.dsc d2eecaa504b37b0859ac37bbc81cf13a5f668ff35f1028d83c7cf7f4838dadf9 192742 txtorcon_0.11.0.orig.tar.gz 12a0ffdb6fbf339d4c80a702e1f6a58fc103fe2970fc45ee5e0e6f51a9ab4061 4992 txtorcon_0.11.0-1.debian.tar.xz dd2a357105e8d91a76e637d4ce23a79ea08d0e32c9a865045ce082566ba5841e 126182 python-txtorcon_0.11.0-1_all.deb Files: 13106bb8adb951b655cb4fef4e5597e5 126182 python extra python-txtorcon_0.11.0-1_all.deb c28895443650e79a2633a4d1cded61b3 2039 python extra txtorcon_0.11.0-1.dsc 30febce001f7aa46070dccb89618e0e2 192742 python extra txtorcon_0.11.0.orig.tar.gz 63e954ee618bbba2a4ee06d037e15758 4992 python extra txtorcon_0.11.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJT8dgQAAoJEEgU3sIrMHw85x8P/j7ivTGd9fOj+Oku4U3mqNCF K2BzQIcLkV/W9CVnwdlQAEkEBbnQmaMuAU/BT8BLsU6Rlm+z2sK/Mfb0bsVM7Jgx Q8pNq/7/ME3IPojyOTBOdI2jZsyaaNZp8GQT0pRsKavfVy/8rdb7uewsGLpw9FPZ d+KBgcD8w17FFWNa3WUCHGHY6qP9F/I7jwBBwzmIHd4GLvjEK40VKXES8f0KKnRF sIrCeo8rCdWLrU1PA7PWf85jEitfln+tNjByFUA94wuGak1WkgpBhQHO1UzcMEly VTvYoMLo3tRuAglNQfnwV3xRFlORSe9HiiTc9IwD/fRajsOUMy1Huukg2ZwCow93 RLEO/eeh+b3jGzqtcIW1yvAJi8ReJphRbHq0d3XtLAusu0ydHKYinAtGxsRjzaQ9 zYT6J1WigLUMb1CT4skKw/n7h6Q3QnCaD4OIycfrTfano2IWumgSJ2ByGA3yAH7l fhaW2zt5d6HOyCZGHwGJUdtEDAEhjRgIlwPo5f15BIBPz6lGtBVd4nErrMafEitu 1X+BCLuYz/H6RXoQWn1Z5R2aH9ds0KYQf0T1+BFIDBaGaN3ExV4J2vTWURt9Vmbv R1NX0m6/JqnClSLLS38f0jxIY2ZQOmrzSHE33gfg/aRQV3W6nmdscM1IP0z/0Lc3 A7stS9aCmO1y4XAdHftF =VaNf -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/e1xjkjl-0002ak...@franck.debian.org
Accepted python3.4 3.4.1-10 (source all i386) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 18 Aug 2014 10:00:55 +0200 Source: python3.4 Binary: python3.4 python3.4-venv libpython3.4-stdlib python3.4-minimal libpython3.4-minimal libpython3.4 python3.4-examples python3.4-dev libpython3.4-dev libpython3.4-testsuite idle-python3.4 python3.4-doc python3.4-dbg libpython3.4-dbg Architecture: source all i386 Version: 3.4.1-10 Distribution: unstable Urgency: medium Maintainer: Matthias Klose d...@debian.org Changed-By: Matthias Klose d...@debian.org Description: idle-python3.4 - IDE for Python (v3.4) using Tkinter libpython3.4 - Shared Python runtime library (version 3.4) libpython3.4-dbg - Debug Build of the Python Interpreter (version 3.4) libpython3.4-dev - Header files and a static library for Python (v3.4) libpython3.4-minimal - Minimal subset of the Python language (version 3.4) libpython3.4-stdlib - Interactive high-level object-oriented language (standard library libpython3.4-testsuite - Testsuite for the Python standard library (v3.4) python3.4 - Interactive high-level object-oriented language (version 3.4) python3.4-dbg - Debug Build of the Python Interpreter (version 3.4) python3.4-dev - Header files and a static library for Python (v3.4) python3.4-doc - Documentation for the high-level object-oriented language Python python3.4-examples - Examples for the Python language (v3.4) python3.4-minimal - Minimal subset of the Python language (version 3.4) python3.4-venv - Interactive high-level object-oriented language (pyvenv binary, v Changes: python3.4 (3.4.1-10) unstable; urgency=medium . * Update to 20140818 from the 3.4 branch. * Build-depend on dpkg-dev (= 1.17.11). Checksums-Sha1: 4f079e735f207c3899af3b9727ef94aa1ed70281 2591 python3.4_3.4.1-10.dsc 481a97a7b75b31676ac205527086735702001880 1018331 python3.4_3.4.1-10.diff.gz 631d44e7fea8d7a8cc5805f6358aa38d6779c994 390898 python3.4-examples_3.4.1-10_all.deb bd3ab646b545c863127218104813d04f2b7ec9de 3012164 libpython3.4-testsuite_3.4.1-10_all.deb ce8f764e3cec11da82c9fa69f6511771dd0789a8 81360 idle-python3.4_3.4.1-10_all.deb 9f52e43ed7dabcb61c95dbe9f8ead2ddcfae3ca4 5240784 python3.4-doc_3.4.1-10_all.deb 518ee1664b3832533b42e413c36eee00e0291aec 201266 python3.4_3.4.1-10_i386.deb 3058003bb03f0d2061734a970bd37b35a03871b1 5448 python3.4-venv_3.4.1-10_i386.deb d891260494fd66c693b646585a97878caa2e40e7 2092074 libpython3.4-stdlib_3.4.1-10_i386.deb 8333f898745ee277d1b615a2f8d1ec0fbfc0f49b 1638014 python3.4-minimal_3.4.1-10_i386.deb c774c1d7f5ae44a7231af06f669cc97293b986b2 491262 libpython3.4-minimal_3.4.1-10_i386.deb bb25272b03903ad9739ef2317e7dbac3016c3ac7 1319514 libpython3.4_3.4.1-10_i386.deb 58597beccc7cd2f7d22fbd68bfd3945c5e521d91 418358 python3.4-dev_3.4.1-10_i386.deb de65071fb8ad4e2fa7d80fc4ffd570163aadc439 39171990 libpython3.4-dev_3.4.1-10_i386.deb fcb65a702f98857ca1d6df4cecfdec129cab19cd 6832274 python3.4-dbg_3.4.1-10_i386.deb 7349241fd46a44ea4dcb467f3d819211bb5fb7fe 5018498 libpython3.4-dbg_3.4.1-10_i386.deb Checksums-Sha256: 5f0abd51f5944268d65e504169156e85a9dbe53b55abdfc483fe4c61225fa56f 2591 python3.4_3.4.1-10.dsc f2380582ed88c580fba8fc370af096f7e60c50069596e3c1e45b54ce8a485388 1018331 python3.4_3.4.1-10.diff.gz d6ee16eecdc04b16e9e2ea005394062de1ad91d9a59c38b9124a31f63b76476e 390898 python3.4-examples_3.4.1-10_all.deb 668d1efa76f686853583e7edee4e3becd79dad5acccaddc190542a73a3be1fb4 3012164 libpython3.4-testsuite_3.4.1-10_all.deb 7b9405931ae53b7e7613b4be989983ac7dea8919eb6c7a436eb0e63e4db564a2 81360 idle-python3.4_3.4.1-10_all.deb 88653ffb0842dc8a7581d36f0ceb33bb52b81624ba58fc4eb2578d2b78ee6067 5240784 python3.4-doc_3.4.1-10_all.deb 303b2b9086f41f7c6c1f9f06e705bc35cc91cd786a24ddc29cc0963ff1704de2 201266 python3.4_3.4.1-10_i386.deb 5e6ce9304d16da1eb499b9dfc9adbdb676c57511f7d604d92aad4ad4b31da501 5448 python3.4-venv_3.4.1-10_i386.deb 2b664e53a759f14557606a7145b413e761f8fde86293845099cc6966ef18daf0 2092074 libpython3.4-stdlib_3.4.1-10_i386.deb 1534bf4114420db7393430ebce1d9c9745614300e4d65c05ffbe27170782585f 1638014 python3.4-minimal_3.4.1-10_i386.deb a11182c019527cafc93bd1ed0d7671a8b893176eaac5f8c589bcfd9024f8ff41 491262 libpython3.4-minimal_3.4.1-10_i386.deb 4d1cc82d21fb6f909ace5dd52b1bc892313498a31a5415a89d71d1de0aefaf7d 1319514 libpython3.4_3.4.1-10_i386.deb af145e3c41853b6d15eab032f8e60b52a28c16e0f0fbe8dc932140a00e91d0f4 418358 python3.4-dev_3.4.1-10_i386.deb a8a67b1399cf5bb0d6490bc57895b82e3e48222545b820602f4093ff8e68db44 39171990 libpython3.4-dev_3.4.1-10_i386.deb 174a942406558dd12cd4ea501d3aafd98a4d0009a11237cbd497dc1285421a3f 6832274 python3.4-dbg_3.4.1-10_i386.deb 62479914dff2601134f8565c7ddebced34ea2b13e4a865684d45c3b8ad8f81f0 5018498 libpython3.4-dbg_3.4.1-10_i386.deb Files: a6078a0db342f73744a10f9ed22d3074 390898 python optional python3.4-examples_3.4.1-10_all.deb f79ad1bc961abc8fc42dc4bf8c6cc8dd 3012164 libdevel optional libpython3.4-testsuite_3.4.1-10_all.deb
Accepted r-cran-maldiquant 1.11-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 13:04:34 +0200 Source: r-cran-maldiquant Binary: r-cran-maldiquant Architecture: source amd64 Version: 1.11-1 Distribution: unstable Urgency: low Maintainer: The Debichem Group debichem-de...@lists.alioth.debian.org Changed-By: Filippo Rusconi lopi...@debian.org Description: r-cran-maldiquant - GNU R package for quantitative analysis of mass spectrometry data Changes: r-cran-maldiquant (1.11-1) unstable; urgency=low . * New upstream release. * Move debian/upstream to debian/upstream/metadata. * Upload by Filippo Rusconi lopi...@debian.org Checksums-Sha1: 1968c6931b7b1ce34b20a8c63c12c7e0a75e553d 2062 r-cran-maldiquant_1.11-1.dsc 1591bd99a5f097d22e81859d2d806734000f5950 1967171 r-cran-maldiquant_1.11.orig.tar.gz 7b2f5b7b68a1f629123408c879c514d67831117a 2640 r-cran-maldiquant_1.11-1.debian.tar.xz eb06f6ae80c1e1368e55ec23d8c87f5c689e5522 2086976 r-cran-maldiquant_1.11-1_amd64.deb Checksums-Sha256: 2bcdbc54549d602ffac81719bbee7272486d8dc0ce1887bb2964a8853fa0ed46 2062 r-cran-maldiquant_1.11-1.dsc 9bff5fec165f7f7db0dac1bfe897cbda218e824b7634df89ec355162d8f58f13 1967171 r-cran-maldiquant_1.11.orig.tar.gz 15348a039a36165ea7a4ad31951bd42e0d93b937d32bf1590d986f7a139d99ef 2640 r-cran-maldiquant_1.11-1.debian.tar.xz 322acf290be6022cc947b9b9baa6328f7cd9a8f323cd6319c0d1ae785e9b59ce 2086976 r-cran-maldiquant_1.11-1_amd64.deb Files: 7b8f82d48206c9241c100216cd253193 2086976 gnu-r optional r-cran-maldiquant_1.11-1_amd64.deb 242230dbfb5fa72b7abd353563937fac 2062 gnu-r optional r-cran-maldiquant_1.11-1.dsc f4bfe4c08ecee41b1875ca1a9c9060d6 1967171 gnu-r optional r-cran-maldiquant_1.11.orig.tar.gz 3c4f70ea50b449c8cc3065a4b55af3d6 2640 gnu-r optional r-cran-maldiquant_1.11-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8d6DAAoJEEGrSE12lM9Cvw8P/2jcFjRDGDeIRQEENrjtqtMR gnGGuVp9W1nXMCbd7ekLYJ9UYhA9UAOtmmw5I6cTSenQ71l7Ja4nCBrfH2jJ4TIc EN7oldh6TIxaAuoqsq5QQQpXRADtfCSSesRhTG6+hK8IXK2h0elXKONllnioEbp1 SEMfy0uJURn0tliSDkX4xM8v5zbSY16PFpH5we+pz/skpDBgj0HmHF/uqcTwepIc JcrR01ZT359PlzoWWZZ7F7oYMuj/c8LqVObzD7Wh4PRyWE6jrry2+PvtrnoFWNFj kO9OHc+8elJTkW1q/2l+sXh+iT0dMMpfuTsAg43HwJz94OZOvo86oMaZI0ayA57a fiwqrWDzFfoDGoZhMm6+q1MTaGnw2EeIlOaNtMQFe7oV0+jWrXJ/lu98F66YGH6s aPGyEES1zK0NXAQd9elJ2hUa/xRmKSklh6WGgejCJUR7s4DwYFYV9uuGgzsb3ia9 jQqAA8R4jiHs4QV8msh9iJFGx1EY7z7wGzZlx4nHxNW7vMQzMNp6+4pWQ9SwVD0a fuf2aD4CgLQ7im3xEeknu45kugXXIOjZ1k3mtjmTruifyoJC5HR/7/lFb1ghduwf Vw5zoOHIU35Wpv8vvPNo3CysGo1dBW/SnNVVox9rgVshw1PhnK7ojHtpCgapU6AH pNO+R78AfHO1WWoHgzmn =wzuL -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/e1xjkyo-0007ee...@franck.debian.org
Accepted r-cran-maldiquantforeign 0.9-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 13:11:09 +0200 Source: r-cran-maldiquantforeign Binary: r-cran-maldiquantforeign Architecture: source amd64 Version: 0.9-1 Distribution: unstable Urgency: low Maintainer: The Debichem Group debichem-de...@lists.alioth.debian.org Changed-By: Filippo Rusconi lopi...@debian.org Description: r-cran-maldiquantforeign - GNU R package providing import/export routines for MALDIquant Changes: r-cran-maldiquantforeign (0.9-1) unstable; urgency=low . [ The Debichem Group ] * New upstream release. . [ Filippo Rusconi ] * Upload by Filippo Rusconi lopi...@debian.org. Checksums-Sha1: 7c92075b32934d9ad7325eba1891c7c1bfb8a4d5 2289 r-cran-maldiquantforeign_0.9-1.dsc baf5bd38ac76ae7ae915e94294e34c3264f32ae1 189329 r-cran-maldiquantforeign_0.9.orig.tar.gz d49159a1eef870e6439627a3c1807f0c2565be01 2052 r-cran-maldiquantforeign_0.9-1.debian.tar.xz 4514470eeb06d3f411857d71707f66401ec758c4 263976 r-cran-maldiquantforeign_0.9-1_amd64.deb Checksums-Sha256: c081e22af59f055a119ee8771a9835b271e8a73c2c3756ddc498f721030dae41 2289 r-cran-maldiquantforeign_0.9-1.dsc 1751f277baf9e4aa365f515b6fc1268ac178d7290e3a4ea02852a4bf94fd3bd3 189329 r-cran-maldiquantforeign_0.9.orig.tar.gz 9a30e804d65298279827c7c50f53571f19adfc3dd985927abd332c2b7c98aedb 2052 r-cran-maldiquantforeign_0.9-1.debian.tar.xz 1e49fb0c5bc6e29dbfcff321c587a91fdc9da7a100f52f027f57c67353803389 263976 r-cran-maldiquantforeign_0.9-1_amd64.deb Files: 731294e7c780f57d147a4ebcedc3d932 263976 gnu-r optional r-cran-maldiquantforeign_0.9-1_amd64.deb 79ffe40a76c133012d89fb17da9c78bd 2289 gnu-r optional r-cran-maldiquantforeign_0.9-1.dsc b7ae77b51f6219f133c1e2e2f71bfbd6 189329 gnu-r optional r-cran-maldiquantforeign_0.9.orig.tar.gz 686d4d8c2ffab3c7b314d1c3731d726c 2052 gnu-r optional r-cran-maldiquantforeign_0.9-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8d/kAAoJEEGrSE12lM9CKnUQAKNa6dBbTNGQRZaXOoopAh5C SD2w4h3wp2osNBZY2tdHJzQFPgFbKySpbBAX2Q+BjPGxwgXk7rCM3ga1Hr4YiSve TPVyJ0yFhUDMDYba8ecQnQz/n6Of5qvE3Y35xXPk7L5gHk0c9sVljhIPjcwrxPHW nVWAYMxLmhqD75cbfgvVh0BEtp76fslcpKhZLMYsjufC0XXWT0+/fmvjdkt/XLen urjjGS+XwAppdtMwKPtqheGlDxKi/dO4QCXhW2cX0UicnLDwQTCXNAXsl2Vsak0m KcCJ/X898FpxKygNv303FWYgtwL8IuFAUv5S0H1zZuQjEa0GGfRPlmLZ1aZKN4mg HHSPRMqtxeStsvCOdpwpVaNkxjO4AipLC4SEDZqK7wo6okTI6h1Gp8U0blKl29+8 6gda3MXbLTAxey7pGAawA8bEYLS0jtYlvzPMCqtbMI36YEskgmyCp4so6WlYfjyQ YsIHu45x+cpPmnVdHQfz2UoGT+3OHrmij7il52wOTKOupo1y6fD1Df8nrAN8jUlm paHfeBORvl9qyM6SAjJ/UyQJqlbDIpkkV8QuLWknQD91zfmNl8i/lbRNwzYIrdem VvNdmDGEShAkYfGCIXFulm6bRKNj3ZUztkfkbTQx8JPSZfPtZDxo60ZNvzW74Gof 7JEHbfcoIdtb7TqD4X47 =/Kt8 -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/e1xjlcj-0003u1...@franck.debian.org
Accepted debci 0.8.1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 08:25:23 -0300 Source: debci Binary: debci Architecture: source all Version: 0.8.1 Distribution: unstable Urgency: medium Maintainer: Antonio Terceiro terce...@debian.org Changed-By: Antonio Terceiro terce...@debian.org Description: debci - continuous integration system for Debian Changes: debci (0.8.1) unstable; urgency=medium . * Documentation updates * Fix obtaining the finish date of tests. Parsing the adt-run log started producing bad dates when adt-run changed to displaying only the time without the date. debci now uses the timestamp of when adt-run finished instead. * debci-batch: store offline mark in persistent storage to avoid going back online after a reboot. * debci-test: revert to updating only package-specific data; it turns out that updating global data after every package is too expensive. * debci-batch: update global data every 1 hour or so * debci-generate-index: avoid crash when regenerating data for extenal consumption from scratch. This process is not completely idempotent yet, so it needs more work. Checksums-Sha1: 11ea7ed7835124bf4f06133f0fdba6f74073dd9d 1665 debci_0.8.1.dsc 62cdb065129072b0e11d571767fd6f9941b89493 146460 debci_0.8.1.tar.xz 56bfc6cc8537dd3f4891464383aa0928d6b9abfa 162596 debci_0.8.1_all.deb Checksums-Sha256: f3e18c0168511f7e0bd86d6718b46bf491cc15c7160bc871891cbd46ef96a5c4 1665 debci_0.8.1.dsc 25400f8698780180dee4a062cb62ef9dc4188210bdcbc823cb093688b1073811 146460 debci_0.8.1.tar.xz 342ba271e7916643767c4e5fe5a2b0fd8a3160e932abffccba57cef95a43ce3e 162596 debci_0.8.1_all.deb Files: 6bded2248e54bc74d2edddaa9b3e13cf 162596 devel optional debci_0.8.1_all.deb 390aeb6638b89de6119e52ee93a3c6ce 1665 devel optional debci_0.8.1.dsc a0b7dd10d05bd55a08e0ca8ae5a59d84 146460 devel optional debci_0.8.1.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8eV/AAoJEPwNsbvNRgvesxwP/R6vIvcqvDNeDfRx68eXx24f WTC310KYEEIpB8nyfiTHvSC6Bx7tJiEJfuDVfTrRHRksbRMj713IGF+0DB/Rm4fZ V4PHtwqs+K3fGgTZ9crqYm8kms8PigMjcJtUxJzn6EztmnbHtQwCZdVfK07U7j3J eOjUteE5tgyRzgGbH/Hm/VCzq5yu//QthiTvqexoks0eWQdzRMht6jVEa/mD4ux4 h4KN36KC1Ff4E1PS/NHBBJ1FLyXoC4geqTgOOTDZaPwR/CFNtJWBShCyBjna7mOx 9Ji47kWTkYIDt4Els7WqVvtmmnEId8sgNhwIor7mF8kOgCb01ny8FcTG2pSjAt+f fnc1efJ5IH1bfx8SE5TfGrVlRr3ryVLEEbNglmExLQlZCBVsmDIGxmtAUug0zpPM lzy0lAcRBsESI4P9jdYn21Rr0nENdygsIi0DVL8ZPq5/SJmXDUpey3esZ7UIvOfn RIA1g1ZoXWJSzUmoiSamyCE736gWK33sxZquIG4kxsbZBRj1eKgeoihaZIia4luU CbsNKpTIManVB3RJlclUK8ZEvM0d5FY7aqTUJ/oYKMoEJnmLyGdOZOeukbpRr/oi /e6tqTfrKOs94h5FuL8UYiMafSwyqVTNe+41GbFrB57gOMJq6EFYka6WxQQyUPdf HWGbr6v9x0ZWhIr8aPLW =yYbP -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/e1xjlr3-0001su...@franck.debian.org
Accepted libnet-dns-sec-perl 0.20-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 13:26:07 +0200 Source: libnet-dns-sec-perl Binary: libnet-dns-sec-perl Architecture: source all Version: 0.20-1 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-sec-perl - DNSSEC extension to NET::DNS Changes: libnet-dns-sec-perl (0.20-1) unstable; urgency=medium . [ Salvatore Bonaccorso ] * Update Vcs-Browser URL to cgit web frontend . [ Ondřej Surý ] * New upstream version 0.20 Checksums-Sha1: dfcf0ec9c9cbeb9aab6431b79fd7e7b2b5cbfb44 2297 libnet-dns-sec-perl_0.20-1.dsc 96a097a1d2dbd1f466156bab3da70022263a539d 80778 libnet-dns-sec-perl_0.20.orig.tar.gz 82fe6070a4a9ef6ef4a0b19d09a5c21210197747 2944 libnet-dns-sec-perl_0.20-1.debian.tar.xz 3e6cd32eec9722ef12c30f6cdf455abf05edfd5f 72162 libnet-dns-sec-perl_0.20-1_all.deb Checksums-Sha256: cb26ea1501a604f098803a24abc4c787230b1fbc2cd2c2ea449f3179fb8df055 2297 libnet-dns-sec-perl_0.20-1.dsc 161b3309148554eb2ca9fdb8dc0e8ec7948a0cb1203144e76812b6e7ddb68491 80778 libnet-dns-sec-perl_0.20.orig.tar.gz 2694574ccfda48775d64c2c3825f27dfa2857d2e8e7939882199b12383bcaaf4 2944 libnet-dns-sec-perl_0.20-1.debian.tar.xz 949e2a4140339f35eab55b135aeb40530129fd7a1d7d62dab4d2b287f1f8e01e 72162 libnet-dns-sec-perl_0.20-1_all.deb Files: 990bd98c5aae5648ff590982021d3798 72162 perl optional libnet-dns-sec-perl_0.20-1_all.deb 9911c072aa0e79385df3dc8295636f75 2297 perl optional libnet-dns-sec-perl_0.20-1.dsc 8f376c0e2473744689457efa642f75bf 80778 perl optional libnet-dns-sec-perl_0.20.orig.tar.gz 83dc630d0272132557b58ee25608f716 2944 perl optional libnet-dns-sec-perl_0.20-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8eN8AAoJEAyZtw70/LsHX+oP/1ICs1NF3jNUpKPoMjxw1oty KlOuLm5t5Ovx1AYLSCw8gGh6FyktKWPr9o0v4Q+8TSe/0sc7kXg8zNApS15Aa6t+ 6plA4YhEooNuguHeDpfYnxgUZNRlx9HRfpc609b43qyNBXhHh6cqLHmcugi/5I66 vVDS8xBySFmjt62Qo6xw1/VnSwGkGa+XikGqYBj3Sk2YX5GixZYEz9CRlGuy/OfC NzdXMCOwFcg4YaiAe1oLERBywo1lqmP5PAkWEHQ9N383tLQ2VcpxlKMtKxTNM8hh IgG1RJoxgNnIGqn21c+m5tw7Qcv6jdI+uI/GjMp8drqztAd0NB2uBQ6LSDwGXHJm LOXsCK1JYec8v+dPjiPI2BVkO8mvEQlBDPitW6vc8CTQsIdGojouSjEqdonAS9Wr SBn+fPJ9B3YQ3Xiy36zSC0YcRs6workI8ZurcSy6RWsDtgrHdi2X/CNtAOqqWzRQ w/34I/e3ULQdqNE9WfDtLH6t5eg7e18sjYePssMxR3885XWO0nTqAqSqQ1NyFHGU 1vziQIvY8WG4wxdvUyqMIcJ2strebER8GtdZbNMOujT4mYb5xXJZa/E/f64vKPYR sAvay+l5Ih7iflEZU9ngwG6rqHdiusHT8TuStLxRfvKEDuOjjdiCuRWyqi+CpfER cYJGZKA31bLZnBgAswMD =s74L -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/e1xjlrg-00028x...@franck.debian.org
Accepted freeipmi 1.4.4-1 (source all amd64) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 15 Aug 2014 09:23:03 -0400 Source: freeipmi Binary: freeipmi-common freeipmi-tools freeipmi-bmc-watchdog freeipmi-ipmidetect freeipmi-ipmiseld libfreeipmi16 libfreeipmi-dev libipmidetect0 libipmidetect-dev libipmimonitoring5a libipmimonitoring-dev libipmiconsole2 libipmiconsole-dev freeipmi Architecture: source all amd64 Version: 1.4.4-1 Distribution: unstable Urgency: low Maintainer: Debian FreeIPMI Maintainers pkg-freeipmi-de...@lists.alioth.debian.org Changed-By: Yaroslav Halchenko deb...@onerussian.com Description: freeipmi - GNU implementation of the IPMI protocol freeipmi-bmc-watchdog - GNU implementation of the IPMI protocol - BMC watchdog freeipmi-common - GNU implementation of the IPMI protocol - common files freeipmi-ipmidetect - GNU IPMI - IPMI node detection tool freeipmi-ipmiseld - GNU IPMI - IPMI node detection tool freeipmi-tools - GNU implementation of the IPMI protocol - tools libfreeipmi-dev - GNU IPMI - development package libfreeipmi16 - GNU IPMI - libraries libipmiconsole-dev - GNU IPMI - ipmiconsole development package libipmiconsole2 - GNU IPMI - Serial-over-Lan library libipmidetect-dev - GNU IPMI - ipmidetect development package libipmidetect0 - GNU IPMI - IPMI node detection library libipmimonitoring-dev - GNU IPMI - ipmimonitoring development package libipmimonitoring5a - GNU IPMI - Sensor monitoring library Changes: freeipmi (1.4.4-1) unstable; urgency=low . [ Tollef Fog Heen ] * New upstream release - bump sonames - new tool: ipmi-config - refresh quilt patches - upstream dropped freeipmi-bmc-watchdog logrotate.d snippet, reintroduce as a Debian patch. * Add freeipmi-ipmiseld package. * Adjust dh_fixperms_override call to only be called on binary-indep. Checksums-Sha1: c9aef99d30d81c93eebf51337862eca6f09773c8 2232 freeipmi_1.4.4-1.dsc 343b574ca79038d22827c895ef0ca95ee38137ae 3089763 freeipmi_1.4.4.orig.tar.gz fd66f5df39cdf118800bb9a93a4aa0b2c683dd90 24312 freeipmi_1.4.4-1.debian.tar.xz 1f4ec517ba6b8d32780c4f2d5eb006043d1d3655 336366 freeipmi-common_1.4.4-1_all.deb d59caf4f0d2447997163643f351bfcf62f5cb384 600848 freeipmi-tools_1.4.4-1_amd64.deb b821c95804fc7e8c361c02130f3ca7c962cfb193 44934 freeipmi-bmc-watchdog_1.4.4-1_amd64.deb 5eae5bf5aa9cb59fce097d30b4afa50363ed6487 37878 freeipmi-ipmidetect_1.4.4-1_amd64.deb 7c5343ee62220fe342b4f8a79894e956dd36f7b0 79072 freeipmi-ipmiseld_1.4.4-1_amd64.deb d93371d0b35a3dc341321923ced1655e163a881b 755976 libfreeipmi16_1.4.4-1_amd64.deb 63c2bbd8eea0f255852eafa374626d08be5af235 849990 libfreeipmi-dev_1.4.4-1_amd64.deb 503861c52d1ef2127d998aa93058b093791a7cb3 25550 libipmidetect0_1.4.4-1_amd64.deb b9255c788479694a62224932b3e84aa47cbdc860 31418 libipmidetect-dev_1.4.4-1_amd64.deb 9fb8027890d9d1a5858b834903c58c9d27a7cf43 43420 libipmimonitoring5a_1.4.4-1_amd64.deb 4f7f4e66b2d568d12ffca52331800b1b9a2aa77e 61422 libipmimonitoring-dev_1.4.4-1_amd64.deb 9b906677c41e87064d22cfa5e190bf7372439fe1 85648 libipmiconsole2_1.4.4-1_amd64.deb 916836272b3f5d7109b3259d7c9038923bb46f42 101442 libipmiconsole-dev_1.4.4-1_amd64.deb 4ea3e37cda968db680a75f11b93e4f2af6d633dd 1022 freeipmi_1.4.4-1_all.deb Checksums-Sha256: 04d6020d510d16e8babc03df3d25dac752c6003e7b50182f9da1e9557611 2232 freeipmi_1.4.4-1.dsc 7e7011f54a988453f6a679a24ed7b90c70ba5f5b685e3842ccbd4fd806554962 3089763 freeipmi_1.4.4.orig.tar.gz bbe120dc7b92360f28b757e0757b9b4ca4595ecda14418a1926562bae35df39f 24312 freeipmi_1.4.4-1.debian.tar.xz 9eaa93f7ce34f59948218ebdc46c580910c2c2483fa1f73a10662ff167e54397 336366 freeipmi-common_1.4.4-1_all.deb aa4aadba9b6e828d58dde181c6c3c355ea6535068859172d60ff3d074063d18e 600848 freeipmi-tools_1.4.4-1_amd64.deb d0373acaf746b4982956bfaceaffc94eaa7999d7ca67a3dc197b026258e9e7e1 44934 freeipmi-bmc-watchdog_1.4.4-1_amd64.deb 181d84f75c9d4b0fe65ba4960ddab40f79914c5a87d7d9f4f20f55e72849e34c 37878 freeipmi-ipmidetect_1.4.4-1_amd64.deb 1ce41b4c282db7364d19a94dba11c1632298c067588a761c5bb25f832f19fe78 79072 freeipmi-ipmiseld_1.4.4-1_amd64.deb 823fbb63e1ba2f22237ecb3e406f2df71a6a60a785e7b32dbd22d99721d92da8 755976 libfreeipmi16_1.4.4-1_amd64.deb 8f9179b86513565acddc8f77b6f2b494a53d146dfc0c386aab1b06a037d00d3b 849990 libfreeipmi-dev_1.4.4-1_amd64.deb 0e3092658d3cb6e746dd39cce43f26cbaa5e6a05d6c131ba4ef12845544826f2 25550 libipmidetect0_1.4.4-1_amd64.deb d809d7fa7f4a75c1a8619be2993362eef41babbb53ef2f0530da0eb78f94d4f3 31418 libipmidetect-dev_1.4.4-1_amd64.deb 765f75ea49496fda62eed4ae2e1c072b1b06d94f2b37bf60a9bb39489a4a7708 43420 libipmimonitoring5a_1.4.4-1_amd64.deb d87728526a1a13c0a1de43298f74774deb6cc219111bf574b6489d906dc0130d 61422 libipmimonitoring-dev_1.4.4-1_amd64.deb 365f52e67656fd7d2af7fd84fc54abfd052581f35b1e28f1175c698ed79bdd7f 85648 libipmiconsole2_1.4.4-1_amd64.deb d166002668cda9a8c216356900c44623988af1f16c664c21b1966f298408afab 101442 libipmiconsole-dev_1.4.4-1_amd64.deb
Accepted wxpython3.0 3.0.0.0+dfsg-4 (source all) into unstable, unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 17 Aug 2014 23:00:56 +1200 Source: wxpython3.0 Binary: python-wxgtk3.0 python-wxgtk3.0-dev python-wxgtk-media3.0 python-wxversion python-wxtools Architecture: source all Version: 3.0.0.0+dfsg-4 Distribution: unstable Urgency: medium Maintainer: wxWidgets Maintainers freewx-ma...@lists.alioth.debian.org Changed-By: Olly Betts o...@survex.com Description: python-wxgtk-media3.0 - Python interface to the wxWidgets Cross-platform C++ GUI toolkit python-wxgtk3.0 - Python interface to the wxWidgets Cross-platform C++ GUI toolkit python-wxgtk3.0-dev - Development files for wxPython python-wxtools - Tools from the wxPython distribution python-wxversion - API for selecting the wxPython version to use Closes: 722687 758209 Changes: wxpython3.0 (3.0.0.0+dfsg-4) unstable; urgency=medium . * Fix python-wxversion to include wx.pth as a symlink so that 'import wx' works when python-wxgtk2.8 is installed but python-wxgtk3.0 isn't. (Closes: #758209) * New binary package python-gtk-media3.0 for wx.media. (Closes: #722687) Checksums-Sha1: 64b8dc7433b5871021be9978be631bf73ce66674 2377 wxpython3.0_3.0.0.0+dfsg-4.dsc 7ddee6aaf4395a37ec07efff3daa96c2cdf2fd85 34120 wxpython3.0_3.0.0.0+dfsg-4.debian.tar.xz 69fe7357be72a64003484be8c61b028b2ae8ce74 528006 python-wxgtk3.0-dev_3.0.0.0+dfsg-4_all.deb 0ab975591094fc06d92595c17bc25394460d0172 110486 python-wxversion_3.0.0.0+dfsg-4_all.deb 4f97d78805073492bd4149acb73d599a2439ebbe 108250 python-wxtools_3.0.0.0+dfsg-4_all.deb Checksums-Sha256: 2bcdd3eb51847293efe3b4168590ee3ea5cf835b3c91140ddd91d77354850300 2377 wxpython3.0_3.0.0.0+dfsg-4.dsc cbae2bd01a4180339ce053d13d5bf586f977278f6e8674bf363824501af5cca3 34120 wxpython3.0_3.0.0.0+dfsg-4.debian.tar.xz 02c689a1f4c60f37d5edc9b7e77b5e37393524dc9694fcc623274c9791aa10e2 528006 python-wxgtk3.0-dev_3.0.0.0+dfsg-4_all.deb 0205cdbd61d4b5a8ee4c6cd6b860da810f2dab06852061b5c12a478381ac9b1e 110486 python-wxversion_3.0.0.0+dfsg-4_all.deb a2609fc6f180e3787e90b592779b3e7ce4cb5d5b987591d766a786d904b86e8a 108250 python-wxtools_3.0.0.0+dfsg-4_all.deb Files: a261b091d06ff89c6bed7b5be1d177bb 528006 python optional python-wxgtk3.0-dev_3.0.0.0+dfsg-4_all.deb 645537d77529c7a384c41e5e04f2fd70 110486 python optional python-wxversion_3.0.0.0+dfsg-4_all.deb 530524924e3316ff60d183416ec23035 108250 python optional python-wxtools_3.0.0.0+dfsg-4_all.deb 2f8e1cfd306d30a58b66b7a648b93355 2377 python optional wxpython3.0_3.0.0.0+dfsg-4.dsc 0733aae5f83af57f57e3e4086bd9b7cc 34120 python optional wxpython3.0_3.0.0.0+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJT8I4wAAoJEBgUewc7rSsHw6IQAJ0LkWQGO3Qn0nd4vCynA7sk urvbYroNN++YxmqmT7lnkj0hqAo0Lz/NkzU71GXjVjEICBp7TAQmbnXiNtHGTkZo /7p82TCJZqq8zYGcJ+cHqtUhLNUSHg8Dqb1VVoro9l20O46r8YuolgJ0/BRg4G+V yEirjeM0Nuk51P5RvjLQWkDGVjHc3fJ/ZI+syMJB37AT7++8/yc9ZudCHpEdEdX8 PUkqPdSLmjKcxjzG2j0Ht7ox1Ka+6b5i2u29NwA9p4KNCUi6d1E6qhMRyg4x/Ru2 2qo56ICUsyqGC0gzmXG86Z5fxD7VrmeuBYNht2QIeBPoB1tsj0+oNWRwdSi8lXz7 kKYIq6HszgNQu5kwMXGjWs5+YlTzDeN8pETnIwlt6rdpK2o1q+kcJOwJ9tu1sjvG gVnSpL+nw9b1uXmBp7wBWvHFxzdlAXpSewuoyn/NpUIEk3Cn44RZ2/OPKd2QvQ6S q1PGO9bQH7FEh7MjzN72RCyJ+Su24y3NVgZHG3yue/m3QIW1BXNXjvBp+ayF4WMx VF4zlz68linTmuQsZ67YDf66Q9QUEqxmvAb8V1lg3IXC6EuTVTeEcm3kdGma53BW RHP3t4o6mIZHR+iUrybv3uHhm5L75pFW55ZFILUUmf9nRkYGSdZ2zuH09TVutPMm 2Hcyh352GJx4tcNdJG25 =InDv -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/e1xjlbb-0006kr...@franck.debian.org
Accepted php5 5.6.0~rc4+dfsg-2 (source all amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 12:16:56 +0200 Source: php5 Binary: php5 php5-common libapache2-mod-php5 libapache2-mod-php5filter php5-cgi php5-cli php5-phpdbg php5-fpm libphp5-embed php5-dev php5-dbg php-pear php5-curl php5-enchant php5-gd php5-gmp php5-imap php5-interbase php5-intl php5-ldap php5-mcrypt php5-readline php5-mysql php5-mysqlnd php5-odbc php5-pgsql php5-pspell php5-recode php5-snmp php5-sqlite php5-sybase php5-tidy php5-xmlrpc php5-xsl Architecture: source all amd64 Version: 5.6.0~rc4+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian PHP Maintainers pkg-php-ma...@lists.alioth.debian.org Changed-By: Ondřej Surý ond...@debian.org Description: libapache2-mod-php5 - server-side, HTML-embedded scripting language (Apache 2 module) libapache2-mod-php5filter - server-side, HTML-embedded scripting language (apache 2 filter mo libphp5-embed - HTML-embedded scripting language (Embedded SAPI library) php-pear - PEAR - PHP Extension and Application Repository php5 - server-side, HTML-embedded scripting language (metapackage) php5-cgi - server-side, HTML-embedded scripting language (CGI binary) php5-cli - command-line interpreter for the php5 scripting language php5-common - Common files for packages built from the php5 source php5-curl - CURL module for php5 php5-dbg - Debug symbols for PHP5 php5-dev - Files for PHP5 module development php5-enchant - Enchant module for php5 php5-fpm - server-side, HTML-embedded scripting language (FPM-CGI binary) php5-gd- GD module for php5 php5-gmp - GMP module for php5 php5-imap - IMAP module for php5 php5-interbase - interbase/firebird module for php5 php5-intl - internationalisation module for php5 php5-ldap - LDAP module for php5 php5-mcrypt - MCrypt module for php5 php5-mysql - MySQL module for php5 php5-mysqlnd - MySQL module for php5 (Native Driver) php5-odbc - ODBC module for php5 php5-pgsql - PostgreSQL module for php5 php5-phpdbg - server-side, HTML-embedded scripting language (PHPDBG binary) php5-pspell - pspell module for php5 php5-readline - Readline module for php5 php5-recode - recode module for php5 php5-snmp - SNMP module for php5 php5-sqlite - SQLite module for php5 php5-sybase - Sybase / MS SQL Server module for php5 php5-tidy - tidy module for php5 php5-xmlrpc - XML-RPC module for php5 php5-xsl - XSL module for php5 Closes: 758185 Changes: php5 (5.6.0~rc4+dfsg-2) unstable; urgency=medium . * Sanitize $PATH in php5-common postinst script (Closes: #758185) * Update the sessionclean script to only check for SAPI processes (Courtesy of Steve Kamerman) * Other various minor improvements in the session cleanup script Checksums-Sha1: ec156680f562682e9c1291a0ef55a64e585faf78 5044 php5_5.6.0~rc4+dfsg-2.dsc 6a51c57ab21129796852d99c8003ee7c6bfa9e73 117376 php5_5.6.0~rc4+dfsg-2.debian.tar.xz a2c748771167e87a8e9c89f4df29336f9b10f453 1312 php5_5.6.0~rc4+dfsg-2_all.deb 3c4b0e83bc7665026984d04f3efdb2482d9054c9 268748 php-pear_5.6.0~rc4+dfsg-2_all.deb 83576e6b6defd81f237afc93fc09485e016231a3 537088 php5-common_5.6.0~rc4+dfsg-2_amd64.deb 683af77d38f1ade99f69501ae0518dc12f949153 2204488 libapache2-mod-php5_5.6.0~rc4+dfsg-2_amd64.deb 672f7a385ff3b81b2b6746feb7cfcda6f457bf5d 2198614 libapache2-mod-php5filter_5.6.0~rc4+dfsg-2_amd64.deb bb028fac80e5fa16d37ba91eb52f8999af72d29a 4261784 php5-cgi_5.6.0~rc4+dfsg-2_amd64.deb 49908e3fd639bddd2938086363fa082905fb932b 2165530 php5-cli_5.6.0~rc4+dfsg-2_amd64.deb 24b787044fe3891c13e89bdb6f108452be0f9200 2182168 php5-phpdbg_5.6.0~rc4+dfsg-2_amd64.deb 0b86a63a33d6d531b6b7adc8d3d7fc4123123e20 2184270 php5-fpm_5.6.0~rc4+dfsg-2_amd64.deb 0f2c01cb34f88f0841c57504014d34e90e60efc1 2199648 libphp5-embed_5.6.0~rc4+dfsg-2_amd64.deb d2af1b6df902c8cf3d81ddaa3cc1464765562490 354676 php5-dev_5.6.0~rc4+dfsg-2_amd64.deb fca3e7f9605d465fb448ca5beb8091addccec8f5 44887248 php5-dbg_5.6.0~rc4+dfsg-2_amd64.deb 30e43406c31eda93b7071ecd565ad6ed60a09e72 27706 php5-curl_5.6.0~rc4+dfsg-2_amd64.deb 9079aa174a314ce21c860ea8cba0011fc1dfa22e 9414 php5-enchant_5.6.0~rc4+dfsg-2_amd64.deb ad07c94927e97ffd089eeff6636c5fefa196e492 28780 php5-gd_5.6.0~rc4+dfsg-2_amd64.deb c2f8560f6c2dbd98c02c7f640b516cea97c60c91 20058 php5-gmp_5.6.0~rc4+dfsg-2_amd64.deb 677bfd0e0103dd18f8b0c6a042ea7a9487e54f40 31016 php5-imap_5.6.0~rc4+dfsg-2_amd64.deb 8a5251fca8923763780b70df82d9aad7bbf3ee9a 42672 php5-interbase_5.6.0~rc4+dfsg-2_amd64.deb 55220e2d54a0cf2d15b52163afd9e5ec1e5b9e1f 111664 php5-intl_5.6.0~rc4+dfsg-2_amd64.deb 69dbc207d61b7bdd0a03e944039f476c08ef7d13 21916 php5-ldap_5.6.0~rc4+dfsg-2_amd64.deb 8c8e98d37f741e0b9e99b6f9173f8c9cafa8a70e 15278 php5-mcrypt_5.6.0~rc4+dfsg-2_amd64.deb 31a74f749bd4c06fd4cbfcc6dbe67bcb5068ed2e 12536 php5-readline_5.6.0~rc4+dfsg-2_amd64.deb b9217839e5e91736a8df1f556a205f7f9b75c659 64944 php5-mysql_5.6.0~rc4+dfsg-2_amd64.deb
Accepted rpcbind 0.2.1-6 (source mips) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Aug 2014 10:45:45 +0100 Source: rpcbind Binary: rpcbind Architecture: source mips Version: 0.2.1-6 Distribution: unstable Urgency: medium Maintainer: Anibal Monsalve Salazar ani...@debian.org Changed-By: Anibal Monsalve Salazar ani...@debian.org Description: rpcbind- converts RPC program numbers into universal addresses Closes: 734903 Changes: rpcbind (0.2.1-6) unstable; urgency=medium . * Upload to unstable. * Fix fails to upgrade from 'wheezy' - trying to overwrite /usr/share/man/man8/rpcinfo.8.gz. Breaks+Replaces: libc-bin ( 2.16). Don't depend on libc-bin (= 2.16). Closes: #734903. * Remove debian/source/options. Checksums-Sha1: 41ef61cedad51435990a9a1e23cc568441c24855 1793 rpcbind_0.2.1-6.dsc 3ad733fc1ebd743408a434309a46c0ea7f0652ca 8476 rpcbind_0.2.1-6.debian.tar.xz 8275b282608400a131374ac9a892eb00d61ca0fd 39464 rpcbind_0.2.1-6_mips.deb Checksums-Sha256: c8963deca7b2471a92b9231ec11f70c193fa66c2797503409bed14bf7aa1d907 1793 rpcbind_0.2.1-6.dsc 49d0d7b5c936cdd8300cf035d259c31b3fab5a82edcddec16f8d488f60d8e00b 8476 rpcbind_0.2.1-6.debian.tar.xz 3a4fcb09f81280cd3995a70fa8cc538c927c4f96c1807b61dbc0ba85a6da29ae 39464 rpcbind_0.2.1-6_mips.deb Files: 0023eee1baa4af7ccdca34bd1179e65e 39464 net standard rpcbind_0.2.1-6_mips.deb 314a356859fc3598f69e255cd7da0c37 1793 net standard rpcbind_0.2.1-6.dsc 65ae949e51d8468cc04c343679e87482 8476 net standard rpcbind_0.2.1-6.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJT8eq5AAoJEHxWrP6UeJfYTQEQAMYNlsfYA4PLWb1nX7gp4MYj NmUyo6aPfuZiJEGmz6gu3CG3Hd+b/RJJq4pZ5qrQSZqLO9a1T88K+t/gJx2U4sC+ XQW/LDuxiNX0tMWVb+k7Jk/O7smqmEcwr9QVwXvhSgubMDDuAa1btTGDHW3fg6bM Kitmx79I+RLDbSeD9lQOUc7/CrM+N5eyFITBy1qMJLYUyHqFQd8tryd+bCMmLk02 qjs0amai92azKbn6QtQjlKrQR/PvTG92lrAlE58Xx67aYD8JA+gwsZQFIw5RrLwf r3rleIVXHUqqT4YZsS46LqC/G6jF7ZYC0xCkno63zLAfCNAvX3aZzh78XaQh6SU3 JjwO5OmqLmtWrRoSELU6gqW1IalwFOHZ4qNPjB5Gs3hOSmbGlOPYqI324rHklp9l X+NFiHQWpZxXR63pCXYYE26/yvKZ5WauxUbp1rCHP5M8D+wNUuqI5hYagc2KXiSV 0Cwno9SyAHY32MAUNCfzMw5JSbz+UGbzvi+2fx/jhrIJ0M4GfyeHicQvH7nXpYE6 ZqYQ1KkanjkzBpY5xBCLbV2xfHs60Ux1D85dnTe/TUaWG1QLj7i+QInLn+oKAXfr xZYKyUcm/PAlaja9l/pk+zrNtg07GJk4u8GwinKZ5wO3zL8tVEXUj9Nv17a2Updj uf9J3WAMUCmEi1sKc2rs =ippe -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/e1xjlvc-0002r3...@franck.debian.org
Accepted fxt 0.3.0-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Aug 2014 14:19:40 +0200 Source: fxt Binary: libfxt-dev libfxt0 fxt-tools Architecture: source amd64 Version: 0.3.0-1 Distribution: unstable Urgency: medium Maintainer: Samuel Thibault sthiba...@debian.org Changed-By: Samuel Thibault sthiba...@debian.org Description: fxt-tools - Multithreaded tracing library libfxt-dev - Multithreaded tracing library libfxt0- Multithreaded tracing library Changes: fxt (0.3.0-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: fbae5a09aab08cca76be253f7fdf4c131ca64854 1985 fxt_0.3.0-1.dsc 4b4d8af1b3b51d32c2283b448b36ab5fde4615d6 1088432 fxt_0.3.0.orig.tar.gz 9b27f2860dddb007d0beaa470e292ff8663818e6 2584 fxt_0.3.0-1.debian.tar.xz a9e612b6a1013f7a53ff863f11f5565fca1feb7f 39292 libfxt-dev_0.3.0-1_amd64.deb f63e6531d748283545f8f49acfac91ce807648a3 29084 libfxt0_0.3.0-1_amd64.deb f1868fd098b7df2a3dec30ab1275eed98eb33cec 12782 fxt-tools_0.3.0-1_amd64.deb Checksums-Sha256: 0881457a5e10ca19ca8e32c7221f32009460d00c4de3a4b508d28abe0a9c76ca 1985 fxt_0.3.0-1.dsc 835dcd82c53f1eda067b98d3598321c11aef4dd270ab7f7b6ccc6025157d9317 1088432 fxt_0.3.0.orig.tar.gz b8f153f54c040e97fcd61cb9ed35a193af2a8d86c54e75691bbfde4191e7 2584 fxt_0.3.0-1.debian.tar.xz 454d8359e52f1d0a5fca067aa6ae8108ff361f7084b08b03479837379125963d 39292 libfxt-dev_0.3.0-1_amd64.deb 46795ef63eb38105624df8dba27f6b105be70e63fe9cbbfe2633e7a8299f034c 29084 libfxt0_0.3.0-1_amd64.deb 4ac406d361f4b6ab30dff05f97fa2811404a28d79d40a34fcc4859a8f4c21142 12782 fxt-tools_0.3.0-1_amd64.deb Files: a0eec84a2eb7e98e6c2b5ff7c95901b8 39292 libdevel extra libfxt-dev_0.3.0-1_amd64.deb 2b860b4f2d4835f8836f5ad302148add 29084 libs extra libfxt0_0.3.0-1_amd64.deb f6bd24929bc72831dd172d06b896fe59 12782 science extra fxt-tools_0.3.0-1_amd64.deb 9dca267c1d32a5c128964013b505a0d4 1985 libs extra fxt_0.3.0-1.dsc 1aeb6807bda817163d432087b27ef855 1088432 libs extra fxt_0.3.0.orig.tar.gz 0ee524ee5bb86a7d739ae6e606fba850 2584 libs extra fxt_0.3.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJT8fAiAAoJEBH0lP5vGG7N+s8P/j6PjlgvyLIP/CZonexG9Ce4 vMPUnKFnytcw8JUO+6zWLhYoZLiP6XaOO0LbeqVtV4MO9OvYkasDzTQr5W+ZQurp JFrFhNRRqU0fH8796pZlohtlvBPB3rPSvOWVPGZtW9AAoV8qg58+dDaginJs89Mp J8RMR7jAfXyWHrEYqKBzT1OvYv6dZsDl0vd6xSGJBVUVlVx3mebr35W6hr3kG4O0 yQC+2bqMvI0tPDs6/+u82X5AZOSTXklJTIbijBAZHT8L9+qziH8+59moSTwvpg+h AMptF4gLoORY7KBasJHMIv/5XoU2O22eW7mDe0t59Zm78xBcOoF4YO1DzaoGHp1h qFD0zKFLm9q3vDyN92rRhNSzEPuAHPbFXqQJzxKWmB+EPagXXOB/vnXbKMrHM7kX NmdPGxZwU5VJw8vfY6x1x1ul/UB764QBqm3dfZ+63C8rBHfw60jzKz9YPl6fXKNj Gsmlvi108pWYZW3qS6ArkeBe3ENeq0CfD77D1Pp3XUgFbbqJdzXUM/CkITQm/WON hKawiWvWC7Hwl8e/lrNV96J+DUF58ec6+b+0JgfehAZ46FBYzfk2poEMT9RSz9sW 7aNtTomFmuBsidabFnAL5lNYXGJ0WFCzKHT0GPXQlCUWn1QXc1b4lk/wFgvv8By3 6PrVo/8Cj/u1TneN6nmP =zIFB -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/e1xjm8l-0004gf...@franck.debian.org
Accepted qlandkartegt 1.7.7-3 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 18 Aug 2014 10:13:53 +0200 Source: qlandkartegt Binary: qlandkartegt Architecture: source amd64 Version: 1.7.7-3 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org Changed-By: Jaromír Mikeš mira.mi...@seznam.cz Description: qlandkartegt - GPS mapping (GeoTiff and vector) and GPSr management Changes: qlandkartegt (1.7.7-3) unstable; urgency=medium . [ Jaromír Mikeš ] * Move package from collab-maint to the Debian GIS team (pkg-grass). . [ Bas Couwenberg ] * Team upload. * Fix uploader-address-malformed lintian issue, by separating the Uploaders with a comma. * Reformat control file with cme, update gdal and proj build dependencies. Checksums-Sha1: cb5de78d122b447a4b7609d02ca450d1a3a8451e 2136 qlandkartegt_1.7.7-3.dsc abc33a83183f0541a0d788506cfca01844b1e4cd 8488 qlandkartegt_1.7.7-3.debian.tar.xz e4065126496cda07efdc25e6a2d505dc1889af7e 3914108 qlandkartegt_1.7.7-3_amd64.deb Checksums-Sha256: 3e37563cb4c69dce14b79e682f0316788913f441c362f7ee4359b3e8a58acf6e 2136 qlandkartegt_1.7.7-3.dsc 46e158d9d3f6e19acf7868726d30e5ee6f943f11cd04789a7d720a36f64d2fe7 8488 qlandkartegt_1.7.7-3.debian.tar.xz cd21f47865d043cc25e676a601034448eba0ec3f2c3966bfe8b17c078b19eafb 3914108 qlandkartegt_1.7.7-3_amd64.deb Files: e18e41d81b95750b2d93a4adaf20fcaf 3914108 science optional qlandkartegt_1.7.7-3_amd64.deb 9394bedb17745c323e5f0bef29a62eba 2136 science optional qlandkartegt_1.7.7-3.dsc 4b605e000596b7d478c4945ce2cb9c9c 8488 science optional qlandkartegt_1.7.7-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJT8fCOAAoJEFsBlFXiuE+lomEQAI5Wn8jsL5UV40HR1+8aSGsY fDtVtHGjxo1NuYzuLmGNxJXs3cMhFMaFTlHN/OyiMqfwRpPcKGbzI8OPfBGCKtnp zEK41QM/I0o/FMBD7KG8FzokDcQrSijqXJdFjnYWpFnfFUdt0+izRKDTtQm+IOCK Dh7D0zBY4oCwRquO0KQQtfdez2FUAcWfceFB+yiRN88LeUmR1NF/2jEho6SGepCp 2ppwMKKwUZoBJP6pqkxX7PgxDYfkwTI4LjLNKWs5BMzmiBwouX6KksjIHqd6XcVH F0vKZUKUAm0mZ2+8P6VSTeTqHYv+8le5w0UM5sAEoUpCDk5fVzDDSj0EWYFeCgdU XTyZl/1HEwGz13febZOYsV/NB8zNMETLcIR2gOyl+8tviw1XCprOGLS69sk6OTkk 1A7Ztj+GjcawGTwympjC9hUClg2LWYL7mhZmcXJ750RQP9/RRgAGOJTH9BpvDVu/ GvmSryE5SwZT2VV9C1L3dzCvEl3ux18xkSnhrnhI8hgL9+QC9WY65xeZuYgD28zh cd8kRbg2M2aDi0k+3XPFnAhzuVkzICV5+thhMJdXmtfzhhQR+Pq8Q+h+6iunLfrC PGoR4TFemxp7CbHTkg+OIyUazCqgJMG4Ww1nikuhSVTapihJNcxWoHp1cwG/Op82 AN53mNqEZJNQM26r3Bug =jL/M -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/e1xjm9l-0004nw...@franck.debian.org
Accepted binutils 2.24.51.20140818-1 (source all i386) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 18 Aug 2014 13:49:01 +0200 Source: binutils Binary: binutils binutils-dev binutils-multiarch binutils-multiarch-dev binutils-hppa64 binutils-doc binutils-source Architecture: source all i386 Version: 2.24.51.20140818-1 Distribution: unstable Urgency: high Maintainer: Matthias Klose d...@debian.org Changed-By: Matthias Klose d...@debian.org Description: binutils - GNU assembler, linker and binary utilities binutils-dev - GNU binary utilities (BFD development files) binutils-doc - Documentation for the GNU assembler, linker and binary utilities binutils-hppa64 - GNU assembler, linker and binary utilities targeted for hppa64-li binutils-multiarch - Binary utilities that support multi-arch targets binutils-multiarch-dev - GNU binary utilities that support multi-arch targets (BFD develop binutils-source - GNU assembler, linker and binary utilities (source) Changes: binutils (2.24.51.20140818-1) unstable; urgency=high . * Snapshot, taken from the trunk 20140818. - Fix GLIBC ifunc breakage on PowerPC64 ELFv2. LP: #1355962. Checksums-Sha1: adbc477361791d99e945e1553d883a7892475b33 1807 binutils_2.24.51.20140818-1.dsc 05ad855a21ac50ba7f0b66a62d75b3785a8f54d9 29393648 binutils_2.24.51.20140818.orig.tar.gz 8be09c3cbd9f5bd9256636b5e8ff41f3569a94a5 75498 binutils_2.24.51.20140818-1.diff.gz 3c5b8edb8148bd01b0dc9a5b5226fae59603a27f 499530 binutils-doc_2.24.51.20140818-1_all.deb 7586ccbaa33ab854a21e42b45c272f89c2d4a77a 16846756 binutils-source_2.24.51.20140818-1_all.deb 56868792c04ceee88b09fcd152c70ba15ab4fad0 3460062 binutils_2.24.51.20140818-1_i386.deb 20d6b97a3103af36b8b2a4bf05edf69f31e9921c 1749688 binutils-dev_2.24.51.20140818-1_i386.deb 8c3923c657285afb6f148bb5b4289ed8f22466f3 1706302 binutils-multiarch_2.24.51.20140818-1_i386.deb d4362b40e46ec500db43e976a0c9afad6d44f6a7 1206 binutils-multiarch-dev_2.24.51.20140818-1_i386.deb Checksums-Sha256: 97b8f12d9cda75b187bd492b045602903d9145f719f469198fd31a985c088f89 1807 binutils_2.24.51.20140818-1.dsc fe5531a3f6abb4bbd11d95367de1beb4ab538aa4c4d8c0f088dba1cee66ef4e8 29393648 binutils_2.24.51.20140818.orig.tar.gz 9f49ea91d076766f49e7c3689b32f08123748e399fc541fce5ac3df035d2d649 75498 binutils_2.24.51.20140818-1.diff.gz 5276b0557b068f660594c860575e3ae7041622e1dabffbe729b9c2043aaeaed3 499530 binutils-doc_2.24.51.20140818-1_all.deb 57a6fffda5f6088515ecc6d71c361ebb1089911fa086e2257137ddfc9b10e985 16846756 binutils-source_2.24.51.20140818-1_all.deb 7e93e944f02a700718170a203e753d347c26d7907e7032118e2bc61349481ce5 3460062 binutils_2.24.51.20140818-1_i386.deb 310c52bccb7c99e99087a54809f954a77f38f52ccad84607b7191aaf0140c982 1749688 binutils-dev_2.24.51.20140818-1_i386.deb 4c4b45b08daa274a2b662613d2af48627ca76be8b8bb93839381e83c4e16f670 1706302 binutils-multiarch_2.24.51.20140818-1_i386.deb a2034ee117500f362e5a7234be546b86f3913070cd57a3300aa2fe2fa164aaaf 1206 binutils-multiarch-dev_2.24.51.20140818-1_i386.deb Files: 61b696cccbcaba398e1c0c7a0e93d099 499530 doc optional binutils-doc_2.24.51.20140818-1_all.deb 379dd6aef919986fabeba67097799ebe 16846756 devel optional binutils-source_2.24.51.20140818-1_all.deb f2d997ec111bb871cfd215387e88c25d 3460062 devel optional binutils_2.24.51.20140818-1_i386.deb 8becb49dcbc0f63f4266dd477012118d 1749688 devel extra binutils-dev_2.24.51.20140818-1_i386.deb 4a6c73b065d2148dcaa47ea3cfb6d32a 1706302 devel extra binutils-multiarch_2.24.51.20140818-1_i386.deb 09b50ec38d6e0ec16c59a19486369146 1206 devel extra binutils-multiarch-dev_2.24.51.20140818-1_i386.deb 68aa0d1a6b8b98348801b7cfb8d7ad96 1807 devel optional binutils_2.24.51.20140818-1.dsc 684246129e9f868627680cbcd25c5539 29393648 devel optional binutils_2.24.51.20140818.orig.tar.gz e308b88aa3ef68ca5be61a623849a970 75498 devel optional binutils_2.24.51.20140818-1.diff.gz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlPx81QACgkQStlRaw+TLJyQTgCgpW4XnOArYpfLSrnTW08hjwH4 WEoAn05GqDFg3IyGb+9BRsKVVZP9g/fU =bZxd -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/e1xjmmr-0006ap...@franck.debian.org
Accepted muparser 2.2.3-4 (source i386 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 29 Jun 2014 09:38:49 -0400 Source: muparser Binary: libmuparser-dev libmuparser2 libmuparser-doc Architecture: source i386 all Version: 2.2.3-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Scott Howard show...@debian.org Description: libmuparser-dev - fast mathematical expressions parse library (development) libmuparser-doc - fast mathematical expressions parser library (documentation) libmuparser2 - fast mathematical expressions parser library (runtime) Changes: muparser (2.2.3-4) unstable; urgency=medium . * Use debian/rules to clean out privacy breaches Checksums-Sha1: 569ac461d28c85cde063839fbed71b8f4989473d 2155 muparser_2.2.3-4.dsc 29f3eb266fbc19241334a963f4272d9d6220d51c 9120 muparser_2.2.3-4.debian.tar.xz 5ef82b2f70365803ef40d671a0ca6bd5eb59703c 28742 libmuparser-dev_2.2.3-4_i386.deb cf8352deec1f676006a5160e324656bda10062d4 122616 libmuparser2_2.2.3-4_i386.deb fc1d00e5f44dfb940f056eb1227087477f3dd412 607098 libmuparser-doc_2.2.3-4_all.deb Checksums-Sha256: 2175d3b08c2eee636edfa159162ca8d2eec0fc9f0c29c098419e0e488835135c 2155 muparser_2.2.3-4.dsc 4f54979a1435c7582dc8887385799c11aa5309d4415efa746da2fc6d98a63b28 9120 muparser_2.2.3-4.debian.tar.xz a202b9ae8b39b65928b99c06ca01671b2c2c1622ad1dcb7793850a372f42e286 28742 libmuparser-dev_2.2.3-4_i386.deb 3c52b6f469e6237f3af258acb7c941cb8edb1bc8c307acb9b7d94d8d0c290353 122616 libmuparser2_2.2.3-4_i386.deb 42be41ab4af4fe94177fd4018a33a48ab9ba176c36c4bd17b2def6831076e0c0 607098 libmuparser-doc_2.2.3-4_all.deb Files: ef657af99a07b80fb3d28efc56c0ab31 28742 libdevel extra libmuparser-dev_2.2.3-4_i386.deb 6b4edbb90a3984e60efe1887feb8a421 122616 libs optional libmuparser2_2.2.3-4_i386.deb 0a982bd0fead3b83f664ecfbadd046bc 607098 doc extra libmuparser-doc_2.2.3-4_all.deb 8250641b67935cdb85c30357fcdcf36f 2155 libs extra muparser_2.2.3-4.dsc a87ae7c36fe33a09e629f634f62ec257 9120 libs extra muparser_2.2.3-4.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJT8fS9AAoJEI7QYGkDfiTyDJkP/3M27uSEiOFf4Tus8OiatUaw r869MzvK7PAXzup7C7KZrweFdIoRjNIaqt0ipTNlNub4zPPK/rSINb8dirMggK1v jCRFfRFfChKlyTvUMbkEilr60+cWhHCFRRXBrJ3zeA0waL4SydR9YkrBbEmvZYWO P3pNYQGJVvnJDWIbi1+SucDhcwrZCjryIm7JJHU9w+6bAQxHdXnFMNuzN/m3QCn8 CqjsxicLVfSMsIf1kiVNieNyPX0efyNKVO2mVEjdwvYANl3iSg5NB3bNt1Jfo+Q9 JdWZTka3TcpLvTKlE7GmWOIqtF0HL6IP7iExA9TAhD2U+BDHRKngbNiS0jTNBJLQ 1LqdbiRqvEntHaUgUxk1jWY/2uTlIz+dlefv+XVUHzQGsqFglmqdXAqlWSgl2dLH sTlUIEkC22NZy164aH0h4SGNSwMEJplupWSpLyChrB2bI2SonKpNiZQbHeTDwPFN yS9i1wSdCWbTULAm6kpNqFSdRW1m5bW2RoCddX2io7SK+KzDiAfQMG5AV4m0PR/X dwKoYmcua48DNemADHFeDHFVlCaOWeRQ4kG/uZM00QoidkwzWJECNE39M6a6oF9K pUIvCfqbWu3k5sFDYE7Z2NlQnUYbrbEZzGDNbWlPjWF/I/LTpMYZ65axQ0AdZW6S EP01frzMxqQyi8gqFfdN =jChU -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/e1xjmns-0006hp...@franck.debian.org
Accepted cuneiform 1.1.0+dfsg-5 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 13:48:04 +0200 Source: cuneiform Binary: cuneiform cuneiform-common libcuneiform-dev libcuneiform0 Architecture: source all Version: 1.1.0+dfsg-5 Distribution: unstable Urgency: low Maintainer: Debian QA Group packa...@qa.debian.org Changed-By: Jakub Wilk jw...@debian.org Description: cuneiform - multi-language OCR system cuneiform-common - multi-language OCR system (common) libcuneiform-dev - multi-language OCR system (development) libcuneiform0 - multi-language OCR system (shared library) Changes: cuneiform (1.1.0+dfsg-5) unstable; urgency=low . * QA upload. * Orphan the package. Set Maintainer to Debian QA Group. * Update debian/watch to use the HTTPS protocol. * Bump standards version to 3.9.5 (no changes needed). * Don't use dh_testdir; instead, use makefile rules to ensure that debian/rules can be only run in the correct directory. * Force .debian.tar compression to bz2, to match .orig.tar compression. * Improve the get-orig-source target: + Use the POSIX 1003.1-1988 (ustar) format for tarballs. + Create temporary directory in /tmp. + Use “dpkg-parsechangelog -SVersion” to acquire the package version. * Improve DEP-8 tests: + Remove “Features: no-build-needed”; it's the default now. + Add tests that run adequate(1) against the packages. * Use dh-buildinfo: + Update debian/rules. + Add the package to Build-Depends. Checksums-Sha1: b7ba672bbbd40b3ee21d51efe40aa0fdba8a3d18 2128 cuneiform_1.1.0+dfsg-5.dsc 0116fde892e6d8459bc5b544f5441a8e126951e2 10727 cuneiform_1.1.0+dfsg-5.debian.tar.bz2 6b848df53f0dab6b0c800dd183c8c65590978a50 21840036 cuneiform-common_1.1.0+dfsg-5_all.deb Checksums-Sha256: 59aae048ca4ec586fc87e5141fda8cc1b458b837f4fbf85df86489b9d33e3f95 2128 cuneiform_1.1.0+dfsg-5.dsc 74c6a81f9bbbd288d19d45ca37852429d8d93cf65084089bd821b98f726f8a5b 10727 cuneiform_1.1.0+dfsg-5.debian.tar.bz2 979ba03f7b91838d15a00f60c7c4d88234d6d83be6bcdd42ad6e7c435035 21840036 cuneiform-common_1.1.0+dfsg-5_all.deb Files: 66a3bb0e59c3aa79d118aeea1be42da7 21840036 non-free/graphics optional cuneiform-common_1.1.0+dfsg-5_all.deb 3691c7cba98e35fe02065d5e0bab44c2 2128 non-free/graphics optional cuneiform_1.1.0+dfsg-5.dsc f0969d69ceaf1ca813d3072cceced2ed 10727 non-free/graphics optional cuneiform_1.1.0+dfsg-5.debian.tar.bz2 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8fGHAAoJEC1Os6YBVHX1fOgP/jWdl4ocg1iyQfxWzJ7Ng6U3 gyM5glbTlQIaQq4/NVpTU8noqjjpwg8rclLHycl6PnMkh7h/+CA1luov2hIbarFj Ic03wAwrDpoP7HBsjVF02IB+X76kPQkisOMx9D3XDk/aZhSV42twpfU8ZHVkFUlP JDiRFG4enhlhyyyGj4/SAD9T+QiMsSVFWeynSj09nbI6lC7uxpU6KX32Jr1Ycf05 sp4YkIngb4TIR1rAlJPqFSRD1uwtakd7HcaRaCZIkE45rFjN5SiF7ZJUqJbpo/S2 SH2qEiFFsGjJ86mq3ZnntXVkGBhvhUyHo7+8Imgoh/Tp7JKJzsHpt3aAI9Jo0BKs GUOk08cJPzv5+Sa4pSbrMKeYADji2hVK8FkioNLnE9TvNkTKr2ubN2TA/ji3mefK W4WAHRXYC3A6MlY/F9miQ2nI1RkrIqa4XHDIR9nALcF8SEBCoS+uEdgEXxEnWTM7 Dpf2du6O0xZiyBUJlLdWIbnC2vFzaYTRmw5js0iG6dC+3XTF8AxI2/aTzwjFwyFs EFrGxIipN99k9r2gMQqPY+AqC0KjJRut4ZILcLwEXH1tQBFECirA0WPcOWngHQHe +QYS6/KVZGXi/ndip7V7ZLsBdGKw9RVPah2QiINTBNinzq7dHeugphigQbw2M7LN 9vq+D2xYkBaslXFT4uoi =FweY -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/e1xjmbb-0008d2...@franck.debian.org
Accepted cb2bib 1.4.9-4 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 10:47:26 +0200 Source: cb2bib Binary: cb2bib Architecture: source amd64 Version: 1.4.9-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Filippo Rusconi lopi...@debian.org Description: cb2bib - extract bibliographic references from various sources Changes: cb2bib (1.4.9-4) unstable; urgency=medium . * mv upstream upstream/metadata; . * new debian/patches/fix-keywords-desktop-files.patch to fix missing keywords in desktop files. Checksums-Sha1: 22ff477c2be6cd449d9228464619529d954c45e6 2035 cb2bib_1.4.9-4.dsc 424fdb58d28e78ec32560a3899c1624e89107463 8212 cb2bib_1.4.9-4.debian.tar.xz 48a805a27d4d7f12f23ce98e53924912f1623fe2 1207578 cb2bib_1.4.9-4_amd64.deb Checksums-Sha256: 6768ad1aa59080f9b61a4afebc42db4c7f30680f8a938a0c6acec2f2f5d3e350 2035 cb2bib_1.4.9-4.dsc cf6b701f02374dbd24d3802b101da82d44c82d8313094e73f924a50aaa6b8b41 8212 cb2bib_1.4.9-4.debian.tar.xz 6466bbddc237b3c59922043582737578124ec162ebc3d84c2f1fa13f6beb6459 1207578 cb2bib_1.4.9-4_amd64.deb Files: ec242f09413569a7b7780a3e5ccffdb2 1207578 text optional cb2bib_1.4.9-4_amd64.deb 6a512d58a80f290e31f2ca843fa45205 2035 text optional cb2bib_1.4.9-4.dsc 3c6a2f7c3babfcb499b6e8f983c4fc5a 8212 text optional cb2bib_1.4.9-4.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8fvYAAoJEEGrSE12lM9CIbAQAKcjUMa/OM+kKY6FG9L/WWoC /qwQk+CEWebz8TlkmMw1DvmB3fLFuA4JSvIsMaCmmpW/srE1rxym6COfIENP153I xnnQNGw8Ri3LceteIfIFyTNiVG33L+s7+jODIPSW1oGJE3ljwSpcdHb/eFUbV1ok eTn6ukAVAMuNCWL9y9QOV7G2h2X9dwNZoXJrV94L/QyWFOio3GUfS+w4kX9cfjjq MJOgxZhOaPRht9J0Y9b0q5YkjaHsJTmN4s3R2yuyLtdOIh/J7UQHamaBpbbddqIo lrRG4c/Ixe7JQE/325MVbRmvwSqfI4ORXKHiDK2R3d8h0dBTrbRHZQm7ep697xKL 1vqiakt0NbhlBmXYwBEgrUDIrlXmX1uUfsm09DuxM8YGpeJ07CiqBnuHsT5n6xa+ fcT3Wv9DQ/Wy913hMRX4kews+/DHyfVZRMbVTXWPLH60l6gnLp2RwLpFiRPq/mNb N9c1r1wHydh9bibxru6PQoUziU9FEKG3HKDDdHDExMzc9y4FjCNlkdPxlPFDF8Rx hbb5piCCfLbyOzbuiuO1M1BzM+fCDBbwzKTSwcUi8QIRTJYlyDel/ejOHTSVw0fX EB0gM7nEiwUWuFhcsWUHJrfxUMy90U3+uVHhfJasueOMNOiz6VGiGH32kjQyxXU8 Q2NTlvalGA1EB4xiodQt =36D0 -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/e1xjmpw-00021q...@franck.debian.org
Accepted fakeroot 1.20.1-1.1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 14:58:00 +0200 Source: fakeroot Binary: fakeroot libfakeroot Architecture: source Version: 1.20.1-1.1 Distribution: unstable Urgency: medium Maintainer: Clint Adams cl...@debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: fakeroot - tool for simulating superuser privileges libfakeroot - tool for simulating superuser privileges - shared libraries Closes: 758406 Changes: fakeroot (1.20.1-1.1) unstable; urgency=medium . * Non-maintainer upload with maintainer permission. * Add patch glibc-xattr-types to fix the type of xattr functions. closes: #758406. Checksums-Sha1: 5090e6d7c00bbcfb4ee7444270826046b0d9b6fc 1899 fakeroot_1.20.1-1.1.dsc 36bd6dd165bc00e792118d6e83102775c4012848 43140 fakeroot_1.20.1-1.1.debian.tar.xz Checksums-Sha256: 9344c208725d631c8d07297a37f14dba0bc3436012a02065959b840ddc710193 1899 fakeroot_1.20.1-1.1.dsc 2000e7ea766b2c8c5e7d81742346abf09303fab3042cf159242a74dfbdb19150 43140 fakeroot_1.20.1-1.1.debian.tar.xz Files: 6c780ebab12f5cb4f366e32378451517 1899 utils optional fakeroot_1.20.1-1.1.dsc 253c2a915ccc426b5a956855c0181515 43140 utils optional fakeroot_1.20.1-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIVAwUBU/H6FLqceAYd3YybAQjbNg//Z0kWFlRRMm23+CQSbrSMQCOVAHK7NeER pYNWUOucx/E3XDMzqziQmJdBKOzTNHHpZZPGPAYlnGgr4UOvVSlX0VGZAWv8NxId PSi5Nnc6Hcwfp+5bl8U9V/KP89YE6WFWumfRtA9iEhXOIWPTMeGxLgpR+7hNN8Nm zXFnaD12ZVgcLwwUVwOuHcQDlUZbu0ADaFjI1jbhL1tlcqcmvxXE8D86YpRYeIHw XIiTjwKtjEARkxbv1PyDcOELYeQQltVAd/MIGcRjTrmqMV+qqVOoHOiHxESCJqFt E4ya38gn6Jb+yMFn7/C8RMwsr6ODRam5vOHl6tFSs0rwXxHJ8Zx8Y8Yz98JgYF8E 8yGn1tbNPlZzqzZACLq0vPAfDQELCGxBaJjq9oac+iJV1VadOlhU+AO1REAG+b/F YMIPRSET4UdFnMJDnB2KnTQgyeEsYCte8DbOOS327qAkq3yypdJgizrc4hslMGrO 6bGXBVKV2pI3qKayZRwC78OVH6cIP+AzXUGWGBHrxLwObNQvLuLW7rJtyvrEXSR6 kOlIqYJn1Xbi+PkZLEEVAi6gsp78LUKmXHBCzEvPhYNyvUmbMkklQBIh7HtJBZT3 8QQkTgME8R4GQ9ldZ7+6vtupDzU2+vR7Lke3PZIcGEs1b1dUxUAfAI9wysWD2Gdm fnM8aRdRJpY= =cJep -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/e1xjmpd-00022y...@franck.debian.org
Accepted lutefisk 1.0.7+dfsg-4 (source amd64 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 11:46:48 +0200 Source: lutefisk Binary: lutefisk lutefisk-doc Architecture: source amd64 all Version: 1.0.7+dfsg-4 Distribution: unstable Urgency: medium Maintainer: The Debichem Group debichem-de...@lists.alioth.debian.org Changed-By: Filippo Rusconi lopi...@debian.org Description: lutefisk - de novo interpretation of peptide CID spectra lutefisk-doc - De novo interpretation of peptide CID spectra - documentation Changes: lutefisk (1.0.7+dfsg-4) unstable; urgency=medium . * mv upstream upstream/metadata . * Switch to more concise debhelper rules syntax. Checksums-Sha1: 30ead86444166e323bc86b37a961a847791da1c6 2027 lutefisk_1.0.7+dfsg-4.dsc 384d71c7cbcce5cc16e0eea1f8a182fa84c924d7 8396 lutefisk_1.0.7+dfsg-4.debian.tar.xz 956b97f298e2e51b467eb833356ed7fce08f11d6 117360 lutefisk_1.0.7+dfsg-4_amd64.deb 885ddfec4a9d446ffc7e28674cb9725a42f20780 36506 lutefisk-doc_1.0.7+dfsg-4_all.deb Checksums-Sha256: 5086f141a051567e81a8895e75cc85c1d4491eae1837bdb523164865de13bc78 2027 lutefisk_1.0.7+dfsg-4.dsc 07f5aec0365e313005e99d3af07011fcfb7d6a565107f04c766be487a1ffa074 8396 lutefisk_1.0.7+dfsg-4.debian.tar.xz 9d55f1f00721eba4f47717bf298837176a4a05374f32861331d4283606d77919 117360 lutefisk_1.0.7+dfsg-4_amd64.deb eabd6de21bb3b8b97fc2363140e01cbef7a8f06cd93fc02c497d3717c875f169 36506 lutefisk-doc_1.0.7+dfsg-4_all.deb Files: cfd32f6a08eb965b7b5737aaa86c5b27 117360 science optional lutefisk_1.0.7+dfsg-4_amd64.deb 708060cdc4ec5fdc157951b94e2828e6 36506 doc optional lutefisk-doc_1.0.7+dfsg-4_all.deb d77e5b34fe92f0f16cd84e277bef048b 2027 science optional lutefisk_1.0.7+dfsg-4.dsc 9d897de5308324b24e57190a455a74b0 8396 science optional lutefisk_1.0.7+dfsg-4.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8frrAAoJEEGrSE12lM9CJw4QAI6UqDJ+8gEfkXdbH4loXI9w 04xBVMxkZnihXQYV8dbeheHvQmcOkYWSOBpxl0wFlZFFOJS0pZG2rXHceEzvJLp2 mLVnBIfhGsKS/YGUbMDNO8wtVmShfZ6egyUu97uNUPmZG7xGhAJyIZG2s/IG9Khx 4o8zjt/kqgI1q4QpeL4wssdXYzVf5AITjQFuUx40P3UtNCNNtiaGCvkvGQrJ5KTy XP7+/zPyjMUjGy66S0Hnc+f22uBKfVJOCBJwu7MjmTw7k+LBs1GFpPlGUOIuOf66 ajrkbJj1jr1LW7kFgj4Ot92Lr3RElTFUTdDNRAykDATnTNAbDA+9gmeozXs9WSSl gX7CnItFKhIPyZWqMKjqJPizKmc5+SsRdpLFchAY8TKMuGAQUB3buYQky+JrYPxD y/p/4Y3+d+9zvrOE0q7lapIZzodzBpeisJ534eu73OWwn5HlHILA7d3Qr3UtUMuD rGEEavVVPObTsEnDX7gtY4VGEQzlRCDJDKWBlk5jt850JXrDtvdAWdvtZ8jqW3EA IUQR3rW0kdEINWPkjzPwvUB8YfIX4gRCbj9I7QZb1eX0S9FWA0hSU7Jxm/BWRNBn 9+IJZVcrgc5suhqWrRFjb72e5jHwYg8huer8AdniJneMrexJeS2H+JYaOXfi4dEe e+y5I+f97gPen9umI+lI =6sXZ -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/e1xjmrr-0002g0...@franck.debian.org
Accepted mmass 5.5.0-3 (source all amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 11:47:51 +0200 Source: mmass Binary: mmass mmass-modules Architecture: source all amd64 Version: 5.5.0-3 Distribution: unstable Urgency: medium Maintainer: The Debichem Group debichem-de...@lists.alioth.debian.org Changed-By: Filippo Rusconi lopi...@debian.org Description: mmass - Mass spectrometry tool for proteomics mmass-modules - Mass spectrometry tool for proteomics - extension modules Changes: mmass (5.5.0-3) unstable; urgency=medium . * mv upstream upstream/metadata; . * Bump-up to Standards-Version: 3.9.5. Checksums-Sha1: 95565f9e2c303a6648c7c3abd609399f23bf4be7 2049 mmass_5.5.0-3.dsc 45557ba89c7a7549a3cb7ca7063351b63153e045 8192 mmass_5.5.0-3.debian.tar.xz 7ee40ae4e56902cfe73d0e30f0d4e02fc82223ac 2071544 mmass_5.5.0-3_all.deb 938aa48b4a5c8ddcdc3899af50bb45b60f5071c5 19892 mmass-modules_5.5.0-3_amd64.deb Checksums-Sha256: f9f2f54bbb182640a9aea64e77b060f658ba05c8d9c5045d2e7531fb39d69765 2049 mmass_5.5.0-3.dsc 14a4ca1a9fb46c437e49b0106d3994a3316fac1944a4a4fe39a88d69abec9f44 8192 mmass_5.5.0-3.debian.tar.xz afb83c697cde24ad76518a8d078a47d32e6fd47ad16cb120d36a1ac87be7bd04 2071544 mmass_5.5.0-3_all.deb 88a8579242362ac8773c85fcf7b03d547dbc4251e1f4f033b9344e2def2fbbce 19892 mmass-modules_5.5.0-3_amd64.deb Files: ea03d39e2d151ed2bf0a5f911ec572b5 2071544 science optional mmass_5.5.0-3_all.deb bcdb8949fe2b296405cac273e53bb26e 19892 science optional mmass-modules_5.5.0-3_amd64.deb cb4886f650be0f136f888f0a6fd0ae84 2049 science optional mmass_5.5.0-3.dsc 7f38a7f55297c66b8860c1d3f5de8dcf 8192 science optional mmass_5.5.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8fxWAAoJEEGrSE12lM9CWnkP/04AZWHJF3u200c4IrCqOS48 3woRIt6MGKYW9Flu3jZkRwFgbt+IY2JKLJHh/60qmTfTLihzsbAuHwF+F0Maw89q E0H0PyjmjRZphuOpUjZ2hdC1eZ1V4frLGxNAj31CJhfBHNsV154f1XfDtC9YS09a vPE8JraA7TOZ2hGydApAy4F7F4YhEHpn3wdhcuF6q1hzU8n2Q9WSxW1vFLCZzLR9 tMdOQ64fvgQftHeqnh5PlFMiszfuqGPsdyuk2L/9FIiUQK/4mqWp6JR+L8ji69Qa p+qPpwxweW69lVDrxsJlwDEt9fy2SeguKW9Z4d6G1xwdmmSkHzqqbO2VmeWnB9el dMbNr3sqmciHBnVHU46TilmBPT5a4wA1Z9NQ+wkjLLMF7RlmrKZ5JU4OTjTM30Ks IzOkvDiDtHuSObZWOHNx/DOM0aqlHC4gE563Q8uIYN7GGKMlr2MyGquhLqBYwUtb lj5bFA177xI6CEojwvJgSz6s55lzpOrEHxUqgT4SZ9GJc7389kHuY++esayR4TEe +Cwxi6QF1qyHZaRHxEaBAAdYF86jTGa4WcQyb41vJMuEZC8rcTTKmMUBoICs6WO1 8sjnrppDAGOlO7v6gqdi3BsLglWHxau1iRzr3PxDA5k1qwNdLyV9fHhSiI720grz CDlnY48426FI/O+8pyLB =P1xI -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/e1xjn4v-0004v8...@franck.debian.org
Accepted xen 4.4.0-2 (source all amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 18 Aug 2014 15:18:42 +0200 Source: xen Binary: libxen-4.4 libxenstore3.0 libxen-dev xenstore-utils libxen-ocaml libxen-ocaml-dev xen-utils-common xen-utils-4.4 xen-hypervisor-4.4-amd64 xen-system-amd64 xen-hypervisor-4.4-arm64 xen-system-arm64 xen-hypervisor-4.4-armhf xen-system-armhf Architecture: source all amd64 Version: 4.4.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Xen Team pkg-xen-de...@lists.alioth.debian.org Changed-By: Bastian Blank wa...@debian.org Description: libxen-4.4 - Public libs for Xen libxen-dev - Public headers and libs for Xen libxen-ocaml - OCaml libraries for controlling Xen libxen-ocaml-dev - OCaml libraries for controlling Xen (devel package) libxenstore3.0 - Xenstore communications library for Xen xen-hypervisor-4.4-amd64 - Xen Hypervisor on AMD64 xen-hypervisor-4.4-arm64 - Xen Hypervisor on ARM64 xen-hypervisor-4.4-armhf - Xen Hypervisor on ARMHF xen-system-amd64 - Xen System on AMD64 (meta-package) xen-system-arm64 - Xen System on ARM64 (meta-package) xen-system-armhf - Xen System on ARMHF (meta-package) xen-utils-4.4 - XEN administrative tools xen-utils-common - Xen administrative tools - common files xenstore-utils - Xenstore utilities for Xen Changes: xen (4.4.0-2) unstable; urgency=medium . * Remove broken and unused OCaml-support. Checksums-Sha1: 9d0b2916ce69a7f03e0dc1ddf75da7bd20a0753f 2769 xen_4.4.0-2.dsc d605eddc9a6a00a8894d74746296a32aa05af032 47792 xen_4.4.0-2.debian.tar.xz 00c4e226a7412f7308dc80f50fcb28a407634463 115882 xen-utils-common_4.4.0-2_all.deb 28ddc0b85b3cb3f97637616bdb85ce2fc92e2eaf 867646 xen-hypervisor-4.4-amd64_4.4.0-2_amd64.deb 1a3c612dcd02271d704e7d8068624c06ff1327a7 18482 xen-system-amd64_4.4.0-2_amd64.deb 9383a57e63a04cb79d8cff3844691ca1f57177b3 29264 libxenstore3.0_4.4.0-2_amd64.deb 4c9f49aebdcd46e459cbc511b91efe8e048e3111 293500 libxen-4.4_4.4.0-2_amd64.deb dd9a973235f0716162956de6110811263ec7345f 473924 libxen-dev_4.4.0-2_amd64.deb d6f33113c7e39e9ec10969ad47aa8e3aac01b47e 386948 xen-utils-4.4_4.4.0-2_amd64.deb 0a4b4db2778b2f86ca246d9849e3baf3a9e41c64 24732 xenstore-utils_4.4.0-2_amd64.deb Checksums-Sha256: b06d424ed98e98edb37b74f392fade7ddb4ba48ae7ea1a32ab3312c11d08c72e 2769 xen_4.4.0-2.dsc 45013bf33a192ae1aeccd0ac55aa45b1614268096e8de5f7a949c389cc07cc23 47792 xen_4.4.0-2.debian.tar.xz 2192787e9586f3e1f7e02a6f6c04c4e496469462ba66a1ffd9cd57aac7edc5c4 115882 xen-utils-common_4.4.0-2_all.deb 6df67475b22570a1fececa42461b2f6c32e8b6f08269d1d9fed087e8c39e85da 867646 xen-hypervisor-4.4-amd64_4.4.0-2_amd64.deb f2ee65540f59262567f6ed924e851e5ecb282ea5b798b81dec29f8c2b8733212 18482 xen-system-amd64_4.4.0-2_amd64.deb be4dedcce8cebbc38359ef09c627bb73dd769a34d32bdffe28776b8446dc2118 29264 libxenstore3.0_4.4.0-2_amd64.deb 58e1849b43d6530031c2b1b1256d04e4f1fe0c17822051d2f33b1b683880a078 293500 libxen-4.4_4.4.0-2_amd64.deb 7f794dbd37f160aef6f920d25c4bd17ead542fff6390e761a3d73f535849e8e7 473924 libxen-dev_4.4.0-2_amd64.deb 0e21b81f21a7a240d43588a0d9c14b86f3c4bfa8170c1dac2e32ac2820435372 386948 xen-utils-4.4_4.4.0-2_amd64.deb fa9576dd906f3e4aeb63bcb08059e1bac1a6dc257d371b950539793159f6f8d4 24732 xenstore-utils_4.4.0-2_amd64.deb Files: a21b2e0054b56f1509c5f1added91fa9 115882 kernel optional xen-utils-common_4.4.0-2_all.deb fb910276beadef96ace5b373bdef9e44 867646 kernel optional xen-hypervisor-4.4-amd64_4.4.0-2_amd64.deb ff2f06fb506f5b7754beb30396f8ce9a 18482 kernel optional xen-system-amd64_4.4.0-2_amd64.deb 0ac9c617a7209178fd1c9393f5ca558a 29264 libs optional libxenstore3.0_4.4.0-2_amd64.deb 83d99399b653a1d585d4da2934d0963d 293500 libs optional libxen-4.4_4.4.0-2_amd64.deb d5b287e72d819267b5beeab2dca7ebff 473924 libdevel optional libxen-dev_4.4.0-2_amd64.deb b8eb35f6d64d6a5c2793148eb5d7534d 386948 kernel optional xen-utils-4.4_4.4.0-2_amd64.deb c5ccdacaa22b451889fd963ef2201657 24732 admin optional xenstore-utils_4.4.0-2_amd64.deb d09d84d13e212667bedd3e5a2361353e 2769 kernel optional xen_4.4.0-2.dsc 50b44c83ad6f0e5d49f30072d25bfe45 47792 kernel optional xen_4.4.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJT8gHqAAoJEG2TiIWKaf5R0RQIAJrwpRNl3XcLARY+ph/5ixJQ 0XYd+dkdoP6hhvvb5Msmw6b6sjkUZGwReSRMwB+87DndX/AcQMqjOqDjx1Mlsa4n djGr5CIY24hF6Ymz0IsE0n7+SmEj4CIV5Uy03OQYVVFTZS/acX1Mh6i6nQGkBk+F 8E+VnaT/VIqk4vtCU/5pp22DpljCCYSPJOTqhGYiD1UO0mwI5RavQS0Ib+DXe4NW 3n7umWQWANqSLe9crnkI6K7iZWmjKba+59yAVJzC6g0emao5QYzQDuJAEAae5iam l+6b9G6cpTHuqqZ5kBPR4fT47o6B0WF7YVLIWnRymgOAcYSFo6Ecko7X0tQLb3o= =VUj2 -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/e1xjnky-0007ay...@franck.debian.org
Accepted barman 1.3.3-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 16:51:02 +0200 Source: barman Binary: barman Architecture: source all Version: 1.3.3-1 Distribution: unstable Urgency: medium Maintainer: Marco Nenciarini mnen...@debian.org Changed-By: Marco Nenciarini mnen...@debian.org Description: barman - Backup and Recovery Manager for PostgreSQL Changes: barman (1.3.3-1) unstable; urgency=medium . * Imported Upstream version 1.3.3 Checksums-Sha1: 93af9d9c3f0528f64c7f22cb3a6dfbf49b3402e1 1850 barman_1.3.3-1.dsc 6f8ff87332d58f1228b741c3a2ad5ea6c88f2da7 111462 barman_1.3.3.orig.tar.gz 60d14c7df440c7d8d0536e1f5192b44cfe9105f3 3000 barman_1.3.3-1.debian.tar.xz e568b19a44f5b0ad1b7577d544a0696aa27839ac 84568 barman_1.3.3-1_all.deb Checksums-Sha256: 34b24882675c18ef7a4422be8bc07e3bfd761f5b454cbf754158a02a9e2560ae 1850 barman_1.3.3-1.dsc 3e3af2fec16ac2836965a4c135d9ef4959ed690fb40ef06571d03ff526448468 111462 barman_1.3.3.orig.tar.gz b4fdfd6e160b4dcebaf9253fad668a43e958c2554dfecafce7d98d12773b0f5f 3000 barman_1.3.3-1.debian.tar.xz 427bc7eaf60685cc179adbf90409ead126155503df91350197dab962e09c188f 84568 barman_1.3.3-1_all.deb Files: 332ae2fcf91893eedbbcea966b0b8302 84568 database extra barman_1.3.3-1_all.deb 6c7df0e0c9452fb1f521ab4c80679e16 1850 database extra barman_1.3.3-1.dsc 49f5857a3bae3fa603f124ea50b1e11e 111462 database extra barman_1.3.3.orig.tar.gz d29e7935cf7ac1b6019556ae299667cc 3000 database extra barman_1.3.3-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8hURAAoJEFifA/AbpVA4RjcP/i2QnZ9H+v2Xsnno31JCvOpK 8b9Fgr7PrJldNBB/OIhK9OCnN97maKlu42NPjoO0B0fF1XWnDzc40VAhSd5mFJVJ dDlXTU8ASkdZEyBBhKIbxFF8Z2vs1+CXX4eR3MUzOCFGdImwSUcyjGVnxML/bSgQ xBKbYV82+Zpwk4SmQax5BLc0PayKwDbr0rFwYWhj308hzVgaJzYpWD2ygCqSvQeT NI22woecisCv/hcGD9APcDdT3nGttTEkrNQ3fgT9Vb/8L+U5d2w/NkDdhrmlMvPA k57r52zWrcdKF79WcTIwQCijXoY0TmqtbelQbG+/ATJ/Qi08HAg15OevfOM+xH0v 6fPTfzAV7YPtiGJ02uXOmoW+NfjKWYIWOvRiKk1o58GCPYSljFBk9NhEef/pMdm5 ME39wnTZyVk411xt15epjs8jPN5F2zue1rr4Opf+rrlvat4wzGYMzA30qKthQ+m1 cfd2sIdZEofhwsW5rUyexJYkEivTa+5/gpw5IAxR9wl0q96mbaRFrYglOg2shWlZ XFE8LiFToFsCxRFPtDoan3iMCRpr/a6xJASFPpjA/N/EK5lQX1XXZQJeI7Wx+unw dKyLUWwB7fuR05L81/eJi/k1SGNDet2nQIB9Ndh1PEpNsb91YZ7xfJ0FHtXC+Oa2 7N3rL3p8/XsAfLlAo5qx =yqaB -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/e1xjoik-0001ir...@franck.debian.org
Accepted discosnp 1.2.3-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 16:42:33 +0200 Source: discosnp Binary: discosnp Architecture: source amd64 Version: 1.2.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team debian-med-packag...@lists.alioth.debian.org Changed-By: Olivier Sallou osal...@debian.org Description: discosnp - discovering Single Nucleotide Polymorphism from raw set(s) of rea Changes: discosnp (1.2.3-1) unstable; urgency=medium . * New upstream release Checksums-Sha1: 5fbf7f7a90fb0cbad2586d3fa4ba3a31b3ddbb5a 1992 discosnp_1.2.3-1.dsc 1cf2ff009d5ce68220474a9ffc123ca1a191bf30 584787 discosnp_1.2.3.orig.tar.gz fafdc2f9b8de8305bd5479da43b89cf1aff9465e 11404 discosnp_1.2.3-1.debian.tar.xz ae0d496502988f3440a3846ea8133f1e626bb214 140924 discosnp_1.2.3-1_amd64.deb Checksums-Sha256: f6a7eb25e7c30eaf5d4c599b601ef9510108489615dc6f594e3c288b289fd0c8 1992 discosnp_1.2.3-1.dsc fe0b5ea4b09bbfadde10ec1ecee4057b08f5d4ac561bb101f93bfb1e25e99231 584787 discosnp_1.2.3.orig.tar.gz 3e420271d55966f90969d1ae7bfcbb311274c018c310ffbf7c8576a9acc0113b 11404 discosnp_1.2.3-1.debian.tar.xz d356d59de19a07fa4ec6b5889a882b21f422523b7f39f087718671ee84e7da61 140924 discosnp_1.2.3-1_amd64.deb Files: 9ff51398fc14031f1550773acdfe959f 140924 science optional discosnp_1.2.3-1_amd64.deb d2348d7b19ddd48e7a677f1e57d7f0a6 1992 science optional discosnp_1.2.3-1.dsc aad47dc9dc6974ef0c3a980d880ed5fd 584787 science optional discosnp_1.2.3.orig.tar.gz 4f2922fd36720042f18ac642598bcb4a 11404 science optional discosnp_1.2.3-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBCAAGBQJT8hfJAAoJEHjcaNsybYQ4M/4P/36HOaFYaT/dfLD+b8rqKkBj CQqbQa3Qppx4bL5tdTVs3/jqrE0td1S8KZaOAL+Y6s4izTTdzlbiK31M7j9O5KNI m9c72B2eoFlIcikrvF5JGRlFrhrcWekaTgAtzR/onbOeI/gyn7NrhiOQNtCdENjt vvv4l4gK1EVKgFdc0uI63AS30wxSEnQLikiGkh1QuPY27l8RlZofRrIQTlNkHpTg 7z9SfzdSMjiFT3P2cnolpOP500kAjvLa0urgUSZkjbmhp+ajOX5+6Bd5kNlkR2hS 5HDePVdCsO8ifvP+3Q2saKU7HM2zG1nG4ENbGH5ac0at4KXoY9wiJ16af1zS8E9k lBQ9lZJoADhHO/Wz2sIzfl1IK8SH6iAMzaQOLtqm8l5lyJjKKQHSIEL51eUL2f3Q AMCtLTnEZBJLzdGr0+xhj/6BMYV4MhoB1tO4YA9nZNcy/AVrGxWXJmdzi3jgcnTs 8hCRedcL+72Aa3BWl5kTCFL48FN8BtMLm4Y2RpcNNXTopJVk3b6448H289qkqmia i3MhbnbtkPiwa1NHuhCScDS2I58dW9m8YqI761RdrxTYsa/p7Xe6+ksl3aH8EwV7 l+a3JsTAFLqXBnTRTGFEEZ0LDmA8+bMX1Y2G/XxugGBnePih2LmdnQFriskriUY+ 8MFbnuEyIAXD9Cz9qqNq =/oiW -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/e1xjoje-0001rw...@franck.debian.org
Accepted lintian4python 0.28.3 (source all) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 15:27:41 +0200 Source: lintian4python Binary: lintian4python Architecture: source all Version: 0.28.3 Distribution: experimental Urgency: low Maintainer: Jakub Wilk jw...@debian.org Changed-By: Jakub Wilk jw...@debian.org Description: lintian4python - Debian package checker (for Python packages) Changes: lintian4python (0.28.3) experimental; urgency=low . * checks/python/egg-info: + Update pkg_resources documentation URL. . * checks/python/helpers: + Fix the “keys on reference is experimental” warning. . * checks/python/*.desc: + Use HTTPS URLs when they are available. . * data/python*-projects: + Update. . * debian/copyright (and other files): + Use HTTPS when referring to the GNU website. . * private/update-coverage: + Use glob.iglob(), instead of glob.glob(), in the place where a list is not needed. . * private/update-exception-names: + Use HTTPS URLs. . * tests/blackbox/*: + Use HTTPS URLs when they are available. Checksums-Sha1: f06e0d9fdd801e8d7566af8a13c79310aea5cf4d 1886 lintian4python_0.28.3.dsc 21392af5a70e7c8c4527902f0a08b39b2b4a4308 80528 lintian4python_0.28.3.tar.xz 5e55fd146722ecd6bfda810e054eb91d97c27ab5 59312 lintian4python_0.28.3_all.deb Checksums-Sha256: 760cbee0f790620a6abf5a4cbe8f0db2c6d4eb53a7fb4bb8d76bb542d8dc5934 1886 lintian4python_0.28.3.dsc cc2b95f3c6e024e5999ce1e26089510e9a9d5e935966224bba0967510f5370f0 80528 lintian4python_0.28.3.tar.xz 6f94e782ffa7a6a66e40b4c987a5175d8a484f379e5b2ed01ffac2c642972096 59312 lintian4python_0.28.3_all.deb Files: 59e73a9e6333efa40e85d251a3f28f51 59312 devel extra lintian4python_0.28.3_all.deb fce44d82bdd382faf689ee4cc9dbb45a 1886 devel extra lintian4python_0.28.3.dsc dfe9e104c5aa16f39e785b03f6c983e2 80528 devel extra lintian4python_0.28.3.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8gUPAAoJEC1Os6YBVHX1WZIP/0ArzQbCux7txTs99EKbY+hE 1/6+/BI6gKIX1vhPcpG6ovM6fZ/M83y50Hh9XthpWcTYbAILRTuOPmUaeTSkxPS0 vj4fs9uZDptHH+PK4UXWXIii9VYbLOkshNAyYPGnax33SZmGYbMSIoGVZYor43Ob GWlE9Mayg6b6SYuZe8HY/xDmKcDZJwvLYkeo5Y1aizCBfwDv5hnO4pUPQZcjJIJi WT819H+HlLNZ4tm3jAwzYPEA7UDTjjAx5P5pyudvCvUc6kqeINsnbC+mc93J4oZ3 yuhtnWbak6yxZs4M/UfYBV3rZGQ9rPSvNORJ7dYCKBWuqsRmNlvCUuT1IHIvHo6a BH58k5qXFcUrsiAqir6wnPZcc3Ij5uIw8l3Ap+vWUX+b1OUPdoSmlIc81T5CtdXR yUIvyU0Vo62PaGSxwIFtP7S+a2Xs7Hu2TyVmSLacWaTvcPkXiUjt43gDKbXy1AlP h29Ivndq6wqKo7t40rGWD11X3fVrAC/KpeSdUrdWkdwELoRHONraV1+6195nPFCC RSCPo5FXouChJvwy/FEEm6Qhx+jkXZZCoNEUaeziUtgw9upEY8g8JBaNTpeI9c4B bGZyMENitVollAQcDUgCLp9XYrqrv7rcO6nCPKWJWSR7eCaUtW79BKNWqk4Ysn1n toAoAZYUoaTG6LiRbhm5 =75eq -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/e1xjolg-0002tc...@franck.debian.org
Accepted mona 1.4-15-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Aug 2014 11:55:14 +0200 Source: mona Binary: mona Architecture: source amd64 Version: 1.4-15-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: Ralf Treinen trei...@debian.org Description: mona - theorem prover based on automata Changes: mona (1.4-15-1) unstable; urgency=medium . * new upstream release * add debian/watch * dh compatibility level 9 * standards-version 3.9.5: - migrate debian/copyright to machine-readable format 1.0 * rewrite the package build system: - start with the standard dh file for debian/rules - override dh_install to remove: - mona-mode.el which upstream's makefile installs in the wrong dir - usr/lib/*/*.la which we don't need - install mona-mode.el via debian/mona.install - install Examples/ via debian/mona.examples * we don't use chrpath any more, so we drop it from the build-dependencies * refresh lintian override non-dev-pkg-with-shlib-symlink (new location of lib files) * add autopkgtests, one test script: valid Checksums-Sha1: 9d88c0b1949f853e11fa6b3c02a35b45d374c48a 1954 mona_1.4-15-1.dsc 2f64239e6235352ada0f1ac153cfa6cb7b989478 681794 mona_1.4-15.orig.tar.gz e96748486abd9b29bd2beb4625e9d8c63a9b0a25 6116 mona_1.4-15-1.debian.tar.xz 0673304cd57009b3e385c6464f3ae893721cebea 394818 mona_1.4-15-1_amd64.deb Checksums-Sha256: 6f31ea744385195310766f9f630443297d374ca8331de00de64fe36ccf869fa0 1954 mona_1.4-15-1.dsc c107079dda8d4a9d82ffa382bad6fe206d6d995c9e8da978c33fe804bc26afcc 681794 mona_1.4-15.orig.tar.gz 94814e7a377474bf9e979f418fa49bad04454855ce7faf07b11b7c66a3ef0f51 6116 mona_1.4-15-1.debian.tar.xz e757d6b763dd4730aaa340c4629795a6d368b739128d610afe00a536f7eb83cc 394818 mona_1.4-15-1_amd64.deb Files: 3968bffdefedd65932647405ba9f3ad2 394818 science extra mona_1.4-15-1_amd64.deb 3376be58bf29a7165df21dcdee5748de 1954 science extra mona_1.4-15-1.dsc b93fe15cae360bbd9836420fe300c9bf 681794 science extra mona_1.4-15.orig.tar.gz c61f2162cf9883300bfb65cfe8027d97 6116 science extra mona_1.4-15-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJT8hS5AAoJEHRcR2bUys3/wKYP/RErhhIzsKbRf6xLaIy8q/tq f0iWuxOTczjIkbDOkb5L2WkUW7oYg/ZrOI0gLXomaDJmA/sst1fZ7Vj3jq4u+nit ypMWkfNFfvnu5+h6r8rmBOt4q5kgezfDcLweMxy83nimI1LjUZRuD44V7yvJM5o0 LFtY8/rT+wpA7MjEFpVrsCsDTT+X79C5KxphtNIMGrwNKsD6eCf0aLpZBwzUeaRf gnydhnVVT7RywF1OmwXvKZ03w3oFF1KLUcLI288XokJFD8vXHLTvp9fwpzS5czJq +rCyBPKppX93NpBFf76BmkzTqMsONe+LLmEcff6kvMYy8Lo2xCqYPw08gB82xvmU kZVCK4VsKDDjpxdNNEA25QnxMMH3C4omUUmihr3kGgCrGuXAyak7Rk9K8G9x5ozt rVh7ES5/z28r951ngCpbfGGYU2dpIRS9wpvTY647kveKQ79h0IdnOYcLAFWRCYwf 5T9jqufEGp/oyRlC6EM5q7UvF5R/3D7zVkcocRS6J86OwE2RFD3De5Fg7+d6mbqg Rvu4cPO3bfKK/a+rQBYH69GgkmXZrrL4mExxc18VFdPGjRiEH1ozP6sZHz37JAr0 x8CDuC45vPoeL6TGVJAf0MNtHKFoSpMuZXc7v+7nSQewJXESMOvnEbG+oAG464NT V7uag8oXXyfeZAgP/Mc8 =n9PM -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/e1xjoma-0002bc...@franck.debian.org
