date:20120518

On Fri, May 18, 2012 at 09:24:04AM +0200, Bernd Zeimetz wrote:
 On 05/17/2012 04:52 PM, Gergely Nagy wrote:
  I'm confused concerning the above; the point of a VCS in this context is 
  to 
  track changes to the source package, and the patches are themselves 
  important 
  changes to the source package.  If you have Git ignore the patches then 
  Git 
  doesn't have a complete view of the source package anymore.  Why would you 
  want to do that?
  
  Git does have a complete view. What the above does, is tell dpkg-source
  to fold any changes made to the upstream sources into a single
  patch. Since the git tree already has the patches applied (with upstream
  sources on a different branch, most probably), it has a full view.
  
  This basically folds whatever patches the git tree has over upstream,
  outside of debian/ into a single file. That's about it. Since that file
  is generated, it has no business staying in git.
 
 Doing that is the most stupid idea ever. All it does is to ensure that you
 package can't be NMUed sanely and that people who need to work with the 
 sources
 and your patches for whatever reason have to clone your git, which might be 
 not
 available or just too large for them to download - so at the end changes are
 high that they end up with a largish unreadable patch, similar to the mess we
 get from Ubuntu sometimes.
 The only thing that makes sense would be to use git-format-patch to export 
 your
 patches to debian/patches and list them in the series file. Or use gbp-pq, 
 which
 was made exactly for that.

Uhm, please switch around git and quilt, and say that again.

Quilt is a kind of really primitive VCS.  It does not make sense to use both
it and a modern one, and when someone tries, this ends up with no end of
woe.  Quilt sprinkles its modifications around the source, breaks timestamps
causing unnecessary rebuilds, breaks basic VCS abilities like bisection,
makes it really hard to even review history, and so on.

You complain about forcing people to use git, while you push quilt onto
everyone else.  And while git can do every single thing quilt can do, the
reverse is thoroughly untrue.

I really wish there was a 3.0 format besides 3.0 (quilt), so people are
not mislead into thinking they have to (or even, would gain anything) from
writing patches in quilt's format.

-- 
“This is gonna be as easy as cheating on an ethics exam!”
-Cerise Brightmoon


signature.asc
Description: Digital signature

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

2012-05-18 Thread Tollef Fog Heen

]] Igor Pashev 

 What about stable release? Git branches?

Sure.  Branches are cheap.

 What about users who want rebuild a package (probably with new patches)?

They'll then just grab the git tree, apply their patches, build their
package.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87y5opssq1@qurzaw.varnish-software.com

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

2012-05-18 Thread Andrew Shadura

Hello,

On Fri, 18 May 2012 11:37:08 +0200
Adam Borowski kilob...@angband.pl wrote:

 Quilt is a kind of really primitive VCS.  It does not make sense to
 use both it and a modern one, and when someone tries, this ends up
 with no end of woe.  Quilt sprinkles its modifications around the
 source, breaks timestamps causing unnecessary rebuilds, breaks basic
 VCS abilities like bisection, makes it really hard to even review
 history, and so on.

I'm sorry to disappoint you, but quilt isn't a VCS at all. It's a patch
queue management system, and it does its job well. And, by the way, git
can't do it better at the moment as guilt seems to be dead, and stgit
is buggy (mq in mercurial is better than quilt, but we speak of git
atm).

Keeping patches in git makes thing less transparent and more
complicated. You have to inspect all the history just to find out what
changes did maintainer do to the original source. And, of course, you
need to have a clone of the repo.

 You complain about forcing people to use git, while you push quilt
 onto everyone else.  And while git can do every single thing quilt
 can do, the reverse is thoroughly untrue.

No, it can't. Please check what git, and what quilt is. They are
different tools for different purposes and they can't do each other's
job well enough.

-- 
WBR, Andrew


signature.asc
Description: PGP signature

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

2012-05-18 Thread Michal Suchanek

Excerpts from David Kalnischkies's message of Thu May 17 18:21:59 +0200 2012:
 On Thu, May 17, 2012 at 3:16 PM, Michal Suchanek
 michal.sucha...@ruk.cuni.cz wrote:
  Excerpts from Ian Jackson's message of Thu May 17 14:53:30 +0200 2012:
  Michal Suchanek writes (Re: Bug#671503: general: APT repository format is 
  not documented):
   Excerpts from Filipus Klutiero's message of Wed May 16 18:44:21 +0200 
   2012:
Could you clarify how this differs from #481129?
  
   It's 4 years later.
  
   Sorry, forgot that I filed the bug already. It's quite some time.
  
   Given there is no feedback in 4 years I guess it is futile reporting
   this.
 
  Well, it's useful to bring it up again.
 
   Admittedly there is no text in social contract about using
   Debian-proprietary formats. And a format only defined by apt can read
   that is definitely Debian-proprietary there is no better term for that.
 
  Everyone agrees that it would be better if this were documented.
  (I have struggled on occasion myself due to the lack of
  documentation.)
 
  But I think the use of the word proprietary is going too far.  It's
  certainly a special Debian format, but that wouldn't be changed if it
  were documented.  But it's not secret and we publish at least two
  writer implementations and one reader implementation AFAIK, with
  proper Free licences.
 
  However, it's easier to reverse-engineer  an existing repository than
  the source code so for all practical purposes it's the same as if it
  were closed source.
 
 That is non-sense. You said yourself that the repository is not sufficient
 to understand it, yet you say that it is easier to understand with it than
 with looking at the source (and the various bits and pieces where parts
 are documented).

No, understanding the repository (or current apt source) is not
sufficient to ensure that your repository will be readable by future apt
or that future repositories will not become unreadable by your apt
without any warning or explanation.

Both has happened.

 But I don't know why we are still talking here. Russ already said he would
 like to have it as a subpolicy in the debian-policy. ftpmasters already said
 they would accept maintaining it. Everything left is writing this goddamn
 piece of documentation. So, maybe you should just write it…
 If you want to be extra fancy, start a wikipage in the debian wiki,
 but start typing. Go to debian-dak@l.d.o and discuss your work there.

That would be awesome.

Maybe he just forgot to CC this bug as well?

 
 Would be way more productive than talking about that this document is missing…
 Everbody knows that. Everybody doesn't like it. Now go and fix that.
 That everyone would like to have such a document but nobody has it so far
 is a strong indication that the current people are busy with other stuff.
 An opportunity to get involved, I would say.
 

As said earlier, just writing a random document does not make apt not
diverging from it.

   I'd say it's slightly discriminatory against software not part of Debian
   that cannot rely on getting notified when apt can read that silently
   changes, there is no document defining what apt should be able to read
   that software authors can rely on to interoperate with apt, one of the
   core Debian tools. Apt in turn relies on open standards like HTTP and
   FTP to interoperate with the rest of the world.
 
  I think this is not an appropriate use of the social contract or its
  concepts.
 
  Rather than complaining that this documentation doesn't exist, how
  about writing the document yourself ?  It's not a trivial job but it
  should be feasible by looking at the apt source code.
 
  For me it is not feasible at all.
 
  I can, of course, describe what current repositories look like or what
  the current apt code accepts.
 
  However, that has silently changed in the past and is considered apt
  feature, not a bug.
 
 It hasn't silently changed. It was and is still the same. Your script was
 just horribly wrong and older APT versions just happened to work with
 that brokenness a little better. What you created with that script was NEVER
 intended to work, it just happened to be working out of complete luck
 (A Release file is supposed to include current data, not non-existent
  data, this conclusion is reachable even without too much guessing.
  Beside that this is actually documented in apt-secure and co, but that is
  the problem with most of the documentation, nobody really reads it even
  if it exists… which in the specific case of the Release file is even
  translated to a few languages -- i am to lazy to look it up now…).

My script did exactly what apt-secure says. Well, at least so much as
apt-secure is specific bout it. And the data was existing and well
recognized by apt so it passed all available tests.

 
 At the time you reported that bug i also told you what was wrong in that
 script and how to fix it if you want to continue to use that script, so
 please don't

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

Michal Suchanek michal.sucha...@ruk.cuni.cz writes:

 Excerpts from Ian Jackson's message of Thu May 17 14:53:30 +0200 2012:
 Michal Suchanek writes (Re: Bug#671503: general: APT repository format is 
 not documented):
  Excerpts from Filipus Klutiero's message of Wed May 16 18:44:21 +0200 2012:
   Could you clarify how this differs from #481129?
  
  It's 4 years later.
  
  Sorry, forgot that I filed the bug already. It's quite some time.
  
  Given there is no feedback in 4 years I guess it is futile reporting
  this.
 
 Well, it's useful to bring it up again.
 
  Admittedly there is no text in social contract about using
  Debian-proprietary formats. And a format only defined by apt can read
  that is definitely Debian-proprietary there is no better term for that.
 
 Everyone agrees that it would be better if this were documented.
 (I have struggled on occasion myself due to the lack of
 documentation.)
 
 But I think the use of the word proprietary is going too far.  It's
 certainly a special Debian format, but that wouldn't be changed if it
 were documented.  But it's not secret and we publish at least two
 writer implementations and one reader implementation AFAIK, with
 proper Free licences.

 However, it's easier to reverse-engineer  an existing repository than
 the source code so for all practical purposes it's the same as if it
 were closed source.

 
  I'd say it's slightly discriminatory against software not part of Debian
  that cannot rely on getting notified when apt can read that silently
  changes, there is no document defining what apt should be able to read
  that software authors can rely on to interoperate with apt, one of the
  core Debian tools. Apt in turn relies on open standards like HTTP and
  FTP to interoperate with the rest of the world.
 
 I think this is not an appropriate use of the social contract or its
 concepts.
 
 Rather than complaining that this documentation doesn't exist, how
 about writing the document yourself ?  It's not a trivial job but it
 should be feasible by looking at the apt source code.

 For me it is not feasible at all.

 I can, of course, describe what current repositories look like or what
 the current apt code accepts.

 However, that has silently changed in the past and is considered apt
 feature, not a bug.

 
 Once such a document exists, even if it's a bit sketchy or perhaps not
 entirely accurate, it will be much easier to insist that future
 changes are likewise documented.

 I am not so sure about that.

 So long as the document merely describes what apt happens to do at the
 moment rather than apt implementing what the document says there is no
 saying this document has any value.

 The status was 'documented' by existing repositories which stopped
 working.

 Thanks

 Michal

I would suggest you look at existing repositories, whatever scraps of
information is in the manuals and maybe a bit at the source and start to
write a documentation. Once you have that offer it for review and other
people can pitch in their bits of knowledge. Getting the current format
documented right shouldn't be that hard if someone just starts.

And once such a document exists it is much easier to get people do
document changes or hit them over the head if they don't.

Remember that you don't have to be 100% right in what you write. You
only need to write a draft to start the process. Getting people to
comment and correct any mistakes you simply don't know about is much
much easier than getting someone else to write the whole thing.

MfG
Goswin


-- 
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/87mx55lqbo.fsf@frosties.localnet

Re: What to do with bug reports against non-existing/removed packages

2012-05-18 Thread Gergely Nagy

Daniel Leidert daniel.leidert.s...@gmx.net writes:

 Hi,

 Our bug tracker contains items for packages, which do (not longer)
 exist. What should happen to them? I see, that it might be a good idea
 to keep them for the case, a package is re-introduced. But this might
 happen only for a few packages. Most of them got removed because newer
 versions were released. What about closing those reports, if an
 RM-request is filed?

This is a hard task, as there's no simple set of rules that would apply
to all bugs. Some were filed against packages that existed at a time,
but got removed without the bug being closed (this often happens when
the source remains, it just stops building a particular binary
package). In this case, the bug should be examined, and either
reassigned if it still applies, or closed (preferably with a version) if
it does not.

Then there are the case of misfiled bugs: bugs filed against packages
that never existed, but were installed from a third party repository
(these should be closed with an appropriate message, urging the
submitter to either contact the third party repo's maintainer, or
upstream, whichever is more applicable); typos in package names, where a
reapply would be best; bugs against packages not yet in the archive (but
either in NEW, or in the archive, but so fresh its not known to the BTS
yet): these should be left alone most of the time, but in certain cases,
it might be a good idea to contact the maintainer, so he'll know about
these reports, as the BTS will not notify him when the package enters
the archive. If he doesn't check the BTS page, but relies on email, he
won't know about the reports.

There are probably a few other corner cases, but as you can see, it's
not simple. That's why the list is so long still. On and off, a few
people (myself included) try to shorten a bit, and so far, it seems we
can handle the newly misfiled bugs.

Any help with getting the backlog down to a much smaller number would be
greatly appreciated. Updating the wiki[1] with guidelines and HOWTOs on
how to handle specific cases would also be desirable, and I'm happy to
help with either.

 [1]: http://wiki.debian.org/Teams/unknown-package/TODO

-- 
|8]


-- 
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/87mx55n5ho.fsf@algernon.balabit

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

2012-05-18 Thread Ian Jackson

CC'ing the apt list de...@lists.debian.org.

Goswin von Brederlow writes (Re: Bug#481129: Bug#671503: general: APT 
repository format is not documented):
 Michal Suchanek michal.sucha...@ruk.cuni.cz writes:
  [ discussions regarding documenting the apt repository format ]
 
 I would suggest you look at existing repositories, whatever scraps of
 information is in the manuals and maybe a bit at the source and start to
 write a documentation. Once you have that offer it for review and other
 people can pitch in their bits of knowledge. Getting the current format
 documented right shouldn't be that hard if someone just starts.

Right.

 And once such a document exists it is much easier to get people do
 document changes or hit them over the head if they don't.

Can the apt maintainers confirm that once such a document exists, they
will insist that future contributions to apt which change the
repository format update the document ?

What form do the apt maintainers think the document should take ?
Should it eventually be in the apt source package or somewhere else ?

 Remember that you don't have to be 100% right in what you write. You
 only need to write a draft to start the process. Getting people to
 comment and correct any mistakes you simply don't know about is much
 much easier than getting someone else to write the whole thing.

Indeed so.

Thanks,
Ian.


-- 
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/20406.11351.808519.174...@chiark.greenend.org.uk

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

Jon Dowland j...@debian.org writes:

 On Wed, May 16, 2012 at 12:38:49PM +0200, Adam Borowski wrote:
 It is true that 3.0 (quilt) does have a great downside, quilt, but it also
 has a number of upsides.  And working around quilt is simple:
 
 echo single-debian-patch debian/source/options
 echo /.pc .gitignore
 echo /debian/patches .gitignore

 Thanks for the recipes for avoiding the quilt stuff; whilst still more work
 than just use 1.0, but perhaps the advantages are indeed worth it. (Esp.
 in light of the talk re: xz compression.)

For me a huge advantage is that .hg and .git files are properly ignored
when building source packages. Not to mention multiple upstream
tarballs and support for adding binary files (think debian icon).

 Except for nuking upstream debian/ dir which can mean a bit of lost work if
 the upstream is sane (and can save some if they're not), the 3.0 format is
 strictly better than 1.0.

 I had to go away and read up on the other things 3.0 brings to the table.
 Indeed they are nice-to-haves, which I am not benefiting from precisely 
 because
 they are presently only available in Debian via 3.0 (quilt).  This is a bit of
 a marketing fail for 3.0., in hindsight.

I think one large problem is that people don't know how to make 3.0
(quilt) format play nice with RCS systems and their own worflows. This
is something that has only evolved recently as more people have used 3.0
(quilt) format with their favourite RCS and workflow and the surrounding
tools have adapted.

MfG
Goswin


-- 
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/87ehqhlor2.fsf@frosties.localnet

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

On Wed, May 16, 2012 at 07:45:24PM -0700, Russ Allbery wrote:
 Charles Plessy ple...@debian.org writes:
 
  Also, it is very sad that, as a project, we can not decide whether we go
  for 3.0 (git) or not, or have a concrete list of resolvable objections
  from the people whose work is direclty impacted by the use of this
  format.
 
 We know what a primary concrete objection is.  We discussed it at length
 at DebConf two years ago, and then on debian-devel afterwards.  Uploading
 a Git archive requires reviewing the entire contents of the archive, not
 just the current code, for licensing issues, which is pretty painful from
 the ftp-master perspective.

How come?  If the .git directory shipped in the package is pruned, there is
no hidden data.  All you have to review are commits that are present there,
which is exactly the same as with quilt: you need to review the tarball and
every single patch.

 There was never really a satisfactory resolution to that discussion.  We
 can upload very shallow clones, but they end up looking a lot like the
 existing quilt format with single-debian-patch,

There's a whole world between shallow clones and complete ones.  While
existing git porcelain provides no convenient tools to selectively
shallowify a repository, this is because no one had that need before.

For example, if you limit yourself to a bunch of linear rebased commits atop
of the newest upstream tag, you can exactly emulate quilt workflow except
for not having to deal with quilt's peculiarities.  This goes to the point
of shipping EXACTLY the same data as quilt would, with only metadata
different[1].  And unlike what you say, commits are not flattened in any
way.

If we allow non-linear Debian changes (ie, merged not rebased, etc), there
is indeed a complex question: where to cut[2].  But even then, a given commit
is either present or not.  If too much old history is there, that's no
different from the upstream shipping an old tarball and a pile of patches
upon it (like ancient apache or qmail).

And besides, what's the reason behind enforcing exactly one upstream and
exactly one Debian?  This just leads to problems if either side has
multiple layers.

 and it's not horribly
 clear what the advantages of 3.0 (git) are at that point.  Many of the
 really compelling use cases for 3.0 (git), neat stuff like possibly being
 able to just push a signed tag instead of uploading or having the package
 history when you get the source package, aren't very interesting with
 shallow clones.

It's more a psychological issue: while you can use 3.0 (quilt) to emulate
1.0, people don't know about that.  Even though 6500 of packages in Debian
store their packaging in git, they typically fight with quilt, while that
shallow copy = single-debian-patch would at least remove that concern.


[1]. Git keeps references to commits not present in the shallow repository.
3.0 (quilt) in turn partially and inconsistently preserves timestamps, but
only on files that haven't been modified in any of the patches.  Also, the
tarball may ship an empty directory, device nodes, named pipes, etc --
again, only as long as no patch touches them.

[2]. One way: cut all commits which don't have one of current upstream
tarballs as an ancestor.  This can sometimes cut more than one would want,
but is strictly better than a shallow copy.

-- 
“This is gonna be as easy as cheating on an ethics exam!”
-Cerise Brightmoon


signature.asc
Description: Digital signature

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

Chris Knadle chris.kna...@coredump.us writes:

 On Wednesday, May 16, 2012 06:38:49, Adam Borowski wrote:
 On Tue, May 15, 2012 at 10:10:28AM +0100, Jon Dowland wrote:
  On Tue, May 15, 2012 at 03:17:17PM +0900, Norbert Preining wrote:
   No, I hereby start saying good by to 3.0
  
  I'm hoping we can revisit 3.0 (git) post-squeeze, myself. But I have also
  found myself to be incompatible iwth 3.0 (quilt) and used 1.0 for my last
  few packages.
 
 I can't see any reason to use 1.0 anymore, ever.
 
 It is true that 3.0 (quilt) does have a great downside, quilt, but it also
 has a number of upsides.  And working around quilt is simple:
 
 echo single-debian-patch debian/source/options
 echo /.pc .gitignore
 echo /debian/patches .gitignore

 I'm confused concerning the above; the point of a VCS in this context is to 
 track changes to the source package, and the patches are themselves important 
 changes to the source package.  If you have Git ignore the patches then Git 
 doesn't have a complete view of the source package anymore.  Why would you 
 want to do that?

You're source VCS would be with the patches applied already. When
building the source package dpkg-source will simply create
debian/patches/debian-changes as the diff between your working directory
and the orig tarball every time. Same as it did create a diff.gz file
with 1.0 format.

 and perhaps rm -rf .pc debian/patches in the clean target if those bother
 you -- and you have all the goodies that come with the 3.0 format, with
 getting none of quilt brain damage onto you.  Suddenly, nothing conflicts
 with the VCS you're using, nothing breaks bisects, nothing causes spurious
 recompiles, etc.
 
 Except for nuking upstream debian/ dir which can mean a bit of lost work if
 the upstream is sane (and can save some if they're not), the 3.0 format is
 strictly better than 1.0.

 If debian/ is nuked then so is debian/patches, and if Git has been told to 
 ignore debian/patches then it cannot bring those files back.  Patching the 
 source can be an effort especially concerning documenting why the patches 
 were 
 done and the source of the patches, so these seem like they'd be important to 
 track rather than something to ignore.

Small misunderstanding here.

If you have a 1.0 format package that contains debian/ in the orig
tarball then the diff.gz will contain only the changes to the debian
dir.

In 3.0 (quilt) the debian dir is ignored when unpacking an orig tarball
and the debian tarball contains the full debian dir. The benefit is that
you do no longer need to repack the orig tarball to remove files from
the debian dir and changes upstream does to the debian dir are
ignored. The drawback is that changes upstream does to the debian dir
are ignored.

MfG
Goswin


-- 
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/87aa15lodn.fsf@frosties.localnet

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

On Fri, May 18, 2012 at 12:02:47PM +0100, Ian Jackson wrote:
 CC'ing the apt list de...@lists.debian.org.
 
 Goswin von Brederlow writes (Re: Bug#481129: Bug#671503: general: APT 
 repository format is not documented):
  Michal Suchanek michal.sucha...@ruk.cuni.cz writes:
   [ discussions regarding documenting the apt repository format ]
  
  I would suggest you look at existing repositories, whatever scraps of
  information is in the manuals and maybe a bit at the source and start to
  write a documentation. Once you have that offer it for review and other
  people can pitch in their bits of knowledge. Getting the current format
  documented right shouldn't be that hard if someone just starts.
 
 Right.
 
  And once such a document exists it is much easier to get people do
  document changes or hit them over the head if they don't.
 
 Can the apt maintainers confirm that once such a document exists, they
 will insist that future contributions to apt which change the
 repository format update the document ?
 
 What form do the apt maintainers think the document should take ?
 Should it eventually be in the apt source package or somewhere else ?

I do not think that APT is responsible for the repository format. The
repository format is defined by ftpmaster, not by APT. APT has to my
knowledge not defined anything new, but only implemented changes to
the repository format after they were introduced by ftpmaster (see
InRelease files).

We currently have three independent implementations of the repository
format in the archive: APT, cupt, smartpm. Furthermore, tools like
debian-cd probably also have some knowledge about the repository
format.

The repository format should thus be part of Policy, not part of
APT. APT is one of the users of that format, not the one defining
it (it might just get stricter in behavior from time to time, just
like compilers). Changes to the format should require approval of
ftpmaster, as they have to implement them on the server-side.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.



pgpWPZByoczjc.pgp
Description: PGP signature

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

On Fri, May 18, 2012 at 12:16:40PM +0200, Andrew Shadura wrote:
 On Fri, 18 May 2012 11:37:08 +0200
 Adam Borowski kilob...@angband.pl wrote:
  Quilt is a kind of really primitive VCS.  It does not make sense to
  use both it and a modern one, and when someone tries,
 
 I'm sorry to disappoint you, but quilt isn't a VCS at all. It's a patch
 queue management system, and it does its job well. And, by the way, git
 can't do it better at the moment as guilt seems to be dead, and stgit
 is buggy (mq in mercurial is better than quilt, but we speak of git
 atm).

What would you need guilt or stgit for?  Various invocations of git-rebase
can already do all of that.  -i in particular can do most of that in an
user-friendly way.

 Keeping patches in git makes thing less transparent and more
 complicated. You have to inspect all the history just to find out what
 changes did maintainer do to the original source.

I'm sorry but I fail to see any core differences between quilt and a series
of patches rebased on top of the latest upstream tag.  Except that git's
porcelain has better tools to do that -- just recall recent complains about
unfuzzying patches.  Git will do a 3-way merge during rebasing, which is
more powerful than just copying a patch over as it has more context
(especially, old context vs new context) to work with.

A rebased series is just one way to work with git, but it alone can do
everything quilt can.

 And, of course, you need to have a clone of the repo.

A semi-shallow clone of [upstream_tag .. HEAD] ships exactly as much as
tarball + quilt series.

-- 
“This is gonna be as easy as cheating on an ethics exam!”
-Cerise Brightmoon


signature.asc
Description: Digital signature

Re: debuild/dpkg-buildpackage behaves not as expected

debian-de...@liska.ath.cx (OlÐµ Streicher) writes:

 James McCoy vega.ja...@gmail.com writes:
 On Wed, May 16, 2012 at 04:23:05PM +0200, OlÐµ Streicher wrote:
 Unpatching the sources *before* the build process was cleaned up makes
 no sense to me at all. Could you provide a use case for that?
 As was described in #649531:

   vcs clone repository with unpatched source
   cd repo
   ... tweak a little ...
   dpkg-buildpackage; # applies patches, builds, and unapplies patches
   vcs diff; # looks good?
   vcs commit

 This works only for the special case that build does not change any
 source file. Otherwise you would also commit the changed source files.

And it better not. There is no excuse for changing source files during
build. If you need to change a file then that means that file isn't
source anymore but generated. Try switching to out-of-tree builds if you
have something like that.

 Since for Debian you have only changes in the debian/ subdirectory, you
 may do the following:

 vcs clone repository with unpatched source
 cd repo
  tweak a little ...
 dpkg-buildpackage; # applies patches, builds, and unapplies patches
 vcs diff debian
 vcs commit debian

 this does not require unpatching, since it commits only the debian
 subdirectory, which is not affected by any patches.

 Therefore, I don't see that the workflow you mentioned is a use case
 that would require unpatching.

 [Quoting restored: Goswin wrote]
 What happens if you now call
 debuild patch
 to apply the patches in a 3.0 (quilt) package that has patch/unpatch
 targets?

 because it does *not* leave the sources in the same state.

 Yes, it does.  

 He wrote it himself: patch was meant as a target that *applies* the
 patches. Therefore, it does not leave the sources in the same state
 (since it applies the patches).

I ment: It leaves the source in the same state it found it other than
the side effects the called target(s) have themself.

 If you started with patches applied, then they will still be applied
 after calling dpkg-buildpackage.  If you didn't have patches
 applied, then dpkg-buildpackage will apply the patches, build and
 unapply the patches.

 We discussed the debuild patch option here which was introduced by
 Goswin. 

 Best

 Ole

My main point, which I didn't explicitly state, is this:

The way debuild/dpkg-buildpackage/dpkg-source currently behave allow
maintainers to modify the behaviour by adding something to
debian/rules. If the clean target needs the patches applied then
debian/rules can easily make sure that they are.

On the other hand if the clean target doesn't need the patches applied,
as is the case for 99.9% of all packages then applying them would be
wastefull.


Personaly I try to set up all my packages in such a way that clean or no
clean I can simply commit changes. That means that the build MUST not
modify any source files (which is simply evil to begin with) and that
you add a bunch of stuff to the ignore file (e.g. debian/files,
debian/pkg/, debian/*.debhelper.log, debian/*.substvars, stamp files,
...). That is something you do once and after that clean or no clean you
can simply commit. But that requires that patches are unapplied after
build (unapply-patches in debian/source/local-options to enforce
this). I usualy never call clean directly so the above problem can't
even arise.

MfG
Goswin


-- 
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/8762btlniv.fsf@frosties.localnet

Re: on the use of chmod/chown in maintainer scripts

Roger Leigh rle...@codelibre.net writes:

 On Wed, May 16, 2012 at 02:38:14PM +0200, Goswin von Brederlow wrote:
 That just leaves the question of wether dpkg uses uid/gid or symbolic
 names when unpacking debs.

 I think this one is clear: it must be symbolic since the uids/gids
 aren't static.  Unless you want to provide a package-specific
 mapping in the control data, and I can't see that gains much, since
 it makes unpacking unnecessarily complex.  If it's symbolic, you
 simply just extract it.

Full ACK on symbolic. The question is what dpkg currently does. Do we
need to fix dpkg or is dpkg already ready for this?

MfG
Goswin


-- 
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/871umhlneo.fsf@frosties.localnet

Re: What to do with bug reports against non-existing/removed packages

Daniel Leidert daniel.leidert.s...@gmx.net writes:

 Hi,

 Our bug tracker contains items for packages, which do (not longer) exist. 
 What should happen to them? I see, that it might be a good idea to keep them 
 for the case, a package is re-introduced. But this might happen only for a 
 few packages. Most of them got removed because newer versions were released. 
 What about closing those reports, if an RM-request is filed?

 http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=

 Regards, Daniel

I think for binary packages the bugs should be reassigned to (or at least
keep showing up for) the source package.

For the rest see other replies.

MfG
Goswin


-- 
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/87wr49k8q0.fsf@frosties.localnet

Re: Wheezy release: CDs are not big enough any more...

2012-05-18 Thread Wookey

+++ Mehdi Dogguy [2012-05-16 16:24 +0200]:
 On 16/05/12 13:41, Wookey wrote:
 is there any reason not to just upload this to Debian?
 
 There are ITPs filed for it:
 - http://bugs.debian.org/582884
 - http://bugs.debian.org/576359

Yes. I discovered that when I went to file an ITP :-)

It turns out that there is a problem preventing upload. The rather
generic name 'usb-creator' was objected-to and a request made to
change it to 'startup-disk-creator' (The name the app shows).

Upload seems to be stalled on changing the name of the launchpad
project to give matching source and binary names. This seems
well-meaning but has the unfortunate effect that nothign has happened
for a year, despite several people expressing an interst in uploading.

I also tested it with a debian installer image and found that it is
bust due to a load of ugly code dealing with the syslinux transition
from 2.3x to 2.4x around Ubuntu 10.04-10.10 (generating old images
whilst running on a new machine, and vice versa, different package and
different syntax). It blows up on debian due to 'GNU/Linux' not being
a valid version. As we don't even have syslinux-legacy in Debian all
this mess should probably just be thrown away.
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1000527

My python-foo wasn't up to actually fixing it myself. Nor do I know
how important it is to keep this sort of old-release compatibility
(how old?).

Anyone with the enthusiasm to fix the upstream-renaming thing, or this
code (not hard, just fiddly) could get this into Debian promptly I
think. 

Wookey


-- 
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/20120518121724.gu11...@stoneboat.aleph1.co.uk

Enforce clean before unpatch (was: Re: debuild/dpkg-buildpackage behaves not as expected)

2012-05-18 Thread Thibaut Paumard

Hi,

Le 18/05/12 13:46, Goswin von Brederlow a écrit :
 This works only for the special case that build does not change any
 source file. Otherwise you would also commit the changed source files.
 
 And it better not. There is no excuse for changing source files during
 build. If you need to change a file then that means that file isn't
 source anymore but generated. Try switching to out-of-tree builds if you
 have something like that.

In an ideal world, every file should be either source or generated.
Unfortunately in the real world some build systems modify some source
files. Even though, from our point of view, it would be best to get
upstream fixing this, this is not a reasonable assumption to think that
we can force them to.

Policy states that clean must revert any changes made during build, but
no policy states that no source file must be modified during build.

This is therefore not a reasonable assumption to expect that you can
unpatch before cleaning in the general case.

[...]

 I ment: It leaves the source in the same state it found it other than
 the side effects the called target(s) have themself.

And it's the role of the clean target to revert the changes introduced
by the build and binary targets...

 [...]
 My main point, which I didn't explicitly state, is this:
 
 The way debuild/dpkg-buildpackage/dpkg-source currently behave allow
 maintainers to modify the behaviour by adding something to
 debian/rules. If the clean target needs the patches applied then
 debian/rules can easily make sure that they are.

Tanks, that's certainly the point: Ole and I must have missed the
documentation on this feature. Is it sufficient to make the clean target
depend on patch?

It's also possible that we simply have to dump a line in
debian/source/option to get the -tc option by default. Any pointer to
the right option would be welcome. I did look for it, but then: I can't
even find the butter in the fridge :-)

 [...] That means that the build MUST not
 modify any source files (which is simply evil to begin with) 

Evil is part of this world.

 [...]

Regards, Thibaut.


-- 
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/4fb64390.8040...@free.fr

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

On Fri, May 18, 2012 at 01:38:40PM +0200, Julian Andres Klode wrote:
 On Fri, May 18, 2012 at 12:02:47PM +0100, Ian Jackson wrote:
  CC'ing the apt list de...@lists.debian.org.
  
  Goswin von Brederlow writes (Re: Bug#481129: Bug#671503: general: APT 
  repository format is not documented):
   Michal Suchanek michal.sucha...@ruk.cuni.cz writes:
[ discussions regarding documenting the apt repository format ]
   
   I would suggest you look at existing repositories, whatever scraps of
   information is in the manuals and maybe a bit at the source and start to
   write a documentation. Once you have that offer it for review and other
   people can pitch in their bits of knowledge. Getting the current format
   documented right shouldn't be that hard if someone just starts.
  
  Right.
  
   And once such a document exists it is much easier to get people do
   document changes or hit them over the head if they don't.
  
  Can the apt maintainers confirm that once such a document exists, they
  will insist that future contributions to apt which change the
  repository format update the document ?
  
  What form do the apt maintainers think the document should take ?
  Should it eventually be in the apt source package or somewhere else ?
 
 I do not think that APT is responsible for the repository format. The
 repository format is defined by ftpmaster, not by APT. APT has to my
 knowledge not defined anything new, but only implemented changes to
 the repository format after they were introduced by ftpmaster (see
 InRelease files).
 
 We currently have three independent implementations of the repository
 format in the archive: APT, cupt, smartpm. Furthermore, tools like
 debian-cd probably also have some knowledge about the repository
 format.
 
 The repository format should thus be part of Policy, not part of
 APT. APT is one of the users of that format, not the one defining
 it (it might just get stricter in behavior from time to time, just
 like compilers). Changes to the format should require approval of
 ftpmaster, as they have to implement them on the server-side.
 

A working draft could be something like the following. It mostly
describes the current format for Release, Packages, and Sources
files. It's thus missing Contents and Translations, pdiffs, and
stuff, but it's a beginning.

It specifies different requirements for servers and clients,
in order to have clients be backwards compatible with more
repositories, and forcing servers to be stricter. Don't know
how good that is, though.



= Debian Repository Format =


This documents a subset of the Debian repository format. This is a work
in progress.

Release files
===
The file dists/$DIST/Release shall contain meta-information about the
distribution and checksums for the indices. The file dists/$DIST/Release.gpg
shall be an GPG signature of the Release file, compatible with the format
used by the GPG options -a -b -s. The file dists/$DIST/InRelease shall be
the Release file with a GPG clearsign signature  compatible with the format
used by the GPG options -a -s --clearsign.

The following fields might be available:

- Origin
- Label
- Suite
- Codename
- Date
- Valid-Until
- Architectures
- Components
- Description
- MD5sum, SHA1, SHA256
- NotAutomatic and ButAutomaticUpgrades

Servers shall provide the Release file, and its signed counterparts with at
least the following keys:

- SHA256
- Origin
- Suite and/or Codename
- Architectures

Clients shall accept missing Release files, and Release files without the
fields required for servers. They might reject Release files that do not
contain at least one of the fields defined herein.

Architectures
-
Whitespace separated unique single words identifying Debian machine 
architectures
as described in Architecture specification strings, Section 11.1.

Origin
--
Shall indicate the origin of the repository.

Label
-
Optional field including some kind of label.

Suite
-
The Suite field shall describe the suite. In Debian, this shall be one of
oldstable, stable, testing, unstable, or experimental; with optional suffixes
separated by - (such as stable-updates).

Codename

The Suite field shall describe the codename of the release. This is mostly
a free-form string used to give a name to a release.

Date, Valid-Until
-
The Date field shall specify the time at which the Release file was created. The
Valid-Until field shall specify at which time the Release file should be
considered expired by the client. Client behaviour on expired Release files
is unspecified.

Components
---
A whitespace separated list of areas.

Example:
Components: main contrib non-free

MD5sum, SHA1, SHA256

Those fields shall be multi-line fields containing multiple lines of whitespace
separated

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

2012-05-18 Thread Roger Leigh

On Fri, May 18, 2012 at 01:27:50PM +0200, Adam Borowski wrote:
 On Wed, May 16, 2012 at 07:45:24PM -0700, Russ Allbery wrote:
  Charles Plessy ple...@debian.org writes:
  
   Also, it is very sad that, as a project, we can not decide whether we go
   for 3.0 (git) or not, or have a concrete list of resolvable objections
   from the people whose work is direclty impacted by the use of this
   format.
  
  We know what a primary concrete objection is.  We discussed it at length
  at DebConf two years ago, and then on debian-devel afterwards.  Uploading
  a Git archive requires reviewing the entire contents of the archive, not
  just the current code, for licensing issues, which is pretty painful from
  the ftp-master perspective.
 
 How come?  If the .git directory shipped in the package is pruned, there is
 no hidden data.  All you have to review are commits that are present there,
 which is exactly the same as with quilt: you need to review the tarball and
 every single patch.

I think this is a key point.  The aim of the git format should not be
provide the entire history, any more than the other formats do (not).

What should be provided needs to be
- sufficient to build the package
- sufficient to determine the changes made between the Upstream
  release and the Debian upload
- sufficient to allow further uploads, including NMUs
- (allow restoration of the full history)

  There was never really a satisfactory resolution to that discussion.  We
  can upload very shallow clones, but they end up looking a lot like the
  existing quilt format with single-debian-patch,
 
 There's a whole world between shallow clones and complete ones.  While
 existing git porcelain provides no convenient tools to selectively
 shallowify a repository, this is because no one had that need before.
 
 If we allow non-linear Debian changes (ie, merged not rebased, etc), there
 is indeed a complex question: where to cut[2].  But even then, a given commit
 is either present or not.  If too much old history is there, that's no
 different from the upstream shipping an old tarball and a pile of patches
 upon it (like ancient apache or qmail).

If the git repo contain two tags, maybe signed, one which uniquely
referenced the upstream version, and one which referenced the debian
version, then all commits not part of the graph between these two
commits could be dropped.  This would preserve all history of
branching and merging between these two points.  Tools used for
importing upstream tarballs could automatically create such tags;
native git projects can do this themselves.  These tags could be
put in the .dsc, so that projects can use their own naming rules,
or dpkg-source could use a specific method. [As an upstream who uses
signed tags for all releases, the flexibility to use the project-
specific tags would be useful.]

dak could check that the upstream tag referenced the same commit
between uploads, as well as maybe also verifying the tag signature.
This would ensure that the upstream source couldn't be altered in
an upload, the same as is enforced for orig.tar right now.
dak could also check the debian tag if required; though the .dsc
signature would presumably be sufficient, signed tag verification
would be useful for a potential git-only workflow in the future.

Providing that the packaged repo contains links to the public
git repo, and we can get this from debian/control (in case the
developer is using a private or git+ssh repo), the end user
should be able to do a simple git fetch origin to restore the
full history.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linuxhttp://people.debian.org/~rleigh/
 `. `'   schroot and sbuild  http://alioth.debian.org/projects/buildd-tools
   `-GPG Public Key  F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800


-- 
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/20120518124912.gi22...@codelibre.net

Re: debuild/dpkg-buildpackage behaves not as expected

2012-05-18 Thread Olе Streicher

Goswin von Brederlow goswin-...@web.de writes:
 debian-de...@liska.ath.cx (OlÐµ Streicher) writes:
 James McCoy vega.ja...@gmail.com writes:
 On Wed, May 16, 2012 at 04:23:05PM +0200, OlÐµ Streicher wrote:
 Unpatching the sources *before* the build process was cleaned up makes
 no sense to me at all. Could you provide a use case for that?
 As was described in #649531:

   vcs clone repository with unpatched source
   cd repo
   ... tweak a little ...
   dpkg-buildpackage; # applies patches, builds, and unapplies patches
   vcs diff; # looks good?
   vcs commit

 This works only for the special case that build does not change any
 source file. Otherwise you would also commit the changed source files.

 And it better not. There is no excuse for changing source files during
 build. 

Welcome to reality. Usually, configure scripts are distributed with
(upstream) source on purpose (since they shall provide an easy adoption
to the current enviroment without the need of additional packages), but
they are going to be changed during the packaging.

Another examples are convienence copies of generated files from a parser
generator. Or, sometimes Makefiles are going to be *changed* (not even
regenerated!) by adding/changing dependencies at their end.

Would you really require for all packages using autoconf that they
repackage upstream source in order to get rid of the regenerated files?
And how would you handle the case that a Makefile gets a system
dependent dependency extension?

 If you need to change a file then that means that file isn't source
 anymore but generated. Try switching to out-of-tree builds if you have
 something like that.

What is the advantage of that? From the Debian policy, I don't see a
need why sources should kept untouched during the build process.

 patch was meant as a target that *applies* the patches. Therefore,
 it does not leave the sources in the same state (since it applies the
 patches).

 I ment: It leaves the source in the same state it found it other than
 the side effects the called target(s) have themself.

Why would you need to have a local patch target? If it is somehow
generally useful, it should be common to all packages -- and than it
could just be builtin as an option into dpkg-buildpackage. Or just use
quilt directly.

 My main point, which I didn't explicitly state, is this:

 The way debuild/dpkg-buildpackage/dpkg-source currently behave allow
 maintainers to modify the behaviour by adding something to
 debian/rules. If the clean target needs the patches applied then
 debian/rules can easily make sure that they are.

Since clean usually calls the upstream cleanup, its work depends on
whether the upstream cleanup would actually work on the unchanged
package. Trying to apply the clean target from the unpatched source on
a directory that is built by the patched source seems to me buggy by
design and just works on accident.

 On the other hand if the clean target doesn't need the patches applied,
 as is the case for 99.9% of all packages then applying them would be
 wastefull.

It is just the better design: the package was built with a patched
source, so only the patched version knows for sure how to clean it up. 

 Personaly I try to set up all my packages in such a way that clean or
 no clean I can simply commit changes. That means that the build MUST
 not modify any source files (which is simply evil to begin with) and
 that you add a bunch of stuff to the ignore file (e.g. debian/files,
 debian/pkg/, debian/*.debhelper.log, debian/*.substvars, stamp
 files, ...). That is something you do once and after that clean or no
 clean you can simply commit. But that requires that patches are
 unapplied after build (unapply-patches in debian/source/local-options
 to enforce this).

It does not, as long as you commit just the debian/ subdirectory. Since
*all* changes you make are in this directory, I don't see why this is a
limitation. 

Best regards

Ole

P.S. Would you please not Cc: me as long as you reply to the list?



-- 
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/87txzdlkiv@news.ole.ath.cx

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

On Fri, May 18, 2012 at 01:38:40PM +0200, Julian Andres Klode wrote:
 I do not think that APT is responsible for the repository format. The
 repository format is defined by ftpmaster, not by APT. APT has to my
 knowledge not defined anything new, but only implemented changes to
 the repository format after they were introduced by ftpmaster (see
 InRelease files).

OK, we actually do have some more extensions not used by Debian or
Ubuntu. One of those is the Important: yes field, which is like
Essential, but does not force installation of the package like
Essential would do (and does not force immediate configuration
nowadays, so that we can use it for custom meta packages [so
that users cannot accidentally remove the meta package that
configures the complete system]).

I don't know of any other extensions, though. In any case,
they should probably not be part of an official specification,
but rather documented in APT.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.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/20120518144739.ga21...@debian.org

Re: What to do with bug reports against non-existing/removed packages

2012-05-18 Thread Manuel A. Fernandez Montecelo

Hi,

2012/5/18 Daniel Leidert daniel.leidert.s...@gmx.net:
Hi,

Our bug tracker contains items for packages, which do (not longer) exist.
What should happen to them? I see, that it might be a good idea to keep them
for the case, a package is re-introduced. But this might happen only for a
few packages. Most of them got removed because newer versions were released.
What about closing those reports, if an RM-request is filed?

http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=

As others have said, I asked the question only a few weeks ago:

http://lists.debian.org/debian-devel/2012/03/msg00946.html

Reassigning 300 bugs from emacsX (X23) to current emacs packages is
not very helpful, really. What I did is to notify the maintainers (or
related mailing lists) of the three biggest groups (linux, gcc, emacs)
to decide what to do.

Ben Hutchings took care of the ones of the kernel, I'm especially
focusing on the ones of GCC right now (trying to reproduce, closing or
reassigning when appropriate), and the same with emacs ones (but I did
only one session of those or so, closing some tagged fixed-upstream).
I also handled other reports here and there from other packages.

I'm thinking that the fix one orphan bug before posting to
debian-devel@ flame threads would be helpful here :-)

Don't know what to suggest, really, but it's a shame that some very
helpful bug reports are lost in this process for Debian. The are many
good bug reports about GCC, e.g. incorrect optimisations or wrong code
in some architectures that were closed so close as 1 month ago (so
they are not part of 4.7, they will be in 4.8), and which were
reported in Debian (and forwarded upstream by Debian maintainers) many
many years ago. Some similar ones reported years ago are still not
forwarded, but I haven't yet handled them to see if they are valid,
reproducible or what (#448370, #470557).

So I wouldn't blindly close those bug reports, and that's why I'm
triaging and handling them in my spare time.

Cheers.

--
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/CAPQ4b8mZzsSt=mfgko-3jsqtvsprd7kay57vwkdvktgvfnh...@mail.gmail.com

Re: switching from exim to postfix

2012-05-18 Thread Henrique de Moraes Holschuh

On Thu, 17 May 2012, Thomas Goirand wrote:
 On 05/03/2012 07:23 AM, Henrique de Moraes Holschuh wrote:
  Well, FWIW postfix allows you to override all MTA notifications, not just
  bounce messages, but the full set.  We do that at work.

 Interesting. Can you post an example here?

man bounce(8postfix).  You need recent postfix, so that means backports,
testing or unstable.

We keep the original text in english at the bottom, but add text in
portuguese on top.

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120518134839.gd...@khazad-dum.debian.net

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

2012-05-18 Thread Henrique de Moraes Holschuh

On Fri, 18 May 2012, Adam Borowski wrote:
 On Fri, May 18, 2012 at 12:16:40PM +0200, Andrew Shadura wrote:
  On Fri, 18 May 2012 11:37:08 +0200
  Adam Borowski kilob...@angband.pl wrote:
   Quilt is a kind of really primitive VCS.  It does not make sense to
   use both it and a modern one, and when someone tries,
  
  I'm sorry to disappoint you, but quilt isn't a VCS at all. It's a patch
  queue management system, and it does its job well. And, by the way, git
  can't do it better at the moment as guilt seems to be dead, and stgit
  is buggy (mq in mercurial is better than quilt, but we speak of git
  atm).
 
 What would you need guilt or stgit for?  Various invocations of git-rebase
 can already do all of that.  -i in particular can do most of that in an
 user-friendly way.

You rebase, that branch is crap that cannot possibly be used by others in
any way that is not (1) error-prone; (2) annoying; (3) at least as
troublesome as quilt (IMHO it is much worse than quilt).  Have you ever been
downstream from someone that publishes branches that are rebased all the
time?

But yes, git is *MUCH* better at merging than patch, which would be the
reason why I work on development of patch-based deliverables (anything for
the Linux kernel, and anything that is supposed to make its way upstream)
using the latest development shapshot of stgit instead of quilt.

When it is time to release/upload, the branch gets git format-patch'd, and
makes its way to debian/patches for 3.0(quilt) to handle.  That branch is
never published.  git-pq can automate this stuff in an even better way that
is rebase-less if you want, but I don't bother.

 I'm sorry but I fail to see any core differences between quilt and a series
 of patches rebased on top of the latest upstream tag.  Except that git's

3.0(quilt) doesn't need a full git repository to actually be manipulated.
Since we cannot use 3.0(git) with the full git repository in Debian, IMO
that makes 3.0(git) useless if you're going to use it like that.

You're free to propose that we change the way 3.0(git) is supposed to be
used, and maybe that will require a 3.1(git), or maybe not.  That's probably
where we'll get some value out of this necrotic thread.  Damn, I hate the
stink of dead horse corpses...

It would certainly be possible to define that all that can go in the git
repository is the snapshots uploaded to Debian/Ubuntu.  That DOES mean you
CANNOT use git directly with the upstream repository, you'll need to
transport changes using git format-patch and git-am, or maybe git
cherry-pick from a remote.  I think this will actually be worse for people
to understand than 3.0(quilt), but it does have the advantage that you will
be using git instead of quilt to manipulate the changes.   We'd need a
procedure to deal with uploads fixing cannot be distributed, but it was
problems, and THAT will require rewriting history to get rid of the
offending data.  Which is rather nasty, but doable.

 A rebased series is just one way to work with git, but it alone can do
 everything quilt can.

Indeed.  But shallow clones are not the way (we've debated this already on
a huge technical thread, at least twice).

-- 
  One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie. -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120518140907.ge...@khazad-dum.debian.net

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

2012-05-18 Thread Michal Suchanek

FWIW

posted on the wiki: http://wiki.debian.org/RepositoryFormat

Thanks

Michal


-- 
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/1337349939-sup-8...@virtual.ruk.cuni.cz

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

2012-05-18 Thread Bernhard R. Link

* Adam Borowski kilob...@angband.pl [120518 11:37]:
 You complain about forcing people to use git, while you push quilt onto
 everyone else.
 [...]

 I really wish there was a 3.0 format besides 3.0 (quilt), so people are
 not mislead into thinking they have to (or even, would gain anything) from
 writing patches in quilt's format.

Noone is forcing quilt on anyone.

We need a source format that can properly represent changes to the
upstream source code and that is best done as some series of patches.
Using a format that is a subset of quilt without all the magic makes
sense as that makes it easy for anyone to write or read.
(It's just a set of patches to be applied with -p1 and a file to list
the names of those patches line by line, i.e. no special sort algorithm
for filesnames needs to be defined).

One of the biggest faults of 3.0 (quilt) is its name. It should really
have been called 3.0 (patches) or even better 3.0 (non-native).

A proper package should either have no upstream changes or broken down
changeset that can actually be applied. If you have those changes it is
trivial to create a 3.0 (quilt) source package out of that.

And yes, git is the better quilt for managing a source tree. Which is
why I use it exclusively to work on my 3.0 (quilt) packages.

Bernhard R. Link


-- 
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/20120518145644.gb2...@client.brlink.eu

Re: What to do with bug reports against non-existing/removed packages

2012-05-18 Thread Neil Williams

On Fri, 18 May 2012 14:34:40 +0100
Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote:

 Hi,
 
 2012/5/18 Daniel Leidert daniel.leidert.s...@gmx.net:
  Hi,
 
  Our bug tracker contains items for packages, which do (not longer) exist. 
  What should happen to them? I see, that it might be a good idea to keep 
  them for the case, a package is re-introduced. But this might happen only 
  for a few packages. Most of them got removed because newer versions were 
  released. What about closing those reports, if an RM-request is filed?
 
  http://bugs.debian.org/cgi-bin/pkgreport.cgi?maint=
 
 As others have said, I asked the question only a few weeks ago:
 
   http://lists.debian.org/debian-devel/2012/03/msg00946.html
 
 Reassigning 300 bugs from emacsX (X23) to current emacs packages is
 not very helpful, really.  What I did is to notify the maintainers (or
 related mailing lists) of the three biggest groups (linux, gcc, emacs)
 to decide what to do.

There's a big difference between these bugs and the rest - here there
are clear migration paths to later packages which can be used to triage
the bug reports in order not to lose reports. A lot of the rest *can*
be closed without more triage work because the package was removed, not
replaced. e.g. gcc-4.4 bugs may be applicable with gcc-4.7 and need to
be triaged. The opensync/multisync bugs just had to be closed without
even looking at any of them.

Identifying this subset (which could be quite large) which apply only
to packages which have no appropriate replacement packages would be a
very useful QA step and dramatically improve the total number of bugs
in this situation.

Simplest safeguard here is to ensure that the list of bugs closed in
this way is fed back to a comment in the original bug report against
ftp.debian.org which got the package removed in the first place and
which is the permanent record of the removal.

 Don't know what to suggest, really, but it's a shame that some very
 helpful bug reports are lost in this process for Debian.  The are many
 good bug reports about GCC, e.g. incorrect optimisations or wrong code
 in some architectures that were closed so close as 1 month ago (so
 they are not part of 4.7, they will be in 4.8), and which were
 reported in Debian (and forwarded upstream by Debian maintainers) many
 many years ago.  Some similar ones reported years ago are still not
 forwarded, but I haven't yet handled them to see if they are valid,
 reproducible or what (#448370, #470557).
 
 So I wouldn't blindly close those bug reports, and that's why I'm
 triaging and handling them in my spare time.

Where there are replacement packages, there is work to do. Otherwise,
the bugs need to be closed. The very small number of packages which get
re-introduced after ftpmaster removal don't merit special treatment in
this regard - as long as when the orphaned bugs are closed, some
mention is made of the bug numbers in the bug report at ftp.debian.org.

(If ftp.debian.org gets removed we will have larger problems, or no
problems at all, depending on your perspective.)

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpeomPNC6faJ.pgp
Description: PGP signature

Re: What to do with bug reports against non-existing/removed packages

2012-05-18 Thread Manuel A. Fernandez Montecelo

2012/5/18 Neil Williams codeh...@debian.org:
There's a big difference between these bugs and the rest - here there
are clear migration paths to later packages which can be used to triage
the bug reports in order not to lose reports. A lot of the rest *can*
be closed without more triage work because the package was removed, not
replaced. e.g. gcc-4.4 bugs may be applicable with gcc-4.7 and need to
be triaged. The opensync/multisync bugs just had to be closed without
even looking at any of them.

Yes, I fully agree with that for the packages-removed-for-good.

The thing is that a big % of the initial bugs (1500+ when I brought
this up, 1200+ now) is made up of the gcc like cases: gcc, emacs,
linux, libdb, python2.4, various java stuff, tomcat5.5...

I don't know if they're 30, 50 or 80%, but definitely there is a big
amount of real bugs still related to current software shipped in
Debian.

Another question, perhaps unrelated is, what happens with the bugs
closed from egroupware or salome (removed from unstable/testing but
still present in stable releases) when their users look for them in
the BTS? They would be closed and archived, I suppose, and users of
stable wouldn't be able to find them easily -- and them maybe report
them again.

So at the moment I left those bugs alone. I assume that they will be
autodeleted by some process when they're not present in stable
anymore, but perhaps are wrong and that's why there are such high
number of orphan bugs.

Cheers.

--
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/capq4b8nh+urvcoyz10vpahavoataw5em_1n6y2n-utdpmje...@mail.gmail.com

Re: What to do with bug reports against non-existing/removed packages

2012-05-18 Thread Thomas Preud'homme

Le vendredi 18 mai 2012 17:41:55, Manuel A. Fernandez Montecelo a écrit :
 2012/5/18 Neil Williams codeh...@debian.org:
  There's a big difference between these bugs and the rest - here there
  are clear migration paths to later packages which can be used to triage
  the bug reports in order not to lose reports. A lot of the rest *can*
  be closed without more triage work because the package was removed, not
  replaced. e.g. gcc-4.4 bugs may be applicable with gcc-4.7 and need to
  be triaged. The opensync/multisync bugs just had to be closed without
  even looking at any of them.
 
 Yes, I fully agree with that for the packages-removed-for-good.
 
 The thing is that a big % of the initial bugs (1500+ when I brought
 this up, 1200+ now) is made up of the gcc like cases: gcc, emacs,
 linux, libdb, python2.4, various java stuff, tomcat5.5...
 
 I don't know if they're 30, 50 or 80%, but definitely there is a big
 amount of real bugs still related to current software shipped in
 Debian.
 
 Another question, perhaps unrelated is, what happens with the bugs
 closed from egroupware or salome (removed from unstable/testing but
 still present in stable releases) when their users look for them in
 the BTS?  They would be closed and archived, I suppose, and users of
 stable wouldn't be able to find them easily -- and them maybe report
 them again.

According to [1] salome is not part of any debian release now. Did I miss 
something? IIRW, for package still in stable, if the -done mail contains the 
right version then the bug will still be visible as long as it affects stable.

[1] http://packages.qa.debian.org/s/salome.html

 
 So at the moment I left those bugs alone.  I assume that they will be
 autodeleted by some process when they're not present in stable
 anymore, but perhaps are wrong and that's why there are such high
 number of orphan bugs.
 
 
 Cheers.

Cheers.


signature.asc
Description: This is a digitally signed message part.

Re: What to do with bug reports against non-existing/removed packages

2012-05-18 Thread Manuel A. Fernandez Montecelo

2012/5/18 Thomas Preud'homme robo...@celest.fr:
 According to [1] salome is not part of any debian release now. Did I miss
 something? IIRW, for package still in stable, if the -done mail contains the
 right version then the bug will still be visible as long as it affects stable.

Oh yes, egroupware only in oldstable... and I saw some entries of
salome [1] and mistakenly took them for oldstable, not unstable in
some architectures.

http://packages.debian.org/search?keywords=salome

Cheers.


-- 
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/CAPQ4b8=b+SZScVmv+DU_vtVWg+_-q-GbcbJLbQ5tE6Lk=zu...@mail.gmail.com

Re: What to do with bug reports against non-existing/removed packages

2012-05-18 Thread Neil Williams

On Fri, 18 May 2012 16:41:55 +0100
Manuel A. Fernandez Montecelo manuel.montez...@gmail.com wrote:

 Another question, perhaps unrelated is, what happens with the bugs
 closed from egroupware or salome (removed from unstable/testing but
 still present in stable releases) when their users look for them in
 the BTS?  They would be closed and archived, I suppose, and users of
 stable wouldn't be able to find them easily -- and them maybe report
 them again.

Depends on the found version of the bugs. If the bug isn't found in any
version currently in Debian, the bug needs to be closed. It could be
triaged in the previous versions, if people have the time, but that may
well have already happened or someone may have added a comment to the
bug that it affects old releases too.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpRfWwcshipn.pgp
Description: PGP signature

Re: Wheezy release: CDs are not big enough any more...

2012-05-18 Thread Joey Hess

Guillem Jover wrote:
 Only as long as the debian/control information matches the one from
 the archive override.

I checked, and currently the only base package with an overridden priority
is libsigc++-2.0-0c2a

-- 
see shy jo


signature.asc
Description: Digital signature

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

2012-05-18 Thread Bernd Zeimetz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 05/18/2012 11:37 AM, Adam Borowski wrote:
 On Fri, May 18, 2012 at 09:24:04AM +0200, Bernd Zeimetz wrote:
 On 05/17/2012 04:52 PM, Gergely Nagy wrote:
 I'm confused concerning the above; the point of a VCS in this context
 is to track changes to the source package, and the patches are
 themselves important changes to the source package.  If you have Git
 ignore the patches then Git doesn't have a complete view of the
 source package anymore.  Why would you want to do that?
 
 Git does have a complete view. What the above does, is tell
 dpkg-source to fold any changes made to the upstream sources into a
 single patch. Since the git tree already has the patches applied (with
 upstream sources on a different branch, most probably), it has a full
 view.
 
 This basically folds whatever patches the git tree has over upstream, 
 outside of debian/ into a single file. That's about it. Since that
 file is generated, it has no business staying in git.
 
 Doing that is the most stupid idea ever. All it does is to ensure that
 you package can't be NMUed sanely and that people who need to work with
 the sources and your patches for whatever reason have to clone your git,
 which might be not available or just too large for them to download - so
 at the end changes are high that they end up with a largish unreadable
 patch, similar to the mess we get from Ubuntu sometimes. The only thing
 that makes sense would be to use git-format-patch to export your patches
 to debian/patches and list them in the series file. Or use gbp-pq, which 
 was made exactly for that.
 
 Uhm, please switch around git and quilt, and say that again.

No.

 Quilt is a kind of really primitive VCS.  It does not make sense to use
 both it and a modern one, and when someone tries, this ends up with no end
 of woe.  Quilt sprinkles its modifications around the source, breaks
 timestamps causing unnecessary rebuilds, breaks basic VCS abilities like
 bisection, makes it really hard to even review history, and so on.

If you get a cd image with sources nobody cares what the maintainer used to
manage the package. A developer without internet access cares about usable
patches in debian/patches instead of a big, uncommented blob. Quilt is not a
VCS at all, it is a system to apply and unapply a list of patches, nothing more.


 You complain about forcing people to use git, while you push quilt onto 
 everyone else.  And while git can do every single thing quilt can do, the 
 reverse is thoroughly untrue.

See above. To use patches in debian/patches you don't even need quilt. People
might not have access to your famous git repository.


 I really wish there was a 3.0 format besides 3.0 (quilt), so people
 are not mislead into thinking they have to (or even, would gain anything)
 from writing patches in quilt's format.

Quilt doesn't us a special format. You can just go and run git-format-patch to
export patches from git.

If you want people to be able to work with your patches *AND* you don't like
to ship a proper (quilt) set of patches, figure out what needs to be done to
get 3.0 (git) accepted (like automatic removal of branches which are not part
of the packaging, ensuring that source versions which were not distributable
were removed from the repository, and so on...) - then you can happily assume
that people are able to use your git repository as they actually get a copy on 
CD.



- -- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJPtnjHAAoJEOs2Fxpv+UNfQREP/A9Y2Cy6zzd+kQeje8AvjtSQ
VrWJEFwNDcWM/Sf5K6NvccSg+G+8dMjb8XXv9HOJKf9wnSXLLpHTbIAUpTTms71a
HHis4lCIrm6t1HAU7GmQAHwhJKW+z1G52xzzEXC9SHfECCaMERDPgUwrHsO2mujx
qN9ormQufui0SmWUlIvRyNp9S5UtY7Qvq1iNzquK+D/9l8U5sCx8TcxhBmR7L8ZO
8Ncby9dIzvYVUahGXwpOB4am/1VPPJkMIMW+IrpJIXKrpjg8KWXJ5JC1eFOu3PHs
vUBoqm42M9LeFhmcCO2H20aCF9JhoMQkPkqTmQBJEpvtIvo3xm9/SQIm296aGtKS
dWA3Vs3XZCL0+OOxfo0pE46kwxb3M7m327dg2O0mdMtq+NPTh8Xon1E2k4yHVSEe
BBl4o2JRrXEVKj3NnJbT9PbajwzOMzZYuIk0APyWePPfi1j5j6kaZXFBblz6x4H/
+R5PshcVoiX0ZQKmXcOmr1QNDc6XygiS2PCapeQbFURcVBqEvf1ePtqHAendYP+F
1QmIYh5HbKVI+Tkr9962Kd782zJuT2Ja9GeZE40XpxxXiKKI84mVdlNTuUzHXixl
8MIg97VsEOp0LC6K9Oa3vOEObJ+4ln3ZCKUn9npWDZ59+Yt9Fmkw1K3V/NuJFsTS
uYhgNlkRtgPojwfw+L5t
=oQ0Y
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4fb678d5.8040...@bzed.de

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

On Fri, May 18, 2012 at 04:06:23PM +0200, Michal Suchanek wrote:
 FWIW
 
 posted on the wiki: http://wiki.debian.org/RepositoryFormat
 
 Thanks
 
 Michal

I have now documented the Contents indices and the diffs
as well, mostly (sans the exact format we use for the
patches), and Translation indices. Now we're basically
only missing details, it is fairly complete otherwise
(i.e. we should have mentioned every file and field
currently in use, but may not have explained all of
them completely).

We now have documented

dists/$DIST/Release (and InRelease, Release.gpg)
dists/$DIST/$COMP/binary-$ARCH/Packages
dists/$DIST/$COMP/source/Sources
dists/$DIST/$COMP/Contents-$ARCH.gz
dists/$DIST/$COMP/i18n/{Index,Translation-*.bz2}
*.diff/Index *.diff/%Y-%m-%d-%H%M.%S.gz

The other Release files have been omitted, as they are not
used anywhere. We are only missing udeb content files and
packages files now, which are just small subsentences.

In a few months, I'd like to rework this in DocBook form,
and submit it to debian-policy for inclusion into official
Policy, as a sub-policy like copyright-format.


-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.


pgpvMrHdLCzhm.pgp
Description: PGP signature

Re: Wheezy release: CDs are not big enough any more...

2012-05-18 Thread Joey Hess

While this has been an interesting thread, it may be predicated on a
false premise. I examined the latest weekly CD build, and the reason no
desktop tasks at all (even lxde or xfce) appear on their respective CDs
is because debian-cd is simply not including tasksel's new task-*
packages, at all. 

The packages on the CD seem fairly random, including things not in any
task like wmaker, alien, and, on the lxde+xfce CD, lots of KDE, but no
ldxe or xfce.

Even DVD #1 seems broken, containing task-desktop, but not
task-gnome-desktop. I'm sure gnome still fits on a DVD.

Seems likely that things are badly broken in debian-cd's task handling.
Likely related to tasksel's new task-* packages.

The way debian-cd needs to handle the new task packages is this:

* Put task-gnome-desktop on CD#1, task-kde-dekstop on KDE CD #1, etc.
  (No need to use /usr/share/tasksel/descs/debian-tasks.desc anymore.)
* Try to include at all Recommends of task-* packages, not only their
  dependencies, as this is used to pull in the majority of packages for
  tasks. Do this even when normal Recommends inclusion is disabled.
* If space is tight, drop some of the task-* Recommends. And, since
  this needs to be special cased anyway, it would be nice to have an
  option to abort the build, and/or warn if they don't fully fit.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

On Fri, May 18, 2012 at 04:06:23PM +0200, Michal Suchanek wrote:
 FWIW
 
 posted on the wiki: http://wiki.debian.org/RepositoryFormat

What's the opinion about the flat repository format, where you
just have one directory with Release, Packages, Sources, and
friends and no sub-directories?

Should they be documented as well then? We would then have two
kind of documented repository formats:

1. Debian-style, with a pool (or similar) and a dists directory
2. Flat-style, with just one directory

This should cover everything we currently support. Although I don't
know much about how much stuff we support in flat directories WRT
Translation, Contents, and diffs.

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.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/20120518185407.ga15...@debian.org

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

On Fri, May 18, 2012 at 06:45:00PM +0100, Wookey wrote:
 +++ Julian Andres Klode [2012-05-18 13:38 +0200]:
 
  We currently have three independent implementations of the repository
  format in the archive: APT, cupt, smartpm. 
 
 I think reprepro is another?

Of course, I was just only talking about clients. When it comes to
creating we probably have much more than 3 programs needing some
knowledge of the repository format. We have dak, apt-ftparchive,
reprepro, debian-cd, everyone's small script, mini-dinstall (the
latter using flat repositories, if I am not mistaken).
-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.


pgpLQZvyw4KlE.pgp
Description: PGP signature

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

2012-05-18 Thread Wookey

+++ Julian Andres Klode [2012-05-18 13:38 +0200]:

 We currently have three independent implementations of the repository
 format in the archive: APT, cupt, smartpm. 

I think reprepro is another?

/usr/share/doc/reprepro/manual.html contains a 'repository basics'
section which includes useful layout/format information.

Wookey


-- 
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/20120518174500.gf11...@stoneboat.aleph1.co.uk

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

On Fri, May 18, 2012 at 08:12:16PM +0200, Michal Suchanek wrote:
 The formatting is not consistent but that will have to be changed for
 docbook anyway.

Yes, and it will also be more readable then, than the current wiki
version.

 
 Also would need some proof-reading. If nothing else somebody should look
 in a few weeks from now if it still makes sense ;-)

I'd also like to hear bits from the launchpad team about their
implementation and see whether they agree with everything then.


 
 I put a link on the RepositoryHowto page for more exposure.
 
 I am not so sure documenting Debian installer files is tremendously
 useful. I don't think anyone outside Debian Installer team makes Debian
 Installer repositories and there are other aspects of Debian Installer
 that would need to be documented in order for it to be usable for
 'outside' people in non-default configurations.

We still need to at least document the udeb stuff, the images and
other stuff is not relevant to the core format and probably defined
by the d-i team anyway (and installed by-hand).

The udeb stuff is relatively easy to document, as it just adds one
new directory and one new filename for Contents files, so can be
done in about two sentences (and udebs are uploaded by standard
.changes with the rest of the package, and are thus standard).

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.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/20120518201701.ga17...@debian.org

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

2012-05-18 Thread Michal Suchanek

Excerpts from Julian Andres Klode's message of Fri May 18 18:49:10 +0200 2012:
 On Fri, May 18, 2012 at 04:06:23PM +0200, Michal Suchanek wrote:
  FWIW
  
  posted on the wiki: http://wiki.debian.org/RepositoryFormat
  
  Thanks
  
  Michal
 
 I have now documented the Contents indices and the diffs
 as well, mostly (sans the exact format we use for the
 patches), and Translation indices. Now we're basically
 only missing details, it is fairly complete otherwise
 (i.e. we should have mentioned every file and field
 currently in use, but may not have explained all of
 them completely).
 
 We now have documented
 
 dists/$DIST/Release (and InRelease, Release.gpg)
 dists/$DIST/$COMP/binary-$ARCH/Packages
 dists/$DIST/$COMP/source/Sources
 dists/$DIST/$COMP/Contents-$ARCH.gz
 dists/$DIST/$COMP/i18n/{Index,Translation-*.bz2}
 *.diff/Index *.diff/%Y-%m-%d-%H%M.%S.gz
 
 The other Release files have been omitted, as they are not
 used anywhere. We are only missing udeb content files and
 packages files now, which are just small subsentences.
 
 In a few months, I'd like to rework this in DocBook form,
 and submit it to debian-policy for inclusion into official
 Policy, as a sub-policy like copyright-format.
 

Yes, looks fairly complete.

The formatting is not consistent but that will have to be changed for
docbook anyway.

Also would need some proof-reading. If nothing else somebody should look
in a few weeks from now if it still makes sense ;-)

I put a link on the RepositoryHowto page for more exposure.

I am not so sure documenting Debian installer files is tremendously
useful. I don't think anyone outside Debian Installer team makes Debian
Installer repositories and there are other aspects of Debian Installer
that would need to be documented in order for it to be usable for
'outside' people in non-default configurations.

Thanks

Michal


-- 
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/1337363087-sup-4...@virtual.ruk.cuni.cz

Re: What to do with bug reports against non-existing/removed packages

2012-05-18 Thread Alexander Reichle-Schmehl


Hi!

On 18.05.2012 10:50, Paul Wise wrote:


Our bug tracker contains items for packages, which do (not longer) exist. What 
should happen to them? I see, that it might be a good idea to keep them for the 
case, a package is re-introduced. But this might happen only for a few 
packages. Most of them got removed because newer versions were released. What 
about closing those reports, if an RM-request is filed?


ftpmaster already close bugs automatically when processing RM requests.


Not always.  IIRC we only close bugs on removal if:

a) BTS is up and running.
b) source and binary are removed.
c) The package is removed from unstable.
d) The removed package is on sync on all arches. (Because otherwise we 
won't know with which version we'd like to close the bug.)


d) also affects binNMUed packages.


Best regards,
  Alexander


--
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/4fb6a0d2.6000...@schmehl.info

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

2012-05-18 Thread Russ Allbery

Henrique de Moraes Holschuh h...@debian.org writes:

 When it is time to release/upload, the branch gets git format-patch'd,
 and makes its way to debian/patches for 3.0(quilt) to handle.  That
 branch is never published.  git-pq can automate this stuff in an even
 better way that is rebase-less if you want, but I don't bother.

I do this work in cases where keeping the patches separate is useful for
some reason, but mostly it's not.  I therefore use single-debian-patch for
most of my packages, and only use this sort of automation for a very few
where there are lots of upstream changes and some benefit to keeping them
separate.

I'm unwilling to do all this extra work for a theoretical marginal benefit
that only applies to people who aren't using Git.  I'm only willing to do
it when the benefit is not theoretical.  For most of my packages, no one
is going to care, particularly for those where I'm also upstream.

-- 
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/87r4uhcmi8@windlord.stanford.edu

Re: Wheezy release: CDs are not big enough any more...

On Fri, May 18, 2012 at 12:27:15PM -0400, Joey Hess wrote:
 Guillem Jover wrote:
  Only as long as the debian/control information matches the one from
  the archive override.
 
 I checked, and currently the only base package with an overridden priority
 is libsigc++-2.0-0c2a

So, would it be safe to make dpkg-deb default to xz if priority is 
important for wheezy?

My point is, the sooner this change is made, the more of the pre-release
upload spike will benefit from reduced package size.  It can be then changed
by either improving debootstrap (unlikely due to old versions) or the
base-ness check.

Also, lintian currently doesn't complain if a base package uses xz.  Should
it?  This check wouldn't be very useful since priority override is the only
interesting case, though.

-- 
“This is gonna be as easy as cheating on an ethics exam!”
-Cerise Brightmoon


signature.asc
Description: Digital signature

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

2012-05-18 Thread Paul Wise

On Sat, May 19, 2012 at 12:58 AM, Julian Andres Klode wrote:

 What's the opinion about the flat repository format, where you
 just have one directory with Release, Packages, Sources, and
 friends and no sub-directories?

 Should they be documented as well then? We would then have two
 kind of documented repository formats:

        1. Debian-style, with a pool (or similar) and a dists directory
        2. Flat-style, with just one directory

 This should cover everything we currently support. Although I don't
 know much about how much stuff we support in flat directories WRT
 Translation, Contents, and diffs.

I would like to see the flat-style repository documented too, since
some of the derivatives in the Debian derivatives census use it and I
would like to lint their apt repositories.

-- 
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/caktje6gw9k_p_7ch-kzwnsxnpiwdbs3hxu1cyw_qjmgaydh...@mail.gmail.com

Re: on the use of chmod/chown in maintainer scripts

2012-05-18 Thread Raphael Geissert

Hi Peter,

Thanks for bringing up this issue again. Admittedly, there hasn't been much 
progress since it was discussed last year.

Hopefully, the discussion has focused on a solution to completely avoid the 
problem during upgrades.
For the general issue, the only progress I made was in the form of #608623, 
but I haven't spent any time trying to implement lchmod in the kernel.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net


-- 
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/jp6rda$8st$1...@dough.gmane.org

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

2012-05-18 Thread Charles Plessy

Le Wed, May 16, 2012 at 07:45:24PM -0700, Russ Allbery a écrit :
 Charles Plessy ple...@debian.org writes:
 
  Also, it is very sad that, as a project, we can not decide whether we go
  for 3.0 (git) or not, or have a concrete list of resolvable objections
  from the people whose work is direclty impacted by the use of this
  format.
 
 We know what a primary concrete objection is.  We discussed it at length
 at DebConf two years ago, and then on debian-devel afterwards.  Uploading
 a Git archive requires reviewing the entire contents of the archive, not
 just the current code, for licensing issues, which is pretty painful from
 the ftp-master perspective.
 
 There was never really a satisfactory resolution to that discussion.

Hi Russ and everybody,

it is indeed hard to reach conclusions when discussing on high-traffic mailing
lists.

I have attempted to summarise some elements of discussion on wiki.debian.org.
Please let me know if I have misunderstood or misrepresented people's
contributions, and I will correct.  Please of course feel free to correct or
update by yourself.

  http://wiki.debian.org/GitSrc#Discussion

In the case of the initial copryight review, which is if I understand well the
strongest objection, wouldn't it be solved if the first upload to Debian would
contain as few history as possible ?  Then the quantity of history in the
source packages could be allowed to grow, for instance up to one or two
previous stable releases.

Have a nice week-end,

-- 
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/20120519025607.ga5...@falafel.plessy.net

Re: Bug#642801: ftp.debian.org: Please support dpkg-source format 3.0 (git) in our archive.

2012-05-18 Thread Charles Plessy

Le Sat, May 19, 2012 at 11:56:07AM +0900, Charles Plessy a écrit :
 
 In the case of the initial copryight review, which is if I understand well the
 strongest objection, wouldn't it be solved if the first upload to Debian would
 contain as few history as possible ?  Then the quantity of history in the
 source packages could be allowed to grow, for instance up to one or two
 previous stable releases.

Only after sending that email I remembered about #642801.  Sorry for the noise.

Dear FTP team,

is the wontfix tag only related to the problem of the copyright review or do
you think other issues are blocking ?

In case of the copyright review, would it be accepteable if the first upload of
a package in 3.0 (git) package would contain as little history as possible,
that is, either one revision, or multiple when they correspond to the equivalent
of Debian-specific patches ?

Have a nice week-end,

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120519034159.gc5...@falafel.plessy.net

Re: Bug#481129: Bug#671503: general: APT repository format is not documented

2012-05-18 Thread Charles Plessy

Le Fri, May 18, 2012 at 06:49:10PM +0200, Julian Andres Klode a écrit :
 
 In a few months, I'd like to rework this in DocBook form, and submit it to
 debian-policy for inclusion into official Policy, as a sub-policy like
 copyright-format.

Dear Julian and everybody,

thank you for this documentation effort.  I think it is very useful.

How about integrating it with the Policy's chapter 5 (thus enlarging its scope)
instead of having it as a separate document ?  That would help to underline
when a field is used in the same way or differently as in the package control
data files.

Have a nice week-end,

-- 
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/20120519042845.gd5...@falafel.plessy.net

Re: why do people introduce stup^Wstrange changes to quilt 3.0 format

2012-05-18 Thread Tollef Fog Heen

]] Roger Leigh 

 I think this is a key point.  The aim of the git format should not be
 provide the entire history, any more than the other formats do (not).
 
 What should be provided needs to be
 - sufficient to build the package
 - sufficient to determine the changes made between the Upstream
   release and the Debian upload
 - sufficient to allow further uploads, including NMUs
 - (allow restoration of the full history)

- The source, aka the preferred form for modification.

I think we're failing to provide that in many cases today, since if
you're going to do any serious hacking on a project, you end up cloning
its VCS, you don't just grab a tarball and use that.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87txzcsrc7@qurzaw.varnish-software.com

About building packages in porterbox

2012-05-18 Thread Liang Guo

Hi, List,

One of my packages [1] failed to build on armel, kfreebsd and hurd, 
But I don't have such a machine to test my packages. Is it possible
to use debian porterbox to build the package and dig into this 
problem ?

[1] https://buildd.debian.org/status/package.php?p=spice-vdagent

Thanks and Regards,
--
Liang Guo
http://bluestone.cublog.cn


signature.asc
Description: Digital signature

Accepted btrfs-tools 0.19+20120328-2 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 07:50:12 +0200
Source: btrfs-tools
Binary: btrfs-tools btrfs-tools-udeb btrfs-tools-dbg
Architecture: source i386
Version: 0.19+20120328-2
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
Changed-By: Daniel Baumann daniel.baum...@progress-technologies.net
Description: 
 btrfs-tools - Checksumming Copy on Write Filesystem utilities
 btrfs-tools-dbg - Checksumming Copy on Write Filesystem utilities (debug)
 btrfs-tools-udeb - Checksumming Copy on Write Filesystem utilities (udeb) 
(udeb)
Closes: 673283
Changes: 
 btrfs-tools (0.19+20120328-2) unstable; urgency=low
 .
   * Updating compression handling for udeb with newer debhelper (Closes:
 #673283).
Checksums-Sha1: 
 f2d594d9a15ed4760c243d6572efa52cc0c02cb4 1339 btrfs-tools_0.19+20120328-2.dsc
 9409306e0e9d7f94efb7a67df7ec8d956cfa6379 7458 
btrfs-tools_0.19+20120328-2.debian.tar.gz
 44a887f077b9d344fca059fe3330c4db714d4b16 1172918 
btrfs-tools_0.19+20120328-2_i386.deb
 14373302cde0d691c2dbfca5138151bacf81d2d3 76796 
btrfs-tools-udeb_0.19+20120328-2_i386.udeb
 3cfc8687d94ec04e9ababce5a86832ad59330d87 3836220 
btrfs-tools-dbg_0.19+20120328-2_i386.deb
Checksums-Sha256: 
 2baf954363401ddb3326a7cab323f93127d6e3d1caed3863d6664c0a3e94feba 1339 
btrfs-tools_0.19+20120328-2.dsc
 65bb551866819ca6ec2202e988ac2bc1a0f2f057e7b69976bb2faeadf0cfd9d7 7458 
btrfs-tools_0.19+20120328-2.debian.tar.gz
 6b24a3bedfb4cc0750e8a9bcd90bffa3b1a1f3a398d8dafd2db414c56aec0d11 1172918 
btrfs-tools_0.19+20120328-2_i386.deb
 a76ec30a94862779cd3bf17449755793fab00bfe6aaa04a578c916c7f096794f 76796 
btrfs-tools-udeb_0.19+20120328-2_i386.udeb
 903cb66cff0622c0c77e96fe9bb59967ed5ed90ec4579b9881856dea80839390 3836220 
btrfs-tools-dbg_0.19+20120328-2_i386.deb
Files: 
 47e5d10c1abef5a8e7d3ab787aa125f4 1339 admin optional 
btrfs-tools_0.19+20120328-2.dsc
 702bd71e46f65578ebcec3f9a850beed 7458 admin optional 
btrfs-tools_0.19+20120328-2.debian.tar.gz
 c70f60e883275917c1fc65a7ae040406 1172918 admin optional 
btrfs-tools_0.19+20120328-2_i386.deb
 2d9f03ff7296590f3c28b9c177412e40 76796 debian-installer optional 
btrfs-tools-udeb_0.19+20120328-2_i386.udeb
 e2e19268391d6db8be21ca437137c6c8 3836220 debug extra 
btrfs-tools-dbg_0.19+20120328-2_i386.deb
Package-Type: udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+15TYACgkQ+C5cwEsrK56l4QCfS4guSkZHsdQ9pN4Wl0VDbyh6
YFsAnRlSq2+fTP+KOatUPOkgJjxgzYj+
=OC9W
-END PGP SIGNATURE-


Accepted:
btrfs-tools-dbg_0.19+20120328-2_i386.deb
  to main/b/btrfs-tools/btrfs-tools-dbg_0.19+20120328-2_i386.deb
btrfs-tools-udeb_0.19+20120328-2_i386.udeb
  to main/b/btrfs-tools/btrfs-tools-udeb_0.19+20120328-2_i386.udeb
btrfs-tools_0.19+20120328-2.debian.tar.gz
  to main/b/btrfs-tools/btrfs-tools_0.19+20120328-2.debian.tar.gz
btrfs-tools_0.19+20120328-2.dsc
  to main/b/btrfs-tools/btrfs-tools_0.19+20120328-2.dsc
btrfs-tools_0.19+20120328-2_i386.deb
  to main/b/btrfs-tools/btrfs-tools_0.19+20120328-2_i386.deb


-- 
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/e1svggu-000730...@franck.debian.org

Accepted dmidecode 2.11-7 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 08:00:01 +0200
Source: dmidecode
Binary: dmidecode dmidecode-udeb
Architecture: source i386
Version: 2.11-7
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
Changed-By: Daniel Baumann daniel.baum...@progress-technologies.net
Description: 
 dmidecode  - SMBIOS/DMI table decoder
 dmidecode-udeb - SMBIOS/DMI table decoder (udeb) (udeb)
Changes: 
 dmidecode (2.11-7) unstable; urgency=low
 .
   * Updating compression handling for udeb with newer debhelper.
Checksums-Sha1: 
 af244a995404f82ef48bdd3b4bef685a4e180240 1166 dmidecode_2.11-7.dsc
 cfc6b43b997c59043e06fb5198a07d48537faa09 8351 dmidecode_2.11-7.debian.tar.gz
 8613275b89f64d0359d98d80618e2983968bd92f 71118 dmidecode_2.11-7_i386.deb
 624b18657a1399a3ef16970b8b143a5aad6f6594 26658 dmidecode-udeb_2.11-7_i386.udeb
Checksums-Sha256: 
 9a2cc328e37bac3ec940e4939ea162683f7ff01af949609f5c274c4995c27e48 1166 
dmidecode_2.11-7.dsc
 795bf5dc0b59cdfc466c6c1c47b2e3b0fdac8d57f204748bde5170d228cf0a00 8351 
dmidecode_2.11-7.debian.tar.gz
 c4fcd91f0b05cd7f83ec56e20bbff686021eea63ef34152ad9e061e2efd45a73 71118 
dmidecode_2.11-7_i386.deb
 3d2c2cfececbdbb1fc2f6a5a62817d51a9500d1ba49b8501d90e605dea4e2627 26658 
dmidecode-udeb_2.11-7_i386.udeb
Files: 
 11bbcd4802242c991e39fd6a98137247 1166 utils optional dmidecode_2.11-7.dsc
 e42cee1738a08fc8dfb38cd00151a0ca 8351 utils optional 
dmidecode_2.11-7.debian.tar.gz
 665ec59c38735e714b123dc0753b1b7d 71118 utils important 
dmidecode_2.11-7_i386.deb
 51f439ff7ca2d933d41cc97f9a545ef5 26658 debian-installer optional 
dmidecode-udeb_2.11-7_i386.udeb
Package-Type: udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+15d0ACgkQ+C5cwEsrK57bZgCfS+GuR06odkNN3ouqdufebwzV
ma8AoNEcGJqq1Z8OOa2BexVOHpcvw3zF
=5PIb
-END PGP SIGNATURE-


Accepted:
dmidecode-udeb_2.11-7_i386.udeb
  to main/d/dmidecode/dmidecode-udeb_2.11-7_i386.udeb
dmidecode_2.11-7.debian.tar.gz
  to main/d/dmidecode/dmidecode_2.11-7.debian.tar.gz
dmidecode_2.11-7.dsc
  to main/d/dmidecode/dmidecode_2.11-7.dsc
dmidecode_2.11-7_i386.deb
  to main/d/dmidecode/dmidecode_2.11-7_i386.deb


-- 
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/e1svgvq-0007or...@franck.debian.org

Accepted fuse 2.9.0-1 (source i386 all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 08:25:16 +0200
Source: fuse
Binary: fuse fuse-dbg fuse-utils libfuse2 libfuse-dev fuse-udeb libfuse2-udeb
Architecture: source i386 all
Version: 2.9.0-1
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
Changed-By: Daniel Baumann daniel.baum...@progress-technologies.net
Description: 
 fuse   - Filesystem in Userspace
 fuse-dbg   - Filesystem in Userspace
 fuse-udeb  - Filesystem in Userspace (udeb)
 fuse-utils - Filesystem in Userspace (transitional package)
 libfuse-dev - Filesystem in Userspace (development)
 libfuse2   - Filesystem in Userspace (library)
 libfuse2-udeb - Filesystem in Userspace (library) (udeb)
Changes: 
 fuse (2.9.0-1) unstable; urgency=low
 .
   * Updating compression handling for udeb with newer debhelper.
   * Merging upstream version 2.9.0.
   * Rediffing initscript.patch.
   * Rediffing kfreebsd.patch.
   * Rediffing examples.patch.
   * Removing cve-2011-0542.patch, included upstream.
   * Removing ftbfs.patch, included upstream.
   * Removing local manpages, included upstream.
Checksums-Sha1: 
 d50ec0a2b3ad19dc530322129a8d3d46e9ef01c0 1376 fuse_2.9.0-1.dsc
 e64396d516cca55995e0a8f8dd75456fd9d9d21d 558554 fuse_2.9.0.orig.tar.gz
 0ece34e6e351e72e91096963796689a023d969ce 15816 fuse_2.9.0-1.debian.tar.gz
 a4b1eb41306f3c24bbe9732a7f46070d2b72c93e 72706 fuse_2.9.0-1_i386.deb
 abdd0c9b24b2dfd9df6cc8b4f9e904802ffa2cd2 304448 fuse-dbg_2.9.0-1_i386.deb
 85b900d1046d4b105013125d6cb2f68dd06e4f22 43444 fuse-utils_2.9.0-1_all.deb
 d6852ab92a580d0ee511e2a7526947980f00ef94 179864 libfuse2_2.9.0-1_i386.deb
 7558ab50199a364836326375c492eb3a5b9d1206 178896 libfuse-dev_2.9.0-1_i386.deb
 62c76a62e2a8347e60e40946cd7a2a6836df78f0 14066 fuse-udeb_2.9.0-1_i386.udeb
 91cd9092c39d7064dea5bcae640335dd3fc82f2f 69334 libfuse2-udeb_2.9.0-1_i386.udeb
Checksums-Sha256: 
 162cbb112e010c5510bd071136fb94e66e9647bd07ebf293a8672add5c9134bb 1376 
fuse_2.9.0-1.dsc
 1bf669e5388d4f256c7875079d5a6b97837bad23eb77a1cbc8b54b46a88315f2 558554 
fuse_2.9.0.orig.tar.gz
 8555d00c38446848471d40209fe098ffef7bc76b185dcd25296e17950f9d6eb7 15816 
fuse_2.9.0-1.debian.tar.gz
 8de66d3f1cc10b477675ec1af6222e8c335d47e08f05072a2ca9430cb3e5687c 72706 
fuse_2.9.0-1_i386.deb
 e692e3ce76d3b798f35613c5314a15af17004387fe0ecf6051058506b596b8bd 304448 
fuse-dbg_2.9.0-1_i386.deb
 eb9a5dd0cc7a9c08f1b9719abcd1c15cd448e502fd6c10f40418b577a84c41b7 43444 
fuse-utils_2.9.0-1_all.deb
 ccdead16207c4544356e64e45c7bb4280b7213ac7a38eb6fa4c0f87b4bea97c7 179864 
libfuse2_2.9.0-1_i386.deb
 181b7ceb02ff102dbc3183d3288a6123fbcdf0cb1f8eafe7ebf5bdd40df658f1 178896 
libfuse-dev_2.9.0-1_i386.deb
 f75344a2a502889b8b5b63925da6df1926457a4a04723b61523f7329def444e1 14066 
fuse-udeb_2.9.0-1_i386.udeb
 cf1c4e62e39600911593c5ded3016aa15686624bc990a30547aaad54d8d27069 69334 
libfuse2-udeb_2.9.0-1_i386.udeb
Files: 
 b0eff422d47ea67a4bdbc33404cf992b 1376 utils optional fuse_2.9.0-1.dsc
 894ee11674f89a915ae87524aed55bc4 558554 utils optional fuse_2.9.0.orig.tar.gz
 56e9f559d0d1d0e3a45dc6e6588754d4 15816 utils optional 
fuse_2.9.0-1.debian.tar.gz
 83a3e9b0f3cd4191c21f840120d9ddfa 72706 utils optional fuse_2.9.0-1_i386.deb
 689ff7f62db83b5bf262e5b5e3d16dd7 304448 debug extra fuse-dbg_2.9.0-1_i386.deb
 b5895fd60f1a01b48e39dce6a656cddf 43444 utils optional 
fuse-utils_2.9.0-1_all.deb
 65f317c1793abd2d1df937be13208b91 179864 libs optional libfuse2_2.9.0-1_i386.deb
 586c0125c26d1e7faa76630cc75cdd3d 178896 libdevel optional 
libfuse-dev_2.9.0-1_i386.deb
 b35f61862a362b73f48f069296a4fb32 14066 debian-installer optional 
fuse-udeb_2.9.0-1_i386.udeb
 a7f1266eab0c9ba7e300fb640f4c19e7 69334 debian-installer optional 
libfuse2-udeb_2.9.0-1_i386.udeb
Package-Type: udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+173IACgkQ+C5cwEsrK56E8QCeOChmhF/eHSrRv8DXWDSmz7sI
DDAAmwe7QmZ/eCfWNhxk4j5TS8UxNNcz
=UNJQ
-END PGP SIGNATURE-


Accepted:
fuse-dbg_2.9.0-1_i386.deb
  to main/f/fuse/fuse-dbg_2.9.0-1_i386.deb
fuse-udeb_2.9.0-1_i386.udeb
  to main/f/fuse/fuse-udeb_2.9.0-1_i386.udeb
fuse-utils_2.9.0-1_all.deb
  to main/f/fuse/fuse-utils_2.9.0-1_all.deb
fuse_2.9.0-1.debian.tar.gz
  to main/f/fuse/fuse_2.9.0-1.debian.tar.gz
fuse_2.9.0-1.dsc
  to main/f/fuse/fuse_2.9.0-1.dsc
fuse_2.9.0-1_i386.deb
  to main/f/fuse/fuse_2.9.0-1_i386.deb
fuse_2.9.0.orig.tar.gz
  to main/f/fuse/fuse_2.9.0.orig.tar.gz
libfuse-dev_2.9.0-1_i386.deb
  to main/f/fuse/libfuse-dev_2.9.0-1_i386.deb
libfuse2-udeb_2.9.0-1_i386.udeb
  to main/f/fuse/libfuse2-udeb_2.9.0-1_i386.udeb
libfuse2_2.9.0-1_i386.deb
  to main/f/fuse/libfuse2_2.9.0-1_i386.deb


-- 
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/e1svgyp-0001dr...@franck.debian.org

Accepted libvalidation-class-perl 7.21-1 (source all)

2012-05-18 Thread Salvatore Bonaccorso

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 May 2012 08:44:53 +0200
Source: libvalidation-class-perl
Binary: libvalidation-class-perl
Architecture: source all
Version: 7.21-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org
Changed-By: Salvatore Bonaccorso car...@debian.org
Description: 
 libvalidation-class-perl - module for centralized, simplified input validation
Changes: 
 libvalidation-class-perl (7.21-1) unstable; urgency=low
 .
   * Team upload.
   * Imported Upstream version 7.21
   * Drop spelling-error.diff patch.
 Patch was applied upstream.
   * Update Build-Depends-Indep for new tests.
 Add libdbi-perl, libdbd-sqlite3-perl and libclass-method-modifiers-perl
 to Build-Depends-Indep to enable two new tests.
Checksums-Sha1: 
 31be1c5b57e23cd311e35ba9825bae2609bff305 2339 
libvalidation-class-perl_7.21-1.dsc
 5a3348dfb48a500cdb800098f1429acaa6c68aee 75385 
libvalidation-class-perl_7.21.orig.tar.gz
 bab4024a22c20cf036684874143c87773e67abc8 3315 
libvalidation-class-perl_7.21-1.debian.tar.gz
 54e554972b79a9151d0c49322bfe252f553f1106 95770 
libvalidation-class-perl_7.21-1_all.deb
Checksums-Sha256: 
 3647ea7573fc030e8e6b465e7c15455b671833f6f7453fc26112e722e16d4f4d 2339 
libvalidation-class-perl_7.21-1.dsc
 b67e76e70b0e7eea3c0319daa164ec654274b9863dd5ab166b37f794e7959806 75385 
libvalidation-class-perl_7.21.orig.tar.gz
 ac2f57abadd1df35aafd99ad46477b52a05223088405eabdca97da3a6ae6920b 3315 
libvalidation-class-perl_7.21-1.debian.tar.gz
 64a480b70aed0323a075dfd9e7083b2589452712c8e82b62206a8b27671d06c9 95770 
libvalidation-class-perl_7.21-1_all.deb
Files: 
 c6bb0b5076c870c53d40326b7cc7616f 2339 perl optional 
libvalidation-class-perl_7.21-1.dsc
 6211ee72fe558eaa66a3d3934932c628 75385 perl optional 
libvalidation-class-perl_7.21.orig.tar.gz
 b04d361f855d972dff7c263bc531e5fd 3315 perl optional 
libvalidation-class-perl_7.21-1.debian.tar.gz
 b09731483710ee403baf81c08e83e849 95770 perl optional 
libvalidation-class-perl_7.21-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJPtfAoAAoJEHidbwV/2GP+9PgQAKL1+xNbOBsenE1gVF6WJZhI
xBCNgtF66DpCaPWunK24vUOSWvHgHb8HNIGRRcDc5KKDxrEftl+2FO7olwFFAJGs
pLy0W/Y3FN2ia4JcVaUcrNwF/8if6f97cwGPk4ryEyuXP9pT/pfXG1VGl7oThZNJ
VTtLrArmOVcyNJJ2WjJe/Mb9fbbRwTHMv9QFH0Jlimq0Z6/dX/ATRNoPUBfF6nQs
FZepsTHOl9aRROBUcMQ9AzKzVHhFTOq/nmmUJQwDqRoTPigZ+iUUUlDODlo991kH
3lKRQdAW6sFX4dkDxkGZ1DDYmz4j1sGWTBmsmVxqVu0Iriq2Sb7qds1twAeWdjoo
pSb1/7YGQwMYPBOpuyeOxirMQm8YiO2TpD3Eelowz/0xTPiiP+7t1WviIeDqwr0T
ureH+3rutdYxvHfXZ5HTe6CQfXQm3MJT6KreMWhhm2Mm09K0MBCvBrXPeMdHdpRb
QKLgcEbhq8NfMvAiIeiKuoSevbq2oVjYjg7FnG43OjWCls7ABHqyIqQ7toQBagFv
ClKhZ9qifjBmiwmuWSce5zrE5ucgVnHM1t4C1DxY6tna0tLTd9iCxmhJIZ+BxvGy
0jI+ht4Xnpja49Yfzq55LSoI01Ko7pPCq9waRBr85GqcJXSenyz3R0VNpJmjCOEo
2Ctq4fwmK15lWmFsT1L+
=UQsv
-END PGP SIGNATURE-


Accepted:
libvalidation-class-perl_7.21-1.debian.tar.gz
  to 
main/libv/libvalidation-class-perl/libvalidation-class-perl_7.21-1.debian.tar.gz
libvalidation-class-perl_7.21-1.dsc
  to main/libv/libvalidation-class-perl/libvalidation-class-perl_7.21-1.dsc
libvalidation-class-perl_7.21-1_all.deb
  to main/libv/libvalidation-class-perl/libvalidation-class-perl_7.21-1_all.deb
libvalidation-class-perl_7.21.orig.tar.gz
  to 
main/libv/libvalidation-class-perl/libvalidation-class-perl_7.21.orig.tar.gz


-- 
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/e1svh0c-0001h0...@franck.debian.org

Accepted ntfs-3g 1:2012.1.15AR.5-1 (source i386 all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 08:45:24 +0200
Source: ntfs-3g
Binary: ntfs-3g ntfs-3g-dbg ntfs-3g-dev ntfs-3g-udeb ntfsprogs
Architecture: source i386 all
Version: 1:2012.1.15AR.5-1
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
Changed-By: Daniel Baumann daniel.baum...@progress-technologies.net
Description: 
 ntfs-3g- read/write NTFS driver for FUSE
 ntfs-3g-dbg - read/write NTFS driver for FUSE (debug)
 ntfs-3g-dev - read/write NTFS driver for FUSE (development)
 ntfs-3g-udeb - read/write NTFS driver for FUSE (udeb)
 ntfsprogs  - read/write NTFS driver for FUSE (transitional package)
Changes: 
 ntfs-3g (1:2012.1.15AR.5-1) unstable; urgency=low
 .
   * Merging upstream version 2012.1.15AR.5.
   * Updating compression handling for udeb with newer debhelper.
Checksums-Sha1: 
 99a505dc0c4e0e91b571d520ead4189dbd3089e8 1478 ntfs-3g_2012.1.15AR.5-1.dsc
 374bf58976d73d513bab0d6c776ee340f7914539 1165281 
ntfs-3g_2012.1.15AR.5.orig.tar.gz
 6587f0c2246f397538597239c409d12bb6271a13 28152 
ntfs-3g_2012.1.15AR.5-1.debian.tar.gz
 2c29f89a73e43d59ae03183c18a809ded106bc23 663070 
ntfs-3g_2012.1.15AR.5-1_i386.deb
 4cd8d851e8d313009814d53c46676590e69dad4e 1338384 
ntfs-3g-dbg_2012.1.15AR.5-1_i386.deb
 9edf25ace33f69f6ede7613d9a6a8139c145b91a 270630 
ntfs-3g-dev_2012.1.15AR.5-1_i386.deb
 5bc72dbdfb6b7a08734e63e3571e7763fa493c8f 198518 
ntfs-3g-udeb_2012.1.15AR.5-1_i386.udeb
 b78ef6e769d5a10a47b62c200d856be36301b8fc 17312 
ntfsprogs_2012.1.15AR.5-1_all.deb
Checksums-Sha256: 
 d20a6566fbcb14ee184777d73dad146aab70729a0f5723f1bdddebcd6ea03acf 1478 
ntfs-3g_2012.1.15AR.5-1.dsc
 72f93c5c003ce22b5da451ece5eb94faa5fd1b46c69c3c5a9c5c17a96d9de79d 1165281 
ntfs-3g_2012.1.15AR.5.orig.tar.gz
 f35f63fbfdc797212f09bf84c1ee11caf07f43c59985fe9f552988ea0787fd06 28152 
ntfs-3g_2012.1.15AR.5-1.debian.tar.gz
 859af01ba2f2f84f49781cda09b60c8aa4ccd8b7916c01182f4bee44d1c254d7 663070 
ntfs-3g_2012.1.15AR.5-1_i386.deb
 7ff6ee29bd8b6213bb3a5fa37a7e405ad9d7f39d2c6e4f10020a4edf50d450d8 1338384 
ntfs-3g-dbg_2012.1.15AR.5-1_i386.deb
 9e032061aeaa1cc21f877a2dd0ad2851f1bafd2dd1586569ab0be3ad2ffdb9ea 270630 
ntfs-3g-dev_2012.1.15AR.5-1_i386.deb
 d166f404e15251960177d3e1b8e9a52d2815040bc4bef5fd8061751c707488fc 198518 
ntfs-3g-udeb_2012.1.15AR.5-1_i386.udeb
 4d4fc7cff156172e38953714085438c04e50aeaf220126202658520257071d21 17312 
ntfsprogs_2012.1.15AR.5-1_all.deb
Files: 
 c5a94cb7352297eb24643d83239804e1 1478 otherosfs optional 
ntfs-3g_2012.1.15AR.5-1.dsc
 5fa418ef6e2f6ce96dc535331c524ec3 1165281 otherosfs optional 
ntfs-3g_2012.1.15AR.5.orig.tar.gz
 eed0bbd3ff917445d1ac9adc98179ecb 28152 otherosfs optional 
ntfs-3g_2012.1.15AR.5-1.debian.tar.gz
 2bc85087cf8e5233f173d52796d3a2a7 663070 otherosfs optional 
ntfs-3g_2012.1.15AR.5-1_i386.deb
 5e20122c79de355f8645712c2d676e16 1338384 debug extra 
ntfs-3g-dbg_2012.1.15AR.5-1_i386.deb
 172fb050c64362418b4121b1033aec1b 270630 libdevel optional 
ntfs-3g-dev_2012.1.15AR.5-1_i386.deb
 b02308da7b34a169ad0b8069cf64b38b 198518 debian-installer optional 
ntfs-3g-udeb_2012.1.15AR.5-1_i386.udeb
 5e89f89cec4fa32e05ae4fe09fc5fb0e 17312 metapackages optional 
ntfsprogs_2012.1.15AR.5-1_all.deb
Package-Type: udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+18eAACgkQ+C5cwEsrK570KACglQOmBSSGFOiHV3jbXstOPiYY
NDcAoITh7nLM7EsbJKcKvKljSfzZ4A63
=4Usr
-END PGP SIGNATURE-


Accepted:
ntfs-3g-dbg_2012.1.15AR.5-1_i386.deb
  to main/n/ntfs-3g/ntfs-3g-dbg_2012.1.15AR.5-1_i386.deb
ntfs-3g-dev_2012.1.15AR.5-1_i386.deb
  to main/n/ntfs-3g/ntfs-3g-dev_2012.1.15AR.5-1_i386.deb
ntfs-3g-udeb_2012.1.15AR.5-1_i386.udeb
  to main/n/ntfs-3g/ntfs-3g-udeb_2012.1.15AR.5-1_i386.udeb
ntfs-3g_2012.1.15AR.5-1.debian.tar.gz
  to main/n/ntfs-3g/ntfs-3g_2012.1.15AR.5-1.debian.tar.gz
ntfs-3g_2012.1.15AR.5-1.dsc
  to main/n/ntfs-3g/ntfs-3g_2012.1.15AR.5-1.dsc
ntfs-3g_2012.1.15AR.5-1_i386.deb
  to main/n/ntfs-3g/ntfs-3g_2012.1.15AR.5-1_i386.deb
ntfs-3g_2012.1.15AR.5.orig.tar.gz
  to main/n/ntfs-3g/ntfs-3g_2012.1.15AR.5.orig.tar.gz
ntfsprogs_2012.1.15AR.5-1_all.deb
  to main/n/ntfs-3g/ntfsprogs_2012.1.15AR.5-1_all.deb


-- 
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/e1svhdf-0002p7...@franck.debian.org

Accepted eegdev 0.2-1 (source amd64)

2012-05-18 Thread Nicolas Bourdaud

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 16 May 2012 17:35:25 +0200
Source: eegdev
Binary: libeegdev0 eegdev-plugins-free libeegdev-dev libeegdev0-dbg
Architecture: source amd64
Version: 0.2-1
Distribution: unstable
Urgency: low
Maintainer: Nicolas Bourdaud nicolas.bourd...@gmail.com
Changed-By: Nicolas Bourdaud nicolas.bourd...@gmail.com
Description: 
 eegdev-plugins-free - Biosignal acquisition device library (free plugins)
 libeegdev-dev - Biosignal acquisition device library (Developement files)
 libeegdev0 - Biosignal acquisition device library
 libeegdev0-dbg - Biosignal acquisition device library (Debugging symbols)
Closes: 662745
Changes: 
 eegdev (0.2-1) unstable; urgency=low
 .
   * New upstream version: 0.2
 - Drop implement-libusb_fill_bulk_transfer-in-fake-libusb.patch (applied
   upstream).
 - New build-depends: bison, flex, gnulib
 - dh_autoreconf use autogen.sh script
   * Recommends plugin package instead of Suggests. (Closes: #662745)
   * Drop conditional build depending on the architecture (new version should
 build and run on all platforms but Hurd).
   * Bump debhelper compatibility level to 9.
   * Add multiarch support.
   * Bump Debian policy version to 3.9.3 -- no changes.
   * Use versioned copyright format.
Checksums-Sha1: 
 5baf76c50d08b067979f6495290f0e814fc17567 2089 eegdev_0.2-1.dsc
 99fb5ba1d3e96167b7c3acc526b02a95ad1d9c23 687600 eegdev_0.2.orig.tar.bz2
 2c3131849a2456966f96536a92ca3854ef4b4d97 5011 eegdev_0.2-1.debian.tar.gz
 e1cf95b1dabe25cb77a9227876675da88610d72d 45914 libeegdev0_0.2-1_amd64.deb
 1062c0a40a73603b3069d284e2a3fb40e39e49c5 29138 
eegdev-plugins-free_0.2-1_amd64.deb
 12f7e6ebd4b62b4cb70f2bcbbedffc6b4a810990 22406 libeegdev-dev_0.2-1_amd64.deb
 330579e8fdcc49c26616046cb199706439e03c84 166252 libeegdev0-dbg_0.2-1_amd64.deb
Checksums-Sha256: 
 b6f7af2f9c4482c120ffa1cdae8435cea14d832d1c37d35b1509df8c75e01ba7 2089 
eegdev_0.2-1.dsc
 3ad091a9659974247850477b227da06ff77ba09a07047ecf3bc2fbff9ceed714 687600 
eegdev_0.2.orig.tar.bz2
 f3da0601140f908325f54035eb7e1dd51bd3fe6b2f28b7133212acdae1f7175b 5011 
eegdev_0.2-1.debian.tar.gz
 bf81e1f312be90cf365ea225b14d3180f75e3f7a3b126ac29ad8713fcb25a672 45914 
libeegdev0_0.2-1_amd64.deb
 cdcde3ad8306bc79c08ac32c0b6bbbc643b65aa8a1db5fd1a05745dfa4d5b084 29138 
eegdev-plugins-free_0.2-1_amd64.deb
 0e75d6e837c3684d97e15e688f8ab89c6979273ae3ba82923124164f284b4c27 22406 
libeegdev-dev_0.2-1_amd64.deb
 83f162370212f72db1a2a21f3fd5f10e42ddd5512b89234af4a41af54413dce4 166252 
libeegdev0-dbg_0.2-1_amd64.deb
Files: 
 96ee7fef77db150d101d5caed929581a 2089 libs extra eegdev_0.2-1.dsc
 4508e0c8fedfc122c01a73149036d23d 687600 libs extra eegdev_0.2.orig.tar.bz2
 0a65d9fddbc2a977bf952f347e76091f 5011 libs extra eegdev_0.2-1.debian.tar.gz
 0325e9ee43450e29ff3b0a6c64f7574d 45914 libs extra libeegdev0_0.2-1_amd64.deb
 68ef6ef17d5982db7dd7b6aa31e38b3b 29138 libs extra 
eegdev-plugins-free_0.2-1_amd64.deb
 06c27e90b28ee0749fe275be7c1df2e4 22406 libdevel extra 
libeegdev-dev_0.2-1_amd64.deb
 81704f4b4d291dcda046a155adea8011 166252 debug extra 
libeegdev0-dbg_0.2-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJPtfSLAAoJEMBz0ih/+56bq3cP/3HZKSOCSKZGrSrd7pY10aCU
cV3yeEySYh+KDl0E60UDLslDPRmlZQyMwDXQa6kfyBhXE7S6dobEdqkTBx9EjuaS
QfmF4q5Oenp4CpHun/WhjJmr3Qafls8DAslildmJ+rdu08/IicOhMvH1+TuIuHcu
f04BYwrH9cS2MgOWIlrKHyRjgkbUBWJrD/hAoZ+rlItww9tQUyRBF+X9aWfqw0Y4
L7BNhsRHraN4LPMyGGmNAjuBlEQjt8LivZPTXi60QA+kkKYNTeg4dZ+8S1vwHGb4
TU73h/s8ZTPsVI56Ljb/pjH9SVuhi8iNH9xHA217uUr1dlsRAXLrSN+MK9D/73Ft
jMz6A/7aUXBesGVZ1iCCAaTxbi3q7PSIPwSXDaPrDUN4IJdHMbbqbTIYbrblkHJS
stZ1aINi7Fsvi0BvY8PbdSt2F7j8lHPefMfUsEgD1rX9jpQArt68FEgO2xPTOQ77
uLtjyRCGU+BVqtyS9yDOodkVdePeybbgw3MHgQR2KoGDGuFHlt3wGd0N+UkBrqic
wvy84Z/e1clVDLEKMlg80eI7ipFE/HEDhfp9dVoY3ZU2IfifxK0FiXXL6Jmbc6fz
zRx7j05BATUEPZ0ti4BtznSsUVNA/4rOA0O0FvcwVpsqbE0uht51Wls90BvucBfV
0DITr37L/e2iRFi+pqwp
=FyM1
-END PGP SIGNATURE-


Accepted:
eegdev-plugins-free_0.2-1_amd64.deb
  to main/e/eegdev/eegdev-plugins-free_0.2-1_amd64.deb
eegdev_0.2-1.debian.tar.gz
  to main/e/eegdev/eegdev_0.2-1.debian.tar.gz
eegdev_0.2-1.dsc
  to main/e/eegdev/eegdev_0.2-1.dsc
eegdev_0.2.orig.tar.bz2
  to main/e/eegdev/eegdev_0.2.orig.tar.bz2
libeegdev-dev_0.2-1_amd64.deb
  to main/e/eegdev/libeegdev-dev_0.2-1_amd64.deb
libeegdev0-dbg_0.2-1_amd64.deb
  to main/e/eegdev/libeegdev0-dbg_0.2-1_amd64.deb
libeegdev0_0.2-1_amd64.deb
  to main/e/eegdev/libeegdev0_0.2-1_amd64.deb


-- 
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/e1svhr7-0003af...@franck.debian.org

Accepted syslinux 2:4.05+dfsg-4 (source i386 all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 09:11:09 +0200
Source: syslinux
Binary: syslinux syslinux-udeb extlinux syslinux-common
Architecture: source i386 all
Version: 2:4.05+dfsg-4
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
Changed-By: Daniel Baumann daniel.baum...@progress-technologies.net
Description: 
 extlinux   - collection of boot loaders (ext2/3/4 and btrfs bootloader)
 syslinux   - collection of boot loaders
 syslinux-common - collection of boot loaders (common files)
 syslinux-udeb - collection of boot loaders (udeb)
Closes: 672380 672520
Changes: 
 syslinux (2:4.05+dfsg-4) unstable; urgency=low
 .
   * Updating compression handling for udeb with newer debhelper.
   * Build-depending on gcc-4.6 for the time being in order to avoid
 miscompiling default gcc-4.7 (Closes: #672520).
   * Removing bootloader configuration files for extlinux in postrm when
 purging package (Closes: #672380).
Checksums-Sha1: 
 fcfd6b6ba89f00b901d4b9775384c71de5cfe138 1407 syslinux_4.05+dfsg-4.dsc
 824b4cbec1b8e71dcfa407a017754b66940db082 36231 
syslinux_4.05+dfsg-4.debian.tar.gz
 f5bc50b8ace6040e585a0d9afdeaacd2196def6c 100546 syslinux_4.05+dfsg-4_i386.deb
 413c09b0babf0f4a930bfb5c682a4914a069a6fe 42228 
syslinux-udeb_4.05+dfsg-4_i386.udeb
 b0a5a7eabcede6a4a24c25cd6965656914974362 120004 extlinux_4.05+dfsg-4_i386.deb
 e4b6cf981555c44a555e1d5ee13d1b54f2fd660b 1541016 
syslinux-common_4.05+dfsg-4_all.deb
Checksums-Sha256: 
 0f5bc7f596fbf2b50906112a2e0aaa08df77d43be77727b78be06891cae74f2d 1407 
syslinux_4.05+dfsg-4.dsc
 41cb5abe120e7c47939dc5c907f36d7043a3c2669f7a44cbc9290a2f8b315d07 36231 
syslinux_4.05+dfsg-4.debian.tar.gz
 1a9082ad0e0e18774c57d4585d9bfbb621c4b88ce8c5eff61524b91a77355f96 100546 
syslinux_4.05+dfsg-4_i386.deb
 9bc87d2e5c191805919014ca7d918e60bab4208ce87186d5feaabd2421d6d1ce 42228 
syslinux-udeb_4.05+dfsg-4_i386.udeb
 251d80d0412c3ac32e096549a18297c60995b95cf68683638aec2992f21c 120004 
extlinux_4.05+dfsg-4_i386.deb
 44a6615989e61deb8ae309459f0edc23d0ba2af3d1b85acb6ec4621df765f89f 1541016 
syslinux-common_4.05+dfsg-4_all.deb
Files: 
 b28edff2d883ed257aae02531b6c2de9 1407 utils optional syslinux_4.05+dfsg-4.dsc
 77152d481319e164cf529da84719b266 36231 utils optional 
syslinux_4.05+dfsg-4.debian.tar.gz
 9d6bd4bf130aaa678f25b6425916a9c2 100546 utils optional 
syslinux_4.05+dfsg-4_i386.deb
 95444ed367bfd9091d4117b8bc43b75b 42228 debian-installer optional 
syslinux-udeb_4.05+dfsg-4_i386.udeb
 fa27aa4ee6022c2f7037267c7b81bcf7 120004 utils optional 
extlinux_4.05+dfsg-4_i386.deb
 d18341cb5b879e8e2aaa0007afeaed9a 1541016 utils optional 
syslinux-common_4.05+dfsg-4_all.deb
Package-Type: udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+1+YoACgkQ+C5cwEsrK57sQACfVgpJ+sbPEtOtZVpKKmbifbmY
CJAAoKW+fKSojTnzQx4/NozMQG7JtmIZ
=KCF8
-END PGP SIGNATURE-


Accepted:
extlinux_4.05+dfsg-4_i386.deb
  to main/s/syslinux/extlinux_4.05+dfsg-4_i386.deb
syslinux-common_4.05+dfsg-4_all.deb
  to main/s/syslinux/syslinux-common_4.05+dfsg-4_all.deb
syslinux-udeb_4.05+dfsg-4_i386.udeb
  to main/s/syslinux/syslinux-udeb_4.05+dfsg-4_i386.udeb
syslinux_4.05+dfsg-4.debian.tar.gz
  to main/s/syslinux/syslinux_4.05+dfsg-4.debian.tar.gz
syslinux_4.05+dfsg-4.dsc
  to main/s/syslinux/syslinux_4.05+dfsg-4.dsc
syslinux_4.05+dfsg-4_i386.deb
  to main/s/syslinux/syslinux_4.05+dfsg-4_i386.deb


-- 
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/e1svhi2-0005on...@franck.debian.org

Accepted haskell-hakyll 3.2.7.2-1 (source all amd64)

2012-05-18 Thread Joachim Breitner

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 00:23:21 +0200
Source: haskell-hakyll
Binary: libghc-hakyll-dev libghc-hakyll-prof libghc-hakyll-doc
Architecture: source all amd64
Version: 3.2.7.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Haskell Group 
pkg-haskell-maintain...@lists.alioth.debian.org
Changed-By: Joachim Breitner nome...@debian.org
Description: 
 libghc-hakyll-dev - static website compiler library
 libghc-hakyll-doc - static website compiler library; documentation
 libghc-hakyll-prof - static website compiler library; profiling libraries
Changes: 
 haskell-hakyll (3.2.7.2-1) unstable; urgency=low
 .
   * New upstream release.
Checksums-Sha1: 
 819a371b09d87d69b3a6147e19f2eb376b1ffc33 2884 haskell-hakyll_3.2.7.2-1.dsc
 0d91c83ed391b6a5d6ad08f17b77e5988ff6 54474 
haskell-hakyll_3.2.7.2.orig.tar.gz
 9430533cf90af1e6254433e1babf0b04f929fbfe 2949 
haskell-hakyll_3.2.7.2-1.debian.tar.gz
 a16e269abd1b280ec0585d814676f4842c19bd48 195400 
libghc-hakyll-doc_3.2.7.2-1_all.deb
 2cc72ad407faf049c13ec836770876042df33e30 701214 
libghc-hakyll-dev_3.2.7.2-1_amd64.deb
 f77d422b10b4f29f6260fa64d760eae71e46cb9d 707842 
libghc-hakyll-prof_3.2.7.2-1_amd64.deb
Checksums-Sha256: 
 5e85432d2812ddb1efe5c88af61f5473492cdb78e41e368a459e29449a798af3 2884 
haskell-hakyll_3.2.7.2-1.dsc
 1ce297dd77539868a168734a23f57e4cef202844d00238f0949d4129f0e067d0 54474 
haskell-hakyll_3.2.7.2.orig.tar.gz
 13be4d2df0bdb26d23775a6a1997f5b870040a92e43858bd97c7a21811750222 2949 
haskell-hakyll_3.2.7.2-1.debian.tar.gz
 dc3c90bfa78b7b41619260f5cd925ba946a3dd54648bbe0fe7944bf468f90ce5 195400 
libghc-hakyll-doc_3.2.7.2-1_all.deb
 2923fa74dce536f840efadc0ddc2e457c7ba6d7a85f214f4dcb19b1a6be545c9 701214 
libghc-hakyll-dev_3.2.7.2-1_amd64.deb
 f30fc215272bdabf7ab71daf7cbb351cc51dd17efba6c921a9a25e606e955f88 707842 
libghc-hakyll-prof_3.2.7.2-1_amd64.deb
Files: 
 75dee7f0e8c5704b6be96bacc4316242 2884 haskell extra 
haskell-hakyll_3.2.7.2-1.dsc
 dd4d262bbc82474bcf1630f72ba6999c 54474 haskell extra 
haskell-hakyll_3.2.7.2.orig.tar.gz
 03cb48b764d5353788060adc32c00b10 2949 haskell extra 
haskell-hakyll_3.2.7.2-1.debian.tar.gz
 c8c2cf8081e58b606bf49a145df72632 195400 doc extra 
libghc-hakyll-doc_3.2.7.2-1_all.deb
 e0429e557780e6bd73031a4b1a499f3b 701214 haskell extra 
libghc-hakyll-dev_3.2.7.2-1_amd64.deb
 b19f7d57362d321f9114f5b4dc22d019 707842 haskell extra 
libghc-hakyll-prof_3.2.7.2-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAk+1+i4ACgkQ9ijrk0dDIGzZXACdHBjOeP8LpZXP8OrPeMot012H
AT0An1M2HW7IhjgEW5LLXwpAWWP7/lFb
=q+v8
-END PGP SIGNATURE-


Accepted:
haskell-hakyll_3.2.7.2-1.debian.tar.gz
  to main/h/haskell-hakyll/haskell-hakyll_3.2.7.2-1.debian.tar.gz
haskell-hakyll_3.2.7.2-1.dsc
  to main/h/haskell-hakyll/haskell-hakyll_3.2.7.2-1.dsc
haskell-hakyll_3.2.7.2.orig.tar.gz
  to main/h/haskell-hakyll/haskell-hakyll_3.2.7.2.orig.tar.gz
libghc-hakyll-dev_3.2.7.2-1_amd64.deb
  to main/h/haskell-hakyll/libghc-hakyll-dev_3.2.7.2-1_amd64.deb
libghc-hakyll-doc_3.2.7.2-1_all.deb
  to main/h/haskell-hakyll/libghc-hakyll-doc_3.2.7.2-1_all.deb
libghc-hakyll-prof_3.2.7.2-1_amd64.deb
  to main/h/haskell-hakyll/libghc-hakyll-prof_3.2.7.2-1_amd64.deb


-- 
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/e1svhvv-0006ge...@franck.debian.org

Accepted dictionaries-common 1.12.7 (source all)

2012-05-18 Thread Agustin Martin Domingo

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 09:38:01 +0200
Source: dictionaries-common
Binary: dictionaries-common dictionaries-common-dev
Architecture: source all
Version: 1.12.7
Distribution: unstable
Urgency: low
Maintainer: Agustin Martin Domingo agmar...@debian.org
Changed-By: Agustin Martin Domingo agmar...@debian.org
Description: 
 dictionaries-common - Common utilities for spelling dictionary tools
 dictionaries-common-dev - Developer tools and Policy for spelling dictionary 
tools
Changes: 
 dictionaries-common (1.12.7) unstable; urgency=low
 .
   * flyspell.el: Upgraded to upstream r108285:
 - Protect otherchars delay against empty otherchars.
Checksums-Sha1: 
 825a06936cad41bb0868007e47525bf4448d4d78 1225 dictionaries-common_1.12.7.dsc
 535e35ecf43c69274839d19fdc681c12e4a603ac 320561 
dictionaries-common_1.12.7.tar.gz
 476072bea668be24f5475353c0191d2be3a00bb6 301240 
dictionaries-common_1.12.7_all.deb
 82adf2c9289fd89b2c5e753a9a2dca022cd36d4a 132318 
dictionaries-common-dev_1.12.7_all.deb
Checksums-Sha256: 
 74570bc467790f5d8dd2671fdb932002a89b357158e81ad41dc4599c2bd1e679 1225 
dictionaries-common_1.12.7.dsc
 9ebd97e79f3bcdc162bfb76d98af8805c83710e5dedcf591003d0cbd5bdf8397 320561 
dictionaries-common_1.12.7.tar.gz
 a1ea3d6ddc549b2ab8c0659507b393de3ec77d06aec19032a5a368fa15cc92bf 301240 
dictionaries-common_1.12.7_all.deb
 37ac3eb9c9ca48c92fbea7d9a7fb16d4abb60371d2903f5b8ff2afdbe6727f14 132318 
dictionaries-common-dev_1.12.7_all.deb
Files: 
 d7cf60c2417a826908e5924706750140 1225 text optional 
dictionaries-common_1.12.7.dsc
 0b74cab0433e8e8d05c84af12018e532 320561 text optional 
dictionaries-common_1.12.7.tar.gz
 f11b935b48387da698fd1def498ef746 301240 text optional 
dictionaries-common_1.12.7_all.deb
 b5d99313f5ebabdebb882fa802fa6657 132318 devel extra 
dictionaries-common-dev_1.12.7_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iD8DBQFPtf1gTShHqj72DpwRAkfsAJ4iq+m7rITejxEuoumgT7v5XQF03QCgkCuS
Nx8hj+P/EyQwUf3AFlpGR78=
=qrpX
-END PGP SIGNATURE-


Accepted:
dictionaries-common-dev_1.12.7_all.deb
  to main/d/dictionaries-common/dictionaries-common-dev_1.12.7_all.deb
dictionaries-common_1.12.7.dsc
  to main/d/dictionaries-common/dictionaries-common_1.12.7.dsc
dictionaries-common_1.12.7.tar.gz
  to main/d/dictionaries-common/dictionaries-common_1.12.7.tar.gz
dictionaries-common_1.12.7_all.deb
  to main/d/dictionaries-common/dictionaries-common_1.12.7_all.deb


-- 
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/e1svjl5-0005lx...@franck.debian.org

Accepted freefem++ 3.19-1 (source all amd64)

2012-05-18 Thread Dimitrios Eftaxiopoulos

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 12 May 2012 03:59:00 +0200
Source: freefem++
Binary: freefem++ libfreefem++ libfreefem++-dev freefem++-doc
Architecture: source amd64 all
Version: 3.19-1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 
debian-science-maintain...@lists.alioth.debian.org
Changed-By: Dimitrios Eftaxiopoulos eftax...@otenet.gr
Description: 
 freefem++  - Provides the binaries of the FreeFem++ FE suite
 freefem++-doc - Provides the documentation of the FreeFem++ FE suite
 libfreefem++ - Provides the shared libraries of the FreeFem++ FE suite
 libfreefem++-dev - Provides the development files of the FreeFem++ FE suite
Closes: 672612
Changes: 
 freefem++ (3.19-1) unstable; urgency=low
 .
   * New upstream release.
   * Add libmumps-seq-dev to build-deps.
   * Update standards version to 3.9.3.
   * Fix FTBFS due to new g++-4.7 (Closes: #672612).
Checksums-Sha1: 
 59d59d349c644fa00f31af960012233ba03338cf 2082 freefem++_3.19-1.dsc
 0aa400c449f78b9f88135851eb8a3bd62109aa06 24606449 freefem++_3.19.orig.tar.gz
 7aac623e018d444151d7419c47d6c95a199ad234 11229 freefem++_3.19-1.debian.tar.gz
 f7e5891691d8722c4ca68471c017b8dbc91a7d27 15596904 freefem++_3.19-1_amd64.deb
 c8ee83a978ba2297db064adf58b49b4a8a481916 1597420 libfreefem++_3.19-1_amd64.deb
 7b05550d8fb1aa201a6b15febb638c3d8b02a9a6 275734 
libfreefem++-dev_3.19-1_amd64.deb
 ed74555151feaa7954809b3ad0b5c861d4c362a6 9537214 freefem++-doc_3.19-1_all.deb
Checksums-Sha256: 
 8a4b8dced58d5c30022bc7f6b52fc5d31cd070ee00a7da2859eb4760860b1412 2082 
freefem++_3.19-1.dsc
 e302f6a5b5bae8ecbb17f8aa39e31f46e97782289f8de7e9b68e47abb57da882 24606449 
freefem++_3.19.orig.tar.gz
 bb394a93545d85b24eb0c9039665443927f9c5c26427aa372a57755e284795bd 11229 
freefem++_3.19-1.debian.tar.gz
 bf1003fd5736e67c7516685d7b5e6a82efa4fbe1ff0bae1ee1d3298e06f03aaf 15596904 
freefem++_3.19-1_amd64.deb
 e275314be670f1c282bcd9991eb884c82cf8bd8a73bafe515ccf14100f128c3c 1597420 
libfreefem++_3.19-1_amd64.deb
 ee261809d43acf3f306a47cbd924f80d765df86d3d56b664c11f45c021fcbcc0 275734 
libfreefem++-dev_3.19-1_amd64.deb
 4de2e707a90b1a7b432cb7f7a90bed8f4847578a97ac1b3f31aa0df2343eb30b 9537214 
freefem++-doc_3.19-1_all.deb
Files: 
 556957a129b0d0c06fb17f5b3e6d9073 2082 science optional freefem++_3.19-1.dsc
 b30a5aa9c8abd02af23b23faa986c501 24606449 science optional 
freefem++_3.19.orig.tar.gz
 b6d3462c537996a01588ec9b1b0af3eb 11229 science optional 
freefem++_3.19-1.debian.tar.gz
 d88584910c18421c0471acad928baf6f 15596904 math optional 
freefem++_3.19-1_amd64.deb
 0896ec8976e90cbabf5468c6a112bf25 1597420 libs optional 
libfreefem++_3.19-1_amd64.deb
 8c7259980bb96ea1b2e3bc66efb84277 275734 libdevel optional 
libfreefem++-dev_3.19-1_amd64.deb
 c3952eafc46145a24e3b23142378ded7 9537214 doc optional 
freefem++-doc_3.19-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAk+2Dl0ACgkQiOXXM92JlhAFbgCePq//lKfVdwwQdAmTlwelV06Y
GQYAnjF5/11SpzvyIN3sViJXQuHN+IUb
=WAX1
-END PGP SIGNATURE-


Accepted:
freefem++-doc_3.19-1_all.deb
  to main/f/freefem++/freefem++-doc_3.19-1_all.deb
freefem++_3.19-1.debian.tar.gz
  to main/f/freefem++/freefem++_3.19-1.debian.tar.gz
freefem++_3.19-1.dsc
  to main/f/freefem++/freefem++_3.19-1.dsc
freefem++_3.19-1_amd64.deb
  to main/f/freefem++/freefem++_3.19-1_amd64.deb
freefem++_3.19.orig.tar.gz
  to main/f/freefem++/freefem++_3.19.orig.tar.gz
libfreefem++-dev_3.19-1_amd64.deb
  to main/f/freefem++/libfreefem++-dev_3.19-1_amd64.deb
libfreefem++_3.19-1_amd64.deb
  to main/f/freefem++/libfreefem++_3.19-1_amd64.deb


-- 
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/e1svjnt-0006cb...@franck.debian.org

Accepted lcrt 1.1.2-1 (source i386)

2012-05-18 Thread Asias He

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 15:59:58 +0800
Source: lcrt
Binary: lcrt
Architecture: source i386
Version: 1.1.2-1
Distribution: unstable
Urgency: low
Maintainer: Asias He asias.he...@gmail.com
Changed-By: Asias He asias.he...@gmail.com
Description: 
 lcrt   - graphic Linux remote login tool
Changes: 
 lcrt (1.1.2-1) unstable; urgency=low
 .
   * New upstream release.
   * Bump standard version
Checksums-Sha1: 
 9787b82def2e8ed900a199b4b2e93e23d004f3e3 1858 lcrt_1.1.2-1.dsc
 8be6b0376b2e7b8bf8de1f3715a1170b3723419a 469315 lcrt_1.1.2.orig.tar.gz
 a3b6674150844c7de1f172aca18fbb5bca081cfe 1986 lcrt_1.1.2-1.debian.tar.gz
 2a691d916fd85b86f9e00cf4b021430b736971e5 323362 lcrt_1.1.2-1_i386.deb
Checksums-Sha256: 
 dde7bc9cf98d4d48a281d6122191f6b9b59e3c20ff2f9cb555837480b5199e78 1858 
lcrt_1.1.2-1.dsc
 d1d9d806babcc683551ae36bc3fb77f039fabac108132417e41d9b57cde55be6 469315 
lcrt_1.1.2.orig.tar.gz
 0527e358e2013670e94b482c8ed32f47d611c1f4ef46ceead515bb1f5b010069 1986 
lcrt_1.1.2-1.debian.tar.gz
 cebf967051607a71f64b4ab11f3b88d6c4c15b2665cc3d50da9dfba4a8431ea9 323362 
lcrt_1.1.2-1_i386.deb
Files: 
 2f97f9dcead9e6ea51cc4d7b83193aed 1858 net optional lcrt_1.1.2-1.dsc
 7e5b9e30a6c9297bfad8b2b3d6f217a9 469315 net optional lcrt_1.1.2.orig.tar.gz
 6277b6b22759f6decb67db6474cee448 1986 net optional lcrt_1.1.2-1.debian.tar.gz
 f04930198c6aa3b8bd8b46535dcb631e 323362 net optional lcrt_1.1.2-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJPtgQGAAoJEK7JmSstf/GAXJsP/jXscNZ4q++9xPKj0qj+sHZn
xuJXpY47aWXLSFqYZ1fvbkv0jxJDPZuAOt4qEEKriYogiXIFw0yBUN/E2+lakBFt
IKzxN5sqtbSq99Iyfs3w5XtgzXG9ioQX/rN4cJMANSSrHFVtNQFCAoW6yNwlw6UU
bUgSLVyU8M37fhICs21hEL/xw+PbOSv3iNdBfAC5JGy8L1640q6u0c/jM/V4G4iw
ZgLiDLq1hMPBGbVWWHlkWwPLFQxGj/DnR4NDpXiBFM1ADepEGjFjsWO6ZxTIKvza
Eoo3Bc6LFhV0liDzbvz7WiZqQbd2G1riv7tdf4J85RIQShYkx9EUySEXtF8AL0uA
29QNuNIk9lbnU0nD5bAGtaE/JraEa8EJC+/eKTVxWealoaOnJDlwGkFh5DrxNFUD
e+7SDemVTL3kutss2QEw0oEM6NBOxySUe0jmnCP0ZKQJCz8gMDjTXQvMe8Fypkz5
TK50/SjMXnB+y0ZMwqI1aogn0oKVf8BR0zA5oFV01Go3kZSL8X3SL61XCEOiDCQ3
aCylnhGu9wId5uFo+c+V7BvXo2as7iWxeN/RwbAWRENNPMxf6OpmNv2oTDB7iDzK
iDpSoBz3gWLhTBmBJEL6bsYsKd4YCkA4Hu+B0hMM79SY8pD8WHwmkEwUWKsOP/y/
/CLLV9LE4zsCZARjhUCy
=MJNL
-END PGP SIGNATURE-


Accepted:
lcrt_1.1.2-1.debian.tar.gz
  to main/l/lcrt/lcrt_1.1.2-1.debian.tar.gz
lcrt_1.1.2-1.dsc
  to main/l/lcrt/lcrt_1.1.2-1.dsc
lcrt_1.1.2-1_i386.deb
  to main/l/lcrt/lcrt_1.1.2-1_i386.deb
lcrt_1.1.2.orig.tar.gz
  to main/l/lcrt/lcrt_1.1.2.orig.tar.gz


-- 
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/e1svjv6-0007ys...@franck.debian.org

Accepted llvm-2.9 2.9+dfsg-6 (source i386 all)

2012-05-18 Thread Sylvestre Ledru

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 09:24:01 +0200
Source: llvm-2.9
Binary: libllvm2.9 llvm-2.9 llvm-2.9-runtime llvm-2.9-dev libllvm-2.9-ocaml-dev 
llvm-2.9-doc llvm-2.9-examples llvm-2.9-source
Architecture: source i386 all
Version: 2.9+dfsg-6
Distribution: unstable
Urgency: low
Maintainer: LLVM Packaging Team pkg-llvm-t...@lists.alioth.debian.org
Changed-By: Sylvestre Ledru sylves...@debian.org
Description: 
 libllvm-2.9-ocaml-dev - Low-Level Virtual Machine (LLVM), bindings for OCaml
 libllvm2.9 - Low-Level Virtual Machine (LLVM), runtime library
 llvm-2.9   - Low-Level Virtual Machine (LLVM)
 llvm-2.9-dev - Low-Level Virtual Machine (LLVM), libraries and headers
 llvm-2.9-doc - Low-Level Virtual Machine (LLVM), documentation
 llvm-2.9-examples - Low-Level Virtual Machine (LLVM), examples
 llvm-2.9-runtime - Low-Level Virtual Machine (LLVM), bytecode interpreter
 llvm-2.9-source - Low-Level Virtual Machine (LLVM), source code
Closes: 673266
Changes: 
 llvm-2.9 (2.9+dfsg-6) unstable; urgency=low
 .
   [ Vincent Legout ]
   * debian/patches/0035-gcc-4.7.patch: Fix FTBFS with gcc-4.7.
 (Closes: #673266)
Checksums-Sha1: 
 fefdec975b7198e2e0681f8c45e77e0f32ee74e6 2001 llvm-2.9_2.9+dfsg-6.dsc
 c0e6359ab91aba81f3a309101208241cd86d94be 32065 
llvm-2.9_2.9+dfsg-6.debian.tar.gz
 c11c2a802072b8e249cb78e0524c69cb10f0ca3b 6751966 libllvm2.9_2.9+dfsg-6_i386.deb
 348dea1f3091fb128435cabb6d6e8b8b1e5836a5 1368146 llvm-2.9_2.9+dfsg-6_i386.deb
 c561ef54e249cd9eb3561cab0d434a25f2f2698e 34334 
llvm-2.9-runtime_2.9+dfsg-6_i386.deb
 8a922d688080c90f905fce9daaefcb0725768783 11276770 
llvm-2.9-dev_2.9+dfsg-6_i386.deb
 8d386f81fc71bcad4e21a3120b56cfd5e92545ff 254598 
libllvm-2.9-ocaml-dev_2.9+dfsg-6_i386.deb
 b44b7942474d9d5ece931d0bc9c4a61a9e5335e9 967516 llvm-2.9-doc_2.9+dfsg-6_all.deb
 6a66ffa4f99ce789254b1a1a6a44274b9612c56c 112162 
llvm-2.9-examples_2.9+dfsg-6_all.deb
 36ccb5b14452d44b98b5fa9318704877c2c59e61 6741190 
llvm-2.9-source_2.9+dfsg-6_all.deb
Checksums-Sha256: 
 4c0ca20eff7e6aa426b9de911559351e6eedc49a5c4b4a06c40a13cea90db949 2001 
llvm-2.9_2.9+dfsg-6.dsc
 1cb376e2e29a1e977876b61c6556313d8b38bb8fc8895ba24d03997ee7c1abd7 32065 
llvm-2.9_2.9+dfsg-6.debian.tar.gz
 e77f09b10695e2c8a94012a7edfffaba4dd200b7bf9422d85129db6a7cf1b264 6751966 
libllvm2.9_2.9+dfsg-6_i386.deb
 3fde3eba2afc745668472d2b95c4a5e995c819cb793fb783557604f76a35d392 1368146 
llvm-2.9_2.9+dfsg-6_i386.deb
 f88f9d3b2528f5d524c1c3ebde0a274c59e63e7c065a1ba35bf8eb314e9d87d1 34334 
llvm-2.9-runtime_2.9+dfsg-6_i386.deb
 131ac5e778e80f02849353716b3623e4d51f4ef5b2b1a06780c774e14734d771 11276770 
llvm-2.9-dev_2.9+dfsg-6_i386.deb
 c10954f2f3b75c4a927219753527331b5309c22a38a1cb10adea110c1d85f4b3 254598 
libllvm-2.9-ocaml-dev_2.9+dfsg-6_i386.deb
 ccb4ba466129d7e9ee97b9d2a525f9ad0f5994d06db5ad825799ca60427ea16b 967516 
llvm-2.9-doc_2.9+dfsg-6_all.deb
 7733bfc853cf4888c234e6bc46a84a0502b8e14face2035ac9fd88dd2b9d4532 112162 
llvm-2.9-examples_2.9+dfsg-6_all.deb
 8cfc222e1ebcaf159d0b53c9dcb39f3040d9d39fe523967960b33df4b5f5df79 6741190 
llvm-2.9-source_2.9+dfsg-6_all.deb
Files: 
 16628d2e83c192cacf550bbb7618c3d5 2001 devel optional llvm-2.9_2.9+dfsg-6.dsc
 b212c3c708f1a31e009f712427e926e5 32065 devel optional 
llvm-2.9_2.9+dfsg-6.debian.tar.gz
 2b8baa01f23f999a54546d3554c8610f 6751966 libs optional 
libllvm2.9_2.9+dfsg-6_i386.deb
 a60f16c24dd05361177b19133704993a 1368146 devel optional 
llvm-2.9_2.9+dfsg-6_i386.deb
 deae28eb629c2f9bef20cb603479ea86 34334 devel optional 
llvm-2.9-runtime_2.9+dfsg-6_i386.deb
 772a07f66379c9caa54e4b151aee9263 11276770 devel optional 
llvm-2.9-dev_2.9+dfsg-6_i386.deb
 28ff1a86cdd423c7fe003bd49901a894 254598 ocaml optional 
libllvm-2.9-ocaml-dev_2.9+dfsg-6_i386.deb
 1492c82710ae3f54f56ff215796da068 967516 doc optional 
llvm-2.9-doc_2.9+dfsg-6_all.deb
 5e73f1bc66ffecf370fbca81ed556afb 112162 doc optional 
llvm-2.9-examples_2.9+dfsg-6_all.deb
 a8be43ea0fa7b001db4475e9435daed1 6741190 devel optional 
llvm-2.9-source_2.9+dfsg-6_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAk+1/xoACgkQiOXXM92JlhCjsQCffei0SYeMV/xr4yZi0YfHGx1n
3gYAoOtx6yZUky418r3qUNGjMcOZ0Ct+
=Udk0
-END PGP SIGNATURE-


Accepted:
libllvm-2.9-ocaml-dev_2.9+dfsg-6_i386.deb
  to main/l/llvm-2.9/libllvm-2.9-ocaml-dev_2.9+dfsg-6_i386.deb
libllvm2.9_2.9+dfsg-6_i386.deb
  to main/l/llvm-2.9/libllvm2.9_2.9+dfsg-6_i386.deb
llvm-2.9-dev_2.9+dfsg-6_i386.deb
  to main/l/llvm-2.9/llvm-2.9-dev_2.9+dfsg-6_i386.deb
llvm-2.9-doc_2.9+dfsg-6_all.deb
  to main/l/llvm-2.9/llvm-2.9-doc_2.9+dfsg-6_all.deb
llvm-2.9-examples_2.9+dfsg-6_all.deb
  to main/l/llvm-2.9/llvm-2.9-examples_2.9+dfsg-6_all.deb
llvm-2.9-runtime_2.9+dfsg-6_i386.deb
  to main/l/llvm-2.9/llvm-2.9-runtime_2.9+dfsg-6_i386.deb
llvm-2.9-source_2.9+dfsg-6_all.deb
  to main/l/llvm-2.9/llvm-2.9-source_2.9+dfsg-6_all.deb
llvm-2.9_2.9+dfsg-6.debian.tar.gz
  to main/l/llvm-2.9/llvm-2.9_2.9+dfsg-6.debian.tar.gz
llvm-2.9_2.9+dfsg-6.dsc
  to

Accepted lxde-common 0.5.5-5 (source all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 10:06:49 +0200
Source: lxde-common
Binary: lxde-common
Architecture: source all
Version: 0.5.5-5
Distribution: unstable
Urgency: low
Maintainer: Debian LXDE Maintainers lxde-deb...@lists.lxde.org
Changed-By: Daniel Baumann dan...@debian.org
Description: 
 lxde-common - LXDE configuration data
Changes: 
 lxde-common (0.5.5-5) unstable; urgency=low
 .
   [ Daniel Baumann ]
   * Updating Andrews name and email in default-config.patch.
 .
   [ Sergey Slipchenko ]
   * Fixing spelling typo in debian/lxde-common.lintian-overrides.
 .
   [ Andrew Lee (李健秋) ]
   * Dropping build-depends on libgtk2.0-dev.
 .
   [ Daniel Baumann ]
   * Dropping further unecessary build-depends.
 .
   [ Sergey Slipchenko ]
   * Dropping gnome-polkit.patch.
   * Using lxlock instead of xscreensaver-command -lock to lock screen.
   * Dropping to use encoding field in lxde-screenlock desktop file.
Checksums-Sha1: 
 cfa0f2b5bc9510784f8161b6c7abc6f8288794cc 1323 lxde-common_0.5.5-5.dsc
 b74e805a7181c51818b3707d49c4916e22536af0 7720 lxde-common_0.5.5-5.debian.tar.xz
 b9f4c1577a2810808b130e355102cbaac0d734a7 815542 lxde-common_0.5.5-5_all.deb
Checksums-Sha256: 
 abf04c27ecfa0ef30b39c581e9b1628bc9f691b491638aca9fed40022c3ee6d5 1323 
lxde-common_0.5.5-5.dsc
 0317088b4d4798f8265723e2b7716767cd18c851b88d89a09060e190f10a5ec6 7720 
lxde-common_0.5.5-5.debian.tar.xz
 a7a8a05f4cc896e304bf53887a11fea6154cf23acb038c11a8b001c9b768030f 815542 
lxde-common_0.5.5-5_all.deb
Files: 
 c16d410ea6a950a645e5e23383ebe3d5 1323 x11 optional lxde-common_0.5.5-5.dsc
 f2653ce8d411a048fdd32ed3e07ce078 7720 x11 optional 
lxde-common_0.5.5-5.debian.tar.xz
 b64884894ec64644008952443482c5bd 815542 x11 optional 
lxde-common_0.5.5-5_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+2A48ACgkQ+C5cwEsrK57uzwCeJ/fMYFjflxfT9ZMbz06oocMF
zWQAoJuffh+sT3OlPniZ54Lp+4z1SO7Z
=bYcx
-END PGP SIGNATURE-


Accepted:
lxde-common_0.5.5-5.debian.tar.xz
  to main/l/lxde-common/lxde-common_0.5.5-5.debian.tar.xz
lxde-common_0.5.5-5.dsc
  to main/l/lxde-common/lxde-common_0.5.5-5.dsc
lxde-common_0.5.5-5_all.deb
  to main/l/lxde-common/lxde-common_0.5.5-5_all.deb


-- 
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/e1svjx0-na...@franck.debian.org

Accepted lxde-metapackages 2 (source all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 10:08:16 +0200
Source: lxde-metapackages
Binary: lxde-core lxde
Architecture: source all
Version: 2
Distribution: unstable
Urgency: low
Maintainer: Debian LXDE Maintainers lxde-deb...@lists.lxde.org
Changed-By: Daniel Baumann dan...@debian.org
Description: 
 lxde   - LXDE metapackage
 lxde-core  - LXDE core metapackage
Changes: 
 lxde-metapackages (2) unstable; urgency=low
 .
   [ Andrew Lee (李健秋) ]
   * Recommends on gdm3.
   * Adjusting Recommends for lxde meta package (policykit-1-gnome |
 lxpolkit, network-manager-gnome | connman).
 .
   [ Sergey Slipchenko ]
   * Recommend lxpolkit instead of policykit-1-gnome.
 .
   [ Daniel Baumann ]
   * Removing superflous alternative browser in recommends.
   * Restoring original recommends on iceweasel, now that it has improved
 a lot.
Checksums-Sha1: 
 27bce7c2e201dcdf69dcba4105ef89e61f7a4434 1089 lxde-metapackages_2.dsc
 096f81c360873394bb27284e6459cd7e20f34e59 2052 lxde-metapackages_2.tar.xz
 e1775416e5ab3fa712376ab6d47c703ea7fc8040 2218 lxde-core_2_all.deb
 0de5eb87b3d3ce0e4aa26c2f5eba0cf618de749f 2276 lxde_2_all.deb
Checksums-Sha256: 
 c996bd0463eeac4d1bf72f542468f40e9fdd2191e96515e3f3ef53487d2357e1 1089 
lxde-metapackages_2.dsc
 a71d37cdd6ab91ba95824bda356ea88f4d2f6b1ae288baebd8aef6acd0688c61 2052 
lxde-metapackages_2.tar.xz
 6e55896c2e5765ba047b238840b5ba72c27681c12a52269fb0ae07c456405a07 2218 
lxde-core_2_all.deb
 6523b44480d40286768f851c89bd948c030c658bba4a697559f83e4a29739870 2276 
lxde_2_all.deb
Files: 
 a885495a46ea6f6d557956d40fc22419 1089 metapackages optional 
lxde-metapackages_2.dsc
 021b6a18f026803fd8ef73734c0dcea9 2052 metapackages optional 
lxde-metapackages_2.tar.xz
 f5de7206ab3314f33596221fed9484df 2218 metapackages optional lxde-core_2_all.deb
 1ad8064e2e0a67c8e303d42d40091cc6 2276 metapackages optional lxde_2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+2A9MACgkQ+C5cwEsrK55OZQCfTXFghqDeljq6YWgB970R7mw9
O8IAn1Uao5Y5ZlG5fMOu3pGSpYf1Gtdg
=tGvm
-END PGP SIGNATURE-


Accepted:
lxde-core_2_all.deb
  to main/l/lxde-metapackages/lxde-core_2_all.deb
lxde-metapackages_2.dsc
  to main/l/lxde-metapackages/lxde-metapackages_2.dsc
lxde-metapackages_2.tar.xz
  to main/l/lxde-metapackages/lxde-metapackages_2.tar.xz
lxde_2_all.deb
  to main/l/lxde-metapackages/lxde_2_all.deb


-- 
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/e1svjxj-ty...@franck.debian.org

Accepted lxpolkit 0.1.0-3 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 09:48:38 +0200
Source: lxpolkit
Binary: lxpolkit lxpolkit-dbg
Architecture: source i386
Version: 0.1.0-3
Distribution: unstable
Urgency: low
Maintainer: Debian LXDE Maintainers lxde-deb...@lists.lxde.org
Changed-By: Daniel Baumann dan...@debian.org
Description: 
 lxpolkit   - LXDE PolicyKit authentication agent
 lxpolkit-dbg - LXDE PolicyKit authentication agent (debug)
Changes: 
 lxpolkit (0.1.0-3) unstable; urgency=low
 .
   [ Sergey Slipchenko ]
   * Adding patch to allow building with enabled hardening buildflags.
 .
   [ Daniel Baumann ]
   * Correcting destdir in install override in rules to fix empty binary
 packages.
Checksums-Sha1: 
 0071f9d4c3b1fc3d3db40e12df8b8a9cad257da1 1377 lxpolkit_0.1.0-3.dsc
 9bb931ee3ed8e92ac016c0c447446863eb9dae05 3740 lxpolkit_0.1.0-3.debian.tar.xz
 b584534e78202fb77c72ed25c522b6fd5d081849 19022 lxpolkit_0.1.0-3_i386.deb
 e42e52796a7022e7ce9a5e2f98ef69e90b7a6ac2 25316 lxpolkit-dbg_0.1.0-3_i386.deb
Checksums-Sha256: 
 63c2d8f5a08077732ed05a1480f91388219ceb4b3136932fbb85824cacb659f6 1377 
lxpolkit_0.1.0-3.dsc
 b0bf2a15a699d0e1498ac910dd451845545e4515a597af8d81a11e1d8817d746 3740 
lxpolkit_0.1.0-3.debian.tar.xz
 81adbcb3e8651e7544f0f5b1f9d8bcebb1d9559371a2a88610f4e1f1133856cf 19022 
lxpolkit_0.1.0-3_i386.deb
 85116bf13e1ab883a10a2c42143d346a0fcb13686543f4425cdd75c57808dd45 25316 
lxpolkit-dbg_0.1.0-3_i386.deb
Files: 
 c8fcd221d7cba4bfc7ec2ac2c0aaa0a9 1377 x11 optional lxpolkit_0.1.0-3.dsc
 8b701916897f4489f157209c9278f46b 3740 x11 optional 
lxpolkit_0.1.0-3.debian.tar.xz
 a187759cb72d5f5bfb802622bc8c2288 19022 x11 optional lxpolkit_0.1.0-3_i386.deb
 65ba7dd221d53022cbc740b2de346de4 25316 debug extra 
lxpolkit-dbg_0.1.0-3_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+2ACEACgkQ+C5cwEsrK55VGACfWq0xZJnVxMW7E/wvp8YGzGtV
BZAAn1jOPRfi4qZb70UBB8lmNgso8SWv
=9eqG
-END PGP SIGNATURE-


Accepted:
lxpolkit-dbg_0.1.0-3_i386.deb
  to main/l/lxpolkit/lxpolkit-dbg_0.1.0-3_i386.deb
lxpolkit_0.1.0-3.debian.tar.xz
  to main/l/lxpolkit/lxpolkit_0.1.0-3.debian.tar.xz
lxpolkit_0.1.0-3.dsc
  to main/l/lxpolkit/lxpolkit_0.1.0-3.dsc
lxpolkit_0.1.0-3_i386.deb
  to main/l/lxpolkit/lxpolkit_0.1.0-3_i386.deb


-- 
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/e1svjxa-ay...@franck.debian.org

Accepted odin 1.8.5-2 (source amd64)

2012-05-18 Thread Michael Hanke

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 09:39:29 +0200
Source: odin
Binary: odin mitools libodin-dev
Architecture: source amd64
Version: 1.8.5-2
Distribution: unstable
Urgency: low
Maintainer: NeuroDebian Team t...@neuro.debian.net
Changed-By: Michael Hanke m...@debian.org
Description: 
 libodin-dev - static libraries and header for ODIN sequences
 mitools- view, convert and perform basic maths with medical image datasets
 odin   - develop, simulate and run magnetic resonance sequences
Closes: 673217
Changes: 
 odin (1.8.5-2) unstable; urgency=low
 .
   * Amend patch for GCC 4.7 compatibility with another missing header
 include. Thanks to Samuel Thibault for the report and Thies Jochimsen
 for the upstream fix (Closes: #673217).
Checksums-Sha1: 
 d53093c89e9e17f204090d729db6c4aed14ed982 2161 odin_1.8.5-2.dsc
 332e9ec7cec95d03ce7e027aab412d85c273370d 6665 odin_1.8.5-2.debian.tar.gz
 3245dcadce6887dcf3befd2a7fe500b7d612ff12 1538542 odin_1.8.5-2_amd64.deb
 8bd0fe54d5ba65c46888d78ec3c53a26468a7e6d 2485560 mitools_1.8.5-2_amd64.deb
 ef871fe9680b673dd6186ec59cfcf052919f2a4c 4417306 libodin-dev_1.8.5-2_amd64.deb
Checksums-Sha256: 
 225bb996c4c20aa1c69fd193899e5e454bd4199adf9721cac3a9d529fe9e4425 2161 
odin_1.8.5-2.dsc
 1ab796c5bbbe5378be61a82af7336f805e967c74dae634de24260a0595f94e97 6665 
odin_1.8.5-2.debian.tar.gz
 a841b14f37fc796f81872d1dbd2528a54ad1688cb9cf1db98482beec75174927 1538542 
odin_1.8.5-2_amd64.deb
 6f6074f3f31cfb2867a4f033bfc39dbc2908f5f00229d240dd840a3b30b1b988 2485560 
mitools_1.8.5-2_amd64.deb
 01afd29ca679789c55ccfe1b77a584f0ca3f0ceb0f7002d270b07dc303506c62 4417306 
libodin-dev_1.8.5-2_amd64.deb
Files: 
 0e152107b0dbc1c85d77fafeee9d2594 2161 science extra odin_1.8.5-2.dsc
 3c6302b7fcdf7cc2ed5990188e5fa247 6665 science extra odin_1.8.5-2.debian.tar.gz
 18c72acb4a0ef94826df3f7b8fc72b6f 1538542 science extra odin_1.8.5-2_amd64.deb
 e7bafabb9f4f77fb697fe21ce1655a8b 2485560 science extra 
mitools_1.8.5-2_amd64.deb
 704ca60b2b4c8de77d86b66c868fe2e5 4417306 libdevel extra 
libodin-dev_1.8.5-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJPthDEAAoJEMBz0ih/+56bi4kP/149uhkAoUVTHrAlIsHUwtNB
pGK0GK8ppOR9ZY5nCJyxRGQS+DcsIAWpi2xR91bWhlhxMkMWFav+uiPDYOEIPXkd
liDmFyEXZfTAn13iWb+dbl/oudBuKO001ze4R6DTNEbEAeLL1jlZRSB8qi8LoTet
pQCeaiM/cx7xgQcrAyJsCpLykaQTk2G1vLIvslCuRh2l6+OKSuLxLmczI09jS0Cd
DQ7sjTvpOXGnxV3FHOQP7dFfx3TD6FnJvPk4A7hjE0+CKladpTSanvplTQYFjHxR
Qx12J3rl+lkC8RQTpzD48VdrfxKwxHtUaSipNqLIi2L98bOGK07oZMy6PyMRxeiE
O4ux7ZtgHLiESHgxV44SjSup7g3a/H4nU8aJ4Y/CtDk3Y6m4J0tDLrwm8bE3HbHe
COm4lCTqAUbGMgTBJlTfYnD9wfFXvShnZUKPkTEVBxeZuy0VjH/tnmlcS0UGyyhz
24MWh1cwDCvxp3vYro2hu6X4h3GWwuH7w27MiAek47v9EWFzf84hlt3a1VmbYVo5
uE6VqE6y7IDjfZFlh9YTG22zWl6qVgXdsd70vHCT3YfMSgoh3+h7zMOO5GWh9khe
0cFfmNkdR7PjWE+4qI6S1tD2RatWRppsiwBJcVr6YRtAPhLfue1i6cdf6aZ6iil+
VCpA6NoamiSC9aX5cDmY
=p1t4
-END PGP SIGNATURE-


Accepted:
libodin-dev_1.8.5-2_amd64.deb
  to main/o/odin/libodin-dev_1.8.5-2_amd64.deb
mitools_1.8.5-2_amd64.deb
  to main/o/odin/mitools_1.8.5-2_amd64.deb
odin_1.8.5-2.debian.tar.gz
  to main/o/odin/odin_1.8.5-2.debian.tar.gz
odin_1.8.5-2.dsc
  to main/o/odin/odin_1.8.5-2.dsc
odin_1.8.5-2_amd64.deb
  to main/o/odin/odin_1.8.5-2_amd64.deb


-- 
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/e1svjav-0001ex...@franck.debian.org

Accepted tig 1.0-1 (source amd64)

2012-05-18 Thread Sebastian Harl

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 17 May 2012 18:15:46 +0200
Source: tig
Binary: tig
Architecture: source amd64
Version: 1.0-1
Distribution: unstable
Urgency: low
Maintainer: Sebastian Harl tok...@debian.org
Changed-By: Sebastian Harl tok...@debian.org
Description: 
 tig- ncurses-based Git repository browser
Closes: 626124 635546 656810
Changes: 
 tig (1.0-1) UNRELEASED; urgency=low
 .
   * New upstream release; thanks to Salvatore Bonaccorso and Romain Francoise
 for reporting this (Closes: #656810).
 - Fixed substitution of %(xxx) in prompt commands; thanks to Daniel T Chen
   for reporting this (Closes: #635546).
 - Fixed 'go to a line' feature; thanks to Christian Ohm for reporting this
   (Closes: #626124).
   * debian/rules:
 - Don't remove 'test-graph'; it is no longer installed by 'make install'.
 - Don't try to install TODO; it no longer exists.
 - Split build target into build-{arch,indep} as recommended by policy.
 - Enabled harding build flags (use dpkg-buildflags).
   * debian/control:
 - Updated standards-version to 3.9.3 -- no changes.
Checksums-Sha1: 
 52e2dfe9a250a1d8319d1f80d6bb3a577406e9d2 1144 tig_1.0-1.dsc
 3fe744f79d244285b6e00b472e35967746910305 188543 tig_1.0.orig.tar.gz
 66004d083aaa71db84c300c1e88349cc4b3f6659 5998 tig_1.0-1.diff.gz
 6d3aa23e5cf94f468e4a14a5be1db38f47c80e52 244112 tig_1.0-1_amd64.deb
Checksums-Sha256: 
 076e6d007ce375ecf622dd384cffef47e577ea58ec4f3f0d0eb5e1d5bed8502b 1144 
tig_1.0-1.dsc
 e1ecadef82027a94a6489e84a5c02fd5c0d4977bcb13ba2df0a52cca05ad6f71 188543 
tig_1.0.orig.tar.gz
 1f0a590b9781db2ff98a47f7fe80dd9bbee455fb9e7a3d29c62c19e5b244c158 5998 
tig_1.0-1.diff.gz
 79b399581e96aeb6ee7a31065cd7ce69c672faadd0c048522fbd30afdf5f11a1 244112 
tig_1.0-1_amd64.deb
Files: 
 fb4bb4e995f7f3f018d7d1de0eb71ef6 1144 vcs optional tig_1.0-1.dsc
 a2d414d1cebbc9cd4f3d545bc6f225c6 188543 vcs optional tig_1.0.orig.tar.gz
 4d77a865326d1802301080673d18a631 5998 vcs optional tig_1.0-1.diff.gz
 da12be9c0837ad8f0a867e2291b8ee4e 244112 vcs optional tig_1.0-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAk+1/pcACgkQEFEKc4UBx/wEVQCaA29oPbjmuYlxe6eGtwoHDcSH
Yz8An25DCCBfGcmPz1AaUoidHOG8WYD+
=bGOZ
-END PGP SIGNATURE-


Accepted:
tig_1.0-1.diff.gz
  to main/t/tig/tig_1.0-1.diff.gz
tig_1.0-1.dsc
  to main/t/tig/tig_1.0-1.dsc
tig_1.0-1_amd64.deb
  to main/t/tig/tig_1.0-1_amd64.deb
tig_1.0.orig.tar.gz
  to main/t/tig/tig_1.0.orig.tar.gz


-- 
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/e1svjxv-0006gf...@franck.debian.org

Accepted atlas 3.8.4-4~exp5 (source all i386)

2012-05-18 Thread Sylvestre Ledru

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 15 May 2012 18:06:16 +0200
Source: atlas
Binary: libatlas3-base libatlas3gf-base libatlas-base-dev libatlas-dev 
libatlas-test libatlas-doc
Architecture: source all i386
Version: 3.8.4-4~exp5
Distribution: experimental
Urgency: low
Maintainer: Debian Science Team 
debian-science-maintain...@lists.alioth.debian.org
Changed-By: Sylvestre Ledru sylves...@debian.org
Description: 
 libatlas-base-dev - Automatically Tuned Linear Algebra Software, generic static
 libatlas-dev - Automatically Tuned Linear Algebra Software, C header files
 libatlas-doc - Automatically Tuned Linear Algebra Software, documentation
 libatlas-test - Automatically Tuned Linear Algebra Software, test programs
 libatlas3-base - Automatically Tuned Linear Algebra Software, generic shared
 libatlas3gf-base - Transitional package to libatlas3-base
Closes: 643767
Changes: 
 atlas (3.8.4-4~exp5) experimental; urgency=low
 .
   * libblas and liblapack were not correctly named causing upgrades to fails.
 (Closes: #643767)
   * Update the README.Debian and TODO regarding recent changes
Checksums-Sha1: 
 fbfaf2cb371838af0b455dec16f2d638061980bc 1701 atlas_3.8.4-4~exp5.dsc
 b878c376d4908277f33ad74ffaa0b915ee36577e 32433 atlas_3.8.4-4~exp5.debian.tar.gz
 ebec4a5d7ed39a84575be46bc61582136f860867 43232 
libatlas-dev_3.8.4-4~exp5_all.deb
 6b8006f019523567ebc311d54f273b6725fd0c65 1141902 
libatlas-doc_3.8.4-4~exp5_all.deb
 534912b49e0a6d1316392919d723e5519b2acee9 5363292 
libatlas3-base_3.8.4-4~exp5_i386.deb
 371047005fefdf7f38f55433af2952f6a42afce9 33100 
libatlas3gf-base_3.8.4-4~exp5_i386.deb
 51b88bc840a914c7799141cc5d9072d5f422b38a 6532898 
libatlas-base-dev_3.8.4-4~exp5_i386.deb
 18db885028325b737fe4c0d2daee2c00772b262f 13124670 
libatlas-test_3.8.4-4~exp5_i386.deb
Checksums-Sha256: 
 fda265a3c7dc14c2116174d9b4d2af305fd6bab897764df0c3c4b59ac3eff120 1701 
atlas_3.8.4-4~exp5.dsc
 3b91ac29b4687c1141b561ba08ab1206d2465cb6313a20b7520dc2e0154b90f1 32433 
atlas_3.8.4-4~exp5.debian.tar.gz
 68ac05c76f294a7d2bc169977c9a0382ba4e332ee3bcc4f600b72dc790549b49 43232 
libatlas-dev_3.8.4-4~exp5_all.deb
 43ec9c5c80bd2aa8a309473b2f2bcf01af7e644849cee3f3c18148f7de5b50c7 1141902 
libatlas-doc_3.8.4-4~exp5_all.deb
 50cbdfa650018732076ccde2ede4d0395f868c08ad35c724adbca118b0ee1c87 5363292 
libatlas3-base_3.8.4-4~exp5_i386.deb
 6aea4c7c3e3357520e3bd95eb48c6985778162223d76aa05bbd6dc65a4824ba5 33100 
libatlas3gf-base_3.8.4-4~exp5_i386.deb
 2588c7f0bf9964b4ebd0e3fda019eaac45ac492b0b10af7c19a2abb8e38f3ec2 6532898 
libatlas-base-dev_3.8.4-4~exp5_i386.deb
 78030128e207e8c0e3926c3fec36641d25a5a235f66437f43ccc81094657f439 13124670 
libatlas-test_3.8.4-4~exp5_i386.deb
Files: 
 4a522c27da1f19482dafa8ffba3b1c33 1701 devel optional atlas_3.8.4-4~exp5.dsc
 5ccfb5422ea3a7374280bfd023dc13d5 32433 devel optional 
atlas_3.8.4-4~exp5.debian.tar.gz
 308664ca188ea84feca4e09b1456f6c1 43232 libdevel optional 
libatlas-dev_3.8.4-4~exp5_all.deb
 75d5ee9f3f39953f00486c0208d40d18 1141902 doc optional 
libatlas-doc_3.8.4-4~exp5_all.deb
 870e4b14288b86a7f5b9924d1986dd51 5363292 libs optional 
libatlas3-base_3.8.4-4~exp5_i386.deb
 d0258064f1681b73a1a2491d19a38cd6 33100 libs optional 
libatlas3gf-base_3.8.4-4~exp5_i386.deb
 2a6c824c87c485089f06357b134ea4f0 6532898 libdevel optional 
libatlas-base-dev_3.8.4-4~exp5_i386.deb
 176fd375db2b3c4b05aefff257238cad 13124670 devel optional 
libatlas-test_3.8.4-4~exp5_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAk+2GOQACgkQiOXXM92JlhCcqACgvlkmFVKTm3fiIyPW1N/4UgVa
yBMAn1lLuP073gir2HHe6TLNuLkBLfC2
=erAP
-END PGP SIGNATURE-


Accepted:
atlas_3.8.4-4~exp5.debian.tar.gz
  to main/a/atlas/atlas_3.8.4-4~exp5.debian.tar.gz
atlas_3.8.4-4~exp5.dsc
  to main/a/atlas/atlas_3.8.4-4~exp5.dsc
libatlas-base-dev_3.8.4-4~exp5_i386.deb
  to main/a/atlas/libatlas-base-dev_3.8.4-4~exp5_i386.deb
libatlas-dev_3.8.4-4~exp5_all.deb
  to main/a/atlas/libatlas-dev_3.8.4-4~exp5_all.deb
libatlas-doc_3.8.4-4~exp5_all.deb
  to main/a/atlas/libatlas-doc_3.8.4-4~exp5_all.deb
libatlas-test_3.8.4-4~exp5_i386.deb
  to main/a/atlas/libatlas-test_3.8.4-4~exp5_i386.deb
libatlas3-base_3.8.4-4~exp5_i386.deb
  to main/a/atlas/libatlas3-base_3.8.4-4~exp5_i386.deb
libatlas3gf-base_3.8.4-4~exp5_i386.deb
  to main/a/atlas/libatlas3gf-base_3.8.4-4~exp5_i386.deb


-- 
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/e1svkfi-0002h9...@franck.debian.org

Accepted fcitx-hangul 0.1.1-1 (source amd64)

2012-05-18 Thread YunQiang Su

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 15 May 2012 16:09:04 +0800
Source: fcitx-hangul
Binary: fcitx-hangul
Architecture: source amd64
Version: 0.1.1-1
Distribution: unstable
Urgency: low
Maintainer: IME Packaging Team pkg-ime-de...@lists.alioth.debian.org
Changed-By: YunQiang Su wzss...@gmail.com
Description: 
 fcitx-hangul - Free Chinese Input Toy of X - hangul module
Changes: 
 fcitx-hangul (0.1.1-1) unstable; urgency=low
 .
   * New upstream release.
   * Switch to team maintaince and add DMUA.
Checksums-Sha1: 
 7800739cfde3c0727eea48afe36c2dbf8892b7b9 1711 fcitx-hangul_0.1.1-1.dsc
 45ce2f8ee5b9c1f7940bee5e0e424391602aa0e3 24756 fcitx-hangul_0.1.1.orig.tar.xz
 41259a9603ed8d4c3fd2befab694fd661458cf53 2387 
fcitx-hangul_0.1.1-1.debian.tar.gz
 d73edcf6c989ed9e17578af4d28c105171f334bc 24174 fcitx-hangul_0.1.1-1_amd64.deb
Checksums-Sha256: 
 6d42fb9bb2e793897ff77f361a7c0e48465350750d6f43bdb2b56b17fb277737 1711 
fcitx-hangul_0.1.1-1.dsc
 61a2e8f437060ea809b09fb8821da8a4e1307c134eef976e647ffbc19d999dde 24756 
fcitx-hangul_0.1.1.orig.tar.xz
 ef6e94e0056bce4474956249c1ddd44e6caaca537e29674906e22d98b3526109 2387 
fcitx-hangul_0.1.1-1.debian.tar.gz
 6aecf1c373cf17e5711e492717e702ed41a3d81188cea10b26100c051f5b5f14 24174 
fcitx-hangul_0.1.1-1_amd64.deb
Files: 
 b29c6da75ef1ef53654e88c1802dd2be 1711 utils optional fcitx-hangul_0.1.1-1.dsc
 c8426b8dbb6f2a8e81b03a35ff611e85 24756 utils optional 
fcitx-hangul_0.1.1.orig.tar.xz
 8dcb8bc8846c8f924e4a99ee253e99e8 2387 utils optional 
fcitx-hangul_0.1.1-1.debian.tar.gz
 74cfe935d8076268ecbd239a68695f10 24174 utils optional 
fcitx-hangul_0.1.1-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBCgAGBQJPtg9uAAoJEIAhAkTu07wN82YH/A/waC9Z0kxkNw5TO3bMuuBD
GHIWDs4vDh9gfat8617KjZwgLy0hXPGwfUiq5K66gx63+CbGa1aAXXfWA1o6s2mI
xALHH/6G/FK1VFiWVLrjbZvkZLVcYJbqHEwa8o1oeIAwb32Cn0U/+oW/RwZxNNzh
W2O/VOSvT5HaKmZ7jW5stdq+ZK9g+Pwd4r5t5yRMu72dJRUMiMZRAQXp1nb+5Sv6
P7Or7ZQM+f+Hj3KK8DjPbE2V3hjU4PQTAvyFUP1VG/xWKBZ/Jlr3UE4tW15bLSOE
5G0kxh4fg45OEI9v4BhrHa+c4gn+gipjziHDY0TIPPpATvpes4BOV1lEYoKDwmk=
=uFQz
-END PGP SIGNATURE-


Accepted:
fcitx-hangul_0.1.1-1.debian.tar.gz
  to main/f/fcitx-hangul/fcitx-hangul_0.1.1-1.debian.tar.gz
fcitx-hangul_0.1.1-1.dsc
  to main/f/fcitx-hangul/fcitx-hangul_0.1.1-1.dsc
fcitx-hangul_0.1.1-1_amd64.deb
  to main/f/fcitx-hangul/fcitx-hangul_0.1.1-1_amd64.deb
fcitx-hangul_0.1.1.orig.tar.xz
  to main/f/fcitx-hangul/fcitx-hangul_0.1.1.orig.tar.xz


-- 
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/e1svkgq-0002uv...@franck.debian.org

Accepted pmw 1:4.24-1 (source all s390)

2012-05-18 Thread Wouter Verhelst

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 01:13:50 +0200
Source: pmw
Binary: pmw pmw-doc
Architecture: source s390 all
Version: 1:4.24-1
Distribution: unstable
Urgency: low
Maintainer: Wouter Verhelst wou...@debian.org
Changed-By: Wouter Verhelst wou...@debian.org
Description: 
 pmw- Philip's Music Writer
 pmw-doc- Philip's Music Writer - Documentation
Changes: 
 pmw (1:4.24-1) unstable; urgency=low
 .
   * New upstream release
   * Add epoch, because I forgot that 231  23. Argl.
Checksums-Sha1: 
 83f299b1c365da0ce38e20525b50db703b00765e 1834 pmw_4.24-1.dsc
 5b99acf4946c7c219dd2587dbcf534be540dee49 2004028 pmw_4.24.orig.tar.gz
 9edc56e2058a174b92d4d523fd58e6ae8f2ca2a1 4344 pmw_4.24-1.diff.gz
 7ec361b4c5591eeb0cf7f1d06a657077df1357f2 530686 pmw_4.24-1_s390.deb
 117da354b29988ff062c5c36da315922f5fee2f1 784748 pmw-doc_4.24-1_all.deb
Checksums-Sha256: 
 712cabaa6f95b4726c1ef4acc1925c911fd5f8a89c9605177b4658c4019bcb98 1834 
pmw_4.24-1.dsc
 83844b45fe92cd7335e138cfa786de0e4cf508f3c0a9a418f4764c72865a5f78 2004028 
pmw_4.24.orig.tar.gz
 f13c2f95810b8bab5151f2198faa4c07064fc6ce9e0a3305f8870949de13c8d1 4344 
pmw_4.24-1.diff.gz
 fe4799bc9035cf29fd192cbcb786335dd583d9a75750142d77cdda9c0503958e 530686 
pmw_4.24-1_s390.deb
 27f39eefbf2f95268cdb1d6d2e37763b7acaa6e7c6af1944c231030845be215c 784748 
pmw-doc_4.24-1_all.deb
Files: 
 9ff6fed79c64a629cc6d877cf453fe95 1834 tex extra pmw_4.24-1.dsc
 6fde7a36bd9292a93e51c4f0f58c20fd 2004028 tex extra pmw_4.24.orig.tar.gz
 2fd3d4e863a7f0172bda0925cf9b060f 4344 tex extra pmw_4.24-1.diff.gz
 01a6c6a773d5ef124ca42ce5352cc40b 530686 tex extra pmw_4.24-1_s390.deb
 da7043b3e725f7ea568569f73fb4c7ad 784748 doc extra pmw-doc_4.24-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJPthPHAAoJEMKUD5Ub3wqdDYQP/2AormEVPdZY6gPuAsiE83vr
G2ZIMy7VgUuaQIQV4lfYf/Ho+zkS/s5uFRaBvluRtLcTZ1WtUILAlkC6dFR/BhEP
CK/YZ2XCWPswh4NRr+ng4i9uWQA678Bj0P3r2ByvVEl7OzSC48ingPp9Yq8tVvIx
h+aU0g4F5avM3Kk+IxM7TUVWzHLu/KN9PSDZ/8tLTqdFDUoz+tmozg/gjmYHHNEQ
5sG+bUDb/XIA9GZI7jQh3451Addn/IICjuo3FpPFCSl2AeoFblIPdbEf+0EO1BAN
ZGSVUqF/okQZFXbZQSKXn090bCy3jfug0fyygGUFmB4TsbXybIDjmGA7RWJRXrFi
327e1C0D2OG2Sj/IjX0pPSLCn1u472jV8uBDzT/rGB803FGO4vwXmhryGafsxLo3
w1KJa06fUJ/li/t4KHWi6GsyNG1T2QxfJbMTtYFg8YSKF67HcDKvIJnEFs/SKmmg
/SpD0INlebXMuZ0a14nKwAAT9m33L9Q3ES8/p0/hQI3KDA5r53+Yotf0+Dvz3fB1
2nrnwH2cFc0o0qv1K+K0GJbvLo09Q56opbZ/bDUfPos16EC5TMS8aTZ/AdnC4sjI
SrIVTzXGxevvO5le1612n+Dc2zUI0+nlqgeKT6QhYqdeZGh3WExIRjfb16MeYy9k
d0Ks3mGm9qGZvyUXPOpV
=l8WZ
-END PGP SIGNATURE-


Accepted:
pmw-doc_4.24-1_all.deb
  to main/p/pmw/pmw-doc_4.24-1_all.deb
pmw_4.24-1.diff.gz
  to main/p/pmw/pmw_4.24-1.diff.gz
pmw_4.24-1.dsc
  to main/p/pmw/pmw_4.24-1.dsc
pmw_4.24-1_s390.deb
  to main/p/pmw/pmw_4.24-1_s390.deb
pmw_4.24.orig.tar.gz
  to main/p/pmw/pmw_4.24.orig.tar.gz


-- 
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/e1svklk-00042i...@franck.debian.org

Accepted lsyncd 2.0.7-2 (source amd64)

2012-05-18 Thread Jan Dittberner

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 May 2012 12:23:25 +0200
Source: lsyncd
Binary: lsyncd
Architecture: source amd64
Version: 2.0.7-2
Distribution: unstable
Urgency: low
Maintainer: Jan Dittberner ja...@debian.org
Changed-By: Jan Dittberner ja...@debian.org
Description: 
 lsyncd - daemon to synchronize local directories using rsync
Closes: 673387
Changes: 
 lsyncd (2.0.7-2) unstable; urgency=low
 .
   * fix lsyncd init script stores the wrong PID in /var/run/lsyncd.pid so
 cannot stop it by adding -pidfile option to debian/lsyncd.init's
 DAEMON_ARGS (Closes: #673387)
   * debian/rules: fix FTBFS twice in a row
 - override_dh_clean instead of clean
 - remove generated configure
   * enable hardening build flags
 - add dpkg-dev (= 1.16.1~) to Build-Depends
 - add DPKG_EXPORT_BUILDFLAGS=1 and include
   /usr/share/dpkg/buildflags.mk in debian/rules
Checksums-Sha1: 
 e00b5b53d238a5ae4c8089d3499d8380a8fb5379 1951 lsyncd_2.0.7-2.dsc
 355ab66e5eb1e1d910e5ed50ae9b1ee52f4096b5 4887 lsyncd_2.0.7-2.debian.tar.gz
 b74d9f1e37b2dee9469fe8ed57a816396acd62d7 68050 lsyncd_2.0.7-2_amd64.deb
Checksums-Sha256: 
 c29af700718bd819a615e97b9c5814f6714107763ee119e85db0334c79a08c18 1951 
lsyncd_2.0.7-2.dsc
 fb71617be94e6f56d64ace05d82fe991ed712ca68f206029e29700336a965606 4887 
lsyncd_2.0.7-2.debian.tar.gz
 c2afc18271b801eb1162433462a57dd5db84696454e58cb7d93a6ca5b3827f31 68050 
lsyncd_2.0.7-2_amd64.deb
Files: 
 7a555a7fd52c93da540cc57174c1648c 1951 admin optional lsyncd_2.0.7-2.dsc
 4497c07e8921034d0d9dbcfd1c7c1f46 4887 admin optional 
lsyncd_2.0.7-2.debian.tar.gz
 ad4be8fa6ec6c6c9c87c868b4f2507e5 68050 admin optional lsyncd_2.0.7-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJPtiOrAAoJEKc+AFVVj7jdkWEP/RV8s6CoqpAwRaEEONanfpQ4
nApzAitovwGajVpf+ryKXyEnh2wsgBr/FgjI4oFCs7OXhKGQglp8x/IrPiQ10d9u
ijhqGfg/fQLnXah/pgLS7lxLtygx5Ml4sqRdldihJNndITZ1IokZZ7k825AbvP+S
TqgdCfg+td6jSRYEkJxPt3zi9i02wJTFWz+aBUvgYHuvEdKTuVIofQPMDKgiKWAo
mhwA77BYeMlftrlHMkug4xbX8Vb5KY11/WenAizae8ScVYjFUGAzJP2GW+CXk72s
Hp2gfu5BwmJsRxUkvtB+mQJbw0eibeDMPdZIiXwaIJwF7HCIQh6jhg1sHn2Y5KNF
hyqhvrKz40GMPRB80EeNMyd7qzKR+AMokfnMozu10F0I61dE5WgGHAYH9oPoZjcm
Kc3quZPYyYQ+9b32+ayhx/cW9Dtfa6B+3CPIbDGyCya9fZnM0Tsb+uvAWYA/JvnK
TF5My734CN+Q7YZBhY9YEW4wek971biu9rg0mpOO+vON+ABjuRlkKm/CUl/y6JKS
aVNE0cIcVsu0rIRGS4T56BVDETetE+ldpYMqIJiB+/ge2EYXgaHeUD/6LCLJm3qc
NusVMEEOXa8ZcOM1MYeAwtVxwS1uTJfe35hqPWnozvqncCSstFxND3vnq/W3fAoJ
eaCWbc6G/b2nRSbgmvJS
=0kHf
-END PGP SIGNATURE-


Accepted:
lsyncd_2.0.7-2.debian.tar.gz
  to main/l/lsyncd/lsyncd_2.0.7-2.debian.tar.gz
lsyncd_2.0.7-2.dsc
  to main/l/lsyncd/lsyncd_2.0.7-2.dsc
lsyncd_2.0.7-2_amd64.deb
  to main/l/lsyncd/lsyncd_2.0.7-2_amd64.deb


-- 
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/e1svkud-0006ix...@franck.debian.org

Accepted qjackctl 0.3.8-2 (source amd64)

2012-05-18 Thread Alessio Treglia

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 May 2012 12:15:21 +0200
Source: qjackctl
Binary: qjackctl
Architecture: source amd64
Version: 0.3.8-2
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers 
pkg-multimedia-maintain...@lists.alioth.debian.org
Changed-By: Alessio Treglia ales...@debian.org
Description: 
 qjackctl   - User interface for controlling the JACK sound server
Closes: 673381
Changes: 
 qjackctl (0.3.8-2) unstable; urgency=low
 .
   * Add patch to fix FTBFS on Hurd. (Closes: #673381)
   * Bump Standards.
Checksums-Sha1: 
 a1e33eddc0ea47a9d373c2fcaf4dbc07d5998102 2135 qjackctl_0.3.8-2.dsc
 e851cd2b85c221ef2292f837c1f3cf782c1f3889 8407 qjackctl_0.3.8-2.debian.tar.gz
 dc06aea23c33622073b3ff21d8e69c630b8661dc 610186 qjackctl_0.3.8-2_amd64.deb
Checksums-Sha256: 
 c9c22e459a87a078dd0bc4ba0bc2cc5122f84d9959a10250d61ef21388987aa2 2135 
qjackctl_0.3.8-2.dsc
 60921f18a0254d5b248f25cd19a32201550a22f66bee74a8c902d808b5e3413e 8407 
qjackctl_0.3.8-2.debian.tar.gz
 43f90b584d915445517b8f79bd445373c642b3acedd0123586d2d19444fe7c10 610186 
qjackctl_0.3.8-2_amd64.deb
Files: 
 d668e9c1ec7c0bfa004a11ab82e154c6 2135 sound optional qjackctl_0.3.8-2.dsc
 a55675e9681d9399d3ec93eb83f80561 8407 sound optional 
qjackctl_0.3.8-2.debian.tar.gz
 41241fa5a32930b5c5c49f0bf179e560 610186 sound optional 
qjackctl_0.3.8-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCgAGBQJPtiJMAAoJEOikiuUxHXZaZ2kP/AkVJ0UyRVm9guA50kRse+bb
uXfVBZh4nhnQfDwRfAY5lwgx1I4ToNmyjcwvUYHJMqoadCyYPxRwBg+/t+StGZHv
WFkNmhad/KI2cOengNM75lZJJTJKa19DrPwxub+kCKh9cXHZ0nlFMNefI1BJGSMT
eZtbpDrAktosobFeCwWSGt3uIqniplXY8eEfqsr25toSo3oHrZQ99b1GZaEt7vLy
7DY6pDed+fjcg63GicK3EyA+42WLdj/HC+JYNemRV1wp9PdUETuXY4l04LUc8VTd
abpW5+UPblHEQ2zTWpnOpHCmZJLr3LnDsCA67Kr/WcSUrpn3KqgV6UD0hFE3CBPV
FPH25k/rAmWlLOU1B1Gibq35WPGw5GXwncYZYPvkkt+cerdQbkKwpfAZDE9/yxZm
LJI1MQlKv0ImsGvp9QoNq2xYJH9jaiflpFpb7w+9scVrcyxetyRDrgWnQqNZbdk/
buq+1g1DnlRCbO4ThMdA9486D/UV5T/uLex4aKPUV/GqoGNWnrmwQ2+u9tu8vhsF
XRTNURJCl140E5hkgY3TU71K7OWa0WoWSlnmQL8CfFY07SFGgxgT1+D0YEpVHDbx
IMO+hgqUuC6DMudEyZrLbhI3tbiPxxfD6yea5EWuKkhZaoYSSM5piBJcfPRFawtu
jm2bd6/eX/O/xuZ3Cpp+
=ZTqF
-END PGP SIGNATURE-


Accepted:
qjackctl_0.3.8-2.debian.tar.gz
  to main/q/qjackctl/qjackctl_0.3.8-2.debian.tar.gz
qjackctl_0.3.8-2.dsc
  to main/q/qjackctl/qjackctl_0.3.8-2.dsc
qjackctl_0.3.8-2_amd64.deb
  to main/q/qjackctl/qjackctl_0.3.8-2_amd64.deb


-- 
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/e1svkwk-0006el...@franck.debian.org

Accepted xserver-xorg-video-ati 1:6.14.4-3 (source amd64)

2012-05-18 Thread Cyril Brulebois

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 11:39:03 +0200
Source: xserver-xorg-video-ati
Binary: xserver-xorg-video-ati xserver-xorg-video-ati-dbg 
xserver-xorg-video-radeon xserver-xorg-video-radeon-dbg
Architecture: source amd64
Version: 1:6.14.4-3
Distribution: unstable
Urgency: low
Maintainer: Debian X Strike Force debia...@lists.debian.org
Changed-By: Cyril Brulebois k...@debian.org
Description: 
 xserver-xorg-video-ati - X.Org X server -- AMD/ATI display driver wrapper
 xserver-xorg-video-ati-dbg - X.Org X server -- AMD/ATI display driver wrapper 
(debugging symbo
 xserver-xorg-video-radeon - X.Org X server -- AMD/ATI Radeon display driver
 xserver-xorg-video-radeon-dbg - X.Org X server -- AMD/ATI Radeon display 
driver (debugging symbol
Changes: 
 xserver-xorg-video-ati (1:6.14.4-3) unstable; urgency=low
 .
   * Fix uninstallability issues on ia64 by dropping mach64 and r128 from
 dependencies on this architecture, since those were removed (the ia64
 domain I/O support code is gone in xserver 1.12).
Checksums-Sha1: 
 6c7e0d5fc06892065d15d56bdfce820cc4143cb7 1971 
xserver-xorg-video-ati_6.14.4-3.dsc
 38fbed7d2d0379f4b181d4f3e455f3d20dc6cb27 20772 
xserver-xorg-video-ati_6.14.4-3.diff.gz
 9a94eec07b9a98697d3c62011ba8a8e06da8157c 274746 
xserver-xorg-video-ati_6.14.4-3_amd64.deb
 c9d1e1d163d121df460cf60609b65aa673d61567 278814 
xserver-xorg-video-ati-dbg_6.14.4-3_amd64.deb
 a18572da0b7254ed42ddd2d540382781194c470c 724110 
xserver-xorg-video-radeon_6.14.4-3_amd64.deb
 d479f6649d549e75e76b3ebeccf77b3d9e828bdb 2307254 
xserver-xorg-video-radeon-dbg_6.14.4-3_amd64.deb
Checksums-Sha256: 
 976e498830ad2efb72b4fca89ba64460bab637b12a5eae0d4896e1f801e7ead7 1971 
xserver-xorg-video-ati_6.14.4-3.dsc
 f00a35dc8a230e3376121a53a23114a7981be66754c4daf505dad2b650be2406 20772 
xserver-xorg-video-ati_6.14.4-3.diff.gz
 da27572953b529b4d596e26388c80f8121969b41fb5fa0f3dc282e313a21adad 274746 
xserver-xorg-video-ati_6.14.4-3_amd64.deb
 85df2be21c6734f76b56df8762d43bd5e1df137343d2ffc81159ef45fd22cf18 278814 
xserver-xorg-video-ati-dbg_6.14.4-3_amd64.deb
 3005916bc9ed90c0eb1dfbf051647edb41f032650d20f2c580c966ac102a16bd 724110 
xserver-xorg-video-radeon_6.14.4-3_amd64.deb
 796946422a175c28df40567bb5459870dbfa215d8a5554b3926b4b0472bb3759 2307254 
xserver-xorg-video-radeon-dbg_6.14.4-3_amd64.deb
Files: 
 2c6a311fdf5fbd533b89eb508cf77d7f 1971 x11 optional 
xserver-xorg-video-ati_6.14.4-3.dsc
 c686041409110a06129885b847e5055b 20772 x11 optional 
xserver-xorg-video-ati_6.14.4-3.diff.gz
 acbc58fe3f8812efaa3590a21609c79f 274746 x11 optional 
xserver-xorg-video-ati_6.14.4-3_amd64.deb
 4aa855822c5734c40ab484c670479fc1 278814 debug extra 
xserver-xorg-video-ati-dbg_6.14.4-3_amd64.deb
 29b03e50567535757dba34b41df35801 724110 x11 optional 
xserver-xorg-video-radeon_6.14.4-3_amd64.deb
 16362a67c62a71087bd19f4084c65653 2307254 debug extra 
xserver-xorg-video-radeon-dbg_6.14.4-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+2IgoACgkQeGfVPHR5Nd1DtgCfUKTTpLHWqOnk6hdVWTpWMdTd
4KcAoNHtoSw0x5wnczX1M30fdBqUQycz
=xyCI
-END PGP SIGNATURE-


Accepted:
xserver-xorg-video-ati-dbg_6.14.4-3_amd64.deb
  to main/x/xserver-xorg-video-ati/xserver-xorg-video-ati-dbg_6.14.4-3_amd64.deb
xserver-xorg-video-ati_6.14.4-3.diff.gz
  to main/x/xserver-xorg-video-ati/xserver-xorg-video-ati_6.14.4-3.diff.gz
xserver-xorg-video-ati_6.14.4-3.dsc
  to main/x/xserver-xorg-video-ati/xserver-xorg-video-ati_6.14.4-3.dsc
xserver-xorg-video-ati_6.14.4-3_amd64.deb
  to main/x/xserver-xorg-video-ati/xserver-xorg-video-ati_6.14.4-3_amd64.deb
xserver-xorg-video-radeon-dbg_6.14.4-3_amd64.deb
  to 
main/x/xserver-xorg-video-ati/xserver-xorg-video-radeon-dbg_6.14.4-3_amd64.deb
xserver-xorg-video-radeon_6.14.4-3_amd64.deb
  to main/x/xserver-xorg-video-ati/xserver-xorg-video-radeon_6.14.4-3_amd64.deb


-- 
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/e1svkxn-0006uu...@franck.debian.org

Accepted gdb-doc 7.4.1-1 (source all)

2012-05-18 Thread Hector Oron

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 May 2012 11:47:25 +0200
Source: gdb-doc
Binary: gdb-doc
Architecture: source all
Version: 7.4.1-1
Distribution: unstable
Urgency: low
Maintainer: Hector Oron zu...@debian.org
Changed-By: Hector Oron zu...@debian.org
Description: 
 gdb-doc- The GNU Debugger Documentation
Changes: 
 gdb-doc (7.4.1-1) unstable; urgency=low
 .
   * New upstream release.
Checksums-Sha1: 
 82926889cecff709f40b0d6565897e486be8a346 1780 gdb-doc_7.4.1-1.dsc
 a5873c0821da951dfd6737b22eaf276813279f06 1971761 gdb-doc_7.4.1.orig.tar.gz
 2631558a5b9c06a9d5ce082bb643dec9b68f8b53 12274 gdb-doc_7.4.1-1.debian.tar.gz
 1f9053704d9480b1f82db025821372da366a061f 5049022 gdb-doc_7.4.1-1_all.deb
Checksums-Sha256: 
 539d8709fa0288cfe55f89d3bec6199a3f10096951f6f8807b6b63b8f1c2d18a 1780 
gdb-doc_7.4.1-1.dsc
 315c22e4d610b434d04da2ca65725baefeb00fb8dc65ac3d362844bf0eface31 1971761 
gdb-doc_7.4.1.orig.tar.gz
 c98d395e0423d8aab6ab00b37502e1609cc8d5f3690e0e54213e86754b93c868 12274 
gdb-doc_7.4.1-1.debian.tar.gz
 dc4e23cfd5536a0c86d768ff03e6350cae7282552af8d4194b789ca019dfae2c 5049022 
gdb-doc_7.4.1-1_all.deb
Files: 
 d0c717c27dd15ad3f7df18c6f8f9af3a 1780 non-free/devel optional 
gdb-doc_7.4.1-1.dsc
 a5965056c10a06c12d41f0f1840c1836 1971761 non-free/devel optional 
gdb-doc_7.4.1.orig.tar.gz
 fecfe2205773816a3409da88ecc863e2 12274 non-free/devel optional 
gdb-doc_7.4.1-1.debian.tar.gz
 fb56b75673b4fce41b72ed8b285e0f63 5049022 non-free/doc optional 
gdb-doc_7.4.1-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCgAGBQJPtiYaAAoJEK8ig6p24qx7ZUEP/iQeFbvjA8RwGbqIE43D7N1p
hrO2rI9awG6xp8lmsjQsQ4G+iS476vXj15l7PBDW8Ad7794cr+QMHOWmA9eSiEJH
gT/55Ai8MiT13LQzFCz8IhTyMPao3324Zmr9DSbAg8VbLNdr7Jx+EjU6bKwWb5Au
6SCWa/k5cugn+O3Gt2pYr3WakzFVsHVSIGjonkFk7a+vJQfX9IinXPZwb+U8vZzZ
qvXQ+zjMQXYBHO1NlkH5qrF0HkF2WBGXLFm7gk3YwUrl/wq0YFRN5NRl4dgW9LvP
t5Wgqqkxz2l4A5rMxhBhI6d/oq9Pa1otkmNKSyWr4qa7EQSCgrfr9Y+t9rC4+Fow
p0GZjHjy6vChT2osxzEI4sVO2HHv8fEJ5qspkqyHjkzlzygbHFdzz6fPNXilE3gv
JEzxOvOCX03kJ3+NpOXFpf3Q4w7JKAlMnjMiZC08+r9PntDNhmmtVlzx1uMgWphm
gCNNu50yNrFgf3LcZssCOfUqLo9EpnVS5Trw3JXfskrjJnVQM6JTy19bhPimT+Xv
XjNd7JruPenLMRY+Y9gAfKcP1e58kLlc5Bius5gY2CKeYZJiUfX2yClLTdMkylj9
M38mmkDDNLaLi3A8JC9CHrTbSn+O52PEnoxgBbuIkXovD2lgVX8BxyWhZTkB6NDR
7CCtd+iNFuOxbGNFBcJW
=Tph4
-END PGP SIGNATURE-


Accepted:
gdb-doc_7.4.1-1.debian.tar.gz
  to non-free/g/gdb-doc/gdb-doc_7.4.1-1.debian.tar.gz
gdb-doc_7.4.1-1.dsc
  to non-free/g/gdb-doc/gdb-doc_7.4.1-1.dsc
gdb-doc_7.4.1-1_all.deb
  to non-free/g/gdb-doc/gdb-doc_7.4.1-1_all.deb
gdb-doc_7.4.1.orig.tar.gz
  to non-free/g/gdb-doc/gdb-doc_7.4.1.orig.tar.gz


-- 
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/e1svkiw-0008jz...@franck.debian.org

Accepted dmidecode 2.11-8 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 12:36:27 +0200
Source: dmidecode
Binary: dmidecode dmidecode-udeb
Architecture: source i386
Version: 2.11-8
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
Changed-By: Daniel Baumann daniel.baum...@progress-technologies.net
Description: 
 dmidecode  - SMBIOS/DMI table decoder
 dmidecode-udeb - SMBIOS/DMI table decoder (udeb) (udeb)
Closes: 655891
Changes: 
 dmidecode (2.11-8) unstable; urgency=low
 .
   * Using package type instead of custom field for udeb package.
   * Adding patch to escape hypens in manpage.
   * Also passing cppflags to make (Closes: #655891).
Checksums-Sha1: 
 dce0c6ae72bf2bcbc6aa32dabfd4d783ff6e6bee 1169 dmidecode_2.11-8.dsc
 32f22f3f06503fa985078d0f78da63c7267b4de6 11188 dmidecode_2.11-8.debian.tar.gz
 45e80b163aac2ad9d1ff5fa29e98adaad808cf86 71064 dmidecode_2.11-8_i386.deb
 724ffb46713944f7edbe8612c2f2ba16b48d747c 26908 dmidecode-udeb_2.11-8_i386.udeb
Checksums-Sha256: 
 7e3049671333092729c91b8f4942185dfb5b517ce48a7b41543422269bc025f8 1169 
dmidecode_2.11-8.dsc
 b354cfb3ee270906ce97ff752834f0dce0ba0b7fe68f9404f6172c68557cec62 11188 
dmidecode_2.11-8.debian.tar.gz
 781b2b4d03d7516604bd9117bebafd7e713d49ad4cdad1992f3d98003d5500d1 71064 
dmidecode_2.11-8_i386.deb
 00f303602d90d47966fd3e13c2b1520133d42870e689e0c84d69842a77bc2660 26908 
dmidecode-udeb_2.11-8_i386.udeb
Files: 
 e24c9dc1c8c0eaa9d529af44a2809492 1169 utils optional dmidecode_2.11-8.dsc
 1259c3643b5fe794d13f5428fa5a6753 11188 utils optional 
dmidecode_2.11-8.debian.tar.gz
 9d63277e65256a24dba160e913cb6654 71064 utils important 
dmidecode_2.11-8_i386.deb
 acad4dc3ef34227eb02a975582efd4c9 26908 debian-installer optional 
dmidecode-udeb_2.11-8_i386.udeb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+2KI4ACgkQ+C5cwEsrK56DqgCgzNrwyoXRemKK7hkWUwRGqXZT
I3MAoJ+5/+YUaRf1Iux+49wrID6XaWWn
=+Nnk
-END PGP SIGNATURE-


Accepted:
dmidecode-udeb_2.11-8_i386.udeb
  to main/d/dmidecode/dmidecode-udeb_2.11-8_i386.udeb
dmidecode_2.11-8.debian.tar.gz
  to main/d/dmidecode/dmidecode_2.11-8.debian.tar.gz
dmidecode_2.11-8.dsc
  to main/d/dmidecode/dmidecode_2.11-8.dsc
dmidecode_2.11-8_i386.deb
  to main/d/dmidecode/dmidecode_2.11-8_i386.deb


-- 
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/e1svkwm-0001wi...@franck.debian.org

Accepted pygpiv 2.0.0-4.1 (source amd64)

2012-05-18 Thread Jari Aalto

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 12:06:45 +0300
Source: pygpiv
Binary: python-gpiv
Architecture: source amd64
Version: 2.0.0-4.1
Distribution: unstable
Urgency: low
Maintainer: Gerber van der Graaf gerber_gr...@users.sourceforge.net
Changed-By: Jari Aalto jari.aa...@cante.net
Description: 
 python-gpiv - wrapper of libgpiv
Closes: 667862
Changes: 
 pygpiv (2.0.0-4.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Upgrade to packaging format 3.0 quilt.
   * Convert dpatch format *.diff files into DEP3, README.source not needed.
   * Update to Standards-Version to 3.9.3.1 and debhelper to 9.
   * Use hardened build flags and dh_prep in rules file (Closes: #667862).
 http://wiki.debian.org/ReleaseGoals/SecurityHardeningBuildFlags
Checksums-Sha1: 
 189b009f2cb08af4418e4cb8b07b64fae8659028 1262 pygpiv_2.0.0-4.1.dsc
 e528952ca7503a83c25fa0d3ffe210ed0c3ecc03 3727 pygpiv_2.0.0-4.1.debian.tar.gz
 1e9c0f22964c0b1f977a152408ee5d8a28e122f0 168822 python-gpiv_2.0.0-4.1_amd64.deb
Checksums-Sha256: 
 585ecce3433e82b0147e8b7e27ac2b5bd621f0975a9c855a0358484a71592eba 1262 
pygpiv_2.0.0-4.1.dsc
 75c0e0599ec7f27c8cdc40b688673bafbbce58d5429b26aa5661f8429de7a27f 3727 
pygpiv_2.0.0-4.1.debian.tar.gz
 67dd1a8943446e5890306d4f564f7de3e80fdc88a958f3276a2033f909550c4b 168822 
python-gpiv_2.0.0-4.1_amd64.deb
Files: 
 58f7f078f1a52896e27c7c2006ba8324 1262 python extra pygpiv_2.0.0-4.1.dsc
 fbb967aff66279677fc4bece68549bc3 3727 python extra 
pygpiv_2.0.0-4.1.debian.tar.gz
 f1408cf1d6151f0a596c9a3bc82d3ee1 168822 python extra 
python-gpiv_2.0.0-4.1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk+2KVEACgkQLARVQsm1XaxFCACbByAytPaDvtAHSKwYE0ocvnJn
EqoAn3ASqUk7YW/rggc5EmkGBXEcTUno
=pmEL
-END PGP SIGNATURE-


Accepted:
pygpiv_2.0.0-4.1.debian.tar.gz
  to main/p/pygpiv/pygpiv_2.0.0-4.1.debian.tar.gz
pygpiv_2.0.0-4.1.dsc
  to main/p/pygpiv/pygpiv_2.0.0-4.1.dsc
python-gpiv_2.0.0-4.1_amd64.deb
  to main/p/pygpiv/python-gpiv_2.0.0-4.1_amd64.deb


-- 
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/e1svl43-0001sc...@franck.debian.org

Accepted recoll 1.17.2-1 (source amd64)

2012-05-18 Thread Kartik Mistry

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 10:59:21 +0530
Source: recoll
Binary: recoll python-recoll
Architecture: source amd64
Version: 1.17.2-1
Distribution: unstable
Urgency: low
Maintainer: Kartik Mistry kar...@debian.org
Changed-By: Kartik Mistry kar...@debian.org
Description: 
 python-recoll - Python extension for recoll
 recoll - Personal full text search package with a Qt GUI
Changes: 
 recoll (1.17.2-1) unstable; urgency=low
 .
   * New upstream release:
 + Dropped patches: fix-kFreeBSD-ftbfs.patch, recoll_ionice_getpid.patch.
   These are merged with upstream.
 + Refreshed patch: fix-python-install.patch.
   * debian/rules, debian/control:
 + Added hardening support.
   * debian/copyright:
 + Fixed duplicate Copyright sections.
Checksums-Sha1: 
 cc71161d53e5a9a0c852887d9bd9f106527b97c7 1249 recoll_1.17.2-1.dsc
 676be89d376a948798611417b928b31485746b1b 1757337 recoll_1.17.2.orig.tar.gz
 172764c39b58ae668fda0aa8f57a1ef0f83e8c89 9860 recoll_1.17.2-1.debian.tar.gz
 e7ea2d1c59177d87578582553dd92296aeede554 1780860 recoll_1.17.2-1_amd64.deb
 22b19dc50d9fd2a678021ad4869faefc4d7f775b 343644 
python-recoll_1.17.2-1_amd64.deb
Checksums-Sha256: 
 c805c6e20192e4ef2dc82915bbd43cca3e8e5ac93d7fecf7ad17f6dfbc5d5aef 1249 
recoll_1.17.2-1.dsc
 8fa0419ca78bdeca4a18e36d252a9e8254112653499c47b407b178c9f2e58a2a 1757337 
recoll_1.17.2.orig.tar.gz
 8b55d4729f23dedd636ba1f129946bea627320623f9f61f5f4403c7fac7043f5 9860 
recoll_1.17.2-1.debian.tar.gz
 7d9e1d790fdba7fe3bbe28156417982c006b0c3148ab8bea437c6102d2582be1 1780860 
recoll_1.17.2-1_amd64.deb
 b7e04a511fe7dfde523f6e48fb69fd7cde435f4e25e9f5c9d4cebe9b72b6df4d 343644 
python-recoll_1.17.2-1_amd64.deb
Files: 
 8c3583be2c3f8fd24a641c7091b9c4dd 1249 x11 optional recoll_1.17.2-1.dsc
 4e90ec89643759c44be54683426ae78f 1757337 x11 optional recoll_1.17.2.orig.tar.gz
 fbdc331748ff7be5ea397ba85fd91d6d 9860 x11 optional 
recoll_1.17.2-1.debian.tar.gz
 d3edd345f720c3dcbf381f782701c126 1780860 x11 optional recoll_1.17.2-1_amd64.deb
 fb8850a9574e6b359fa58f2f5e248609 343644 python optional 
python-recoll_1.17.2-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAk+2J18ACgkQoRg/jtECjI29bwCgquHqLHerpU1wykWg2WaLnxWt
+lUAoIijXsnCjWSegPy/HsYB5BKJbhLy
=rj2o
-END PGP SIGNATURE-


Accepted:
python-recoll_1.17.2-1_amd64.deb
  to main/r/recoll/python-recoll_1.17.2-1_amd64.deb
recoll_1.17.2-1.debian.tar.gz
  to main/r/recoll/recoll_1.17.2-1.debian.tar.gz
recoll_1.17.2-1.dsc
  to main/r/recoll/recoll_1.17.2-1.dsc
recoll_1.17.2-1_amd64.deb
  to main/r/recoll/recoll_1.17.2-1_amd64.deb
recoll_1.17.2.orig.tar.gz
  to main/r/recoll/recoll_1.17.2.orig.tar.gz


-- 
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/e1svl5s-00022r...@franck.debian.org

Accepted ruby-gir-ffi 0.3.1-1 (source all)

2012-05-18 Thread TANIGUCHI Takaki

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 May 2012 19:44:00 +0900
Source: ruby-gir-ffi
Binary: ruby-gir-ffi
Architecture: source all
Version: 0.3.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Ruby Extras Maintainers 
pkg-ruby-extras-maintain...@lists.alioth.debian.org
Changed-By: TANIGUCHI Takaki tak...@debian.org
Description: 
 ruby-gir-ffi - FFI-based GObject binding using the GObject Introspection 
Reposit
Changes: 
 ruby-gir-ffi (0.3.1-1) unstable; urgency=low
 .
   * Imported Upstream version 0.3.1
Checksums-Sha1: 
 c0f162f9b0a7161947078863fa07b96ea5fe7c9c 2321 ruby-gir-ffi_0.3.1-1.dsc
 283e2028e1ff7e6c506fd237a90bd4543cc52cd4 84930 ruby-gir-ffi_0.3.1.orig.tar.gz
 5e847e98c8a439496ca9b78ad1a206d47bafb906 2330 
ruby-gir-ffi_0.3.1-1.debian.tar.gz
 f4f9f28f3eb9cb60e3c7e340412f2576420b3ac9 40550 ruby-gir-ffi_0.3.1-1_all.deb
Checksums-Sha256: 
 7a19e5aa23f5f7e8933326d9018b5815da252b33f9d6b88a8f3847b03f92551b 2321 
ruby-gir-ffi_0.3.1-1.dsc
 c55c01f900a3882c1e1ff055c284613473e7cf8943c8549fb3d961c2a35aa16d 84930 
ruby-gir-ffi_0.3.1.orig.tar.gz
 380bb562818a5e4ab48e3c813ca34410229c89f275a44bc6073abc8d7cef39c0 2330 
ruby-gir-ffi_0.3.1-1.debian.tar.gz
 d590a0e8a5bff9cabd3378e074d518cf92a26e5227aaee453fa65def7346362d 40550 
ruby-gir-ffi_0.3.1-1_all.deb
Files: 
 beeab5fe8b2a848897e1b3dcb5e7569b 2321 ruby optional ruby-gir-ffi_0.3.1-1.dsc
 c7447684929ec85b3f6358ae8c36833b 84930 ruby optional 
ruby-gir-ffi_0.3.1.orig.tar.gz
 d334fb3b665c555cef336935e124efc8 2330 ruby optional 
ruby-gir-ffi_0.3.1-1.debian.tar.gz
 74451a44785045a62550f46059cbf8a3 40550 ruby optional 
ruby-gir-ffi_0.3.1-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJPtighAAoJEMwUn2wopeJX8ZsQAK/v4YKwPwL3fVraGWyjQ3vQ
q6HRuSHSmDT5KoSnN/2vplfH+XCIOMxUw/5Uvd22tqRh13ImeVs+dEsMx5awJNN2
CzKDfuG8EBedZkLu3p6/jmve+IklcjxfmQx6kPo/pV46/N0iUB57YiPqLb+8tCyb
QSfbLHH0H6ZesFF5oH7zZdfWi1Z0K8bzTec/aKIF2FsgkERtFbxmPSlx+81h1dJc
K9mgtuuUdPznMWR7XoQ9EUOAkdcLWC4BE2es7fQW4KeulanZWofoQgyRCcSmqXAA
oCKyY7NXXbHRwuOc49hq9Slip+8rA8WgGTVQEbbEUWO/GJF9rfPOtL2X+jqVPekt
3FM8HXM7v/QR+gKYVIFp5/RAfS7lfcIRXG0Kfp3cngNuxmS7JIw2zxhQPqBZauNh
BKT10C5swNcotAx7d4hDksnwEVccKmWq0ExJ+rco9VuFOyORrBYBIqGhxtO5/7Uh
y5hfvW5NS5VZASY+2dcTGC53HXNSULUFzHbWuOlVehvlMDReoZ4DePi/30VW6Vxk
/171MGvUs9qAIHcFoZWBEqueAUzoMyAKE7E6qjt3RmIa3t+EGua27fcLF6eu5MNy
eI3I2+t8bwkkrNdec9Jn6j5qEiH7M7sMy7oqskVzVMcEiPQIDmBM5IoycFiA3I0z
QAbEF0l0QYqTbsQHSxb7
=vpcz
-END PGP SIGNATURE-


Accepted:
ruby-gir-ffi_0.3.1-1.debian.tar.gz
  to main/r/ruby-gir-ffi/ruby-gir-ffi_0.3.1-1.debian.tar.gz
ruby-gir-ffi_0.3.1-1.dsc
  to main/r/ruby-gir-ffi/ruby-gir-ffi_0.3.1-1.dsc
ruby-gir-ffi_0.3.1-1_all.deb
  to main/r/ruby-gir-ffi/ruby-gir-ffi_0.3.1-1_all.deb
ruby-gir-ffi_0.3.1.orig.tar.gz
  to main/r/ruby-gir-ffi/ruby-gir-ffi_0.3.1.orig.tar.gz


-- 
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/e1svl5k-00023z...@franck.debian.org

Accepted traceroute 1:2.0.18-2 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 12:53:18 +0200
Source: traceroute
Binary: traceroute
Architecture: source i386
Version: 1:2.0.18-2
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
Changed-By: Daniel Baumann daniel.baum...@progress-technologies.net
Description: 
 traceroute - Traces the route taken by packets over an IPv4/IPv6 network
Closes: 656014
Changes: 
 traceroute (1:2.0.18-2) unstable; urgency=low
 .
   * Using compression level 9 also for binary packages.
   * Updating package to standards version 3.9.3.
   * Updating package to debhelper version 9.
   * Adding patch to avoid overwriting build environment.
   * Adding patch from Moritz Muehlenhoff j...@debian.org to add missing
 format strings in order to build with hardening flags.
   * Enabling hardening build flags (Closes: #656014).
   * Updating copyright file to machine-readable format version 1.0.
Checksums-Sha1: 
 491354302d4f7b7688165485cf995a154c83b8cc 1112 traceroute_2.0.18-2.dsc
 7d34c4cdfd3e29baede68398b4753d1675bf5fea 8223 traceroute_2.0.18-2.debian.tar.gz
 8b6fb6915f6c859f69d9745dd5f23a329b67b038 61884 traceroute_2.0.18-2_i386.deb
Checksums-Sha256: 
 4e07cc2e129589f7bfcaeac649b7b00ed7a9e5a401c7bd43841b0a20caa03e97 1112 
traceroute_2.0.18-2.dsc
 900657aec7a58e85c5e79e7a46dc8cfc73196d0471e143d136313fd843dc0e93 8223 
traceroute_2.0.18-2.debian.tar.gz
 e838faf01ed5a5e0c1b5ac384ef01414124c7cb408a5ca2f34da711e056e94f4 61884 
traceroute_2.0.18-2_i386.deb
Files: 
 f53707c96526b741e4bb5d59bcfaa164 1112 net important traceroute_2.0.18-2.dsc
 472889d59f8f129f15d2652ba1107aad 8223 net important 
traceroute_2.0.18-2.debian.tar.gz
 cfbbec00fa251b7c4cbe31217fab469e 61884 net important 
traceroute_2.0.18-2_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+2K0UACgkQ+C5cwEsrK54s5wCgqN/xyHclva21xYL5xMiKXK5d
/+AAoIzoKv72sP2dMOJRpBPDOLrv+RgS
=wfOL
-END PGP SIGNATURE-


Accepted:
traceroute_2.0.18-2.debian.tar.gz
  to main/t/traceroute/traceroute_2.0.18-2.debian.tar.gz
traceroute_2.0.18-2.dsc
  to main/t/traceroute/traceroute_2.0.18-2.dsc
traceroute_2.0.18-2_i386.deb
  to main/t/traceroute/traceroute_2.0.18-2_i386.deb


-- 
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/e1svl72-00025k...@franck.debian.org

Accepted audacious 3.2.2-2 (source amd64)

2012-05-18 Thread Alessio Treglia

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 18 May 2012 13:11:45 +0200
Source: audacious
Binary: audacious audacious-dbg audacious-dev libaudclient2 libaudcore1
Architecture: source amd64
Version: 3.2.2-2
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers 
pkg-multimedia-maintain...@lists.alioth.debian.org
Changed-By: Alessio Treglia ales...@debian.org
Description: 
 audacious  - small and fast audio player which supports lots of formats
 audacious-dbg - audacious media player (debugging symbols)
 audacious-dev - audacious development files
 libaudclient2 - audacious dbus remote control library
 libaudcore1 - audacious core engine library
Changes: 
 audacious (3.2.2-2) unstable; urgency=low
 .
   * Team upload.
   * Upload to unstable.
Checksums-Sha1: 
 656374187b9ab850669934dad86a151395543b0c 2409 audacious_3.2.2-2.dsc
 4559274d06d55f4f0e114992369329fb927374eb 14838 audacious_3.2.2-2.debian.tar.gz
 c006cdfd569b39271c41fe8d93fd4c1b25856e91 415274 audacious_3.2.2-2_amd64.deb
 5ea5679d39f81f6b11f9aa50ef27a7b9ab324563 651350 audacious-dbg_3.2.2-2_amd64.deb
 b9b19d5d9b9e0875a3b5f7655e923806edb33f3f 48624 audacious-dev_3.2.2-2_amd64.deb
 d2b4626aee898db830764397474485a84b3d64de 26568 libaudclient2_3.2.2-2_amd64.deb
 124373a8cb870be9dcffe91ae0f90b85ed0ead9c 106952 libaudcore1_3.2.2-2_amd64.deb
Checksums-Sha256: 
 e5a1a8ce45fe42fcb13925d9eb3381c870d3814458768489eef206caf4992257 2409 
audacious_3.2.2-2.dsc
 93ee8e487d8821ed3cc3f9c494cea9b8a26fab2211960fae66e4b4d711815c09 14838 
audacious_3.2.2-2.debian.tar.gz
 3710029aa6ae6ede2ca5c9a8fa5318ca6110308edce5c22936f1532ea3e4337c 415274 
audacious_3.2.2-2_amd64.deb
 0a47da220f5d2ad3703d70d5731bfadc6dcdd6cbee1ba5ea2f2aa87e2bd81bbd 651350 
audacious-dbg_3.2.2-2_amd64.deb
 c845e8a64cb8f7e28f934da6a3f2baede73ac43781747cae808be3dc3009d703 48624 
audacious-dev_3.2.2-2_amd64.deb
 370d0d9ebef6fae1dc87df23956d16627d6d20c4a2a4fef57f9d99283a6f55a9 26568 
libaudclient2_3.2.2-2_amd64.deb
 f27acb7d32b34f43a858c187f63fd94c496dee888a71f50a99e4ad6067d8e54f 106952 
libaudcore1_3.2.2-2_amd64.deb
Files: 
 98495e7c156af02141a0e7cb33fd46b2 2409 sound optional audacious_3.2.2-2.dsc
 668add24cf7bd08eca08ef5bb5c42983 14838 sound optional 
audacious_3.2.2-2.debian.tar.gz
 560f748221893fa441e2d67c483cd5af 415274 sound optional 
audacious_3.2.2-2_amd64.deb
 dfba035a6baac57eba86556c2f4d1322 651350 debug extra 
audacious-dbg_3.2.2-2_amd64.deb
 afebf2e8fa5c08bcf4f9bacd78a19c3f 48624 libdevel optional 
audacious-dev_3.2.2-2_amd64.deb
 0ff8b61cab23612760e4dcd5054a3ba2 26568 sound optional 
libaudclient2_3.2.2-2_amd64.deb
 b3f225c10cd17649433dfadc38e2d9cc 106952 sound optional 
libaudcore1_3.2.2-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCgAGBQJPtjAzAAoJEOikiuUxHXZavW0QAKvdrgeNK5RyqaM3vmRM5jYT
068E4gxNpiDSnzaU02gknu+FRlshJ26t8pDf6sK9VI7UXha5p2O9+opVENrvTywh
0oH6uBU09Msyf0lKF0PP+i6j2la9UsdMOTylBY8Axax14HvjE3i8GMEsQ5ZjfZtc
f7Tjop9jk+gYM/NxueyX/htB9LvRlCOLZwQE0Xc345blZ5HntV3DVVeKM/16Y0n+
xrD9Ng2TvW4Y7GislrsI1YMp47KDYhCirBTzJwI+rODFPFo+WmbKxpDRc7yPxTP9
ul5YR5o2zzjwZFUy0ExKk9/TtxcRXM+6waEsZ6XINNhQ/jaSnTT0ESnVwWc/CfJm
YjKYxfMunXfr/9SUrkUo/EIaQo3ScrsY8J5ngT+Jx5L8xLmt98O6Xvi4bHGvL9MH
bjPBvfghTv6DEYHnrybkYXftPUmEPCOpVowE2dSi9HvnhQoX3/1yOZhBmIdaWbLf
/WflSiLLhE2RGlYZD+t1xnUCl7oEcCdIkh8boguKiJoxaTEWBczFVQOI57ls8aeZ
4z6u7T8jt3Js+SdTfGZnz33yk63hMImk8e5axpxDYIQ7GK3y7P/fRk09pmqQSVJC
w41d2abUim1EVZ2QNvzp7N3vd6aRVvFjX05OCV1zUSzwzcyI5jRHw2SBA19G7ggA
mtBin8bsUshGoU+0y2Do
=UnIB
-END PGP SIGNATURE-


Accepted:
audacious-dbg_3.2.2-2_amd64.deb
  to main/a/audacious/audacious-dbg_3.2.2-2_amd64.deb
audacious-dev_3.2.2-2_amd64.deb
  to main/a/audacious/audacious-dev_3.2.2-2_amd64.deb
audacious_3.2.2-2.debian.tar.gz
  to main/a/audacious/audacious_3.2.2-2.debian.tar.gz
audacious_3.2.2-2.dsc
  to main/a/audacious/audacious_3.2.2-2.dsc
audacious_3.2.2-2_amd64.deb
  to main/a/audacious/audacious_3.2.2-2_amd64.deb
libaudclient2_3.2.2-2_amd64.deb
  to main/a/audacious/libaudclient2_3.2.2-2_amd64.deb
libaudcore1_3.2.2-2_amd64.deb
  to main/a/audacious/libaudcore1_3.2.2-2_amd64.deb


-- 
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/e1svlpp-0004wm...@franck.debian.org

Accepted aufs-tools 1:3.0+20120411-1 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 13:17:14 +0200
Source: aufs-tools
Binary: aufs-tools aufs-tools-dbg
Architecture: source i386
Version: 1:3.0+20120411-1
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
Changed-By: Daniel Baumann daniel.baum...@progress-technologies.net
Description: 
 aufs-tools - Tools to manage aufs filesystems
 aufs-tools-dbg - Tools to manage aufs filesystems (debug)
Changes: 
 aufs-tools (1:3.0+20120411-1) unstable; urgency=low
 .
   * Updating package to standards version 3.9.3.
   * Updating package to debhelper version 9.
   * Updating copyright file to machine-readable format version 1.0.
   * Merging upstream version 3.0+20120411.
Checksums-Sha1: 
 53f84041e987c59413542f2ce43e6e70acf2fac4 1229 aufs-tools_3.0+20120411-1.dsc
 3e1615c75356203e14b911be36c04ddfb4402b97 90827 
aufs-tools_3.0+20120411.orig.tar.gz
 17a9571a9475af9661e21661980270cfb31a1366 3077 
aufs-tools_3.0+20120411-1.debian.tar.gz
 7fc16ab10e3e4f4e3fc5fc117db3696c3e4a056f 101070 
aufs-tools_3.0+20120411-1_i386.deb
 62ddb0b22e92cdbe97317cc7097f18a787fa091e 61530 
aufs-tools-dbg_3.0+20120411-1_i386.deb
Checksums-Sha256: 
 85cd6eda3b1c3215d7713e7af5c9f5455a37cd97ef65c13713f8c4ad73ba7ef0 1229 
aufs-tools_3.0+20120411-1.dsc
 69f60bb92f053ba74d1ec637befe14df7e5416b5cfd79cb35ebe74d2ba8e3778 90827 
aufs-tools_3.0+20120411.orig.tar.gz
 9e6b35e9dea83c94853c14c20a5e1150a352802d056576c1daa4b8620b7f592c 3077 
aufs-tools_3.0+20120411-1.debian.tar.gz
 6953f16dc06d534729e38be282d2427484002c4be3713faf2bedbd382859a85f 101070 
aufs-tools_3.0+20120411-1_i386.deb
 2006b498d3e43be5fbbd5f6ae2783f7ad1f8ff4d6b460cc36258756cf3e2ceba 61530 
aufs-tools-dbg_3.0+20120411-1_i386.deb
Files: 
 95ea1df26ed8ddbca78eba21af65d381 1229 kernel optional 
aufs-tools_3.0+20120411-1.dsc
 e7673131c9ad9b0e9fb952b945520d92 90827 kernel optional 
aufs-tools_3.0+20120411.orig.tar.gz
 3f75f1810eb8da17ac4a4c2bb57d08fd 3077 kernel optional 
aufs-tools_3.0+20120411-1.debian.tar.gz
 367c44c903a26b5dce1f7ba21c35eb68 101070 kernel optional 
aufs-tools_3.0+20120411-1_i386.deb
 9d4f9d446ff6a6fc441460519e85f0e6 61530 debug extra 
aufs-tools-dbg_3.0+20120411-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+2MHUACgkQ+C5cwEsrK57hdACeKqkmbWqtv6NCZHWzS4wC52zs
VtoAmwaTnbmbGE3q6xXh3FJE9bozj/wi
=PjVM
-END PGP SIGNATURE-


Accepted:
aufs-tools-dbg_3.0+20120411-1_i386.deb
  to main/a/aufs-tools/aufs-tools-dbg_3.0+20120411-1_i386.deb
aufs-tools_3.0+20120411-1.debian.tar.gz
  to main/a/aufs-tools/aufs-tools_3.0+20120411-1.debian.tar.gz
aufs-tools_3.0+20120411-1.dsc
  to main/a/aufs-tools/aufs-tools_3.0+20120411-1.dsc
aufs-tools_3.0+20120411-1_i386.deb
  to main/a/aufs-tools/aufs-tools_3.0+20120411-1_i386.deb
aufs-tools_3.0+20120411.orig.tar.gz
  to main/a/aufs-tools/aufs-tools_3.0+20120411.orig.tar.gz


-- 
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/e1svlq5-0004x1...@franck.debian.org

Accepted yash 2.30-2 (source amd64)

2012-05-18 Thread TANIGUCHI Takaki

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 May 2012 20:14:29 +0900
Source: yash
Binary: yash
Architecture: source amd64
Version: 2.30-2
Distribution: unstable
Urgency: low
Maintainer: TANIGUCHI Takaki tak...@debian.org
Changed-By: TANIGUCHI Takaki tak...@debian.org
Description: 
 yash   - yet another shell
Closes: 673246
Changes: 
 yash (2.30-2) unstable; urgency=low
 .
   * Add yash.1 (by Khalid El Fathi) (Closes: #673246)
Checksums-Sha1: 
 adb1ce318566b9d2929c6ef90a07639e1f5e3331 1825 yash_2.30-2.dsc
 6a86fca0eca0f499cc02f80260d7fc799e964389 4487 yash_2.30-2.debian.tar.gz
 a927e47cb1f4028924713bdc4c03f4e9055d0716 383538 yash_2.30-2_amd64.deb
Checksums-Sha256: 
 66bab8475c3934d59aa9f666cc547420952f47fe08057d62e21f60ca91a04f2b 1825 
yash_2.30-2.dsc
 f00df2aae92b594515094daca79b1a1588e4ebfa5ca128e735c548a58de52f67 4487 
yash_2.30-2.debian.tar.gz
 501092a0ee75c78757ab5ee5cce2c384186eddede31403f5757294ddd53bc755 383538 
yash_2.30-2_amd64.deb
Files: 
 d058eb2805df7a7bdc9b7452a3f08474 1825 shells extra yash_2.30-2.dsc
 0f9ecd17d711fba09b140b1280fc027a 4487 shells extra yash_2.30-2.debian.tar.gz
 b52bb8843d0d66aa12cecfb1225c38e7 383538 shells extra yash_2.30-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJPti91AAoJEMwUn2wopeJXsDkQAL+pWWjewVo2CjYVvgiEzFOr
63t5fufi4nN2u5YLnLlRTCCyb3TNpkORk1RTtm7Tiim2QEtjeS3N0o5USFMnCbFg
cvhUKBJ/eqrtQUgT6p3q/zhCcEBuxITFO88dKOWcPmaCwW2xieeXRSjuB9A64GRO
sp5RGANhqDVRuZvgJNqWCHeoNTTi3DggK+LbSmkIS7uuvhHb8gr34iZozLTPqllE
hEe3KFpoQ43hiuh16/lCcTAXUTVEeCqtklWta1purqbLKMIfgqichHLyaZ4mkGH0
1rY11DeP27n6L5DrKNW26kB2AgYInmhLptMYzUU+6g3XvqfNgXFTDiNTBFyxca9E
CcXJcjRDCR4LSPg4OhVJY8PsTQJTeSapRQ9RsjgT728GQER5saVZJjbe2i0PeVgF
rohTW2CvvJzHQ2nRsFrpuDvFVZgoe/OSmEw71m5bUDZg1geahGOm1AqfP8R6lt8y
Y7joohUaHIQZybvvo31ZHV4cpILisaevfVLiE0x0ve0VtxJkPZlK9UfqeibOoyIV
/KzvwgbaQV61mbtH+AXAke3QwsAuiMzgiAvIQDFdlQL5bruUA8ywYnVX7OS/oxk0
y4VCHUnOUanaiYkMWnUfUgUK5Wr1bIS7cg24U9j/yd2Zrwqxla2hDK1ls/iNXOlC
QzoLBBWauHxmIAPlKDpH
=m5pd
-END PGP SIGNATURE-


Accepted:
yash_2.30-2.debian.tar.gz
  to main/y/yash/yash_2.30-2.debian.tar.gz
yash_2.30-2.dsc
  to main/y/yash/yash_2.30-2.dsc
yash_2.30-2_amd64.deb
  to main/y/yash/yash_2.30-2_amd64.deb


-- 
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/e1svluf-0004k3...@franck.debian.org

Accepted db-defaults 5.1.6 (source all amd64)

2012-05-18 Thread Ondřej Surý

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 09:32:13 +0200
Source: db-defaults
Binary: libdb-dev db-util db-upgrade-util libdb++-dev libdb-sql-dev 
libdb-java-dev libdb-java
Architecture: source amd64 all
Version: 5.1.6
Distribution: unstable
Urgency: low
Maintainer: Debian Berkeley DB Group pkg-db-de...@lists.alioth.debian.org
Changed-By: Ondřej Surý ond...@debian.org
Description: 
 db-upgrade-util - Berkeley Database Utilities (old versions)
 db-util- Berkeley Database Utilities
 libdb++-dev - Berkeley Database Libraries for C++ [development]
 libdb-dev  - Berkeley Database Libraries [development]
 libdb-java - Berkeley Database Libraries for Java
 libdb-java-dev - Berkeley Database Libraries for Java [development]
 libdb-sql-dev - Berkeley Database Libraries [SQL development]
Changes: 
 db-defaults (5.1.6) unstable; urgency=low
 .
   * Remove M-A: foreign from libdb-java, since it was wrong
Checksums-Sha1: 
 4e2ae1bdc361794345947bf319e8c1d0ca8e5e6f 1229 db-defaults_5.1.6.dsc
 2e9a84e1951480b212b7ccafe21a7b4a7a36b1df 2749 db-defaults_5.1.6.tar.gz
 c353274d8f666fd2e72cd5558c84be1a24be11fd 2240 libdb-dev_5.1.6_amd64.deb
 fae06ada2725ece281bdcbd6aea20d6bdde562a7 2866 db-util_5.1.6_all.deb
 fac94a9a00aad2972e2a0a29f378d770e4b5f322 2400 db-upgrade-util_5.1.6_all.deb
 beebb64ea145c62a3b14fe82b31e0db37b2094ec 2298 libdb++-dev_5.1.6_amd64.deb
 42b0c10c2f07a3d7806db72e40c95a44ef159554 2232 libdb-sql-dev_5.1.6_amd64.deb
 46747eba45b28d7034efe24d4e1f8c6bda49f9a5 2268 libdb-java-dev_5.1.6_amd64.deb
 c7e33dbdaf362add7760e3f571c3d4cd385e521e 2212 libdb-java_5.1.6_all.deb
Checksums-Sha256: 
 35844b084dab8c658662fcc323995874f98b9272fb4c7c97d783d9e081a0c55a 1229 
db-defaults_5.1.6.dsc
 7dfc311e7a992a4b16c6848dda2fdd500be46107dce0aef00e6face594ac0901 2749 
db-defaults_5.1.6.tar.gz
 3b0fdee3ac89c9c1392d6415c172bc0be8f1b3f2cf491cf74e992318709f1ad1 2240 
libdb-dev_5.1.6_amd64.deb
 96d00e103c031ea407d239a0f36c973c7f861a1d1718a0e4ac2e46728e34d57a 2866 
db-util_5.1.6_all.deb
 faff2b6851ef2d32257ba8bab75569b9fe73469a3f6a2c92461f9070a5e155dd 2400 
db-upgrade-util_5.1.6_all.deb
 9b8a5c7d07b228765022aa00a281263c09a2392f88f55bf750de2f156f6a16ab 2298 
libdb++-dev_5.1.6_amd64.deb
 2f18ace01f371c9a08e9422a7b59a9ea9bdfb3a24ab71cc9ff02283363ea6fac 2232 
libdb-sql-dev_5.1.6_amd64.deb
 4b20f40af15905fe3076ef67278ac4ea7fb1fc4c765db963a0593e33173fc9a2 2268 
libdb-java-dev_5.1.6_amd64.deb
 4fcf0375851a3057dfd12c419e6b333810b2eaa0b739147efca0357689967f29 2212 
libdb-java_5.1.6_all.deb
Files: 
 cc54201b49edb3ef486cd83cadc0a754 1229 libdevel extra db-defaults_5.1.6.dsc
 375fe6c7efc51e79baa95d0b905c6cef 2749 libdevel extra db-defaults_5.1.6.tar.gz
 18627ba743fb96578ef1505499e1b0bf 2240 libdevel extra libdb-dev_5.1.6_amd64.deb
 7999cb93dc2fc1bf981c87e202ae8cce 2866 utils extra db-util_5.1.6_all.deb
 4d5f698c9bbee5ef0d369a3b739e79ba 2400 utils extra db-upgrade-util_5.1.6_all.deb
 fa4f9c1ca9a6356d186629b97c9f95af 2298 libdevel extra 
libdb++-dev_5.1.6_amd64.deb
 86532a6947d00778fa86c0ad842bc8a7 2232 libdevel extra 
libdb-sql-dev_5.1.6_amd64.deb
 31ae8f6ac57776b298aa7ab56e71c3ef 2268 libdevel extra 
libdb-java-dev_5.1.6_amd64.deb
 8c031c4140013f6c610ce0bfd05d2c3f 2212 java extra libdb-java_5.1.6_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+2OeoACgkQ9OZqfMIN8nOU5wCfXs2O4a0AL7GlrDl4ZTw+1Ph5
eJwAmwfnEuvbyftOoeXSMMEJGowH1G1s
=XJDh
-END PGP SIGNATURE-


Accepted:
db-defaults_5.1.6.dsc
  to main/d/db-defaults/db-defaults_5.1.6.dsc
db-defaults_5.1.6.tar.gz
  to main/d/db-defaults/db-defaults_5.1.6.tar.gz
db-upgrade-util_5.1.6_all.deb
  to main/d/db-defaults/db-upgrade-util_5.1.6_all.deb
db-util_5.1.6_all.deb
  to main/d/db-defaults/db-util_5.1.6_all.deb
libdb++-dev_5.1.6_amd64.deb
  to main/d/db-defaults/libdb++-dev_5.1.6_amd64.deb
libdb-dev_5.1.6_amd64.deb
  to main/d/db-defaults/libdb-dev_5.1.6_amd64.deb
libdb-java-dev_5.1.6_amd64.deb
  to main/d/db-defaults/libdb-java-dev_5.1.6_amd64.deb
libdb-java_5.1.6_all.deb
  to main/d/db-defaults/libdb-java_5.1.6_all.deb
libdb-sql-dev_5.1.6_amd64.deb
  to main/d/db-defaults/libdb-sql-dev_5.1.6_amd64.deb


-- 
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/e1svm7z-00075x...@franck.debian.org

Accepted openmpi 1.4.5-1 (source i386 all)

2012-05-18 Thread Sylvestre Ledru

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 11:26:16 +0200
Source: openmpi
Binary: openmpi-bin libopenmpi-dev libopenmpi1.3 openmpi-common openmpi-doc 
libopenmpi-dbg openmpi-checkpoint
Architecture: source i386 all
Version: 1.4.5-1
Distribution: unstable
Urgency: low
Maintainer: Debian Open MPI Maintainers 
pkg-openmpi-maintain...@lists.alioth.debian.org
Changed-By: Sylvestre Ledru sylves...@debian.org
Description: 
 libopenmpi-dbg - high performance message passing library -- debug library
 libopenmpi-dev - high performance message passing library -- header files
 libopenmpi1.3 - high performance message passing library -- shared library
 openmpi-bin - high performance message passing library -- binaries
 openmpi-checkpoint - high performance message passing library -- checkpoint 
support
 openmpi-common - high performance message passing library -- common files
 openmpi-doc - high performance message passing library -- man pages
Changes: 
 openmpi (1.4.5-1) unstable; urgency=low
 .
   * New upstream release
   * ACK NMUs
   * Switch to dpkg-source 3.0 (quilt) format
   * Refresh of the patches
   * Standards-Version updated to version 3.9.3
Checksums-Sha1: 
 441a41338176d8508f944a2c944ba8a8ff2d7000 1990 openmpi_1.4.5-1.dsc
 ffc613be834a892744ac463c8812d5f5b7e32745 10110428 openmpi_1.4.5.orig.tar.gz
 4bab6d3ddae4089ff42ce3da00ede3e7a706417a 28248 openmpi_1.4.5-1.debian.tar.gz
 45cc9f2a9a7d291c301c8a2f936f72b28b9caf09 164706 openmpi-bin_1.4.5-1_i386.deb
 6277f5d7fc0e8b99f10ecc38b13892dc513409da 2682800 
libopenmpi-dev_1.4.5-1_i386.deb
 7dc17b878ad2b5437bc8e47dd35f415221b6a104 1384102 libopenmpi1.3_1.4.5-1_i386.deb
 5dc952642d8f6ccf329163f10443da53785ef677 6181886 
libopenmpi-dbg_1.4.5-1_i386.deb
 ec940ab10fea2af2eda8b6aa9003bf8e35270fb1 93978 
openmpi-checkpoint_1.4.5-1_i386.deb
 f3faf342944969dae15ba19cbf7717d06463c9b9 101006 openmpi-common_1.4.5-1_all.deb
 cf3225874f14343bad6ca840ea675be5b204b443 480588 openmpi-doc_1.4.5-1_all.deb
Checksums-Sha256: 
 c7fd6720b4f565e49acb7783034b7ebf2d01e7dbdb47a214164932c6bc510aa6 1990 
openmpi_1.4.5-1.dsc
 a1306bb4d44d0cf3a89680c4c6723bb665126c9d5523022f187b944b9d4ea6a5 10110428 
openmpi_1.4.5.orig.tar.gz
 b5361c05f009e8aa4acac45bb75e6f0d065f8eb5fb7f3308fa8819a0451ac66a 28248 
openmpi_1.4.5-1.debian.tar.gz
 941328813de8738204bdafff5edad42445aadd94ee83b8a0916a83606cc1fc90 164706 
openmpi-bin_1.4.5-1_i386.deb
 ae9b8e0bfb6cb783a993c53c6cc31929546f76e5d0630d5708dc8167c167ea4d 2682800 
libopenmpi-dev_1.4.5-1_i386.deb
 68c2d5affe7f09a5b4fd7f0db56843a82341c0b2e1465c9de5595758b9d9e63f 1384102 
libopenmpi1.3_1.4.5-1_i386.deb
 52c436e0e7958f8dd75181cae7e6e53dfee8c2acf57f1884bd998b8c081bf053 6181886 
libopenmpi-dbg_1.4.5-1_i386.deb
 9ec209dd23b1abc7cdee79fe7faf0e505bd8138b860161a16be03b08d53d1644 93978 
openmpi-checkpoint_1.4.5-1_i386.deb
 17ded8e739e50768b8e2e69b6c140f0d10db5bc15cc7453019af63bcc2e7c500 101006 
openmpi-common_1.4.5-1_all.deb
 fa7eee2f789448d573fbfaa3964026c1107fc75cabe56bcf1e9092ae88d917d0 480588 
openmpi-doc_1.4.5-1_all.deb
Files: 
 b6dfc723b614e23e68753eb471086c34 1990 net extra openmpi_1.4.5-1.dsc
 28b2a7f9c2fcee0217facf47bf35d5ea 10110428 net extra openmpi_1.4.5.orig.tar.gz
 284707089511b47d1f4603e133d03690 28248 net extra openmpi_1.4.5-1.debian.tar.gz
 7baddaae5f4758da9be56c20d48d0854 164706 net extra openmpi-bin_1.4.5-1_i386.deb
 1118b26f9c2dcbcd67320eaba5633c6f 2682800 libdevel extra 
libopenmpi-dev_1.4.5-1_i386.deb
 b369d01ada178217ad89a8e4aef33b4b 1384102 libs extra 
libopenmpi1.3_1.4.5-1_i386.deb
 af904d043906bab662491d35c9f89dc5 6181886 debug extra 
libopenmpi-dbg_1.4.5-1_i386.deb
 c7fb7ce90f07f000fb3cc840d732dcc2 93978 net extra 
openmpi-checkpoint_1.4.5-1_i386.deb
 a393a23cd65aacc0b3ab257a0232e945 101006 net extra 
openmpi-common_1.4.5-1_all.deb
 d0649c696af00b9a4e9f03a37ae2265a 480588 doc extra openmpi-doc_1.4.5-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAk+2OjkACgkQiOXXM92JlhCGVgCdHlucBLYaSw5eP6vmUUcVVERt
nDQAn06246art4JIHuwRWO8SdAAXv+YC
=un6C
-END PGP SIGNATURE-


Accepted:
libopenmpi-dbg_1.4.5-1_i386.deb
  to main/o/openmpi/libopenmpi-dbg_1.4.5-1_i386.deb
libopenmpi-dev_1.4.5-1_i386.deb
  to main/o/openmpi/libopenmpi-dev_1.4.5-1_i386.deb
libopenmpi1.3_1.4.5-1_i386.deb
  to main/o/openmpi/libopenmpi1.3_1.4.5-1_i386.deb
openmpi-bin_1.4.5-1_i386.deb
  to main/o/openmpi/openmpi-bin_1.4.5-1_i386.deb
openmpi-checkpoint_1.4.5-1_i386.deb
  to main/o/openmpi/openmpi-checkpoint_1.4.5-1_i386.deb
openmpi-common_1.4.5-1_all.deb
  to main/o/openmpi/openmpi-common_1.4.5-1_all.deb
openmpi-doc_1.4.5-1_all.deb
  to main/o/openmpi/openmpi-doc_1.4.5-1_all.deb
openmpi_1.4.5-1.debian.tar.gz
  to main/o/openmpi/openmpi_1.4.5-1.debian.tar.gz
openmpi_1.4.5-1.dsc
  to main/o/openmpi/openmpi_1.4.5-1.dsc
openmpi_1.4.5.orig.tar.gz
  to main/o/openmpi/openmpi_1.4.5.orig.tar.gz


-- 
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe.

Accepted ecryptfs-utils 96-1 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 13:32:14 +0200
Source: ecryptfs-utils
Binary: ecryptfs-utils ecryptfs-utils-dbg libecryptfs0 libecryptfs-dev 
python-ecryptfs
Architecture: source i386
Version: 96-1
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann daniel.baum...@progress-technologies.net
Changed-By: Daniel Baumann daniel.baum...@progress-technologies.net
Description: 
 ecryptfs-utils - ecryptfs cryptographic filesystem (utilities)
 ecryptfs-utils-dbg - ecryptfs cryptographic filesystem (utilities; debug)
 libecryptfs-dev - ecryptfs cryptographic filesystem (development)
 libecryptfs0 - ecryptfs cryptographic filesystem (library)
 python-ecryptfs - ecryptfs cryptographic filesystem (python)
Closes: 668738
Changes: 
 ecryptfs-utils (96-1) unstable; urgency=low
 .
   * Merging upstream version 96.
   * Updating to debhelper version 9.
   * Updating to standards version 3.9.3.
   * Updating copyright file machine-readable format version 1.0.
   * Removing leading slashes from debhelper install entries.
   * Disabling hardening build flags temporarily to avoid FTBFS.
   * Updating packaging for multiarch.
   * Removing /var/lib/ecryptfs on purge (Closes: #668738).
   * Updating lintian overrides.
Checksums-Sha1: 
 6ee3dda3e645665344c670f1be75c0d59d2b2ae6 1687 ecryptfs-utils_96-1.dsc
 43234bd09a1c4d5293c9f6a35817472c21aab7b7 608135 ecryptfs-utils_96.orig.tar.gz
 0860577649ff873a642754a02a19962bab539f02 8541 ecryptfs-utils_96-1.debian.tar.gz
 653b814982da1b48d5a5a5989df01b170b7dbb2f 111372 ecryptfs-utils_96-1_i386.deb
 21721baeb7beca92ece37a7c8b396fc5e8e648b5 218976 
ecryptfs-utils-dbg_96-1_i386.deb
 4eb15af791f189800e24821ef351b8f3fa36efdc 50986 libecryptfs0_96-1_i386.deb
 22002a1bb9d6fd85a9efb183b418d9e8bca75dd6 58500 libecryptfs-dev_96-1_i386.deb
 6219c534e7557743b15785bd1a8d759cfdaf3def 20358 python-ecryptfs_96-1_i386.deb
Checksums-Sha256: 
 a0deb487be9079690caeb6b0da19da759aac0964e215f885711174cfc1140493 1687 
ecryptfs-utils_96-1.dsc
 04c43b6e7a2f6b3644a24bcf718bfde6384e74bb4266c053ac78b9cc852f2c0c 608135 
ecryptfs-utils_96.orig.tar.gz
 06c310aec707ee48211a6133fe5e036ca7744afdd711944087c2bb4e0dc64f89 8541 
ecryptfs-utils_96-1.debian.tar.gz
 97dace15ce34dd18a2dfe1ce6a4be73717d8376cd55744a5d4ba56dc5528a61d 111372 
ecryptfs-utils_96-1_i386.deb
 c2c20260e9018d27b12411cb57fdfb235f6a4d72e58b9be82128f2cf177b1c71 218976 
ecryptfs-utils-dbg_96-1_i386.deb
 e7341a1300190484c1fca03f80e205165cff96a98cd8bfec5a46fe74f71c5e73 50986 
libecryptfs0_96-1_i386.deb
 cff487e6bf07f2540bd84d319b6fe2726bc57cf166061a4d584314e03f472ec3 58500 
libecryptfs-dev_96-1_i386.deb
 8898b195fb94d29dbb44ba28937e2adbef3eca87c8f7ce143292bd5481cd2d4a 20358 
python-ecryptfs_96-1_i386.deb
Files: 
 c120316363548fcfe24a27c3fa05be4a 1687 misc optional ecryptfs-utils_96-1.dsc
 4f92c9f6e8f62ac00ca7e2c4e480f1d7 608135 misc optional 
ecryptfs-utils_96.orig.tar.gz
 b4fea6a18aaef1403d8ff379d9545c44 8541 misc optional 
ecryptfs-utils_96-1.debian.tar.gz
 3e3d870bf38856b1cbe8e8373c1825b5 111372 misc optional 
ecryptfs-utils_96-1_i386.deb
 e20068390aec5656d9c40ecdafa62344 218976 debug extra 
ecryptfs-utils-dbg_96-1_i386.deb
 9d43ae64384b90e35b84326ea795c9ca 50986 libs optional libecryptfs0_96-1_i386.deb
 7358b4b0043042faaa1b881006f788c7 58500 libdevel optional 
libecryptfs-dev_96-1_i386.deb
 efb4c56fb58cd54d4f05fead14498f12 20358 python optional 
python-ecryptfs_96-1_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAk+2PRgACgkQ+C5cwEsrK55HZACcD21U+qHPibdJvPwh5B+dMklC
yF0AnAvPh/ytA6sbGyqWFkG5u6L+5G1a
=FCjm
-END PGP SIGNATURE-


Accepted:
ecryptfs-utils-dbg_96-1_i386.deb
  to main/e/ecryptfs-utils/ecryptfs-utils-dbg_96-1_i386.deb
ecryptfs-utils_96-1.debian.tar.gz
  to main/e/ecryptfs-utils/ecryptfs-utils_96-1.debian.tar.gz
ecryptfs-utils_96-1.dsc
  to main/e/ecryptfs-utils/ecryptfs-utils_96-1.dsc
ecryptfs-utils_96-1_i386.deb
  to main/e/ecryptfs-utils/ecryptfs-utils_96-1_i386.deb
ecryptfs-utils_96.orig.tar.gz
  to main/e/ecryptfs-utils/ecryptfs-utils_96.orig.tar.gz
libecryptfs-dev_96-1_i386.deb
  to main/e/ecryptfs-utils/libecryptfs-dev_96-1_i386.deb
libecryptfs0_96-1_i386.deb
  to main/e/ecryptfs-utils/libecryptfs0_96-1_i386.deb
python-ecryptfs_96-1_i386.deb
  to main/e/ecryptfs-utils/python-ecryptfs_96-1_i386.deb


-- 
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/e1svmmt-0007x7...@franck.debian.org

Accepted caret 5.6.4~dfsg.1-3 (source amd64)

2012-05-18 Thread Michael Hanke

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 18 May 2012 13:35:38 +0200
Source: caret
Binary: caret
Architecture: source amd64
Version: 5.6.4~dfsg.1-3
Distribution: unstable
Urgency: low
Maintainer: NeuroDebian Team t...@neuro.debian.net
Changed-By: Michael Hanke m...@debian.org
Description: 
 caret  - Computerized Anatomical Reconstruction and Editing Toolkit
Closes: 672020
Changes: 
 caret (5.6.4~dfsg.1-3) unstable; urgency=low
 .
   * Add patch to properly link against libGLU. Thanks to Nicolas Bourdaud
 for the patch (Closes: #672020).
Checksums-Sha1: 
 93d9b1410e1f8611eaaa392c239c890e8f29436a 2136 caret_5.6.4~dfsg.1-3.dsc
 32c22add684b89d52ae1f58eec321a31884c5570 13715 
caret_5.6.4~dfsg.1-3.debian.tar.gz
 2d980a314faa3b9d3754e184c547eb14eb7341ba 7250318 caret_5.6.4~dfsg.1-3_amd64.deb
Checksums-Sha256: 
 7e0db098a804ee5e4e958fe50809c9623dc257c722529a3793e67f6bdf15b54e 2136 
caret_5.6.4~dfsg.1-3.dsc
 cae5c2d9fb11c03b9a97c20af8bd31f9d7200b401d3ab1b5aea9fbb751827739 13715 
caret_5.6.4~dfsg.1-3.debian.tar.gz
 48207852abadbc5b480d5a6ab873416c4b46b28024a8e9d719f31438d0329f0c 7250318 
caret_5.6.4~dfsg.1-3_amd64.deb
Files: 
 2052bfdded02113b038798917673d04e 2136 science optional caret_5.6.4~dfsg.1-3.dsc
 eafd7c9fab95bd49376ad2244dfcdf7b 13715 science optional 
caret_5.6.4~dfsg.1-3.debian.tar.gz
 f231b9788b76744d2a91c5db195526dd 7250318 science optional 
caret_5.6.4~dfsg.1-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJPtkDHAAoJEMBz0ih/+56bfBUQAL1+J/Raqgr8sGkH+ZbrU4hC
DVdzYroImJtW5FdDlaCCOcY4TG12+1ni77Fxpwl1RzflBz9SJOnC9L0yasDmjgSM
X+ANfJQe4HtiH1s+g0Lb5ZVpXmSOpuVt6Iu9zEmLs5treGHUjMP2M1Ij/fLsIvN+
JoZKpFzjid+jz5pfGeuTWZNyXxDy7LXCTS0wuhYXjrZQGOL3cOxAjcSgF6QlgOXj
/q0Hy1BhWPe4j3STNHVA/5jqnYNTPp2V7DKYuqYTEbdObiwHW/jeGlurYNmvij8M
2QslGrXuEkqfQyB8O7itDS/yA628QNJd7uYWq4mpVNQg+btjoj5MLpevT7OOaHBC
9MT4fzbKmuwP99ARBCz4nKcO6yL6iJrV4uN0NymJ78QeydGJjMJkGiomi6V8dRVp
yxwAmjY78oCcHND1HR0blvMhRYA56zlZu7tIGyZPPvesBFrIVNVMQcNn/D1aijaw
SsIQ7h7rb6V3m00P0KaXUZzSXzgv7J6o0p6PEP4OGyTqO+9JiI+vyNR0xkPa8sIT
ql/r/zPmu32CHBVf5CJBJVrurUdOBZKniTIl1+uAAOsH8CNRxRjJoZLMJlPnZA70
fqN0a3njOtqKkCSS4YEvtf5jIAcr1xT3YNEW2aFL93J3yyir9MEMaUokIV3z3BI0
IVNAGEIkZOUzTk74/RIG
=LWxX
-END PGP SIGNATURE-


Accepted:
caret_5.6.4~dfsg.1-3.debian.tar.gz
  to main/c/caret/caret_5.6.4~dfsg.1-3.debian.tar.gz
caret_5.6.4~dfsg.1-3.dsc
  to main/c/caret/caret_5.6.4~dfsg.1-3.dsc
caret_5.6.4~dfsg.1-3_amd64.deb
  to main/c/caret/caret_5.6.4~dfsg.1-3_amd64.deb


-- 
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/e1svmax-bs...@franck.debian.org

Accepted dnprogs 2.59+nmu1 (source amd64)

2012-05-18 Thread Steve McIntyre

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 18 May 2012 13:29:53 +0100
Source: dnprogs
Binary: dnet-common dnet-progs libdnet libdnet-dev
Architecture: source amd64
Version: 2.59+nmu1
Distribution: unstable
Urgency: low
Maintainer: Christine Caulfield chris...@debian.org
Changed-By: Steve McIntyre 93...@debian.org
Description: 
 dnet-common - Base package for Linux DECnet
 dnet-progs - DECnet user programs and daemons
 libdnet- DECnet Libraries
 libdnet-dev - DECnet development libraries  Headers
Closes: 655740
Changes: 
 dnprogs (2.59+nmu1) unstable; urgency=low
 .
   * NMU
   * Reduce libdnet's recommends on dnet-common to suggests again.
 Closes: #655740. Adapted patch from Jonathan Nieder.
Checksums-Sha1: 
 fd6b0cfebf1cbad872891d40c3a35723663707e6 1618 dnprogs_2.59+nmu1.dsc
 b49c7532f730ee75d93e45856e2ba520089ee206 733565 dnprogs_2.59+nmu1.tar.gz
 7c5140664c8cf26326ad783d91ca66fedd2d9796 48058 dnet-common_2.59+nmu1_amd64.deb
 1d9924ff395ce827418bf6d750080d5187ef78d9 290150 dnet-progs_2.59+nmu1_amd64.deb
 1e7e7e8e207884ac7d5bb15d3e8fe352d00639a1 92468 libdnet_2.59+nmu1_amd64.deb
 df68883987d684942b32034ae3bc8393a8372067 331916 libdnet-dev_2.59+nmu1_amd64.deb
Checksums-Sha256: 
 0968ceeb17ec8bc24ece2158f1f4ab6aa3d87530d77f6fa97d35e824d1ec68d0 1618 
dnprogs_2.59+nmu1.dsc
 264d6e9897841ce31b14648474f2f482709e7d7b67fcf10be7584ea6744d711d 733565 
dnprogs_2.59+nmu1.tar.gz
 9f243930b0c4195d50149b692d7535e507c08f984463d94f9fed6bda0d8d65c7 48058 
dnet-common_2.59+nmu1_amd64.deb
 d07a465d4cfc2448ddd31c10f801be280d765f9a769abc2a3f36411008443e05 290150 
dnet-progs_2.59+nmu1_amd64.deb
 7d747ae4446344c105bf1cba8a99aa06122883e8692697c8b20ddad564e51fc0 92468 
libdnet_2.59+nmu1_amd64.deb
 10d8597a111a78bdab1e7af94679d69b7c35b33cee3738136bea54d8be3fc643 331916 
libdnet-dev_2.59+nmu1_amd64.deb
Files: 
 c765523ced76475badb3b54e605c5ab0 1618 net extra dnprogs_2.59+nmu1.dsc
 c42223ac276b7ea2723d94dae8cb1ee6 733565 net extra dnprogs_2.59+nmu1.tar.gz
 e215d1ece3ab7535db8a2fb9bee09e6c 48058 net extra 
dnet-common_2.59+nmu1_amd64.deb
 1d9273874c1cf4c3b840ab0fadf31f5f 290150 net extra 
dnet-progs_2.59+nmu1_amd64.deb
 200cfa8dccb7323b768ee67753db6afb 92468 libs optional 
libdnet_2.59+nmu1_amd64.deb
 20fa9e487ce666b128ff940dc3eca346 331916 libdevel extra 
libdnet-dev_2.59+nmu1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJPtkM8AAoJEFh5eVc0QmhOR8wQAKRQ1S7nyAbJqQIrz5TdNQCQ
e6fvWHiYgncpUpKwz/e4afAfScE4k7XDuGh2P/G56GzDwa8Y+7kx4UYwXGMphTgH
7KmKX9/XUVL1BxcFmodVehmOwX8WS5QKS5bWWZhvbi3uGYEOu4UU8QE8z8xh0t+N
v2ZSpD/dfXF/22dUnPDV7r2/r9QpCj2ToXxHSqz26xFjMDoj9D5lTWaCXehyjPxr
PVT/COfn2qDK2jgQLogyFAll8IyJhpO34qUcto/Lk/8V+otM2ppGUIVYJlnu9KrE
0HdAM4InfJ9UwWtdqGY/HcBjR23koTxGBlXzEPZoHjgLYL8Z8RMccIYAo5a89asE
pYM8LhVh5k6ukvJFj6y9MSRgSq4BLpu8KLIMKo3kXHctLHBNCJ7QdaKHacHHMcGI
921lybVum7F01KlamuKD/OPUgiCt190EQKjoSvOEeWvuwcoV+l1Z5Kle4SLg38AT
3hN0H4qAI/o2SehrcjbGE7qv6IH4NrC04izLdqtz8kP1CH0IlidrurSMhD1Fxv+G
PmvCFoSRVpjS1wAB5dFHuwu2hj4HjPR0HnOk6Ywz/kfdFskgF9QJTPWACYrQkO9C
7jREtKdqWdNIE+q315k+03UrImsPGb/uuGUEVpiufCR8u30wJOvmxgLnscR8J0Kz
B6B8gHB4Tp4AN7GaEHF9
=OdjZ
-END PGP SIGNATURE-


Accepted:
dnet-common_2.59+nmu1_amd64.deb
  to main/d/dnprogs/dnet-common_2.59+nmu1_amd64.deb
dnet-progs_2.59+nmu1_amd64.deb
  to main/d/dnprogs/dnet-progs_2.59+nmu1_amd64.deb
dnprogs_2.59+nmu1.dsc
  to main/d/dnprogs/dnprogs_2.59+nmu1.dsc
dnprogs_2.59+nmu1.tar.gz
  to main/d/dnprogs/dnprogs_2.59+nmu1.tar.gz
libdnet-dev_2.59+nmu1_amd64.deb
  to main/d/dnprogs/libdnet-dev_2.59+nmu1_amd64.deb
libdnet_2.59+nmu1_amd64.deb
  to main/d/dnprogs/libdnet_2.59+nmu1_amd64.deb


-- 
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/e1svmbj-dt...@franck.debian.org

Accepted efilinux 1.0-1 (source i386)