Re: Package version numbers
On Wed, 16 Jan 2013, Christian PERRIER wrote: Quoting Jakub Wilk (jw...@debian.org): I would paint the bikeshed the following color: 0.8.51+dfsg1-0.1 Isn't that missing the fact that this is a t-p-u upload, which is indeed the start of a wheezy branch? So something we were naming +wheezyfoo in the past and which we now name +deb70u1. It's not really relevant because sid has already diverged and has a higher (upstream) version. So 0.8.51+dfsg1-0.1 is acceptable IMO. Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130116084941.gd18...@x230-buxy.home.ouaza.com
Re: Bootstrappable Debian - proposal of needed changes
On 01/16/2013 08:56, Neil Williams wrote: On Wed, 16 Jan 2013 00:26:53 +0100 Jakub Wilk jw...@debian.org wrote: Not only dpkg, but also wanna-build, sbuild, lintian, dak, and who knows what else... It's about which ones need to change. lintian response rates are not likely to be a problem - once this gets approved. dak doesn't necessarily need to do anything - most bootstrapping happens outside the main archive to prepare the ground for a move into debian-ports. Beyond that point, none of the bootstrapping support is required. If you want to use new Build-Depends features for packages in the main archive, dak needs patches too: dak rm -R will warn if Build-Depends are broken by a package removal. So it needs to be able to understand the field. python-apt would need to support the field for the same reason. And we would need the support in stable (or backports) for dak to use it. sbuild can use a specified bootstrapping dependency resolver, e.g. the one used to test the proposal itself. (As could pbuilder.) And the official buildd network would need to use these before any package using build profiles in Build-Depends could be uploaded to the main archive. Ansgar -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50f67199.5080...@debian.org
Re: Continue discussion about uscan enhancement (Was: Uscan enhancements revitalised)
Hi, On Fri, Jan 11, 2013 at 08:06:43PM +0100, Jonas Smedegaard wrote: On Fri, Jan 11, 2013 at 08:39:41PM +0900, Charles Plessy wrote: Not any more (hopefully) since I droped the `find -name` approach which turned out as insufficient (even if very attractive in the first place). In that case, the field in mothur's copyright file (and perhaps others) is not valid, as it uses [] wildcards, which are not recognized in Files fields. Uhmmm, I was not aware of this. Hmmm, this needs to be discussed. Any specific reason not to support [] wildcards? Without having dived deeply into this I'd consider this as an unneeded restriction. Needed or not, it is how the format looks now. Please avoid derailing into _development_ of the format. OK. So Fields-Excluded is currently not part of DEP5 anyway and so I revert my former answer that it fits the Files format because it may contain [] wildcards (and I do not see any problem because of this). I agree with Jonas that discussing the format might be delayed until after Wheezy release. 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: http://lists.debian.org/20130116094504.gj17...@an3as.eu
Re: Continue discussion about uscan enhancement (Was: Uscan enhancements revitalised)
Le Wed, Jan 16, 2013 at 10:45:04AM +0100, Andreas Tille a écrit : OK. So Fields-Excluded is currently not part of DEP5 anyway and so I revert my former answer that it fits the Files format because it may contain [] wildcards (and I do not see any problem because of this). I agree with Jonas that discussing the format might be delayed until after Wheezy release. Hi Andreas, http://bugs.debian.org/685506 is there to receive your proposal when you feel it is the right time. Cheers, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130116095700.gd2...@falafel.plessy.net
Re: Bug#698256: ITP: lz4 -- Extremely Fast Compression algorithm library
* Nobuhiro Iwamatsu iwama...@debian.org, 2013-01-16, 09:51: * URL : http://code.google.com/p/lz4/ * License : BSD 2-Clause License Programming Lang: C Description : Extremely Fast Compression algorithm library LZ4 is a very fast lossless compression algorithm. This uses Dictionary compression, and only supports compression and decompression unit blocks. This looks very promising, but also immature. The upstream makefile doesn't build a shared library, not even a static library, but only an executable (lz4demo). Are there any plans to change that? -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130116100258.ga3...@jwilk.net
Re: Packages with incomplete .md5sum files
2013/1/15 Andreas Beckmann deb...@abeckmann.de: On 2013-01-15 10:29, Julien Cristau wrote: There's no requirement for md5sums files in the first place AFAIK. How are incomplete md5sums worse than no md5sums? If anything this stuff should be minor IMO. If a package is shipping no .md5sum at all, it will be created by dpkg at installation time. A partial .md5sum however will not be completed. This hides some shipped files from debsums, defeating its purpose. I'm pretty sure modifying *any* shipped files in the maintainer scripts should be forbidden, although I didn't find a policy reference for this (this is made explicit for conffiles, what about normal files?). Packages violating this and hiding the fact by excluding the modified files from .md5sums ... should be fixed. There are some cases where debsums should IMHO consider things differently. In particular I mean those corresponding to files shipped under /var with d41d8cd98f00b204e9800998ecf8427e md5sum (empty files created with touch). These are clearly placeholders, being dpkg used to remove/reset them instead of doing things from maintainer scripts. Whether that makes sense or not depends on the package. -- Agustin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cahmxk7jujr7qhuavqcqdylfsuyzext-vu6dtu1ndlzsq20y...@mail.gmail.com
Re: Continue discussion about uscan enhancement (Was: Uscan enhancements revitalised)
Quoting Andreas Tille (2013-01-16 10:45:04) Hi, On Fri, Jan 11, 2013 at 08:06:43PM +0100, Jonas Smedegaard wrote: On Fri, Jan 11, 2013 at 08:39:41PM +0900, Charles Plessy wrote: Not any more (hopefully) since I droped the `find -name` approach which turned out as insufficient (even if very attractive in the first place). In that case, the field in mothur's copyright file (and perhaps others) is not valid, as it uses [] wildcards, which are not recognized in Files fields. Uhmmm, I was not aware of this. Hmmm, this needs to be discussed. Any specific reason not to support [] wildcards? Without having dived deeply into this I'd consider this as an unneeded restriction. Needed or not, it is how the format looks now. Please avoid derailing into _development_ of the format. OK. So Fields-Excluded is currently not part of DEP5 anyway and so I revert my former answer that it fits the Files format because it may contain [] wildcards (and I do not see any problem because of this). I agree with Jonas that discussing the format might be delayed until after Wheezy release. Copyright ile format 1.0 permits unofficial fields, so I disagree with your reasoning to avoid Files-Excluded:. Makes sense to me to a) introduce a new field that can later be adopted in a later revision of the format, but b) reuse existing defined *format* for that new field. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Bootstrappable Debian - proposal of needed changes
On Wed, 16 Jan 2013 10:23:37 +0100 Ansgar Burchardt ans...@debian.org wrote: On 01/16/2013 08:56, Neil Williams wrote: On Wed, 16 Jan 2013 00:26:53 +0100 Jakub Wilk jw...@debian.org wrote: Not only dpkg, but also wanna-build, sbuild, lintian, dak, and who knows what else... It's about which ones need to change. lintian response rates are not likely to be a problem - once this gets approved. dak doesn't necessarily need to do anything - most bootstrapping happens outside the main archive to prepare the ground for a move into debian-ports. Beyond that point, none of the bootstrapping support is required. If you want to use new Build-Depends features for packages in the main archive, dak needs patches too: dak rm -R will warn if Build-Depends are broken by a package removal. So it needs to be able to understand the field. That depends whether bootstrapping foo fields need to cover the *inclusion* of extra Build-Depends only for bootstrapping which would not normally be installed as a default Debian build. Otherwise, dak can have a simpler patch to just allow but ignore foo content in Build-Depends. The main archive only needs to carry this extra information without needing to act upon it. If dak needs patches to allow-and-ignore the new information, that can be done. Most bootstrapping changes are to turn off features by not build-depending on packages which can be turned off in debian/rules. I'm not sure if we are going to find this situation: Source: foo Build-Depends: bar !embedded, baz +embedded (especially where bar does not depend on baz and therefore standard Debian builds would not normally install it. If bar depends on baz then this isn't a problem and dak can ignore all the content without any effects.) We may be able to implement dak support to allow-and-ignore and then deal with the above corner-case later. Wookey, Johannes: has anything come up so far which would trigger this corner case? python-apt would need to support the field for the same reason. And we would need the support in stable (or backports) for dak to use it. backports would be manageable. sbuild can use a specified bootstrapping dependency resolver, e.g. the one used to test the proposal itself. (As could pbuilder.) And the official buildd network would need to use these before any package using build profiles in Build-Depends could be uploaded to the main archive. Isn't that also a case of allow-but-ignore or allow-with-hardcoded-default ? -- Neil Williams = http://www.linux.codehelp.co.uk/ pgp21cUFnY3kQ.pgp Description: PGP signature
Bug#698293: ITP: nafe -- toolset for editing psf format consolefonts
Package: wnpp Severity: wishlist Owner: Gerfried Fuchs rho...@debian.org * Package name: nafe Version : 0.1-1 Upstream Author : Eric Price corvusco...@users.sourceforge.net * URL : http://nafe.sourceforge.net/ * License : GPLv2 Programming Lang: C Description : toolset for editing psf format consolefonts The package contains two tools: psf2txt and txt2psf. With the help of these tools it is possible to change consolefonts in psf format. To not lose the embedded unicode character table you need the psf table tools from the console-tools package, too. Enjoy, Rhonda -- Fühlst du dich mutlos, fass endlich Mut, los | Fühlst du dich hilflos, geh raus und hilf, los| Wir sind Helden Fühlst du dich machtlos, geh raus und mach, los | 23.55: Alles auf Anfang Fühlst du dich haltlos, such Halt und lass los| -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130116130631.ga27...@anguilla.debian.or.at
Re: Continue discussion about uscan enhancement (Was: Uscan enhancements revitalised)
On Wed, Jan 16, 2013 at 12:35:27PM +0100, Jonas Smedegaard wrote: OK. So Fields-Excluded is currently not part of DEP5 anyway and so I revert my former answer that it fits the Files format because it may contain [] wildcards (and I do not see any problem because of this). I agree with Jonas that discussing the format might be delayed until after Wheezy release. Copyright ile format 1.0 permits unofficial fields, so I disagree with your reasoning to avoid Files-Excluded:. I do *not* want to avoid 'Files-Excluded'! I was just asked: By the way, are there differences with the syntax of the Files field ?[1] and my answer was[2] Not any more (hopefully) ... Now Charles has proven my hopes wrong in[3]. Makes sense to me to a) introduce a new field that can later be adopted in a later revision of the format, but b) reuse existing defined *format* for that new field. The Files field seems to be a specific form of the Whitespace-separated lists[4] format (at least the restriction about [] is made only in the Files field definition[5].) It is certainly my fault that I did not joined DEP5 discussion to question this definition which puts a restriction into effect that I do not understand. But I agree that it does not make any sense to reopen a DEP5 debatte now. On the other hand I do not see why I should put any restriction onto a new field if I can use the defined Whitespace-separated lists[4] format. And yes, for sure, I perfectly agree that it is a pretty reasonable goal to use the same format for Files and Files-Excluded and if you want to be safe you might refrain from adding [] wildcards into your copyright files. But for the moment I see no reason to remove this from files living in VCS (exclusively, not released files) that are perfectly working with tools adapted to this (also in VCS not released) just to follow a potential outcome to a non-existing decision. Kind regards Andreas. [1] https://lists.debian.org/debian-devel/2013/01/msg00189.html [2] https://lists.debian.org/debian-devel/2013/01/msg00202.html [3] https://lists.debian.org/debian-devel/2013/01/msg00242.html [4] http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#white-space-lists [5] http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#files-field -- 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: http://lists.debian.org/20130116131955.ge5...@an3as.eu
Re: Continue discussion about uscan enhancement (Was: Uscan enhancements revitalised)
Quoting Andreas Tille (2013-01-16 14:19:55) On Wed, Jan 16, 2013 at 12:35:27PM +0100, Jonas Smedegaard wrote: OK. So Fields-Excluded is currently not part of DEP5 anyway and so I revert my former answer that it fits the Files format because it may contain [] wildcards (and I do not see any problem because of this). I agree with Jonas that discussing the format might be delayed until after Wheezy release. Copyright ile format 1.0 permits unofficial fields, so I disagree with your reasoning to avoid Files-Excluded:. I do *not* want to avoid 'Files-Excluded'! Ok. I misunderstood. Makes sense to me to a) introduce a new field that can later be adopted in a later revision of the format, but b) reuse existing defined *format* for that new field. The Files field seems to be a specific form of the Whitespace-separated lists[4] format (at least the restriction about [] is made only in the Files field definition[5].) It is certainly my fault that I did not joined DEP5 discussion to question this definition which puts a restriction into effect that I do not understand. But I agree that it does not make any sense to reopen a DEP5 debatte now. On the other hand I do not see why I should put any restriction onto a new field if I can use the defined Whitespace-separated lists[4] format. And yes, for sure, I perfectly agree that it is a pretty reasonable goal to use the same format for Files and Files-Excluded and if you want to be safe you might refrain from adding [] wildcards into your copyright files. But for the moment I see no reason to remove this from files living in VCS (exclusively, not released files) that are perfectly working with tools adapted to this (also in VCS not released) just to follow a potential outcome to a non-existing decision. Sorry if I am dense... You agree that Files and Files-Excluded should ideally use same format, but you find it more important that Files-Excluded be flexible - even if Files as currently defined is not. Did I get that correct? In case it was unclear: I find it more important for Files and Files-Excluded to use _same_ format than for Files-Excluded to use an ideal format _now_. I find it better to discuss (later!) relaxing that Files format, which would then affect both Files and Files-Excluded, than to now try second-guess what Files format might be relaxed to allow in the future. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Bootstrappable Debian - proposal of needed changes
Johannes Schauer writes (Bootstrappable Debian - proposal of needed changes): the following is an email written by Wookey and myself. Firstly, I want to say thank you! This seems like excellent work to me. 5. Cross-Builds field = For even further automation and also for quality assurance, we propose another new field for source packages which indicates whether or not this source package is supposed to be cross compilable. Is it possible that packages might only cross build for certain targets ? Or only for certain hosts ? 6. Conclusion = ... The question remains of how many source packages would have to have the proposed new fields added to them to make a full bootstrap from zero possible. If the Gentoo USE flags were not too far off and assuming or tools do the correct thing so far, then: - the number of source packages that has to be modified with the new fields is at maximum 83 (there might be a smaller set). That sounds very manageable. The main questions to this list are: - should Debian be bootstrappable in a fully automated fashion? We created the algorithms that can allow this to happen, we just need more meta data and a way to encode it Yes, please. - do the proposals for the needed fields sound convincing? Can they be improved? Do they have fundamental flaws? I haven't spotted anything hideously wrong. I have three suggestions for changes: * Packages should explicitly declare which profiles they support. This should be done with a Profile field in the source stanza of debian/control. * It should be made explicit in the spec that building occurs with zero or one profile, not several. * The concrete syntax in build-depends should not use but rather reuse the architecture qualification syntax. In more detail: I worry about this: Build-Depends: huge (= 1.0) [i386 arm] !embedded !stage1, tiny This takes the metacharacters and reserves them for build profiles. Metacharacters are very scarce and should only be used when necessary. And indeed the profiles work very much like architectures, just in a different namespace and with different rules for defining whether a profile applies to a particular build. So I think it would be better to make using of this commonality, save a metacharacter, and have a more regular syntax. For example: (a) Build-Depends: huge (= 1.0) [i386 arm] [!profile:embedded !profile:stage1] Another possibility is this: (b) Build-Depends: huge (= 1.0) [i386 arm] [profile: !embedded !stage1] Or this: (c) Build-Depends: huge (= 1.0) [i386 arm] [!embedded !stage1] (Since unknown arches and unknown profiles can be safely ignored as no match, the parser doesn't need to know which of the keywords are profiles and which are architectures.) All of these are a bit longer because they use an identifier rather than a metacharacter to indicate that the qualifier is talking about profiles. I think this is the right tradeoff. The arrangement could be extended later by adding new keywords alongside profile:, if we wanted different qualifiers (whose application to a particular build is specified in a different way to arches and profiles). Of these I prefer (a) or (b). (c) doesn't have a satisfactory answer to the namespace registry. (b) has a more irregular syntax but its fields are slightly more readable and shorter than (a). The semantics I would propose for my unified qualifier syntax are as follows: * Multiple qualifiers (each with the syntax [...]) may occur in one build-dependency. The dependency applies iff _all_ the qualifiers match. * A qualifier must contain either only positive labels (in which case it matches iff any label is true), or only negated ones (ie prefixed with !) (in which case it matches iff no label is true). * A label not known to the software processing the field is taken not to match. * (a) Labels are scope:value, or arch. Labels in a single qualifier must be in the same scope (but this need not be enforced by parsers). There is a registry of scopes, which defines the registry of labels within each scope. or (b) Qualifiers start with scope: iff the scope isn't architecture. Label names are meaningful within scopes. There is a registry of scopes, which defines the registry of labels within each scope. or (c) Labels may be names of build profiles, architectures, or anything else. option (i) There is a registry of labels. option (ii) There is no registry of labels and the label namespace is a free-for-all. * We initially define one scope profile, for build profiles. A build profile is an optional variation that can be applied to a particular package, for the purpose of reducing the build dependencies and/or avoiding the building of unneeded binary packages. The builder of a package
Re: Bootstrappable Debian - proposal of needed changes
Am 16.01.2013 13:05, schrieb Neil Williams:
The main archive only needs to carry this extra information without
needing to act upon it. If dak needs patches to allow-and-ignore the new
information, that can be done. Most bootstrapping changes are to turn off
features by not build-depending on packages which can be turned off in
debian/rules.
I'm not sure if we are going to find this situation:
Source: foo Build-Depends: bar !embedded, baz +embedded
(especially where bar does not depend on baz and therefore standard Debian
builds would not normally install it. If bar depends on baz then this isn't
a problem and dak can ignore all the content without any effects.)
We may be able to implement dak support to allow-and-ignore and then deal
with the above corner-case later.
Wookey, Johannes: has anything come up so far which would trigger this
corner case?
cross building the gcc-4.x packages requires additional build dependencies on
{gobjc++,gccgo,gfortran}-target-gnu-type packages.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50f6b2e2.9000...@debian.org
Re: Continue discussion about uscan enhancement (Was: Uscan enhancements revitalised)
On Wed, Jan 16, 2013 at 02:43:54PM +0100, Jonas Smedegaard wrote: Sorry if I am dense... I like you because I know you are dense. ;-) You agree that Files and Files-Excluded should ideally use same format, but you find it more important that Files-Excluded be flexible - even if Files as currently defined is not. Did I get that correct? In case it was unclear: I find it more important for Files and Files-Excluded to use _same_ format than for Files-Excluded to use an ideal format _now_. I find it better to discuss (later!) relaxing that Files format, which would then affect both Files and Files-Excluded, than to now try second-guess what Files format might be relaxed to allow in the future. Let me put it like this: My *current* implementation of uscan is accepting [] wildcards. I would need to squeeze my mind to reduce the functionality of find to implement the Files format definition. If somebody volunteers to send me a patch I would consider applying it. For the moment I see no need for action before a discussion has started. I have documented the difference between the `Files` and `Files-Excluded` formats in the Wiki[2] to make sure we will not forget. Feel free to add a hint to advise users to refrain from using [] wildcards. Kind regards Andreas. [1] http://anonscm.debian.org/gitweb/?p=users/tille/devscripts.git;a=blob;f=scripts/uscan.pl [2] https://wiki.debian.org/UscanEnhancements -- 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: http://lists.debian.org/20130116141122.gh5...@an3as.eu
Re: Bootstrappable Debian - proposal of needed changes
Am 15.01.2013 19:18, schrieb Johannes Schauer: This mechanism also covers cross-compiler bootstraping. The eglibc, gcc, and kernel packages already have the neceassary staged-build info, but the build profiles (1.) part is also needed to specifiy the reduced build-deps. The cross-toolchain bootstrap ceases to be a special case if treated this way and just becomes packages to be built in stages using the profiles mechansim, like many others in the base system (but for build arch taregtting host, arch, rather than built for host-arch). See the wiki article at [11]. [11] http://wiki.debian.org/MultiarchCrossToolchains Please stop calling this MultiarchCrossToolchains. It was already wrong when used in the Emdebian context, and on some GSOC pages. What you are apparently aiming for is a cross compiler re-using the target libraries built (natively). However this is not yet done, requires dependencies on foreign architectures and only is a very special case, not helping for targets where these are not yet available (like for the arm64 bootstrap). Having a cross-toolchain just built on the host architecture (targeting the target architecture), should still be an option. Binutils, GCC, clang, and probably more packages in Debian are currently aware about the multiarch locations, including native and cross compilers. So please don't hijack this term for your very specific view on a cross compiler. The so called cross-toolchain bootstrap is overly complex and probably should not be handled by staged builds, but by building from a combined source tree. Matthias -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/50f6bb1f.7060...@debian.org
Re: Bootstrappable Debian - proposal of needed changes
Am 16.01.2013 14:50, schrieb Ian Jackson:
* We initially define one scope profile, for build profiles.
A build profile is an optional variation that can be applied
to a particular package, for the purpose of reducing the
build dependencies and/or avoiding the building of unneeded
binary packages.
The builder of a package may apply one single build profile.
Build profile names are a controlled namespace and are allocated by
the Debian project. The following are defined:
profile:stage1
profile:stage2
For multi-stage bootstrap. A package may only
declare support for stage2 if it supports stage1 as well.
These are not a global ordering across the distribution.
Rather, stage1 is the most limited build of this
particular package. stage2 is an intermediate bootstrap
build, support for which is provided only if it is
necessary to build this particular package three times.
this only takes care about packages with a reduced package set built, or
packages with reduced functionality. There are same cases missing:
- extra build dependencies for cross builds, like for gcc-4.7:
{gobjc++,gccgo,gfortran}-target-gnu-type
profile:cross?
- build dependencies for running the check target. Usually these
dependencies can be ignored when cross-building packages, or when
building a package natively with DEB_BUILD_OPTIONS=nocheck.
profile:check? There are not few packages which can be easier
cross-built when identifying and dropping these build dependencies.
So it does make sense to build with two profiles like stage1 check.
Matthias
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50f6c07f.5050...@debian.org
Re: Bootstrappable Debian - proposal of needed changes
On Wed, 16 Jan 2013 13:50:17 + Ian Jackson ijack...@chiark.greenend.org.uk wrote: For even further automation and also for quality assurance, we propose another new field for source packages which indicates whether or not this source package is supposed to be cross compilable. Is it possible that packages might only cross build for certain targets ? Or only for certain hosts ? For certain host architectures: yes, definitely. Any source package which includes assembly (there are more than most people expect) and any package which then has a build dependency on a binary package built from the source package(s) containing assembly and so on. (This is a separate discussion, please don't hijack this thread for the pros and cons of assembly in packages.) Also, cross-building of kernels other than Linux and the packages which build-depend on the headers for such kernels is often not supported by cross-building toolchains. These failures are recursive and it can be very hard to identify why package A wouldn't cross-build until the bootstrapping process shows that it absolutely requires a package N levels down the dependency chain which fails to cross build. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpPaMTOwMXem.pgp Description: PGP signature
Re: Continue discussion about uscan enhancement (Was: Uscan enhancements revitalised)
Quoting Andreas Tille (2013-01-16 15:11:22) On Wed, Jan 16, 2013 at 02:43:54PM +0100, Jonas Smedegaard wrote: Sorry if I am dense... I like you because I know you are dense. ;-) You agree that Files and Files-Excluded should ideally use same format, but you find it more important that Files-Excluded be flexible - even if Files as currently defined is not. Did I get that correct? In case it was unclear: I find it more important for Files and Files-Excluded to use _same_ format than for Files-Excluded to use an ideal format _now_. I find it better to discuss (later!) relaxing that Files format, which would then affect both Files and Files-Excluded, than to now try second-guess what Files format might be relaxed to allow in the future. Let me put it like this: My *current* implementation of uscan is accepting [] wildcards. I would need to squeeze my mind to reduce the functionality of find to implement the Files format definition. If somebody volunteers to send me a patch I would consider applying it. For the moment I see no need for action before a discussion has started. I have documented the difference between the `Files` and `Files-Excluded` formats in the Wiki[2] to make sure we will not forget. Feel free to add a hint to advise users to refrain from using [] wildcards. Fine with me that uscan can do more than needed. Fine with me if uscan Files-Excluded feature is promoted (e.g. in its manpage) to support same format as Files field. Problematic in my opinion if uscan *documented* format is a custom format. Fine with me if uscan *documented* format is the current Files field format, leaving that additional functionality as an undocumented (mis)feature. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Bootstrappable Debian - proposal of needed changes
Hi, On Wed, Jan 16, 2013 at 01:50:17PM +, Ian Jackson wrote: 5. Cross-Builds field = For even further automation and also for quality assurance, we propose another new field for source packages which indicates whether or not this source package is supposed to be cross compilable. Is it possible that packages might only cross build for certain targets ? Or only for certain hosts ? Yes. But for the intended purpose of this field, it does not make much sense to encode the information on which architecture and for which architecture a source package cross compiles. If a source package would not compile on some architectures or for some architectures, then it would be Cross-Builds:No. If the Cross-Builds field is being introduced, then only a few base source packages *must* carry this field. For all other source packages, this field would be optional. The tools we developed can always be used to calculate which source packages are necessary to cross compile a minimal build system. Therefor, this field would only be: - a more obvious way for the maintainer of a source package to know that his/her package is one of those that must be cross compilable for any upcoming architecture. - a more obvious way for a bootstrapper to see which native build dependency cycles could easily be solved by cross compiling some source packages The field is therefor rather low priority compared to the other ideas. I haven't spotted anything hideously wrong. I have three suggestions for changes: * Packages should explicitly declare which profiles they support. This should be done with a Profile field in the source stanza of debian/control. Good idea - this would make it even more analogous to the Architecture field and its meaning in source and binary stanzas in ./debian/control. * It should be made explicit in the spec that building occurs with zero or one profile, not several. As far as I understood (but I'm not the one who actually cross-compiles things in real life), different dependencies might be needed during cross compilation of some source packages. If that source package must be cross compiled for a minimal base system and if it also must be built with reduced build dependencies, then two build profiles at the same time are necessary. In this case a cross and stage1 profile. * The concrete syntax in build-depends should not use but rather reuse the architecture qualification syntax. You basically propose to extend the architecture qualification syntax from a single disjunction into a conjunctive normal form expression. If any number of disjunctions is allowed, your proposal will also support more than one profile at the same time. What would an example of a different namespace than profile: be? From the perspective of dependency analysis, your proposal seems to be able to carry all information that is needed for it. I leave it up to you guys to decide on which you like better. Thanks for your input! cheers, josch -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130116160543.GA30841@hoothoot
Re: Bootstrappable Debian - proposal of needed changes
Hi,
On Wed, Jan 16, 2013 at 04:00:15PM +0100, Matthias Klose wrote:
this only takes care about packages with a reduced package set built,
or packages with reduced functionality. There are same cases missing:
- extra build dependencies for cross builds, like for gcc-4.7:
{gobjc++,gccgo,gfortran}-target-gnu-type
profile:cross?
- build dependencies for running the check target. Usually these
dependencies can be ignored when cross-building packages, or when
building a package natively with DEB_BUILD_OPTIONS=nocheck.
profile:check? There are not few packages which can be easier
cross-built when identifying and dropping these build dependencies.
So it does make sense to build with two profiles like stage1 check.
You probably mean a nocheck profile?
Your first example indeed demonstrates why multiple profiles are useful
to be enabled at once.
The second example can be accomplished with only one profile by marking
all dependencies that are not being needed by a nocheck profile as not
being needed by the stage1 profile as well.
So instead of:
Build-Depends: foo !stage1, bar !nocheck
and then needing two profiles at the same time, one could have:
Build-Depends: foo !stage1, bar !nocheck !stage1
Though I agree that the first option looks more maintainable.
There is also the idea of a nodocs profile which would work like
DEB_BUILD_OPTIONS=nodocs.
Whether or not nocheck and nodocs can/should become build profiles
is of course still to be debated.
An argument for them becoming build profiles is, that the analysis
algorithm would then be able to just choose the less dangerous nodocs
or nocheck profile instead of a stage1 profile if they break a
dependency cycle. How safe/dangerous choosing a profile is, could be
evaluated by the number of binary packages which are not built with a
given profile but which are needed as build dependencies by other source
packages. While a stage1 profile is likely to not build binary
packages which are needed somewhere else, the nodocs and nocheck
profiles will likely not lead to needed binary packages not being
compiled.
So nocheck and nodocs profiles could allow safer reduced builds.
An argument against nodocs might be, that since (most?) *-doc packages
are Architecture:all, the build dependencies that are needed by them to
be built are already/should be included in Build-Depends-Indep anyways.
The current algorithms discard the Build-Depends-Indep field as
Architecture:all binary packages do naturally not need to be built
during the bootstrapping process.
cheers, josch
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130116162652.GB30841@hoothoot
Pure-mulitarch Cross Toolchains
+++ Matthias Klose [2013-01-16 15:37 +0100]: Am 15.01.2013 19:18, schrieb Johannes Schauer: This mechanism also covers cross-compiler bootstraping. The eglibc, gcc, and kernel packages already have the neceassary staged-build info, but the build profiles (1.) part is also needed to specifiy the reduced build-deps. The cross-toolchain bootstrap ceases to be a special case if treated this way and just becomes packages to be built in stages using the profiles mechansim, like many others in the base system (but for build arch taregtting host, arch, rather than built for host-arch). See the wiki article at [11]. [11] http://wiki.debian.org/MultiarchCrossToolchains Please stop calling this MultiarchCrossToolchains. It was already wrong when used in the Emdebian context, and on some GSOC pages. What you are apparently aiming for is a cross compiler re-using the target libraries built (natively). The target libraries can be built natively or cross-built. Clearly cross-building is necessary when the target architecture does not yet exist (e.g. arm64). The point is that the library dependencies use the multiarch file locations and mechanisms, rather than extra copies in different locations. I agree this is separate from multiarch path support in the cross-toolchain for finding libraries and headers for non-toolchain libs. What term would you like me to use for this cross-toolchain arangement? multiarch-libraryCrossToolchains? PureMultiarchCrossToolchains? FullyMultiarchedCrossToolchains? Yes it's a bit confusing, because multiarch affects various aspects of the toolchain. I'm happy to use a different name to avoid confusion, this just seems to me to be the logical conclusion of 'mulitarching the cross toolchains' (see discussion below), so it seemed a reasonable name. However this is not yet done, It was done in Thibg's GSOC project for 4.7.2-4. Yes it needs more work to properly integrate, test, and make bootstrappable, but we have a working implementation (modulo keeping up with your amazing rate of new uploads :-). (For which kudos, even if it does make it hard to keep up!) requires dependencies on foreign architectures It does. and only is a very special case, This is where we seem to disagree. I think it should be the standard case (for binary distro cross-toolchains). not helping for targets where these are not yet available (like for the arm64 bootstrap). Having a cross-toolchain just built on the host architecture (targeting the target architecture), should still be an option. This is still an option - you just cross-build the target libraries as part of the bootstrap. The wiki page gives the runes. I am not convinced of the benefit in also maintaining toolchains with these libraries installed twice in different locations, now that we have multiarch to make this unnecessary. But I would like to see much wider discussion of this issue so we can reach conclusions as a project on what the default cross-toochain setup should be, and what non-default methods are also worth maintaining in the packaging. The main disadvantage of making use of the multiarch libraries is the need to keep libgcc, libstdc++ etc in version lockstep across architectures. But this applies to multiarch in general for all libraries, and is something we manage in Debian as part of being a distro. It is something to carefully consider. Is the reduced independence of the cross-toolchain library versions a fatal flaw? The main advantage is that the code you build against is actually the code the toolchain was built against, not some other code that happens to be installed in the expected location. Also build-dependencies work automatically without having to have 'equivs' packages for libgcc1, libstc++6-dev etc until the real native ones are built. And having one copy of libgcc1:targetarch, libstdc++:targetarch on the system instead of two seems like good practice to me. Another advantage is that for normal cross-toolchain builds you don't need to do a 3-stage bootstrap build, because you already have the target-arch libc, libgcc1, libstc++ etc available so you just need to rebuild gcc without staging. Much quicker and simpler. This is (fundamentally) how the emdebian toolchain builds worked for many years. Using multiarch libraries also greatly simplifies the gcc packaging (if we are able to drop multilib equivalents as a result). Again we disagree on this point. I think we should be encouaging people to install arm-linux-gnueabi and arm-linux-gnueabihf cross-compilers if they want to target both those arches, not install one or the other, each of which is multilibbed to output code for both, with a corresponding collection of libgcc's. I realise that upstream is not yet convinced of the benefits of this view of the world, but I think we should be using it and demonstrating its effectiveness (assuming we believe that multiarch is actually the right way to be dealing with multiple ABIs)
Re: Bootstrappable Debian - proposal of needed changes
On Tue, Jan 15, 2013 at 07:18:40PM +0100, Johannes Schauer wrote: Besides bootstrapping, these build profiles could also be used for embedded builds, and to allow for changed buil-deps when cross-building. On a related point, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695287 I've been thinking, and talking to Wookey, about how to do this sanely. The best idea I have is for those packages for which we have -triplet versions (gcc-x.y et al, pkg-config, and so on) to have an extra control field called something like Cross-Tool-Available: yes. sbuild and dpkg-checkbuilddeps could then use the presence of this field to know that they need to translate Build-Depends: gcc-4.6 into Build-Depends: gcc-4.6:native, gcc-4.6-arm-linux-gnueabihf when cross-compiling to armhf, say. Given my recent sbuild patches, it's very easy for sbuild to do this once we have agreement on how it should detect when to do so. This is cleaner than any of the other options I've come up with: it doesn't require hardcoding a list of toolchain packages that have special cross versions; it would allow us to stop having to shove pkg-config-HOST into cross-build chroots; and it wouldn't require dpkg-checkbuilddeps to violate layers by looking in the apt cache, at least as long as the available file is up to date. Does it seem sane to people? While this field is meant to make sure not to allow any profile built binary package to be uploaded to the archive, it can also be abused to only allow some build profiles to be uploaded. For example ubuntu might generally forbid profile built binary packages to be uploaded except for packages built with the ubuntu profile only. I'm not sure we (Ubuntu) would actually want to do this, FWIW. It wouldn't buy us much since all our binaries are required to be built on our own buildds anyway. That said, the ability to have conditional build-dependencies for Ubuntu and its descendant dpkg-vendors would be valuable; but I'm wary of feature creep. 5. Cross-Builds field = For even further automation and also for quality assurance, we propose another new field for source packages which indicates whether or not this source package is supposed to be cross compilable. I don't think we should do this. Instead, we should have a cross-buildd that regularly tests whether packages are cross-buildable, and over time we should expect packages considerably beyond just the base system to be cross-buildable. I want to be able to take any package that I might find on (for the sake of argument ...) an Ubuntu phone and expect that I can cross-build it cleanly; I don't want cross-building to be this strange thing that only works for a few exceptional packages, and I think that having this field sets that expectation. The more packages that just work, the easier it will be to do anything related to cross-building. This shouldn't be unrealistic, although it's certainly ambitious. http://people.canonical.com/~cjwatson/cross/armhf/raring/ shows about 35% of Ubuntu main cross-building cleanly right now, and there are lots of cross-build and multiarch patches sitting in the Debian BTS (I've forwarded and/or uploaded everything I've done) which would improve the state of a similar core-ish set of Debian source packages to something similar. There are really only a handful of underlying causes representing many of the remaining failures - and yes, I know these are fairly hard (perl, python, gobject-introspection, ...) but they aren't intractable. If Debian wants to incorporate the ability to being bootstrappable in its policy, then there *must* be some packages which are cross compiled for a minimal build system. Adding this header to those source packages would make it a bug if they do not actually cross compile. Without this header, cross compilation would be wishlist as usual. This would be better done by way of an external list of the packages that need to cross-build cleanly. Furthermore, cross compilation is one of the methods a porter can use to break build dependency cycles. If some packages carry this new field then not only could a porter decide quicker whether or not a source package is cross compilable, an algorithm could also incorporate this information to automatically break build dependency cycles for cross compilation. While this is true, having stared at similar things myself in the past, I've come to believe that it's a better use of time to just make everything in sight cross-buildable than to spend lots of effort trying to algorithmically decide what might work or not. If more automated bootstrapping of Debian is desired, then at least build profiles (1.) should be introduced. I am strongly in favour of something occupying the general position of build profiles; there are several otherwise-intractable cross-building problems that will require something like them. I don't have much interest in the specifics so will refrain from
Re: Bootstrappable Debian - proposal of needed changes
On Wed, Jan 16, 2013 at 12:26:53AM +0100, Jakub Wilk wrote: 2) Support for the :any qualifiers in Build-Depends was added to apt in February 2010, and to dpkg in March 2012; AFAIK it's still not supported by wanna-build. I'm working on the buildd/wanna-build side of things at the moment (late last week). Now that I know where to find the branches that need to be changed it would be easy for me to add support for profiles as well once they're agreed elsewhere, and I'm motivated to do so. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130116174249.gb3...@riva.dynamic.greenend.org.uk
Re: Bootstrappable Debian - proposal of needed changes
On Wed, Jan 16, 2013 at 11:52:42AM +0800, Paul Wise wrote: That sounds useful, so yes. arm64 is on the way, it would be a nice test case but I guess wookey/Sledge are onto that. The SH-5 CPU architecture apparently exists but has no port. There are also the architectures with open-source CPU designs OpenRISC and LatticeMico32 (LM32, used in the Milkymist SoC). Also potentially x32. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130116174457.gc3...@riva.dynamic.greenend.org.uk
Re: Bootstrappable Debian - proposal of needed changes
On Wed, Jan 16, 2013 at 03:40:52PM +, Neil Williams wrote: On Wed, 16 Jan 2013 13:50:17 + Ian Jackson ijack...@chiark.greenend.org.uk wrote: Is it possible that packages might only cross build for certain targets ? Or only for certain hosts ? In my reply I'm going to use autoconf terminology, so host = architecture built for, and target = only relevant when talking about cross-tools themselves. (Not everyone likes this terminology, but it is widespread and autoconf tends to do a better job than virtually any other build system at supporting cross-building so I tend to end up preferring its terms.) For certain host architectures: yes, definitely. Any source package which includes assembly (there are more than most people expect) and any package which then has a build dependency on a binary package built from the source package(s) containing assembly and so on. Such packages would typically fail to build natively for the architecture in question too. I think it's more interesting to consider cases where, of the set of architectures on which a package can be built natively, it can cross-build to some of those host architectures but not others. However, I can't think of any such packages right now, although no doubt anything is possible; at least, it seems to me to be rare enough not to be worth inventing metadata for. I suspect that most such instances will be where packages only cross-build to similar enough architectures, e.g. where you happen to have a multilib toolchain available, so amd64 to i386, or perhaps architectures with the same bit length and/or endianness. In other words, such bugs would be a function of the combination of build and host architectures, rather than just of the host architecture. (I haven't run into many of these, since I cross-build from amd64 to armhf and they're fairly different.) Neil, can you think of any packages that meet this stricter criterion? -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130116175500.gd3...@riva.dynamic.greenend.org.uk
Re: Bootstrappable Debian - proposal of needed changes
On Wed, 16 Jan 2013 17:55:00 + Colin Watson cjwat...@debian.org wrote: On Wed, Jan 16, 2013 at 03:40:52PM +, Neil Williams wrote: On Wed, 16 Jan 2013 13:50:17 + Ian Jackson ijack...@chiark.greenend.org.uk wrote: In my reply I'm going to use autoconf terminology, so host = architecture built for, and target = only relevant when talking about cross-tools themselves. (Not everyone likes this terminology, but it is widespread and autoconf tends to do a better job than virtually any other build system at supporting cross-building so I tend to end up preferring its terms.) I remember the same convention using builD == desktop Host == handheld. Not perfect, but it may help others as it's helped me. (You can also think of Build == Big.) For certain host architectures: yes, definitely. Any source package which includes assembly (there are more than most people expect) and any package which then has a build dependency on a binary package built from the source package(s) containing assembly and so on. Such packages would typically fail to build natively for the architecture in question too. Oh absolutely. I think it's more interesting to consider cases where, of the set of architectures on which a package can be built natively, it can cross-build to some of those host architectures but not others. However, I can't think of any such packages right now, although no doubt anything is possible; at least, it seems to me to be rare enough not to be worth inventing metadata for. I suspect that most such instances will be where packages only cross-build to similar enough architectures, e.g. where you happen to have a multilib toolchain available, so amd64 to i386, or perhaps architectures with the same bit length and/or endianness. In other words, such bugs would be a function of the combination of build and host architectures, rather than just of the host architecture. (I haven't run into many of these, since I cross-build from amd64 to armhf and they're fairly different.) Neil, can you think of any packages that meet this stricter criterion? Not from memory, no. The list could have changed from when I last looked into it. A different - similarly strict - criterion would catch out glib2, gtk and others- introspection / marshalling code. This can cause a build failure but can also cause more difficult bugs which only show at runtime. Skipping the execution causes missing functionality, copying data from the build architecture is likely to cause other kinds of misbehaviour or crashes. I had this problem with Emdebian Crush - none of the icons would display because all of the cache data was to have been generated in the build but had to be omitted during the cross build. -- Neil Williams = http://www.linux.codehelp.co.uk/ pgp_pq_1lDARI.pgp Description: PGP signature
Re: Bootstrappable Debian - proposal of needed changes
On Wed, Jan 16, 2013 at 05:41:31PM +, Colin Watson wrote: If Debian wants to incorporate the ability to being bootstrappable in its policy, then there *must* be some packages which are cross compiled for a minimal build system. Adding this header to those source packages would make it a bug if they do not actually cross compile. Without this header, cross compilation would be wishlist as usual. This would be better done by way of an external list of the packages that need to cross-build cleanly. It will be possible for every developer to generate this external list by using the tools that were developed during my GSoC. Note, that a consistent list cannot be generated at this point, as some source packages have conflicts in their multiarch cross build dependencies. So (as pointed out in my initial email) the algorithms exist but package meta data must still be fixed. What we have right now is: - the *minimum* list of source packages that must be cross compiled - the *maximum* list of source packages that must be cross compiled The actual list of source packages that must be cross compiled is somewhere in between, closer to the minimum list of source packages and depends on how multiarch cross dependencies will be resolved in practice. Furthermore, cross compilation is one of the methods a porter can use to break build dependency cycles. If some packages carry this new field then not only could a porter decide quicker whether or not a source package is cross compilable, an algorithm could also incorporate this information to automatically break build dependency cycles for cross compilation. While this is true, having stared at similar things myself in the past, I've come to believe that it's a better use of time to just make everything in sight cross-buildable than to spend lots of effort trying to algorithmically decide what might work or not. The only way to algorithmically decide this, is to actually attempt to cross build the package in question. For example by using a buildd which constantly tests source packages for cross buildability as you already mentioned in your last email. From what I was told by wookey and others, cross building should only be the very last option and therefor the current version of the tools tries to select as few source packages as possible for cross compilation. Cross building is also currently regarded as only the last resort for breaking native build dependency cycles. From the perspective of the dependency analysis algorithms, deciding that cross compilation is suddenly an easy thing which can and should be done for most source packages, is just switching the dependency resolution from native to cross. So the developed algorithms would still all be valid if building things cross were suddenly preferred. The question remains of how many source packages would have to have the proposed new fields added to them to make a full bootstrap from zero possible. If the Gentoo USE flags were not too far off and assuming or tools do the correct thing so far, then: - the number of source packages that has to be modified with the new fields is at maximum 83 (there might be a smaller set). https://wiki.ubuntu.com/CrossBuilding/BuilddChroot (thanks, Matthias) suggests that we are not that far from being able to at least get to a sensible minimal chroot with a modicum of hacking. Not sure whether you meant to reply to my paragraph above yours, but you linked to a different selection of packages than I meant. The 83 source packages I mentioned were not the minimal build system but those which need to have build profile information added to break dependency cycles. The ~300 source packages out of which the 83 are selected can be found here: http://wiki.debian.org/DebianBootstrap/TODO#Break_dependency_cycles_using_staged_builds The list is of Debian Sid from (IIRC) August last year and consists of the main build dependency problem. All those ~300 source packages depend upon each other through their build dependencies. Maximum 83 of them must be modified to break this strongly connected component into a directed acyclic graph. cheers, josch -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130116195100.GA12783@hoothoot
Re: Package version numbers
Quoting Raphael Hertzog (hert...@debian.org): On Wed, 16 Jan 2013, Christian PERRIER wrote: Quoting Jakub Wilk (jw...@debian.org): I would paint the bikeshed the following color: 0.8.51+dfsg1-0.1 Isn't that missing the fact that this is a t-p-u upload, which is indeed the start of a wheezy branch? So something we were naming +wheezyfoo in the past and which we now name +deb70u1. It's not really relevant because sid has already diverged and has a higher (upstream) version. So 0.8.51+dfsg1-0.1 is acceptable IMO. Indeed. And the theoretical question of what if sid hadn't diverged wrt upstream is silly as this is a native package. Steve, problem solved, then..:). We were bikeshedding a bit too much. Merci, Raphaël. signature.asc Description: Digital signature
Re: Bootstrappable Debian - proposal of needed changes
Am 16.01.2013 17:26, schrieb Johannes Schauer:
Hi,
On Wed, Jan 16, 2013 at 04:00:15PM +0100, Matthias Klose wrote:
this only takes care about packages with a reduced package set built,
or packages with reduced functionality. There are same cases missing:
- extra build dependencies for cross builds, like for gcc-4.7:
{gobjc++,gccgo,gfortran}-target-gnu-type
profile:cross?
- build dependencies for running the check target. Usually these
dependencies can be ignored when cross-building packages, or when
building a package natively with DEB_BUILD_OPTIONS=nocheck.
profile:check? There are not few packages which can be easier
cross-built when identifying and dropping these build dependencies.
So it does make sense to build with two profiles like stage1 check.
You probably mean a nocheck profile?
Your first example indeed demonstrates why multiple profiles are useful
to be enabled at once.
The second example can be accomplished with only one profile by marking
all dependencies that are not being needed by a nocheck profile as not
being needed by the stage1 profile as well.
So instead of:
Build-Depends: foo !stage1, bar !nocheck
and then needing two profiles at the same time, one could have:
Build-Depends: foo !stage1, bar !nocheck !stage1
Though I agree that the first option looks more maintainable.
and I would assume that it better documents the intention. It maybe could be
used for a (native) test rebuild on a slow architecture, where you wouldn't do
that otherwise. For this case I don't want to have a package built with reduced
functionality.
There is also the idea of a nodocs profile which would work like
DEB_BUILD_OPTIONS=nodocs.
This seems to be less important, because these b-d's most likely end up b-d-i.
Side question: if a package offers a --disable-docs configure option, is there a
good way to enable it for arch only builds?
An argument for them becoming build profiles is, that the analysis
algorithm would then be able to just choose the less dangerous nodocs
or nocheck profile instead of a stage1 profile if they break a
dependency cycle. How safe/dangerous choosing a profile is, could be
evaluated by the number of binary packages which are not built with a
given profile but which are needed as build dependencies by other source
packages. While a stage1 profile is likely to not build binary
packages which are needed somewhere else, the nodocs and nocheck
profiles will likely not lead to needed binary packages not being
compiled.
So nocheck and nodocs profiles could allow safer reduced builds.
did somebody make an analysis for what stage1 and stage2 are currently used for?
I would like to see more descriptive profiles, so I can break down these
profiles ... For packages within a buildd chroot, I see
- nobindings -- disabling bindings for various interpreters/languages.
(could be something for DEB_BUILD_OPTIONS too, like nobindings=python,tcl)
- no ... gobject-introspection, building udev without gobject-introspection
and libgirepository1.0-dev.
Even if there are a few more, I like it better to make the profiles more
granular, and then letting the people doing a bootstrap decide what to include
in a stage1 or stage2 build.
Matthias
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50f708e9.4090...@ubuntu.com
Re: Pure-mulitarch Cross Toolchains
Am 16.01.2013 17:30, schrieb Wookey: +++ Matthias Klose [2013-01-16 15:37 +0100]: Am 15.01.2013 19:18, schrieb Johannes Schauer: This mechanism also covers cross-compiler bootstraping. The eglibc, gcc, and kernel packages already have the neceassary staged-build info, but the build profiles (1.) part is also needed to specifiy the reduced build-deps. The cross-toolchain bootstrap ceases to be a special case if treated this way and just becomes packages to be built in stages using the profiles mechansim, like many others in the base system (but for build arch taregtting host, arch, rather than built for host-arch). See the wiki article at [11]. [11] http://wiki.debian.org/MultiarchCrossToolchains Please stop calling this MultiarchCrossToolchains. It was already wrong when used in the Emdebian context, and on some GSOC pages. What you are apparently aiming for is a cross compiler re-using the target libraries built (natively). The target libraries can be built natively or cross-built. Clearly cross-building is necessary when the target architecture does not yet exist (e.g. arm64). The point is that the library dependencies use the multiarch file locations and mechanisms, rather than extra copies in different locations. I agree this is separate from multiarch path support in the cross-toolchain for finding libraries and headers for non-toolchain libs. What term would you like me to use for this cross-toolchain arangement? multiarch-libraryCrossToolchains? PureMultiarchCrossToolchains? FullyMultiarchedCrossToolchains? Yes it's a bit confusing, because multiarch affects various aspects of the toolchain. I'm happy to use a different name to avoid confusion, this just seems to me to be the logical conclusion of 'mulitarching the cross toolchains' (see discussion below), so it seemed a reasonable name. just leave any *Multiarch* out of the name. However this is not yet done, It was done in Thibg's GSOC project for 4.7.2-4. Yes it needs more work to properly integrate, test, and make bootstrappable, but we have a working implementation (modulo keeping up with your amazing rate of new uploads :-). (For which kudos, even if it does make it hard to keep up!) requires dependencies on foreign architectures It does. and only is a very special case, This is where we seem to disagree. I think it should be the standard case (for binary distro cross-toolchains). not helping for targets where these are not yet available (like for the arm64 bootstrap). Having a cross-toolchain just built on the host architecture (targeting the target architecture), should still be an option. This is still an option - you just cross-build the target libraries as part of the bootstrap. The wiki page gives the runes. I am not convinced of the benefit in also maintaining toolchains with these libraries installed twice in different locations, now that we have multiarch to make this unnecessary. But I would like to see much wider discussion of this issue so we can reach conclusions as a project on what the default cross-toochain setup should be, and what non-default methods are also worth maintaining in the packaging. The main disadvantage of making use of the multiarch libraries is the need to keep libgcc, libstdc++ etc in version lockstep across architectures. But this applies to multiarch in general for all libraries, and is something we manage in Debian as part of being a distro. It is something to carefully consider. Is the reduced independence of the cross-toolchain library versions a fatal flaw? The main advantage is that the code you build against is actually the code the toolchain was built against, not some other code that happens to be installed in the expected location. Also build-dependencies work automatically without having to have 'equivs' packages for libgcc1, libstc++6-dev etc until the real native ones are built. And having one copy of libgcc1:targetarch, libstdc++:targetarch on the system instead of two seems like good practice to me. Another advantage is that for normal cross-toolchain builds you don't need to do a 3-stage bootstrap build, because you already have the target-arch libc, libgcc1, libstc++ etc available so you just need to rebuild gcc without staging. Much quicker and simpler. This is (fundamentally) how the emdebian toolchain builds worked for many years. emdebian is not debian. emdebian has a rather limited subset what to target and what to build. This may fit emdebian, but not a cross-toolchain for debian. Using multiarch libraries also greatly simplifies the gcc packaging (if we are able to drop multilib equivalents as a result). Again we disagree on this point. no, your perception is wrong. there is no way that multilib'ed GCC builds will go away. Yes, emdebian does ignore the topic, Debian should not. I think we should be encouaging people to install arm-linux-gnueabi and
Re: Bootstrappable Debian - proposal of needed changes
On Wed, Jan 16, 2013 at 06:47:01PM +, Neil Williams wrote: A different - similarly strict - criterion would catch out glib2, gtk and others- introspection / marshalling code. This can cause a build failure but can also cause more difficult bugs which only show at runtime. Skipping the execution causes missing functionality, copying data from the build architecture is likely to cause other kinds of misbehaviour or crashes. Yeah, that and gtk-doc. I do have some ideas on how to deal with gobject-introspection; but I think it's going to require a gobject-introspection-TRIPLET for each host architecture, which is one reason I want to have a reasonably generalisable solution to the build-dep substitution problem. There's probably no general magic bullet to the problem where cross-built packages build successfully but turn out to be inadequate in some way, although I guess that file list comparison against natively-built packages would catch a majority of the problems. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130116215218.ga24...@riva.dynamic.greenend.org.uk
Wheezy testing versus Wheezy release repositories: confused on how to get source code
I installed Wheezy beta 4 from CD and was surprised that compiz window manager was removed. Compiz is the best thing about Linux, that's a shame. I tracked down some explanations, don't want to start a flame war about that decision. But, even though Debian is not including compiz, I still love it and am going to build compiz and use it. My plan is to get the compiz source packages from the most recent Wheezy which did include compiz. But I'm having trouble finding that and understanding the way the repositories fit together. The Wheezy repo that was testing during the Squeeze time is a different thing from the Wheezy that is Wheezy release beta 4? Right? In Wheezy beta 4, why can't I see the same compiz files that I could see when I ran Squeeze with the wheezy repo enabled in apt? pj -- Paul E. Johnson Professor, Political Science Assoc. Director 1541 Lilac Lane, Room 504 Center for Research Methods University of Kansas University of Kansas http://pj.freefaculty.org http://quant.ku.edu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAErODj-nqNi_j2+3SaJLCxggm=-aa9uhtcwcfp_wtrbbec1...@mail.gmail.com
Re: Wheezy testing versus Wheezy release repositories: confused on how to get source code
Hi! Why don't you just use the Sid version? = http://packages.debian.org/sid/compiz 2013/1/16 Paul Johnson pauljoh...@gmail.com: [...] The Wheezy repo that was testing during the Squeeze time is a different thing from the Wheezy that is Wheezy release beta 4? Right? No. Testing *is* Wheezy at time ;-) In Wheezy beta 4, why can't I see the same compiz files that I could see when I ran Squeeze with the wheezy repo enabled in apt? Because the Compiz packages have now been removed from Testing7Wheezy, I guess. But you should be fine with the Sid version. Cheers, Matthias -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKNHny-7U=kww1+emb2f6v5qxtmy2xi972otbmjn3gnyazi...@mail.gmail.com
how to handle architecture dependent headers in subdirectories
There are some issues when you do have an architecture dependent header file which needs to be in the multiarch specific include directory. If the header file is directly located in /usr/include, then moving it to /usr/include/multiarch-tuple usually is not a problem (except for quoting issues as found in the packaging for libreoffice). The compilers (checked here GCC and clang) do include the multiarch include path as a path for system includes too. However there are some issues when you do need to split the header files into different locations. Seen that with python2.7 and python3.3 in experimental, however I think it is a concern for packages like openssl as well. Looking at python in experimental (having the architecture independent headers in /usr/include and the architecture dependent headers in /usr/include/multiarch-tuple) you have some build failures. For the python case: - moving all the headers to the multiarch include path doesn't work, because configure tests fail which assume the include directory a direct subdirectory of prefix. - splitting the header installation into /usr/include and /usr/include/multiarch-tuple doesn't work because packages do use sysconfig.get_python_inc() which only returns the former directory. (This is the current behaviour of the python packages in experimental). - Everything is fine when a package uses pkg-config or python-config, because these give the correct include paths. However not every packaged upstream does use these. So I'm proposing to use a header which can be installed into /usr/include and does include the header file included in a subdirectory installed into /usr/include/multiarch-tuple and works around the issue. Intending to do that for python2.7. For python3.x I do intend to get the sysconfig.get_python_inc() deprecated. Attaching the proposed header file, intending to include it into the gcc package as /usr/lib/gcc/multiarch.h.in Matthias #if defined(__linux__) # if defined(__x86_64__) defined(__LP64__) # include x86_64-linux-gnu/@subdir@/@header@ # elif defined(__x86_64__) defined(__ILP32__) # include x86_64-linux-gnux32/@subdir@/@header@ # elif defined(__i386__) # include i386-linux-gnu/@subdir@/@header@ # elif defined(__alpha__) # include alpha-linux-gnu/@subdir@/@header@ # elif defined(__ARM_EABI__) defined(__ARM_PCS_VFP) # include arm-linux-gnueabihf/@subdir@/@header@ # elif defined(__ARM_EABI__) !defined(__ARM_PCS_VFP) # include arm-linux-gnueabi/@subdir@/@header@ # elif defined(__hppa__) # include hppa-linux-gnu/@subdir@/@header@ # elif defined(__ia64__) # include ia64-linux-gnu/@subdir@/@header@ # elif defined(__m68k__) !defined(__mcoldfire__) # include m68k-linux-gnu/@subdir@/@header@ # elif defined(__mips_hard_float) defined(_MIPSEL) # if defined(_ABIO32) # include mipsel-linux-gnu/@subdir@/@header@ # elif defined(_ABIN32) # include mips64el-linux-gnuabin32/@subdir@/@header@ # elif defined(_ABI64) # include mips64el-linux-gnuabi64/@subdir@/@header@ # else # error unknown multiarch location for @header@ # endif # elif defined(__mips_hard_float) # if defined(_ABIO32) # include mips-linux-gnu/@subdir@/@header@ # elif defined(_ABIN32) # include mips64-linux-gnuabin32/@subdir@/@header@ # elif defined(_ABI64) # include mips64-linux-gnuabi64/@subdir@/@header@ # else # error unknown multiarch location for @header@ # endif # elif defined(__powerpc__) defined(__SPE__) # include powerpc-linux-gnuspe/@subdir@/@header@ # elif defined(__powerpc__) # include powerpc-linux-gnu/@subdir@/@header@ # elif defined(__powerpc64__) # include powerpc64-linux-gnu/@subdir@/@header@ # elif defined(__s390x__) # include s390x-linux-gnu/@subdir@/@header@ # elif defined(__s390__) # include s390-linux-gnu/@subdir@/@header@ # elif defined(__sh__) defined(__LITTLE_ENDIAN__) # include sh4-linux-gnu/@subdir@/@header@ # elif defined(__sparc__) # include sparc-linux-gnu/@subdir@/@header@ # elif defined(__sparc64__) # include sparc64-linux-gnu/@subdir@/@header@ # else # error unknown multiarch location for @header@ # endif #elif defined(__FreeBSD_kernel__) # if defined(__LP64__) # include x86_64-kfreebsd-gnu/@subdir@/@header@ # elif defined(__i386__) # include i386-kfreebsd-gnu/@subdir@/@header@ # else # error unknown multiarch location for @header@ # endif #elif defined(__gnu_hurd__) # include i386-gnu/@subdir@/@header@ #else # error unknown multiarch location for @header@ #endif
Re: Bug#698256: ITP: lz4 -- Extremely Fast Compression algorithm library
Hi,
On Wed, Jan 16, 2013 at 7:02 PM, Jakub Wilk jw...@debian.org wrote:
* Nobuhiro Iwamatsu iwama...@debian.org, 2013-01-16, 09:51:
* URL : http://code.google.com/p/lz4/
* License : BSD 2-Clause License
Programming Lang: C
Description : Extremely Fast Compression algorithm library
LZ4 is a very fast lossless compression algorithm.
This uses Dictionary compression, and only supports compression and
decompression unit blocks.
This looks very promising, but also immature. The upstream makefile doesn't
build a shared library, not even a static library, but only an executable
(lz4demo). Are there any plans to change that?
Yes, I am correcting the part which you pointed out.
And I will send the patch to upstream.
A static library, shared library and sample program are provided when
this is installed in Debian.
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CABMQnV+C9GAxK1SvOmPMztDT4XriWM6P5o=fzuqzcjq0f8b...@mail.gmail.com
Re: Package version numbers
On Wed, 16 Jan 2013 19:16:26 +0100, Christian PERRIER bubu...@debian.org wrote: Quoting Raphael Hertzog (hert...@debian.org): On Wed, 16 Jan 2013, Christian PERRIER wrote: Quoting Jakub Wilk (jw...@debian.org): I would paint the bikeshed the following color: 0.8.51+dfsg1-0.1 Isn't that missing the fact that this is a t-p-u upload, which is indeed the start of a wheezy branch? So something we were naming +wheezyfoo in the past and which we now name +deb70u1. It's not really relevant because sid has already diverged and has a higher (upstream) version. So 0.8.51+dfsg1-0.1 is acceptable IMO. Indeed. And the theoretical question of what if sid hadn't diverged wrt upstream is silly as this is a native package. Steve, problem solved, then..:). We were bikeshedding a bit too much. Yup, thanks! A case of “Pourquoi faire simple quand on peut faire compliqué ?” ;-) (“Why make things simple when they can be complicated?”) An updated package is coming up shortly... Regards, Stephen signature.asc Description: PGP signature
Re: problematic shlibs entry in substvars file
Le Wed, Jan 16, 2013 at 10:44:53AM +0800, Paul Wise a écrit : The version difference is probably due to symbols stuff, read deb-symbols(5), dpkg-shlibdeps(1), dpkg-gensymbols(1) and this wiki page: http://wiki.debian.org/Projects/ImprovedDpkgShlibdeps Hi all, note that since version 3.9.4, this is also well covered in the Policy's chapter 8. http://www.debian.org/doc/debian-policy/ch-sharedlibs.html 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: http://lists.debian.org/20130116225942.ga29...@falafel.plessy.net
Re: how to handle architecture dependent headers in subdirectories
On Wed, Jan 16, 2013 at 11:32:45PM +0100, Matthias Klose wrote: There are some issues when you do have an architecture dependent header file which needs to be in the multiarch specific include directory. If the header file is directly located in /usr/include, then moving it to /usr/include/multiarch-tuple usually is not a problem (except for quoting issues as found in the packaging for libreoffice). The compilers (checked here GCC and clang) do include the multiarch include path as a path for system includes too. However there are some issues when you do need to split the header files into different locations. So I'm proposing to use a header which can be installed into /usr/include and does include the header file included in a subdirectory installed into /usr/include/multiarch-tuple and works around the issue. Attaching the proposed header file, intending to include it into the gcc package as /usr/lib/gcc/multiarch.h.in #if defined(__linux__) # if defined(__x86_64__) defined(__LP64__) # include x86_64-linux-gnu/@subdir@/@header@ # elif defined(__x86_64__) defined(__ILP32__) # include x86_64-linux-gnux32/@subdir@/@header@ # elif defined(__i386__) # include i386-linux-gnu/@subdir@/@header@ This looks just like the solution ultimately chosen for #682183, except for the include being monstrous. Let's instead add a file to libc6-dev with the following: #define DEB_HOST_MULTIARCH x86_64-linux-gnu (for different values of x86_64-linux-gnu). It might be either a new file on its own, or an addition to one of existing headers. This is currently /usr/include/x86_64-linux-gnu/lua5.1-deb-multiarch.h except that it'd be a pain to do this for every single package. Having a #define that says amd64 could be good, too. Doing it this way would remove a yet another place that has to be changed when adding a new arch. Also, having it as a string allows other uses than a static #include. -- How to squander your resources: those silly Swedes have a sauce named hovmästarsås, the best thing ever to put on cheese, yet they waste it solely on mere salmon. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130116232343.ga16...@angband.pl
Re: how to handle architecture dependent headers in subdirectories
Matthias Klose d...@debian.org writes: There are some issues when you do have an architecture dependent header file which needs to be in the multiarch specific include directory. If the header file is directly located in /usr/include, then moving it to /usr/include/multiarch-tuple usually is not a problem (except for quoting issues as found in the packaging for libreoffice). The compilers (checked here GCC and clang) do include the multiarch include path as a path for system includes too. However there are some issues when you do need to split the header files into different locations. Seen that with python2.7 and python3.3 in experimental, however I think it is a concern for packages like openssl as well. Looking at python in experimental (having the architecture independent headers in /usr/include and the architecture dependent headers in /usr/include/multiarch-tuple) you have some build failures. For the python case: - moving all the headers to the multiarch include path doesn't work, because configure tests fail which assume the include directory a direct subdirectory of prefix. Why not just fix this bug instead? That's what I did for OpenAFS. I think it's more robust than trying to split the header files apart. This is probably a sign of badly-written configure probes anyway, since it implies that configure is not using the compiler to test headers and is instead poking about on the file system. -- 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: http://lists.debian.org/87bocog11m@windlord.stanford.edu
Re: problematic shlibs entry in substvars file
On Thu, Jan 17, 2013 at 6:59 AM, Charles Plessy wrote: Le Wed, Jan 16, 2013 at 10:44:53AM +0800, Paul Wise a écrit : The version difference is probably due to symbols stuff, read deb-symbols(5), dpkg-shlibdeps(1), dpkg-gensymbols(1) and this wiki page: http://wiki.debian.org/Projects/ImprovedDpkgShlibdeps Hi all, note that since version 3.9.4, this is also well covered in the Policy's chapter 8. http://www.debian.org/doc/debian-policy/ch-sharedlibs.html I guess that #s-sharedlibs-symbols on that page should be referenced by deb-symbols(5), dpkg-shlibdeps(1) and dpkg-gensymbols(1), could you file a bug/patch about that on dpkg-dev? -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caktje6f45lhcerscjmpybbzeox1oe2ai0rfhva1kwgb5xjh...@mail.gmail.com
Re: how to handle architecture dependent headers in subdirectories
Would it be possible to use something similar to the bits/ dir in eglibc? Or would your proposal replace that? /usr/include/python2.7/bits - /usr/include/x86_64-linux-gnu/python2.7/bits And in /usr/include/python2.7/* #include python2.7/bits/foo.h -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6F7eY2Wjo9W9ao=f8xjpu7oorh2e3uifwy6syvjazs...@mail.gmail.com
Re: Bootstrappable Debian - proposal of needed changes
Le Wed, Jan 16, 2013 at 05:26:52PM +0100, Johannes Schauer a écrit : Whether or not nocheck and nodocs can/should become build profiles is of course still to be debated. Hi all, for the packages I maintain, I am now replacing the regression tests that were ran during the build process by autopkgtest test suites. http://dep.debian.net/deps/dep8/ (see http://developer.ubuntu.com/packaging/html/auto-pkg-test.html while Alioth-hosted sites seem to be in trouble) If this eventually becomes the norm, then we will not need nocheck build option or profile anymore. 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: http://lists.debian.org/20130117013503.gc29...@falafel.plessy.net
Re: Bootstrappable Debian - proposal of needed changes
+++ Matthias Klose [2013-01-16 21:09 +0100]: Am 16.01.2013 17:26, schrieb Johannes Schauer: On Wed, Jan 16, 2013 at 04:00:15PM +0100, Matthias Klose wrote: So it does make sense to build with two profiles like stage1 check. Yes. I can think of situations where being able to specify more than one profile at a time would be useful/flexible. stage1 cross for example. I'd like to enable this if it doesn't make things too complicated. Your first example indeed demonstrates why multiple profiles are useful to be enabled at once. The second example can be accomplished with only one profile by marking all dependencies that are not being needed by a nocheck profile as not being needed by the stage1 profile as well. So instead of: Build-Depends: foo !stage1, bar !nocheck and then needing two profiles at the same time, one could have: Build-Depends: foo !stage1, bar !nocheck !stage1 Though I agree that the first option looks more maintainable. and I would assume that it better documents the intention. It maybe could be used for a (native) test rebuild on a slow architecture, where you wouldn't do that otherwise. For this case I don't want to have a package built with reduced functionality. Makes sense. There is also the idea of a nodocs profile which would work like DEB_BUILD_OPTIONS=nodocs. This seems to be less important, because these b-d's most likely end up b-d-i. There is potentially some overlap between DEB_BUILD_OPTIONS and DEB_BUILD_PROFILES. Indeed implementing them as DEB_BUILD_OPTIONS=profile=foo was in the spec at one point but we moved away from that. My feeling for the best way to think about this is that DEB_BUILD_OPTIONS are for things that don't change the dependencies (optimisation options, parallelisation options, most checks). DEB_BUILD_PROFILES are for things that do have dependency implications (bootstrap builds, embedded builds, check-only build-deps, binaries not produced). Side question: if a package offers a --disable-docs configure option, is there a good way to enable it for arch only builds? Shouldn't this be done in the rules file for binary-arch/binary-indep targets? did somebody make an analysis for what stage1 and stage2 are currently used for? Not a formal analysis, and having a done a few I suspect you have as good an idea as anyone. I've found: Removing language bindings, removing optinal library deps (selinux for eglibc for example, ldap for gnupg or krb5), building without gui components when some fairly low-level package also has a gui-tool that brings in a pile more build-deps. I would like to see more descriptive profiles, so I can break down these profiles ... For packages within a buildd chroot, I see - nobindings -- disabling bindings for various interpreters/languages. (could be something for DEB_BUILD_OPTIONS too, like nobindings=python,tcl) - no ... gobject-introspection, building udev without gobject-introspection and libgirepository1.0-dev. Even if there are a few more, I like it better to make the profiles more granular, and then letting the people doing a bootstrap decide what to include in a stage1 or stage2 build. I can see some logic to this, and ultimately profiles _could_ be used for anything like this. Packagers are best-placed to know which aspects of their software are logically optional. But this could get out of hand with a very long list in the build-deps line, so we should resist going too crazy. libdose can cope with an arbitrary set of profiles, and work out which ones provide linearisable builds, so maybe there is no actual need for regularised names (stage1, stage2), so long as available profiles are discoverable (as ijw mentioned - I agree that would be wise). I'm not sure how this might work with generating version numbers so profiled builds supercede each other correctly in automated uploads to a bootstrap repo. It's easy with 'stage1, stage2'. Tools would have to get smarter with arbitrary names. But we can probably make it work with a bit of thought. And it will work 'manually' without this (but it's very annoying fighting reprepro all the time). One thing that should come out of this work is recomendations for packagers on what profiles are available/recommended/supported by tools. We can use the mechansim as much/little as seems sensible. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130117031831.gs5...@stoneboat.aleph1.co.uk
Re: Bootstrappable Debian - proposal of needed changes
+++ Ian Jackson [2013-01-16 13:50 +]: Johannes Schauer writes (Bootstrappable Debian - proposal of needed changes): 6. Conclusion = ... - do the proposals for the needed fields sound convincing? Can they be improved? Do they have fundamental flaws? I haven't spotted anything hideously wrong. I have three suggestions for changes: * Packages should explicitly declare which profiles they support. This should be done with a Profile field in the source stanza of debian/control. I agree this is a really good idea. They could be inferred from parsing the build-deps line, but profiles that don't actually change the build-deps could exist and they would be undiscoverable without a field like this. I did think about putting this in the spec mail, but decided it was long enough to be going on with. * It should be made explicit in the spec that building occurs with zero or one profile, not several. This is something to ponder. We could decree that and it would simplify some things. But I think there are good reasons to consider what we gain from relatively granular profiles which brings along with it the likelihood of needing to specify more than one. * The concrete syntax in build-depends should not use but rather reuse the architecture qualification syntax. This takes the metacharacters and reserves them for build profiles. Metacharacters are very scarce and should only be used when necessary. This is a good point. I really don't care what the syntax is so long as as it represents the semantics we need. The current syntax was suggested by the dpkg people, and it has been shown to be sufficient. If we can make it work sensibly without using a new metacharacter then that's fine by me. [snip very useful attempt to try and define a spec]. We do need something explicit like this writing down, so thanks for doing that. In fact I'll copy it over the wiki page. The details of this need a decision on whether more than one can be specified at a time or not, before we can finalise them. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130117034544.gu5...@stoneboat.aleph1.co.uk
Bug#698329: ITP: sos -- This set of tools is designed to provide information to support organizations
Package: wnpp Severity: wishlist Owner: Adam Stokes adam-sto...@ubuntu.com * Package name: sos Version : 2.3.1 Upstream Author : Adam Stokes adam-sto...@ubuntu.com * URL : https://github.com/sosreport/sosreport * License : GPL2+ Programming Lang: Python Description : This set of tools is designed to provide information to support organizations This set of tools is designed to provide information to support organizations in an extensible manner, allowing third parties, package maintainers, and anyone else to provide plugins that will collect and report information that is useful for supporting software packages. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130117042707.25687.77206.reportbug@localhost
Re: Bootstrappable Debian - proposal of needed changes
Hi Johannes, On Tue, Jan 15, 2013 at 07:18:40PM +0100, Johannes Schauer wrote: [...] 2. Build-Profiles (extension 1) === When a source package is built with fewer build dependencies (cross, embedded, stage1, nodocs...), then it often happens that it does not build one or more of its binary packages at all (e.g. foo-gtk, foo-java, foo-doc). While this is a minor nuisance during a half automated bootstrap, a fully automated bootstrapping process needs to know which binary packages a source package does not build if it is compiled in one of its profiles. We therefore propose a new field for binary packages in their control file which indicates for which profiles it builds. Builds-With-Profile: !stage1 !embedded Different profile names are separated by spaces similar to the Architecture field. A binary package with the above field would not be built during the profile builds stage1 or embedded. Binary packages which do not have this field would default to being built by every profile. This field would mean a minor change to dpkg-gencontrol. 3. Build-profiles (extension 2) === A build profile is set either using a DEB_ environment variable or a command-line option. DEB_STAGE has been used historically in a few packages with staged build support, but that is specific to the staged-builds purpose. For the more generic build-profiles DEB_BUILD_PROFILE=label is proposed instead - (only 7 existing packages would need to be changed - patches exist for some already). Setting the build-profile causes dpkg-checkbuilddeps to use the modified deps, dpkg-gencontrol to mark the built package with a new field: Built-With-Profile: stage1 cross This new field is optional and just meant to mark binary packages such that they can not accidentally make it to the archive. Another idea is to encode this information in the package version by adding a ~stage1. Using the field is more powerful as source packages can also be built with multiple profiles activated at once and the field can store a list of profile names. In above example, the binary package was built with the cross profile activated for cross compilation and the stage1 profile activated to break a build dependency cycle. While this field is meant to make sure not to allow any profile built binary package to be uploaded to the archive, it can also be abused to only allow some build profiles to be uploaded. If wanna-build is updated to support these two fields, then I imagine it can run the bootstrapping dependency algorithm. While you wouldn't want to upload a package to the debian.org archive when the architecture is as yet incomplete, the same isn't true for the debian-ports.org archive. It would require some patches for wanna-build to understand that package foo would need to be rebuilt once a particular profile is fully built and available, but I don't think that's impossible. However, to do that, there's one thing I'm missing in your mail: there will be cases where packages, when built in a particular profile do not support some functionality. That is, the package is available and does most of what the full package does, but because some build-dependency is missing, it doesn't support some feature or other -- for example, let's say that a document translation package (which we'll call foo) which supports many input formats does not support XML as an input format when built in the stage1 profile. The output of its stage1 build would not change the number of binary packages built with the source package, it would just build a binary package with reduced functionality. Now it might be that a package build-depends on our package foo because it needs to translate documents in that XML format into something else, With your proposal, there's no way for the build-depending package to declare that it needs a version of foo that was built at a richer profile than stage1. Is this something you've considered? -- Copyshops should do vouchers. So that next time some bureaucracy requires you to mail a form in triplicate, you can mail it just once, add a voucher, and save on postage. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130117073357.ga1...@grep.be
Accepted octave-statistics 1.2.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Jan 2013 10:19:41 +0100 Source: octave-statistics Binary: octave-statistics Architecture: source all Version: 1.2.0-1 Distribution: experimental Urgency: low Maintainer: Debian Octave Group pkg-octave-de...@lists.alioth.debian.org Changed-By: Sébastien Villemot sebast...@debian.org Description: octave-statistics - additional statistical functions for Octave Changes: octave-statistics (1.2.0-1) experimental; urgency=low . [ Rafael Laboissiere ] * Imported Upstream version 1.2.0 * Bump Standards-Version to 3.9.4 (no changes needed) * Use Sébastien Villemot's @debian.org email address * Remove obsolete DM-Upload-Allowed flag * debian/copyright: + Reflect upstream changes + Use the octave-maintainers mailing list as upstream contact . [ Sébastien Villemot ] * debian/patches/autoload-yes.patch: new patch Checksums-Sha1: 5d15851be30814ed9833481aa2c35334afc9dba5 2099 octave-statistics_1.2.0-1.dsc 86610b99c60f3f6dba710ad2315540dcf5961662 88899 octave-statistics_1.2.0.orig.tar.gz e0dcf3e915f4f819d2fdc5525d78c76c1bc0dbb8 4464 octave-statistics_1.2.0-1.debian.tar.gz b2366a3005d93bd25f13ef6011796d5fc80e7bc9 120296 octave-statistics_1.2.0-1_all.deb Checksums-Sha256: 848a08d3d62137568bbe9da2c90dd928c08b55060d7e904ed8d5a4b241071531 2099 octave-statistics_1.2.0-1.dsc ae83008508d282d6fcdf4626941983eca69fa3ba045fd9d73c5ce987d52b9523 88899 octave-statistics_1.2.0.orig.tar.gz f9c482ae653d18a903714ade46d53bbf82b15713434d85a5881234474fee4739 4464 octave-statistics_1.2.0-1.debian.tar.gz 846bf97934ea342b2483ecb51528e6a94cc92b52f9bb42a6bb312cc6169ab32f 120296 octave-statistics_1.2.0-1_all.deb Files: 0680165bb2cd8b4e9c2603ea3bfe675a 2099 math optional octave-statistics_1.2.0-1.dsc e9698d52254d5bc5e86319f80afaae29 88899 math optional octave-statistics_1.2.0.orig.tar.gz eecbdcd7b25f74d849654d63b040512c 4464 math optional octave-statistics_1.2.0-1.debian.tar.gz f857e8e602c075be18722d950326239c 120296 math optional octave-statistics_1.2.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ9nFSAAoJECzs6TUOzr5KkgoP/RlOILMSXsh5yESljAwxpqTK 6OmEIqSrwhKlJmI5sM0xpHQAv48ESFqFMGQx7F3hhBQnTdtM1sLY1Q6fuOhSki9D 8Xbbm12My/s20h07DGGysy1ETPPub3+XJbBarm3NOUcRIQeEi1ooDdJiHt+Q2N7V i7MlCO5Giu14wHomezF/ldglq/y+oiunFlMlRCiyt9cuj0pk/cTCZ7nU+Mim1wMk s1EVZI0mxBhD8KcwhUqpk5WIXKtsYsJ5vHjTZJLLIhIdBUgGguGxRSlextUq+fol U4PLyS/sznwjJQZXpw9l1k5xHHagylbTBFEJ/UJy7p4IsJzRgI8xpFj3PNo1vA6f s55vbOIwZds3ShIEcgHNSplm9A4v9ZJzRt15VaMR3lZGj2uf8tvHrreRBsOV2Y72 dVqTIcJEJbV//zr9Vz0c3Cpe6mU2uBZNA5z/nXda2u9A4aaCfKPDYJ1YYjzjo/sH A76oKTRaSswhKmWpfxDGbiCIE6iIQlAcrSiBVGq0WTrL3lRZILvr++GF8nXwHKhF zybumyjNBCJjUNjHkDP5BOx8rdmj8FdbcUVRNYfp+3ZY9FpI67laWaHm+zDxNZbL bb21kcY57KMCZsSY/Kj6koAOzWdvad90NhMvqaGS0xPezw0W66glNYZmH6xUK95O siZp8ZlziAtTk/hn6gDS =34NW -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: http://lists.debian.org/e1tvpmm-0004uq...@franck.debian.org
Accepted at-spi2-core 2.7.4.1-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 16 Jan 2013 11:13:40 +0100 Source: at-spi2-core Binary: at-spi2-core at-spi2-core-dbg libatspi2.0-0 libatspi2.0-dev libatspi2.0-0-dbg gir1.2-atspi-2.0 at-spi2-doc Architecture: source amd64 all Version: 2.7.4.1-1 Distribution: experimental Urgency: low Maintainer: Debian Accessibility Team debian-accessibil...@lists.debian.org Changed-By: Samuel Thibault sthiba...@debian.org Description: at-spi2-core - Assistive Technology Service Provider Interface (dbus core) at-spi2-core-dbg - Assistive Technology Service Provider Interface - debugging symbo at-spi2-doc - Assistive Technology Service Provider Interface (Documentation) gir1.2-atspi-2.0 - Assistive Technology Service Provider (GObject introspection) libatspi2.0-0 - Assistive Technology Service Provider Interface - shared library libatspi2.0-0-dbg - Assistive Technology Service Provider Interface - debugging symbo libatspi2.0-dev - Development files for the assistive technology serice provider Changes: at-spi2-core (2.7.4.1-1) experimental; urgency=low . [ Luke Yelavich ] * New upstream release Checksums-Sha1: 242a5bcc30ea62a6bf9c7908f41e80232028870a 2488 at-spi2-core_2.7.4.1-1.dsc 03894928fba141ff490f16aaaf18c299d7b1a4a0 435928 at-spi2-core_2.7.4.1.orig.tar.xz 99b4f2308347e9b741040f054bb33c6505ecfdab 4766 at-spi2-core_2.7.4.1-1.debian.tar.gz 1223af8ce06825770d83cf116fadd9e40d371211 54082 at-spi2-core_2.7.4.1-1_amd64.deb c6f511bdad38fe1a2461f1988e6a4524adf90934 63192 at-spi2-core-dbg_2.7.4.1-1_amd64.deb 0ac322f4ab559cfb46a2a94fb5b09897e3c7c3b8 62114 libatspi2.0-0_2.7.4.1-1_amd64.deb b31e2783bcb5b61223a88a246d93086826ac3c62 61892 libatspi2.0-dev_2.7.4.1-1_amd64.deb 6fc5475223933029cbc455bc220f91694636b362 93504 libatspi2.0-0-dbg_2.7.4.1-1_amd64.deb 4ae5107a5403874510de7d7bf04b59fa3bb573a7 18310 gir1.2-atspi-2.0_2.7.4.1-1_amd64.deb de7ddb44a1c0eff206d16679381dd8d5e90f9b9e 100942 at-spi2-doc_2.7.4.1-1_all.deb Checksums-Sha256: b733bfe9f4f834db0b3708cad7abd5b1a35c83449572e6d3a320aa9afac3 2488 at-spi2-core_2.7.4.1-1.dsc 7fe15e8d6acfd28c942e69f7be9b71f7541c3416fd6fba810518d408c1154a90 435928 at-spi2-core_2.7.4.1.orig.tar.xz 10e0fa6254750de4710da352f82fef818c0765ca8fc7535f3b7d6be41aeff9a8 4766 at-spi2-core_2.7.4.1-1.debian.tar.gz 7e7637d32043bdee8d64550cc7b62664b6286202b06fc99fe7cb929c5e89110e 54082 at-spi2-core_2.7.4.1-1_amd64.deb 85906b4a15b051d3c149c065107c28ada5b6a1fdb576bde3f039b116aafd5ffa 63192 at-spi2-core-dbg_2.7.4.1-1_amd64.deb b1f66fefa0620f1d21d90b89faf52e64dd4c5a09731baa5ac5abe26ea5197a21 62114 libatspi2.0-0_2.7.4.1-1_amd64.deb e3c3b0afbd76bed12ef2c85e53b244f97b79a260a96e1301e8db6a98aa6b5565 61892 libatspi2.0-dev_2.7.4.1-1_amd64.deb 777070f79a61b1317c623ad946ddc0a2f1cf63875ea403dbe8e575fa29eb983a 93504 libatspi2.0-0-dbg_2.7.4.1-1_amd64.deb 29e2816d12b6a8aa7614c30eee85e97312ea8bed8dbdd90907e5748eca51b9dc 18310 gir1.2-atspi-2.0_2.7.4.1-1_amd64.deb 72580e554ebbaf74c915358cb734cb428dc098e19137b72745eda780c8a6bde1 100942 at-spi2-doc_2.7.4.1-1_all.deb Files: 8142aab23e286897298c0ed0fccdf775 2488 misc optional at-spi2-core_2.7.4.1-1.dsc e069f8ad5f4b56cb3a3098f0eafd6457 435928 misc optional at-spi2-core_2.7.4.1.orig.tar.xz 04c1adde9fae616092f8878d7153e417 4766 misc optional at-spi2-core_2.7.4.1-1.debian.tar.gz ab09000edeab5737d95a8d838261729b 54082 misc optional at-spi2-core_2.7.4.1-1_amd64.deb ba6b561aec309f7be8f955abc20c8a71 63192 debug extra at-spi2-core-dbg_2.7.4.1-1_amd64.deb 2c6970457d9662f2e28df53d3ed935f5 62114 libs optional libatspi2.0-0_2.7.4.1-1_amd64.deb 6696932373d432a6a57e7e3b0bbf96cd 61892 libdevel optional libatspi2.0-dev_2.7.4.1-1_amd64.deb 1677e194bc568ec8db4067784159a713 93504 debug extra libatspi2.0-0-dbg_2.7.4.1-1_amd64.deb 1bef4c46069cca49d85b2a8233aea8c7 18310 introspection optional gir1.2-atspi-2.0_2.7.4.1-1_amd64.deb 4e886baa964c3ba77cf5e46a0a406c33 100942 doc optional at-spi2-doc_2.7.4.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQ9n6rAAoJECqpogBB8bdX7HgP/3gF2qxrHmoXBrZbka4yfzaC AlvhIkMAjG58/4TwXK2XVYcYuXVxRuW5tLZRDBt97+jeKzBhmC32TrVULEPVIlnQ G1xTtBcyVRkwMfgCB9qp5XHK9vXYUKlge398iEhC7pJK7TCU7jPMhAFZP04VQ+W2 iG+FjLGJEe386/vqlf6YJSptsXJ2XgAGQvfwNawkjJXswxdsNFsqcRbeD7lwzgGf Flb5+v1ykX+LLv4tL4F3y/0MNrYGBXjMpjcGzYBg+Bu86ETBAsCMzNoGffYkOLs5 9RTErj3N1VkclfwwybtH4uCBi3SHC8bXDuIUnJcYE8efB6vEQ8VBqqwNSL6AX+RD kg6ld4JpHTr07o/GkmB5xVR53QQrAlsYOh32UYH8dj97PfwD5eWxhbPMYrTY2n+/ 5H2C6gSuf//CXzcttFS6RLQkq2jL8HCmR57vFs8fNap0V7YO1Bmmj2n5jXJhOOhs o1s9OfWZfjgQOartjgC7VPBJ6KQFzVutbKZleZA/wSbk2UYxl1z9zvOMdJpxu7Ca 9iuZosENgtr7AqPiqOOtb11zavWGhJjvMpa+HiGc07kG8ysPO8OaI2hEvr3wXxuh 1ORZkxw8gj2NDTPNbzl1VnHWpmj7WsMWqduLqopJ16svjiSeVwS0Wwu1QAAS5/Lr LFOUPtZwq4IuYmB6Kr2w =72/k -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:
Accepted openjdk-7 7u9-2.3.4-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Tue, 15 Jan 2013 23:38:48 +0100
Source: openjdk-7
Binary: openjdk-7-jdk openjdk-7-jre-headless openjdk-7-jre openjdk-7-jre-lib
openjdk-7-demo openjdk-7-source openjdk-7-doc openjdk-7-dbg icedtea-7-jre-jamvm
openjdk-7-jre-zero
Architecture: source amd64 all
Version: 7u9-2.3.4-1
Distribution: experimental
Urgency: low
Maintainer: OpenJDK Team open...@lists.launchpad.net
Changed-By: Matthias Klose d...@ubuntu.com
Description:
icedtea-7-jre-jamvm - Alternative JVM for OpenJDK, using JamVM
openjdk-7-dbg - Java runtime based on OpenJDK (debugging symbols)
openjdk-7-demo - Java runtime based on OpenJDK (demos and examples)
openjdk-7-doc - OpenJDK Development Kit (JDK) documentation
openjdk-7-jdk - OpenJDK Development Kit (JDK)
openjdk-7-jre - OpenJDK Java runtime, using ${vm:Name}
openjdk-7-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
openjdk-7-jre-lib - OpenJDK Java runtime (architecture independent libraries)
openjdk-7-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
openjdk-7-source - OpenJDK Development Kit (JDK) source files
Closes: 695028 695992
Changes:
openjdk-7 (7u9-2.3.4-1) experimental; urgency=low
.
* IcedTea7 2.3.4 release.
* Security fixes
- S8004933, CVE-2012-3174: Improve MethodHandle interaction with libraries.
- S8006017, CVE-2013-0422: Improve lookup resolutions.
- S8006125: Update MethodHandles library interactions.
* Bug fixes
- S7197906: BlockOffsetArray::power_to_cards_back() needs to handle 32
bit
shifts.
- G422525: Fix building with PaX enabled kernels.
.
[ Matthias Klose ]
* Loosen OpenGL dependency. Closes: #695028.
* Fix error parsing drop files parameter from pcmanfm (Alberto Fernández
Martínez). Closes: #695992.
.
[ Thorsten Glaser ]
* debian/rules: Use gcj-4.6-jdk for m68k builds.
* d/patches/text-relocations.patch: build with -fPIC on all archs.
Checksums-Sha1:
8b0777e91dd78087389e906983d3043ab7d76013 2843 openjdk-7_7u9-2.3.4-1.dsc
42d05ceb4aba43effb7fe78b1a72ae58cd2ab3e8 73554974
openjdk-7_7u9-2.3.4.orig.tar.gz
993fd858d6ac40ed4d6374e56557381876d7f271 182775 openjdk-7_7u9-2.3.4-1.diff.gz
745393ece7571b5675c943c4e1a6079f6ae19c86 16874704
openjdk-7-jdk_7u9-2.3.4-1_amd64.deb
8647805f4c07728d9a0e6fcd1099f213107d1a4b 35273904
openjdk-7-jre-headless_7u9-2.3.4-1_amd64.deb
701b702bfc2b98dea97e63582b2e00c9fda6efa3 229188
openjdk-7-jre_7u9-2.3.4-1_amd64.deb
1ec24980855b1b8348dfab6f6446c1917131fb7a 2474148
openjdk-7-demo_7u9-2.3.4-1_amd64.deb
d6a77fee92b15389ccd4f587bf570315243fa16a 152169150
openjdk-7-dbg_7u9-2.3.4-1_amd64.deb
cc691fff55abeb14df7c0860028dd350bb26c702 634002
icedtea-7-jre-jamvm_7u9-2.3.4-1_amd64.deb
1c8cf7e00989f9359cf69bca0622d34b8ceb96f1 2337924
openjdk-7-jre-zero_7u9-2.3.4-1_amd64.deb
9a6946acf75fd1aad4bfca0d133f6f029cde299c 5534584
openjdk-7-jre-lib_7u9-2.3.4-1_all.deb
323d7276ff53ed8fa73cf5575ee37f6404b2ecd2 41387290
openjdk-7-source_7u9-2.3.4-1_all.deb
b3349d33527e8790d24347b044b00e53a84ff7dd 22084690
openjdk-7-doc_7u9-2.3.4-1_all.deb
Checksums-Sha256:
f1af8954a2bcf41f2ba54faae6e51c0a5f4bace036cc8349f8c7f007b1f4e355 2843
openjdk-7_7u9-2.3.4-1.dsc
92d7b1ff6c161bad055e366fb61a326d55320541cca643aa6c92ef7829c1cc55 73554974
openjdk-7_7u9-2.3.4.orig.tar.gz
a05ff524d57b727fb150b7773175dda1978cb4fdd498404a2a235f838251aeba 182775
openjdk-7_7u9-2.3.4-1.diff.gz
66c42d9e335a2624a2eb52e79245453d14b3f29c91694febe580e27cbe608a1c 16874704
openjdk-7-jdk_7u9-2.3.4-1_amd64.deb
229bd242eab47676c86317c6bea74b440ff99684e0517439a1027a41023222ba 35273904
openjdk-7-jre-headless_7u9-2.3.4-1_amd64.deb
5a7ae5a656a4e78cf3875f7bfa981cc7d0646d9abc2ec79e1356513e2ed471b9 229188
openjdk-7-jre_7u9-2.3.4-1_amd64.deb
6b3cc4b055f39c948d3d7ec737a48b5a815cd5ad7f1a265cd6a572ace3f9f873 2474148
openjdk-7-demo_7u9-2.3.4-1_amd64.deb
c2fbb538488d8a64498909eee15adade8b32f0d0a0e420236b7b7964ca4db776 152169150
openjdk-7-dbg_7u9-2.3.4-1_amd64.deb
5a07a4f5334c5933e0be57c2fa0c2f7b820352aa1ec710ea2bc7238edc5e6b46 634002
icedtea-7-jre-jamvm_7u9-2.3.4-1_amd64.deb
81a2bf61187388cdf17ed3e278b7dde864771cb9b884bb393e4082868b0f8660 2337924
openjdk-7-jre-zero_7u9-2.3.4-1_amd64.deb
d8ae3373e86a12550bcedc82a78af1fb03267454bf1f414d624818ce7713a00e 5534584
openjdk-7-jre-lib_7u9-2.3.4-1_all.deb
9fa8afe20214cee1916bf5bd1014c8ebbb7914012257034730a71dd65062161a 41387290
openjdk-7-source_7u9-2.3.4-1_all.deb
6b0059425dc5e2d97b9709ea9aca63e389b9a9ace3aedd66e8fb8321772c3693 22084690
openjdk-7-doc_7u9-2.3.4-1_all.deb
Files:
3d5c00dce2ab853ad868f7c4e5ffba90 2843 java optional openjdk-7_7u9-2.3.4-1.dsc
da0d7755a7e4fde471e01d6e92798f1b 73554974 java optional
openjdk-7_7u9-2.3.4.orig.tar.gz
2c1d9eb927275c228ddacf3897410cec 182775 java optional
openjdk-7_7u9-2.3.4-1.diff.gz
168893371f4b75ce374ff77d8fdbd89f 16874704 java optional
openjdk-7-jdk_7u9-2.3.4-1_amd64.deb
3154365657c5f93785a9b71e6dc6d4d4 35273904 java
Accepted ruby-activerecord-2.3 2.3.14-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 15 Jan 2013 21:16:20 -0300 Source: ruby-activerecord-2.3 Binary: ruby-activerecord-2.3 Architecture: source all Version: 2.3.14-4 Distribution: unstable Urgency: high Maintainer: Debian Ruby Extras Maintainers pkg-ruby-extras-maintain...@lists.alioth.debian.org Changed-By: Antonio Terceiro terce...@debian.org Description: ruby-activerecord-2.3 - ORD database interface for ruby Changes: ruby-activerecord-2.3 (2.3.14-4) unstable; urgency=high . * Team upload. * debian/patches/CVE-2013-0155.patch: fix Unsafe Query Generation Risk. Checksums-Sha1: 9247539c7145b6fe708d131e7e1954166ebe8d5c 1529 ruby-activerecord-2.3_2.3.14-4.dsc 3dd4ee27487578d187a4667b7c23f3c8da4269b7 11982 ruby-activerecord-2.3_2.3.14-4.debian.tar.gz c80f77118be5af3db2a8a1ef4898364833f3ad66 307674 ruby-activerecord-2.3_2.3.14-4_all.deb Checksums-Sha256: c9587127a95138c4a907d6404021fd37d514bb865baa28fb90e3eccf47d10013 1529 ruby-activerecord-2.3_2.3.14-4.dsc 83208d2a1ff9fc87adc196197200e2b6c9345303319cf67d1814377b7f597e87 11982 ruby-activerecord-2.3_2.3.14-4.debian.tar.gz a3bb62c3a3ea3a6cc6b87b6a1a997c27e68e35cea7e5d0671fa73dc5863d26ff 307674 ruby-activerecord-2.3_2.3.14-4_all.deb Files: 93422e5ed7e2189b3a5a72e1bc4e45c8 1529 ruby optional ruby-activerecord-2.3_2.3.14-4.dsc f4fa39778d4ebc603ab4e02cbd3fb340 11982 ruby optional ruby-activerecord-2.3_2.3.14-4.debian.tar.gz cd58858d16c8e25dd11f9b6090155f02 307674 ruby optional ruby-activerecord-2.3_2.3.14-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD2jTMACgkQDOM8kQ+cso+MWgCeJ17Py+n7OzdfOhCpxCeaR9F+ qgEAnjo1uQHIwo/Vywlv1ITO+rmte4t8 =GTZJ -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: http://lists.debian.org/e1tvrex-mi...@franck.debian.org
Accepted wokkel 0.7.1-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 11:12:37 +0100 Source: wokkel Binary: python-wokkel Architecture: source all Version: 0.7.1-1 Distribution: unstable Urgency: low Maintainer: Angel Abad an...@debian.org Changed-By: Angel Abad an...@debian.org Description: python-wokkel - collection of enhancements for Twisted Changes: wokkel (0.7.1-1) unstable; urgency=low . * Imported Upstream version 0.7.1 * debian/control: Update VCS fields for Git * debian/rules: - Don't remove egg-info dir - Remove override_dh_auto_clean target * debian/copyright: Update format to copyright-format 1.0 * Bump Standards-Version to 3.9.4 Checksums-Sha1: c14cebcf884357dcc7fc9b3f9a006ac22f0d367f 1314 wokkel_0.7.1-1.dsc 267b308e73a0f0a013d69540284ad8765022fcde 120217 wokkel_0.7.1.orig.tar.gz 4cf4b3640ecc6c5ade37303bebf8f474c2ed11fd 2698 wokkel_0.7.1-1.debian.tar.gz 85e2c31990edabf2ce1daf8424582b534c38db10 125444 python-wokkel_0.7.1-1_all.deb Checksums-Sha256: d9637947a9bcc51c5ead97980b33d26be9fd17ddb490636d1286d26fc89b0d95 1314 wokkel_0.7.1-1.dsc 5306591c28f406873fad1d4eba27e5e081a4a7f37e3725b24afd47b3137f4965 120217 wokkel_0.7.1.orig.tar.gz c93e9ea4a6468b049a393b023fcae3134498441ea2fe8d3780ef8f3f7b0e9c88 2698 wokkel_0.7.1-1.debian.tar.gz 99a4571e65a1ee3dff4d245ef81be5a723e39aa02fe6b46e19f243465af98362 125444 python-wokkel_0.7.1-1_all.deb Files: f4dea3d0aed12b465c64ad1476ede1ec 1314 python optional wokkel_0.7.1-1.dsc fe51e9aaf4846dcdd891c3049c0e0e70 120217 python optional wokkel_0.7.1.orig.tar.gz 060c61032be5c498074dae440d254a04 2698 python optional wokkel_0.7.1-1.debian.tar.gz 0be9e088a82bf58fc92bb44b97c190ce 125444 python optional python-wokkel_0.7.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlD2hnYACgkQCY2uR+47wnnxcwCglj0gU7BWkwUGttXT4J6iF8Lm wtYAn0znxbvGh1LEFNKpzO9JtCZy4wV/ =P6KE -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: http://lists.debian.org/e1tvqly-0003pi...@franck.debian.org
Accepted julia 0.0.0+20130107.gitd9656f41-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Jan 2013 12:29:42 +0100 Source: julia Binary: julia julia-doc Architecture: source amd64 all Version: 0.0.0+20130107.gitd9656f41-1 Distribution: unstable Urgency: low Maintainer: Debian Julia Team pkg-julia-de...@lists.alioth.debian.org Changed-By: Sébastien Villemot sebast...@debian.org Description: julia - high-performance programming language for technical computing julia-doc - high-performance programming language for technical computing (do Changes: julia (0.0.0+20130107.gitd9656f41-1) unstable; urgency=low . * New upstream snashot * No longer try to rebuild helpdb.jl. + debian/rules: remove helpdb.jl from build-arch rule + debian/control: move back python-sphinx to Build-Depends-Indep * debian/copyright: reflect upstream changes * Add Build-Conflicts on libatlas3-base (makes linalg tests fail) * debian/rules: replace obsolete USE_DEBIAN makeflag by a list of USE_SYSTEM_* flags * debian/rules: on non-x86 systems, use libm instead of openlibm * dpkg-buildflags.patch: remove patch, applied upstream * Refreshed other patches Checksums-Sha1: b06fb21052a79bf05f6a6dbab6a25e52c13ff071 2385 julia_0.0.0+20130107.gitd9656f41-1.dsc 80d9f32b66433055adc891ff49ed44308a9151da 2982460 julia_0.0.0+20130107.gitd9656f41.orig.tar.xz 388c55d0de6aadb601a60a792730180db5b16090 17325 julia_0.0.0+20130107.gitd9656f41-1.debian.tar.gz d5abc056cd8e97830c6333acdd36107a77cd2045 2024760 julia_0.0.0+20130107.gitd9656f41-1_amd64.deb c778e984af287ac89896ced771ae9ee4a44af096 1266608 julia-doc_0.0.0+20130107.gitd9656f41-1_all.deb Checksums-Sha256: 292ffef113c1047944d52545a5d55e5dd91910167a1e643e51e72296a1fef907 2385 julia_0.0.0+20130107.gitd9656f41-1.dsc 332de3937d0667e1e15ebad6d5e34ef2abfc7c40b82ce7616e4ae86e648c084f 2982460 julia_0.0.0+20130107.gitd9656f41.orig.tar.xz bd3ee127dc6f975623acf2f26e11233ed70b6a075d9e57250903bbecdadcfacd 17325 julia_0.0.0+20130107.gitd9656f41-1.debian.tar.gz 2d60279cb4021068abaf4a9a893b24e4dd21e49027d31c3ad8df86c49ddff5c8 2024760 julia_0.0.0+20130107.gitd9656f41-1_amd64.deb de8e3e5056adef4a679e78b86c5d935d090ad28c1332e124f8c028afee9113a2 1266608 julia-doc_0.0.0+20130107.gitd9656f41-1_all.deb Files: df739f369ffd6a4aeddc5fd48d758fbb 2385 science extra julia_0.0.0+20130107.gitd9656f41-1.dsc 41f70ca944766da281510cd848a11e2a 2982460 science extra julia_0.0.0+20130107.gitd9656f41.orig.tar.xz 3da37a964cb2d441248cda762a467e97 17325 science extra julia_0.0.0+20130107.gitd9656f41-1.debian.tar.gz 08ffe852489ac5716f13735781aed68f 2024760 science extra julia_0.0.0+20130107.gitd9656f41-1_amd64.deb 766caa63ca205373342f296fe37dc117 1266608 doc extra julia-doc_0.0.0+20130107.gitd9656f41-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ9pGHAAoJECzs6TUOzr5K2qIP/0Lj0MLZ8IVpsyC8VHAEUvTI YCVmZYnX/IJB2+fe5GWNi5ShlSpgD0fwzpb4q/TeTy6w04Tm1gEqYOl3tMf9Q0zI yM2EzkVlowu2phBYR07DdeW+ejyIKcskavYhNfZY1I97+fkYuxEW8jL8Yn711EBT 8l6j6qAJmP0KLp+stS8XrAmRnc3Y8d8ah0fncTXgRi7sY+UoIqANpeqlWErCFqL6 M49C4hEQwS4a+mi4A39Kzgqr2drRYlvj4pGUADu/TIFGSt8gORinCcCDcQ+xdvwK BIBgR4lYuD1FhJlJc/fViZ4M6FQnJbtiZwjUgfwAKqtTqj5AweROhs0WxLtKmn8V uJBgwRRPinDVK1LKpQj/7W3+Y/JJdhRK30QA6IWqfqncuBYO9DbKDbEkg5qi2nkQ DVg64R1lHWfQLFX+/Ve4SZMq3L5Af0UeQ+9OYPGvR13PGcuqICySPhnOb6UcHRKS 6nrf/0ZrcSqBao9RYMJx6QmdsLvGDveOauyYOCJSEzNA65GNlXLJRSjniQRwjvL1 1zJ0t1YFNYvH6mmoMx+IC6LxDwN8VXOrYa/oFPa6HLRMnu+KOL7ySnX1qH4h8ABy PXf/wdbXG2XWAgJs0VfmZU9H6Tfv/E5LKHEeIzollBrmbGw9z4ugXitgRlK6lKX7 pjsrGGXGVI/DSgCl6Lyo =xj9A -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: http://lists.debian.org/e1tvrt8-00032i...@franck.debian.org
Accepted libunicode-collate-perl 0.97-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 12:56:13 +0100 Source: libunicode-collate-perl Binary: libunicode-collate-perl Architecture: source amd64 Version: 0.97-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Angel Abad an...@debian.org Description: libunicode-collate-perl - Unicode collation algorithm built with fast XSUB Changes: libunicode-collate-perl (0.97-1) unstable; urgency=low . [ Salvatore Bonaccorso ] * Change Vcs-Git to canonical URI (git://anonscm.debian.org) . [ Angel Abad ] * Imported Upstream version 0.97 * debian/copyright: Update debian years Checksums-Sha1: 6d00df8753278e9fa43aca69fd96059b1f2ef0e8 1584 libunicode-collate-perl_0.97-1.dsc f4ff02eb641779a56d0f21a8a54fd18a92452ec8 931698 libunicode-collate-perl_0.97.orig.tar.gz 71c8251fc6774b7e590c2de6e613624aa9176925 3936 libunicode-collate-perl_0.97-1.debian.tar.xz 208a36ca7793e94a61602e23216fecc7652576d8 570304 libunicode-collate-perl_0.97-1_amd64.deb Checksums-Sha256: f75fa053691dedac7b2fdb0ede8853121b9c275f71038f49217ed20d7e66cad4 1584 libunicode-collate-perl_0.97-1.dsc b00e86e885ff9d3b4950c8db8716e4e4d7e957e315f5026c465c56c9640a9bee 931698 libunicode-collate-perl_0.97.orig.tar.gz be2eec1e081fa5475c83372ce02dec79982026265268a3b58df72953a72faf9f 3936 libunicode-collate-perl_0.97-1.debian.tar.xz dc58b1eb4a6dc0406c16aafbcd6ca80801f229514fca4f2bb36b4928cf881c92 570304 libunicode-collate-perl_0.97-1_amd64.deb Files: 1e9099ebbc79be5b681dcccbb902d37e 1584 perl optional libunicode-collate-perl_0.97-1.dsc e85eee9c8d7bbc4c133a1b75654bda8e 931698 perl optional libunicode-collate-perl_0.97.orig.tar.gz 3f9052ec08f53880cc7d3e99e73fa8a1 3936 perl optional libunicode-collate-perl_0.97-1.debian.tar.xz daa53a36e516e39e2240ffcdfee71fd2 570304 perl optional libunicode-collate-perl_0.97-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAlD2lsUACgkQCY2uR+47wnlcyQCZAYjtv448s935dUvo2w6Bpz/C AAYAoJ0FShocRoSes9zKpOZ7XA1KykvH =4Yq6 -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: http://lists.debian.org/e1tvrvw-0008rp...@franck.debian.org
Accepted twisted-mail 12.3.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 12:58:52 +0100 Source: twisted-mail Binary: python-twisted-mail Architecture: source all Version: 12.3.0-1 Distribution: experimental Urgency: low Maintainer: Matthias Klose d...@debian.org Changed-By: Free Ekanayaka fr...@debian.org Description: python-twisted-mail - SMTP, IMAP and POP protocol implementation Changes: twisted-mail (12.3.0-1) experimental; urgency=low . * New upstream release * Bump Standards-Version Checksums-Sha1: 1a18d639ed5c911dd57ee03246e0e4bb4aa0 1215 twisted-mail_12.3.0-1.dsc 00fdafe4b9263c6640d26a1b5b284d87835c20bf 154204 twisted-mail_12.3.0.orig.tar.bz2 d3b3af6391d1c8d6e35d729b96c619a3e866ac99 7674 twisted-mail_12.3.0-1.debian.tar.gz 765d13cccff0cbd63070646092e7b0a7da3ca9d4 206696 python-twisted-mail_12.3.0-1_all.deb Checksums-Sha256: 9be6931398534e859433ba9b7a86ea5307e6dad303a043e0eddd77bb5f458b6d 1215 twisted-mail_12.3.0-1.dsc 339f04f9d49f9be2945086c7d1ffb530bcbc653ae0151d3fa0bd899ad82034b0 154204 twisted-mail_12.3.0.orig.tar.bz2 8bc06a7bf9f337bdd74a746967f157286b52871e8c665a1cfa8a846f4e0a5fe2 7674 twisted-mail_12.3.0-1.debian.tar.gz 891e4869dd52948c3364bb7a875a9ed2e89dc21b259b202856f29a45c001250f 206696 python-twisted-mail_12.3.0-1_all.deb Files: 9fcdad08940db56bade51c97e8ae1536 1215 python optional twisted-mail_12.3.0-1.dsc c285ce7e7b2d8e606b3d35a26b025bad 154204 python optional twisted-mail_12.3.0.orig.tar.bz2 8c22fbfc0ec5e34ef9e5b0353570398e 7674 python optional twisted-mail_12.3.0-1.debian.tar.gz ce10fe26a257018360ea47b0f4f4b201 206696 python optional python-twisted-mail_12.3.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD2l10ACgkQcanJGlcVnllI0ACg2da6tJ85AkvMOBMwFmdOIQE7 GqMAoIYk9OT3/65ocf+Bdc7wLKj1Dyav =KiTI -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: http://lists.debian.org/e1tvrw2-0008um...@franck.debian.org
Accepted xtv 1.1-13 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 12:34:15 + Source: xtv Binary: xtv Architecture: source amd64 Version: 1.1-13 Distribution: unstable Urgency: low Maintainer: Barak A. Pearlmutter b...@debian.org Changed-By: Barak A. Pearlmutter b...@debian.org Description: xtv- View the screen of a remote X11 display Changes: xtv (1.1-13) unstable; urgency=low . * bump standards version (debian/control) * dh --parallel * dh 9 Checksums-Sha1: 24285444fbb12de057eb0d2c6cfd77b0e15a2715 1108 xtv_1.1-13.dsc 105bb621d666c79f60cd99d79b3781622ec25b57 6568 xtv_1.1-13.debian.tar.gz 37bcac3706dca22907b8f7409f9e3626500496fb 8156 xtv_1.1-13_amd64.deb Checksums-Sha256: e194973238878892f56e37cf8740e028edbd0d82622b4fe776ec3f48c76bc887 1108 xtv_1.1-13.dsc 5ba377ac98ce2cb67174959e6983768bd03d4a97d5acff97678df0c35e6e38b0 6568 xtv_1.1-13.debian.tar.gz a1021b173f4f8d99ad2d829b1b90b259c17b7bafbd581325120ef078ff192db0 8156 xtv_1.1-13_amd64.deb Files: 6d181fe5042d119d4d9ac3f38864cc7d 1108 x11 extra xtv_1.1-13.dsc 696962cf0e6d7c79e6d0b4a6e35b2e96 6568 x11 extra xtv_1.1-13.debian.tar.gz 72a0747f17e130590f644a9a636a7a12 8156 x11 extra xtv_1.1-13_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD2pCQACgkQLz4Gnv7CP7IE/wCfWVotTYf6myhzb72EZzKWQcUB gwEAoKjTfDnXzvJYq9Xq1ZQGfn3/3yL7 =KCoS -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: http://lists.debian.org/e1tvss7-0002jo...@franck.debian.org
Accepted libio-prompter-perl 0.004003-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 16 Jan 2013 13:25:20 +0100 Source: libio-prompter-perl Binary: libio-prompter-perl Architecture: source all Version: 0.004003-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Salvatore Bonaccorso car...@debian.org Description: libio-prompter-perl - Perl module to prompt for input, read it, clean it, return it Changes: libio-prompter-perl (0.004003-1) unstable; urgency=low . * Imported Upstream version 0.004003 * Change Vcs-Git to canonical URI (git://anonscm.debian.org) * Update copyright years for debian/* packaging files Checksums-Sha1: 3f590aeb00d90742f5bf7d6503108538a58715cc 2175 libio-prompter-perl_0.004003-1.dsc 40fd90b71b178188e38698a2d274bb1ea26546d1 41566 libio-prompter-perl_0.004003.orig.tar.gz 465996bf5f0edf4ae409175bcc51cce28681b441 1974 libio-prompter-perl_0.004003-1.debian.tar.gz 840d15e17f9f8eae44d7c3b1a13214e099611be6 62344 libio-prompter-perl_0.004003-1_all.deb Checksums-Sha256: 3d0539e424d1a791ffd8b027749c5fcd88251c32cc07cd2d437d84dc073eb6da 2175 libio-prompter-perl_0.004003-1.dsc cadc70d2b285d4e20637d442a075e66333f0e314a0d882703cf39562ef242277 41566 libio-prompter-perl_0.004003.orig.tar.gz 80178d98ac9ace33caa4936a188642257d5748aad1f945120266a2f5cec11abc 1974 libio-prompter-perl_0.004003-1.debian.tar.gz 78060c94c15f3d07d72d6247d973e20b7ec79a23fe5cca1f63ba6cdabed2db04 62344 libio-prompter-perl_0.004003-1_all.deb Files: b277463d437979274f7180c04087158e 2175 perl optional libio-prompter-perl_0.004003-1.dsc 97a429faf54d898b7fb6a7a1363a75f3 41566 perl optional libio-prompter-perl_0.004003.orig.tar.gz adaaa917e17c2a906268186020eb5adb 1974 perl optional libio-prompter-perl_0.004003-1.debian.tar.gz ab8aef439d9fdd5965b876215d2c715c 62344 perl optional libio-prompter-perl_0.004003-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQ9q0LAAoJEHidbwV/2GP+fjsQAJ8US+TzEzC3WihDNnQGggxh kN0qGJMTSPpXZFWKLFb6f4yF9+Np7vijPYkyQek0E8HqJgDSvrpmmm3CgqIuagZc +5b8/Nt9wrQj2qUtMdN/Uh37YHdIx70uIpKdV9eMi8Z+C01CYfxUYXgs0lJvZ2ff 4YRZrKNqEUI74VaVAxOON69MGPu7PLaKaGP7ClP9nOZGEF68kzxjI5Jholm+AvlX BhFvqbcxFkLprsfmgrGOOPGXsJ4zxiQEQxno0gGwu10oSiDq1c5hUuC1KIeGOuOm R3lFqgZzz3biYT5H7kAtyAh0vVg3SSFODGWRvrCuwOEOZkizkLvTRrrl+ANE4HdO KooASfYrUPHS0qdZEtkON4CJzylqCHq7kY7H9wgky6cFZm4/Wu9LdNNaU6wRlGL3 zcDEdzcDYKfTQjvash9W9jxtOSB3Csz/fpp/ZzTn8NoMd8gEuJ2/0sS9oeZRhUGb 0gEJHXzdG/LeVjvVXy1+CaEumTtT1U8BfFcSY+LaSLK/nXFSY3nsyUSYhnOK8Uq8 n8k6NOOIcpb2RU8BK7f1YbWd5pWIPK/emPKaHyuK604Mn1puswDk+Ab/SEk1idUh ZUv1VRpryamdqrvs3ycl/grGqZT8i2WMztXejJxmLled+vWECyqDsHJUMfbxp03W bx/nbiFtjCo7XdfgwAhn =CLOv -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: http://lists.debian.org/e1tvtkz-0008a8...@franck.debian.org
Accepted liblivemedia 2013.01.15-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 16 Jan 2013 14:20:43 +0100 Source: liblivemedia Binary: liblivemedia-dev libbasicusageenvironment0 libgroupsock0 liblivemedia1 libusageenvironment0 livemedia-utils Architecture: source amd64 Version: 2013.01.15-1 Distribution: experimental Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Benjamin Drung bdr...@debian.org Description: libbasicusageenvironment0 - multimedia RTSP streaming library (BasicUsageEnvironment class) libgroupsock0 - multimedia RTSP streaming library (network interfaces and sockets liblivemedia-dev - multimedia RTSP streaming library (development files) liblivemedia1 - multimedia RTSP streaming library libusageenvironment0 - multimedia RTSP streaming library (UsageEnvironment classes) livemedia-utils - multimedia RTSP streaming tools Changes: liblivemedia (2013.01.15-1) experimental; urgency=low . * Team upload. * New upstream release. * Drop linker-flags.patch (accepted upstream). Checksums-Sha1: 51a31b1973fc93a029a3777d86f2783c2f5af256 2407 liblivemedia_2013.01.15-1.dsc fe4c70b708b1cdefdeccdad72cd4af615df38e29 569955 liblivemedia_2013.01.15.orig.tar.gz 3d41af39d04113abc1c04b418824480213cf929f 18484 liblivemedia_2013.01.15-1.debian.tar.gz 4b7fefcc10ab53dee4a623b18f4be0c2cf02c05f 1147552 liblivemedia-dev_2013.01.15-1_amd64.deb b358361bbac4b31df391cdd1b93c6a80eae6a2e1 24620 libbasicusageenvironment0_2013.01.15-1_amd64.deb 8e8e8652f3f2a96f859602d989bb082ac039964f 31152 libgroupsock0_2013.01.15-1_amd64.deb dbc870dd2babfe46cf6f635e0d9afc8a5df5c268 342784 liblivemedia1_2013.01.15-1_amd64.deb f16a52f2a433634ae45a6c81c8148084957a7d02 12244 libusageenvironment0_2013.01.15-1_amd64.deb d8d1ef3a1e0c579480a98ec282fb46d14cb3373a 121410 livemedia-utils_2013.01.15-1_amd64.deb Checksums-Sha256: 500321bc1f9f8acfed5abe6b28789944e1cc4b95c99317369ac32a7b8805bba2 2407 liblivemedia_2013.01.15-1.dsc a12458a9a64b0ca63cd1e36bf90b8e0edbb870eea8500b913c1d9de7ee3d7823 569955 liblivemedia_2013.01.15.orig.tar.gz 3c8a12313f42f483bb11fdb594d46c4efc4c471c8d8ef80a752e00d6e5ad5339 18484 liblivemedia_2013.01.15-1.debian.tar.gz d3b8ccf6ca05ea7a2fb280bb7d20d153fae4cc240c56695b315be8dcbfc12ba1 1147552 liblivemedia-dev_2013.01.15-1_amd64.deb b7f03fc2d5a06c38b10c7187cdcd099dd519599e725e5a559cced453a215aef5 24620 libbasicusageenvironment0_2013.01.15-1_amd64.deb ec47e69d2d2b862562deee8f8ce16da19d72615eb6729a7a649325d33e787880 31152 libgroupsock0_2013.01.15-1_amd64.deb c1e500491cc1bcef08a518f4d0a01b90e3cbe0675ef9f1bd3cab3f215d567ef3 342784 liblivemedia1_2013.01.15-1_amd64.deb 88e5d169100994ec57344855e377b180b3282943c8e8c53dfbdef24e1e6b4e30 12244 libusageenvironment0_2013.01.15-1_amd64.deb e360e1c2a91b188d8fde37a70ca43c1730322be91bb9c22fd490e8496a2069a7 121410 livemedia-utils_2013.01.15-1_amd64.deb Files: c17e9d0476dc7719c1855bfea8521ccb 2407 libs optional liblivemedia_2013.01.15-1.dsc acdf517eea51ec16541750fca0f0e567 569955 libs optional liblivemedia_2013.01.15.orig.tar.gz 773b62f2d4a4eed61023bfe49bd8420e 18484 libs optional liblivemedia_2013.01.15-1.debian.tar.gz ffef243cf08c037c3b1e9b028a11c186 1147552 libdevel optional liblivemedia-dev_2013.01.15-1_amd64.deb 84d2f3621365b42ed837c07aab1e7612 24620 libs optional libbasicusageenvironment0_2013.01.15-1_amd64.deb 6c59a58f00ce047bbdd1e9bcb57e2df0 31152 libs optional libgroupsock0_2013.01.15-1_amd64.deb 748aedf42097b39b81ce55ce96c5c6e8 342784 libs optional liblivemedia1_2013.01.15-1_amd64.deb 8915e79eb29d9367bd360065a365448f 12244 libs optional libusageenvironment0_2013.01.15-1_amd64.deb da2d2201ca0a683912847eedcde804ed 121410 net optional livemedia-utils_2013.01.15-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCgAGBQJQ9qxJAAoJEBWetcTvyHdMwGwP/A81d/Td2ZQv5FzuEnAkEega MdYdyS9ssX6gJ/cAPHXVF6l7OtCrR0SfC/nbgAUO9rkfdiEGNcLSsPx4UfWSBvl9 JjMUV1tvMMDO03rUgBlMeoIOgYrQNDu78zz7arij+QoL24IC07L9lNAR6mPyCyYx lDr3Y5Wtrv8DS0NF8OWwoLGAnzN92nBRY+DBgJUFyTUFS56eW5TQpyohtf5NnGbO E9ldXY0vu289EIAycv8evSu58ygXw8luHU4fscMeAF+cRLVyckkMwn3tzqYBqe/W yMhrE+ErDooetaEpb06dWP/CcbfqZJhd6pNPaSp6hVAsVKIDWeaUtxDuHqq0VZA6 d732VM2+UsuYI6Jbnc05NPazA1f9lsHw494cP6+ZMX2iamMMjLXBLciEwPC/Z/Ns WCl+fz9QVl8SxnCOQhL6okhwsYKuH7kGoCCOeO0z4kcy389qpXn5i6OARABWWO7C 0R/MGYb+OvZkAS5olO8m385/68r/W3mQtrlNr21rzw2y4jLaqvJ7pE8QcNDbpCes govUo2VYqv4gCUTkQ44HLAz4iEUdfp6ZE0QlZw5S+A45Z72ghiRYIYT6aSIg3HJ4 AO5coOazAsJX8K1mxvlLN0efqa6AxVs3YMek2at+Z43vNM9iYBovDOUqebDA1Vgs 5lGA4b7WAUeOdMV14lWR =Nql7 -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: http://lists.debian.org/e1tvtl9-0008q6...@franck.debian.org
Accepted git 1:1.8.1.1-1 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 08:17:53 + Source: git Binary: git git-man git-core git-doc git-arch git-cvs git-svn git-email git-daemon-run git-daemon-sysvinit git-gui gitk git-el gitweb git-all Architecture: all source Version: 1:1.8.1.1-1 Distribution: experimental Urgency: low Maintainer: Gerrit Pape p...@smarden.org Changed-By: Gerrit Pape p...@smarden.org Description: git- fast, scalable, distributed revision control system git-all- fast, scalable, distributed revision control system (all subpacka git-arch - fast, scalable, distributed revision control system (arch interop git-core - fast, scalable, distributed revision control system (obsolete) git-cvs- fast, scalable, distributed revision control system (cvs interope git-daemon-run - fast, scalable, distributed revision control system (git-daemon s git-daemon-sysvinit - fast, scalable, distributed revision control system (git-daemon s git-doc- fast, scalable, distributed revision control system (documentatio git-el - fast, scalable, distributed revision control system (emacs suppor git-email - fast, scalable, distributed revision control system (email add-on git-gui- fast, scalable, distributed revision control system (GUI) git-man- fast, scalable, distributed revision control system (manual pages git-svn- fast, scalable, distributed revision control system (svn interope gitk - fast, scalable, distributed revision control system (revision tre gitweb - fast, scalable, distributed revision control system (web interfac Closes: 698055 Changes: git (1:1.8.1.1-1) experimental; urgency=low . [ Jonathan Nieder ] * debian/git.NEWS.Debian: bash completion script moved to /usr/share/bash-completion/completions/ (thx Philipp Marek; closes: #698055). . [ Gerrit Pape ] * new upstream release. Checksums-Sha1: 7edd7e4dbe664492b7967d5ee3405f7b3a2b29f0 2027 git_1.8.1.1-1.dsc 44b90aab937b0e0dbb0661eb5ec4ca6182e60854 4295398 git_1.8.1.1.orig.tar.gz 85080033b4421df319ae1bcc65964c34ca4170be 535005 git_1.8.1.1-1.diff.gz c693350688f8c95140c8fa6e4933dab62766dc57 2440176 git-doc_1.8.1.1-1_all.deb ced675bd9f72efc351a60f23d35b2bd69399e714 500688 git-arch_1.8.1.1-1_all.deb 143ecb158642241871976995dd8792b4a1ebb333 574160 git-cvs_1.8.1.1-1_all.deb 59a378f0f15221bf7e2f553cbe037b8fec33a7ba 520080 git-svn_1.8.1.1-1_all.deb 57ddc4b2991c85b36a187339fb6c472af250ef3c 487258 git-daemon-run_1.8.1.1-1_all.deb 28716a639b577a711efe91f41edd60df2ff2ea79 488668 git-daemon-sysvinit_1.8.1.1-1_all.deb b1955e2136032b96ad856df1398e86e6150af5c1 505982 git-email_1.8.1.1-1_all.deb 806a895a42a830445c503df6b3196ba4100e25f7 767122 git-gui_1.8.1.1-1_all.deb 62801afdf82d77911e40e9ae979196342c476060 615414 gitk_1.8.1.1-1_all.deb 3bb47c43e4819d5193ed8fefab47e149e65524e7 490468 gitweb_1.8.1.1-1_all.deb 0035ec4e2ce7f8114cf8dbdf10cc7ba679ea3be2 485310 git-all_1.8.1.1-1_all.deb c30ab5559c9f3f86588add59a1a544a33c4f4b3d 1350 git-core_1.8.1.1-1_all.deb 7ce949d84e16154e28794186347935bea1a9f6d8 509212 git-el_1.8.1.1-1_all.deb 5d3c12a1796df2c0c69c80dc02069057d3b71679 1127348 git-man_1.8.1.1-1_all.deb Checksums-Sha256: de26b0a162ed8d6ce245b7102fdfa1b813a66416a44f74d2aad0937e6c85e9a4 2027 git_1.8.1.1-1.dsc 8b5bd081dc38f3e14acc86f234231a9a46d1e9a990c8c732aed6856d2714dff6 4295398 git_1.8.1.1.orig.tar.gz c15b895bfb233d42758b58724bfab022b760ba07cd40eaae1a62140c0d447b80 535005 git_1.8.1.1-1.diff.gz 1df0068eff6a090f7734532d5ba6995d804ac32030bad0d307abba5876985452 2440176 git-doc_1.8.1.1-1_all.deb 556783c7dfe59ec90eb74157a827f1986f8b3e100b83ba514af4207ff1d837bc 500688 git-arch_1.8.1.1-1_all.deb a45e35cb55d5646a4d12b2066bafd96f2f7ad9d0782a302772d84aaa80912741 574160 git-cvs_1.8.1.1-1_all.deb eb00c4b5926f84870abe2493e81afd4a55d383d16c3d97277f4db08b1b333e00 520080 git-svn_1.8.1.1-1_all.deb b6c85018bab560e5fa91e5c822695c9e380c43ed20013e0dc6a2c20cac88094f 487258 git-daemon-run_1.8.1.1-1_all.deb 77a369c88563a7650e9cccb81cbc73d0915208d3b8ff16660e1ffd6186c8ca9a 488668 git-daemon-sysvinit_1.8.1.1-1_all.deb efc12fe4ab435f8665fdeabc11cb96cd9aae28d829f7398e4d01c055e7df8eda 505982 git-email_1.8.1.1-1_all.deb 4a90da45b393b45f1f71fe6a2479c0d03c88c1568b23b2b8dddae0bda9b98b92 767122 git-gui_1.8.1.1-1_all.deb 88900eb8ea50efccd863298b779c385607a7fe1a72d74c78540ef51e06f5ffac 615414 gitk_1.8.1.1-1_all.deb 7d306de9278451630a252e40f7f33fa7a80c21434f9039f4f776695a842c75ff 490468 gitweb_1.8.1.1-1_all.deb d4a0cb5d4d78f31d315ac017322e7cf86b9dc5d48cd865d6ce9939bebafc3328 485310 git-all_1.8.1.1-1_all.deb 3ea089253013fbd4fe473c5ce21449a56d78195cb40a65db56d0278ff893ffa1 1350 git-core_1.8.1.1-1_all.deb 60ddad5c3206c3f29626fbf22520cda0a4eaad64f80f0879be4d1fa25e9b0ceb 509212 git-el_1.8.1.1-1_all.deb dd13a4f7b63657fbe905cabcd2105ccba7223b650d9f03a61e9e224000b43a1c 1127348 git-man_1.8.1.1-1_all.deb Files: 5480c1a777f8c88c699d2bf38d9c980f 2027 vcs optional
Accepted bcron 0.09-13 (all source)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 10:13:37 + Source: bcron Binary: bcron bcron-run Architecture: all source Version: 0.09-13 Distribution: unstable Urgency: medium Maintainer: Gerrit Pape p...@smarden.org Changed-By: Gerrit Pape p...@smarden.org Description: bcron - Bruce's cron system (programs) bcron-run - Bruce's cron system Closes: 686650 Changes: bcron (0.09-13) unstable; urgency=medium . * debian/diff/0008-bcron-exec-Mark-all-temporary-files-close-...diff: new; from upstream git; bcron-exec: Mark all temporary files close-on-exec and close selfpipe; this fixes a security bug in bcron where cron jobs get access to the temporary output files from all other jobs that are still running (closes: #686650). Checksums-Sha1: acf2f180ec33b25510d373a00edcb8057221548b 1042 bcron_0.09-13.dsc 13967b5f9bc815f44da4d3c57dfcae0155da00d1 9893 bcron_0.09-13.diff.gz f3b7353f6e83f25e2a0015d8bf01793ea1decfec 8930 bcron-run_0.09-13_all.deb Checksums-Sha256: 4ce05a73efee27ba75d6a95efdb5ff8f9915ca70c041a0ef15182c4fb7e8e878 1042 bcron_0.09-13.dsc d7a5c0da1e7cb92faa1fa9a29ef4c6636f1f9df158acd9f94ae35e7e5b304f52 9893 bcron_0.09-13.diff.gz f7700963d863fdaa08f30360b6ceaa1ec303e9fb10185beef4e29bce98d1c3ce 8930 bcron-run_0.09-13_all.deb Files: 4617fcc0b0c088ea88656e22f6588e3f 1042 admin optional bcron_0.09-13.dsc d2fc2b72ebd095d55764e8f6e6ad2e67 9893 admin optional bcron_0.09-13.diff.gz 2dea60dad96f5c0d3843bab5000527d6 8930 admin optional bcron-run_0.09-13_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD2gFMACgkQGJoyQbxwpv/DPACfWNiOscyMpSz8wj03EMExC5CX SsIAn2nS3o4wWZqwjHU7AIB3IdWioS87 =8npn -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: http://lists.debian.org/e1tvuvy-0004kl...@franck.debian.org
Accepted python-secretstorage 0.8.1-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Jan 2013 19:10:48 +0400 Source: python-secretstorage Binary: python-secretstorage python3-secretstorage python-secretstorage-doc Architecture: source all Version: 0.8.1-1 Distribution: unstable Urgency: low Maintainer: Dmitry Shachnev mity...@gmail.com Changed-By: Dmitry Shachnev mity...@gmail.com Description: python-secretstorage - Python module for storing secrets - Python 2.x version python-secretstorage-doc - Python module for storing secrets - documentation python3-secretstorage - Python module for storing secrets - Python 3.x version Changes: python-secretstorage (0.8.1-1) unstable; urgency=low . * Upload to unstable. * New upstream release. * Add missing python3 build. * Build docs using sphinx. * Removed obsolete d/patches/bzr_use_check_call.patch. * Bump Standards-Version to 3.9.4, no changes needed. * Moved dependencies on python*-gi to Recommends. Checksums-Sha1: e9bc935e6f023e5c4d5d82cd183e501704ed7125 2303 python-secretstorage_0.8.1-1.dsc 7d0208775d50b4d19ad007909fc63072b8360ab4 12874 python-secretstorage_0.8.1.orig.tar.gz e91e28cda993dc2f34d7e381861ad4b00c67ff10 2718 python-secretstorage_0.8.1-1.debian.tar.gz 797c99bfc55c08267a0521f2770571133b4d5963 8956 python-secretstorage_0.8.1-1_all.deb b07079f4a9a88f27b33a1d352353778ad0d20704 8732 python3-secretstorage_0.8.1-1_all.deb bf163273853fd69e1138eae513ebf454468a7351 34678 python-secretstorage-doc_0.8.1-1_all.deb Checksums-Sha256: 94c4b31244b017531742a544a8ed5df6615f68cfbb837eeb85892ecc443eaf32 2303 python-secretstorage_0.8.1-1.dsc 00d9ce8bb684884db5958f4367dd98999c125dc1cb8366377fe1fa02dceea8aa 12874 python-secretstorage_0.8.1.orig.tar.gz bce0606045b56a14a090ae19c9c7305b6011afadfba2a4cd0400e85f1927 2718 python-secretstorage_0.8.1-1.debian.tar.gz 2e76010086a674d1be5e4af3bd6cf32c5d8ac43bc054caafea84a75f41c2fd14 8956 python-secretstorage_0.8.1-1_all.deb a6d8b7577036850706c28c789da9db26d22b010c0f3a8566ad5ef4befd9dd68f 8732 python3-secretstorage_0.8.1-1_all.deb d265b54edb93d213c38de430093218be0fe3f084abf362db783e541811cedf37 34678 python-secretstorage-doc_0.8.1-1_all.deb Files: 1a18bda7b20c3bf46973acba6fb930a4 2303 python optional python-secretstorage_0.8.1-1.dsc 1d9b3a469f78d44b4e11c67edb574365 12874 python optional python-secretstorage_0.8.1.orig.tar.gz 36f129caff76303f57ea5798c27b62aa 2718 python optional python-secretstorage_0.8.1-1.debian.tar.gz 396f0dde886615c83ad1e3048b06a5b6 8956 python optional python-secretstorage_0.8.1-1_all.deb ee3b61266dd19d7e5d6bce13ff0c1bbe 8732 python optional python3-secretstorage_0.8.1-1_all.deb 2270921f26cde8cb88154f4f990459ea 34678 doc optional python-secretstorage-doc_0.8.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJQ9sM7AAoJEGAmk20vHIrgnPcP/jg58hfV8TagnsK3k/brhIBe ARoDXXPqr+fkY29cIJdwMnisnCawts536lUkbM7vHhaACvc2A5NHgBPvY3KnOfNn JSetEdxXgoGFzvjLwlYx90fm9gV/KqRTyX0vpgPrSKzkHgsf/qmxw6/I2Aj86nGP 2rR0avxGHL2wMWRXG9W1Pr+GlWl6dA9Sajm3Hmrg0UOFOrdfoOCLSM2UtaNGtJRC dvEmKtPNcdrO/Siz5HclGh7FtmGn87GR8k2SjnpdOUKEoygmOeO8rwYlB+xfUbxL B+ALGZXEbERWSvoIUkzVVww664d0cYB6aVdbuKSmY8cAc8Dh9hLYdG3NkIjur+TK 7gWvR7yXfCN/PKEdaLK7fr/0Qzz92jB8hDsV7YSOnRPbTK4K9jbTk2RezFp1jssp UTzm4UxWmEVbrqsy+6zs6uqCRI6DnWrjeqHYF2mndJAi6e4uv8r2r5ajxFfDy0UY cpRszXYMiZjm37MQGar+ixeIO2EtmXazhz8wMZgWaYXwq8ubJ7LP2CLknVv6AOFj 4/QLGsp3icvtRk3FUgw43jrNJU6XjAvEtlZNDKejwAGKRNn47B0N5a609kcvCx62 iS7i3jj/0RUtBk+EjdN7sOfV6lV4+gG/iQunK8fpDsVk40eXmEw9FKVFGWeySbuV CUrXbFrRLuFNLc77MwIo =9qlI -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: http://lists.debian.org/e1tvuyk-0001pc...@franck.debian.org
Accepted sciscipy 1.0.0-1~exp1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 13:56:14 +0100 Source: sciscipy Binary: python-sciscipy Architecture: source amd64 Version: 1.0.0-1~exp1 Distribution: experimental Urgency: low Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org Changed-By: Sylvestre Ledru sylves...@debian.org Description: python-sciscipy - Python binding of Scilab Closes: 697244 Changes: sciscipy (1.0.0-1~exp1) experimental; urgency=low . * New upstream release * sciscipy depends now fully on Scilab stack (Closes: #697244) * Enable numpy features * Also search Java in /usr//lib/jvm/default-java/ Checksums-Sha1: 43b5c37a20867ac89ddbb3b83dc386489390d0c2 1507 sciscipy_1.0.0-1~exp1.dsc 503e878b221e6c4400f8177f89d00a59d61f14da 143087 sciscipy_1.0.0.orig.tar.gz 25a6e8d711fb89a5f096e3ce265e3eba272128bd 2581 sciscipy_1.0.0-1~exp1.debian.tar.gz d9ec8ba7d604790f24a8b003f8a1e56811eb9014 20342 python-sciscipy_1.0.0-1~exp1_amd64.deb Checksums-Sha256: 9c66829bfae2bd384df7ba15d1948f747d4357f6e6b753d3e6c2b0c91b528543 1507 sciscipy_1.0.0-1~exp1.dsc 91d73aa35adc62f24b1d175f30792b1be1611f1a2269f112e235956d05b42889 143087 sciscipy_1.0.0.orig.tar.gz 1b43bfdfd6e4f41cd2b79467e1638ba00c305bf22acb66195e0afb487303f827 2581 sciscipy_1.0.0-1~exp1.debian.tar.gz 111da7099a2532758bdadecda51b1084743df2ab495c7739ce6d7efdcbb1cb8b 20342 python-sciscipy_1.0.0-1~exp1_amd64.deb Files: 8d2312f67158afc90e39fdf1f7385b21 1507 python optional sciscipy_1.0.0-1~exp1.dsc 5031372fabce020879585336b9f1acb5 143087 python optional sciscipy_1.0.0.orig.tar.gz 8cce369da5b4f4d5554d8995e2bbfdff 2581 python optional sciscipy_1.0.0-1~exp1.debian.tar.gz a5b33adf41b9c409718ca6d50ac5bc2e 20342 python optional python-sciscipy_1.0.0-1~exp1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD2w+EACgkQiOXXM92JlhC/UACeMBcNYezPTlPwinNHo5uOJfmS FOUAnjz38xa/NOyAfd7ZuQnubIV2KEpM =3dRD -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: http://lists.debian.org/e1tvuyp-0001st...@franck.debian.org
Accepted pcsc-lite 1.8.8-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 16:24:42 +0100 Source: pcsc-lite Binary: pcscd libpcsclite-dev libpcsclite-dbg libpcsclite1 Architecture: source amd64 Version: 1.8.8-1 Distribution: unstable Urgency: low Maintainer: Ludovic Rousseau rouss...@debian.org Changed-By: Ludovic Rousseau rouss...@debian.org Description: libpcsclite-dbg - Middleware to access a smart card using PC/SC (debugging symbols) libpcsclite-dev - Middleware to access a smart card using PC/SC (development files) libpcsclite1 - Middleware to access a smart card using PC/SC (library) pcscd - Middleware to access a smart card using PC/SC (daemon side) Changes: pcsc-lite (1.8.8-1) unstable; urgency=low . * New upstream release * do not use a pcscd group any more. pcscd is started at boot or by systemd Checksums-Sha1: 051c6fc67d404a65ded6519b6100fa00e7fce40b 1493 pcsc-lite_1.8.8-1.dsc 714efaaaf5333e4a04309efd3a6dbc8e7edc61ce 551751 pcsc-lite_1.8.8.orig.tar.bz2 71e126f535afcdcfce115a763dc06f1df675fb0e 15686 pcsc-lite_1.8.8-1.debian.tar.gz 3f81be2d445fcd39bd217be6df15979439dfda38 98216 pcscd_1.8.8-1_amd64.deb a46fc4213c80de225395dadb3850ecca08a0f269 76146 libpcsclite-dev_1.8.8-1_amd64.deb e95937e87de5933a64ebea8d8ac84aecd2eca7cf 215668 libpcsclite-dbg_1.8.8-1_amd64.deb b14f207b9f482dc2b75e90148ddf4d78a60e31b8 57630 libpcsclite1_1.8.8-1_amd64.deb Checksums-Sha256: 87cef8e36c380c8fb1730e8581774daa793a4acf4eb83ed0e339b2a00d3b269f 1493 pcsc-lite_1.8.8-1.dsc fe66354a7e738d3ef8b4e572c7e447b85894da9262381fbf004e8abcc12885e7 551751 pcsc-lite_1.8.8.orig.tar.bz2 aeefc31462ea63ece1f0e33d849cd42cd01d0c3ab30804b45f815852c08c9169 15686 pcsc-lite_1.8.8-1.debian.tar.gz 15ef4345ef1608cc1638293f25ac733794944244aef4bc5e8d9fd69811d596c2 98216 pcscd_1.8.8-1_amd64.deb 436d325388b80017730b8dcb37520c16cd89ffbc47d6d2f0b54595f6f67f460d 76146 libpcsclite-dev_1.8.8-1_amd64.deb 6332d86acd25495adfe618c64b87b4938f744ce7b7433f9961fdd226a87b3bae 215668 libpcsclite-dbg_1.8.8-1_amd64.deb f950c2b00ef6db8cec9718fdf5a853ab6573bc4895b247603f4d88a8fbe34a07 57630 libpcsclite1_1.8.8-1_amd64.deb Files: 875e24922c5870bb3f3e41024a6c7a16 1493 misc optional pcsc-lite_1.8.8-1.dsc 069dc875a2ae2d85a2ebceac73252c0a 551751 misc optional pcsc-lite_1.8.8.orig.tar.bz2 faff3190c8f3fb0358d887fc2408e1b8 15686 misc optional pcsc-lite_1.8.8-1.debian.tar.gz 12cfaf4c10d6507270cb697c09d2b54f 98216 misc optional pcscd_1.8.8-1_amd64.deb cf63b8cb72303d8d24d9fd7051db69d4 76146 libdevel optional libpcsclite-dev_1.8.8-1_amd64.deb db86129c162efef96cd56adb814d1792 215668 debug extra libpcsclite-dbg_1.8.8-1_amd64.deb 499a5ebdfb821ac993f75c3de3def6d6 57630 libs optional libpcsclite1_1.8.8-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEUEARECAAYFAlD2yI0ACgkQP0qKj+B/HPkNAACcCPkCDhW8sxYqNm/f3H3Wuk4h RL4AmJVflUL2qb34m2Ui2xbaoWFcOZE= =Tq4C -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: http://lists.debian.org/e1tvvdh-0004ha...@franck.debian.org
Accepted swath 0.4.3-3 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 22:34:04 +0700 Source: swath Binary: swath Architecture: source amd64 Version: 0.4.3-3 Distribution: unstable Urgency: medium Maintainer: Theppitak Karoonboonyanan t...@debian.org Changed-By: Theppitak Karoonboonyanan t...@debian.org Description: swath - Thai word segmentation program Closes: 698189 Changes: swath (0.4.3-3) unstable; urgency=medium . * Urgency medium for security fix. * debian/patches/01_buffer-overflow.patch: backport patch from upstream to fix potential buffer overflow in Mule mode. Thanks Dominik Maier for the report. (Closes: #698189) Checksums-Sha1: 4cfb2c57684e5735371f44d0ad2994d657144327 1910 swath_0.4.3-3.dsc ecf7d4f360890a71927e7e69e7491fa56a20d57e 4914 swath_0.4.3-3.debian.tar.gz e50a8db9a69c983d6756c3a0acff11c0fcc31c1a 156210 swath_0.4.3-3_amd64.deb Checksums-Sha256: cf46f4a632649ad2ffeffc624afe462a3319516917fdb12f0c1cae1a4bd539cf 1910 swath_0.4.3-3.dsc 431c3331a31088db1c6f030012a8e869c9f9938b769bf5e6892f5d2364e7eb0b 4914 swath_0.4.3-3.debian.tar.gz 4b2443be7e6610d7f93640c5bf15f8741253a3d1d00ed0d143adb7e8d8fc208d 156210 swath_0.4.3-3_amd64.deb Files: 4af3de21d577b947e6ce6febfccc051e 1910 text optional swath_0.4.3-3.dsc 81b164634325d20afeee0a253310ed15 4914 text optional swath_0.4.3-3.debian.tar.gz e84576ae28d81e3e61601626e32e04d0 156210 text optional swath_0.4.3-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJQ9s1HAAoJEKLrrtG2+QJBwoQP/3eFYIAC9+oxgptbldno4ucS I/ZcZJ9HxbcFA6mkbif/K5LxI1cQOnlQhsIjJL/ss0853HU9wMsy8mD9B4RI4uJf 7g7ymINPZgVmTUJvhMuRzu4EL+05C8rejx8Pl+ibWg0T6pJ7WkLiqTtHTTHnXiVi 9UIroSH1O9FCE1yoD40PnaNl128JPgoNhxZhazNrT16q8pVIko1TkO5hS9bnXnwX 9ojZS5Vj6bUoJcQC6xdGGpNcpdvBXhPfwANwUf/tTlW1BAHirn8SWEJUXNAZ/w1h 9sw/q5lphWVDL6Kn6ey+lAqi7DO5isE3DdR2vKMU+AMHxCxQI5Jm4Wv03ujPHR7P CykkjZnml7Ug7d4OLt5y+FrRInfIRCQ7Qk6VXQoiYHCn/gDPE7ERFTCSnZQWXmjD mzDuyyPBHo+ZT37HMRkS6RNmYL3zYlweHbny3zjZo1W6ZGqQsS14s3TIYRtcTIA3 qiAw1jXG4KbdBV6DoO6uhP1QodF9YB9uQO839Pvh2/NQ0dduMRAPOzFNO6+ByuTb 5WHA8+kJ18hk4+3XQIrnuvkcwf/IXlU2iKvYVVA0t8PNPE9FHuoayMEbG1Kef0kL K1eOgEvmwBoQxicVk/53Oo2lsdbpIAlAVJlmphQa/uos8HtyFCNH9bjNhDF77Bu4 ElX5Eet6f/rkhHb9+Y9t =oLZ1 -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: http://lists.debian.org/e1tvvrg-000797...@franck.debian.org
Accepted ccid 1.4.9-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 16:41:46 +0100 Source: ccid Binary: libccid Architecture: source amd64 Version: 1.4.9-1 Distribution: unstable Urgency: low Maintainer: Ludovic Rousseau rouss...@debian.org Changed-By: Ludovic Rousseau rouss...@debian.org Description: libccid- PC/SC driver for USB CCID smart card readers Changes: ccid (1.4.9-1) unstable; urgency=low . * New upstream release * debian/control: Standards-Version: 3.9.3 - 3.9.4. No change needed. Checksums-Sha1: b4b01d23727cb0fe973eee9002d24505d5b4173b 1260 ccid_1.4.9-1.dsc da28de874903c221c10e06ca6af26e46b871d2a0 470339 ccid_1.4.9.orig.tar.bz2 f7104a5506cbb448b473040d2fb6f96dd7b0b86c 6471 ccid_1.4.9-1.debian.tar.gz 359d89a498301b4f3f8ed6e1e81d7555d4fa329d 191060 libccid_1.4.9-1_amd64.deb Checksums-Sha256: 3f92bdfbaa7e97c28b60cde7e21b6c0218be4fa44491e4aaa2444726d748c8f5 1260 ccid_1.4.9-1.dsc e4b3f245c6c436e41391dcc142c38b101087378f6fbd3aa0c3f0cf9d53e93d54 470339 ccid_1.4.9.orig.tar.bz2 857f9f81afa1b8715784a98e9d2342fad6902f775401fbf0923f8d14de907543 6471 ccid_1.4.9-1.debian.tar.gz 84c579695ad1a2eed340dc9a046e0ec7ca4486177835e8c1396401dd222fa816 191060 libccid_1.4.9-1_amd64.deb Files: 34a5c456365293bf5ac1637810cc59c2 1260 libs extra ccid_1.4.9-1.dsc 1afd9cc6fb1676d1fdd605d10c70d08e 470339 libs extra ccid_1.4.9.orig.tar.bz2 29cac9435933f786bbe2abbe4ea2b132 6471 libs extra ccid_1.4.9-1.debian.tar.gz 4e1746627380654002346168308cbd38 191060 libs extra libccid_1.4.9-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD2zmsACgkQP0qKj+B/HPkF8gCfap5CssH5GYi0BohLpKjSc6AX cZoAn2BGOy7MskKVkBDHQ5LmLbDfzx6J =KR4i -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: http://lists.debian.org/e1tvvgf-0001rl...@franck.debian.org
Accepted scirenderer 1.0.4-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 16:52:44 +0100 Source: scirenderer Binary: libscirenderer-java libscirenderer-java-doc Architecture: source all Version: 1.0.4-1 Distribution: experimental Urgency: low Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org Changed-By: Sylvestre Ledru sylves...@debian.org Description: libscirenderer-java - Java rendering library based on JOGL libscirenderer-java-doc - Java rendering library based on JOGL - doc Changes: scirenderer (1.0.4-1) experimental; urgency=low . * New upstream release Checksums-Sha1: a64a562d120c50ba5e72d4688643cd0455b8e5c0 1515 scirenderer_1.0.4-1.dsc 7a3924fd1fe2b60af41b3379ee401bb9e8e5e824 109724 scirenderer_1.0.4.orig.tar.gz 2b339e75b2ffb08c889f70014b04000700aa24b8 9093 scirenderer_1.0.4-1.debian.tar.gz ec5271af96c472de820e159214b32a0e39fb09fe 152946 libscirenderer-java_1.0.4-1_all.deb f63ec13619cbaccca34b00796ea12af6388b3ee6 303616 libscirenderer-java-doc_1.0.4-1_all.deb Checksums-Sha256: c91a44c4eb0de766e4767d7db131c278948a29c1b6ccb88278042ac81e6bdb75 1515 scirenderer_1.0.4-1.dsc fb48cb4695776681e8d60a17662d60e4701e147ff7863861ad7bbf5ebc5f6faa 109724 scirenderer_1.0.4.orig.tar.gz 849bf0a0861a9245e969a70fd48768caa1c8932c85869f37bbfceec2cd29ef3b 9093 scirenderer_1.0.4-1.debian.tar.gz cce275bde217012dd6d0dc3a2c2c0bc4c67f075ed99dd8a1fcfa6614e47f8012 152946 libscirenderer-java_1.0.4-1_all.deb 4351e028560eea6dd7035600ed450d6eebe1a5170ae85aefa8178ebf5efcf9be 303616 libscirenderer-java-doc_1.0.4-1_all.deb Files: 98310e34e5e8d8f7c85a43da3dcdfb2e 1515 java optional scirenderer_1.0.4-1.dsc fe6394f13db401d0611713324617c1ad 109724 java optional scirenderer_1.0.4.orig.tar.gz 398329488d6d1e3e9971354ab750ed98 9093 java optional scirenderer_1.0.4-1.debian.tar.gz 8fa5cf7b7814e0083cc593d9e7c4074f 152946 java optional libscirenderer-java_1.0.4-1_all.deb 1f44181917c76fc6b4c4d65caaf7294a 303616 doc optional libscirenderer-java-doc_1.0.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD20WoACgkQiOXXM92JlhCk2QCgwfcj1lWe2g3zUFlRNwjKZraJ Bz0AoORHkrkNuI2wfjg46eV1vlz9d8d9 =UYb5 -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: http://lists.debian.org/e1tvvul-0004le...@franck.debian.org
Accepted transmission 2.76-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 15 Jan 2013 22:35:18 +0100 Source: transmission Binary: transmission transmission-common transmission-dbg transmission-cli transmission-gtk transmission-qt transmission-daemon Architecture: source all amd64 Version: 2.76-1 Distribution: experimental Urgency: low Maintainer: Leo Costela cost...@debian.org Changed-By: Leo Costela cost...@debian.org Description: transmission - lightweight BitTorrent client transmission-cli - lightweight BitTorrent client (command line programs) transmission-common - lightweight BitTorrent client (common files) transmission-daemon - lightweight BitTorrent client (daemon) transmission-dbg - lightweight BitTorrent client (debug symbols) transmission-gtk - lightweight BitTorrent client (GTK interface) transmission-qt - lightweight BitTorrent client (Qt interface) Closes: 695115 698134 Changes: transmission (2.76-1) experimental; urgency=low . * [ef26caa5] Imported Upstream version 2.76 (closes: 698134) - update libutp to fix alignment issues (closes: 695115) Checksums-Sha1: 1041202873a115d88873a327b89af621bd72f937 1849 transmission_2.76-1.dsc 410441da2eb11f5457d67b85e01492d68ce62c21 4335915 transmission_2.76.orig.tar.bz2 28f99a3bbb8856dc50236b7281c1d1018426e106 16568 transmission_2.76-1.debian.tar.bz2 6de14efb625f57be877bfc5c7e4a6d991827e544 1086 transmission_2.76-1_all.deb 46ea9ac0a0d0c191badc6cd7e2f171f2f0faee35 297170 transmission-common_2.76-1_all.deb 8ab662f50a1160926591fba0236f99b29a0b9e8a 12873586 transmission-dbg_2.76-1_amd64.deb fde80d683cad07a057832acb130200e8a6802043 1165250 transmission-cli_2.76-1_amd64.deb 3808eb2f58caab119cfd4271e34f8d76f6a7992c 1198366 transmission-gtk_2.76-1_amd64.deb 5966536fa4dc23d1ddda84bdd2190396cd691ebd 651542 transmission-qt_2.76-1_amd64.deb c6e98399656cc589ce45d4a8c2ecc8701497cafe 237488 transmission-daemon_2.76-1_amd64.deb Checksums-Sha256: dd6d0197f075d631f87ab49ed20d5fdcf21e8a9a4995942784902c740a96c928 1849 transmission_2.76-1.dsc 9015319a1191313d0082af5fdea371322f3b9c078a12f14238b72debaf80ccac 4335915 transmission_2.76.orig.tar.bz2 f1f2be674b966f5daf614a0a88596af4a8764faeca0bc1ca11645452ed08b25f 16568 transmission_2.76-1.debian.tar.bz2 ef5fb9f7e483827dbf720b8a3ed3c2bed7c2c8dde5a6c48de013e5922141ba90 1086 transmission_2.76-1_all.deb 7dcc708de50e1e43c80c6e44722e49bf517147eeceaef7926f665ebac780e59c 297170 transmission-common_2.76-1_all.deb e64f528ab0d789602dd208419561c203c450f96749546eeac921bf4b0f6ad212 12873586 transmission-dbg_2.76-1_amd64.deb a2af5d7856aa015c9c97b1323595ee13de2de24539d4cf3c6913092911a75b81 1165250 transmission-cli_2.76-1_amd64.deb 9eb357075215e66b372470c372b2d971afd83c7d0f03424afb6e2fcac802aa26 1198366 transmission-gtk_2.76-1_amd64.deb 90cdd00afff7a91aeea141d5b0349bad97ae0a2b30ddefe56b71f4ae7b312dd7 651542 transmission-qt_2.76-1_amd64.deb a0643114d7dd50cb51461f5b68e05dbcdef78f441db9dca97cb80e8708ef6936 237488 transmission-daemon_2.76-1_amd64.deb Files: 248645b9208d7ac04f93ef081fc8bcb4 1849 net optional transmission_2.76-1.dsc bbe6fb5c9e8a0f8d970defb1d80a28df 4335915 net optional transmission_2.76.orig.tar.bz2 217a0e7f79232df8c5e025b29c39c491 16568 net optional transmission_2.76-1.debian.tar.bz2 2e67521d27aa72762338da733cb5c2cc 1086 net optional transmission_2.76-1_all.deb fe4c3ba996786975d1f21d77049db415 297170 net optional transmission-common_2.76-1_all.deb 28db8251cb2dcb05e042052dda6753d6 12873586 debug extra transmission-dbg_2.76-1_amd64.deb 8eb4d69dc13311e778787579b05a953d 1165250 net optional transmission-cli_2.76-1_amd64.deb 024f70b7a3d857068a44f5b7a385b5b5 1198366 net optional transmission-gtk_2.76-1_amd64.deb d1a074eb84f90517af1f733c523be45f 651542 net optional transmission-qt_2.76-1_amd64.deb dcc9ec1b76ed3acedc45d600609c4a2f 237488 net optional transmission-daemon_2.76-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD23lQACgkQImLTb3rflGYJ8gCfbsomQx9hWHSyUAkJi/c8YCaO YRoAoPimR7YLo/2bx26Y2j7PWFb9eh59 =Lq+q -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: http://lists.debian.org/e1tvwcr-0005o8...@franck.debian.org
Accepted tor 0.2.4.9-alpha-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Jan 2013 10:28:49 UTC Source: tor Binary: tor tor-dbg tor-geoipdb Architecture: source all amd64 Version: 0.2.4.9-alpha-1 Distribution: experimental Urgency: low Maintainer: Peter Palfrader wea...@debian.org Changed-By: Peter Palfrader wea...@debian.org Description: tor- anonymizing overlay network for TCP tor-dbg- debugging symbols for Tor tor-geoipdb - GeoIP database for Tor Checksums-Sha1: fcc28ff5e535d254ce7b8e8a215b5cb1243c7678 1726 tor_0.2.4.9-alpha-1.dsc d46f967df8c5dc0bea81fc7c1f6c3bf79c7e2c90 2895169 tor_0.2.4.9-alpha.orig.tar.gz a0cb03743d7d67317f9df8bf762ccca440116000 35320 tor_0.2.4.9-alpha-1.diff.gz a1645e0095497e823f3e5155035d2a71627162dc 1049524 tor-geoipdb_0.2.4.9-alpha-1_all.deb 17c0d9507d0f16476868064ea93e529ef2a66b16 1313064 tor_0.2.4.9-alpha-1_amd64.deb ce1d9a038ef2d191f0056bc98a1d045f6e2b84b4 105042 tor-dbg_0.2.4.9-alpha-1_amd64.deb Checksums-Sha256: bdffef059c8076893c4c1f540f3766331861fc86d6b65c8ae581b417b751c02b 1726 tor_0.2.4.9-alpha-1.dsc 6a0a0069faea0c58187381b7f603bb31a44bb8d4e0341385e225d03b6a32c463 2895169 tor_0.2.4.9-alpha.orig.tar.gz 3d49b892587858c576a97a5892fabd001b426fd3f2243b646c39e0612458e25e 35320 tor_0.2.4.9-alpha-1.diff.gz 0825faa4e7fa00f71086c1597768122a56648ed9caffa13e428a2a3a96ecf115 1049524 tor-geoipdb_0.2.4.9-alpha-1_all.deb 43700821cbf201a36b7fc52a3872369daf39cd477fc2ae711212b7b9ed1c0d71 1313064 tor_0.2.4.9-alpha-1_amd64.deb b25b0f8e03125b74ee4928e0997ec12ceea690c8b3ec20d73ed88fc335c4b191 105042 tor-dbg_0.2.4.9-alpha-1_amd64.deb Changes: tor (0.2.4.9-alpha-1) experimental; urgency=low . * New upstream version. * Build-Conflict with libnacl-dev so that we don't pull it in accidentally. For now Tor doesn't manage to use it on at least amd64 anyway, but that may change. We should review this decision once we know how things work and where we want to use nacl. * Move the geoip6 file to the tor-geoip package (spotted by George Kargiotakis) * add appropriate Replaces and Breaks to the tor-geoip package for tor 0.2.4.8 since we moved a file to tor-geoip. * If $DAEMON $VERIFY_ARGS fails, call use the same arguments for finding the errors and not $DAEMON --verify-config. Files: 6d814a62a61cc0f8b4b43b1dc3cc44dc 1726 net optional tor_0.2.4.9-alpha-1.dsc e922cf0c0c711192f97a90a3533adf67 2895169 net optional tor_0.2.4.9-alpha.orig.tar.gz 827d6438f8266601ba3dd6148da386ac 35320 net optional tor_0.2.4.9-alpha-1.diff.gz 5ae988510ad30e3b784091b23918976e 1049524 net extra tor-geoipdb_0.2.4.9-alpha-1_all.deb 2dda97fb49d3ba5a8ce7a384735736ed 1313064 net optional tor_0.2.4.9-alpha-1_amd64.deb 3c011f24f39f10dd9fb7c30cd608d569 105042 debug extra tor-dbg_0.2.4.9-alpha-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBCAAGBQJQ9uG4AAoJEDTSCgbh3sV3AjsH/j9jjO2aW9fn60d6w6Tvqj/p QdXSHV0sacg5ET40qqTCSqacDdQ1GG8xjb/vGI4EOjgRnfEtP1bk/vtowMFUOvtE Egz6qaeVCpEkioQOyMEhEKpn8z4vLmh2j0/LI7XQ1k2Qc68VE7zq7jOGphgQ/BRz YRIMB7KNBpgUQs8sbQmO6v5INgThJ16PQ8LQRJP/8xuKguQbhYCanR2l1r1nqGUy a16ghDoUO2ePYjG5zsXnClgNjrfWr5dhWMfeLQzn4hL2JIbARTR3s1iSzdUUH2j+ GXd7NFdj9ctqo3C1Jf9CnL618hkZcLjvvZILeeQIPK6rKoqEpdxQ1rsynxtug9s= =Xr44 -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: http://lists.debian.org/e1tvwqn-0008ca...@franck.debian.org
Accepted gfs2-utils 3.1.3-1.1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 Jan 2013 19:36:49 +0100 Source: gfs2-utils Binary: gfs2-utils gfs2-cluster gfs-pcmk Architecture: source amd64 Version: 3.1.3-1.1 Distribution: unstable Urgency: low Maintainer: Debian HA Maintainers debian-ha-maintain...@lists.alioth.debian.org Changed-By: Salvatore Bonaccorso car...@debian.org Description: gfs-pcmk - Global filesystem 2 - pacemaker module (transitional package) gfs2-cluster - Global File System 2 - cluster tools gfs2-utils - Global File System 2 - filesystem tools Closes: 685061 Changes: gfs2-utils (3.1.3-1.1) unstable; urgency=low . * Non-maintainer upload. * Add missing Depends on gfs2-cluster for gfs2-utils. Fix gfs2-utils: fails to install due to incorrect dependencies in init.d LSB header. gfs2-utils init script contains a dependency on the service providing gfs_controld, which in turn is provided by gfs2-cluster. (Closes: #685061) Checksums-Sha1: 8c51782773986fca0777b38674f5d2cd25f0d67a 2352 gfs2-utils_3.1.3-1.1.dsc 70ba70d308fdeffe76d4a64d4102ba6e79925593 8963 gfs2-utils_3.1.3-1.1.debian.tar.gz 75d9ba6f38789bb56a234b69e8ee442e4d656a18 346054 gfs2-utils_3.1.3-1.1_amd64.deb 018ca905628e2a151d23d7272238c8494b623f96 57446 gfs2-cluster_3.1.3-1.1_amd64.deb 5a99c73d216f9cfda415752c4c55821f41d49295 2330 gfs-pcmk_3.1.3-1.1_amd64.deb Checksums-Sha256: 8be41b9e382feccf1e1e30281efd9b2f6d7f24233d41a4fb26e7a8f330ebdfe6 2352 gfs2-utils_3.1.3-1.1.dsc 2437974b72d56a59d9e27d35b0833a2b5ceb5cfc498d7ce3fb1fd8587a56034f 8963 gfs2-utils_3.1.3-1.1.debian.tar.gz 02dff1c688cf731a21b1f0c05f4e4606c7b4c4c9f9d437f76865330100c73a20 346054 gfs2-utils_3.1.3-1.1_amd64.deb f8476028c136d954ab06bf1bae7598620e0df08f931e87e7e0f9355f2fa5ef41 57446 gfs2-cluster_3.1.3-1.1_amd64.deb 0714721a2daf7b2f31ffa5b34b2e029034708fd73b2688bb789ed1e5bef37f56 2330 gfs-pcmk_3.1.3-1.1_amd64.deb Files: cf41f3cf0e5d9a5aab3ed26736fa4da1 2352 admin optional gfs2-utils_3.1.3-1.1.dsc 650721adf446fcc6351bdc0182df6583 8963 admin optional gfs2-utils_3.1.3-1.1.debian.tar.gz 44d0dbb15948e220985e6b06e6a490d6 346054 admin optional gfs2-utils_3.1.3-1.1_amd64.deb 45ef3411fb44d3e9ae5570bda68b86cc 57446 admin optional gfs2-cluster_3.1.3-1.1_amd64.deb 25f2fa4e3e7059431a6884d5a05b61fe 2330 oldlibs extra gfs-pcmk_3.1.3-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQ8Fi2AAoJEHidbwV/2GP+G2IQAMx3tUiApjXXtttFd5ylFBJa RU34a4Xq+ff/eYL6avmJO2uQ8R7CKycZglJ2Dq05/K/ftsadZdpuzCYoFMlzZ/y0 LgcGQU8MHugPLu4z2T//xkyh9q8YCV8GkXOUUCuVllyWOPhuhkRpOmTVaL8gjmTG xjo93eE1XPC567w5HfW0M/lFrHhlQWtXgGgkOgwEGIlHlcOjR22BFk+crTxtJIR9 JfSt35YIz01bZB7GrfzmXbYTZp2emFpwPLwxEeTsH9GslNhAMuq6dmKO3VfRSAeA LJefGRqMo3S0MXhLTYTChE/XAULZEiieDje+x6LLKk4FNSZJLty5vv6enzhVAKet OIC4CAwYoobKz57wgwDplmBst3dLWaTpBBL93Z+fPvEej5mB0ONzk1xJn4dZxeNM WZ9IObzKs7Wqfi8gsH4k/N2LADV87GbWzSepz1Ur31t/MQi8qm79/L4ueumfF05p WHY0tls2ZiwaExKSzabgEpmkIDleoldvQpl/VAhY+UuCPbxkHuapGWr+MjtoHi62 a1Py53/BuAa2forcrspe+8tnltGPNhcnPYfopDVgftyiYAvP4d3i/GR9RoPYpzUl 3QQDY4jf2OoqubXJZ7P9spyp/hlSfytkhBJF4kyNYo+fD9jlRUX55wgeHmtdHrRl 8j82Y5moiVi+XauzQLoH =qpvF -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: http://lists.debian.org/e1tvyfq-00018u...@franck.debian.org
Accepted qpdf 4.0.0-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 13:44:28 -0500 Source: qpdf Binary: libqpdf10 libqpdf-dev qpdf Architecture: source amd64 Version: 4.0.0-2 Distribution: experimental Urgency: low Maintainer: Jay Berkenbilt q...@debian.org Changed-By: Jay Berkenbilt q...@debian.org Description: libqpdf-dev - development files for PDF transformation/inspection library libqpdf10 - runtime library for PDF transformation/inspection software qpdf - tools for and transforming and inspecting PDF files Changes: qpdf (4.0.0-2) experimental; urgency=low . * Patch to test code for detection of binary attachments on big-endian systems. No actual qpdf code is changed. Checksums-Sha1: dd11b8b112e1069158d00c78855a3c11619dbfb3 1817 qpdf_4.0.0-2.dsc 08f85a0651ba6a95e5a576effbfa5f74b87d8183 7848 qpdf_4.0.0-2.debian.tar.gz e0e786d2b3c39f357efaff9375906f251a3ebf5e 357418 libqpdf10_4.0.0-2_amd64.deb 1fb0c05889d693e417637a70e2d7c7010fa0c2b2 520828 libqpdf-dev_4.0.0-2_amd64.deb 0a0f8fe0cf837ad7c524d92a4617726c57f1cf60 224290 qpdf_4.0.0-2_amd64.deb Checksums-Sha256: 505968748d7d598d5b590eb881ea6f9a13ccaa63c4f810751edcf3a7401af63a 1817 qpdf_4.0.0-2.dsc 7016400adde122c7050826347fec119198b2663873a5205d4e652fc0c92a712c 7848 qpdf_4.0.0-2.debian.tar.gz 261a67cf27220b17d2f83c8f23dce53adb66c693535bf454cac3d7f6c2697c9d 357418 libqpdf10_4.0.0-2_amd64.deb 046b62840bf6796200595f1ffb3f27a5e153e10b93231a31dc72b4f6d05f25b1 520828 libqpdf-dev_4.0.0-2_amd64.deb 511e02043ce68ce1bff9b9eed44f139ec22746b652489d79f8a56fed96fed0ce 224290 qpdf_4.0.0-2_amd64.deb Files: c2f5becd2ffcc3aa0a02a124cc8e5e7d 1817 libs optional qpdf_4.0.0-2.dsc cb1f3a472f6aa2dbc7a612f3a5d60ff8 7848 libs optional qpdf_4.0.0-2.debian.tar.gz 50a9c9b77aae14b636fb0d202c78ff45 357418 libs optional libqpdf10_4.0.0-2_amd64.deb 500d3a093882778900f67f6a714d6bd7 520828 libdevel optional libqpdf-dev_4.0.0-2_amd64.deb fb9353932954f027cf6f9bee2cc78036 224290 text optional qpdf_4.0.0-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJQ9vbpAAoJEIp10QmYASx+mvEQAIfgQgiikpyskMoSpr2c4Ybx Dc+zFB7jdoKXOnVrKvJgvB/6R7QzJuj+ZncTNRgnki0Edtc8P8XeMId4oo5HS53+ 9IbOIYiRARSA5BNpF5AVPQIl4E2jRhnZboIaXnnAYlZFyFDYwoiFC5F+tn/u1kUr WRUgSh2AezWPqqtyOuCRMU5ynTd+TRPjc8GPIDbt3EZM4mQhjrYrs2BmykeA16E3 HBOFt9rEdlNK6zrOcwQoBdCBYakPg9Z/xAdKDQbi0gNzOtlcfj9rbWMk91wpRPuo cP9hAs2kPmRdmVokXi1aTb7yLUup0cDNmzv7LRzGgfO2jkLRDrWJ5QSIp0fn/GvB 1pSqQF6uP2rJ6KCZ39zI8U6IpIOSM+GQjgVWDs/QAu3ERW+xAYyMvhOrKI49WtIH eDTzE5+KxAgjiK0JKPZNzASTkEKUyl9pj3hBKQWmAyCEIQ3E/SraPJLxEZDdYy7A kmXHX8TcocWIAsXIpwu2Wf2ortzYS4EDg0QGsH4daRZnufThSHUbcc4iu90Q/QLx ryVvHOyjLSk56i2ftpdALUIUAur4I1D7Wm0XAgLejIDQxBQhyGhdxjU0PDZgqEA3 VV7DSQYOHCzdElpEg1NPo1dyjqiIC5YZlyXR8hUj4C7ZW6/xgSGzOLG2SR45Jjh5 g9Di25aIPVqBHD6ckB3s =Vg3k -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: http://lists.debian.org/e1tvyfy-0001er...@franck.debian.org
Accepted supertransball2 1.5-6 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Jan 2013 17:02:03 +0100 Source: supertransball2 Binary: supertransball2 supertransball2-data Architecture: source amd64 all Version: 1.5-6 Distribution: unstable Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Markus Koschany a...@gambaru.de Description: supertransball2 - Thrust type of game supertransball2-data - data files for supertransball2 Changes: supertransball2 (1.5-6) unstable; urgency=low . * debian/rules: - Use separate dh_auto_install-arch and dh_auto_install-indep overrides to avoid a FTBFS on the build servers. Checksums-Sha1: 230f0d3e390d01e4f881156fe6ac6bbe534a0126 2150 supertransball2_1.5-6.dsc 08aab2a815e23933f6ade3cfcd10b50885e82d5c 280265 supertransball2_1.5.orig.tar.gz 0646915a65c08818882966469cd036d9eb1ffd71 25990 supertransball2_1.5-6.debian.tar.gz 5c358c9cc031becc1a81069153548552dda11059 75404 supertransball2_1.5-6_amd64.deb dbd216e79aafbd91d4ef367732794bb46d184c40 239902 supertransball2-data_1.5-6_all.deb Checksums-Sha256: 9138d98b8033d0abda92ca64e0cd543188151b5dd6399ca2218ff8694eebac84 2150 supertransball2_1.5-6.dsc b62a5854cf00807077888a5b0ed41e5cbd191747d2ed40790e9d61dc04a76bd5 280265 supertransball2_1.5.orig.tar.gz 58fe96c43e1e3d8898fc08a088505f0cbe13b489486c8b0ae633d2bd871d74c6 25990 supertransball2_1.5-6.debian.tar.gz 30b08580eae46a07923cde07a1dd5cb1b7436953c8d463feed5cf1ba9453 75404 supertransball2_1.5-6_amd64.deb f020cab257c1dbf197e468c02780a2652e95331e0537f359d7cd97eac199df45 239902 supertransball2-data_1.5-6_all.deb Files: d3992486d4c7db78e83942630b1c165b 2150 games optional supertransball2_1.5-6.dsc d7dafaca8aa5dcb5d74fbc36789c325b 280265 games optional supertransball2_1.5.orig.tar.gz baa072fb9bf8cbda104d4be71681da8b 25990 games optional supertransball2_1.5-6.debian.tar.gz 536117bf5928df302d6b6004de937b24 75404 games optional supertransball2_1.5-6_amd64.deb 354c97e3c16a4af93d24b6ecf6ba5172 239902 games optional supertransball2-data_1.5-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ9va/AAoJEHQmOzf1tfkTyCMP/inr3HPrWdslUbE2qp4UqJxf QKy7ceoKFZ56h+1eiaCAHUe0uZoL0488jr8ZrsoEutbCR9gMVTh3Rrz17dJ7jYor aJZrbFPiyv/VeZBxcqHYCpedGp0znEyaaQpWEhPkfNW+1ov3CKpaOhqw4kJJGuJt siKNCAqU2q1t622YMK26eJprxRJudpQqMebShVHBiXNb+K8nYrNGuqxrIYXJQPcg Ekim1h5w91vqi1Z6FqsEjM8UeVJqXYzTnbdWctXHRhPI5z1fs2xOFWNvNMXbjNxp bBCv/0bbzLRUoB9yukDDKi+nKpy8cCyIMLlzGyYRHFAktEtBGW2Gv/81g4GH+Ym4 R4clDUeN9KDHzM4VK75rYro2rWBol7XkEn3ina1Ub7I7Vda866ZJUdSlk7w40KYv ElMA5dDGzlR8zDI1+tzc8Bn70SB5XL0NxgrI7CCC7HUovKggF2athx+dnaRqYcO2 Jw0oh30+OJflPy4VzyxYw1imiVEpAZ1uQF9PkVanbSvMBX0TGqBlYLnzEVWAPvzj PoR2b6C/sp9sMpF/uVF4oaZRdVRd1uCFUeMy2M9QVOFZEV4lqJxIB3BUZMJY1SfO P2mfb8oKdma5HejPN09YidNSk1MSgLWF7HBzTgQAPXLg9Q8UEXlk5jmFiIJbF8/Z uvIpLzYfVpUO2QHy6QKq =lpQG -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: http://lists.debian.org/e1tvyg2-0001jk...@franck.debian.org
Accepted redhat-cluster 3.1.8-1.1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 Jan 2013 21:40:28 +0100 Source: redhat-cluster Binary: redhat-cluster-suite cman liblogthread3 liblogthread-dev libccs3 libccs-dev libccs-perl libcman3 libcman-dev libdlm3 libdlm-dev libdlmcontrol3 libdlmcontrol-dev libfence4 libfence-dev rgmanager Architecture: source all amd64 Version: 3.1.8-1.1 Distribution: unstable Urgency: low Maintainer: Debian HA Maintainers debian-ha-maintain...@lists.alioth.debian.org Changed-By: Salvatore Bonaccorso car...@debian.org Description: cman - Red Hat cluster suite - cluster manager libccs-dev - Red Hat cluster suite - cluster manager development files libccs-perl - Red Hat cluster suite - cluster configuration module libccs3- Red Hat cluster suite - cluster configuration libraries libcman-dev - Red Hat cluster suite - cluster manager development files libcman3 - Red Hat cluster suite - cluster manager libraries libdlm-dev - Red Hat cluster suite - distributed lock manager development file libdlm3- Red Hat cluster suite - distributed lock manager library libdlmcontrol-dev - Red Hat cluster suite - distributed lock manager development file libdlmcontrol3 - Red Hat cluster suite - distributed lock manager library libfence-dev - Red Hat cluster suite - fence server development files libfence4 - Red Hat cluster suite - fence client library liblogthread-dev - Red Hat cluster suite - cluster logging development files liblogthread3 - Red Hat cluster suite - cluster logging libraries redhat-cluster-suite - Red Hat cluster suite - metapackage rgmanager - Red Hat cluster suite - clustered resource group manager Closes: 697870 Changes: redhat-cluster (3.1.8-1.1) unstable; urgency=low . * Non-maintainer upload. * Drop clvm Depends for redhat-cluster-suite binary package. Cluster (clvm) support was dropped in lvm2 source package by removing the clvm binary package. Drop the Depends also in redhat-cluster-suite. (Closes: #697870) Checksums-Sha1: 75a53585b0f9d3d677c1d79b77b0f3ac41429505 3058 redhat-cluster_3.1.8-1.1.dsc 4d03a0d9ee9f04d440a969c83ee8401da8330be4 35502 redhat-cluster_3.1.8-1.1.debian.tar.gz a56f40d2de48cb7dbf4e926741e0e4891edaa1f3 20592 redhat-cluster-suite_3.1.8-1.1_all.deb 35f2632439a4c2e9e6c3c97f8ff447ef4b3184d9 402658 cman_3.1.8-1.1_amd64.deb c2b4f3df24d91837b46642531aa230b966221715 23604 liblogthread3_3.1.8-1.1_amd64.deb d603aa5a4e38de9ca517afdf2dafaeb5d9e55bbc 23054 liblogthread-dev_3.1.8-1.1_amd64.deb 5562d9e50b1abb6105aae8becc4f702936b9c9a3 31234 libccs3_3.1.8-1.1_amd64.deb bd897b61543a0f25e8c6a0db257a80b6831c233c 31844 libccs-dev_3.1.8-1.1_amd64.deb 3457088a6a74bc157d01d357b08f4f6cedcccb30 28766 libccs-perl_3.1.8-1.1_amd64.deb 8a7a560a9cc2696cdbd299f023a26f932636ae8c 27752 libcman3_3.1.8-1.1_amd64.deb fd882ea6ee648b055d8de41ecf7ea6c8bf5595fb 32038 libcman-dev_3.1.8-1.1_amd64.deb fd56af031c99223cad6fd8308e09b3465aecb908 32302 libdlm3_3.1.8-1.1_amd64.deb f93665ed1962c9421ba04bbbae78275fa9f612ea 40012 libdlm-dev_3.1.8-1.1_amd64.deb 8ba2bb5d227b7f645d7320072d2dba341a581cd4 24000 libdlmcontrol3_3.1.8-1.1_amd64.deb fb9556a20d9f4b02c7e2afc3a2332b9e7b6b8559 23946 libdlmcontrol-dev_3.1.8-1.1_amd64.deb 077b1a6783b6128eae2caed3675840fcbe9f84ab 27212 libfence4_3.1.8-1.1_amd64.deb f5f6012cc67a414c025852c8166023495220d578 26602 libfence-dev_3.1.8-1.1_amd64.deb 34f12ce71efb74dc73c571d6f2ecb887aec7eadf 221792 rgmanager_3.1.8-1.1_amd64.deb Checksums-Sha256: 0592542c6fd038002df8a721b8d5676cacb4b5469c6e5b7a7f30750fe4e00f91 3058 redhat-cluster_3.1.8-1.1.dsc ea89f8ce2961704c7676ee104d01b0e5ed1516ff2ee3ac420a2932c03d3c1f19 35502 redhat-cluster_3.1.8-1.1.debian.tar.gz 141398249c2678f97579df82fe5e976b2a8e9565137ffc4f6cfdb418cd175321 20592 redhat-cluster-suite_3.1.8-1.1_all.deb ad567e318898a20a3739a791ff09d578050f0501b769d3941a873e08828a 402658 cman_3.1.8-1.1_amd64.deb 4baeacc2ccd65aa13bd7471717d0ee629b9fe84a9787b7d8f21aebc54dad4e95 23604 liblogthread3_3.1.8-1.1_amd64.deb 21b18356bcee37332f49719f6d76e860cc471e0bb36ed643ce7909adcf944c40 23054 liblogthread-dev_3.1.8-1.1_amd64.deb 95cc69e2fa4b35b9842d7f9ee274ef0611057f43280b117ae30c00b43dc0ec7f 31234 libccs3_3.1.8-1.1_amd64.deb 35deeaddf27279ee97f5e0e777cd1e2f6a50c20f168b35e36f50a4e95bec8b22 31844 libccs-dev_3.1.8-1.1_amd64.deb 5406c34a47262e8c207016525e55c70e8e909799d8e35f88225b54c7f8739e91 28766 libccs-perl_3.1.8-1.1_amd64.deb 5e00a68a9019d2fb04b8a3553faa5da49dfcb383bdd6e352c94520ec5fd7804f 27752 libcman3_3.1.8-1.1_amd64.deb 69dcfa5b2760de071ddf41bed75f9ddc6c3fafa501fa8c88f5ab5ea3ec4c771d 32038 libcman-dev_3.1.8-1.1_amd64.deb 993e8ed5d3064e7bab21c05ddf3d403d36b0a4b4060d48ce380f91a7f46c00e9 32302 libdlm3_3.1.8-1.1_amd64.deb 7dc3e7da52bb03cb40a5701b7fd0171893f0ec7900a1d1554d7ebc1c355fa978 40012 libdlm-dev_3.1.8-1.1_amd64.deb 4d545f254e86f5ae1ca0115e0a8342ec40892454ed3242daea4387424fd6c0a5 24000 libdlmcontrol3_3.1.8-1.1_amd64.deb
Accepted briquolo 0.5.7-6 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Jan 2013 19:01:42 +0100 Source: briquolo Binary: briquolo briquolo-data Architecture: source amd64 all Version: 0.5.7-6 Distribution: unstable Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Markus Koschany a...@gambaru.de Description: briquolo - fast paced 3d Breakout game briquolo-data - data files for the fast paced 3d Breakout game Briquolo Changes: briquolo (0.5.7-6) unstable; urgency=low . * Fix FTBFS on buildd by using .install files and debian/tmp as --destdir. Do not move files around in binary-arch target which are arch independent. Checksums-Sha1: 16160724e7b3e5ce8a7538dc8fbabb914cdefadf 2048 briquolo_0.5.7-6.dsc 244defd37319134c38b678cfa145aa344516bb0c 269 briquolo_0.5.7.orig.tar.gz 40b351b07e0f21e38bd71dfedea3f67f4e8cebeb 12595 briquolo_0.5.7-6.debian.tar.gz 2c914df21fcf6c688a31446767c71cf58fc5416c 219224 briquolo_0.5.7-6_amd64.deb d0c856d74561b21891d3ca4f95788900d482e114 1337338 briquolo-data_0.5.7-6_all.deb Checksums-Sha256: 4c9351087a74b774c4d5f4682920df15c81cfd65b3e194629b983ff49fb3c2b2 2048 briquolo_0.5.7-6.dsc c43c3aa40010a6a54c5c6092fc4b3716478fe47af8f69f54b5f8be99ce9fbbc4 269 briquolo_0.5.7.orig.tar.gz ecc3ead6c9c6aa95e779699256f09a730f22a3fabed5dc0865e2147da28baf7c 12595 briquolo_0.5.7-6.debian.tar.gz 94e89754764e3f35a1abdb9806525ef1c10961aea2445522b169da7bcdde3c38 219224 briquolo_0.5.7-6_amd64.deb a51a0d2eedd46453f34d1c1e99abb46fd7c7e80cb6eba26aa1a66776820504ea 1337338 briquolo-data_0.5.7-6_all.deb Files: 9476f04424cc601fc00bbdee8c043385 2048 games optional briquolo_0.5.7-6.dsc 62dd8c3afcfc51ed264641c92e1372a8 269 games optional briquolo_0.5.7.orig.tar.gz 486b949e5ad65dbd7ea8100a05e50880 12595 games optional briquolo_0.5.7-6.debian.tar.gz 85661811d45731707f5b25b37c672050 219224 games optional briquolo_0.5.7-6_amd64.deb a8be6614ae804a34d89dbabf94d63561 1337338 games optional briquolo-data_0.5.7-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ9wzFAAoJEHQmOzf1tfkTvNUP/1OmRV47XruyHbbBoA1+nami Ny30Agy+gE0a2ou3TsFt1TwflESy9vbxZIwVPSO6SLFiNJohPR48/iGwZ81gM4Ik zVXfHBqL/Q/bwvqR3YGryzq9W9fLNgwbMNF5twOC7eNvR8AGRZMNDH4OkLAFQAXo CJjMwQ1cWnmhKXVsyDMtw6Ib3iWAajtd8/7ZlcSkm7uggo60AWULX3ksEf265YCY LG0qVe2GX7Wrr8IMtzmFgtSXfKrRFl2VzN5Z+XWr6IZKq3rnBLtndTAxbkjssFUA cIaaK5q6NbfLWYu9v7DOvrLaxlhLqeMd7JqqniuoP+8sbexHgoKa7oYBZzQVdIeB L3eM4Ouw+KqDYZ+5L8Pqn4JK4/tijD2NGim9Yo+GwkENFFjslgzCUaaX4iZpNUKd LrApFLUXBhATKsc/ZLrS57tjxo5c7hXC5A/NkqIHrj26IAPccOHn9KVThxvX5dhf 2Q7DlNpewua960ZhrwVCZpukbWwGzC/QpmqTDLcLu3+ED0UJLBCgYKKOV1UW3eNN qoYuDQhqs8PAWHBWw4dQCy1jzYsGSsmS0w9SGLL5nxy/lDyFYNZc4o8jxeP8lhK9 lwRApHWtrys8BpJrVKClDljAiZDpfO7eNMZ4VIhUDxucmnv0Ky0oHwjevCiQwFsR Ngb9KSroSnloTGW3HH6J =AAWD -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: http://lists.debian.org/e1tvztx-0002kn...@franck.debian.org
Accepted libdigest-sha-perl 5.71-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 16 Jan 2013 20:51:48 +0100 Source: libdigest-sha-perl Binary: libdigest-sha-perl Architecture: source amd64 Version: 5.71-2 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Salvatore Bonaccorso car...@debian.org Description: libdigest-sha-perl - Perl extension for SHA-1/224/256/384/512, SHA-512/224 and SHA-512 Closes: 698172 Changes: libdigest-sha-perl (5.71-2) unstable; urgency=low . * Add 698172-fix-double-free-in-load-subroutine.patch patch. Fix double-free when loading Digest::SHA object representing the intermediate SHA state from a file. (Closes: #698172) Checksums-Sha1: a02b590cb9359ba6c23b4b5050a5df17b1afed7b 2210 libdigest-sha-perl_5.71-2.dsc 8725272e6d03a7d3aaf5c46b07b3c7653ec10de6 4797 libdigest-sha-perl_5.71-2.debian.tar.gz 3ca9bf3bf2894f8f0eb3d20d44ca7ed638f290b0 58880 libdigest-sha-perl_5.71-2_amd64.deb Checksums-Sha256: e091472b3beb392437d81b06cc386c9efb440a9d6cd370a6a27c70b09ae9116b 2210 libdigest-sha-perl_5.71-2.dsc fac8a16c2a483c8f3e0eab1489b4c42a0833959cd1a901a36c78af7b85c3e851 4797 libdigest-sha-perl_5.71-2.debian.tar.gz 0da965f6c78d977917e9f1e5ddcfa9105569f01324c8ca408e56e4e4b6c958fd 58880 libdigest-sha-perl_5.71-2_amd64.deb Files: d7e2deeead49e2dd9528f9ac43941991 2210 perl optional libdigest-sha-perl_5.71-2.dsc 96c8ad0504ad4bf4ad44ba87a055eca5 4797 perl optional libdigest-sha-perl_5.71-2.debian.tar.gz c672e1f8706ae2295cce7eef42b5b396 58880 perl optional libdigest-sha-perl_5.71-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQ9wWlAAoJEHidbwV/2GP+084QALFwMRmZJKOOUaNPBUxCiYiE WjMVHKv2MMT8IdO2njyjmCiGgg/xqaXiR+drqCtf+Ftqw6k+lUzC1t58M9q5DjG7 ItaSkwoouJfBHRg94krBZtEwpuxANwp6ge/F+1E8hwEW/G9r60Fme/8NMnFtqZLD lPmzvQf08WR/sHILJc1rn3JZOrOS2cA9RFOgnhvmMeCcf9EBsr5YhUzPhOt3HKEc TFg3fDJkXyA3JgRKWOqgLqEjBV+Z4dPt9hXbqQA0zdaH5fq2nrc2RnO1VAasyyvl b17kgdjPQWtJd9EDtROkjfzFTrcCo4wG/imbLDPtlJdwvOZKRHDy2pcIp9n1k+3N Jc062tACGYtBTELaDbHsf329NjV3cXUEV9GhMziuI6L3NA74UL+BCUfogYQQ7vQ/ V1q2yCjNilRVYGG12fbAuJ7bN5iVf8BDyMFLxcfoE5Ud0V3yVIz9rKSSG9/UWrQs wU9aU64WKrSw3LhS/sjrLLgo9idXlFxjHZahr7/SvLjg24yjigqOGHrWAJ9T5mqM uEGl+I9gaoaaEJHdPiIiAalxgAFRWDeFk0D6WVaCIEaLEZvd3pIKTQpSFu2v9iMu SxPYzmUmj6KscUis7/NsxBVOLd2Pk4jPo+FLEFPmJiYdoLertx4QilO7FBb86lYG G14RjM0XObMByei0p7Qn =I8Kx -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: http://lists.debian.org/e1tvztd-0002om...@franck.debian.org
Accepted nvidia-graphics-drivers 313.18-1 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 16 Jan 2013 21:07:03 +0100
Source: nvidia-graphics-drivers
Binary: nvidia-glx xserver-xorg-video-nvidia nvidia-glx-ia32 libgl1-nvidia-glx
libgl1-nvidia-glx-ia32 nvidia-alternative nvidia-kernel-dkms
nvidia-kernel-source nvidia-vdpau-driver nvidia-vdpau-driver-ia32 nvidia-smi
nvidia-cuda-proxy libcuda1 libcuda1-ia32 libnvidia-compiler
libnvidia-compiler-ia32 libnvcuvid1 libnvidia-ml1 nvidia-opencl-common
nvidia-opencl-icd nvidia-opencl-icd-ia32 nvidia-libopencl1
nvidia-libopencl1-ia32 libgl1-nvidia-alternatives
libgl1-nvidia-alternatives-ia32 libglx-nvidia-alternatives nvidia-detect
Architecture: source i386
Version: 313.18-1
Distribution: experimental
Urgency: low
Maintainer: Debian NVIDIA Maintainers pkg-nvidia-de...@lists.alioth.debian.org
Changed-By: Andreas Beckmann deb...@abeckmann.de
Description:
libcuda1 - NVIDIA CUDA runtime library
libcuda1-ia32 - please switch to multiarch libcuda1:i386
libgl1-nvidia-alternatives - transition libGL.so* diversions to
glx-alternative-nvidia
libgl1-nvidia-alternatives-ia32 - simplifies replacing MESA libGL with GPU
vendor libraries (32-bit
libgl1-nvidia-glx - NVIDIA binary OpenGL libraries${nvidia:LegacyDesc}
libgl1-nvidia-glx-ia32 - please switch to multiarch
libgl1-nvidia${nvidia:Legacy}-glx:i386
libglx-nvidia-alternatives - transition libgl.so diversions to
glx-alternative-nvidia
libnvcuvid1 - NVIDIA CUDA nvcuvid runtime library
libnvidia-compiler - NVIDIA runtime compiler library
libnvidia-compiler-ia32 - please switch to multiarch libnvidia-compiler:i386
libnvidia-ml1 - NVIDIA management library (NVML) runtime library
nvidia-alternative - allows the selection of NVIDIA as GLX provider
nvidia-cuda-proxy - NVIDIA CUDA Proxy
nvidia-detect - NVIDIA GPU detection utility
nvidia-glx - NVIDIA metapackage${nvidia:LegacyDesc}
nvidia-glx-ia32 - NVIDIA 32-bit libraries${nvidia:LegacyDesc} (transitional
package
nvidia-kernel-dkms - NVIDIA binary kernel module DKMS
source${nvidia:LegacyDesc}
nvidia-kernel-source - NVIDIA binary kernel module source${nvidia:LegacyDesc}
nvidia-libopencl1 - NVIDIA OpenCL library
nvidia-libopencl1-ia32 - please switch to multiarch nvidia-libopencl1:i386
nvidia-opencl-common - NVIDIA OpenCL driver
nvidia-opencl-icd - NVIDIA OpenCL ICD
nvidia-opencl-icd-ia32 - please switch to multiarch nvidia-opencl-icd:i386
nvidia-smi - NVIDIA System Management Interface
nvidia-vdpau-driver - NVIDIA vdpau driver
nvidia-vdpau-driver-ia32 - please switch to multiarch nvidia-vdpau-driver:i386
xserver-xorg-video-nvidia - NVIDIA binary Xorg driver${nvidia:LegacyDesc}
Changes:
nvidia-graphics-drivers (313.18-1) experimental; urgency=low
.
* New upstream release 313.18 (2013-01-16).
- Added support in NV-CONTROL and in nvidia-settings for changing the
Double Precision performance boost mode on supported GPUs.
- Fixed several OpenGL driver bugs related to stencil-only framebuffer
objects.
* New upstream beta 313.09 (2012-12-11).
- Updated the NVIDIA X driver to reprobe displays when VT-switching to
X, to allow reporting of hotplug events when displays are connected
or disconnected while VT-switched away from X.
- Added unofficial GLX protocol support (i.e for GLX indirect rendering)
for the following extension and core commands.
GL_ARB_vertex_array_object
OpenGL 3.0 commands ClearBufferfi, ClearBufferfv, ClearBufferiv,
ClearBufferuiv and GetStringi.
- Fixed a bug that caused the cursor shadow to be clipped to 32x32
pixels, even on Kepler GPUs that support a 256x256 cursor image.
- Fixed a bug that prevented some cursor image updates from taking
effect on displays with rotation or other transformations applied.
- Fixed cursor alpha blending artifacts on displays with rotation
or other transformations applied.
- Added support for the GLX_EXT_buffer_age extension.
- Improved the performance of glDrawPixels() by up to 450% when the pixel
data is of type GL_BYTE.
* New upstream release 310 series.
- Fixed a bug when enabling framelock between displays connected to
the same GPU as other displays with different refresh rates, which
caused the latter to be incorrectly assigned to the framelock group.
- Updated the reporting of HDMI 3D framerates and pixel clocks to be
more consistent with how they are reported by HDMI 3D displays.
- Fixed a bug that sometimes prevented rotation controls in the nvidia-
settings control panel from working after changing resolutions.
- Fixed a bug that could cause applications using GL_NV_vdpau_interop
to crash during modeswitches.
- Fixed a regression that could cause OpenGL applications to crash
while compiling shaders.
- Added a kernel module parameter, NVreg_EnablePCIeGen3, which can be
used to enable PCIe gen 3
Accepted tandem-mass 20121001-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 21:26:08 +0100 Source: tandem-mass Binary: tandem-mass Architecture: source amd64 Version: 20121001-2 Distribution: unstable Urgency: low Maintainer: The Debichem Group debichem-de...@lists.alioth.debian.org Changed-By: Filippo Rusconi lopi...@debian.org Description: tandem-mass - mass spectrometry software for protein identification Closes: 695553 Changes: tandem-mass (20121001-2) unstable; urgency=low . * Fix the target build-stamp by adding the $(QUILT_STAMPFN) dependency. This missing dependency seemingly caused problems in Ubuntu (as reported by Tim Gardner tim.gard...@canonical.com; Closes: #695553). Thanks Tim. Checksums-Sha1: b7603c1874319b99a7d054bd377f08f7b1011880 1401 tandem-mass_20121001-2.dsc 050741cb4161815102bff703ac83c68a07c04b7c 4744 tandem-mass_20121001-2.debian.tar.gz 5b4f9e70be03a893ec51c56c1c18dc15dd098d0b 227058 tandem-mass_20121001-2_amd64.deb Checksums-Sha256: 519def03197bc8abd81d1e9e786b7981cea8ecff160544ab76b2c62ad15761b4 1401 tandem-mass_20121001-2.dsc 486030945e5d8d5f7d1390b9207fe084d57283ca13d9a41e80115c4aff0efa5c 4744 tandem-mass_20121001-2.debian.tar.gz 1cd61040188f0c97d9a77666073ba6e4ef2aa80e6d0b53cf4b03a4045464f344 227058 tandem-mass_20121001-2_amd64.deb Files: 164d1f7fd61aee1c10f583814b8822a7 1401 science optional tandem-mass_20121001-2.dsc 5620e41bd50ceca32513251de00125a1 4744 science optional tandem-mass_20121001-2.debian.tar.gz e8ffec516449c61ae7dcbe62177cbba4 227058 science optional tandem-mass_20121001-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD3DgwACgkQTTOs5MePaHySjwCcD3wzLNrKeHhFDNHPMl2LRS/O r4gAn0ObYK3OnR8/tVr8EFLyEOh7VpFX =2Auo -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: http://lists.debian.org/e1tvzv9-00038k...@franck.debian.org
Accepted nvidia-settings 313.18-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Jan 2013 21:44:29 +0100 Source: nvidia-settings Binary: nvidia-settings libxnvctrl0 libxnvctrl-dev Architecture: source i386 Version: 313.18-1 Distribution: experimental Urgency: low Maintainer: Debian NVIDIA Maintainers pkg-nvidia-de...@lists.alioth.debian.org Changed-By: Andreas Beckmann deb...@abeckmann.de Description: libxnvctrl-dev - NV-CONTROL X extension (development files) libxnvctrl0 - NV-CONTROL X extension (runtime library) nvidia-settings - Tool for configuring the NVIDIA graphics driver Changes: nvidia-settings (313.18-1) experimental; urgency=low . * New upstream release 313.18. - Added support in NV-CONTROL and in nvidia-settings for changing the Double Precision performance boost mode on supported GPUs. - Fixed a bug in nvidia-settings that allowed unavailable features to be selected in some drop-down menus. * New upstream release 310 series. - Fixed a bug that sometimes prevented rotation controls in the nvidia- settings control panel from working after changing resolutions. - Fixed a bug in nvidia-settings that could cause the wrong resolution to be set in basic mode for setups based on one display per X screen. * Update symbols control files. Checksums-Sha1: 2a4718c04a8604a7c94020824a0022786f267abc 2347 nvidia-settings_313.18-1.dsc c188adfda6785ddc57ecbc45e2a381468fb0254b 1494889 nvidia-settings_313.18.orig.tar.bz2 95a8eb35f30653e1b20e9fefcb21dc538d9c04a7 15326 nvidia-settings_313.18-1.debian.tar.gz d5b0dd0916cdfecd1cd970df47ee46dd766d3fd3 829206 nvidia-settings_313.18-1_i386.deb ffc5d6ef015f53e791600508b7d06646c5e79fe8 17218 libxnvctrl0_313.18-1_i386.deb a05ab054193f8a891a35133e4d6dbee472ed58ec 98656 libxnvctrl-dev_313.18-1_i386.deb Checksums-Sha256: ea86fe33a05caab9ca7892f927dc01e05148119dd12ac6ce7eaf6e7ae971d241 2347 nvidia-settings_313.18-1.dsc f7f5523e708c51b13c81a66f2432014df2f6e1344618baa33176ad8d224e2c01 1494889 nvidia-settings_313.18.orig.tar.bz2 ce5783182025f66005841b4efb34f351fed18d244bb040f997bdc9a2563eb87f 15326 nvidia-settings_313.18-1.debian.tar.gz 45225c715cdabc82a4fdad843281772ea689040f4e815a6ef26245900631f992 829206 nvidia-settings_313.18-1_i386.deb e365e5b757526a2ce239b59de897af66911f9d67cd6711e5832d752e23025031 17218 libxnvctrl0_313.18-1_i386.deb cc49f9804d1cf2fb6437f901829966852cf8ec845862eb8b28c2c523f165b5de 98656 libxnvctrl-dev_313.18-1_i386.deb Files: 96a48a24e5e210bb9c5161b1712afc08 2347 contrib/x11 optional nvidia-settings_313.18-1.dsc 441a3130816a1906e719539b8e494376 1494889 contrib/x11 optional nvidia-settings_313.18.orig.tar.bz2 74af5287c6cd2d9302cd1248ad4b370f 15326 contrib/x11 optional nvidia-settings_313.18-1.debian.tar.gz c692069a776af76fc2742eee3e1d0c7c 829206 contrib/x11 optional nvidia-settings_313.18-1_i386.deb da44b29a368e9fe445d51d7508e8e1f4 17218 contrib/libs optional libxnvctrl0_313.18-1_i386.deb 387d0eb3cba003d2ddc19e721a65cb51 98656 contrib/libdevel optional libxnvctrl-dev_313.18-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ9xH+AAoJEF+zP5NZ6e0IbHwP/0J64UUkI6vCombkwYLBF9BT 8nypRixVH3RXCpWB1GtSXmVd2ggyTXG+ZqzSBrDBW3+vcsBE0N1wL41RYWA582bm 1TA2ssTFvJy8SKovXs4zmFtxJx+fKCG8D1sTmmDBote83CGboyiFc2aBSNd+jPe8 T4S13EyqcDWC4ZzADwnBqJwobw+KmbG8s+ocweIUHMxA8djyzfjEQfVa4hNpp/xn /Fdpbd1HzB5FwwWgk7M/3Yn5X3KLVZ/6h9cRjxIK0cIUQ1ssRjuAYHT9opsDRjND wBBWq1LAs5QDDkzGWmyyQHInVxputMRryHSBovP2Ey4K14zgAERGIGBD42R4D/Ah MwKZaEzhKJotUU+vzxTxbvLERU9wQNADzpIOfInyME0SuJvypjfhkxRwZ/GevYWx mASbT1o7ZH6Ql5ElAR1uu27yqUeHm5DMcCUQ7kQrtIoL3L4JBON/T48GBsj1HWOc 4IyOGY2B5gMzW5/NFMTc+4WUw5et5uHPktre65DaAzYcm8MtsQsM9NzC63kLqYAq sbxxX4es0iBX2LDkX5XBjaG3TdIdVhWT1TqjnilqVEauD8bCrL3My4AsnTEbzXAx 0t4dC0u3sa/ImQxb5e6tHyOT1o9eGJPDmVxUnji/4BJKymmpiuV5EUdhBnQv5PNz 1OcImh4/L58NspNyUznZ =QzHL -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: http://lists.debian.org/e1tva84-0005vs...@franck.debian.org
Accepted libthrift-java 0.9.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 15 Jan 2013 02:01:50 + Source: libthrift-java Binary: libthrift-java Architecture: source all Version: 0.9.0-1 Distribution: unstable Urgency: low Maintainer: Eric Evans eev...@debian.org Changed-By: Eric Evans eev...@debian.org Description: libthrift-java - Java language support for Thrift Changes: libthrift-java (0.9.0-1) unstable; urgency=low . * New upstream release. Checksums-Sha1: b7c7b107dc2c95be25ce191ba7908eaa7bb7d365 1403 libthrift-java_0.9.0-1.dsc fa4ff2f8190e2c4210867d3d6ed1a1979b334045 123014 libthrift-java_0.9.0.orig.tar.gz 298aeb851164f44d81365be8b0af0ee7b3c6f5ef 1885 libthrift-java_0.9.0-1.diff.gz e1f00eee8526237a4e0e6d4b4e498f733431946d 348542 libthrift-java_0.9.0-1_all.deb Checksums-Sha256: 9decbb545b22c284366954a9fffe91d74e603ce9914c66c8fc2bd527a45c8ab2 1403 libthrift-java_0.9.0-1.dsc 2f974ab98deb1c7786f1c87d97023e025a1a64046457e42345886ef8c5bd6f46 123014 libthrift-java_0.9.0.orig.tar.gz 876814c55f1b833953def8734ea007ce64fdf93992dba40733651ea5549a6612 1885 libthrift-java_0.9.0-1.diff.gz c3a47d3097344e3dffb9acc538a791cc2e4187378aba636b2f581b9edbffc2c4 348542 libthrift-java_0.9.0-1_all.deb Files: f6ad96f021928001612fa4859b1f0c12 1403 java extra libthrift-java_0.9.0-1.dsc 079c7baef9f562c43fa843580d4ffb2c 123014 java extra libthrift-java_0.9.0.orig.tar.gz eb9b665c95f899b038b0c71f4b4b75ed 1885 java extra libthrift-java_0.9.0-1.diff.gz 3e180788b23f82521b7357cdc9bf612a 348542 java extra libthrift-java_0.9.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD3Fg8ACgkQ+DWPovKDPJOVUQCcD6myDOvsFLpyhnhtmFm5swxo AWEAoJEL4wyF32Xj5KhCsCZPWzwzdzkx =9zIM -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: http://lists.debian.org/e1tvamg-gw...@franck.debian.org
Accepted python-thrift 0.9.0-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 15 Jan 2013 01:55:02 + Source: python-thrift Binary: python-thrift Architecture: source amd64 Version: 0.9.0-1 Distribution: unstable Urgency: low Maintainer: Eric Evans eev...@debian.org Changed-By: Eric Evans eev...@debian.org Description: python-thrift - Python library for Thrift Changes: python-thrift (0.9.0-1) unstable; urgency=low . * New upstream release. Checksums-Sha1: 8f2aafd82a36e403a3b3b67f87540c6252cf9892 1251 python-thrift_0.9.0-1.dsc 66cd1e1337157b0694b310590a7a6f3b05932128 41384 python-thrift_0.9.0.orig.tar.gz 7592ebbaff3c2bd1d41ea1820b4c33146d15755d 2492 python-thrift_0.9.0-1.diff.gz bb1bb4e2e81f7b2eb9a19264cba80ec093117231 36562 python-thrift_0.9.0-1_amd64.deb Checksums-Sha256: ccfb4c54ad72a31c48f89ce2dd943bc3da61eb04715fc5e666d246ea5ff88132 1251 python-thrift_0.9.0-1.dsc b56efdff445561842241e1b575ff49eac40ae277b5a0aa75d7478cc513f460be 41384 python-thrift_0.9.0.orig.tar.gz c10357c84a338c8f591b87d54753325f210c2508c4665518e848bfebc5cb8189 2492 python-thrift_0.9.0-1.diff.gz 54d482ee54b796e19dc5e935a11d073f8f2286d1a034a62671ed9bec9d7e18ca 36562 python-thrift_0.9.0-1_amd64.deb Files: 370975059e5ba997eafc41d924f10545 1251 devel extra python-thrift_0.9.0-1.dsc e4a5656c9bbf2f53d12fe25f48e038ff 41384 devel extra python-thrift_0.9.0.orig.tar.gz 38dcb7f8674220ea83d56d5bc63af262 2492 devel extra python-thrift_0.9.0-1.diff.gz 66e629fa5b5e71af64d91cd2e56c24da 36562 python extra python-thrift_0.9.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD3FhgACgkQ+DWPovKDPJNe3wCgmrZ/xyGOq64++Fax7GbrLa7b SYoAn12UDMcB6vZgNJpl5vlX0X9CvgUv =zRZf -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: http://lists.debian.org/e1tvamu-tk...@franck.debian.org
Accepted shelldap 0.7-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 16 Jan 2013 22:02:29 +0100 Source: shelldap Binary: shelldap Architecture: source all Version: 0.7-1 Distribution: experimental Urgency: low Maintainer: Salvatore Bonaccorso car...@debian.org Changed-By: Salvatore Bonaccorso car...@debian.org Description: shelldap - shell-like interface for browsing LDAP servers and editing their Changes: shelldap (0.7-1) experimental; urgency=low . * Imported Upstream version 0.7 * Update debian/copyright information. Update copyright years for upstream files and for debian/* packaging files. * Drop fix-for-conversion-path-to-dn.patch patch. Patch included in version 0.7. * Drop 0001-Take-only-second-argument-for-run_-cd-edit-mkdir.patch patch. Patch is included in version 0.7. Checksums-Sha1: ae820106623a779a7cf82b0d730f40b7d5105247 1722 shelldap_0.7-1.dsc 98349e6c55913952b3ab28c3d26107f3cac79f31 19764 shelldap_0.7.orig.tar.gz 272afdfd36e4e5f815d748b2329411cae88d3b1f 3384 shelldap_0.7-1.debian.tar.gz 291376d2e194e194ca80b3b335c70057dc2d2582 26446 shelldap_0.7-1_all.deb Checksums-Sha256: 05ecf1c1d5d1a8f3431fcaa6ef11e56ca6e138c1cf6dfebcde3cba612f4e02c6 1722 shelldap_0.7-1.dsc 0e8ce24b608df5799ce93dc94a90d6870ec296a31ee5cb7b6f7039ee82250382 19764 shelldap_0.7.orig.tar.gz 73c0246ae9a28da2e837f5baa6a45b96900850fc975419d586a4bb1317118733 3384 shelldap_0.7-1.debian.tar.gz a0e28440c0757c2b7f93e7cfb5845cdec645238607595fdb02024f7ac8dd3cce 26446 shelldap_0.7-1_all.deb Files: de0155378de320f105b43e474707fd95 1722 utils optional shelldap_0.7-1.dsc 56975cede4a40ad5afe41ebba93d8db5 19764 utils optional shelldap_0.7.orig.tar.gz d6f70a6cb462035b9d9378302c03fd79 3384 utils optional shelldap_0.7-1.debian.tar.gz b4f38a68490c2a6cd2f834778e82e951 26446 utils optional shelldap_0.7-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQ9xbzAAoJEHidbwV/2GP+4wQQANRFGfpPce0NBIia1094UvkM soxsswbrSeLrf55Ep+/9Qw5GTF4PEOGOqlNo4dwKEeBstkeVxSjtiUiJPEdrpfW1 VmbXh2CRXdr0UXi+0a9+vZyaMPszucp/UmMBlfbGxZQ6f37Myips1by4iu/PqWMK iSHOnCXC+0QRjfpSHlWY2KVQVFy7lMP2CVTeQvpBZ5r1Hsx4fjYfL6G937Ioi+6n eEt9OMsRtmsI6mKSUt7kPaGJ0HbroyZMvLaTgYJq1gTKs7j1PLAJRbQWtz5bIBeQ 4NkKDVOpK0iX2tfuNVfUnzaXfV0i50yr8GRntmMiyQHc+0IRYB5JV1+9M/R5jFYX wNBKxGtWefWVu0uAmSKAzoOR+1xcYuX11v0zqG+NIuQqH2kglTgaaCfnOGo/noPL iNEv/q07VZPk8PQ5k76faIQqpVhwSbFsx4PEbIOftyGjgTaQd1DamNCYgk6J4My2 DDJT1WZe7HQs/ITRYhvxKt0zzhw+h3N12tPB8UrWKGhiYo67ktBH7CH22w+DijMH Nu4x8z674A4TTtKWG0LVA0klL5YIWU2N0y93KPTnDvfyqLBb4AjgZx1/j9dHAIg1 mO5iABnUAJxvPAmgjL04Rt2xUJGYe1qbHQ4EFus84txfAJ+nqUxM6yfqi8EQHteN Vzt+JLDK6eIIQbBGyGQ1 =QPjb -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: http://lists.debian.org/e1tvamz-w4...@franck.debian.org
Accepted thrift-compiler 0.9.0-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 15 Jan 2013 01:35:51 + Source: thrift-compiler Binary: thrift-compiler Architecture: source amd64 Version: 0.9.0-1 Distribution: unstable Urgency: low Maintainer: Eric Evans eev...@debian.org Changed-By: Eric Evans eev...@debian.org Description: thrift-compiler - code generator/compiler for Thrift definitions Changes: thrift-compiler (0.9.0-1) unstable; urgency=low . * New upstream release. Checksums-Sha1: edc530a72d806ee7a728f98a18e3c0b58fc15cc3 1278 thrift-compiler_0.9.0-1.dsc 024c7a6dbaeb85960d9921a69ef2200ff2fbb8a4 312987 thrift-compiler_0.9.0.orig.tar.gz 67272c3b8325735342c589189d02c02afdd163e9 3136 thrift-compiler_0.9.0-1.diff.gz 6613abdcb5e02f5a5f690cbaad4a93da18a508ba 857042 thrift-compiler_0.9.0-1_amd64.deb Checksums-Sha256: 5c4417945b7f868dd4eb816c95ef6a3ce6db917b2f9f2b6ccdb5e203a0d4a8c1 1278 thrift-compiler_0.9.0-1.dsc 59c128a12c4890c2a156dee4e81850eebc911b70edbb4ea057c419a4aa62f336 312987 thrift-compiler_0.9.0.orig.tar.gz fd8c2830bbd79275ac56cc7c87511121d32f03c0d63c4f5bd3e77c1bb848bf21 3136 thrift-compiler_0.9.0-1.diff.gz 3c4eb82f1f46de16bbb60cab52de13e5cdc0a327692e7c921e79cbceba9fd737 857042 thrift-compiler_0.9.0-1_amd64.deb Files: 5162423051e506e3ef8ba41a54bbf470 1278 devel extra thrift-compiler_0.9.0-1.dsc 0e01b4439e55b7c23305048be19e897a 312987 devel extra thrift-compiler_0.9.0.orig.tar.gz e36628a3f2c4e195d5b39c31eb594333 3136 devel extra thrift-compiler_0.9.0-1.diff.gz 7764ae738aea38dfcee587733aa4585b 857042 devel extra thrift-compiler_0.9.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlD3Fh4ACgkQ+DWPovKDPJPFpgCdF4GA8eOhCt0MBrPTZjHsNbko k2EAn3wQc9B07890f/87TDYvJygcPE+e =hyXj -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: http://lists.debian.org/e1tvan5-zg...@franck.debian.org
Accepted sanlock 2.2-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 03 Jan 2013 22:12:33 +0100 Source: sanlock Binary: sanlock libsanlock-client1 libsanlock-dev Architecture: source amd64 Version: 2.2-2 Distribution: unstable Urgency: low Maintainer: David Weber w...@munzinger.de Changed-By: David Weber w...@munzinger.de Description: libsanlock-client1 - shared storage lock manager (client library) libsanlock-dev - shared storage lock manager (development files) sanlock- shared storage lock manager Closes: 689696 696424 Changes: sanlock (2.2-2) unstable; urgency=low . * Fix CVE-2012-5638 sanlock world writable /var/log/sanlock.log. Thanks to Salvatore Bonaccorso (Closes: #696424) Add patches cherry-picked from git repository: - 0001-sanlock-remove-umask-0.patch - 0001-sanlock-use-lockfile-mode-644.patch - 0001-wdmd-use-lockfile-mode-644.patch * Replace restrict field name (Closes: #689696) Add patch cherry-picked from git repository: - restrict.patch Checksums-Sha1: a205e34a5ef2e387f7e511978c1e2fc1619eebc2 1825 sanlock_2.2-2.dsc 311da627f0daf4ec4aaa1bede5a8b795532669ac 9410 sanlock_2.2-2.debian.tar.gz b29a37da4c85842437340efd14b6d46da758eb1b 112110 sanlock_2.2-2_amd64.deb 647bc244a0cc8ba69e8833b80908dd7453153637 9698 libsanlock-client1_2.2-2_amd64.deb c578a8120a3d9ead344074020f3268c2a5375435 5858 libsanlock-dev_2.2-2_amd64.deb Checksums-Sha256: 1a68c41bebf077e9dc98df73f1a702ccd50fb1a3c5eba8c0f06e71d01ae6b221 1825 sanlock_2.2-2.dsc d792c8e5b709df190ef9897164d84013905ab4fa221c51ed8c83410c5bd9ec3f 9410 sanlock_2.2-2.debian.tar.gz 7674e4b376e02910d7dba21866ac73cfca62714622ca2aa583e68cc60163f9f6 112110 sanlock_2.2-2_amd64.deb a10b24546e4866b10c5e5fe12c6bcf36ee5b98b055316df583c1179dfd3fad47 9698 libsanlock-client1_2.2-2_amd64.deb 0743507745b851e9fc1b9b31c2c4c5cd5617967277b30ca991572cf8c540d40a 5858 libsanlock-dev_2.2-2_amd64.deb Files: 57d7b01349eb07741723f1cdcdc7acd0 1825 libs optional sanlock_2.2-2.dsc 1a13a28e0cda2e5365561453b0716479 9410 libs optional sanlock_2.2-2.debian.tar.gz 53acb0f2df3e5506bedcb69e497e3a09 112110 libs optional sanlock_2.2-2_amd64.deb 32aa85948df25bfd304f3f94e814834b 9698 libs optional libsanlock-client1_2.2-2_amd64.deb 0153758bad90eedbc07981bfd6ca81ef 5858 libdevel optional libsanlock-dev_2.2-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJQ9xxxAAoJEHidbwV/2GP+xcAP/31GvUkcsHQVRZNpvDp6lcOE dOi2wIwR6hLcVHdHCEK6juLq1fNTkEBzbbJdFla0ktWutxBSt6hH9KOU1YvIv0Cb sFevf9ik45Vd57i8O7V1CNq/+wVBS9PkEti+KxIMYyBj/o0bcIWglcLZCm77uWhG B53p8+psAWGcIosh/DpJz+dba/Wqui0/1vDzjgvww6edsEG4MG3CKezMnKQZaavw lV37TJ5Yq9jGn11vbpzeqReKGvTtYBilJPwxWEkp+ptSAifSQPE62xJ0E6boWqCw DCQz3DtbBEQU8731VhD85Hwg9OIotO7rHkGeiEblSlkT6uGPAJt1ctAdxldOWt9v XbUXKuZ10HKC/O/R9/pEqQSPy7kkvX/DI7p5zf+ZhNHASTJ8ynPPcMlsXBVtoe+R nN2kxGGUh5s4wR9rzF5ZxOj+zd8U5zB6JSUc+LZrZh4DxFuqVV6X3s4YT/rkenJg jZpljGGWTsyeXGx2W3WCzEuJ+vb/QrZ/BnWpoJVUBAAY65toS/4+McaXhBMfHvD9 5GSl9fP/dHafxFqzst1TSmJH04PoMYnVdImZquitJVxp4P2Rf0kgZykgPAG+idFK q3gxNZwD0kfi0eaWUSW6EjAITZk384GxfkH8PgUqRA0nU17SIgOATP6aJUSaKLLI eyq3iuYuDrPIZxU/M9Mn =dCPq -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: http://lists.debian.org/e1tvaqd-0006pq...@franck.debian.org
Accepted rcmdr 1.9-3-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 15:55:32 -0600 Source: rcmdr Binary: r-cran-rcmdr Architecture: source i386 Version: 1.9-3-1 Distribution: unstable Urgency: low Maintainer: Dirk Eddelbuettel e...@debian.org Changed-By: Dirk Eddelbuettel e...@debian.org Description: r-cran-rcmdr - GNU R platform-independent basic-statistics GUI Changes: rcmdr (1.9-3-1) unstable; urgency=low . * New upstream release . * debian/control: Set Build-Depends: to current R version Checksums-Sha1: 6513128f2d91959a1f745da8996959716b946a48 1035 rcmdr_1.9-3-1.dsc 2c484549a11d9ed660b8a833612da212aa1282f5 3400017 rcmdr_1.9-3.orig.tar.gz 8c62284e677c282056896f1a966c50fb43091c8f 5637 rcmdr_1.9-3-1.diff.gz c1eefa01a86549385fe42ad3620008cb17a5679f 3762960 r-cran-rcmdr_1.9-3-1_i386.deb Checksums-Sha256: 8d55cda30aa7616c93d19c17e7334731c78abda94f691b83ce59e9f3f689f6dc 1035 rcmdr_1.9-3-1.dsc acb331bb9b9a3b9bb13cf78b2469436b6952d85fa195a9737d909862f6a1602a 3400017 rcmdr_1.9-3.orig.tar.gz 7f14bc83109c2d905512c8dcbff1b8b433731144b71d2dd988b9e724421d61bc 5637 rcmdr_1.9-3-1.diff.gz 7e52e7200bfbdb807e04ad11905f35bdf8e05bf932f020c7bd57ae4654fa5b92 3762960 r-cran-rcmdr_1.9-3-1_i386.deb Files: cf95e126433b17150b4ef95409fa8f51 1035 gnu-r optional rcmdr_1.9-3-1.dsc 309095f069af405c24c2559b2e7617f1 3400017 gnu-r optional rcmdr_1.9-3.orig.tar.gz 58673a7ae0954119de7fb3e6309bb1b9 5637 gnu-r optional rcmdr_1.9-3-1.diff.gz 8cb97c0272f44ff5610c440ee9d7fd39 3762960 gnu-r optional r-cran-rcmdr_1.9-3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iD8DBQFQ9yIYCZSR95Gw07cRAqDaAJ9iX/9OPP8XmwWqUqTRBiIaZrF4igCeNcc5 8Yp+HsLZsaFHjthDQ17Md+8= =kUIU -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: http://lists.debian.org/e1tvb45-0001ky...@franck.debian.org
Accepted openyahtzee 1.9.1-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 09 Nov 2012 21:04:16 +0100 Source: openyahtzee Binary: openyahtzee Architecture: source amd64 Version: 1.9.1-2 Distribution: unstable Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Markus Koschany a...@gambaru.de Description: openyahtzee - classic dice game of Yahtzee Closes: 544935 Changes: openyahtzee (1.9.1-2) unstable; urgency=low . * New Maintainer. (Closes: #544935) * debian/control: - Change Priority from extra to optional. - New Standards-Version 3.9.4, no changes needed. - Update Vcs-fields. Now Open Yahtzee is maintained in a git repository. * Update debian/copyright to copyright format 1.0. * debian/rules: - Build with hardening=+all. - Build with --as-needed to avoid unnecessary dependencies. - Remove autotools_dev addon because autoreconf does the job just as well. * Bump compat level to 9 and require debhelper (=9) to use automatic hardening build flags. Checksums-Sha1: f3768a3724db7c8cfd368204974f913f3daa9091 2020 openyahtzee_1.9.1-2.dsc 7d3c4ff4ce5aa38594e40514a072942141d4bedd 159149 openyahtzee_1.9.1.orig.tar.bz2 dabde264865a339090db00e43d1bc91fabe5a83b 2848 openyahtzee_1.9.1-2.debian.tar.gz 3137aa005f234f2c2de27595ac3f8803b0d2716a 184918 openyahtzee_1.9.1-2_amd64.deb Checksums-Sha256: a1b6003e67feeae326caf7a101c926aeccc3e19c222b6c6acefee6d1e1c6 2020 openyahtzee_1.9.1-2.dsc aa553a248d30ba259abb8dee735d5728bfdbb8d4705805bc716453245f1cb0a0 159149 openyahtzee_1.9.1.orig.tar.bz2 d9a8b2c1b4fd5dbc842e291b612fec4ea325b372c0695f37b542f0c1875a05fe 2848 openyahtzee_1.9.1-2.debian.tar.gz 27b67eb53766d7f0d3ad829ca09ceb839d3c8c2286d6e483f36536f1641dd3af 184918 openyahtzee_1.9.1-2_amd64.deb Files: 9386a6b057233b6be97e6855e9c4012b 2020 games optional openyahtzee_1.9.1-2.dsc b45d42abe3f62741043e59d2ba9b83e9 159149 games optional openyahtzee_1.9.1.orig.tar.bz2 a34dbf75a17a26733ff0619467c53a59 2848 games optional openyahtzee_1.9.1-2.debian.tar.gz a07e9c98801c15ed53e8f3aef8b888df 184918 games optional openyahtzee_1.9.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ9yOUAAoJEHQmOzf1tfkTJyoP/iEkvUKTeyowGvrS+8AiW5hP fj8gr/uIa6U94qCZ117cG6Qfx6Q6bq1Otiu2SKWgFOx3v9pEDA6hYTiR1Ct//GT+ oD7XxU9ou0e+GK0mriN8WudZTjohkXF4EDaA9V5GjFrEcHlwuAlV7n8Kzfa6b7xS V/v7jg4oBRX0BxE22cqOvUOUS3XBQ5t/K0drR0ujQE6dgjbdNglj9FCx7nFxb3Go 8GYj63D0xLbgQm1XXrrungKNwPg3/mhVEakXxGr8EIafto/SsnkH7v+s8rSOCHK3 JyXMxS6GNd4X57eetoJaVIU5tGX1FIU4+ftnH/vVUdHtKophgBPeBpKf8r7+LZ0u ZX6fFVkJbnVT6iNWgi4UEu9x8y6b7oqplFs7z/Lo5srG2g/VKwLVN/DsenaM8MWw aB5Um/BhzYhHsl2ACKaCMkT9Kdp5/Uw4dYjdF7zDJDX4LTKfC4vSpfzt0k730h2p hqnBfCSFlt9B6p9+weDeFaLF0rkaXYVmppCqzb7vighPwtC/h3/3V9bJyJneeUi2 7BxzA0eAAXbn+MKIQ29CGzqLWER4zyjSIJgo6T6SGMwqgMGVXYAQrbvYVuAFxr1I K79QXKNutufGspDVmwu+TOgW4XkDouzAvBE78kP+GYQxwPWBFeOANvXQ4iiHSfgG vYQXtQPs9sdz2pFVe7x6 =ysdU -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: http://lists.debian.org/e1tvbin-0004xy...@franck.debian.org
Accepted etw 3.6+svn162-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 05 Jan 2013 10:27:47 +0100 Source: etw Binary: etw etw-data Architecture: source amd64 all Version: 3.6+svn162-1 Distribution: unstable Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Markus Koschany a...@gambaru.de Description: etw- arcade-style soccer game etw-data - graphics and audio data for etw Closes: 693949 Changes: etw (3.6+svn162-1) unstable; urgency=low . * New upstream SVN snapshot. - Mostly code cleanup, small bug fixes and renaming of italian variables. * Switch to package format 3.0 (quilt). * debian/patches: - Drop changelog patch. A changelog was never installed. - Refresh all other patches, drop patch numbers and prepare Makefile.linux for hardening. - Add Fix-conflicting-types-for-drawtext-declaration.patch which fixes a FTBFS. * debian/control: - Drop superfluous quilt dependency. - Drop sharutils dependency. In version 3.6 we don't need it anymore to fix bug #335719. - New Standards-Version: 3.9.4. * Bump compat level to 9 and change requirement for debhelper to = 9. * Update README.Debian and point to upstream's EatTheWhistle.txt which has been renamed to README. It contains additional and more useful information. * Update debian/copyright to copyright format 1.0. * Update etw's manpage. * Remove postinst and preinst script. Keep it simple and less error-prone. * Add etw.png icon and install etw.xpm only to /usr/share/pixmaps. * Update desktop and menu file and add German comments. * debian/rules: - Simplify debian/rules by using dh sequencer. - Update get-orig-source target. - Build with dh --parallel. - Fix FTBFS with binutils-gold and add -lm to LDFLAGS. (Closes: #693949) * Build with Wl, --as-needed to avoid unnecessary dependencies. * Partially build with hardening build flags. Unfortunately enabling all hardening features makes the game unusable. * Update watch file. Checksums-Sha1: da53b5ee22cfa4968178363bfd0a96ef3a4eac1e 1965 etw_3.6+svn162-1.dsc e396a5dce81168c4b17eb9c2450b11f9989ba766 9205100 etw_3.6+svn162.orig.tar.gz db7fe48ec5413713bd673df9839b4cf981a29716 11141 etw_3.6+svn162-1.debian.tar.gz 79fffed2b30e524670a78ed753e32d04990ac845 212582 etw_3.6+svn162-1_amd64.deb f2f22c8ae45931f888925431b831fa4633589303 8052618 etw-data_3.6+svn162-1_all.deb Checksums-Sha256: cad132187580c0bb56fdd70333ea3c2e687b30cd61005b53910026107d82f1ac 1965 etw_3.6+svn162-1.dsc 147e7e0136d2411ed3155bc9f57aea3e6f3fd428e667265a4d19590d0a95cbc6 9205100 etw_3.6+svn162.orig.tar.gz 5a04fc591c32ed044907a6c1af93f533f456e30166d67c88ee86f75f78e9992d 11141 etw_3.6+svn162-1.debian.tar.gz 85261949e2ec1a2a9eac23a82185fb3e77e80dcac01afba4a18f0ec3f63eb611 212582 etw_3.6+svn162-1_amd64.deb 162fceb1d16142499a1a0013da8e64134d045cddeb85bfe897ce053b8e050ae8 8052618 etw-data_3.6+svn162-1_all.deb Files: bf25c457e70c4482a608ee8fd09124e8 1965 games optional etw_3.6+svn162-1.dsc 9acac9aa2d433ea9eb02df0a3f276640 9205100 games optional etw_3.6+svn162.orig.tar.gz 12fac505f34e05001576633e0c306abd 11141 games optional etw_3.6+svn162-1.debian.tar.gz bc65a0a49325254e985cbbad63284b85 212582 games optional etw_3.6+svn162-1_amd64.deb 9c81b337f23533e2501aabc47e2ea85a 8052618 games optional etw-data_3.6+svn162-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ9ydKAAoJEHQmOzf1tfkTKz0P+gMELaLNk203n8euryaW7jGV jGO6f/m9qw8hJHCijTFZwljbyXm6po+Tm+bK5GP8VbigWDPbDO0qeCrDaV5bzJDD SrbOFkhSqNM88nwXiM1fMHbWn65rqprICRAa62TbEk8izp2JYU1rlJ+AX9HWRP1v P+SP6vFIKaLsoTjLERvhpCcadUg2Trn5t/CYmCnJHLGhzzg855coRXJA0EDMExtK vN0ol6sFlrxBDaSZanBzWT8ea4TGFgk3xVzA4hbVelg/TM8aAGO+Q68OggO4gpIl 3g2m1vxyqOibZkTHxTfod40xQk8EYz/WdM32mBTHO1Kw/3DIyKCvhFjXCIDdBmY0 T/fob+pHZe0BGRHGqrjjsx5icMfKsctHdlMNanf59a0jPnlhcRMrPbVF0LDmVTGC ooOBpMPcEnqFJt++FhdXm7T1qDmyQU2QsoH36DsXodXShRaD3lhQn+4Hebh7LXWI IYsA2btiwxUnuvY+bokOQR9hH5bAzD60jNZqTKE/IyALI159gOY6HNydOCy8YJfM 9VqTTAVRJI5DO8ODKRNvk0meCr5r+PaZ6fr4VLE0gqzTjd62n9F6m1Q0BjwCO00Q Q0wb6ngp5sAMxWb/hisXbaBkZag3QyKj+fzQMT1qplXihdnhsczNxMxZfbPv6zbl ymnTU6DqTNngOnaN8BVp =p7kY -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: http://lists.debian.org/e1tvbx8-0001lg...@franck.debian.org
Accepted libarchive 3.1.1-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 16 Jan 2013 17:06:36 -0500 Source: libarchive Binary: libarchive-dev libarchive13 bsdtar bsdcpio Architecture: source amd64 Version: 3.1.1-1 Distribution: experimental Urgency: low Maintainer: Debian Libarchive Maintainers ah-libarch...@debian.org Changed-By: Andres Mejia ame...@debian.org Description: bsdcpio- Implementation of the 'cpio' program from FreeBSD bsdtar - Implementation of the 'tar' program from FreeBSD libarchive-dev - Multi-format archive and compression library (development files) libarchive13 - Multi-format archive and compression library (shared library) Changes: libarchive (3.1.1-1) experimental; urgency=low . * New upstream release. Checksums-Sha1: 8792591c805d892f70415b23c30f2043ce923533 2273 libarchive_3.1.1-1.dsc 611f296718cea684b3c1bcbd1eccd5f9693ce859 4260083 libarchive_3.1.1.orig.tar.gz 352937bed2840041e51764a03ca2873a708dc6ab 10434 libarchive_3.1.1-1.debian.tar.gz 13da11153ab3b7c4c887f1fdb9799a332fd8ef9a 495716 libarchive-dev_3.1.1-1_amd64.deb 99df0faa3728c009bd6e1b4eed864f1f2c13ec82 318038 libarchive13_3.1.1-1_amd64.deb 133e28c781933e2993cf9bd5a4eb5750da6442e0 57608 bsdtar_3.1.1-1_amd64.deb b9fe87f7c380af7e5c99a9ee21e8effc58898f93 41516 bsdcpio_3.1.1-1_amd64.deb Checksums-Sha256: d517688f3c3d7b408f9b649e81f92fd63de212f37eb3053ddd93e66e6967040e 2273 libarchive_3.1.1-1.dsc b70acd1a185e4c8bf7b2dda566a3240adf055e99dc97faec3dd4567ee84ec568 4260083 libarchive_3.1.1.orig.tar.gz 7046d8e2ec4a7df863b060294e8249b6bf99b3d2bdcb4f0037094d10d455b953 10434 libarchive_3.1.1-1.debian.tar.gz 926238be983a72501b1b8d23d33da39bc907dd47017f065c14aeddf7fce3ab2f 495716 libarchive-dev_3.1.1-1_amd64.deb dbe8847ffe2ad1c0b082873c567ea0237dd2af054606e2bd60dde98fbaedfb60 318038 libarchive13_3.1.1-1_amd64.deb 0b0456bb2d743f235c47574c877104cd3727b968d4c4fe0187cf476cf0241f49 57608 bsdtar_3.1.1-1_amd64.deb 93e3c9c65100835f05bc5d4ab78b0fe02afbac8eb4f8ef96d90c849c378ea98f 41516 bsdcpio_3.1.1-1_amd64.deb Files: 3c93a1bce0ccd53778f289f95feaa5db 2273 libs optional libarchive_3.1.1-1.dsc 1dd72aa8eff177db1af9a1011ec22556 4260083 libs optional libarchive_3.1.1.orig.tar.gz b8edf245fda63cd8aac8553b7ed101c4 10434 libs optional libarchive_3.1.1-1.debian.tar.gz 38fbb97c87616d4b77b75e24bbf386c8 495716 libdevel optional libarchive-dev_3.1.1-1_amd64.deb 94a2a8a3acbe5e8578072a6fd9f98ff0 318038 libs optional libarchive13_3.1.1-1_amd64.deb 6d462e950b9bcc369a0d9f1cd7984eb9 57608 utils optional bsdtar_3.1.1-1_amd64.deb 38a2310f492be2fdf58ad155df874ea8 41516 utils optional bsdcpio_3.1.1-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBAgAGBQJQ9yYiAAoJED+5x4pTyFTfVgEP/128Bslh7E4Ce0+8VGHyEBrO 07MG0wRT3HjzshP1fkND0Hjc24gFcUC0wKQlEYFFOiNTx0Yg67uydPMSZ2PkyGFv 6moa8zt49fcYfcMH4BUwOCj2Lzwm6bCXBwv7fr4/wBAVXv3qwAy9SwINGcL5ml1F rXmWE6n2Ye/wlXaGMYLEKJ1mXyPbGo7+gISIgcFnq2YVaJS8OWEnTdRdcPVjYK02 PxviTos57tsYAOgEbaM2YtLg+XY67c0kxoaVmtoFKsUEYn/Exf3q/Bmp0K6xuGGM UZgi3TGxYxuWtmxHGQrnW5xR0iahoGmwgyBTfv9ByP8Sfbty58dReNMG0YNpotV4 9baFeILPkFBq/fAvKNWXMIdXG59skqtNIe/tIth35hyM2xNpX/mlHpxDn4LLHEj2 UQlQND/pAgX0zhgL/qY0XqaIIsVE8GuizCNKS4h5q5A3K4TUecHrdhpOFsCRMlEZ u9P470bbS8ET3AsDVaWXVy4Gr6As46JE4nyZ2ZhJUaz34KMEX+z0HAPKOOSvpxWO aHV+DEDz9Eb0WAszFXw9KVxfe0IhHInAOM+r7erox2DvV2UGGGedsGNxKbQRbcRt odJsW8UY0QVKArQX88KlY6jLe2JMFBzcLOKt0M/YJgcVsri/Kp7cDWfV+EftY2To dFw4STs4rLeeB9J/RGGc =xtDj -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: http://lists.debian.org/e1tvbxj-00023o...@franck.debian.org
Accepted openjdk-7 7u3-2.1.4-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 16 Jan 2013 11:46:20 +0100
Source: openjdk-7
Binary: openjdk-7-jdk openjdk-7-jre-headless openjdk-7-jre openjdk-7-jre-lib
openjdk-7-demo openjdk-7-source openjdk-7-doc openjdk-7-dbg icedtea-7-jre-cacao
icedtea-7-jre-jamvm openjdk-7-jre-zero
Architecture: source amd64 all
Version: 7u3-2.1.4-1
Distribution: unstable
Urgency: low
Maintainer: OpenJDK Team open...@lists.launchpad.net
Changed-By: Matthias Klose d...@ubuntu.com
Description:
icedtea-7-jre-cacao - Alternative JVM for OpenJDK, using Cacao
icedtea-7-jre-jamvm - Alternative JVM for OpenJDK, using JamVM
openjdk-7-dbg - Java runtime based on OpenJDK (debugging symbols)
openjdk-7-demo - Java runtime based on OpenJDK (demos and examples)
openjdk-7-doc - OpenJDK Development Kit (JDK) documentation
openjdk-7-jdk - OpenJDK Development Kit (JDK)
openjdk-7-jre - OpenJDK Java runtime, using ${vm:Name}
openjdk-7-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
openjdk-7-jre-lib - OpenJDK Java runtime (architecture independent libraries)
openjdk-7-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
openjdk-7-source - OpenJDK Development Kit (JDK) source files
Closes: 695028 695992
Changes:
openjdk-7 (7u3-2.1.4-1) unstable; urgency=low
.
* IcedTea7 2.1.4 release.
* Security fixes
- S8004933, CVE-2012-3174: Improve MethodHandle interaction with libraries
- S8006017, CVE-2013-0422: Improve lookup resolutions
- S8006125: Update MethodHandles library interactions
* Loosen OpenGL dependency. Closes: #695028.
* Fix error parsing drop files parameter from pcmanfm (Alberto Fernández
Martínez). Closes: #695992.
Checksums-Sha1:
3b133d5e5beef6aebbc1ceb0ae0a323c6a7282a0 2905 openjdk-7_7u3-2.1.4-1.dsc
decfc6bfba7e47b4619884bff2fc5ad2cc523a84 66716922
openjdk-7_7u3-2.1.4.orig.tar.gz
561da7188f760a960f135f51d2f5ed71119874f9 190216 openjdk-7_7u3-2.1.4-1.diff.gz
a557a1d286d66bed0078229ab1f7c747522d4209 12115520
openjdk-7-jdk_7u3-2.1.4-1_amd64.deb
b07918e04a45db1047bc645ab9ba1f32d0e1581d 28010572
openjdk-7-jre-headless_7u3-2.1.4-1_amd64.deb
c618f470d522ef11aadb64c9a18163ea823dd84e 227516
openjdk-7-jre_7u3-2.1.4-1_amd64.deb
bb6c41a82fcae61bf8825a07ab52fdb3dce0cd31 2469886
openjdk-7-demo_7u3-2.1.4-1_amd64.deb
5c5c872be30106eb439b2e56280144f36ba6d72b 155496058
openjdk-7-dbg_7u3-2.1.4-1_amd64.deb
c43165360f1d7100cb0b0928ba2f1e600bd98910 848828
icedtea-7-jre-cacao_7u3-2.1.4-1_amd64.deb
453d06ebbf4a23af5a9a8fc06dee196d75150d73 629924
icedtea-7-jre-jamvm_7u3-2.1.4-1_amd64.deb
02400c59176ef1c5e7daa627417f664ca10bc704 2336268
openjdk-7-jre-zero_7u3-2.1.4-1_amd64.deb
be3d095fd92b1fdc5b69a4f36a7589ed3e94d4f9 5193880
openjdk-7-jre-lib_7u3-2.1.4-1_all.deb
9d1e254e0cdaa47ddc69d706e64dd18cf4d91536 41364562
openjdk-7-source_7u3-2.1.4-1_all.deb
17ba63269e979b2f89306e302a707c0843a85016 22087256
openjdk-7-doc_7u3-2.1.4-1_all.deb
Checksums-Sha256:
501e7666ae9829361df0a2aeda0dfb9ddf8f957a5731c4c038769d5892d9c9fb 2905
openjdk-7_7u3-2.1.4-1.dsc
508797342ad059b39b3c589597ed4416d9d1b4ca689af02c047e415a3275b274 66716922
openjdk-7_7u3-2.1.4.orig.tar.gz
43065f59f6b63cb7c70af4e5be1258727d3f1dd7233d4f5d68e8667e6f48a650 190216
openjdk-7_7u3-2.1.4-1.diff.gz
bb8a233c346bd102c0ac291e521a5c6d04cb24409d7c72f112976099e8dd5f40 12115520
openjdk-7-jdk_7u3-2.1.4-1_amd64.deb
b52a1cccfca92a3d64c3021bcb050a0c1b3784154b723fab58d26e56b16bdef6 28010572
openjdk-7-jre-headless_7u3-2.1.4-1_amd64.deb
b19fce2f1a3befd45db5d3321cc5c9d6d052a31a9d1e204e2b5492ed05a15f49 227516
openjdk-7-jre_7u3-2.1.4-1_amd64.deb
bc8e1910ab1de1a870729c5b9687fddccb20e0c207744dec23fac6854b9b1173 2469886
openjdk-7-demo_7u3-2.1.4-1_amd64.deb
991221d8a3779659156d10576a683b8b0675fe525cf1721bf5a8d566a461a747 155496058
openjdk-7-dbg_7u3-2.1.4-1_amd64.deb
d352be788dec0fae466f7afc6fe1019ca6a812bec61bf792e20f2bd8cfa34d5a 848828
icedtea-7-jre-cacao_7u3-2.1.4-1_amd64.deb
8b3ce1d523b932b746bec671504c831d50e49326fdf1f25977e0105240ee 629924
icedtea-7-jre-jamvm_7u3-2.1.4-1_amd64.deb
4114294a316108ee33215c99e3c55e31475855219fbb5a8ab7fcfa3eccbae315 2336268
openjdk-7-jre-zero_7u3-2.1.4-1_amd64.deb
bed005a56914d269fc9527b389237c6d96c092e0298a1b5c3c75c227d1eafef2 5193880
openjdk-7-jre-lib_7u3-2.1.4-1_all.deb
496b34a4bd8ed269aeee4b6f02f14de77157aa47b7221cee37f93fc7e002e003 41364562
openjdk-7-source_7u3-2.1.4-1_all.deb
0328748ab7572784783c4335f58447cc7185761994d55fb65dcf955d49745722 22087256
openjdk-7-doc_7u3-2.1.4-1_all.deb
Files:
f4577d27d52685dfc500dc139a51db6d 2905 java optional openjdk-7_7u3-2.1.4-1.dsc
4df6939fe6f5cd73021ee0d0d5517308 66716922 java optional
openjdk-7_7u3-2.1.4.orig.tar.gz
2313fee0cbfdd3d06b552c5e58b37ad2 190216 java optional
openjdk-7_7u3-2.1.4-1.diff.gz
a6b646ea55d1f8eaf4e04e28d69b7d06 12115520 java optional
openjdk-7-jdk_7u3-2.1.4-1_amd64.deb
1d065b8e9283f6aea7f24ef86c31a4c2 28010572 java optional
openjdk-7-jre-headless_7u3-2.1.4-1_amd64.deb
Accepted s2tc 0~git20121227-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Jan 2013 14:34:46 +0100 Source: s2tc Binary: libtxc-dxtn-s2tc0 libtxc-dxtn-s2tc-bin libtxc-dxtn-s2tc-dev Architecture: source amd64 Version: 0~git20121227-1 Distribution: unstable Urgency: low Maintainer: Lennart Weller l...@ring0.de Changed-By: Lennart Weller l...@ring0.de Description: libtxc-dxtn-s2tc-bin - S2TC texture compression and conversion tools libtxc-dxtn-s2tc-dev - Development files for the S2TC library libtxc-dxtn-s2tc0 - Texture compression library for Mesa Changes: s2tc (0~git20121227-1) unstable; urgency=low . * new upstream release * fixes crash with some some bugged decoders Checksums-Sha1: a4d4c9f305cc43027a2603fff237cc46c210ac99 2079 s2tc_0~git20121227-1.dsc d841112d3953df172e41cc8d3f821691a4d42bad 1395373 s2tc_0~git20121227.orig.tar.gz bcbb4754a7bfe33b0561424dea00176a855313e0 3929 s2tc_0~git20121227-1.debian.tar.gz e7bc106d52ece2a35cd7b06a22895420d9cd6090 61204 libtxc-dxtn-s2tc0_0~git20121227-1_amd64.deb 31f93e94ba91836fcda986c7e9eac60a52d012fb 14584 libtxc-dxtn-s2tc-bin_0~git20121227-1_amd64.deb 116d72c7d802d1c0de9770735763d2d09559c7f4 3220 libtxc-dxtn-s2tc-dev_0~git20121227-1_amd64.deb Checksums-Sha256: 87ad2f1ac838fa956857b3f6837d0e0103e1eff9938cfd16712a5e2d94c43f5b 2079 s2tc_0~git20121227-1.dsc b7715aed3010edcce8a6d68e7d599379a1eadf45a9e8d78524f7eb0dafd4b5f6 1395373 s2tc_0~git20121227.orig.tar.gz 5846d16766fb47e783db4f4b982c5de9dba107d25c9a761bb35e6774b8bbac22 3929 s2tc_0~git20121227-1.debian.tar.gz fb15dd96c2b5a714d5e6c083be51d9106f17e7abf19dfec3324e4ac2100caad7 61204 libtxc-dxtn-s2tc0_0~git20121227-1_amd64.deb 757df599747f556d0e3b16b031a3ad9bd4650481e17df0364ddc70201ad0c614 14584 libtxc-dxtn-s2tc-bin_0~git20121227-1_amd64.deb 20223f338cb71283700b1ead899fb285793a58074da357405e0e7297a8e4484c 3220 libtxc-dxtn-s2tc-dev_0~git20121227-1_amd64.deb Files: c73509c51bfc4a229cf2e2c4a0c533bd 2079 libs extra s2tc_0~git20121227-1.dsc f01ae4f9a3bcccb2dd66644dc19a54ba 1395373 libs extra s2tc_0~git20121227.orig.tar.gz f824cc6d5ac5d8e90f9f28d713937c4e 3929 libs extra s2tc_0~git20121227-1.debian.tar.gz 46ba1ce7347c200fe64e261803c404ff 61204 libs extra libtxc-dxtn-s2tc0_0~git20121227-1_amd64.deb 85fb2a9e58c0866c4d3ce988392d5f98 14584 misc extra libtxc-dxtn-s2tc-bin_0~git20121227-1_amd64.deb b090fee36acaeebe9d6096e850d6dfb0 3220 libdevel extra libtxc-dxtn-s2tc-dev_0~git20121227-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ9zFnAAoJENju1/PIO/qacdIP/2FtsZNF2oJRsIN5y9kDSSPU drqYvMHhe6KqMtpBF3301oTNP+HVwhg2I6lFCjxgNfoIUjxsrYm0y+IylYo40Y7F c/AIM6dIqesTHkJmhuRYc+i/BbmZLjALX/LjG2It7ixdLFvAG/iOpZ2XdUAgzKnN fek+8pgVVwP5+WK5lVl/7oBPfgQOiDdrE7gyOG3nXoab7Fo6n9cCaL3qnCHcCHgb ohbW1k64Pjz7rv2U3OrS0UQSpiOtGA/8xoUX8FodG+8x4Osmyrak0Wd/wNtHgbvv K6gbrTIh8NHGatuPbbfDZZ2fpYvCK+9C49gOAsITN/+tio67nzwMWTvxVmEJfouC urQzyYhok8ZZSfuavSEo5RoVwyrMerPQTiPpX8P+LO6c2UP+SdhABQXES+BQPrOI Er9xI9PJWZGzcVfPXe1JJqjZLjffrOW8BYUHEPzNOCxeXKty+bulw4WGjpErd/Nz VTXPiJWwxQA/0+gKextH1dF2btIUaukVSjSfcSq9q2CyU42U0QaxD85NfZDbUd+P wqEmO87As2l/dRbFLrSW4YNKJjnlFINcEVq6eZaYF71nAOHh6cgdAK830yjReLV8 t81Sfa5HiCmuGxQaalXPrMUC0oF0DbNkTbW6saQHh2334vH7pcPPei20MqVrqbjJ VIcq88OpcGngppXhecj9 =Uq3M -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: http://lists.debian.org/e1tvcep-000554...@franck.debian.org
Accepted z80ex 1.1.20-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 17 Jan 2013 01:00:32 +0100 Source: z80ex Binary: libz80ex-dev libz80ex1 Architecture: source amd64 Version: 1.1.20-1 Distribution: unstable Urgency: low Maintainer: John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de Changed-By: John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de Description: libz80ex-dev - z80ex emulation library, development files libz80ex1 - z80ex emulation library, shared files Changes: z80ex (1.1.20-1) unstable; urgency=low . * New upstream release. * Bump standards version to 3.9.4 (no changes required). * Add fields Vcs-Git and Vcs-Browser to debian/control. Checksums-Sha1: 92174cd37a752db56d0a2808fa0dba23bef4ebaa 1864 z80ex_1.1.20-1.dsc c852b01f6f2d1cc11e9a331ab88383e48e508b27 65652 z80ex_1.1.20.orig.tar.gz 1516ddfca262b106ab74a98eb3a8131fff765c66 3530 z80ex_1.1.20-1.debian.tar.gz f64f9dcd82629f7aa4f527b4df7d91a058866947 71680 libz80ex-dev_1.1.20-1_amd64.deb db84f902fd77837cc8665cb6419c8818aded6e6a 67460 libz80ex1_1.1.20-1_amd64.deb Checksums-Sha256: 2af54c3f9e3caec8ff14c2c14db54b49ecc4611ec7ed7dce2f81e55fa4a2fbe9 1864 z80ex_1.1.20-1.dsc 2e2eb7b35e96ec002f8ae9b0112e900e860b0fd4520b49d240c719a4e7401b43 65652 z80ex_1.1.20.orig.tar.gz 7b6989a7f2e303475e62fd02693556b84df60bf9fbd0bdf8f323ab7846b62f27 3530 z80ex_1.1.20-1.debian.tar.gz 60e1a1c0e1c5dc8887f5acb5eb1056bb6479f0eece2b5f7b77f29d760b54915c 71680 libz80ex-dev_1.1.20-1_amd64.deb 97fd473de5fe326e52aec5ebbbff451be7a463cdeb15832e912a18cf3bd17b6a 67460 libz80ex1_1.1.20-1_amd64.deb Files: bd8326a53d6d652057fe33e7c5ff3e23 1864 libs extra z80ex_1.1.20-1.dsc 8e138129063ba726b249970d252d00ca 65652 libs extra z80ex_1.1.20.orig.tar.gz 0e9b28be39289255dadf8f7d49de2267 3530 libs extra z80ex_1.1.20-1.debian.tar.gz c7d620944b3a6e850af77b704d4c8181 71680 libdevel extra libz80ex-dev_1.1.20-1_amd64.deb d48a767fc82ea3c6f6eaa224f6f154e8 67460 libs extra libz80ex1_1.1.20-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ90CvAAoJEHQmOzf1tfkTNggP/j3eq3hKVF0fpkuZI1K1zSqu aVRA2b+81/rbpixdNhzdXtdSrqqlwmJa/usf+y1Jtuu42SrDM4zSUHuZ7VzirOkk ujXsUHme2cpbut2LuawHSsIZks4o3UvbA+wzl0T4u2kHyHEwF42KIQjBTgrb5AC3 I0H5SxQETGbdlyEz52prubVjDRnSNmaI19aIlmra+hdZ+I/m8vPbk9u5OhVZx3/C aTvKuSnTbot7E9OcwTfQZFZxk5CTvSvI95KqXzMtu819U0ZNueLijMWTyXyNpTNC TenvRcL4ORbzfAt/LGdaRvXLqno/JBg0NtIUWvnE/9NAXqzhW/I/X3cIxwaPWq+P Gy2wI3Lte4Tx8HUkrvfEb75CAROvxGCzeebOkqYYvgGW5XxBI5Ti6XnpNOKsQ7F8 7Cj3/Q1OwfA5mokE3erp+nV4Uly8lBkWRFIp9/H4J5uOi20iUT5j5YfwZezOyzS9 lqw7Q2NprtBI6PrmYHdzkk6nABvm1SMsPK9b0gj1IFaljlGqW/JEqwEZFSbHNLHO SECM2DULAY8Y/ka/dcjLzuHj73kUUMHMpf97EfXl3xx0bz9JxzZOLeA4f4BsPyY1 zE0pC23z7EMNPFbl2hUcPhnXemirKUb5f+uaDX2kmoTioqAaxtCH6qiSJn2JNDGq nliQ4x5V+7GvpPP70kV4 =WLSS -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: http://lists.debian.org/e1tvdaj-00089w...@franck.debian.org
Accepted fusesmb 0.8.7-1.2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 11 Jan 2013 18:12:40 -0600 Source: fusesmb Binary: fusesmb Architecture: source amd64 Version: 0.8.7-1.2 Distribution: unstable Urgency: low Maintainer: Samuel Mimram smim...@debian.org Changed-By: Gunnar Wolf gw...@debian.org Description: fusesmb- filesystem client based on the SMB file transfer protocol Closes: 697665 Changes: fusesmb (0.8.7-1.2) unstable; urgency=low . * Non-maintainer upload. * Change dependency from fuse-utils (now a virtual package) to fuse (Closes: #697665) Checksums-Sha1: 7ee768760c4f6c8bb36cd75759b62d039ed06562 1719 fusesmb_0.8.7-1.2.dsc 6e71d56c9305d75e3dff7264d0c39482a4e10493 17248 fusesmb_0.8.7-1.2.diff.gz f11956e762c1b95e21382077a59fde2a977b35b7 30362 fusesmb_0.8.7-1.2_amd64.deb Checksums-Sha256: d4828db92fcbaecefef469918a821941a61ee8db146ab1166fd96c15a70a73fe 1719 fusesmb_0.8.7-1.2.dsc 47809835a5ac09b42cb176ceb87e472f3a3dd7d91db886a36a8ee79adf5159df 17248 fusesmb_0.8.7-1.2.diff.gz 6b0d5e415b13ebade4ce9291ca09ae9a35ef4d6ae52c859cb907572b0f546cf8 30362 fusesmb_0.8.7-1.2_amd64.deb Files: 5cae1b1b227a88ecaa84eb1901affaf9 1719 utils optional fusesmb_0.8.7-1.2.dsc 38d939fc3c3b652226e7b7290b943304 17248 utils optional fusesmb_0.8.7-1.2.diff.gz 94867e5acc847868904d5eca6438069a 30362 utils optional fusesmb_0.8.7-1.2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ8Kr+AAoJEGc6A+TB25If+PwP/iTXFaR9CuICzW95CyMZKnFl J28LgF2TOiukuJLFK+vXxsYdGw/2pIHIga/llPbhcKtOL3GDAy3GHeaslE5IwbAo rN0WSIpUBpcRzIIWcShL3gY5bKmIjuIzrk0HdyXzn29EHhOBdfQw17vvgLLwJgzc AKB68PEY6Uj3dKS245Vbjam8xlEBN7qyoMZfK5yWrdqLmr2YaYKPDQZoL4wKw5ye LZhEUDA74XMxHO2b+uH5AYNKoa52PWYATxeG9HOnPN6qgzxNr9IF1sNSw6f3Fok3 ZriO0+rcOvrgx6S9yZoVi9+2o6oYNUujLcUjrqsHoepQYTReIic3D4JG63bSuhBs sNJqW2pU049dfmd/eYxoPX0Idx+LHbVum9qTo5B89RHhLhdoy2l5E4dn5HOnWx47 NChaiZndpSJR1wjxyuITgr7tdfAtlhUxsRwV/28/cmDKfyQxMKXISsG5G455U6Wx 2oIqUW8V/wHVtyI5ZEh4je7n2/gqXKbu+k6LTeOr5j8OPVNeChVOh7VKJmSjcIyb peM3kzMPeMr7xFCAfu8jXl3wpveuLXIf1xSWp7E+/HmBSfpooPoG/mvfJpVGKpaK zWAPSA40nHjbmEA1/1ycCwZ5oJR5dMRrZ/6EiPeLE92BRfhTwaet1rIdoN4watJw QjpXyl36j7BAj2IQca+6 =q4xc -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: http://lists.debian.org/e1tvdsc-0008r7...@franck.debian.org
Accepted java-package 0.50+nmu2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 15 Jan 2013 15:06:26 -0400 Source: java-package Binary: java-package Architecture: source all Version: 0.50+nmu2 Distribution: unstable Urgency: high Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org Changed-By: David Prévot taf...@debian.org Description: java-package - Utility for creating Java Debian packages Closes: 597294 698108 Changes: java-package (0.50+nmu2) unstable; urgency=high . * Non-maintainer upload. * Allow two digits in Java 7 updates. Closes: #597294, #698108 Checksums-Sha1: d214ffe96b295aa06cd47271873504d7b8b8093c 1642 java-package_0.50+nmu2.dsc 571685c1c3d80c291f0da4faa821f4477f8e3e52 17453 java-package_0.50+nmu2.tar.gz 335af5cba2f647118f93c39201ac850c94028aa2 19486 java-package_0.50+nmu2_all.deb Checksums-Sha256: 730e93d4bae5a4d9caf89315b7504d451dd5224f6a419f3567104e1a212520fe 1642 java-package_0.50+nmu2.dsc 936c5e55dd92ed25a7b8dbde5cb33567c248c750560048458aa4d74462a22391 17453 java-package_0.50+nmu2.tar.gz 3925d98bbda5ef4199f0b7e18b651185051e18e2b35df739ebe5aa3a8d8b02cb 19486 java-package_0.50+nmu2_all.deb Files: a7b6b2a3595318daa837603772b4d41a 1642 contrib/misc optional java-package_0.50+nmu2.dsc e095ae54bd5fbf8499b9657c3dadcd0b 17453 contrib/misc optional java-package_0.50+nmu2.tar.gz 26ddd326899de1992e845b93fb9cdbbc 19486 contrib/misc optional java-package_0.50+nmu2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ9apqAAoJELgqIXr9/gnyOAMQAIW/829X+QHJlyHI6igSiYVK bzX3DV/tOu9RLXv7VwHfzeQrY8KoB2vLLH5CyHOOiELyoos+83e1tbFzM6T7Jiy3 ZRqV2WvGxm5TEN5Mli7Tn9Lz0xCKVuQ8e71wLUmuGGgPXaUJmpCV5XLSWeo+xciK i0UkhtdiEgV05Y8cut5NlW8SktYyuL6ObGnXQXop0Yuj0dWX2VCb9kjZzYr2A4o1 B9p/sD9ECpOhThbYSv0zpivoO1ylssCPtRIaFAvLpXSQXshemfgBAdIruoQCkQQV vnsAwJBiIJ+iLjBQN3YI9PlqeG5sOT3bCzadLD3Y5C5d+pAPzl22/g33XJBQDvFI VWtWMiJh4M85ulUtkckw8Wj0PnnLGqLnDGl3gPiTRuAfhYFDMlJnCnGWA36ENhrr /A7W591VikRXocYAHVXuptg4d+NCp2KaAoE2cF5AzFkVhgS5WmEJ/eWvIhNvsFde 0eKvYGbfSQ1L+R4IfeJG5lir8WdnNzeysdS0x1fon+Ik0qFitv+KWKaj4gGcZvB9 vMqgQZsvAGptKxxrvOjEjddWXtwQiqLMjWAQliXN30qYCCWwC2TuCaZJh5ZPI3eo WJNdYJnASoen9vWR/pOGCGFG5RSVPxeyBGBaDj4FX/eeSlsH9Ob1c/EPFcW4p/QW Rz40GFOrgIaErbsLtZlA =d6Bc -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: http://lists.debian.org/e1tvfvq-0008sw...@franck.debian.org
Accepted wims 1:4.04~dfsg-2 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 17 Jan 2013 00:47:01 +0100 Source: wims Binary: wims wims-modules wims-java-applets flydraw Architecture: source amd64 all Version: 1:4.04~dfsg-2 Distribution: unstable Urgency: low Maintainer: Georges Khaznadar georg...@debian.org Changed-By: Georges Khaznadar georg...@debian.org Description: flydraw- command-line drawing tool wims - server for educational content: courses, exercises, and exams wims-java-applets - applets for modules used by WIMS wims-modules - minimal set of modules used by WIMS Closes: 687947 Changes: wims (1:4.04~dfsg-2) unstable; urgency=low . * modified files packaged for themes. Some are now distributed as templates so they can be customized at postinst time. Removed the file log/unsecure from the package since it makes no sense for Debian installations. Closes:#687947 Checksums-Sha1: 9e2224eee19e96d535ee46724edbff0fabd748a7 1440 wims_4.04~dfsg-2.dsc 1bba632cd023b5beb734ae2e5043270992773bbe 46217 wims_4.04~dfsg-2.debian.tar.gz 40b48ea5752031b50dc1e87fafeca5b90df5bd13 23653524 wims_4.04~dfsg-2_amd64.deb 095412d848b22efdb9a3a4c9f48693c3234703dc 1301618 wims-java-applets_4.04~dfsg-2_amd64.deb 3380f194f834d012f006118e3a7a7d112adb580a 61146 flydraw_4.04~dfsg-2_amd64.deb 9881288ece5a2665a0c91449d4b9da8de64b2f18 1828338 wims-modules_4.04~dfsg-2_all.deb Checksums-Sha256: 3ced181bd45c12fa18053ba30c5e93d0e30d00b0372d2a57a3d0cb3c86432d4b 1440 wims_4.04~dfsg-2.dsc 744c73bec7dc2252eb8c4c6409a1caea6c1a029eb90b720345606f0abc8d0244 46217 wims_4.04~dfsg-2.debian.tar.gz 736130baf2605a67ed8dc550e6a8fa1333eccce3940b9feb26dba1dc466a9e1c 23653524 wims_4.04~dfsg-2_amd64.deb dbe1e43342ca5d875913fbaa7512296f81c881f2c88e1c8be523af55536a17a2 1301618 wims-java-applets_4.04~dfsg-2_amd64.deb 20012a17e0d3f2153e9ee3b123f15f615285bc873757be008df8749f0fba79f6 61146 flydraw_4.04~dfsg-2_amd64.deb e2a31f86e59b275eb59f485305b70193cab372856bd33bdbd1db698c8484e356 1828338 wims-modules_4.04~dfsg-2_all.deb Files: 8c3ec52037ae8b6ae8e4793291c7cdde 1440 web optional wims_4.04~dfsg-2.dsc 04f2661a6393316f9dd606f7bc97c512 46217 web optional wims_4.04~dfsg-2.debian.tar.gz 3c09c695359e29f1f992ce4b09edf71c 23653524 web optional wims_4.04~dfsg-2_amd64.deb 2052a1889bce236ebad3b5750ca8544e 1301618 web optional wims-java-applets_4.04~dfsg-2_amd64.deb f00504a17af97b99b01154215ae20a3b 61146 graphics optional flydraw_4.04~dfsg-2_amd64.deb 8c90022ee6bbe87ee7f31f5d2fba0e16 1828338 web optional wims-modules_4.04~dfsg-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iD8DBQFQ91iFnfmb2hFpETARAl5KAKCQ5At9d2ssiZaxTFicULlYwgJj/QCfdQdn HRqrSlaThns0fOcbxtqdLoY= =uSU7 -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: http://lists.debian.org/e1tvfwf-nf...@franck.debian.org
Accepted mangler 1.2.5-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Jan 2013 20:04:47 -0800 Source: mangler Binary: mangler libventrilo3-0 libventrilo-dev Architecture: source amd64 Version: 1.2.5-1 Distribution: unstable Urgency: low Maintainer: Vincent Cheng vincentc1...@gmail.com Changed-By: Vincent Cheng vincentc1...@gmail.com Description: libventrilo-dev - library for communicating with Ventrilo servers (development) libventrilo3-0 - library for communicating with Ventrilo servers mangler- Ventrilo compatible client for Linux Changes: mangler (1.2.5-1) unstable; urgency=low . * New upstream release. * Fix lintian tag vcs-field-not-canonical. * Bump Standards version from 3.9.3 to 3.9.4, no changes required. Checksums-Sha1: 4b8a9d002eba63de8660067ebcf16e134a5248cf 2185 mangler_1.2.5-1.dsc 94b0a309a03449bb9899681f3f502fe269faa48c 2108367 mangler_1.2.5.orig.tar.gz 2a54c876220daf8345751824b3d3575e51d1458c 3885 mangler_1.2.5-1.debian.tar.gz 4fa68a46f71fee261c9b8cddf3c9944b2bdb6e6d 719606 mangler_1.2.5-1_amd64.deb f5bf6f137c4f25af263bd395f9a1dff048ca1c64 83236 libventrilo3-0_1.2.5-1_amd64.deb 46de5b319d12b08bb4169fdc65e2e581f015cb91 93358 libventrilo-dev_1.2.5-1_amd64.deb Checksums-Sha256: 9a0839579ca7c1c9f9cfdff62b13642317e861689b19d2aac50c3e091523d547 2185 mangler_1.2.5-1.dsc 53fcce24d7e1e28a41784204a8f946ecd131eec82bf1db10f8d552a06b6ceb67 2108367 mangler_1.2.5.orig.tar.gz be841adfcf4c120262601f97394c23d30679cbb67880b4e75426353dabeaa904 3885 mangler_1.2.5-1.debian.tar.gz 27693efbedb2996141576ff70f577ccd492218a99bbf4290b59242cff0242dbd 719606 mangler_1.2.5-1_amd64.deb 26a578f584746503122d468168161d6c274ac92fc968678a9f8df6eeecc34ae3 83236 libventrilo3-0_1.2.5-1_amd64.deb 4bd37f322f97954ea33a8ecbed7d261614a2fd2d0b7ea68675a668fca63dea16 93358 libventrilo-dev_1.2.5-1_amd64.deb Files: 7c8202ce69fbf129b53c0de82a837548 2185 net optional mangler_1.2.5-1.dsc c1d23c6e4b1d3eef48fb2cc34da1329c 2108367 net optional mangler_1.2.5.orig.tar.gz cb450959700492575cb774e58f6e0c44 3885 net optional mangler_1.2.5-1.debian.tar.gz 2e5aa7943d6167f5d59a221b142dd577 719606 net optional mangler_1.2.5-1_amd64.deb 47391495d1dff47865b956ba45b43de3 83236 libs optional libventrilo3-0_1.2.5-1_amd64.deb 5b919a72afca478c7cac142c6e0da6f3 93358 libdevel optional libventrilo-dev_1.2.5-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ93xMAAoJEI7tzBuqHzL/k24QAI/GGRBMUhB1WFqa/3e53Ejr whznJ2B7yWCdVbu0aGcIxb0o0ApcT48msqWzfddiA7kBuYNAkTf7IKG5+3qmlreN QcpEyv7A//LLEYhWl0g4wrRQoeJJD51gQIAFsRC+74b62hztFYqt4QcQJOXYE+Sf 8bmV1LNp4j6DLMESynkMxYZ7BRD0SxJ07FuUXCu9H74wfqCYqLJL8mOX9qvWdZ2G l0mm7okahcc6yGVQtgbFk68Rbb/8jjsLFioSglWb7SAElB2DZFa0GsV1J6jhOmtp C/PMBCJdiQ+C2+nfIrodJ5kQ4dn2tBPsuOvWjHM7tSY1m8JInOAroEC7sRbXS5pV 5sz0eGgAv69XuzemXL1a/aTByABwzrxLJb4Qsi8czxGps77giQAp30FVvF6YCDfQ lGJqeSOmiA7l1cWn6gJnDTPOVa6I/5mUUT0P3MVVOFRbcac8NwSoJbSTnz/L02V+ rIEoZTDun1Z4YnHIbIyDdxXMnvnFFvZLv93zlIRkmfqjWuMKmGo4Hj/Kn1uMSsnJ wsP+3pfz/jXmQvxbfNWmYh9ERXXh6+Dv+DQwFtyMvZ/biwBVBKU51yf+kHkIvzwr Gv6NlP0TABnmsELj0hsbFkZ7JTmCLPjeS/fydoe4TGzeO/WF7rxdbzNwhSv25JiR PC6bpq86Gt0FuJKzTRNp =pKjT -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: http://lists.debian.org/e1tvh9v-0003fk...@franck.debian.org
Accepted gnu-fdisk 1.2.5-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 17 Jan 2013 04:44:52 + Source: gnu-fdisk Binary: gnu-fdisk Architecture: source i386 Version: 1.2.5-2 Distribution: unstable Urgency: low Maintainer: Parted Maintainer Team parted-maintain...@lists.alioth.debian.org Changed-By: Colin Watson cjwat...@debian.org Description: gnu-fdisk - Linux fdisk replacement based on libparted Changes: gnu-fdisk (1.2.5-2) unstable; urgency=low . * Convert rules file to dh. * Upgrade to debhelper 9, thereby honouring dpkg-buildflags. Checksums-Sha1: 7a683a2e5eebc66c87a1b1061329689e85f8d1c5 2029 gnu-fdisk_1.2.5-2.dsc 783af088697e2057e9a63d1cc54cdbc110184b79 4379 gnu-fdisk_1.2.5-2.debian.tar.gz b66a5d16766eed789f3e9bce9c8688ec42925e5e 121548 gnu-fdisk_1.2.5-2_i386.deb Checksums-Sha256: bb1807dbc4b752f5ed193b0b722cb0366ddcc16fe16fb713452f6ae3c640ef72 2029 gnu-fdisk_1.2.5-2.dsc 7712a5fc4ea242aabd7d640391d783520e91eb5040f5e7cf4e327bdd68296dac 4379 gnu-fdisk_1.2.5-2.debian.tar.gz ed57ce79b73cc5c00541c9ee7cc2b99e41ae9b45a8721399d28b1876612fcb31 121548 gnu-fdisk_1.2.5-2_i386.deb Files: 2c6024110d422b13c6740f82beaf8054 2029 utils extra gnu-fdisk_1.2.5-2.dsc a55baaa4e837fa778fa88de812704b6a 4379 utils extra gnu-fdisk_1.2.5-2.debian.tar.gz b5eceb81bfba4c3e6f667a726f42bf52 121548 utils extra gnu-fdisk_1.2.5-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Colin Watson cjwat...@debian.org -- Debian developer iQIVAwUBUPeFDDk1h9l9hlALAQikZw//dOj2FvhSgOPERzuH5LQoih4u475/Aq3z xKOwEl7EWwS8fYxZ9kHz8PMa3cNnIKzBNfHj7jLnaRDxvbP0W1vonCqTva9c/qmE 0BusLrDbsk8F4tH9JdkwxSTCdEkXdqKNgjxECVS6b2a1QzkcFygxSBVcELk7og7j +NORRiSKlpWlQn1rkqg1FbglIOY3dB56ISi4T+EvG5ww0nWGaQRxWOGB60Zs52Rd CQckEnIr/PtFzrFVOGBUYa2w7k4BPWJ5dHqAO2kt09FODLwX+1Zi0A4PWTeQhpDd nwRyGtTigq90KRVfXZH0DF4Kwe/4J4uMtSE3Va85lzlVNQ7N+Cs3FPSTKPVlOr7z Iz2dAvQYJLsk0cQ//duAsNZ2Dp30JFFV5XoLOyfn/Lv+INtl2tfFY9EYgOQTBcOr gTKQlE62yCktgwqgHRrapfMjOXbjBCwrgcm/EcoR57mBg8Z2IhMzwCiS/5igExEl CrIFGcNaUJATZz3XLxOlKZR1kaj92XDerkH4H25Evw2Y2DGTkF6Z96Z9iUJ35T8d 5cyH5oseP/BKSQargSiUVMHwB1ZFjF0DSKkYdHnyKJpm3HasoLfIHR7LEI7prgXd Sl4UNeAKZ83EQhWCJYwaGcsX2Avuex/TwU0G+wvSPQ1n1O1Xpj4bw5j3WBTI+RuK RLYaj/sk6mw= =w05d -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: http://lists.debian.org/e1tvhqz-0003hz...@franck.debian.org
Accepted python-cdo 1.2.1-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Jan 2013 21:46:06 + Source: python-cdo Binary: python-cdo Architecture: source i386 Version: 1.2.1-1 Distribution: unstable Urgency: low Maintainer: Alastair McKinstry mckins...@debian.org Changed-By: Alastair McKinstry mckins...@debian.org Description: python-cdo - Python module for Climate Data Operators Changes: python-cdo (1.2.1-1) unstable; urgency=low . * New upstream release. * Move to debhelper =9 dependency and Standards-Version: 3.9.4; no changes required. * Run the tests/ test suite from debian/rules testing target. Checksums-Sha1: 12756a98e5395a4154675e4a74da817d3283a603 1790 python-cdo_1.2.1-1.dsc 733baad086ee8d5aa70f9e1a891b9d888d28b5e4 7740 python-cdo_1.2.1.orig.tar.bz2 dfb5ca6a2bb2e3b73cff887b2ff657c6ec477575 2129 python-cdo_1.2.1-1.debian.tar.gz 1fb239069fc8bc82f87557203db45afeb6eab52d 7298 python-cdo_1.2.1-1_i386.deb Checksums-Sha256: 3ef6f3d9f5a826d85520a3a0cf0e8d620ea4a2678e99746bd884ba77f946b95e 1790 python-cdo_1.2.1-1.dsc 05b994ffaf810ad06a5660336b1c9f62ef6e2ab1c05d6f84409ee6f37799bcac 7740 python-cdo_1.2.1.orig.tar.bz2 7e6893c273f6409c9e816388fc1f01de27070879e573bc74489485ea04558ca5 2129 python-cdo_1.2.1-1.debian.tar.gz d2cf69bceaad16488e31139ccf8314f329fecdcc698020e8b180741c3c9456bc 7298 python-cdo_1.2.1-1_i386.deb Files: 7f2562a847ac65f38f578c28891340c5 1790 utils extra python-cdo_1.2.1-1.dsc fcaced27d0316b6b02953725fb18b1c4 7740 utils extra python-cdo_1.2.1.orig.tar.bz2 6792d14391272b74671048bd4a6b3718 2129 utils extra python-cdo_1.2.1-1.debian.tar.gz 5954c62eb015c5fff9e5367c89c4d486 7298 python extra python-cdo_1.2.1-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQ9zPHAAoJEN9LdrZRJ3QsXo4QAJSLsJ5zXxkap8SKaKwByJAH 05CAQSjlb+EpZb3+a2gNXTeLCMoo6hmcjx3hjaqVxJ4r7q2qrtrYA3cUZROMx2c7 GnwHLFTusvL4hNSk9G+nyLDH4LAOBfGU5Qv3Wni9Vj7nMxtIhsdv3IsNZ1jts2S8 8k4+tzuHGGKJR7rEDpzaWp7zuBaJDO/l4nbu4y0ID+ieuX1jVl6nMZMAdXTZHVCh fqlhWbKm5dF48B458IqWeDutNYpkt3nHirmAAbXMJYx1VOq6Jm4q7oIo0EzjjXLx VgSugoZ3Zn7/XDQzI94VyPZFLEkKE38VJZqe6BTAo2sK2pjau32iVNbVjjVunGB/ Tlaaa3GwGaQkY0DTKzwg5gi1pRF0Sw3/YZ6bgOEG5y1ksxtM1LKwsvpKZzgfICbI ffvOkq8099zCFwlvKZgKjT2NLR34itIUxWl92KfCOnZQ9/bcRzwqvWRhVoqmFzc+ eb9Vz4eb3PPCHjYGauBcjztF23zwd4KUZPQGL/EsX3tjdOIwu2DdNtbaOHJif5yr fBXpdnD11AWGbx7hQIpiZHNCgRKwAXtvy5t2P8eQbArefSvgD8yEwde3wt0J3Iu5 Bfqi0y39TPHnHbLVPYTaubVzrbB+0deCDxB+935rPXSnm0Sy4E6SpaDd98tWSI/8 W4AxWprvWNE1fdSgLIuh =w6Bu -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: http://lists.debian.org/e1tvjub-0004n0...@franck.debian.org
Accepted intel-vaapi-driver 1.0.19-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 15 Jan 2013 16:23:59 +0100 Source: intel-vaapi-driver Binary: i965-va-driver i965-va-driver-dbg libva-intel-vaapi-driver libva-intel-vaapi-driver-dbg Architecture: source amd64 all Version: 1.0.19-1 Distribution: experimental Urgency: low Maintainer: Reinhard Tartler siret...@debian.org Changed-By: Matteo F. Vescovi mfv.deb...@gmail.com Description: i965-va-driver - VAAPI driver for Intel G45 HD Graphics family i965-va-driver-dbg - VAAPI driver for Intel G45 HD Graphics family (debug symbols) libva-intel-vaapi-driver - VAAPI driver for Intel G45 HD Graphics family (transitional pac libva-intel-vaapi-driver-dbg - VAAPI driver for Intel G45 HD Graphics family (dbg transitional Changes: intel-vaapi-driver (1.0.19-1) experimental; urgency=low . [ Matteo F. Vescovi ] * New upstream release * debian/control: S-V 3.9.3 = 3.9.4 (no changes needed) * debian/control: Vcs-Git URL updated . [ Reinhard Tartler ] * bump library dependency on libav-dev ( 1.0.16) this is stated as such in the upstream's README Checksums-Sha1: 5e22abe3fc33c7da7094ad20533c2701224ff6ec 1887 intel-vaapi-driver_1.0.19-1.dsc 1daf42a067a4a69d75feeb139c210aa867d5d3f7 631264 intel-vaapi-driver_1.0.19.orig.tar.gz e25708ab286293f31a2cd90dc82202f876a7d216 5912 intel-vaapi-driver_1.0.19-1.debian.tar.gz dd5c1e55b7cd23472b5c735be0dd5a1b5a0055d4 198546 i965-va-driver_1.0.19-1_amd64.deb d33a15032039b969d5935962c7ba64e4b963ecc1 410310 i965-va-driver-dbg_1.0.19-1_amd64.deb 2d233e276fe146e82391b1ab67dee045ab16e0c6 5882 libva-intel-vaapi-driver_1.0.19-1_all.deb d8188820a295e316e609038c119836a3ceb1ca69 5924 libva-intel-vaapi-driver-dbg_1.0.19-1_all.deb Checksums-Sha256: 26023320ec57e0a83cdb77e092353e2672dc11a4235af8da3b7198d14305d7e9 1887 intel-vaapi-driver_1.0.19-1.dsc 0b05383784a23b68791167793fbbf4bd8a676d5361a1bccae5e67716216d8f0a 631264 intel-vaapi-driver_1.0.19.orig.tar.gz fba640ee76880ef1578f7bf73853e56a727c84b0ff60cb253dd9c3d3420e2d63 5912 intel-vaapi-driver_1.0.19-1.debian.tar.gz 43e7abc0625e496d0b5011e8be45f6a0fecbc6bb262b1f96281de344aec47a1e 198546 i965-va-driver_1.0.19-1_amd64.deb fa77f65a7ae05402671625b411cbbd5ec9ac66f684fbbd102238be2829d4eb5b 410310 i965-va-driver-dbg_1.0.19-1_amd64.deb a2de36d06e82a2f5daa0bcd2f5b87404a91d5db90fb7f9a346d8cfe8c6109790 5882 libva-intel-vaapi-driver_1.0.19-1_all.deb 45d126983d4e35f03ca63bb44eccd187b7b0f3bde58fafc78a6c25d64971947d 5924 libva-intel-vaapi-driver-dbg_1.0.19-1_all.deb Files: 8b1a3fc26d7ae8bce97ffb08b4c1b999 1887 libs optional intel-vaapi-driver_1.0.19-1.dsc 41d030498f75161506986a86ef2f3ec5 631264 libs optional intel-vaapi-driver_1.0.19.orig.tar.gz 59a2bfc486137bb2432e34c3fe210fe9 5912 libs optional intel-vaapi-driver_1.0.19-1.debian.tar.gz 88247a17fdf338c19a34e032b8965680 198546 libs optional i965-va-driver_1.0.19-1_amd64.deb 57769360e09a1f26063d0bc31def108f 410310 debug extra i965-va-driver-dbg_1.0.19-1_amd64.deb 0e329a6b1d7d8a73ad4f2a08cfc01526 5882 oldlibs extra libva-intel-vaapi-driver_1.0.19-1_all.deb 0e7639490ce7376f54ce5fa683113678 5924 oldlibs extra libva-intel-vaapi-driver-dbg_1.0.19-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Debian Powered! iEYEARECAAYFAlD3qicACgkQmAg1RJRTSKSVCQCggBpiVRN3uPyygOpZTWlURRbp nDgAn0TzRRyhkcKC71iGGQovH1bNXtHm =tF7T -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: http://lists.debian.org/e1tvkcf-0002dl...@franck.debian.org
