date:20100525

Ferenc Wagner wrote:
 Stephen Powell zlinux...@wowway.com writes:

 Both grub-legacy and grub-pc use sectors on the hard disk outside of
 the master boot record and outside of a partition ...

 You may want to try extlinux, it works much like LILO in this respect.

Well, I tried extlinux last night, and I am hopeful that this is going
to be a solution, at least for me.  extlinux seems to combine the best
parts of grub-pc and lilo.  Like grub-pc, extlinux understands the file
system, and can read the configuration file, kernel, and the initial
RAM file system image from the file system without needing a list of
specific blocks to read.  Thus, the boot loader does not need to be re-run
every time a kernel is installed or updated or an initial RAM file system
image is installed or updated.  The number of file systems it supports
is limited, but that's OK.  A separate /boot partition of the file system
type supported by the boot loader is acceptable.

But like lilo it stays out of unallocated (and therefore not backed up)
sectors.  The boot block of extlinux is installed in the boot sector
of a partition, and the second stage loader occupies a file within the
partition.  It does not use the master boot record.  It relies on a
master boot record program to chain load it from the partition boot
sector.  (I use the mbr package for that.)  It *does* support the
specification of an initial text video mode (vga option), though this
is not specifically documented.

Speaking of documentation, that seems to be its main weakness.
Documentation is sketchy and spread out over a number of different files.
I would have had a hard time configuring it if it weren't for
correct guesses based on my knowledge of how lilo is configured, which
newer users won't have.  It installs hook scripts that I don't want
(and that have bugs).  But after manual configuration and tweaking,
it works just fine.  Now, if it passes the backup / low-level-format /
restore test, I'll be good to go.  Stay tuned ...

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
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/1078928757.35141.1274793733671.javamail.r...@md01.wow.synacor.com

Re: Upstream stopped to ship tar.gz file. What to do?

2010-05-25 Thread Paul Wise

On Tue, May 25, 2010 at 7:58 PM, Artur R. Czechowski artu...@snafu.pl wrote:

 Upstream of imms stopped to ship tar.gz file and ships only tar.bz2.

So they deleted existing tarballs and added new tar.bz2 tarballs?

 However, there is no new upstream release at the moment. The question is:
 Shall I prepare new release of Debian package using tar.bz2 tarball?

Send upstream Ubuntu's patch, make patches for the 2 bugs, poke them
to make a new release, fix the watch file etc and then upload that.

 There was a short discussion on #debian-devel, but there was no conclusion.
 Possible answers are:
 1. Definitely, if possible you shall keep the tarball the same as upstream
   tarball (unless other concerns are involved, like, for example, DFSG
   compliancy).
 2. Absolutely not. Just stick to current tarball and switch when new upstream
   release will be available.
 3. This is the sole maintainer's decision.

I prefer my solution, but otherwise 3, then 2 then 1.

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

Re: Upstream stopped to ship tar.gz file. What to do?

2010-05-25 Thread Russ Allbery

Artur R. Czechowski artu...@snafu.pl writes:

 Upstream of imms stopped to ship tar.gz file and ships only tar.bz2.
 However, there is no new upstream release at the moment. The question
 is:  Shall I prepare new release of Debian package using tar.bz2
 tarball?

 There was a short discussion on #debian-devel, but there was no conclusion.
 Possible answers are:
 1. Definitely, if possible you shall keep the tarball the same as upstream
tarball (unless other concerns are involved, like, for example, DFSG
compliancy).
 2. Absolutely not. Just stick to current tarball and switch when new upstream
release will be available.

I'd go with 2.  I don't see any need to hurry with replacing the tarball
with a bzip2-compressed version until upstream releases a new release.

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

Re: lilo removal in squeeze (or, please test grub2)

On Tue, 25 May 2010 07:08:20 -0400 (EDT), Mihamina Rakotomandimby wrote:
 William Pitcock neno...@dereferenced.org wrote:
 This bug *can* be fixed, but not without a significant rewrite of the
 way that lilo's stage2 loader code works.  Given that there is no
 active upstream and that the Debian lilo package carries many patches
 for bug fixes that are alleviated by standardizing on grub2, this
 seems like the best option for Debian.
 
 Agreed: dead (and buggy) softwares must be out of the distribution.
 Whatever happens. If LILO regains upstream coders, its return to the
 distribution is quite easy.

By that standard, grub-pc should be removed from the distribution.
It may have upstream support, but based on other posts I've seen, it
effectively has no maintainer.  Which is worse, a package with
effectively no upstream support or a package with effectively no
maintainer?  And grub-pc is buggier than lilo.

I understand the need to remove packages with no upstream support.
But asking users to test a package with umpteen known release-critical
bugs, most of which have apparently been fixed upstream, but have
not been fixed in Debian because there is no maintainer to download
a new upstream version, is not a reasonable request in my humble
opinion.  Get a maintainer for it, fix the known bugs, and *then*
ask the users to test it.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
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/1927842586.35924.1274795074336.javamail.r...@md01.wow.synacor.com

Re: Bug#581488: general: lower vm.swappiness by default for desktop installations

2010-05-25 Thread David Weinehall

On Tue, May 25, 2010 at 06:59:45AM -0600, Aaron Toponce wrote:
 On 5/12/2010 1:22 PM, Marcus Better wrote:
  Recently I got the advice [1] to set vm.swappiness to 0, rather than
  the default 60. This improved things dramatically. Apparently Eclipse
  is no longer being swapped out preemptively all the time. The
  difference in perceived responsiveness is spectacular.
 
 You might also be interested in:
 
 # sync; cat 3  /proc/sys/vm/drop_caches

That'd be

sync; echo 3  /proc/sys/vm/drop_caches



Kind regards: David Weinehall
-- 
 /) David Weinehall t...@debian.org /) Rime on my window   (\
//  ~   //  Diamond-white roses of fire //
\)  http://www.acc.umu.se/~tao/(/   Beautiful hoar-frost   (/


-- 
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/20100525142625.gg24...@test5.acc.umu.se

Re: lilo removal in squeeze (or, please test grub2)

2010-05-25 Thread David Weinehall

On Tue, May 25, 2010 at 09:22:13AM -0400, Stephen Powell wrote:

[snip]

 Speaking of documentation, that seems to be its main weakness.
 Documentation is sketchy and spread out over a number of different files.
 I would have had a hard time configuring it if it weren't for
 correct guesses based on my knowledge of how lilo is configured, which
 newer users won't have.  It installs hook scripts that I don't want
 (and that have bugs).  But after manual configuration and tweaking,
 it works just fine.  Now, if it passes the backup / low-level-format /
 restore test, I'll be good to go.  Stay tuned ...

Perhaps you, with the experienced gained from your adventures with
extlinux, could help write some documentation?


Kind regards: David Weinehall
-- 
 /) David Weinehall t...@debian.org /) Rime on my window   (\
//  ~   //  Diamond-white roses of fire //
\)  http://www.acc.umu.se/~tao/(/   Beautiful hoar-frost   (/


-- 
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/20100525143916.gh24...@test5.acc.umu.se

Re: lilo removal in squeeze (or, please test grub2)

2010-05-25 Thread Ferenc Wagner

Stephen Powell zlinux...@wowway.com writes:

 Ferenc Wagner wrote:

 Stephen Powell zlinux...@wowway.com writes:

 Both grub-legacy and grub-pc use sectors on the hard disk outside of
 the master boot record and outside of a partition ...

 You may want to try extlinux, it works much like LILO in this respect.

 It does not use the master boot record.  It relies on a master boot
 record program to chain load it from the partition boot sector.  (I
 use the mbr package for that.)

The extlinux package itself also contains an mbr.bin, which you can use
(it's strong point is probably EBIOS support).

 Speaking of documentation, that seems to be its main weakness.
 Documentation is sketchy and spread out over a number of different files.

/usr/share/doc/extlinux.txt.gz references syslinux.txt, which is fairly
comprehensive according to my standards, at least as far as the core is
concerned.  What did you miss?  Some modules may be less well documented.

 It installs hook scripts that I don't want (and that have bugs).

I hope we can fix them soon (they are Debian specific additions).
-- 
Cheers,
Feri.


-- 
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/874ohwt3td@tac.ki.iif.hu

Re: Upstream stopped to ship tar.gz file. What to do?

2010-05-25 Thread Peter Samuelson


[Artur R. Czechowski]
 BTW, I'm doing also other changes in the package. So, changing the tarball
 is not an only purpose of new package release.
 
 Pro:
 To verify if tarball content is the same as upstream ones, one need
 to fetch both tarballs, unpack them and verify the checksum of each
 file, instead of just checking the checksum of whole tarballs.

bzip2 only has one commonly used implementation, and it hasn't really
changed in a long time, and it doesn't have troublesome features like
gzip -n or --rsyncable, so usually you can check a published checksum
with:

gzip -cd foo.tar.gz | bzip2 -9 | md5sum -

(Most people use -9, anyway.)

I agree with Russ.  There's no compelling reason to upload a tar.bz2
that has the same content as an existing tar.gz.  At the very least,
you would have to give the tarball a new upstream version number.  Not
worth it.
-- 
Peter Samuelson | org-tld!p12n!peter | http://p12n.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/20100525155518.gb18...@p12n.org

Re: Re (2): lilo removal in squeeze (or, please test grub2)

On Mon, 24 May 2010 17:29:54 -0400 (EDT), Peter Easthope wrote:
 Stephen Powell wrote:
 (3) The need for special backup requirements will be 
 used by the opponents of Linux at my place of employment 
 to oppose further deployments of Linux, ...
 
 What about the carrot approach?  Find an even better 
 backup method, compatible with Grub 2 and appealing 
 to your management for its efficiency.

You're missing the point.  The main selling point to management
is that Linux is free.  If they have to buy new backup software
in order to accommodate Linux' backup requirements, that will
kill it on the spot.  Whatever boot loader I use must not
require new backup software or impose special backup requirements.
And its not just money.  As a rule, people like what they know.
The backup people are Windows people, and they'd love an
excuse to complain to management about the backup requirements
of my Linux servers.  grub-legacy and grub-pc are non-starters
for me for that reason.  Until now, only lilo, as far as I knew,
met all my requirements.  It now appears that extlinux may also
work.  I'll soon know.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
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/351821928.39974.1274802154546.javamail.r...@md01.wow.synacor.com

Re: Re (2): lilo removal in squeeze (or, please test grub2)

2010-05-25 Thread Mark

On Tue, May 25, 2010 at 8:42 AM, Stephen Powell zlinux...@wowway.comwrote:

 On Mon, 24 May 2010 17:29:54 -0400 (EDT), Peter Easthope wrote:
  Stephen Powell wrote:
  (3) The need for special backup requirements will be
  used by the opponents of Linux at my place of employment
  to oppose further deployments of Linux, ...
 
  What about the carrot approach?  Find an even better
  backup method, compatible with Grub 2 and appealing
  to your management for its efficiency.

 You're missing the point.  The main selling point to management
 is that Linux is free.  If they have to buy new backup software
 in order to accommodate Linux' backup requirements, that will
 kill it on the spot.  Whatever boot loader I use must not
 require new backup software or impose special backup requirements.
 And its not just money.  As a rule, people like what they know.
 The backup people are Windows people, and they'd love an
 excuse to complain to management about the backup requirements
 of my Linux servers.  grub-legacy and grub-pc are non-starters
 for me for that reason.  Until now, only lilo, as far as I knew,
 met all my requirements.  It now appears that extlinux may also
 work.  I'll soon know.


Clonezilla is free, and when using the saveparts option to save an image
of one partition and not the full hard drive, it includes the MBR and
associated data.  You can then drop that partition image onto a new/blank
disk, that does not have anything in the MBR, and once Clonezilla restores
the image to the new partition, will put the MBR in place and the machine
boots on its own the next time, with no extra work (I just did this last
week with a new hard drive).  This has been my experience with using
Clonezilla and Lenny, at least.  So it may help in your case.

Mark

Re: Translations copyrights/licences

2010-05-25 Thread Julien Valroff

Le dimanche 23 mai 2010 à 09:01 +0100, Neil Williams a écrit :
 On Sun, 23 May 2010 07:53:14 +0200
 Julien Valroff jul...@kirya.net wrote:
 
  The sources contain gettext translations, the copyrights and licences
  of which are sometimes unclearly stated, eg:
 
 Nearly all packages with translations have problems like this. It
 isn't actually a problem, there's nothing realistic that can be done
 about it and nearly all packages with translations would have the same
 problem. If we accept that this is an issue, we'll have 14,000 RC
 bugs overnight and we'll never release again.
[...]
 
 I see no reason to specify these in debian/copyright.
[...]
  How to deal with such unclear/incomplete headers?
 
 As Debian Maintainer, you don't. Simple.

Thanks a lot to you and to Helge for your clear answers.
I will then follow your advise and not consider information for po
files ;)

Cheers,
Julien


-- 
Julien Valroff jul...@kirya.net
http://www.kirya.net
GPG key: 4096R/290D20C5 
092F 4CB5 5F19 E006 1CFD  B489 D32B 8D66 290D 20C5


-- 
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/1274805771.2652.19.ca...@gaia.kirya.net

Bug#583133: ITP: haskell-glib -- Binding to the GLIB library for Gtk2Hs

2010-05-25 Thread Marco Túlio Gontijo e Silva

Package: wnpp
Severity: wishlist
Owner: Marco Túlio Gontijo e Silva mar...@debian.org

* Package name: haskell-glib
  Version : 0.11.0
  Upstream Author : Axel Simon, Duncan Coutts
* URL : http://www.haskell.org/gtk2hs/
* License : LGPL-2.1
  Programming Lang: Haskell
  Description : Binding to the GLIB library for Gtk2Hs

 This package provides a library for the Haskell programming language.
 See http://www.haskell.org/ for more information on Haskell.
 .
 The GNU Library is a collection of C data structures and utility function for
 dealing with Unicode. This package only binds as much functionality as
 required to support the packages that wrap libraries that are themselves based
 on GLib.



--
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/20100525164121.2702.80988.report...@zezinho

Re: Re (2): lilo removal in squeeze (or, please test grub2)

On Tue, 25 May 2010 11:51:11 -0400 (EDT), Mark mamar...@gmail.com
 On Tue, May 25, 2010 at 8:42 AM, Stephen Powell zlinux...@wowway.comwrote:
 On Mon, 24 May 2010 17:29:54 -0400 (EDT), Peter Easthope wrote:
 Stephen Powell wrote:
 (3) The need for special backup requirements will be
 used by the opponents of Linux at my place of employment
 to oppose further deployments of Linux, ...

 What about the carrot approach?  Find an even better
 backup method, compatible with Grub 2 and appealing
 to your management for its efficiency.

 You're missing the point.  The main selling point to management
 is that Linux is free.  ...

 Clonezilla is free, and when using the saveparts option to save an image
 of one partition and not the full hard drive, it includes the MBR and
 associated data.  You can then drop that partition image onto a new/blank
 disk, that does not have anything in the MBR, and once Clonezilla restores
 the image to the new partition, will put the MBR in place and the machine
 boots on its own the next time, with no extra work (I just did this last
 week with a new hard drive).  This has been my experience with using
 Clonezilla and Lenny, at least.  So it may help in your case.

Perhaps so.  But it's not what the backup people know.  They're very
comfortable with the backup software that they know and love for
backing up their Windows servers, which was purchased with Windows servers
in mind.  Do you think they're going to redo their whole backup architecture
just for a few Linux servers?  If I want to play in their sandbox, I have
to play by their rules.  That's the political reality.  At our shop, Linux
has a small beachhead on a vast continent controlled by Windows.  Over time,
the role of Linux may expand to the point where Linux is actually thought
about and planned for when decisions are made.  But that day is not today.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
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/479605722.42620.1274806845480.javamail.r...@md01.wow.synacor.com

Re: Re (2): lilo removal in squeeze (or, please test grub2)

On Tue, 25 May 2010 12:03:17 -0400 (EDT), Boyd Stephen Smith Jr. wrote:
 Stephen Powell wrote:
 
 You're missing the point.  The main selling point to management
 is that Linux is free.
 
 No software is entirely without cost.  Free Software is no exception.  There 
 are usually no up-front licening fees, sure.  However, volunteers work on 
 whatever they like, and if no one volunteers to maintain and support your 
 software you may have to pay for that.
 
 Even with volunteers providing maintenance and support, your specific 
 requirements may differ from their goals and that will require effort to 
 resolve.
 ...
 Also, volunteers are rarely concerned with market share, losing your 
 management as users is not necessarily a concern to them.  If it is a concern 
 for you, you may have to put forward some additional effort to address your 
 management's issues.

All excellent points, Boyd.  Fortunately in this case, extlinux appears
to be a viable solution.  I'll soon know.  The guy I need to see about
setting a test server to test the backup and restore scenario
has been off work with a sick child for the past couple of days, but when
he gets back I'll try to prove that it is 100% compatible with our
backup software.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
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/1557806589.43087.1274807547943.javamail.r...@md01.wow.synacor.com

Re: Translations copyrights/licences

2010-05-25 Thread Darren Salt

I demand that Helge Kreutzmann may or may not have written...

 Speaking both with my translator and my Debian Maintainer hat on, I can
 state the following:

 a) There are lots of drive by translators. Systems like launchpad or
DDTP even *encourage* this. In this case, it is most likely not
possible at all to contact individual translators.

 b) In structured projects (Debian, Fedora, OOo, KDE, GNOME) there are
often language teams. In this case, translations are often
channeled via the team. So if you want, you can try to collect
the names in the copyright, but a team adress is more valuable.

To me, this all doesn't matter so long as who changed what is recorded and I
can get (or generate) a series of diffs which I can then commit where
appropriate. If I can't, then I'm not really interested.

[snip]
-- 
| Darren Salt| linux at youmustbejoking | nr. Ashington, | Toon
| using Debian GNU/Linux | or ds,demon,co,uk| Northumberland | back!
| + Travel less. Share transport more.   PRODUCE LESS CARBON DIOXIDE.

Without fools there would be no wisdom.


-- 
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/51227c3724%li...@youmustbejoking.demon.co.uk

Browser's and Distro's (was: SWR Iron: Chromium without the data-mining)

Am Tue, 18 May 2010 22:36:56 +0200
schrieb Christoph Anton Mitterer cales...@scientia.net:

 Hi.
 
 AFAIK, even Chrome has disabled most tracking stuff per default
 (except those things which FF/etc. do too).

You may be raising a good point.

As it is now: the first thing firefox seems to do when it's run, is to
connect to search engines and have them set cookies, then, there are
intelligent Bookmarks that connect to aggregators, while no cookie
safe (or cs lite), noscript and better privacy are installed and
set up properly by default. And the website blocking feature even seems
to send URL hashes somewhere by default. The receiver might even not
need to compute that hash himself anymore to join that info into
their database.

I don't know, would that make users look as if they were sold to some
company? They certainly seem exposed to any kind of tracking by
default. 

Would it be a responsible and sane decision for any
distribution to turn that off, while providing simple buttons to allow
things selectively? (i.e. noscript option to enable scripts for
particular sites one want's to use, but not for any goo-analytics
goo-mail, goo-login, goo-website or flashy goo-toolkit someone was
lured to inject into your browser.)

I mean what do you think of a distro when you notice it
started pushing all interactions with its websites to some goo-analytics
tracking?

With so easy to use social network clients ( i.e. with maybe only
freebee fishnet like servers put up centrally, that track any business
and social interactions) installed in a distro, at least you can choose
not to use them.
And you can work on implementing/improving alternative, easy to use
free software tools that function in a distributed, peer based manner to
help people connect in their real social network in more direct ways.

But with browsers and websites set to injecting scripts, you actively
need to turn things off.

I'm really wondering about what you guys think of this.

Kind regards,
Christian


-- 
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/20100525204443.14237bcdc.gatzeme...@tu-bs.de@tu-bs.de

Bug#583151: ITP: geronimo-jpa-2.0-spec -- Geronimo JSR-317 Java Persistence (JPA) 2.0 Spec API

2010-05-25 Thread Miguel Landaeta

Package: wnpp
Severity: wishlist
Owner: Miguel Landaeta mig...@miguel.cc

* Package name: geronimo-jpa-2.0-spec
  Version : 1.1
  Upstream Author : Apache Software Foundation (ASF)
* URL : 
http://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jpa_2.0_spec-1.1/
* License : Apache-2.0
  Programming Lang: Java
  Description : Geronimo JSR-317 Java Persistence (JPA) 2.0 Spec API

  The Java Persistence API is the Java API for the management of persistence and
  object/relational mapping for Java EE and Java SE environments. 
  .
  The goal of this specification is to provide an object/relational mapping
  facility for the Java application developer using a Java domain model
  to manage a relational database.
  .
  Persistence in this context covers three areas:
   - The API itself, defined in the javax.persistence package.
   - The Java Persistence Query Language (JPQL).
   - Object/relational metadata.
  .
  The Java Persistence 2.0 specification addresses improvements in the areas of
  domain modeling, object/relational mapping, EntityManager and Query
  interfaces, and the Java Persistence query language. It adds an API for
  criteria queries, a metamodel API, and support for validation.
  .
  This package contains only API of JSR-317 spec. Apache OpenJPA and Eclipselink
  are implementations of this spec.

This library is needed to package OpenJPA and EclipseLink, which in turn,
they are needed to package Spring Framework 3.0.

-- 
Miguel Landaeta, miguel at miguel.cc
secure email with PGP 0x7D8967E9 available at http://keyserver.pgp.com/
Faith means not wanting to know what is true. -- Nietzsche



-- 
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/20100525192104.ga27...@miguel.cc

Re (3): lilo removal in squeeze (or, please test grub2)

2010-05-25 Thread peasthope

From:   Stephen Powell zlinux...@wowway.com
Date:   Tue, 25 May 2010 11:42:34 -0400 (EDT)
 The backup people are Windows people, and they'd love an
 excuse to complain to management about the backup requirements
 of my Linux servers.

Implies that you don't have responsibility for 
backing the Linux systems.  Too bad; or maybe 
you'd rather not have the extra chore.

Regards,... Peter E.

-- 
Carnot is waiting for a disk replacement; Web pages may not work.
Google pathology workshop.
In ETHNO click here - Desktops.OpenDoc http://carnot.pathology.ubc.ca/.

-- 
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/171056505.51375.497...@cantor.invalid

The story behind UPG and umask.


Hi,
am glad UPGs and the default umask finally got some momentum.

Technical issues below.


For anybody who has any doubt about UPGs or thinks it's insecure, here
is a explanation snippet from [0]:

~
(This should be true, but still needs the fixes from below.)

It is easy for multiple users to collaborate on debian systems.

Just keep in mind that access permission to a file always depends on
the permissions of the file itself AND the permissions of the directory
path to it. By default files are readable for whoever has access to
them, just as paper files are, but not writeable. If you don't want
others to read your files, keep them in a private/ subdirectory. The
path into your home directory is not restricted, just as the path
others can take to ring your bell at home is not restricted. As a
matter of fact you may post some files on your door, for others or to
read. For example many programs read config files that you deposit in
your home path. Besides, other users can drop files (for you
personally) in your ~/incomming/ directory.

All this can work because the primary group of each user is set to a
private user group (UPG) by default. (A group without any mentioned
members in /etc/group, named equal to the user.) This allows to grant
write permissions to created files for the group by default. No one
exept the owning user will be able to write to the file. Exept that is,
if it has been created in a group directory...

Group directories (directories with the set-group-id flag set) are
special places (that again all users are able to visit) where the
members of the group that owns the directory can write files in it.
According to the set-group-id flag files created in the group directory
will belong to the creating user who wrote the file and to the group
*the directory belongs to*. The result is that all members of the group
can work on the files in a groupdir of theirs. Other than that, group
directories work just like home directories. So if a file for example
should be readable only by group members, again put it into a private
subdirectory.

Group directories may be set up by regular users in their home
directories, or by the system administrator or (automatically) by
the addgroup command under /home/group. 
~~



It seems things quite used to work before PAM was introduced while it
didn't support any UPG detection at that time, but now pam_umask is
here to help us out and we get the chance to fix it better then before.


Some additions I'd like to make:


* Things like ssh can and should keep requiring private permissions!
  Instead tools/scripts should be patched to adequately write these
  files with the umask set accordingly. (If they are not already,
  simply by having them manually override the default umask.)


According to [1,2] a UPG is identifiable by

1) A group of the same name as the username

2) A special case is true: The group is set as the main group of the
   user (in /etc/passwd) while the user is NOT added to his group
   in /etc/groups.

3) UID==GID was questioned to be a requrement, probably because it was
   seen that it isn't be enforced, but it can be of great help if you
   are looking at a filesystem (removable drive) without knowing the
   corresponding passwd/groups file.

   So maybe it is sane that UID==GID is a requirement, and its only an
   adduser bug when it does not skip IDs that have been taken by non
   UPG groups when creating users, and thus does not deliver that
   requirement.


With 2) you can still see that the group has been set up as a UPG even
if additional users are added to the group.

Explicitly it allows to detect that:

 A) Those users were added intentionally to the UPG and the umask 
should still be set to 002. (In general you create separate groups
to enable user collaboration on UPG systems, so tools may
very well give a warning/hint about it if you try to add a
user to a UPG.)

 B) The group can be deleted if the user is deleted.


Kind regards,
Christian

[0]https://wiki.ubuntu.com/MultiUserManagement
[1]https://bugs.launchpad.net/gst/+bug/488158
[2]http://lists.alioth.debian.org/pipermail/adduser-devel/2008-February/003161.html


-- 
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/20100525220935.201d11b8c.gatzeme...@tu-bs.de@tu-bs.de

Bug#583157: ITP: haskell-gio -- Binding to the GIO

2010-05-25 Thread Marco Túlio Gontijo e Silva

Package: wnpp
Severity: wishlist
Owner: Marco Túlio Gontijo e Silva mar...@debian.org

* Package name: haskell-gio
  Version : 0.11.0
  Upstream Author : Peter Gavin, Andy Stewart
* URL : http://www.haskell.org/gtk2hs/
* License : GPL
  Programming Lang: Haskell
  Description : Binding to the GIO

 This package provides a library for the Haskell programming language.
 See http://www.haskell.org/ for more information on Haskell.
 .
 GIO is striving to provide a modern, easy-to-use VFS API that sits at the
 right level in the library stack. The goal is to overcome the shortcomings of
 GnomeVFS and provide an API that is so good that developers prefer it over raw
 POSIX calls. Among other things that means using GObject. It also means not
 cloning the POSIX API, but providing higher-level, document-centric
 interfaces.



--
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/20100525201549.10886.93145.report...@zezinho

Re: lilo removal in squeeze (or, please test grub2)

2010-05-25 Thread Joachim Wiedorn

Harald Braumann ha...@unheit.net wrote on Tue, 25 May 2010:
 
 On simple standard system -- one disk, one kernel in /boot, no fancy
 stuff -- it works quite well.

This is enough to use grub2 for new installing of Debian.

 On other systems it often breaks miserably. Updates leave my system
 unbootable every other time. One major problem are incompatible
 versions of the boot loader installed in the MBR and grub.cfg.
 
 Currently, automatic installation of grub in the MBR is a no-go for me,
 because of #554790 but I can't prevent grub from automatically
 updating grub.cfg which leads to incompatible versions, hence an
 unbootable system. 

And these problems say, we still need an alternative - I would say: LiLO.

William Pitcock neno...@dereferenced.org wrote on Sat, 22 May 2010:
 
 After some discussion about lilo on #debian-devel in IRC, it has pretty
 much been determined that kernel sizes have crossed the line past where
 lilo can reliably determine the payload size.

But not all kernels are to large - especially the custom kernels - and
LiLO can be used for this special situation. Until which size of kernel 
is LiLO usable?

My suggestion / recommendation is now:

  a) using grub2 as default boot manager for new installations (d-i)
 and for updating grub.

  b) provide LiLO in squeeze as alternative for grub2. The
 limitations must be said while installing the lilo package.
 I think it must not be a proposal in d-i.

Because I still use LiLO for all my systems, I could support the
maintaining of LiLO. Would this a way for you, William?

Fondest regards,
 Joachim Wiedorn



signature.asc
Description: PGP signature

Re: The story behind UPG and umask.

2010-05-25 Thread Harald Braumann

On Tue, May 25, 2010 at 10:09:35PM +0200, C. Gatzemeier wrote:

 The
 path into your home directory is not restricted, just as the path
 others can take to ring your bell at home is not restricted. 

Depends on adduser settings. Both, world readable and private home
directories are common.

 All this can work because the primary group of each user is set to a
 private user group (UPG) by default. 

This is a bold assumption. In a system where user management is
external (e.g. LDAP), anything is possible and there are no defaults.

 According to [1,2] a UPG is identifiable by

This is wrong. There is no way to differentiate UPG - non-UPG. But I'm
repeating myself ...

Cheers,
harry


-- 
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/20100525204751.gb30...@sbs288.lan

Re: The story behind UPG and umask.

2010-05-25 Thread Michael Banck

On Tue, May 25, 2010 at 10:09:35PM +0200, C. Gatzemeier wrote:
 3) UID==GID was questioned to be a requrement, probably because it was
seen that it isn't be enforced, but it can be of great help if you
are looking at a filesystem (removable drive) without knowing the
corresponding passwd/groups file.
 
So maybe it is sane that UID==GID is a requirement, and its only an
adduser bug when it does not skip IDs that have been taken by non
UPG groups when creating users, and thus does not deliver that
requirement.

I think it is not sane to make this a requirement for UPG, but it would probably
be sufficient proof of UPG.

Seems worthwhile to change adduser how you suggest to me, is there a bug
filed to this end?


Michael


-- 
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/20100525205411.gd27...@nighthawk.chemicalconnection.dyndns.org

RFH: bashisms in configure script

Hi everyone,

dash recently added support for the magic variable $LINENO, which was the last 
piece to make it POSIX compliant. However, this change made the autoconf-
generated configure scripts use dash to execute the script's code. Without 
support for LINENO, configure scripts exec to bash automatically.

With this behaviour change, bashisms in configure scripts are now making 
packages FTBFS[1]. Due to some bugs in checkbashisms, most of the code in 
configure scripts was skipped, making those bashisms invisible.

An archive-wide check of the source packages gives an estimate of over 3425 
source packages with bashisms in *any file*. This doesn't necessarily mean that 
we are drowned by bashisms, as some of those may already be fixed by Debian-
provided packages or might affect unused code (either at the build process or 
code not included in the final binary package.)

A rough estimate of the number of source packages with bashisms in configure 
scripts (false positives included and not necessarily autoconf's configure 
script) is 1504.

SUMMARY:

1. If your name is on the list at [2] please check at [3] the .dsc file that 
corresponds to the source packages you co-/maintain, review and fix.  The .dsc 
files contain checkbashisms' output.
2. Do the same for other packages in the list: review, file report[4], and try 
to provide a patch/NMU.
3. Do the same for other packages in [3] (which are not necessarily in the 
list below): review, file report[4], try to provide a patch/NMU.


Please encourage others to work on these issues.

Normally I would process the results and file the bug reports myself but I 
don't have and won't have time to do it any time soon. I've already tried to 
find some time yesterday and today to work on checkbashisms to come up with bug 
fixes[4], and am probably  going to find a bit more to only fast-process the 
results of a new run against the binary packages.

Thanks in advance!

(before anybody asks/complains, the list of maintainers is too big to be 
attached to the email, even if compressed.)

[1] http://bugs.debian.org/582952
[2] http://people.debian.org/~geissert/source-bashisms/dd-list.txt
[3] http://people.debian.org/~geissert/source-bashisms/
[4] Please set User: debian-rele...@lists.debian.org and Usertags: goal-
dash when filing the report. Severity should be important (or serious if it 
makes the package FTBFS.)
[5] See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497489#13 and 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497489#40

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/201005251613.37139.geiss...@debian.org

Improving in-place upgrades of Ada packages from Lenny to Squeeze

2010-05-25 Thread Ludovic Brenta

Over the last two weeks I have been testing upgrades of Ada packages
from Lenny to Sid and Squeeze in a chroot.  The picture is not as pretty
as it should be.  In a nutshell, when you change /etc/apt/sources.list
from lenny to squeeze (unstable, actually) and do aptitude update, you
end up with a lot of broken packages and must intervene manually to
resolve the problem (i.e. remove the broken packages, install new
versions).

The following packages upgrade seamlessly:

* adabrowse
* adacontrol
* asis-programs
* ghdl
* gnat
* gnat-4.3 deleted, replaced with gnat-4.4
* gnat-gps
* libaws-bin
* libaws-doc
* libgnat{vsn,prj}-dev
* libgnat{vsn,prj}4.3-dev deleted, replaced with gnat{vsn,prj}4.4-dev
* libgtkada2-bin
* libgtkada2-doc

In the case of gnat-4.3 and gnat-4.4, this is because of the gnat
package that selects and depends on the default version of the compiler.

In the case of libgnat{vsn,prj}4.3-dev, this is only because I recently
added dummy transition packages, libgnat{vsn,prj}-dev in gnat-4.4 (=
4.4.4-4).

The following packages upgrade seamlessly but can silently cause
third-party packages to FTBFS; this is a violation of the Debian Policy
for Ada[1]:

* libadasockets-dev (see #580907)

The following packages are obsolete or locally created and marked as
broken by the removal of gnat-4.3:

* libasis-dev  (libasis2008-dev available but not installed)
* libaunit-dev (libaunit1-dev available)
* libaws-dev   (libaws2.7-dev available)
* libflorist-dev   (libflorist2009-dev available)
* libgnademysql-dev(no replacement available)
* libgnadeodbc-dev (libgnadeodbc1-dev available)
* libgnadepostgresql-dev   (no replacement available)
* libgnadesqlite-dev   (libgnadesqlite3-1-dev available)
* libgnomeada2-dev (libgnomeada2.14.2-dev available)
* libtemplates-parser-dev  (libtemplates-parser11.5-dev available)
* libtexttools-dev (libtexttools2-dev available)
* libxmlada-dev(libxmlada3.2-dev available)

The following packages are obsolete or locally created but not marked
as broken (even though they are); in Lenny, they lack a dependency on
gnat-4.3:

* libahven-dev (libahven1-dev available)
* libalog-dev  (libalog1-{base|full}-dev available)
* libopentoken-dev (libopentoken2-dev available)

The reason for all this is that when a package libX2-dev Conflicts: with
and Replaces: a package libX1-dev, aptitude does not remove libX1-dev
and install libX2-dev; instead, it marks libX1-dev as broken and leaves
libX2-dev uninstalled.  As a consequence, upgrades from Lenny to Sid
currently require manual intervention; this precludes unattended
upgrades.  The proper resolution of these dependencies is to remove the
broken packages.  The dependency resolver in aptitude never suggests
that; instead all the solutions I've looked at involved holding the
broken packages in their current state, essentially halting the upgrade.

The reason why all packages must change names is to ensure consistency
of programs at the source and binary level; the rules of the Ada
language guarantee that an executable program always consists of object
files that are consistent both with their sources and with one another.
Full details in [1,2].

Given the constraints that:
(a) all -dev packages must change names due to the above;
(b) we would like to make upgrades as seamless as possible, and even
permit unattended upgrades,

can anyone recommend a way to achieve that goal?

[1] http://people.debian.org/~lbrenta/debian-ada-policy.html
[2] http://www.adaic.com/standards/05rm/html/RM-10-1-4.html, clause 5

-- 
Ludovic Brenta.


-- 
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/87ljb78ysx@ludovic-brenta.org

Re: RFH: bashisms in configure script

2010-05-25 Thread Petter Reinholdtsen

[Raphael Geissert]
 Hi everyone,

 dash recently added support for the magic variable $LINENO, which
 was the last piece to make it POSIX compliant. However, this change
 made the autoconf- generated configure scripts use dash to execute
 the script's code. Without support for LINENO, configure scripts
 exec to bash automatically.

What about reverting this change in dash until after Squeeze is
released?  Now seem like a bad time to make thousand of packages in
Debian fail to build from source. :)

Or perhaps can this feature be made to turn on or off using some 'set'
command, configuration file or command line argument to dash, to allow
us to keep the old behaviour for Squeeze while allowing users to
convert dash to be POSIX compliant locally?

Happy hacking,
-- 
Petter Reinholdtsen


-- 
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/2flpr0jvenf@login2.uio.no

Re: RFH: bashisms in configure script

On Tue, May 25, 2010 at 04:13:36PM -0500, Raphael Geissert wrote:
 [1] http://bugs.debian.org/582952
 [2] http://people.debian.org/~geissert/source-bashisms/dd-list.txt

That is just a list of all packages per person?  It's listing
packages that have no shell script in it at all, and also
don't have a .dsc file.


Kurt


-- 
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/20100525215130.ga19...@roeckx.be

Re: RFH: bashisms in configure script

2010-05-25 Thread Frans Pop

 dash recently added support for the magic variable $LINENO, which was
 the last piece to make it POSIX compliant. However, this change made the
 autoconf- generated configure scripts use dash to execute the script's
 code. Without support for LINENO, configure scripts exec to bash
 automatically.

Isn't it a bit late in the release cycle for a change with such a major 
impact?

 An archive-wide check of the source packages gives an estimate of over
 3425 source packages with bashisms in *any file*.

This and the file under [2] must contain a *huge* amount of false 
positives.

For example, almost all udebs are listed. Why? Because udebs execute 
busybox shell as /bin/sh, which happens to be fairly compatible with bash.

I think this needs to be trimmed quite a bit before it's useful.

Cheers,
FJP


-- 
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/201005252356.00453.elen...@planet.nl

Re: RFH: bashisms in configure script

2010-05-25 Thread Julien Cristau

On Tue, May 25, 2010 at 23:45:56 +0200, Petter Reinholdtsen wrote:

 What about reverting this change in dash until after Squeeze is
 released?  Now seem like a bad time to make thousand of packages in
 Debian fail to build from source. :)
 
That's the plan, see #582952.

Cheers,
Julien


signature.asc
Description: Digital signature

Re: RFH: bashisms in configure script

2010-05-25 Thread Neil Williams

On Tue, 25 May 2010 16:13:36 -0500
Raphael Geissert geiss...@debian.org wrote:

 dash recently added support for the magic variable $LINENO, which was the 
 last 
 piece to make it POSIX compliant. However, this change made the autoconf-
 generated configure scripts use dash to execute the script's code. Without 
 support for LINENO, configure scripts exec to bash automatically.

Can't we just patch this OUT of dash until after the release??? (or
forever? or just on buildd's?)

All this work for ONE VARIABLE???!?!?!

 An archive-wide check of the source packages gives an estimate of over 3425 
 source packages with bashisms in *any file*. This doesn't necessarily mean 
 that 
 we are drowned by bashisms, as some of those may already be fixed by Debian-
 provided packages or might affect unused code (either at the build process or 
 code not included in the final binary package.)

This is just scare mongering - there are packages there which have
nothing to do with autoconf or have any configure script of any kind,
even the simplest perl script packages!

 A rough estimate of the number of source packages with bashisms in configure 
 scripts (false positives included and not necessarily autoconf's configure 
 script) is 1504.

Which, at a rough estimate, would take at least a year to fix, not
including all the transitions that would result.

./configure is a *generated* script too, if dash cannot handle it, dash
has to be crippled to let the other packages continue working. Unless
autoconf itself has already been patched to fix all of these issues when
regenerating ./configure from configure.ac, all this would be a waste
of effort anyway.

This sounds more like a grave bug in dash by breaking everything else.
I can't believe this can happen. It's plain crazy.

 Please encourage others to work on these issues.

Please fix dash instead.
 
 Normally I would process the results and file the bug reports myself but I 
 don't have and won't have time to do it any time soon. I've already tried to 
 find some time yesterday and today to work on checkbashisms to come up with 
 bug 
 fixes[4], and am probably  going to find a bit more to only fast-process the 
 results of a new run against the binary packages.
 
 Thanks in advance!

... for nothing. I'm in no mood to thank anyone for this one.
 
 (before anybody asks/complains, the list of maintainers is too big to be 
 attached to the email, even if compressed.)

Which is reason enough to fix dash, not thousands of other packages
which were fine until this change.

One package (one variable) cannot be allowed to break over a THOUSAND
source packages. 

Has someone put the clock back to 1st April? This just has to be a sick
joke.

Someone please tell me this broken version of dash hasn't been uploaded
yet.

-- 


Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/



pgpZG2uezv6dR.pgp
Description: PGP signature

Re: RFH: bashisms in configure script

On Tue, May 25, 2010 at 11:51:30PM +0200, Kurt Roeckx wrote:
 On Tue, May 25, 2010 at 04:13:36PM -0500, Raphael Geissert wrote:
  [1] http://bugs.debian.org/582952
  [2] http://people.debian.org/~geissert/source-bashisms/dd-list.txt
 
 That is just a list of all packages per person?  It's listing
 packages that have no shell script in it at all, and also
 don't have a .dsc file.

They do contain shell scripts, the maintainer script.  But they
clearly don't generate a warning.


Kurt


-- 
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/20100525220435.ga19...@roeckx.be

Re: RFH: bashisms in configure script

On Tue, May 25, 2010 at 04:13:36PM -0500, Raphael Geissert wrote:
 1. If your name is on the list at [2] please check at [3] the .dsc file that 
 corresponds to the source packages you co-/maintain, review and fix.  The 
 .dsc 
 files contain checkbashisms' output.

I get alot of them that have:
possible bashism in ./configure line 22 ($BASH_SOMETHING):
elif test -n ${BASH_VERSION+set}  (set -o posix) /dev/null 21; then
possible bashism in ./configure line 147 ($BASH_SOMETHING):
 $as_unset BASH_ENV || test ${BASH_ENV+set} != set || { 
BASH_ENV=; export BASH_ENV; }

This is autogenerated code by autoconf (2.59).  I think that code
that makes sure it behaves the way you want under bash isn't
really going to be a problem if you run it with something else.


Kurt


-- 
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/20100525220732.ga19...@roeckx.be

Re: RFH: bashisms in configure script

2010-05-25 Thread Emilio Pozuelo Monfort

On 25/05/10 23:45, Petter Reinholdtsen wrote:
 What about reverting this change in dash until after Squeeze is
 released?  Now seem like a bad time to make thousand of packages in
 Debian fail to build from source. :)

See bug #582952.

Emilio


-- 
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/4bfc465d.1080...@debian.org

Re: RFH: bashisms in configure script

2010-05-25 Thread Neil Williams

On Tue, 25 May 2010 16:13:36 -0500
Raphael Geissert geiss...@debian.org wrote:

A much more sane list is in the bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=45;filename=failed-dash.txt;att=1;bug=582952

124 source packages. Bad, but not as crazy as 1,540.

(I've heard of off-by-one errors but off-by-one-order-of-magnitude is a
stretch.)

Please, let's get some accurate figures before raising things like
this. (Oh, and yes, putting a patched dash into unstable and putting
this broken one into experimental is a VERY good idea IMHO. It's kinda
why we have experimental in the first place. Sheesh! This thing
gonna give me nightmares.)

-- 


Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/



pgpexJad0mjTS.pgp
Description: PGP signature

Re: RFH: bashisms in configure script

2010-05-25 Thread David Weinehall

On Tue, May 25, 2010 at 11:10:10PM +0100, Neil Williams wrote:
On Tue, 25 May 2010 16:13:36 -0500
Raphael Geissert geiss...@debian.org wrote:

A much more sane list is in the bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=45;filename=failed-dash.txt;att=1;bug=582952

124 source packages. Bad, but not as crazy as 1,540.

(I've heard of off-by-one errors but off-by-one-order-of-magnitude is a
stretch.)

Please, let's get some accurate figures before raising things like
this. (Oh, and yes, putting a patched dash into unstable and putting
this broken one into experimental is a VERY good idea IMHO. It's kinda
why we have experimental in the first place. Sheesh! This thing
gonna give me nightmares.)

You're getting things the wrong way around. The version of dash that
will be put in experimental will be the correct one, the one in unstable
will be the crippled one. The reason things fails isn't because of
dash, but because of sloppy programming on behalf of people that still
believe that bash is the say all and end all when it comes to shell
scripts.

Regards: David
--
/) David Weinehall t...@debian.org /) Rime on my window (\
// ~ // Diamond-white roses of fire //
\) http://www.acc.umu.se/~tao/(/ Beautiful hoar-frost (/

--
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/20100525221823.gk24...@test5.acc.umu.se

Re: RFH: bashisms in configure script

On Tue, May 25, 2010 at 04:13:36PM -0500, Raphael Geissert wrote:
 
 1. If your name is on the list at [2] please check at [3] the .dsc file that 
 corresponds to the source packages you co-/maintain, review and fix.  The 
 .dsc 
 files contain checkbashisms' output.

Is there some kind of documentation on what those errors really
mean?


Kurt


-- 
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/20100525222056.ga20...@roeckx.be

Bug#583168: ITP: haskell-hsp -- Haskell library for writing dynamic server-side web pages

2010-05-25 Thread Giovanni Mascellani

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Owner: mascell...@poisson.phc.unipi.it

   Package name: haskell-hsp
Version: 0.5.2
Upstream Author: Joel Bjornson, Niklas Broberg
URL: http://hackage.haskell.org/package/hsp
License: BSD
Description: Haskell library for writing dynamic server-side web pages

Haskell Server Pages (HSP) is an extension of vanilla Haskell, targetted
at the task of writing dynamic server-side web pages. Features include
an embedded XML syntax and a (low-to-mid-level) programming model for
writing dynamic web pages.

Rationale: it is a dependency of happstack (bug #569501).

Regards, Giovanni.
-- 
Giovanni Mascellani mascell...@poisson.phc.unipi.it
Pisa, Italy

Web: http://poisson.phc.unipi.it/~mascellani
Jabber: g.mascell...@jabber.org / giova...@elabor.homelinux.org











signature.asc
Description: OpenPGP digital signature

Re: Bug#581488: general: lower vm.swappiness by default for desktop installations

2010-05-25 Thread Philipp Kern

On 2010-05-25, Aaron Toponce aaron.topo...@gmail.com wrote:
 On 5/12/2010 1:22 PM, Marcus Better wrote:
 Recently I got the advice [1] to set vm.swappiness to 0, rather than
 the default 60. This improved things dramatically. Apparently Eclipse
 is no longer being swapped out preemptively all the time. The
 difference in perceived responsiveness is spectacular.
 You might also be interested in:

 # sync; cat 3  /proc/sys/vm/drop_caches

 This is a nondestructive operation that will drop your clean caches,
 clear up unused inodes, and free up available RAM. Usually, after
 running my desktop for a few hours, depending on the applications I'm
 running as well, this will free up about 1/2 of my installed RAM.

Why would I want to drop my caches?  In fact I even use Tux on Ice for
hibernation so that I can keep my buffer cache, otherwise it takes ages
for the buffer cache to be loaded in after restore...

Kind regards,
Philipp Kern


-- 
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/slrnhvojpr.8ec.tr...@kelgar.0x539.de

Bug#583169: ITP: haskell-sendfile -- Haskell portable sendfile library

2010-05-25 Thread Giovanni Mascellani

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Owner: mascell...@poisson.phc.unipi.it

   Package name: haskell-sendfile
Version: 0.6.1
Upstream Author: Matthew Elder m...@mattelder.org
URL: http://hackage.haskell.org/package/sendfile
License: BSD
Description: Haskell portable sendfile library

This Haskell library exposes zero-copy sendfile functionality in a
portable way. sendfile is a non standard system call that copies data
between one file descriptor and another. This library uses the native
implementations where possible (for example, under Linux or FreeBSD) and
provides an Haskell replacement in other cases, thus providing a
portable interface.

Rationale: it is a dependency of happstack (bug #569501).

Regards, Giovanni.
-- 
Giovanni Mascellani mascell...@poisson.phc.unipi.it
Pisa, Italy

Web: http://poisson.phc.unipi.it/~mascellani
Jabber: g.mascell...@jabber.org / giova...@elabor.homelinux.org













signature.asc
Description: OpenPGP digital signature

Re: The story behind UPG and umask.

2010-05-25 Thread Stephen Gran

This one time, at band camp, Michael Banck said:
 On Tue, May 25, 2010 at 10:09:35PM +0200, C. Gatzemeier wrote:
  3) UID==GID was questioned to be a requrement, probably because it was
 seen that it isn't be enforced, but it can be of great help if you
 are looking at a filesystem (removable drive) without knowing the
 corresponding passwd/groups file.
  
 So maybe it is sane that UID==GID is a requirement, and its only an
 adduser bug when it does not skip IDs that have been taken by non
 UPG groups when creating users, and thus does not deliver that
 requirement.
 
 I think it is not sane to make this a requirement for UPG, but it would 
 probably
 be sufficient proof of UPG.
 
 Seems worthwhile to change adduser how you suggest to me, is there a bug
 filed to this end?

adduser has had bugs filed in the past asking for uid to be equal to gid
by default, and I have so far rejected them as not worth the complexity
for the aesthetic pleasure of having numbers match.  Is there some
problem with username == primary group name?

Cheers,
-- 
 -
|   ,''`.Stephen Gran |
|  : :' :sg...@debian.org |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -


signature.asc
Description: Digital signature

Re: RFH: bashisms in configure script

2010-05-25 Thread Darren Salt

I demand that Kurt Roeckx may or may not have written...

 On Tue, May 25, 2010 at 04:13:36PM -0500, Raphael Geissert wrote:
 1. If your name is on the list at [2] please check at [3] the .dsc file
 that corresponds to the source packages you co-/maintain, review and fix.
 The .dsc files contain checkbashisms' output.

 I get alot of them that have:
 possible bashism in ./configure line 22 ($BASH_SOMETHING):
 elif test -n ${BASH_VERSION+set}  (set -o posix) /dev/null 21; then
 possible bashism in ./configure line 147 ($BASH_SOMETHING):
  $as_unset BASH_ENV || test ${BASH_ENV+set} != set || {
BASH_ENV=; export BASH_ENV; }

 This is autogenerated code by autoconf (2.59).  I think that code that
 makes sure it behaves the way you want under bash isn't really going to be
 a problem if you run it with something else.

I'm seeing only these for gxine, xine-lib and xine-ui, which is slightly odd
because testing with dash has shown up an actual bashism in xine-lib's
configure.ac (which I've just fixed upstream): use of test x == y.

-- 
| Darren Salt| linux at youmustbejoking | nr. Ashington, | Toon
| using Debian GNU/Linux | or ds,demon,co,uk| Northumberland | back!
| + Buy local produce. Try to walk or cycle. TRANSPORT CAUSES GLOBAL WARMING.

This tagline was stolen by the International Brotherhood of Tagline Thieves.


-- 
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/512296bb08%li...@youmustbejoking.demon.co.uk

Bug#583170: ITP: haskell-hsemail -- Haskell parser for email messages and SMTP conversations

2010-05-25 Thread Giovanni Mascellani

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Owner: mascell...@poisson.phc.unipi.it

   Package name: haskell-hsemail
Version: 1.6
Upstream Author: Peter Simons sim...@cryp.to and others
URL: http://hackage.haskell.org/package/hsemail
License: BSD
Description: Haskell parser for email messages and SMTP conversations

This Haskell library is parser for email messages (as described in RFC
2822) and SMTP conversation (as described in RFC 2821).

Rationale: it is a dependency of happstack (bug #569501).

Regards, Giovanni.
-- 
Giovanni Mascellani mascell...@poisson.phc.unipi.it
Pisa, Italy

Web: http://poisson.phc.unipi.it/~mascellani
Jabber: g.mascell...@jabber.org / giova...@elabor.homelinux.org















signature.asc
Description: OpenPGP digital signature

Re: RFH: bashisms in configure script

2010-05-25 Thread Stephen Gran

This one time, at band camp, Kurt Roeckx said:
 On Tue, May 25, 2010 at 04:13:36PM -0500, Raphael Geissert wrote:
  
  1. If your name is on the list at [2] please check at [3] the .dsc file 
  that 
  corresponds to the source packages you co-/maintain, review and fix.  The 
  .dsc 
  files contain checkbashisms' output.
 
 Is there some kind of documentation on what those errors really
 mean?

They largely mean that checkbashisms is an overly blunt tool for the job
at hand.

Cheers,
-- 
 -
|   ,''`.Stephen Gran |
|  : :' :sg...@debian.org |
|  `. `'Debian user, admin, and developer |
|`- http://www.debian.org |
 -


signature.asc
Description: Digital signature

Re: RFH: bashisms in configure script

2010-05-25 Thread Emilio Pozuelo Monfort

On 25/05/10 23:13, Raphael Geissert wrote:
 Normally I would process the results and file the bug reports myself but I 
 don't have and won't have time to do it any time soon. I've already tried to 
 find some time yesterday and today to work on checkbashisms to come up with 
 bug 
 fixes[4], and am probably  going to find a bit more to only fast-process the 
 results of a new run against the binary packages.

It would also be good to build all the archive (or all the affected packages)
with and without LINENO support in dash, and then debdiff'ing them and check if
they are equal or not.

And I've seen configure scripts with the following bashism that checkbashisms
didn't find:

if test x$foo == xyes; then

(== is a bashism, should be =).

Emilio


-- 
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/4bfc50b3.40...@debian.org

Software untuk Toko/Swalayan/Restoran/dll -- Gratis -- Terbatas -- Ayo Cepat Download !!

2010-05-25 Thread PT Asli Indonesia 2

Software AlfaPOS (Point of Sales)

Software AlfaPOS sudah terbukti sukses diimplementasikan diberbagai jenis 
bisnis retail sejak tahun 2006.

Bidang usaha yang wajib menggunakan AlfaPOS :
- Swalayan/Minimarket/Supermarket
- Toko Komputer/HP/Elektronik/Kelontong/ATK/Buku/Fotokopi
- Toko Bangunan/Keramik/Alat Rumah Tangga
- Toko Pakaian/Butik/Distro/Tas/Sepatu/Sandal/Perhiasan/Aksesoris Pria Wanita
- Toko Furniture/Oleh-Oleh/Kue/Merchandise
- Apotek/Bengkel/Dealer Motor/Showroom/Koperasi Karyawan/Cafe/Restoran

Fasilitas dan Keunggulan :
- Front Office : Penjualan Tunai/Kredit, Pembayaran Cicilan Pelanggan, Retur 
Penjualan, Service, dll
- Back Office : Master Data, Pembelian, Inventory, Reporting, Utility Manager, 
dll
- Sistem promosi : 8 macam diskon, voucher belanja, point reward, komisi sales, 
penjadwalan harga jual, dll
- Fasilitas plus : Membership management, multi user, multi cara bayar, AR/AP, 
petty cash
- Sudah teruji sejak tahun 2006 sukses menangani berbagai jenis bisnis
- Layanan support yang baik dari tim yang professional

Alamat Download :
http://alfapos4.ifastnet.com
http://alfapos4.phpnet.us

Bagi yang internetnya agak lambat, kami menyediakan paket CD berisi semua 
installer, ebook manual, video panduan, dll.
Untuk order CD via Pos, silahkan transfer ke BCA, atas nama Fatkul Amri, nomor 
rekening 629-014-6303,
sebesar Rp 50 rb (sdh termasuk paket CD + ongkos kirim). File2 dalam CD kurang 
lebih 500MB.
Setelah transfer, kirim SMS ke 0817-9151-359 dengan menyebutkan nama dan alamat 
lengkap.

Jika perlu informasi dan support, silahkan menghubungi :
- Jakarta, Bpk Toni, (021) 30075400, 0856-4855-3477
- Jakarta, Bpk Toha, (021) 30123430, 8297832, 0817-127-823
- Surabaya, Bpk Zubin, (031) 72794177, 83386707, 0857-3110-8601
- Malang, Bpk Wawan, (0341) 402160, 402168, 0856-4641-4385
- Bali, Bpk Doni, (0361) 7875755
- Balikpapan, Bpk Ghimoyo, (0542) 7000100, 8879990, 0811-598-998


Jika ingin jadi distributor/agen, silahkan hubungi 0817-9155-632.


--
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/alfadev1a79b49cba7bb468083030d58f24de...@alfadev1

Re: RFH: bashisms in configure script

2010-05-25 Thread Peter Samuelson


[Kurt Roeckx]
 I get alot of them that have:
 possible bashism in ./configure line 22 ($BASH_SOMETHING):
 elif test -n ${BASH_VERSION+set}  (set -o posix) /dev/null 21; then
 possible bashism in ./configure line 147 ($BASH_SOMETHING):
  $as_unset BASH_ENV || test ${BASH_ENV+set} != set || { 
 BASH_ENV=; export BASH_ENV; }

And more false positives:

possible bashism in ./configure line 44 ($BASH_SOMETHING):
if test -z $BASH_VERSION$ZSH_VERSION \
 (test X`print -r -- $as_echo` = X$as_echo) 2/dev/null; then
possible bashism in ./configure line 367 (should be word 21):
$as_echo $as_me:${as_lineno-$LINENO}: error: $1 $3

Both were produced by autoconf 2.65.

First is a false positive for the same reason Kurt's example is.
Second is a false positive because $3 in this instance is a numbered
file descriptor.

Peter


-- 
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/20100525230926.gc18...@p12n.org

proper umask default setting / disabling UPGs / release notes / steps to take


The umask used to be (and should be again now) settable
centrally. (/etc/login.defs or /etc/default/login LSB?)

Setting the umask in /etc/profile and multiple other rc
files (instead centrally in login.defs) was only necessary while
pam_umask was not available, and to be depreciated.

All the times since 94'
http://lists.debian.org/msgid-search/m0piquw-0002dgc.ijack...@nyx.cs.du.edu
until PAM was included without support for it, the login package seems
to have done the umask adjustment for UPG users, that pam_umask is
requested to do again, now that it is available.

To disable UPGs you currently need to change two settings, one in
in /etc/login.defs and one in /etc/adduser.conf.


So for a release note draft we can note:

* A link to a (maybe improved version) of the users perspective on
  UPGs. https://wiki.ubuntu.com/MultiUserManagement

* That existing users with UPG will now again get a correct
  UPG-default-umask.

* That since existing users should have been set up with UPGs by the
  debian defaults all the time, this should be no security compromise.

* That a central UMASK setting is now again possible in login.defs that
  can do a much better job than the umask lines in
  existing /etc/profile files etc.

* That all umask settings have to be removed from
  preexisting /etc/profile ~/.bashrc and other shell rc files to take
  advantage from the improvements.

* The option to disabling UPGs alltogether in adduser.conf and
  login.defs.


As for a list of steps to do:

1) remove/comment out any umask settings in all shell configuration
   files shiped in debian (i.e. /etc/profile) and add a comment
   pointing to the right place for the global default umask setting.

   It might be /etc/default/login (LSB?), pam_umask looks at both.

2) Adjust /etc/login.defs:
   Refer to the text from:
   https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/487729)
   
   Correct the comment about USERGROUPS_ENAB (now used by pam_umask).
   
   Or point to /etc/default/login (LSB?), pam_umask looks
   at both.

   UMASK 022 should be set in login.defs or /etc/default/login,
   and pam_umask's usergroups feature should be mentioned in the
   comment.


3) Enable pam_umask by fixing the issues related to the first couple
   of points of the howto at https://wiki.ubuntu.com/MultiUserManagement



If anyone knows where this umask/UPG/multi-user issue is tracked, could
you please add this accordingly?

Kind regards,
Christian


-- 
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/20100526012624.3b063ed1c.gatzeme...@tu-bs.de@tu-bs.de

Re: The story behind UPG and umask.

2010-05-25 Thread Steve Langasek

On Tue, May 25, 2010 at 11:30:49PM +0100, Stephen Gran wrote:
 This one time, at band camp, Michael Banck said:
  On Tue, May 25, 2010 at 10:09:35PM +0200, C. Gatzemeier wrote:
   3) UID==GID was questioned to be a requrement, probably because it was
  seen that it isn't be enforced, but it can be of great help if you
  are looking at a filesystem (removable drive) without knowing the
  corresponding passwd/groups file.

  So maybe it is sane that UID==GID is a requirement, and its only an
  adduser bug when it does not skip IDs that have been taken by non
  UPG groups when creating users, and thus does not deliver that
  requirement.

  I think it is not sane to make this a requirement for UPG, but it would 
  probably
  be sufficient proof of UPG.

  Seems worthwhile to change adduser how you suggest to me, is there a bug
  filed to this end?

 adduser has had bugs filed in the past asking for uid to be equal to gid
 by default, and I have so far rejected them as not worth the complexity
 for the aesthetic pleasure of having numbers match.  Is there some
 problem with username == primary group name?

pam_umask requires both username == primary group name and uid == gid before
it will assume UPG are in place when using its 'usergroups' option, and I am
not willing to diverge from upstream on this as this would mean admins
coming from other systems may get an unpleasant surprise when they find that
Debian gives a more relaxed umask than they were expecting in some corner
cases.

So either someone should convince Linux-PAM upstream to change the behavior
of pam_umask, or adduser should enforce the same rules as other
implementations, if pam_umask is to be involved here.  Beyond that, I have
no particular opinion on this question.

Cheers,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100525234321.ga16...@dario.dodds.net

Re: Re (2): lilo removal in squeeze (or, please test grub2)

2010-05-25 Thread owens

 Original Message 
From: zlinux...@wowway.com
To: debian-devel@lists.debian.org, debian-u...@lists.debian.org,
debian-b...@lists.debian.org
Subject: Re: Re (2): lilo removal in squeeze (or, please test
grub2)
Date: Tue, 25 May 2010 13:00:45 -0400 (EDT)

On Tue, 25 May 2010 11:51:11 -0400 (EDT), Mark mamar...@gmail.com
 On Tue, May 25, 2010 at 8:42 AM, Stephen Powell
zlinux...@wowway.comwrote:
 On Mon, 24 May 2010 17:29:54 -0400 (EDT), Peter Easthope wrote:
 Stephen Powell wrote:
 (3) The need for special backup requirements will be
 used by the opponents of Linux at my place of employment
 to oppose further deployments of Linux, ...

 What about the carrot approach?  Find an even better
 backup method, compatible with Grub 2 and appealing
 to your management for its efficiency.

 You're missing the point.  The main selling point to management
 is that Linux is free.  ...

 Clonezilla is free, and when using the saveparts option to save
an image
 of one partition and not the full hard drive, it includes the MBR
and
 associated data.  You can then drop that partition image onto a
new/blank
 disk, that does not have anything in the MBR, and once Clonezilla
restores
 the image to the new partition, will put the MBR in place and the
machine
 boots on its own the next time, with no extra work (I just did
this last
 week with a new hard drive).  This has been my experience with
using
 Clonezilla and Lenny, at least.  So it may help in your case.

Perhaps so.  But it's not what the backup people know.  They're very
comfortable with the backup software that they know and love for
backing up their Windows servers, which was purchased with Windows
servers
in mind.  Do you think they're going to redo their whole backup
architecture
just for a few Linux servers?  If I want to play in their sandbox, I
have
to play by their rules.  That's the political reality.  At our shop,
Linux
has a small beachhead on a vast continent controlled by Windows. 
Over time,
the role of Linux may expand to the point where Linux is actually
thought
about and planned for when decisions are made.  But that day is not
today.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-

+1
I have been where Steven is and agree with his approach.
Larry
-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org
Archive: http://lists.debian.org/479605722.42620.1274806845480.JavaM
ail.r...@md01.wow.synacor.com

--
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/380-220105225234210...@netptc.net

Re: RFH: bashisms in configure script

Kurt Roeckx wrote:

 On Tue, May 25, 2010 at 11:51:30PM +0200, Kurt Roeckx wrote:
 On Tue, May 25, 2010 at 04:13:36PM -0500, Raphael Geissert wrote:
  [1] http://bugs.debian.org/582952
  [2] http://people.debian.org/~geissert/source-bashisms/dd-list.txt
 
 That is just a list of all packages per person?  It's listing
 packages that have no shell script in it at all, and also
 don't have a .dsc file.
 
 They do contain shell scripts, the maintainer script.  But they
 clearly don't generate a warning.

I accidentally screwed the call to dd-list(1) and I made it list all the 
maintainers of every package in the archive. I've fixed it already some 
hours ago.

The .dsc files are at:
 http://people.debian.org/~geissert/source-bashisms/

(there's a sub-directory called 'empty' that has all the, empty, .dsc 
files.)

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/hthpu6$vt...@dough.gmane.org

Re: RFH: bashisms in configure script

Neil Williams wrote:

 On Tue, 25 May 2010 16:13:36 -0500
 Raphael Geissert geiss...@debian.org wrote:
 
 dash recently added support for the magic variable $LINENO, which was the
 last piece to make it POSIX compliant. However, this change made the
 autoconf- generated configure scripts use dash to execute the script's
 code. Without support for LINENO, configure scripts exec to bash
 automatically.
 
 Can't we just patch this OUT of dash until after the release??? (or
 forever? or just on buildd's?)

The plan for now is to disable support for LINENO, as mentioned in the br.

 
 All this work for ONE VARIABLE???!?!?!

POSIX compliance too.

 
 An archive-wide check of the source packages gives an estimate of over
 3425 source packages with bashisms in *any file*. This doesn't
 necessarily mean that we are drowned by bashisms, as some of those may
 already be fixed by Debian- provided packages or might affect unused code
 (either at the build process or code not included in the final binary
 package.)
 
 This is just scare mongering - there are packages there which have
 nothing to do with autoconf or have any configure script of any kind,
 even the simplest perl script packages!
 

The dd-list was bogus and I fixed it already. The .dsc files in the 
directory did not change, however.

 ./configure is a *generated* script too, if dash cannot handle it, dash
 has to be crippled to let the other packages continue working. Unless
 autoconf itself has already been patched to fix all of these issues when
 regenerating ./configure from configure.ac, all this would be a waste
 of effort anyway.

It is not about whether dash can handle it or not. The bashisms don't come 
from autoconf, the come from what the author's added to configure.in{,.in}.

 Someone please tell me this broken version of dash hasn't been uploaded
 yet.

dash isn't broken. It is in testing already.

Regards,
-- 
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/hthqbf$1n...@dough.gmane.org

Re: The story behind UPG and umask.


Am Tue, 25 May 2010 22:47:51 +0200
schrieb Harald Braumann ha...@unheit.net:

 On Tue, May 25, 2010 at 10:09:35PM +0200, C. Gatzemeier wrote:
 
  The
  path into your home directory is not restricted, just as the path
  others can take to ring your bell at home is not restricted. 
 
 Depends on adduser settings. Both, world readable and private home
 directories are common.

Thanks! Adding ...the path to your home *is by default* not
restricted,... seems to be more precise.


 
  All this can work because the primary group of each user is set to a
  private user group (UPG) by default. 
 
 This is a bold assumption. In a system where user management is
 external (e.g. LDAP), anything is possible and there are no defaults.

We were just stating different assumptions, yes. Maybe also
adding ...this can work in a default installation because...?

 
  According to [1,2] a UPG is identifiable by
 
 This is wrong. There is no way to differentiate UPG - non-UPG. But I'm
 repeating myself ...

I've gone though your related posts that I found on the web. (Wasn't
subscribed before, so answering here.)

OK, the definitionn is wrong, or not complete, in the sense that it does
not catch all possible UPGs.

The auto-umask adjusing feature won't work for all possible UPG
implementations, but it should work safely for the default debian
installation, without compromising security in other environments.

So yes, you can setup UPGs with UID!=GID, but then you'll also
have to set the umask manually to make it work (globally or in gecos or
ldap etc.).

The UID==GID and username==groupname restriction of the
pam_umask's usergroups option ensures that the umask is only relaxed
automatically in very specific defined cases.

That's why I'am thinking the UID==GID restriction pam_umask makes (and
login made before) can be sane choice. (Others seem to use it also,
and it is upstream.)

The mentioned three points of the current implementation I found on the
web even allow intentional addititions of users to the UPG as a quick
way to set up trusted (sub-)users without requiring extra groups and
groupdirs to work with files in your sub-user's account. And it allows
proper removal of a UPG together with the user, if it is unused.

 Let me quote from the comments in /etc/login.defs:

 #UMASK 022 is the historical value in Debian for UMASK when it was
 used

Right, that UMASK value was commented out when it needed to be
dispersed into shell rc files, due to PAM not supporting usergroups
yet.

And below that comes USERGROUPS_ENAB yes which also
historicaly did adjust the umask for UPG users. 

Of course we agree that UPGs and all related automatic umask adjustment
should be configurable, i.e. they can be disabled.

Cheers,
Christian


-- 
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/20100526023653.46c6bc5cc.gatzeme...@tu-bs.de@tu-bs.de

Re: RFH: bashisms in configure script

Darren Salt wrote:

 I demand that Kurt Roeckx may or may not have written...
 
 On Tue, May 25, 2010 at 04:13:36PM -0500, Raphael Geissert wrote:
 1. If your name is on the list at [2] please check at [3] the .dsc file
 that corresponds to the source packages you co-/maintain, review and
 fix. The .dsc files contain checkbashisms' output.
 
 I get alot of them that have:
 possible bashism in ./configure line 22 ($BASH_SOMETHING):
 elif test -n ${BASH_VERSION+set}  (set -o posix) /dev/null 21;
 then possible bashism in ./configure line 147 ($BASH_SOMETHING):
  $as_unset BASH_ENV || test ${BASH_ENV+set} != set || {
 BASH_ENV=; export BASH_ENV; }

Yes, $BASH_SOMETHING is just used to make it easier to see that the 
following code (probably a bashism) is only executed after checking the 
shell is actually bash. That and the other FP are the most common ones, yet 
not that easy to fix (the latter, of course, the former is not a FP.)

 I'm seeing only these for gxine, xine-lib and xine-ui, which is slightly
 odd because testing with dash has shown up an actual bashism in xine-lib's
 configure.ac (which I've just fixed upstream): use of test x == y.

Could you please send me by email the files with false negatives? those are 
very likely bugs in checkbashisms' quotes handling code.

Thanks.

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/hthqk6$1n...@dough.gmane.org

Re: RFH: bashisms in configure script

Kurt Roeckx wrote:

 On Tue, May 25, 2010 at 04:13:36PM -0500, Raphael Geissert wrote:
 
 1. If your name is on the list at [2] please check at [3] the .dsc file
 that
 corresponds to the source packages you co-/maintain, review and fix.  The
 .dsc files contain checkbashisms' output.
 
 Is there some kind of documentation on what those errors really
 mean?
 

Yes, most are documented at the following page. I'm going to add more info 
about recently-added and some undocumented checks in a moment.

https://wiki.ubuntu.com/DashAsBinSh

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/hthqtn$1n...@dough.gmane.org

Re: The story behind UPG and umask.

Am Tue, 25 May 2010 23:30:49 +0100
schrieb Stephen Gran sg...@debian.org:

 adduser has had bugs filed in the past asking for uid to be equal to
 gid by default, and I have so far rejected them as not worth the
 complexity for the aesthetic pleasure of having numbers match.  Is
 there some problem with username == primary group name?

I think ensuring UID==GID by default allows having
automatic umask relaxation for UPGs to work and not 
compromising security, even in corner cases when the system is setup in
other environments. Besides making UPGs and permissions more cleanly
visible/detectable/adjustable on removable filesystems or tarballs
(where you can only see numerical IDs).

Cheers,
Christian


-- 
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/20100526024848.3e6888dec.gatzeme...@tu-bs.de@tu-bs.de

Re: RFH: bashisms in configure script

Emilio Pozuelo Monfort wrote:
 It would also be good to build all the archive (or all the affected
 packages) with and without LINENO support in dash, and then debdiff'ing
 them and check if they are equal or not.

A full archive rebuild was already done by Lucas (see the br against dash 
for details.)
One with a version of dash without support for LINENO is useless, as that's 
what it used to be.

 And I've seen configure scripts with the following bashism that
 checkbashisms didn't find:
 
 if test x$foo == xyes; then
 
 (== is a bashism, should be =).

Please send me those configure scripts by email (preferably adding a comment 
at the end of the same line that says BASHISM, so that I can just inject it 
into my testsuite.)

Thanks.

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/hthqr9$1n...@dough.gmane.org

Re: RFH: bashisms in configure script

Hi,

Given the recent responses I'm providing some more info, updates, and hints.

Raphael Geissert wrote:
 This doesn't necessarily mean that we are drowned by bashisms, as some of
 those may already be fixed by Debian- provided packages or might affect
 unused code

s/packages/patches/

 (before anybody asks/complains, the list of maintainers is too big to be
 attached to the email, even if compressed.)

If you were one of those who checked the dd-list.txt file right after I sent 
my original email and up to two hours later, please re-check it. It was 
bogus.

dd-list.txt *only* contains the list of maintainers/packages with bashisms 
in a 'configure' script. A new list for maintainers/packages with any kind 
of bashism (or false positive) in any file can now be found at:

Information about bashisms (how to fix them) and how to understand 
checkbashisms' output can be found at:

https://wiki.ubuntu.com/DashAsBinSh

* Common false positive:

---
possible bashism in ./configure line nnn (should be word 21):
$as_echo $as_me:${as_lineno-$LINENO}: error: $1 $3
---

This one is safe. It is generated by autoconf and $3 points to a numeric 
file descriptor.

---
some sort of detection in *.diff or *.dpatch files
---
In this case those files use a shell wrapper that executes another program 
to process the file. checkbashisms attempts to detect them, but it fails in 
some cases.

---
unsafe echo with backslash:
---
If the output of echo is piped to grep, verified with test/[ or case; in 
most cases it is just some shell code that is used to determine whether the 
echo command expands backlashes by default.


* Not false positives, just indicators[1], but common too:
$BASH
RANDOM=
(OS|MACH)TYPE=
HOST(TYPE|NAME)=
BASH(_SOMETHING)=

[1] they help identify shell tests.


Yes, I'm aware of the high number of false positives and indicators noise. 
There are some false negatives too.

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/hthsoh$7u...@dough.gmane.org

Re: Bug#582831: ITP: png2ico -- png2ico converts PNG files to Windows icon resource files.

2010-05-25 Thread Guillem Jover

Hi!

On Sun, 2010-05-23 at 18:38:26 -0500, Chris Silva wrote:
 Package: wnpp
 Severity: wishlist
 Owner: Chris Silva rac...@makeworld.com
 
 
 * Package name: png2ico
   Version : 12.08.02-1
   Upstream Author : Matthias S. Benkmann matth...@winterdrache.de
 * URL : http://www.winterdrache.de/freeware/png2ico/
 * License : GPL-2
   Programming Lang: G++
   Description : png2ico converts PNG files to Windows icon resource files.
 
 png2ico takes the input files and stores them in the out
 put file as a Windows icon resource. Usually the input
 files would all represent the same image in different
 resolutions (common resolutions are 16x16, 32x32 and 64x64).
 A program reading the icon resource will pick the image
 closest to its desired resolution and will then scale it
 if necessary.

Are you aware of icoutils, which is already in the archive? Is there
anything png2ico can do which icoutils cannot? And in that case
couldn't that be added to icoutils instead, to avoid adding more of
the same to the archive?

regards,
guillem


-- 
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/20100526014640.gc4...@gaara.hadrons.org

Re: lilo removal in squeeze (or, please test grub2)

On Tue, 25 May 2010 11:10:38 -0400 (EDT), Ferenc Wagner wrote:
 Stephen Powell wrote:
 ... I installed the mbr package ...
 
 The extlinux package itself also contains an mbr.bin, which you can use
 (it's strong point is probably EBIOS support).

So it does.  Well, I've now installed extlinux' version
of mbr.bin to the master boot record and purged the mbr package.
extlinux' built-in version of a master boot record boot loader works great.

 Speaking of documentation, that seems to be its main weakness.
 Documentation is sketchy and spread out over a number of different files.
 
 /usr/share/doc/extlinux.txt.gz references syslinux.txt, which is fairly
 comprehensive according to my standards, at least as far as the core is
 concerned.  What did you miss?  Some modules may be less well documented.

Yes, I found those two files.  Reference documentation for each specific
boot loader option is there, but what is lacking is tutorial-type stuff.
For example, there is a global options section at the beginning that applies
to all bootable images, and there are options which are specific to each
boot image.  I guessed at that mainly based on how /etc/lilo.conf works,
but I'm not sure it was directly stated anywhere.  It may be hinted at
in the description of some individual configuration option but not explained
up front.  Also, there's no example configuration file.  There are little
pieces of configuration files but no complete typical configuration file.
A picture is worth a thousand words.

 It installs hook scripts that I don't want (and that have bugs).
 
 I hope we can fix them soon (they are Debian specific additions).

Remember, I'm used to using lilo.  And based on analogies with lilo,
I built a /boot/extlinux/extlinux.conf file that looks like this:

-

DEFAULT Linux
APPEND root=/dev/sda2 ro vga=779
TIMEOUT 50
PROMPT 1
LABEL Linux
KERNEL ../vmlinuz
INITRD ../initrd.img
LABEL LinuxOLD
KERNEL ../vmlinuz.old
INITRD ../initrd.img.old

-

The kernel and initial RAM disk images are specified via the
traditional symlinks.  As long as the symlinks are maintained
properly, my config file never needs updating, just like lilo's.
Consequently, I really don't want the extlinux hook scripts to
execute at all when I install or remove a kernel.  I solved that
temporarily by issuing

   chmod -x /etc/kernel/postinst.d/extlinux
   chmod -x /etc/kernel/postrm.d/extlinux

That works for now; but if a package upgrade for extlinux is ever
downloaded, I'm afraid that new versions of the hook scripts will
be copied into these directories which are marked executable, and
my hand-made configuration file will get wiped out.  I would suggest
testing the existence of some flag file.  If the flag file exists,
then invoking update-extlinux should be bypassed.  Thus, if the user
doesn't want his hand-made /boot/extlinux/extlinux.conf file to be
tampered with, he can create that flag file via touch and the hook
script will not run update-extlinux.  Strictly speaking, this is
an enhancement request.

Second, it is important that any script run as a hook script not
produce any output at all to standard output.  I found that out the
hard way when I was writing my own hook scripts for use with lilo.
That's because they run under debconf, which has redirected standard
output for its own purposes.  Thus, anything written to standard
output is (1) never seen by the user and (2) has a good chance of
messing up debconf, which is examining the output.  The invocation
of update-extlinux should have a redirection on it to redirect
output to standard error.  For example,

   update-extlinux 2

This is a bona-fide bug.

-- 
  .''`. Stephen Powell
 : :'  :
 `. `'`
   `-


-- 
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/630546796.56099.1274837814099.javamail.r...@md01.wow.synacor.com

Re: Bug#582831: ITP: png2ico -- png2ico converts PNG files to Windows icon resource files.

2010-05-25 Thread Chris

On Wed, 26 May 2010 03:46:40 +0200
Guillem Jover guil...@debian.org wrote:

 Hi!
 
 On Sun, 2010-05-23 at 18:38:26 -0500, Chris Silva wrote:
  Package: wnpp
  Severity: wishlist
  Owner: Chris Silva rac...@makeworld.com
  
  
  * Package name: png2ico
Version : 12.08.02-1
Upstream Author : Matthias S. Benkmann matth...@winterdrache.de
  * URL : http://www.winterdrache.de/freeware/png2ico/
  * License : GPL-2
Programming Lang: G++
Description : png2ico converts PNG files to Windows icon
  resource files.
  
  png2ico takes the input files and stores them in the out
  put file as a Windows icon resource. Usually the input
  files would all represent the same image in different
  resolutions (common resolutions are 16x16, 32x32 and 64x64).
  A program reading the icon resource will pick the image
  closest to its desired resolution and will then scale it
  if necessary.
 
 Are you aware of icoutils, which is already in the archive? Is there
 anything png2ico can do which icoutils cannot? And in that case
 couldn't that be added to icoutils instead, to avoid adding more of
 the same to the archive?
 
 regards,
 guillem
 
 
 


Guillem - 

Thanks for the heads-up! I'll take a look over the weekend at it.

-- 
Regards,

Chris


-- 
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/20100525205517.7af44...@makeworld.com

Re: lilo removal in squeeze (or, please test grub2)

2010-05-25 Thread Daniel Baumann

On 05/26/2010 03:36 AM, Stephen Powell wrote:
 That works for now; but if a package upgrade for extlinux is ever
 downloaded, I'm afraid that new versions of the hook scripts will
 be copied into these directories which are marked executable, and
 my hand-made configuration file will get wiped out.  I would suggest
 testing the existence of some flag file.  If the flag file exists,
 then invoking update-extlinux should be bypassed.  Thus, if the user
 doesn't want his hand-made /boot/extlinux/extlinux.conf file to be
 tampered with, he can create that flag file via touch and the hook
 script will not run update-extlinux.  Strictly speaking, this is
 an enhancement request.

as of current git, you can now use EXTLINUX_UPDATE=false in
/etc/default/extlinux to prevent having update-extlinux do anything.

 Second, it is important that any script run as a hook script not
 produce any output at all to standard output.  I found that out the
 hard way when I was writing my own hook scripts for use with lilo.
 That's because they run under debconf, which has redirected standard
 output for its own purposes.  Thus, anything written to standard
 output is (1) never seen by the user and (2) has a good chance of
 messing up debconf, which is examining the output.  The invocation
 of update-extlinux should have a redirection on it to redirect
 output to standard error.  For example,
 
update-extlinux 2

none of the hooks is doing this (initramfs-tools, grub, etc), might
needs further convincing.

-- 
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:  daniel.baum...@panthera-systems.net
Internet:   http://people.panthera-systems.net/~daniel-baumann/


-- 
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/4bfca228.5000...@debian.org

Accepted lifelines 3.0.61-1.1 (source all i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 02 May 2010 17:50:26 +0300
Source: lifelines
Binary: lifelines lifelines-doc lifelines-doc-sv lifelines-reports
Architecture: source all i386
Version: 3.0.61-1.1
Distribution: unstable
Urgency: low
Maintainer: Felipe Augusto van de Wiel (faw) f...@debian.org
Changed-By: Jari Aalto jari.aa...@cante.net
Description: 
 lifelines  - text-based genealogy software
 lifelines-doc - documentation for lifelines, a genealogy software system
 lifelines-doc-sv - swedish documentation for lifelines, a genealogy software 
system
 lifelines-reports - reports for lifelines, a genealogy software system
Closes: 575853
Changes: 
 lifelines (3.0.61-1.1) unstable; urgency=low
 .
   * Non-maintainer upload.
 - New upstream release.
   * debian/chnagelog
 - Remove obsolete Emacs variables from end of file.
   * debian/control
 - (Build-Depends): update obsolete gs to ghostscript.
   (important; Closes: #575853).
Checksums-Sha1: 
 28d8d79a282ed84a53b40785b21e04c5129e8d4c 1244 lifelines_3.0.61-1.1.dsc
 a23104d6a15d00fe1a496af4727bdb50803550fd 32035 lifelines_3.0.61-1.1.diff.gz
 28150e30621c3820edbaeeaafafe59a78d59a777 896424 
lifelines-doc_3.0.61-1.1_all.deb
 d1acd0a6c7e0d4d00d4e67cb868ef391f0b11212 182392 
lifelines-doc-sv_3.0.61-1.1_all.deb
 18d276d75d40daf84c03c2a6cc3b4a737539caec 697168 
lifelines-reports_3.0.61-1.1_all.deb
 7875352347adc54e2718504d2653133f87708acb 991682 lifelines_3.0.61-1.1_i386.deb
Checksums-Sha256: 
 be0a5c53e6a3c6e5d3e86e63310164280bb1c0db6b5c5792b248938110562499 1244 
lifelines_3.0.61-1.1.dsc
 44bba17ee846d3bd238639b5187ef1e2af6cca4d7a896e14d9e6fa5f7ae1d511 32035 
lifelines_3.0.61-1.1.diff.gz
 05e36b15901e02cc486c542a1a594c51d535744ede3c8498f0d3d80b71624070 896424 
lifelines-doc_3.0.61-1.1_all.deb
 02b6e8a5a534af75ca281505272c5124c7779ea207997121e2c460100c79f625 182392 
lifelines-doc-sv_3.0.61-1.1_all.deb
 0ae158c32b761849d1839f5fd2e178f36a2d83605b47768e7c46c8620d5ece43 697168 
lifelines-reports_3.0.61-1.1_all.deb
 09bc37fe2f4b4b032566b17a78314d631cf402bf905d966211ce0ff092997fa1 991682 
lifelines_3.0.61-1.1_i386.deb
Files: 
 6c6ee74c3f83e7e640d4ae30a11bf8da 1244 misc optional lifelines_3.0.61-1.1.dsc
 aad6d2ec133dc5c4eed7aa29a03ed878 32035 misc optional 
lifelines_3.0.61-1.1.diff.gz
 bc49727309e983488cbc28d7afffd178 896424 doc optional 
lifelines-doc_3.0.61-1.1_all.deb
 1a02d890985aff781cd9e43a96648bcf 182392 doc optional 
lifelines-doc-sv_3.0.61-1.1_all.deb
 5b172192679db570d3e509a5b25cc20c 697168 misc optional 
lifelines-reports_3.0.61-1.1_all.deb
 204d744367f97012f87d4f74f6e3871a 991682 misc optional 
lifelines_3.0.61-1.1_i386.deb

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

iEYEARECAAYFAkvuLJMACgkQpdwBkPlyvgMUdQCdEU/TGLkHeQdRk3AzpPzX+cl5
YOAAn3sL7SnjC5D6bV4La6Tl+oNF7N7a
=zcNJ
-END PGP SIGNATURE-


Accepted:
lifelines-doc-sv_3.0.61-1.1_all.deb
  to main/l/lifelines/lifelines-doc-sv_3.0.61-1.1_all.deb
lifelines-doc_3.0.61-1.1_all.deb
  to main/l/lifelines/lifelines-doc_3.0.61-1.1_all.deb
lifelines-reports_3.0.61-1.1_all.deb
  to main/l/lifelines/lifelines-reports_3.0.61-1.1_all.deb
lifelines_3.0.61-1.1.diff.gz
  to main/l/lifelines/lifelines_3.0.61-1.1.diff.gz
lifelines_3.0.61-1.1.dsc
  to main/l/lifelines/lifelines_3.0.61-1.1.dsc
lifelines_3.0.61-1.1_i386.deb
  to main/l/lifelines/lifelines_3.0.61-1.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/e1ogndr-0004jz...@ries.debian.org

Accepted tightvnc 1.3.9-6.1 (source i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 13 May 2010 11:02:08 +0300
Source: tightvnc
Binary: tightvncserver xtightvncviewer
Architecture: source i386
Version: 1.3.9-6.1
Distribution: unstable
Urgency: low
Maintainer: Ola Lundqvist o...@debian.org
Changed-By: Jari Aalto jari.aa...@cante.net
Description: 
 tightvncserver - virtual network computing server software
 xtightvncviewer - virtual network computing client software for X
Closes: 575865
Changes: 
 tightvnc (1.3.9-6.1) unstable; urgency=low
 .
   * Non-maintainer upload.
 - Update to packaging format 3.0 (quilt).
   * debian/compat
 - Update to 7.
   * debian/control
 - (Build-Depends): Update xutils to xutils-dev (important;
   Closes: #575865). Update to debhelper 7.1. Remove obsolete x-dev.
 - (Depends): Add ${misc:Depends}.
 - (Homepage): New field.
 - (Standards-Version): Update to 3.8.4.
 - (tightvncserver::Depends): Replace obsolete xbase-clients with
   x11-utils and xauth. The needed binaries xdpyinfo and xauth
   are used in Perl program /usr/bin/tightvncserver.
   * debian/copyright
 - Point to GPL-2.
   * debian/patches
 - (10, 20): Add new patches.
 - (30): Convert original MIPS patch to apply to current sources.
 - (tightvnc-ftbfs-mips.patch): Removed. See 30.
* debian/*.{postrm,prerm}
 - Add set -e.
 - Fix Lintian maintainer-script-without-set-e.
   * debian/rules
 - (CC): Add. Export variable for xmkmf(1).
 - (DH_COMPAT): Delete; use debian/compat.
 - (install): Correct tightvncpasswd.1x to tightvncpasswd.1.
 - (binary-arch): Remove empty directories.
   * debian/source/format
 - New file.
   * debian/watch
 - New file.
   * debian/tightvncserver.doc-base
 - New file.
   * debian/xtightvncviewer.menu
 - (section): Update obsolete Apps/Net to
   Applications/Network/Communication.
Checksums-Sha1: 
 5f36cc2c5a75af4816efa30b8c4ceca36c579dfe 1249 tightvnc_1.3.9-6.1.dsc
 27b049254abc5bab8326b3ac727179753ce41555 65709 tightvnc_1.3.9-6.1.debian.tar.gz
 08b5b18f4b47ce5e38a6531c81efa258c6fbbf4b 761610 
tightvncserver_1.3.9-6.1_i386.deb
 052d40f3af237a87ec3956a509aef9ea4a06b0f7 88712 
xtightvncviewer_1.3.9-6.1_i386.deb
Checksums-Sha256: 
 fe429db2ba08b3e090198863ac0478c04ca78f503b524e8c72f8af0aa1dd5bce 1249 
tightvnc_1.3.9-6.1.dsc
 3316ba3fb54a4e4ee65e9edd0e212be8ba2c85c7bf8abc7fa7703a188d17e899 65709 
tightvnc_1.3.9-6.1.debian.tar.gz
 22b0c7010f9f8ea46dca1a30e8749057df97f7ca060fcce506ef3e0c4df054da 761610 
tightvncserver_1.3.9-6.1_i386.deb
 3f24d6b4c8915c64092296ec9ed3720a26dd56753d917830c2b9050b595b9a01 88712 
xtightvncviewer_1.3.9-6.1_i386.deb
Files: 
 0f03217faecdc8520400a1ef8761b588 1249 x11 optional tightvnc_1.3.9-6.1.dsc
 6b327f4b4fa75c25ceb05cb3f328425a 65709 x11 optional 
tightvnc_1.3.9-6.1.debian.tar.gz
 765c57a548911f29479608e667bd7b7f 761610 x11 optional 
tightvncserver_1.3.9-6.1_i386.deb
 9d09fc9725a87c96bba2a2db7968818b 88712 x11 optional 
xtightvncviewer_1.3.9-6.1_i386.deb

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

iEYEARECAAYFAkvuLbYACgkQpdwBkPlyvgO0BACfUm7Nuoa8+t7oCYlo8tTI7Shy
zuAAnRHrL+H0qWWF+j6Fk34nr1NAHMTd
=sXBZ
-END PGP SIGNATURE-


Accepted:
tightvnc_1.3.9-6.1.debian.tar.gz
  to main/t/tightvnc/tightvnc_1.3.9-6.1.debian.tar.gz
tightvnc_1.3.9-6.1.dsc
  to main/t/tightvnc/tightvnc_1.3.9-6.1.dsc
tightvncserver_1.3.9-6.1_i386.deb
  to main/t/tightvnc/tightvncserver_1.3.9-6.1_i386.deb
xtightvncviewer_1.3.9-6.1_i386.deb
  to main/t/tightvnc/xtightvncviewer_1.3.9-6.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/e1ogndr-0004sw...@ries.debian.org

Accepted debian-zh-faq 1.11+nmu1 (source all)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sat, 08 May 2010 22:13:12 +0300
Source: debian-zh-faq
Binary: debian-zh-faq-s debian-zh-faq-t
Architecture: source all
Version: 1.11+nmu1
Distribution: unstable
Urgency: low
Maintainer: Yu Guanghui y...@debian.org
Changed-By: Jari Aalto jari.aa...@cante.net
Description: 
 debian-zh-faq-s - Debian Chinese FAQ (Chinese GB)
 debian-zh-faq-t - Debian Chinese FAQ (Chinese Big5)
Closes: 575617
Changes: 
 debian-zh-faq (1.11+nmu1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * debian/changelog
 - Remove obsolete Emacs local variables.
 - Move to packaging format 3.0 (native).
   * debian/chnagelog
 - Delete EOL whitespaces.
   * debian/compat
 - New file.
   * debian/control
 - (Build-Depends): update obsolete gs to ghostscript.
   (important; Closes: #575617).
   Update to debhelper 7.1.
 - (Description): Fix spelling.
 - (Depends): Add ${misc:Depends}.
 - (Homepage): Update to Freshmeat.
 - (Maintainer): Set to QA Group.
 - (Standards-Version): Update to 3.8.4.
   * debian/copyright
 - Update layout. Point to GPL-2.
   * debian/in.doc-base
 - (Files): Correct file locations (E: Lintian).
   * debian/README.Debian.in
 - Fix spelling.
   * debian/rules
 - (DH_COMPAT): Remove; obsolete.
 - (install_subpkgs): Update dh_clean to dh_prep.
 - (clean): Fix lintian debian-rules-ignores-make-clean-error.
   * debian/source/format
 - New file.
Checksums-Sha1: 
 0afc1068886f0b46c3cd8b5b5305d242b9918e72 969 debian-zh-faq_1.11+nmu1.dsc
 b31af06ccac880d4ca157d3a743070af7c323981 35612 debian-zh-faq_1.11+nmu1.tar.gz
 d7afc310c5bc9a78c12511fb5cad0704427a613e 920330 
debian-zh-faq-s_1.11+nmu1_all.deb
 398f7d010f66e4d9b262c78b6fa6619b209ea251 976320 
debian-zh-faq-t_1.11+nmu1_all.deb
Checksums-Sha256: 
 3bc8b4fe6a6aedfd3ef7124ec3a5b4558418bc7bd764c3d16ea45a9397282029 969 
debian-zh-faq_1.11+nmu1.dsc
 b0ac8d4553b14b15274a8606dc8243c1887f14301e98e08ed4b2d1860d19378c 35612 
debian-zh-faq_1.11+nmu1.tar.gz
 2509b46aa14c6ef84ec4af49c23063e271d880dd2914784405acc985ecee5d48 920330 
debian-zh-faq-s_1.11+nmu1_all.deb
 85785d5e7c0a4b58ee5451a695afd867f8ae0ef6f5c98b746edab557d7c51134 976320 
debian-zh-faq-t_1.11+nmu1_all.deb
Files: 
 d7d1160288527610c82ca88715b2c67a 969 doc optional debian-zh-faq_1.11+nmu1.dsc
 d40ff9662bba3c1d057ca4fc9ff641f4 35612 doc optional 
debian-zh-faq_1.11+nmu1.tar.gz
 f81faf366f0eef8737d760ac6ae8f9db 920330 doc optional 
debian-zh-faq-s_1.11+nmu1_all.deb
 2452b1c9ccaa73916542962c06840b9a 976320 doc optional 
debian-zh-faq-t_1.11+nmu1_all.deb

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

iEYEARECAAYFAkvuMeMACgkQpdwBkPlyvgOpIgCdEqVoIMZrcXZtBw6w9hXxr/bE
/pQAn3Z44+FtH9bmL8lVClEJYzXK6+KH
=I5z9
-END PGP SIGNATURE-


Accepted:
debian-zh-faq-s_1.11+nmu1_all.deb
  to main/d/debian-zh-faq/debian-zh-faq-s_1.11+nmu1_all.deb
debian-zh-faq-t_1.11+nmu1_all.deb
  to main/d/debian-zh-faq/debian-zh-faq-t_1.11+nmu1_all.deb
debian-zh-faq_1.11+nmu1.dsc
  to main/d/debian-zh-faq/debian-zh-faq_1.11+nmu1.dsc
debian-zh-faq_1.11+nmu1.tar.gz
  to main/d/debian-zh-faq/debian-zh-faq_1.11+nmu1.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/e1ognrr-0005wl...@ries.debian.org

Accepted evolution 2.30.1.2-3 (source all amd64)

2010-05-25 Thread Yves-Alexis Perez

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 25 May 2010 07:25:00 +0200
Source: evolution
Binary: evolution libevolution evolution-common evolution-dev evolution-dbg 
evolution-plugins evolution-plugins-experimental
Architecture: source all amd64
Version: 2.30.1.2-3
Distribution: unstable
Urgency: low
Maintainer: Debian Evolution Maintainers 
pkg-evolution-maintain...@lists.alioth.debian.org
Changed-By: Yves-Alexis Perez cor...@debian.org
Description: 
 evolution  - groupware suite with mail client and organizer
 evolution-common - architecture independent files for Evolution
 evolution-dbg - debugging symbols for Evolution
 evolution-dev - development library files for Evolution
 evolution-plugins - standard plugins for Evolution
 evolution-plugins-experimental - experimental plugins for Evolution
 libevolution - evolution libraries
Closes: 580419 582491 582564
Changes: 
 evolution (2.30.1.2-3) unstable; urgency=low
 .
   * debian/patches
 - 03_fix-segfault-on-some-mails-display added.  closes: #580419
 - 04_fix-crash-when-viewing-closing-mails-quickly added,
   cherry-picked from upstream. Fix crash when opening/closing mails
   quickly.  closes: #582564
   * debian/evolution.links dropped, upstream doesn't ship them in /usr/bin for
 good reason, they're supposed to be called from evolution not directly by
 user, and the interface might not be stable.closes: #582491
   * debian/watch updated to order the first directory too.
Checksums-Sha1: 
 428a5d805943d243d7916c8ae96870785a1efa47 3520 evolution_2.30.1.2-3.dsc
 07e16f2bc6b0b29c64964087dbc8659ad5e95817 40393 evolution_2.30.1.2-3.diff.gz
 5c3862668f9994ffd0ef29cb0f91beb9e0370fc6 26945494 
evolution-common_2.30.1.2-3_all.deb
 7c62fd28da3786e12148ee6d0db419fc31baa7d5 1142054 evolution_2.30.1.2-3_amd64.deb
 95b4d8ecbdfedc86e997bef911a6b240e341ba37 2300610 
libevolution_2.30.1.2-3_amd64.deb
 e089b46676b462fe1e7726ece786de376bd6a060 466824 
evolution-dev_2.30.1.2-3_amd64.deb
 6f6b1a27fd7d18c75c75f6a46aaadf080255b17a 7865456 
evolution-dbg_2.30.1.2-3_amd64.deb
 ab177dd68a721b2817422aa72902ca1adf70f915 347476 
evolution-plugins_2.30.1.2-3_amd64.deb
 f5efd58cde74d62f2747c2674376b35623d5e736 169184 
evolution-plugins-experimental_2.30.1.2-3_amd64.deb
Checksums-Sha256: 
 64c118283cf9b3345b1a373c7b77a76e48a3c8318e5b793c7ae2486470e70396 3520 
evolution_2.30.1.2-3.dsc
 4b2ead2a28ac196080c6ce71b2e11beaab74e2b72232ee298c6ccb13f75a819b 40393 
evolution_2.30.1.2-3.diff.gz
 d4fa6478346934add1d91685912236fbab4962aef156c990c037a89e3dc5cc8f 26945494 
evolution-common_2.30.1.2-3_all.deb
 9be32c15fd0afba6dc7eef9de39d43a5b3012285c66a4a455bb4f599a8fa1bc3 1142054 
evolution_2.30.1.2-3_amd64.deb
 9f6b7a6540a4e9fc29bc81154e46f446cb341588fc89d592c4ba16b277a60c52 2300610 
libevolution_2.30.1.2-3_amd64.deb
 65d4d91e298f8994940639bd794d0c0eae1f5652a8e52c90251f2b321cbb3f42 466824 
evolution-dev_2.30.1.2-3_amd64.deb
 50d119cced430649bae27258f9b0171c2d6388253762c92633f5887dea334dd2 7865456 
evolution-dbg_2.30.1.2-3_amd64.deb
 e11d2123a960569c1861d42a680df0faf7cd1b85d3c2bc0614f0fdb8a7b7ee71 347476 
evolution-plugins_2.30.1.2-3_amd64.deb
 ca2875fec80faf662e642ce6d902fe3d42089f7b3756eafae76902d52b5c48bf 169184 
evolution-plugins-experimental_2.30.1.2-3_amd64.deb
Files: 
 50db7688474fed5eae6e4f6af064232b 3520 gnome optional evolution_2.30.1.2-3.dsc
 589ad59cf7a160f8c1118026a361ea18 40393 gnome optional 
evolution_2.30.1.2-3.diff.gz
 d828b66aa8e73d2a69316f0ff87ed882 26945494 gnome optional 
evolution-common_2.30.1.2-3_all.deb
 6e2e8fdbc7fa5223bc11b809a3ee7a98 1142054 gnome optional 
evolution_2.30.1.2-3_amd64.deb
 04bd9c76dd1caffb86c8acfe3128e02f 2300610 gnome optional 
libevolution_2.30.1.2-3_amd64.deb
 0cc0c3bc199491bec1942b633b179172 466824 devel optional 
evolution-dev_2.30.1.2-3_amd64.deb
 0088dfdc24ba9f60ca64eaf47d3ba5e7 7865456 debug extra 
evolution-dbg_2.30.1.2-3_amd64.deb
 566b3189df69b9a78f0e070b61593f97 347476 gnome optional 
evolution-plugins_2.30.1.2-3_amd64.deb
 9382701a8b919108ab04a3f02900b447 169184 gnome optional 
evolution-plugins-experimental_2.30.1.2-3_amd64.deb

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

iQIcBAEBCgAGBQJL+2hTAAoJEDBVD3hx7wuoOCUQANkhBgZaUB3r5kvJmrZVv6qZ
0ylblMNpNW1zBtb+MkO1dPovRD4UaeQffDhg0AAl+scipnuTndvpPvfZiltPCxeM
Fvf5yK9G6TubvpupLQzw3fCNhaod7qlfOPZVUzgOBdqB63JfQtV3shfEeMmjIfOt
gOjd7oAzzjL2aTMW9xM7wSdNXwoSIrBI2Zap6dVTH5DJdNAJXiOuZRQ/sT5wCz+f
v/dccl089KJCoLPfsN0MUvk+cOvPgfsFEdx5uwl1zNUWQhIfxdMgSXWvahoTrmQV
NvBgGYW1LLpXE8MS6SM/A+KgamVsMlilVGvjireJYSR0oZ7bYVM7re4/jHY3CnwR
InWXjSaBKH4CI+p2aRcmyuad0Xv0ducuKbwbLtamW4nBudik36gqrvoxr0deoyXn
ZFDx9YdQrkFeLm62GCWn+p6hQsWgUu6vnTbMWlNWQHmeOdUzzQbGQC/YOQvlOUcW
6MvIBPCANquVweO6Poi5XOw+B1jYglNwXvodsV987F01WRc6ArMj1ETjInvMTs1l
l+m7MgP7ETFgN5mwTAjGC+lOHT27J1s1H1bErCsk9xB+sSNyTquQrp2hSjvXWN0S
NmmF4DzVUGkjhrmEy2orXFIfwqg379Q7cempZHgJerMV6TZrpa7yVe9RgNXVhCAt

Accepted libidn 1.19-1 (source i386 all)

2010-05-25 Thread Simon Josefsson

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 25 May 2010 07:43:14 +0200
Source: libidn
Binary: idn libidn11-dev libidn11 libidn11-java
Architecture: source i386 all
Version: 1.19-1
Distribution: experimental
Urgency: low
Maintainer: Anibal Monsalve Salazar ani...@debian.org
Changed-By: Simon Josefsson si...@josefsson.org
Description: 
 idn- Command line and Emacs interface to GNU Libidn
 libidn11   - GNU Libidn library, implementation of IETF IDN specifications
 libidn11-dev - Development files for GNU Libidn, an IDN library
 libidn11-java - Java port of the GNU Libidn library, an IDN implementation
Changes: 
 libidn (1.19-1) experimental; urgency=low
 .
   * New upstream version.
   * Switch to dpkg-source 3.0 (quilt) format.
   * Disable self checks on mips(el) due to #519006.
   * Upload to experimental to test mips(el) patch pending Anibal approval.
Checksums-Sha1: 
 5ed3163189e272f18908c6b484373ead55137e83 1549 libidn_1.19-1.dsc
 2b6dcb500e8135a9444a250d7df76f545915f25f 3207771 libidn_1.19.orig.tar.gz
 53549f8f47173646ed29898242710a56cb066b17 9709 libidn_1.19-1.debian.tar.gz
 99f4936dc260b920418db6333eb56cdb99f5b8c4 115166 idn_1.19-1_i386.deb
 0fa24eea8c598b7a279508927755c8acc4984f20 735768 libidn11-dev_1.19-1_i386.deb
 7021ece9a69a75c05d244952633227b3470ebb4f 163426 libidn11_1.19-1_i386.deb
 59eb9dc12e2b7b4728aba1b5248cdce9760473fb 218166 libidn11-java_1.19-1_all.deb
Checksums-Sha256: 
 dc5d856dd85de173e6efe434eb33235c7a80d58b5f85f4bcbb55e0fc16a24bda 1549 
libidn_1.19-1.dsc
 8ed2e936b1ae3e30b45b54ca3672deaa83ee0f4d20db5ad83dc1af7222d39f41 3207771 
libidn_1.19.orig.tar.gz
 cdda87b7a89edea54d1b2d83ca767069f2589ffe5166b4f6c8d6be8048eeec0e 9709 
libidn_1.19-1.debian.tar.gz
 51bff8c4ab5d31c7650c2d0c71fad77d0b832168d53bb16efd2e0f2af00abc65 115166 
idn_1.19-1_i386.deb
 08983893f79823353bdcbf655f97684efd5607a659393e59665eeade496a0032 735768 
libidn11-dev_1.19-1_i386.deb
 02bfd7698c7fe5ecc7acd6811559101ccec8aaaff4c575bb18a4e598d659dff4 163426 
libidn11_1.19-1_i386.deb
 ee7f94d182b7ed9b72289f9ddf21060e155a0ed20674ae92a13bf700940b5653 218166 
libidn11-java_1.19-1_all.deb
Files: 
 ad4e4d943c789620a810c4a2c0508e34 1549 libs optional libidn_1.19-1.dsc
 a45142126d28162014c995f969bdb5a8 3207771 libs optional libidn_1.19.orig.tar.gz
 31249f084353bf50ac17fdd5e2ed1f34 9709 libs optional libidn_1.19-1.debian.tar.gz
 d9c7ff14353fad95bbd31d5d75ee0725 115166 misc optional idn_1.19-1_i386.deb
 01edc08763ce6959f565c69602880897 735768 libdevel optional 
libidn11-dev_1.19-1_i386.deb
 27ee356c01dbd104559dd28444312264 163426 libs standard libidn11_1.19-1_i386.deb
 e58fbac294964318b9ac4a2f08ed6daf 218166 java optional 
libidn11-java_1.19-1_all.deb

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

iOoEAQECADQFAkv7atUtFIAAFQAPcGthLWFkZHJlc3NAZ251cGcub3JnamFz
QGV4dHVuZG8uY29tAAoJEO2iHpS1ZXFvRzcE/A15BfaFHo9cRF/XhEzztwi+ZZv5
77YbiTNJVA0nNYQOyCX4kOcic/ZWKPglBTf+kAGwND1Ue+t1UVBDCL9Tx+D8h8Ib
XkTrCIfFJjHYiUQwstZ8sd5wOdfK3K+0BhW6Ru4wk2Imrvsw1ubZ4ghaVYmqI4IY
+9dnUoiLBI31lNX6xihaEL9B3kGgJCV9bArE517lMrV9JopsAKeOZX45Y4E=
=uZzn
-END PGP SIGNATURE-


Accepted:
idn_1.19-1_i386.deb
  to main/libi/libidn/idn_1.19-1_i386.deb
libidn11-dev_1.19-1_i386.deb
  to main/libi/libidn/libidn11-dev_1.19-1_i386.deb
libidn11-java_1.19-1_all.deb
  to main/libi/libidn/libidn11-java_1.19-1_all.deb
libidn11_1.19-1_i386.deb
  to main/libi/libidn/libidn11_1.19-1_i386.deb
libidn_1.19-1.debian.tar.gz
  to main/libi/libidn/libidn_1.19-1.debian.tar.gz
libidn_1.19-1.dsc
  to main/libi/libidn/libidn_1.19-1.dsc
libidn_1.19.orig.tar.gz
  to main/libi/libidn/libidn_1.19.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/e1ogniy-0006vg...@ries.debian.org

Accepted qtiplot 0.9.7.14-1 (source all amd64)

2010-05-25 Thread Gudjon I. Gudjonsson

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 23 May 2010 10:17:19 +0200
Source: qtiplot
Binary: qtiplot qtiplot-doc
Architecture: source amd64 all
Version: 0.9.7.14-1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Team 
debian-science-maintain...@lists.alioth.debian.org
Changed-By: Gudjon I. Gudjonsson gud...@gudjon.org
Description: 
 qtiplot- data analysis and scientific plotting
 qtiplot-doc - data analysis and scientific plotting (documentation)
Changes: 
 qtiplot (0.9.7.14-1) unstable; urgency=low
 .
   * New upstream release
   * Build QTeXEngine into program
   * Bump liborigin2 dependency to =1:06042009+svn1724
   * Bump muparser dependency to 1.32
Checksums-Sha1: 
 272a4aa8a44725d7ff17555117b3c7b4c6db0ba3 1607 qtiplot_0.9.7.14-1.dsc
 6f796a83dfeeec9a2052794802f189851de2a8c7 8586257 qtiplot_0.9.7.14.orig.tar.gz
 8948f26839a65ff2be37206d59090cd1f6be06ca 19952 qtiplot_0.9.7.14-1.debian.tar.gz
 e811cfc34cade33a6f1d413ac9922ef9a6f9369b 2616314 qtiplot_0.9.7.14-1_amd64.deb
 03bb47616bb8a7027eed454fc687638fece680aa 14346324 
qtiplot-doc_0.9.7.14-1_all.deb
Checksums-Sha256: 
 d2521f37891e3ca4cbb05b5841a42368511875fb6bf7d21ca91906dc4dc51a0c 1607 
qtiplot_0.9.7.14-1.dsc
 27b4b833b590ef01bdf9812971fc4178c900788034121c6ba38ccd821014b10d 8586257 
qtiplot_0.9.7.14.orig.tar.gz
 47c1b1363e13f11d52920f3d0a9b8517e56386610223af1aa8932918c94baf4f 19952 
qtiplot_0.9.7.14-1.debian.tar.gz
 979fa7af30938c912fc0d62ad294f40a8d7f1716cd8bdbf4ccb1a4e905b17763 2616314 
qtiplot_0.9.7.14-1_amd64.deb
 0866dcaed199a8eac5ff56c9bb930720a6383f4a9e3a6200d3d2c09dbe82a128 14346324 
qtiplot-doc_0.9.7.14-1_all.deb
Files: 
 f1885fe27a98591eb95437ceafa19af5 1607 math optional qtiplot_0.9.7.14-1.dsc
 16af4bf3dbc03e16efc0d229f070 8586257 math optional 
qtiplot_0.9.7.14.orig.tar.gz
 e456309832d2550889789cf4ff84e1fb 19952 math optional 
qtiplot_0.9.7.14-1.debian.tar.gz
 8e9fc15291b9d3d1525fa9b80e54fb18 2616314 math optional 
qtiplot_0.9.7.14-1_amd64.deb
 c9cb196b22372af154d4f52aaf778181 14346324 doc optional 
qtiplot-doc_0.9.7.14-1_all.deb

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

iEYEARECAAYFAkv6SuMACgkQYDBbMcCf01pHIwCgl0Ju2wPP4CMKhk1uNVun34kx
nKUAni7IqdDVGEAwQ2Ndag+UZ65xEoCN
=7G3/
-END PGP SIGNATURE-


Accepted:
qtiplot-doc_0.9.7.14-1_all.deb
  to main/q/qtiplot/qtiplot-doc_0.9.7.14-1_all.deb
qtiplot_0.9.7.14-1.debian.tar.gz
  to main/q/qtiplot/qtiplot_0.9.7.14-1.debian.tar.gz
qtiplot_0.9.7.14-1.dsc
  to main/q/qtiplot/qtiplot_0.9.7.14-1.dsc
qtiplot_0.9.7.14-1_amd64.deb
  to main/q/qtiplot/qtiplot_0.9.7.14-1_amd64.deb
qtiplot_0.9.7.14.orig.tar.gz
  to main/q/qtiplot/qtiplot_0.9.7.14.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/e1ognlu-0007e7...@ries.debian.org

Accepted jove 4.16.0.72-1 (source i386)

2010-05-25 Thread Cord Beermann

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 25 May 2010 08:04:56 +0200
Source: jove
Binary: jove xjove
Architecture: source i386
Version: 4.16.0.72-1
Distribution: unstable
Urgency: low
Maintainer: Cord Beermann c...@debian.org
Changed-By: Cord Beermann c...@debian.org
Description: 
 jove   - Jonathan's Own Version of Emacs - a compact, powerful editor
 xjove  - X11-Frontend for jove - a compact, powerful editor
Changes: 
 jove (4.16.0.72-1) unstable; urgency=low
 .
   * New upstream release
 + fixes a bug that shows up on 64-bit Ubuntu 10.4
   * Make Lintian Happy
 + Bumped Policy-version
 + Depends on dh 7
 + Adding Source-Format
   * Dropped linking against libolgx (not used by xjove)
   * Fixed a typo in the manpage
   * Acknowledge the NMUs
Checksums-Sha1: 
 810f7048c0bf417499b902720e328401f29c9d1d 1034 jove_4.16.0.72-1.dsc
 9f7ecff8da21c8ba0efac68ce7535e631a37e856 464916 jove_4.16.0.72.orig.tar.gz
 c965482a65aef3b058c36441c4d3e12bfab5038c 16792 jove_4.16.0.72-1.diff.gz
 ff65d28b2123f167032b8361b613e6eab989f267 195200 jove_4.16.0.72-1_i386.deb
 8fe53b582c1a51a9764bd51c3f32cf4a55288027 29830 xjove_4.16.0.72-1_i386.deb
Checksums-Sha256: 
 c3b9a0eed621070afc057c24aa6ca06cd18dc1fc61fa5c0f63fc327c4eefc2f5 1034 
jove_4.16.0.72-1.dsc
 55043b404a23e524ae31a284889639d87d9b1578f5f422503b7e3de4a6bafa44 464916 
jove_4.16.0.72.orig.tar.gz
 1df58d30efbca4f133b71e0408fcc80e9c61044829af554283e0fe8ded3528c5 16792 
jove_4.16.0.72-1.diff.gz
 5b3612683ebdffaebae64de3f1f47ce4d64347372e3854b7f47a322627a34552 195200 
jove_4.16.0.72-1_i386.deb
 ce304e39cc5d7217033f9886f70c4986335940661c56e807d036df9b6bb38ac9 29830 
xjove_4.16.0.72-1_i386.deb
Files: 
 6ca8927b43721b46187be6055d7f4dc5 1034 editors optional jove_4.16.0.72-1.dsc
 4f76e2ad96f854919ed0fba0ae36efc2 464916 editors optional 
jove_4.16.0.72.orig.tar.gz
 b1658eee4f05dccb85fabb76fb7f114c 16792 editors optional 
jove_4.16.0.72-1.diff.gz
 ca81f2486fdfb7fca212b33b0563f645 195200 editors optional 
jove_4.16.0.72-1_i386.deb
 dc789cc7abea60925d2d1e76b49030f1 29830 editors optional 
xjove_4.16.0.72-1_i386.deb

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

iEYEARECAAYFAkv7cRQACgkQ72U+jVr0xGJpawCePU/Fhs50URM3TpehumDxvWin
Il0AoI2zAPxn+AFbalh8niu8L2a3LNCR
=BjNJ
-END PGP SIGNATURE-


Accepted:
jove_4.16.0.72-1.diff.gz
  to main/j/jove/jove_4.16.0.72-1.diff.gz
jove_4.16.0.72-1.dsc
  to main/j/jove/jove_4.16.0.72-1.dsc
jove_4.16.0.72-1_i386.deb
  to main/j/jove/jove_4.16.0.72-1_i386.deb
jove_4.16.0.72.orig.tar.gz
  to main/j/jove/jove_4.16.0.72.orig.tar.gz
xjove_4.16.0.72-1_i386.deb
  to main/j/jove/xjove_4.16.0.72-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/e1ognuv-0007d2...@ries.debian.org

Accepted libmtp 1.0.3-1 (source all i386)

2010-05-25 Thread Alessio Treglia

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 25 May 2010 08:22:17 +0200
Source: libmtp
Binary: libmtp8 libmtp-dev libmtp-dbg libmtp-doc mtp-tools
Architecture: source all i386
Version: 1.0.3-1
Distribution: unstable
Urgency: low
Maintainer: Alessio Treglia quadris...@ubuntu.com
Changed-By: Alessio Treglia quadris...@ubuntu.com
Description: 
 libmtp-dbg - Media Transfer Protocol (MTP) debugging symbols
 libmtp-dev - Media Transfer Protocol (MTP) development files
 libmtp-doc - Media Transfer Protocol (MTP) library documentation
 libmtp8- Media Transfer Protocol (MTP) library
 mtp-tools  - Media Transfer Protocol (MTP) library tools
Changes: 
 libmtp (1.0.3-1) unstable; urgency=low
 .
   * debian/copyright: Update according to DEP-5 proposal.
   * Add apport package hook to reduce delta with Ubuntu.
   * New upstream release:
 - Don't probe HID equipment for device OS descriptors
   some Kensington mice really don't like that (LP: #559892).
   * Switch to debian 3.0 (quilt) source format.
Checksums-Sha1: 
 aed791d80a45586bc1e7e9a3a802aeb173f38733 1295 libmtp_1.0.3-1.dsc
 3d237dc02e420d9ccb8f2539d2818b2f618eaf5f 596040 libmtp_1.0.3.orig.tar.gz
 1af2007c011ebde63058fc314fd56f6f8db76cfd 15036 libmtp_1.0.3-1.debian.tar.gz
 8cf17d61a3bf74bc4a686685e6ba01851e71abc9 360280 libmtp-doc_1.0.3-1_all.deb
 2f32a422894c439bac448bf0759a21ab16dfade9 166288 libmtp8_1.0.3-1_i386.deb
 11d1bd973762b285dbe702a4aa4c5e09edda2235 162160 libmtp-dev_1.0.3-1_i386.deb
 fb6cfe187d245de2617a9785be0a16b4cdc0ada9 236112 libmtp-dbg_1.0.3-1_i386.deb
 ceb8100a0c894a0a1e5f7ea85bd0372c4dad2640 88056 mtp-tools_1.0.3-1_i386.deb
Checksums-Sha256: 
 df9fdd247bab94dc4d2e292f481c41b0cd038c63584ace665d875e7f5cc48cc6 1295 
libmtp_1.0.3-1.dsc
 1d00487618e769bbe641261a6e1312c7bac3c28170af2b13a750b8fa4014caca 596040 
libmtp_1.0.3.orig.tar.gz
 5a60321f39ba2eb5942ba9c68c38d130606e8ccd21becb8989ff260ec85ac9bf 15036 
libmtp_1.0.3-1.debian.tar.gz
 7d98157a03f97ef121f0178db38693f81f98245c839df923d37d15994cb502c8 360280 
libmtp-doc_1.0.3-1_all.deb
 bc56450a93e9f8a055624474aefb2c761aac57bc3b621d2bfb6b237fb203c6ab 166288 
libmtp8_1.0.3-1_i386.deb
 c0673fc13982dec03b7e1076ba09ab3a91be2e99473acdb8445d41b1de8c806a 162160 
libmtp-dev_1.0.3-1_i386.deb
 69c92810c0b6a3c979c5ad83d6c0da2a1df61f50a71b6d65ac74f22851063e87 236112 
libmtp-dbg_1.0.3-1_i386.deb
 f8598b706f09e2eab29b4f68618250f27da370de1a3fef59e00bb7643b5eaf0d 88056 
mtp-tools_1.0.3-1_i386.deb
Files: 
 b5736899bead231e3e72f3a9324bf15e 1295 libs optional libmtp_1.0.3-1.dsc
 a972869860765476e52f2eba45f2b91e 596040 libs optional libmtp_1.0.3.orig.tar.gz
 82002ffb38cbb3ead52983447996cf5f 15036 libs optional 
libmtp_1.0.3-1.debian.tar.gz
 9e5a115afafbaa7822ff277910dd91d1 360280 doc optional libmtp-doc_1.0.3-1_all.deb
 d6fd9e3a6f53b263a05327e17cf1c05f 166288 libs optional libmtp8_1.0.3-1_i386.deb
 1d6f9df3162b63e7923a670f6a3100a9 162160 libdevel optional 
libmtp-dev_1.0.3-1_i386.deb
 37799c49af538a7eadfc34e6fced7b4b 236112 debug extra libmtp-dbg_1.0.3-1_i386.deb
 1d9a38499350f6161cd57c4bfc7a8102 88056 utils optional 
mtp-tools_1.0.3-1_i386.deb

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

iEYEARECAAYFAkv7clAACgkQRdSMfNz8P9BregCaAiKSVainBuoMXPeyxjCui7hH
RmcAn36352l/WZiACsJoVlAkEtt9jq0i
=/RPW
-END PGP SIGNATURE-


Accepted:
libmtp-dbg_1.0.3-1_i386.deb
  to main/libm/libmtp/libmtp-dbg_1.0.3-1_i386.deb
libmtp-dev_1.0.3-1_i386.deb
  to main/libm/libmtp/libmtp-dev_1.0.3-1_i386.deb
libmtp-doc_1.0.3-1_all.deb
  to main/libm/libmtp/libmtp-doc_1.0.3-1_all.deb
libmtp8_1.0.3-1_i386.deb
  to main/libm/libmtp/libmtp8_1.0.3-1_i386.deb
libmtp_1.0.3-1.debian.tar.gz
  to main/libm/libmtp/libmtp_1.0.3-1.debian.tar.gz
libmtp_1.0.3-1.dsc
  to main/libm/libmtp/libmtp_1.0.3-1.dsc
libmtp_1.0.3.orig.tar.gz
  to main/libm/libmtp/libmtp_1.0.3.orig.tar.gz
mtp-tools_1.0.3-1_i386.deb
  to main/libm/libmtp/mtp-tools_1.0.3-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/e1ogo9x-cu...@ries.debian.org

Accepted csmash 0.6.6-6.5 (source all i386)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 11 May 2010 21:30:14 +0300
Source: csmash
Binary: csmash csmash-data
Architecture: source all i386
Version: 0.6.6-6.5
Distribution: unstable
Urgency: low
Maintainer: Bartosz Fenski fe...@debian.org
Changed-By: Jari Aalto jari.aa...@cante.net
Description: 
 csmash - CannonSmash, a table tennis simulation game
 csmash-data - data files for the CannonSmash game
Closes: 356199 578977
Changes: 
 csmash (0.6.6-6.5) unstable; urgency=low
 .
   [ Jari Aalto ]
   * Non-maintainer upload.
 - Update to packaging format 3.0 (quilt).
 - ACK old nmudiff for 0.6.6-6.1 in the BTS (Closes: #356199).
   * cmash.menu
 - (section): Change non-existing Games/Sports to Games/Action.
   * debian/compat
 - New file; value 7.
   * debian/control
 - (Build-Depends): update obsolete xutils to xutils-dev,
   xlibmesa-gl-dev to libgl1-mesa-dev and remove libglu1-xorg-dev
   (important; Closes: #578977). Add libsdl1.2-dev.
   Update to debhelper 7.1. Remove dpatch
 - (Homepage): New field. Lift from description.
 - (Standards-Version): Update from ancient 3.6.1 to 3.8.4.
 - (cmash::Depends): Add ${misc:Depends}. Change obsolete ${Source-Version}
   to ${source:Version}.
 - (cmash::Section): remove duplicate derived field.
 - (cmash-data::Depends): Add ${misc:Depends}.
   * debian/copyright
 - Point to GPL-2. Fix spelling.
   * debian/patches
 - (Number 10): Allow SDL = 1.2.
   * debian/rules
 - Remove dpatch; obsoleted by new package format.
 - (clean): Fix lintian debian-rules-ignores-make-clean-error.
 - (DH_COMPAT): Remove, use debian/compat instead.
 - (install-stamp): use install(1) to copy csmash.xpm.
   Change ch_clean with dh_prep. Install csmash.xpm with mode 644.
   Delete empty directory usr/share/games/.
   * debian/source/format
 - New file.
Checksums-Sha1: 
 2fb60bdfda4ab76c8483f9615b3b5ea871142fc3 1308 csmash_0.6.6-6.5.dsc
 016315109dd0176b461e4d351568586160597e4c 9928 csmash_0.6.6-6.5.debian.tar.gz
 29cdc36488ad2a688f8850b3c61d4030d6585c3b 1707104 csmash-data_0.6.6-6.5_all.deb
 dce9f9ff5c3752adc95786e7e88274a555499d86 172916 csmash_0.6.6-6.5_i386.deb
Checksums-Sha256: 
 ac4a1416d50448b9e1b1adf930110b8810f9fd3f1bb09b67bd2d75dce2ab9b37 1308 
csmash_0.6.6-6.5.dsc
 f821ce5628a28e07cd5dd5dd6b98b6e05f81a164cf2db024ef52f9aba04f5bdd 9928 
csmash_0.6.6-6.5.debian.tar.gz
 0f3f542b2e8a853bc8d54d6efec0f20ea7fb284408c82247fb138bc48f467365 1707104 
csmash-data_0.6.6-6.5_all.deb
 66a73f857b535f9dafc22d2900150629c01e1b4596f631978ca31ef9bde1746f 172916 
csmash_0.6.6-6.5_i386.deb
Files: 
 c8ed176f240354982daf50d5da61809f 1308 games optional csmash_0.6.6-6.5.dsc
 2ab69b464c772c50e7234785c6ab18e5 9928 games optional 
csmash_0.6.6-6.5.debian.tar.gz
 9d7adb082219dccca95f15fe770c 1707104 games optional 
csmash-data_0.6.6-6.5_all.deb
 15a2f77896c54e9d55834ae89f3dfca6 172916 games optional 
csmash_0.6.6-6.5_i386.deb

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

iEYEARECAAYFAkvuP0QACgkQpdwBkPlyvgPc7QCbBJgytCgy5H3hkezVUaUeJA0C
ls4An1FRtoHu7624CjpXACIVWnb5iUXo
=oppx
-END PGP SIGNATURE-


Accepted:
csmash-data_0.6.6-6.5_all.deb
  to main/c/csmash/csmash-data_0.6.6-6.5_all.deb
csmash_0.6.6-6.5.debian.tar.gz
  to main/c/csmash/csmash_0.6.6-6.5.debian.tar.gz
csmash_0.6.6-6.5.dsc
  to main/c/csmash/csmash_0.6.6-6.5.dsc
csmash_0.6.6-6.5_i386.deb
  to main/c/csmash/csmash_0.6.6-6.5_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/e1ogoo0-0001nz...@ries.debian.org

Accepted rails 2.3.5-1 (source all)

2010-05-25 Thread Adam Majer

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 23 May 2010 01:21:31 -0500
Source: rails
Binary: rails rails-ruby1.8 rails-doc libactiverecord-ruby 
libactiverecord-ruby1.8 libactiverecord-ruby1.9.1 libactivesupport-ruby 
libactivesupport-ruby1.8 libactivesupport-ruby1.9.1 libactionpack-ruby 
libactionpack-ruby1.8 libactionmailer-ruby libactionmailer-ruby1.8 
libactiveresource-ruby libactiveresource-ruby1.8
Architecture: source all
Version: 2.3.5-1
Distribution: unstable
Urgency: low
Maintainer: Adam Majer ad...@zombino.com
Changed-By: Adam Majer ad...@zombino.com
Description: 
 libactionmailer-ruby - Framework for generation of customized email messages
 libactionmailer-ruby1.8 - Framework for generation of customized email messages
 libactionpack-ruby - Controller and View framework used by Rails
 libactionpack-ruby1.8 - Controller and View framework used by Rails
 libactiverecord-ruby - ORM database interface for ruby
 libactiverecord-ruby1.8 - ORM database interface for ruby
 libactiverecord-ruby1.9.1 - ORM database interface for ruby
 libactiveresource-ruby - Connects objects and REST web services
 libactiveresource-ruby1.8 - Connects objects and REST web services
 libactivesupport-ruby - utility classes and extensions (Ruby 1.8)
 libactivesupport-ruby1.8 - utility classes and extensions (Ruby 1.8)
 libactivesupport-ruby1.9.1 - utility classes and extensions (Ruby 1.8)
 rails  - MVC ruby based framework geared for web application development
 rails-doc  - Documentation for rails, a MVC ruby based framework
 rails-ruby1.8 - MVC ruby based framework geared for web application development
Closes: 469524 517328 547658
Changes: 
 rails (2.3.5-1) unstable; urgency=low
 .
   * New upstream release (closes: #547658)
   * Package is now split up and non-core rails components, like AR, are on
 the ruby load path. (closes: #469524, #517328)
   * debian/control
 + Depend on rubygems.
 + Suggest thin or thin1.8 as a possible server to run your production
   environment on. This is particularly useful if it is already being
   proxied.
 + xml-simple is no longer used by rails
 + Updated Standard to 3.8.4
Checksums-Sha1: 
 2dfea7ab1b56669e1e38b759c6361b7c7b3f37b6 1647 rails_2.3.5-1.dsc
 f8df515f5137e69cefbdb21af94410eb6a0fd4b4 3173705 rails_2.3.5.orig.tar.gz
 44f2eff4728346ea1fdcb0d12d3de1fb3cb83a28 15643 rails_2.3.5-1.debian.tar.gz
 201364397d145560a504ee4f468390d0792d7e41 11426 rails_2.3.5-1_all.deb
 d3459bf2bcebaf76707f36dea609b35b29dd5244 220872 rails-ruby1.8_2.3.5-1_all.deb
 7d9522208cff6ca967f2dae5afaa26dbd46fe356 886076 rails-doc_2.3.5-1_all.deb
 89ef3150f858183a6ac014029dfea22c838fd988 8916 
libactiverecord-ruby_2.3.5-1_all.deb
 7b2510be592792302a7e26dc2906296f50181a51 264924 
libactiverecord-ruby1.8_2.3.5-1_all.deb
 5582eddfdcb6c711adfd873849132a790b081b74 264498 
libactiverecord-ruby1.9.1_2.3.5-1_all.deb
 5e43171df9c4001efbbb14abe5b04d226307d5c1 8824 
libactivesupport-ruby_2.3.5-1_all.deb
 08b962dbec03c2d726d65b4e3d458c3b59d669b7 255154 
libactivesupport-ruby1.8_2.3.5-1_all.deb
 3874d431ca499f177ceae805ec78e93232e48acb 255194 
libactivesupport-ruby1.9.1_2.3.5-1_all.deb
 894bcf266180a884f81724c0702faa8320cdd434 8964 
libactionpack-ruby_2.3.5-1_all.deb
 7a1b79a9d2928a6ff11d46da0818dbc3607d6571 313618 
libactionpack-ruby1.8_2.3.5-1_all.deb
 06ce9a97967f015f27ad674536376ec6ab428903 8936 
libactionmailer-ruby_2.3.5-1_all.deb
 5846ec4b6354cce4ca12a4fffa5c224a4ffec304 31186 
libactionmailer-ruby1.8_2.3.5-1_all.deb
 2b85a421eeecf1104cb184869479f263263c 8926 
libactiveresource-ruby_2.3.5-1_all.deb
 903730dac154477bf2b64510698f3ad9fcd7d3a0 36228 
libactiveresource-ruby1.8_2.3.5-1_all.deb
Checksums-Sha256: 
 3df53911f99ab21cc54bbd4cb7f1c074db941a55d2237b89bb33d215739093e9 1647 
rails_2.3.5-1.dsc
 f07416a3655ef24316e6fb8bd57bf00f5b06b9d6191cec15be93d08238ed1313 3173705 
rails_2.3.5.orig.tar.gz
 bcb661d84ab6ce742519849b831de695f776d6b9328511fc6aa722070797b962 15643 
rails_2.3.5-1.debian.tar.gz
 4e264a6e039774ae4128e7aa4578ec4719d1c6e13d2d58a2525bec848db1306a 11426 
rails_2.3.5-1_all.deb
 9641f213744d90229fb8ecf4099b921ffa1bddd80b97a735a4e6419dfd706624 220872 
rails-ruby1.8_2.3.5-1_all.deb
 32ae9ba29be49f41a10cef5cbcdad32bcc12b8fb5f1ad0ad06079b4a00da99a4 886076 
rails-doc_2.3.5-1_all.deb
 68c1ea93bdd2c0df7afdd9550678d40b42784a268d8717d99a3f457670261d33 8916 
libactiverecord-ruby_2.3.5-1_all.deb
 ca002af68e930e62eb6b3d295baf944765ed38b81e614f2cf277bf4d70c10748 264924 
libactiverecord-ruby1.8_2.3.5-1_all.deb
 62407ada5a770708e522c6cac519844f291e4f1f32287c5dc0f9d4922a0f102d 264498 
libactiverecord-ruby1.9.1_2.3.5-1_all.deb
 7d5c45c6a6fac9f57203b79caaa47fca7ae9294d5755e125110f1026056e4c08 8824 
libactivesupport-ruby_2.3.5-1_all.deb
 60dc9a83f31df02d14223852eff16c15af9bc4f2ab82dfa60f13c9742ac067d8 255154 
libactivesupport-ruby1.8_2.3.5-1_all.deb
 0a35923bea3b5feda285cbd48e75d8a1b91d132b1afeb7aebca1ad54f99fcb8d 255194 
libactivesupport-ruby1.9.1_2.3.5-1_all.deb

Accepted libusb-1.0 2:1.0.8-2 (source amd64)

2010-05-25 Thread Aurelien Jarno

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 25 May 2010 07:35:56 +
Source: libusb-1.0
Binary: libusb-1.0-0 libusb-1.0-0-dev libusb-1.0-0-udeb
Architecture: source amd64
Version: 2:1.0.8-2
Distribution: unstable
Urgency: low
Maintainer: Aurelien Jarno aure...@debian.org
Changed-By: Aurelien Jarno aure...@debian.org
Description: 
 libusb-1.0-0 - userspace USB programming library
 libusb-1.0-0-dev - userspace USB programming library development files
 libusb-1.0-0-udeb - userspace USB programming library (udeb)
Closes: 582992
Changes: 
 libusb-1.0 (2:1.0.8-2) unstable; urgency=low
 .
   * Add 01-configure-bashisms.diff to fix bashisms (closes: bug#582992).
Checksums-Sha1: 
 0697a1eff2d616e6b64439bdea1efc2855095a3f 1071 libusb-1.0_1.0.8-2.dsc
 45e27f9c062a36b5c35e432d0268f70d0290d6f9 9045 libusb-1.0_1.0.8-2.debian.tar.gz
 97aafb41df78172906a9fe2b57742679bcc169bb 34474 libusb-1.0-0_1.0.8-2_amd64.deb
 a3948a0a23cf9173f3321857f562afb4de43ac93 156986 
libusb-1.0-0-dev_1.0.8-2_amd64.deb
 4c2de94c5d49da58ffdc58ec6718ba7de72b6b08 26026 
libusb-1.0-0-udeb_1.0.8-2_amd64.udeb
Checksums-Sha256: 
 e30988bd83371f842ead6cc43c92b80b863289a19a613db855b22eea673e69f9 1071 
libusb-1.0_1.0.8-2.dsc
 4c8820f24abc204aaf507a69643f5aed34ab8c0db790003cfd69f6d6e7f437c6 9045 
libusb-1.0_1.0.8-2.debian.tar.gz
 0d88fbc7013c8b3972ef1e0f8c6438161133002b48a5a1d3227d9b87e900ca5b 34474 
libusb-1.0-0_1.0.8-2_amd64.deb
 b204089f2e7ebe536e45761ba15e96c5c88dacfdab161d66c0d0ad3c42a1cd77 156986 
libusb-1.0-0-dev_1.0.8-2_amd64.deb
 86a87447beddc9f172578da427a17fb4158fd6285136ce0cf69153f1b95e2ca9 26026 
libusb-1.0-0-udeb_1.0.8-2_amd64.udeb
Files: 
 d11994b8ec5d3cb3ed5a829e1a17341c 1071 libs optional libusb-1.0_1.0.8-2.dsc
 18ce698e6945fc7f621c86377786b5f2 9045 libs optional 
libusb-1.0_1.0.8-2.debian.tar.gz
 9f7a9883471931f467a9fec36510c806 34474 libs optional 
libusb-1.0-0_1.0.8-2_amd64.deb
 c4514f9a61df473d57d7085c9ff752cf 156986 libdevel optional 
libusb-1.0-0-dev_1.0.8-2_amd64.deb
 71940c4d8fbc5095631c7a5ddf6286f0 26026 debian-installer optional 
libusb-1.0-0-udeb_1.0.8-2_amd64.udeb
Package-Type: udeb

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

iD8DBQFL+39ow3ao2vG823MRAprBAJ90uQMDjCYid01jGCVrnZGN9kTyDACeMryE
h76rB1ZvacQhCnXGxFeB9vo=
=S7BB
-END PGP SIGNATURE-


Accepted:
libusb-1.0-0-dev_1.0.8-2_amd64.deb
  to main/libu/libusb-1.0/libusb-1.0-0-dev_1.0.8-2_amd64.deb
libusb-1.0-0-udeb_1.0.8-2_amd64.udeb
  to main/libu/libusb-1.0/libusb-1.0-0-udeb_1.0.8-2_amd64.udeb
libusb-1.0-0_1.0.8-2_amd64.deb
  to main/libu/libusb-1.0/libusb-1.0-0_1.0.8-2_amd64.deb
libusb-1.0_1.0.8-2.debian.tar.gz
  to main/libu/libusb-1.0/libusb-1.0_1.0.8-2.debian.tar.gz
libusb-1.0_1.0.8-2.dsc
  to main/libu/libusb-1.0/libusb-1.0_1.0.8-2.dsc


-- 
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/e1ogovi-hl...@ries.debian.org

Accepted faust 0.9.24-1 (source amd64)

2010-05-25 Thread Mario Lang

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 19 May 2010 13:53:01 +0200
Source: faust
Binary: faust
Architecture: source amd64
Version: 0.9.24-1
Distribution: unstable
Urgency: low
Maintainer: Mario Lang ml...@debian.org
Changed-By: Mario Lang ml...@debian.org
Description: 
 faust  - functional programming language for realtime audio applications
Changes: 
 faust (0.9.24-1) unstable; urgency=low
 .
   * New upstream release
   * Upgrade Standsrds-Version from 3.8.2 to 3.8.4.
Checksums-Sha1: 
 392b230cc55ed7e1b9da243987268d245468214a 943 faust_0.9.24-1.dsc
 d96b4c1e20cda92bafef9a4f791828285a06509b 8211214 faust_0.9.24.orig.tar.gz
 a2c525997439753b8bd13e2f5af04860d3bbac28 3094 faust_0.9.24-1.diff.gz
 67f1a8e91f2cb68edc1c0e2a2e20e815727ed8b1 6977456 faust_0.9.24-1_amd64.deb
Checksums-Sha256: 
 259bf5e717e791c1e7afc5bb0318c1984bba40f47625fcaf3ba92357f49ec074 943 
faust_0.9.24-1.dsc
 efa5174600d084597afe6a7109e1462b3074bbc15172ec88614efea8873572ea 8211214 
faust_0.9.24.orig.tar.gz
 9fc3581ad88de5c84e730ee84ac06e8fb60987d578aed7c4057c9947e1e36f3f 3094 
faust_0.9.24-1.diff.gz
 482eaf412b465c952dc43a809bc5e691bdd1f446afdd5496ff50829ed1b904d9 6977456 
faust_0.9.24-1_amd64.deb
Files: 
 7430adc6ad0ecc3dec8f08cfbdae4557 943 sound optional faust_0.9.24-1.dsc
 0a5c2b04be44870da281bb422e8c7dfb 8211214 sound optional 
faust_0.9.24.orig.tar.gz
 7cc9955a97592134b9777feaee05d264 3094 sound optional faust_0.9.24-1.diff.gz
 9f68b1324f910bcf790e04a73185f538 6977456 sound optional 
faust_0.9.24-1_amd64.deb

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

iD8DBQFL+5IR3/wCKmsRPkQRAv1jAJ9Qr7S1oeKVihnzEUz2nQNb3hRQHgCdGtqe
CzdGXgtSRaYl6DiAEyJz35w=
=R8Ec
-END PGP SIGNATURE-


Accepted:
faust_0.9.24-1.diff.gz
  to main/f/faust/faust_0.9.24-1.diff.gz
faust_0.9.24-1.dsc
  to main/f/faust/faust_0.9.24-1.dsc
faust_0.9.24-1_amd64.deb
  to main/f/faust/faust_0.9.24-1_amd64.deb
faust_0.9.24.orig.tar.gz
  to main/f/faust/faust_0.9.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/e1ogqzd-0007sb...@ries.debian.org

Accepted glib2.0 2.25.7-1 (source all amd64)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 25 May 2010 11:29:07 +0200
Source: glib2.0
Binary: libglib2.0-0 libglib2.0-udeb libglib2.0-bin libglib2.0-dev 
libglib2.0-0-dbg libglib2.0-data libglib2.0-doc libgio-fam libglib2.0-0-refdbg
Architecture: source all amd64
Version: 2.25.7-1
Distribution: experimental
Urgency: low
Maintainer: Loic Minier l...@dooz.org
Changed-By: Sebastian Dröge sl...@debian.org
Description: 
 libgio-fam - GLib Input, Output and Streaming Library (fam module)
 libglib2.0-0 - The GLib library of C routines
 libglib2.0-0-dbg - The GLib libraries and debugging symbols
 libglib2.0-0-refdbg - The GLib library of C routines - refdbg library
 libglib2.0-bin - The programs for the GLib library
 libglib2.0-data - Common files for GLib library
 libglib2.0-dev - Development files for the GLib library
 libglib2.0-doc - Documentation files for the GLib library
 libglib2.0-udeb - The GLib library of C routines - minimal runtime (udeb)
Changes: 
 glib2.0 (2.25.7-1) experimental; urgency=low
 .
   * New upstream development release:
 + debian/rules,
   debian/libglib2.0-0.symbols:
   - Update for API additions.
Checksums-Sha1: 
 cd82caadc49a0de9b5abaef50018d4895c519df1 1686 glib2.0_2.25.7-1.dsc
 4dad2e0f630930b767bc8f8af48b7a08091c9278 8516531 glib2.0_2.25.7.orig.tar.gz
 4cf28ba44f6c7e189c8993cdb67e1d80d0935a13 41647 glib2.0_2.25.7-1.diff.gz
 845e16f42907b05fe9257dd346a96156229ed537 984644 
libglib2.0-data_2.25.7-1_all.deb
 136f1f7a715c39268657de26dc1e29ebdbb63ca9 1788866 
libglib2.0-doc_2.25.7-1_all.deb
 fc40c441674e443fc82e2526cfb840a0d84ef4e7 1297918 
libglib2.0-0_2.25.7-1_amd64.deb
 3a1bd80b26eef02d188c1347029c352940624f4a 1887082 
libglib2.0-udeb_2.25.7-1_amd64.udeb
 eea63a134c97a4f03c4b9f8b17d81d512ec817ce 215640 
libglib2.0-bin_2.25.7-1_amd64.deb
 67c3d704a9bd3cb45759a2df839f6508a4b6b584 1516044 
libglib2.0-dev_2.25.7-1_amd64.deb
 7b010ab3d4e66b892dcc4602b4889a6af4bd402f 1764310 
libglib2.0-0-dbg_2.25.7-1_amd64.deb
 2eaf991324954d65dbc1d379a8f4d5fa6677f9d7 530480 
libglib2.0-0-refdbg_2.25.7-1_amd64.deb
Checksums-Sha256: 
 bfe2b7ecbfe6a10bebcb0e63a6066cc28d65bce7109382cf0af97526a6da245a 1686 
glib2.0_2.25.7-1.dsc
 28f52544ff46b776b6e5c1d1407f77fb7a35d26aa85bab54173256096ecbe000 8516531 
glib2.0_2.25.7.orig.tar.gz
 dc443ac3b7922bca4a06816bb92f4a85825a16c456d9d92a7f22ca348136cb5b 41647 
glib2.0_2.25.7-1.diff.gz
 805aa2ab089821a949db352e4fda0eb21f6c1a738cceca776650bae58733950c 984644 
libglib2.0-data_2.25.7-1_all.deb
 b4398c61474d70da08a93e599167b77adc0e3e11d1e456cbe1842022a1080949 1788866 
libglib2.0-doc_2.25.7-1_all.deb
 fff2faea5da52c8822c3d3975715f5eb6ac11f3883c2cf93d78e697db3db4ddf 1297918 
libglib2.0-0_2.25.7-1_amd64.deb
 41364aa17de906b4a7c364bd1c9bcfe58fd8840c7d52a93d927f1edd977b8d7c 1887082 
libglib2.0-udeb_2.25.7-1_amd64.udeb
 aef896b15711b7c6df435d9272c2e48db5e14d5c3a6cb3303bab5e498e7c7bb4 215640 
libglib2.0-bin_2.25.7-1_amd64.deb
 ea1950dac114262f296f38c2439a8df8ffeaf1ff1a0bab97f4cc0d723b3865e6 1516044 
libglib2.0-dev_2.25.7-1_amd64.deb
 43254440840ef1ebf8e7b229158caf17729e1c96a93e9288dbc033a0b4df 1764310 
libglib2.0-0-dbg_2.25.7-1_amd64.deb
 3a5ad0bdd600a160dfef42d15d7bc9303d20e26fe42e06f9e90465e3be6c7e33 530480 
libglib2.0-0-refdbg_2.25.7-1_amd64.deb
Files: 
 3fccb8c1402c86b00674f9514fee510f 1686 libs optional glib2.0_2.25.7-1.dsc
 ad5a202a7eec32d42aa6c086c45c78fe 8516531 libs optional 
glib2.0_2.25.7.orig.tar.gz
 8aa2002235b057951a72cadd5f6f9393 41647 libs optional glib2.0_2.25.7-1.diff.gz
 a5d4e22dc0fec169585c79cf0609bd3f 984644 libs optional 
libglib2.0-data_2.25.7-1_all.deb
 7efe592711299981bfcd69bb1702dfdd 1788866 doc optional 
libglib2.0-doc_2.25.7-1_all.deb
 b882051c03fff17d1c52fca0d47cf433 1297918 libs optional 
libglib2.0-0_2.25.7-1_amd64.deb
 a76b6971bf3a426b7e93f1e6306bc24d 1887082 debian-installer optional 
libglib2.0-udeb_2.25.7-1_amd64.udeb
 d14006ced37af5559e00debf3ee2224d 215640 misc optional 
libglib2.0-bin_2.25.7-1_amd64.deb
 5d043df9ee30f3d8539a707ea25ad5ad 1516044 libdevel optional 
libglib2.0-dev_2.25.7-1_amd64.deb
 675e13ca1f6b49fe3f59febbada3284f 1764310 debug extra 
libglib2.0-0-dbg_2.25.7-1_amd64.deb
 6a8a25dbe0fc6e5ecdfa5e89e71902b4 530480 debug extra 
libglib2.0-0-refdbg_2.25.7-1_amd64.deb
Package-Type: udeb

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

iEYEARECAAYFAkv7nhYACgkQBsBdh1vkHyHKTgCdHJFiHN3PFlBWcaYZZRMaJO7e
FJQAnjVojdSQ2OMWHeNpXl1aLG3xC251
=c98v
-END PGP SIGNATURE-


Accepted:
glib2.0_2.25.7-1.diff.gz
  to main/g/glib2.0/glib2.0_2.25.7-1.diff.gz
glib2.0_2.25.7-1.dsc
  to main/g/glib2.0/glib2.0_2.25.7-1.dsc
glib2.0_2.25.7.orig.tar.gz
  to main/g/glib2.0/glib2.0_2.25.7.orig.tar.gz
libglib2.0-0-dbg_2.25.7-1_amd64.deb
  to main/g/glib2.0/libglib2.0-0-dbg_2.25.7-1_amd64.deb
libglib2.0-0-refdbg_2.25.7-1_amd64.deb
  to main/g/glib2.0/libglib2.0-0-refdbg_2.25.7-1_amd64.deb
libglib2.0-0_2.25.7-1_amd64.deb
  to main/g/glib2.0/libglib2.0-0_2.25.7-1_amd64.deb

Accepted gobject-introspection 0.6.12-1 (source amd64)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 25 May 2010 11:40:59 +0200
Source: gobject-introspection
Binary: libgirepository1.0-0 libgirepository1.0-dev gobject-introspection 
gir1.0-glib-2.0 gir1.0-freedesktop
Architecture: source amd64
Version: 0.6.12-1
Distribution: unstable
Urgency: low
Maintainer: Sebastian Dröge sl...@debian.org
Changed-By: Sebastian Dröge sl...@debian.org
Description: 
 gir1.0-freedesktop - Introspection data for some FreeDesktop components
 gir1.0-glib-2.0 - Introspection data for GLib, GObject, Gio and GModule
 gobject-introspection - Generate interface introspection data for GObject 
libraries
 libgirepository1.0-0 - Library for handling GObject introspection data 
(runtime library)
 libgirepository1.0-dev - Library for handling GObject introspection data 
(development file
Changes: 
 gobject-introspection (0.6.12-1) unstable; urgency=low
 .
   * New upstream release.
Checksums-Sha1: 
 18f6b615412f98e6242210d6ee475f7569d5a1df 1609 
gobject-introspection_0.6.12-1.dsc
 194ba830070a0fcfdb0bdd7159f803732a75904b 712423 
gobject-introspection_0.6.12.orig.tar.gz
 6f986a01b30252fad1e9ccd7e5fb25632952907a 9822 
gobject-introspection_0.6.12-1.diff.gz
 03524227f0b0939a82e2eb6bc77c92c2c91ffc83 47158 
libgirepository1.0-0_0.6.12-1_amd64.deb
 89dae4082b687a4413c130009629f3b8ba4936a8 261800 
libgirepository1.0-dev_0.6.12-1_amd64.deb
 4edb16fe5d03fa104afae3269aac23e294250326 155958 
gobject-introspection_0.6.12-1_amd64.deb
 07f9c628c237e2f313cf290b0340e777c769a952 125700 
gir1.0-glib-2.0_0.6.12-1_amd64.deb
 0e1557eea0d7ef7009812301f4b891342f8a54d3 15040 
gir1.0-freedesktop_0.6.12-1_amd64.deb
Checksums-Sha256: 
 d743fcf9720d0ec6d4a8adf0f0db7c2f08da9e99c7902bbc1a6596406e366659 1609 
gobject-introspection_0.6.12-1.dsc
 817f55efe53c15ab7a29d2418c0613da14cbab747d8ab2cf31f606fbe487f757 712423 
gobject-introspection_0.6.12.orig.tar.gz
 7642cedad69ec557fad1a7e2638f9a3cbb0b159d89bdbe569eff20ea1d992560 9822 
gobject-introspection_0.6.12-1.diff.gz
 4a3b9167f6e47d53bc2005f0762e6a29281f3a0e4dbf0aa222faff4e775d5051 47158 
libgirepository1.0-0_0.6.12-1_amd64.deb
 5ee7c12db4da74ba71c0da5c89d8267bfd0d1500988fd93c918f96577247f823 261800 
libgirepository1.0-dev_0.6.12-1_amd64.deb
 9622c0bc0e546fd3ad919fdf6144882326d16e56c0f75d32c88f2d2f87a25767 155958 
gobject-introspection_0.6.12-1_amd64.deb
 326373aaa8b688e346f7f31af6ab55822fc665d3b74ca575a61fe0f49e1cd847 125700 
gir1.0-glib-2.0_0.6.12-1_amd64.deb
 1164cf9a62eba10e4ef3efe52765cadc8c079e68132944d02899db215d6287e6 15040 
gir1.0-freedesktop_0.6.12-1_amd64.deb
Files: 
 cadafe18bc88dd7dd2e123f4253ab604 1609 devel optional 
gobject-introspection_0.6.12-1.dsc
 d24d9e961d9932b8d33c4a298b412305 712423 devel optional 
gobject-introspection_0.6.12.orig.tar.gz
 9a09243057c7775f83e31f8900257079 9822 devel optional 
gobject-introspection_0.6.12-1.diff.gz
 847438ed7156114e36bc056f61ca7e97 47158 libs optional 
libgirepository1.0-0_0.6.12-1_amd64.deb
 c98ae882aca02ff73c3369854d004374 261800 libdevel optional 
libgirepository1.0-dev_0.6.12-1_amd64.deb
 b4bf4c610315ee6c4c4f59899615666e 155958 devel optional 
gobject-introspection_0.6.12-1_amd64.deb
 0489e5293cc9695d0d3863f453d94562 125700 libs optional 
gir1.0-glib-2.0_0.6.12-1_amd64.deb
 dcb20bc5be1e1fdad2a3cb69ea59bd57 15040 libs optional 
gir1.0-freedesktop_0.6.12-1_amd64.deb

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

iEYEARECAAYFAkv7nZsACgkQBsBdh1vkHyGqbgCfRlW1335Z/hCqPt+xcJRJNq0T
t+EAoKHH2+5++vjbX8ePmKkjiZbGMO+Z
=BgCN
-END PGP SIGNATURE-


Accepted:
gir1.0-freedesktop_0.6.12-1_amd64.deb
  to main/g/gobject-introspection/gir1.0-freedesktop_0.6.12-1_amd64.deb
gir1.0-glib-2.0_0.6.12-1_amd64.deb
  to main/g/gobject-introspection/gir1.0-glib-2.0_0.6.12-1_amd64.deb
gobject-introspection_0.6.12-1.diff.gz
  to main/g/gobject-introspection/gobject-introspection_0.6.12-1.diff.gz
gobject-introspection_0.6.12-1.dsc
  to main/g/gobject-introspection/gobject-introspection_0.6.12-1.dsc
gobject-introspection_0.6.12-1_amd64.deb
  to main/g/gobject-introspection/gobject-introspection_0.6.12-1_amd64.deb
gobject-introspection_0.6.12.orig.tar.gz
  to main/g/gobject-introspection/gobject-introspection_0.6.12.orig.tar.gz
libgirepository1.0-0_0.6.12-1_amd64.deb
  to main/g/gobject-introspection/libgirepository1.0-0_0.6.12-1_amd64.deb
libgirepository1.0-dev_0.6.12-1_amd64.deb
  to main/g/gobject-introspection/libgirepository1.0-dev_0.6.12-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/e1ogqz2-0001e8...@ries.debian.org

Accepted lm-sensors-3 1:3.1.2-4 (source all amd64)

2010-05-25 Thread Aurelien Jarno

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 25 May 2010 11:33:23 +0200
Source: lm-sensors-3
Binary: lm-sensors libsensors4 libsensors4-dev fancontrol sensord
Architecture: source amd64 all
Version: 1:3.1.2-4
Distribution: unstable
Urgency: low
Maintainer: Aurelien Jarno aure...@debian.org
Changed-By: Aurelien Jarno aure...@debian.org
Description: 
 fancontrol - utilities to read temperature/voltage/fan sensors
 libsensors4 - library to read temperature/voltage/fan sensors
 libsensors4-dev - lm-sensors development kit
 lm-sensors - utilities to read temperature/voltage/fan sensors
 sensord- hardware sensor information logging daemon
Closes: 576932 582979
Changes: 
 lm-sensors-3 (1:3.1.2-4) unstable; urgency=low
 .
   * Check /etc/fancontrol before starting the daemon (closes:
 bug#582979).
   * Add a README.Debian in lm-sensors package. (closes: bug#576932).
Checksums-Sha1: 
 524f40cdf8a3bf9e31d2c76448cf961d24aabf2d 1099 lm-sensors-3_3.1.2-4.dsc
 cc1cec373554d7d424c98542edaba736c93363ea 31326 lm-sensors-3_3.1.2-4.diff.gz
 325529850ba7c6e7d1683f8b218e0920a32f44a5 118208 lm-sensors_3.1.2-4_amd64.deb
 ed57644a8218763c9df6f274278e9036247de2e1 54226 libsensors4_3.1.2-4_amd64.deb
 2f9657d835d524c284f304e295809ca83cb162f6 60830 
libsensors4-dev_3.1.2-4_amd64.deb
 f0b56325c51538c4117cbd3d2bd0ef1aa49d65e8 44212 sensord_3.1.2-4_amd64.deb
 57f86d7de3dd5d9a6e4692758486f21e80882c94 40792 fancontrol_3.1.2-4_all.deb
Checksums-Sha256: 
 a0b6ed6ba030382f2b4d4c88cb99c3d5d3c254ef8675f45ddd24ac5eed7cfdeb 1099 
lm-sensors-3_3.1.2-4.dsc
 757b1ae56edf76ce1e73c659ed928c3f44b9ca0757ab65f2e903525f1a275f91 31326 
lm-sensors-3_3.1.2-4.diff.gz
 27efd22d7b2b216206963820e0f72672686b55392dfa612fd43239d7c4276f24 118208 
lm-sensors_3.1.2-4_amd64.deb
 081a5a46d09e65904676b682201d7b98e7fc7e818ea0647de6ae9de9e81b4b16 54226 
libsensors4_3.1.2-4_amd64.deb
 7f25d0cf5ac2b9522ccb47549939b7abc0f14783249f672cb1c23d23b7aa2d18 60830 
libsensors4-dev_3.1.2-4_amd64.deb
 a2f24856e743bdb6c60c06d305f45c39c66b1af93068d1d8457ea24884b1cfca 44212 
sensord_3.1.2-4_amd64.deb
 c8810db88a3a281edebd788c4a4ddd91aade49a59ddbd9d6ae6173082be7 40792 
fancontrol_3.1.2-4_all.deb
Files: 
 1a74382f2d75a5140d55285f8be1cb5b 1099 utils extra lm-sensors-3_3.1.2-4.dsc
 ef7cbcc90ac7ce60bb233a5193f25e1d 31326 utils extra lm-sensors-3_3.1.2-4.diff.gz
 6e87751ccfe19f7461508006302040cf 118208 utils extra 
lm-sensors_3.1.2-4_amd64.deb
 b0f9ba32de416536982962ebe1d2dad9 54226 libs optional 
libsensors4_3.1.2-4_amd64.deb
 a903f0077150b2076d31bbbe11cf888d 60830 libdevel extra 
libsensors4-dev_3.1.2-4_amd64.deb
 569f26c1c84c11c2a2ae1b58c04765b4 44212 utils extra sensord_3.1.2-4_amd64.deb
 4a74d399ccdda11e38df251cd05cd149 40792 utils extra fancontrol_3.1.2-4_all.deb

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

iD8DBQFL+5qsw3ao2vG823MRAiccAJ4yTS8gUOPAJ99QLhOVE6MdKfJx0wCghFps
JIRRCJkW1x6LE8RMA5J4QQQ=
=ZOS7
-END PGP SIGNATURE-


Accepted:
fancontrol_3.1.2-4_all.deb
  to main/l/lm-sensors-3/fancontrol_3.1.2-4_all.deb
libsensors4-dev_3.1.2-4_amd64.deb
  to main/l/lm-sensors-3/libsensors4-dev_3.1.2-4_amd64.deb
libsensors4_3.1.2-4_amd64.deb
  to main/l/lm-sensors-3/libsensors4_3.1.2-4_amd64.deb
lm-sensors-3_3.1.2-4.diff.gz
  to main/l/lm-sensors-3/lm-sensors-3_3.1.2-4.diff.gz
lm-sensors-3_3.1.2-4.dsc
  to main/l/lm-sensors-3/lm-sensors-3_3.1.2-4.dsc
lm-sensors_3.1.2-4_amd64.deb
  to main/l/lm-sensors-3/lm-sensors_3.1.2-4_amd64.deb
sensord_3.1.2-4_amd64.deb
  to main/l/lm-sensors-3/sensord_3.1.2-4_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/e1ogqzk-0001l4...@ries.debian.org

Accepted gnome-randr-applet 0.4.1-1 (source amd64)

2010-05-25 Thread Barak A. Pearlmutter

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 14 May 2010 12:27:29 +0100
Source: gnome-randr-applet
Binary: gnome-randr-applet
Architecture: source amd64
Version: 0.4.1-1
Distribution: unstable
Urgency: low
Maintainer: Barak A. Pearlmutter b...@debian.org
Changed-By: Barak A. Pearlmutter b...@debian.org
Description: 
 gnome-randr-applet - Simple gnome-panel front end to the xrandr extension
Closes: 402779 453121 515442
Changes: 
 gnome-randr-applet (0.4.1-1) unstable; urgency=low
 .
   * New upstream version (closes: #453121)
   * New maintainer picking up package
   * Modernise packaging, including build dependencies (closes: #515442)
   * Fiddle with GrandrApplet.server.in (closes: #402779)
Checksums-Sha1: 
 20bba08b3bca7ed168839ecf4a48e3b95dfaf843 1388 gnome-randr-applet_0.4.1-1.dsc
 b388f5528e674d24d2d9ee8f5d34a845fa8d1209 161142 
gnome-randr-applet_0.4.1.orig.tar.gz
 92f720b0b159c0e7f0e8228cf609d543d76659f4 204341 
gnome-randr-applet_0.4.1-1.debian.tar.gz
 1f0c2d0d2605f93f5e81eee6286e00c2792a026f 12736 
gnome-randr-applet_0.4.1-1_amd64.deb
Checksums-Sha256: 
 ae7a1b7cefa613bafe650c9beadbc95ded11515e0b9d3adc522f31cdfd5e069b 1388 
gnome-randr-applet_0.4.1-1.dsc
 8a2041759cb77d0222a2e12833d570a1bcf4813475f40cf3a45cace136726a29 161142 
gnome-randr-applet_0.4.1.orig.tar.gz
 d3f4c4019ec82b15a5f4ee07c45a161c866dfbbad8de07baecf4adfb3bcee6af 204341 
gnome-randr-applet_0.4.1-1.debian.tar.gz
 209965ae7ac51ff6a332b1db5197a8755a0b08eddd93d51841d1598f93454cad 12736 
gnome-randr-applet_0.4.1-1_amd64.deb
Files: 
 04d17f162168234b6b85a2c43987d00e 1388 gnome optional 
gnome-randr-applet_0.4.1-1.dsc
 e5503535fad10b1f6e97ed1c1af18960 161142 gnome optional 
gnome-randr-applet_0.4.1.orig.tar.gz
 95570a16797984963cd6b45cd77910d9 204341 gnome optional 
gnome-randr-applet_0.4.1-1.debian.tar.gz
 e7d1cf988c68a9d786918e27f0642348 12736 gnome optional 
gnome-randr-applet_0.4.1-1_amd64.deb

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

iEYEARECAAYFAkvtP6AACgkQLz4Gnv7CP7Lb4QCgjPv8qx8k6lecQfyfO3Lz3bBY
0CgAn20RqMymmCKMnXgltr8e/QepVWqP
=4TXX
-END PGP SIGNATURE-


Accepted:
gnome-randr-applet_0.4.1-1.debian.tar.gz
  to main/g/gnome-randr-applet/gnome-randr-applet_0.4.1-1.debian.tar.gz
gnome-randr-applet_0.4.1-1.dsc
  to main/g/gnome-randr-applet/gnome-randr-applet_0.4.1-1.dsc
gnome-randr-applet_0.4.1-1_amd64.deb
  to main/g/gnome-randr-applet/gnome-randr-applet_0.4.1-1_amd64.deb
gnome-randr-applet_0.4.1.orig.tar.gz
  to main/g/gnome-randr-applet/gnome-randr-applet_0.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/e1ogrc7-0002ze...@ries.debian.org

Accepted autodir 0.99.9-6 (source i386)

2010-05-25 Thread Francesco Paolo Lovergine

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 17 May 2010 12:45:11 +0200
Source: autodir
Binary: autodir
Architecture: source i386
Version: 0.99.9-6
Distribution: unstable
Urgency: low
Maintainer: Francesco Paolo Lovergine fran...@debian.org
Changed-By: Francesco Paolo Lovergine fran...@debian.org
Description: 
 autodir- Automatically creates home and group directories for LDAP/NIS/SQL
Changes: 
 autodir (0.99.9-6) unstable; urgency=low
 .
   * Moved to main.
   * Copyright set to GPL2+, as stated in the code.
   * Removed HOWTO documents provided in the debian/ area and released as CC-A 
v2.
   * README.Debian now points the howto on the autodir site.
Checksums-Sha1: 
 a2eb0e077cdeeedec43d0de7e114a6e24af72c22 1051 autodir_0.99.9-6.dsc
 2ca359f64eea927d0bb775e99376e0ee25a29800 25875 autodir_0.99.9-6.diff.gz
 062f12d58fd473dbcf69649b099bd995c34307a9 47468 autodir_0.99.9-6_i386.deb
Checksums-Sha256: 
 d85b66880af2b3d1ba62703619dad77823c486ec041f6fe05817171cb226e883 1051 
autodir_0.99.9-6.dsc
 c565350200e9cd3527a8e29eb7740ca0d9fcf20c7ca16689213b632a7481ddd1 25875 
autodir_0.99.9-6.diff.gz
 2e1aadb6920f5a285657a1908ea94ddfa97ab4105ca60fca13a0b53c7fabc43d 47468 
autodir_0.99.9-6_i386.deb
Files: 
 8b0d8509ea85d824cf7301a31fd137df 1051 utils optional autodir_0.99.9-6.dsc
 224e5ce9332681e2ee23465229ffa1f7 25875 utils optional autodir_0.99.9-6.diff.gz
 d9e72fbd93267bf812d3c64a6a2bc4b5 47468 utils optional autodir_0.99.9-6_i386.deb

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

iEYEARECAAYFAkvxMD4ACgkQpFNRmenyx0cMNACgiSPXxaqsWPuWeyojX6VI2+wA
ujkAoKN03aOuEMWhl19QkfIXZY15YkD6
=OTMH
-END PGP SIGNATURE-


Accepted:
autodir_0.99.9-6.diff.gz
  to main/a/autodir/autodir_0.99.9-6.diff.gz
autodir_0.99.9-6.dsc
  to main/a/autodir/autodir_0.99.9-6.dsc
autodir_0.99.9-6_i386.deb
  to main/a/autodir/autodir_0.99.9-6_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/e1ogrqe-0003lu...@ries.debian.org

Accepted klick 0.12.2-1 (source i386)

2010-05-25 Thread Jaromír Mikeš

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 25 Apr 2010 16:25:37 +0200
Source: klick
Binary: klick
Architecture: source i386
Version: 0.12.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers 
pkg-multimedia-maintain...@lists.alioth.debian.org
Changed-By: Jaromír Mikeš mira.mi...@seznam.cz
Description: 
 klick  - advanced metronome for JACK
Closes: 579165
Changes: 
 klick (0.12.2-1) unstable; urgency=low
 .
   * Initial release (Closes: #579165).
Checksums-Sha1: 
 b3c1aa42d8faa0678f81c0e1ff88cacbc43850f0 1387 klick_0.12.2-1.dsc
 882645aeb214162ad9e7dfc68d804b9ba67cb9b4 111801 klick_0.12.2.orig.tar.gz
 af496418e759fe94b4efc4aafc06d80383570541 2943 klick_0.12.2-1.diff.gz
 ce502048f571f593334cebc7cbd29c8a8685376a 171544 klick_0.12.2-1_i386.deb
Checksums-Sha256: 
 818b7ee730b70973a94d3fc4e5d726beacdd9d8c49f964df48adcd1e8474be9b 1387 
klick_0.12.2-1.dsc
 1289533c0849b1b66463bf27f7ce5f71736b655cfb7672ef884c7e6eb957ac42 111801 
klick_0.12.2.orig.tar.gz
 d831226a2cd96441fb34c2a3347eae4508484f3d1bc5bd600841d0b9056258bc 2943 
klick_0.12.2-1.diff.gz
 edb4828ed5dee2cd60b36aeb1f58a8f3d325e04a7735d8c5a4d008f51588a8b1 171544 
klick_0.12.2-1_i386.deb
Files: 
 2b4f90f1b393374c49eb11187bf03c86 1387 sound optional klick_0.12.2-1.dsc
 90bc69db650c6edaa08be47df0cfe424 111801 sound optional klick_0.12.2.orig.tar.gz
 3abb1d9457685eab2c3b36b1b6dd4432 2943 sound optional klick_0.12.2-1.diff.gz
 684a0c92144ba00c0c5513d29229af6d 171544 sound optional klick_0.12.2-1_i386.deb

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

iEYEARECAAYFAkvYkLQACgkQ5qqQFxOSsXRHCQCgnwAIsuEnCxOgP4XAkg2pqD9t
R/4An1FT/UWUPQYNi6egx4SRvS2sdVsP
=iBIp
-END PGP SIGNATURE-


Accepted:
klick_0.12.2-1.diff.gz
  to main/k/klick/klick_0.12.2-1.diff.gz
klick_0.12.2-1.dsc
  to main/k/klick/klick_0.12.2-1.dsc
klick_0.12.2-1_i386.deb
  to main/k/klick/klick_0.12.2-1_i386.deb
klick_0.12.2.orig.tar.gz
  to main/k/klick/klick_0.12.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/e1ogrr0-0003ox...@ries.debian.org

Accepted mrtrix 0.2.8-1 (source i386 all)

2010-05-25 Thread Michael Hanke

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sun, 25 Apr 2010 12:47:51 -0400
Source: mrtrix
Binary: mrtrix mrtrix-doc
Architecture: source i386 all
Version: 0.2.8-1
Distribution: unstable
Urgency: low
Maintainer: Michael Hanke michael.ha...@gmail.com
Changed-By: Michael Hanke michael.ha...@gmail.com
Description: 
 mrtrix - diffusion-weighted MRI white matter tractography
 mrtrix-doc - documentation for mrtrix
Closes: 579470
Changes: 
 mrtrix (0.2.8-1) unstable; urgency=low
 .
   * Initial Debian packaging based on debhelper's dh and using the new source
 package format 3.0 (quilt). Closes: #579470.
Checksums-Sha1: 
 97d60dbead116809dc997b75f5d77da88bc8716b 1261 mrtrix_0.2.8-1.dsc
 c834eaba7410ffab09c5bda548463c974c8f5a09 3172920 mrtrix_0.2.8.orig.tar.bz2
 87bebce96cb7e39580a4a9beec40754519e3d842 3440 mrtrix_0.2.8-1.debian.tar.gz
 47a5cc848ab2e4ff5b5968e3de2696799dc0b09d 2252440 mrtrix_0.2.8-1_i386.deb
 c52ad282922e6e6ebaa0b73afe3cc35f9ccab1a0 2949036 mrtrix-doc_0.2.8-1_all.deb
Checksums-Sha256: 
 90eb8fd7aad28b619e0076dac5317f4e34da3a56d4a58bbb76da1dbd214206fc 1261 
mrtrix_0.2.8-1.dsc
 55844a218c3d43b4972cd8881b6a66ab97efbb3c11d654acb3bc3091363437d8 3172920 
mrtrix_0.2.8.orig.tar.bz2
 34ebc2b7bb201652b95935ed86077b2e72c5cbace192c306e60eecd105797dc8 3440 
mrtrix_0.2.8-1.debian.tar.gz
 9e6f12823e224726a8a003f4dbedb480ceeb89c5a1cffc313e52180ae373a92a 2252440 
mrtrix_0.2.8-1_i386.deb
 ab0eef700103bfcb8450236ac70888e71b76b32e4df13ba73abcc16bb77413e6 2949036 
mrtrix-doc_0.2.8-1_all.deb
Files: 
 8adf6387f3a2cc4bddce1a2c061966a7 1261 science extra mrtrix_0.2.8-1.dsc
 7d46370cd0c43f075007799051e9b290 3172920 science extra 
mrtrix_0.2.8.orig.tar.bz2
 8237a528d73f519e0404bef4b80fce3b 3440 science extra 
mrtrix_0.2.8-1.debian.tar.gz
 658c75a095c0bc87ba32d0cdaf0f4d5b 2252440 science extra mrtrix_0.2.8-1_i386.deb
 224417502b5e2bb7afb534e6e1ac3b32 2949036 doc extra mrtrix-doc_0.2.8-1_all.deb

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

iEYEARECAAYFAkvYO7IACgkQjRFFY3XAJMjr7ACfYe4jbfPSE4s9PDttXqkbLr/u
ycIAn3ebvp1XIG4Z8QFesDwozHo+lNL5
=3GPg
-END PGP SIGNATURE-


Accepted:
mrtrix-doc_0.2.8-1_all.deb
  to main/m/mrtrix/mrtrix-doc_0.2.8-1_all.deb
mrtrix_0.2.8-1.debian.tar.gz
  to main/m/mrtrix/mrtrix_0.2.8-1.debian.tar.gz
mrtrix_0.2.8-1.dsc
  to main/m/mrtrix/mrtrix_0.2.8-1.dsc
mrtrix_0.2.8-1_i386.deb
  to main/m/mrtrix/mrtrix_0.2.8-1_i386.deb
mrtrix_0.2.8.orig.tar.bz2
  to main/m/mrtrix/mrtrix_0.2.8.orig.tar.bz2


-- 
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/e1ogrrs-00040g...@ries.debian.org

Accepted zbar 0.10+doc-1 (source amd64)

2010-05-25 Thread Bernd Zeimetz

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 25 May 2010 02:09:41 +0200
Source: zbar
Binary: zbar-tools zbar-dbg libzbar0 libzbar-dev python-zbar python-zbarpygtk 
libzbargtk0 libzbargtk-dev libzbarqt0 libzbarqt-dev libbarcode-zbar-perl
Architecture: source amd64
Version: 0.10+doc-1
Distribution: unstable
Urgency: low
Maintainer: Bernd Zeimetz b...@debian.org
Changed-By: Bernd Zeimetz b...@debian.org
Description: 
 libbarcode-zbar-perl - bar code scanner and decoder (Perl bindings)
 libzbar-dev - bar code scanner and decoder (development)
 libzbar0   - bar code scanner and decoder (library)
 libzbargtk-dev - bar code scanner and decoder (GTK+ bindings development)
 libzbargtk0 - bar code scanner and decoder (GTK+ bindings)
 libzbarqt-dev - bar code scanner and decoder (Qt bindings development)
 libzbarqt0 - bar code scanner and decoder (Qt bindings)
 python-zbar - bar code scanner and decoder (Python bindings)
 python-zbarpygtk - bar code scanner and decoder (PyGTK bindings)
 zbar-dbg   - bar code scanner and decoder (debug)
 zbar-tools - bar code scanner and decoder (utilities)
Closes: 543881
Changes: 
 zbar (0.10+doc-1) unstable; urgency=low
 .
   * Import full upstream source including the doc folder and drop
 the dfsg part in the version (using +doc now as we need a version
 greater than 0.10+dfsg. See the changelog below and debian/copyright
 for details
 .
   * [1f9232b1] Add missing dependencies to libzbar-dev.
   * [577bae53] Tidy .docs files - one debian/docs is enough.
   * [b77a29e5] Python-related packages: Fix dependencies and build
 python-zbar.
   * [6a336b40] Adopt package (Closes: #543881)
   * [d3e7838d] gbp.conf: Remove filter option for git-import-orig.
 Upstream clarified the license for the doc folder, the documentation
 is (and was) under the same license as the rest of the zbar project.
 The former package maintainer just did not bother to ask.
 (http://zbar.hg.sourceforge.net/hgweb/zbar/zbar/rev/a400dd46fb4a)
   * [d9f0f3bd] Remove quilt - no patches necessary anymore.
   * [8e9b2f81] Adding watch file.
   * [ddfdb3db] Merge commit 'upstream/0.10+doc'
   * [4c547f3a] Build zbar for all supported Python versions. Also build
 debug extensions.
   * [c6dbc26d] Ensure proper sonames while installing libraries.
   * [74e55643] Update supported codes in descriptions.
   * [54969382] Install README file into docs.
   * [3d97e382] Updating copyright file.
   * [71bfc1fe] Install manpages for zbar-tools.
   * [9de7a34a] Remove --fail-missing from dh_install call.
   * [39a37679] Add symbol files for libraries.
   * [418ee09b] Be paranoid about symbol files - pass -c4 to dpkg-
 gensymbols.
   * [a1527ed7] Use -L to link against previously built libs.
   * [c672ecc8] Don't include symbols, which are removed by strip, in
 symbols file.
   * [9b93453e] Build Perl bindings into libbarcode-zbar-perl.
   * [76b32218] According to lintian zbar-dbg needs to Depend on all
 packages.
   * [2cb6d478] python-zbar needs to conflict/replace older versions of
 python-zbarpygtk.
   * [bca1a7dc] Better wording for short description.
   * [4f6fdf16] Ensure perl bindings are built without rpath.
   * [df98e89f] Add missing dh_perl call.
   * [18539f50] Add comment about licenses of doc/* to debian/copyright.
   * [2bb4fb29] zbar-dbg needs to depend on python-gtk2-dbg.
   * [3da1a01e] Add VCS information.
Checksums-Sha1: 
 7161955baf227c4010caf78f5b4fb5fd63f9c4ff 1416 zbar_0.10+doc-1.dsc
 ec09cbd18a044cc95953dd3e00c48312aeb4ff79 714457 zbar_0.10+doc.orig.tar.gz
 30efef1cb59765d65c8180115f6695bb439b9270 8314 zbar_0.10+doc-1.diff.gz
 e0534885ddac5f8cce6f4b5a4957a910a469d3be 37068 zbar-tools_0.10+doc-1_amd64.deb
 a88f6dccf9419e4b37590fd198f3460728c77108 725338 zbar-dbg_0.10+doc-1_amd64.deb
 21a359ebd7ef9dddb373cd4517461857150ab05d 114426 libzbar0_0.10+doc-1_amd64.deb
 cfc0851d60db8b17c9dd079d03d37e25373fa8ae 151742 
libzbar-dev_0.10+doc-1_amd64.deb
 f9a89b9db7a4d879c394f6340f883419d9cdaea9 46940 python-zbar_0.10+doc-1_amd64.deb
 0508d254b6eee376342014230ff679a55816e378 19240 
python-zbarpygtk_0.10+doc-1_amd64.deb
 1bdf5660de9852e3de8660e86b45925947b04e7c 24872 libzbargtk0_0.10+doc-1_amd64.deb
 c45c245d2143ca95be02ea4af7f1dc1791f0e6c5 25618 
libzbargtk-dev_0.10+doc-1_amd64.deb
 57b5c662ab6ea2185955209d72bc7b9e62bf4e1a 44280 libzbarqt0_0.10+doc-1_amd64.deb
 1a1b2f59b29def760f1b1d7b8497d9b960f88a7f 53332 
libzbarqt-dev_0.10+doc-1_amd64.deb
 3e9541e706d88856f5de1356ae50c9f42f6cdaae 69666 
libbarcode-zbar-perl_0.10+doc-1_amd64.deb
Checksums-Sha256: 
 7516447e2a6d57cf97e66a341bc778995691105510e280ea086f8e31fccdb21d 1416 
zbar_0.10+doc-1.dsc
 5db2a9bb53f4ae7ec5d2791a1ad347fe7567f4e71fc893fcedb5766bc8b2a710 714457 
zbar_0.10+doc.orig.tar.gz
 ba2d52a79b7cb9277276b4b777130c64a1dd227eed1efab12cf55277bac89a63 8314 
zbar_0.10+doc-1.diff.gz
 89f0dedbe93fdcaaf7ee1899c7514ad9c85fdda8656b74678e75d55f1f28b68f 37068 
zbar-tools_0.10+doc-1_amd64.deb

Accepted gconf 2.31.3-1 (source all amd64)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 25 May 2010 11:56:39 +0200
Source: gconf
Binary: gconf2 gconf2-common gconf-defaults-service libgconf2-4 libgconf2-dev
Architecture: source all amd64
Version: 2.31.3-1
Distribution: experimental
Urgency: low
Maintainer: Josselin Mouette j...@debian.org
Changed-By: Sebastian Dröge sl...@debian.org
Description: 
 gconf-defaults-service - GNOME configuration database system (system defaults 
service)
 gconf2 - GNOME configuration database system (support tools)
 gconf2-common - GNOME configuration database system (common files)
 libgconf2-4 - GNOME configuration database system (shared libraries)
 libgconf2-dev - GNOME configuration database system (development)
Changes: 
 gconf (2.31.3-1) experimental; urgency=low
 .
   * New upstream development release:
 + debian/gconf2.install:
   - Add autostart file for GSettings.
Checksums-Sha1: 
 20e146d7c2add4c6de20322a20e8bcf8372d07e9 1758 gconf_2.31.3-1.dsc
 b22abf7698599b03421e8ce5b001cc22ea1fb5c2 2513332 gconf_2.31.3.orig.tar.gz
 0404450f3f21b8161b8005c067e476269be61d8a 21833 gconf_2.31.3-1.diff.gz
 a2f6ce68bfbb59bdbb5b23073117ab5b6d0048b6 1689054 gconf2-common_2.31.3-1_all.deb
 418f40acc9200c3b44f5c231e36ff2c7de67ac67 160594 gconf2_2.31.3-1_amd64.deb
 38b14ee07a1d2cfaab3b24d8650717f9f17c9759 112954 
gconf-defaults-service_2.31.3-1_amd64.deb
 f8653fcffba2da979f9f70d4e2198d5308e2339f 286416 libgconf2-4_2.31.3-1_amd64.deb
 31951e1460de73f670739c66256d8848b0ad2ad5 311036 
libgconf2-dev_2.31.3-1_amd64.deb
Checksums-Sha256: 
 b054b14af5be5ed449eac5e0b50da50afb6edd93f7d8edb8442e85a7e5a3d2f3 1758 
gconf_2.31.3-1.dsc
 3ac13b79755c9eab15a14e1505e415a57af2f740521b53a5adc2731ff39ddd08 2513332 
gconf_2.31.3.orig.tar.gz
 6c4051e8cd48d3f9ba7852fa5b873d5a53224fb8d50d5297306c035f41972b0d 21833 
gconf_2.31.3-1.diff.gz
 eb289f6a44d00b64d542e507475f62ec3f257fc4678742cc44746b2bcdcdf332 1689054 
gconf2-common_2.31.3-1_all.deb
 d591234ee898e8d404242defcec644471d8334394dd113c2a9279c037d7007e6 160594 
gconf2_2.31.3-1_amd64.deb
 0c5b8b9e3afa7bb117bb56eb0dec253d49cf57bd255c4ead6c169e5cb260d162 112954 
gconf-defaults-service_2.31.3-1_amd64.deb
 6f0228c32e8751fdb47a7f4d8dd64d9daa8d7f671423f3493e8ad361698816ff 286416 
libgconf2-4_2.31.3-1_amd64.deb
 e917420e989c30e80f9647eb3f7ca737246788ebaaf1ebefb6bd9162848bae70 311036 
libgconf2-dev_2.31.3-1_amd64.deb
Files: 
 9a9827e58bd366208656f855bd92668c 1758 libs optional gconf_2.31.3-1.dsc
 fe47117ea9984744012893f6e5cd2247 2513332 libs optional gconf_2.31.3.orig.tar.gz
 4e507272c186f6ea9f0f054023457593 21833 libs optional gconf_2.31.3-1.diff.gz
 1528975c289dce82714265dfa65b3ce8 1689054 libs optional 
gconf2-common_2.31.3-1_all.deb
 ff0e8b026da7dae46d7ae4b2ec9d469d 160594 libs optional gconf2_2.31.3-1_amd64.deb
 39508b88c73daf2de442824a6bc4b216 112954 libs optional 
gconf-defaults-service_2.31.3-1_amd64.deb
 c8927645f762372dc31d5374146ce974 286416 libs optional 
libgconf2-4_2.31.3-1_amd64.deb
 fdf65b4245832a8b71bd83e446d92de9 311036 libdevel optional 
libgconf2-dev_2.31.3-1_amd64.deb

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

iEYEARECAAYFAkv7pOQACgkQBsBdh1vkHyHJTQCfaaK2A4KfXEW7mGmdkdOBAP7f
+2QAnjCHI6pRi8Vdd1KLRFEOPeojPFY1
=bS6G
-END PGP SIGNATURE-


Accepted:
gconf-defaults-service_2.31.3-1_amd64.deb
  to main/g/gconf/gconf-defaults-service_2.31.3-1_amd64.deb
gconf2-common_2.31.3-1_all.deb
  to main/g/gconf/gconf2-common_2.31.3-1_all.deb
gconf2_2.31.3-1_amd64.deb
  to main/g/gconf/gconf2_2.31.3-1_amd64.deb
gconf_2.31.3-1.diff.gz
  to main/g/gconf/gconf_2.31.3-1.diff.gz
gconf_2.31.3-1.dsc
  to main/g/gconf/gconf_2.31.3-1.dsc
gconf_2.31.3.orig.tar.gz
  to main/g/gconf/gconf_2.31.3.orig.tar.gz
libgconf2-4_2.31.3-1_amd64.deb
  to main/g/gconf/libgconf2-4_2.31.3-1_amd64.deb
libgconf2-dev_2.31.3-1_amd64.deb
  to main/g/gconf/libgconf2-dev_2.31.3-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/e1ogruz-00056v...@ries.debian.org

Accepted bley 0.1.1-1 (source all)

2010-05-25 Thread Evgeni Golov

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 27 Apr 2010 18:47:41 +0200
Source: bley
Binary: bley
Architecture: source all
Version: 0.1.1-1
Distribution: unstable
Urgency: low
Maintainer: Evgeni Golov evg...@debian.org
Changed-By: Evgeni Golov evg...@debian.org
Description: 
 bley   - intelligent greylisting daemon for Postfix
Closes: 578491
Changes: 
 bley (0.1.1-1) unstable; urgency=low
 .
   * Initial release (Closes: #578491)
Checksums-Sha1: 
 a03ea2c10b021eac25193e8e275b529b444e104b 1028 bley_0.1.1-1.dsc
 167f5d2106e79874af8a9ab7b971d7badb58a326 8705 bley_0.1.1.orig.tar.gz
 6e7abbb40c5456d0b93cad0ae5eb80654b55548b 4979 bley_0.1.1-1.debian.tar.gz
 af0af370a91ed7ce3170f5a466cde6709f6ed8f8 13806 bley_0.1.1-1_all.deb
Checksums-Sha256: 
 0075b64c22f81ad364afdfd3d5256a28ce75e87d99b3c08e937c3dcc9d45d092 1028 
bley_0.1.1-1.dsc
 532045bab6082909c42851d3ca128a953e3cfe3e5416ad92960a749b49cad5d2 8705 
bley_0.1.1.orig.tar.gz
 b8b458640d2d3cf41626490cf963c018d734bcf155418c144900e7fd6f521d3b 4979 
bley_0.1.1-1.debian.tar.gz
 24be7a354d17fde952e1bbda33628e42754f86fed35b399b3dc1324bf1c8d804 13806 
bley_0.1.1-1_all.deb
Files: 
 d45a379a7530aa15fa1dc480c08bf949 1028 mail optional bley_0.1.1-1.dsc
 70def26577692254ee075a302eda4e1f 8705 mail optional bley_0.1.1.orig.tar.gz
 8ca0d3d419654d57cc712ed285831525 4979 mail optional bley_0.1.1-1.debian.tar.gz
 1228fc74f1d4c9abe18b4105714c87db 13806 mail optional bley_0.1.1-1_all.deb

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

iEYEARECAAYFAkvZV2sACgkQJKAUGKwVtQz3tACZAWIpOJbW40oeHpGfAFxkDTje
zxwAn2760ZaCC86fuevceD+ytaBsQLBC
=7sYX
-END PGP SIGNATURE-


Accepted:
bley_0.1.1-1.debian.tar.gz
  to main/b/bley/bley_0.1.1-1.debian.tar.gz
bley_0.1.1-1.dsc
  to main/b/bley/bley_0.1.1-1.dsc
bley_0.1.1-1_all.deb
  to main/b/bley/bley_0.1.1-1_all.deb
bley_0.1.1.orig.tar.gz
  to main/b/bley/bley_0.1.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/e1ogrf8-0005ib...@ries.debian.org

Accepted latexila 0.2.0-1 (source all amd64)

2010-05-25 Thread Tanguy Ortolo

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Mon, 26 Apr 2010 22:13:00 +0200
Source: latexila
Binary: latexila latexila-data
Architecture: source amd64 all
Version: 0.2.0-1
Distribution: unstable
Urgency: low
Maintainer: Tanguy Ortolo tanguy+deb...@ortolo.eu
Changed-By: Tanguy Ortolo tanguy+deb...@ortolo.eu
Description: 
 latexila   - LaTeX editor designed for the GNOME desktop
 latexila-data - LaTeXila editor -- arch-independent files
Closes: 579279
Changes: 
 latexila (0.2.0-1) unstable; urgency=low
 .
   * Initial release. (Closes: #579279)
Checksums-Sha1: 
 81123873206b56174ac593819433bdbe4dc3a9d4 1252 latexila_0.2.0-1.dsc
 fcb59d1628cd37d72a1c7bdc243705e088eca01c 323027 latexila_0.2.0.orig.tar.gz
 e288f8521ca3b2c409d70f6923171c2040978bda 6443 latexila_0.2.0-1.debian.tar.gz
 a0bf9eb64b86cdd7117450dda8ed1e45be3f3c6c 80442 latexila_0.2.0-1_amd64.deb
 bfe3842efc9bbd3b52e613fdab25f3f5fffcb449 237942 latexila-data_0.2.0-1_all.deb
Checksums-Sha256: 
 822686b3bb98c8c6a9e87e8a506022b3583533c5a6c5daf8106bcb9c4489ba8d 1252 
latexila_0.2.0-1.dsc
 e47da8cb9b8322fdf81bfedc4e2f5cdf322b949d09db192b7ec37925cfba7119 323027 
latexila_0.2.0.orig.tar.gz
 0b79bfde072467207552e18eb9c175e2e0a498a5d19a0c035ac08b5194033f4d 6443 
latexila_0.2.0-1.debian.tar.gz
 734aabc645be77363f80f334383b633bb180bf50b779d2bc906863b13b0f78d4 80442 
latexila_0.2.0-1_amd64.deb
 5dc647b7e71f2866799e34b912cc79c4eaa3e43bd93ceffd30c10bdcd4a79f48 237942 
latexila-data_0.2.0-1_all.deb
Files: 
 e9ba3ba05b8c3d91b9c60428f01d9e6a 1252 tex optional latexila_0.2.0-1.dsc
 bcf97fa5faf6a5a709fb7a2e43daa993 323027 tex optional latexila_0.2.0.orig.tar.gz
 9d6a449373178f7689f15c3ff4fe44d3 6443 tex optional 
latexila_0.2.0-1.debian.tar.gz
 38898d188fb4a59304820da1de3981e8 80442 tex optional latexila_0.2.0-1_amd64.deb
 7e9593ab97f66f588764f9f7c0684ea3 237942 tex optional 
latexila-data_0.2.0-1_all.deb

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

iD8DBQFL2Mhp0r9KownFsJQRAvXsAJ4me5N6EQXgHDZzRHJBuCPzU97+twCePxYl
BvLC+FqM6MjRiBbRbWtECeo=
=Wj1Y
-END PGP SIGNATURE-


Accepted:
latexila-data_0.2.0-1_all.deb
  to main/l/latexila/latexila-data_0.2.0-1_all.deb
latexila_0.2.0-1.debian.tar.gz
  to main/l/latexila/latexila_0.2.0-1.debian.tar.gz
latexila_0.2.0-1.dsc
  to main/l/latexila/latexila_0.2.0-1.dsc
latexila_0.2.0-1_amd64.deb
  to main/l/latexila/latexila_0.2.0-1_amd64.deb
latexila_0.2.0.orig.tar.gz
  to main/l/latexila/latexila_0.2.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/e1ogrfu-0005lr...@ries.debian.org

Accepted verilator 3.801-1 (source i386)

2010-05-25 Thread Ahmed El-Mahmoudy

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 21 Apr 2010 23:33:46 +0200
Source: verilator
Binary: verilator
Architecture: source i386
Version: 3.801-1
Distribution: unstable
Urgency: low
Maintainer: Debian Electronics Team 
pkg-electronics-de...@lists.alioth.debian.org
Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) aelmahmo...@sabily.org
Description: 
 verilator  - fast free Verilog simulator
Closes: 577187
Changes: 
 verilator (3.801-1) unstable; urgency=low
 .
   * New upstream release (Closes: #577187)
   * Switched to 3.0 (quilt) source format.
   * debian/control:
 + Set pkg-electronics as Maintainer and add myself to Uploaders.
 + Bumped Standards-Version to 3.8.4
 + Added proper Vcs-* fields.
 + Removed the from package description.
 + Added DMUA
   * debian/docs:
 + Remove README  readme.pod since they do not provide useful information
   to user.
 + Added verilator.html  verilator.pdf
   * debian/watch: set the upstream URL to one that can be checked.
   * Added manpage for verilator_profcfunc
   * Added debian/links, debian/doc-base, debian/manpages
   * Remove debian/dirs
   * debian/rules:
 + No more need to override dh_auto_test since upstream now skips SystemC
   tests if SystemC is not installed.
 + No need to override dh_auto_install
 + Override dh_installexamples to move examples dir from
   /usr/share/verilator to /usr/share/doc/verilator
   * Added install_perms.diff patch to install data files without executable
 permissions.
   * Added typos.diff patch to fix some spelling mistakes in verilator
 executable  manpage.
   * Added shebang.diff patch to add proper shebangs.
   * debian/copyright:
 + Converted to machine-readable format.
 + Changed packaging license to match that of upstream.
Checksums-Sha1: 
 eff24b4afb1c758e50401ecd519747d7fd534d65 1345 verilator_3.801-1.dsc
 20da19c6ca404a88374c3304f042ba625bbb2b6d 1501379 verilator_3.801.orig.tar.gz
 8c06c8df4760ba407f6b84bd9f394f1406ce5819 7864 verilator_3.801-1.debian.tar.gz
 0881ab1313d8165543621fde8e637f3eb7e9a828 2625130 verilator_3.801-1_i386.deb
Checksums-Sha256: 
 8cbfc60ba386b1c5a340ea91f6cee36460fd7007bf3225e514ca0d9ff63e5fe7 1345 
verilator_3.801-1.dsc
 9192b200155d54a494f25611010fc0cb9e72857d87c199c2f731ab423c5cabe5 1501379 
verilator_3.801.orig.tar.gz
 5171cc4c24df11e3abecbf46975b24beaf46459de296a0dc0436ad1f3f4a6e1a 7864 
verilator_3.801-1.debian.tar.gz
 1790250a0ee01183442d71dccfafc92246cdde5f42d08836f13e54932f419b8e 2625130 
verilator_3.801-1_i386.deb
Files: 
 c8d96b4d0592883ed60d0b6cf193691f 1345 electronics optional 
verilator_3.801-1.dsc
 ca7b264c571fc1a4b2257ae341f0796d 1501379 electronics optional 
verilator_3.801.orig.tar.gz
 cc0f7e1315535c1349465178f76a82d0 7864 electronics optional 
verilator_3.801-1.debian.tar.gz
 1f10a1db9f782f1cfc8ef3fda16a37a4 2625130 electronics optional 
verilator_3.801-1_i386.deb

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

iEYEARECAAYFAkvYoEUACgkQ8KmKTEzW49LgqwCggaMOe+ShNsC7Zj2N5Pe6hYHX
c60Amwb6EaCvcLzAGWGkH79s/mI3iNK3
=AHwk
-END PGP SIGNATURE-


Accepted:
verilator_3.801-1.debian.tar.gz
  to main/v/verilator/verilator_3.801-1.debian.tar.gz
verilator_3.801-1.dsc
  to main/v/verilator/verilator_3.801-1.dsc
verilator_3.801-1_i386.deb
  to main/v/verilator/verilator_3.801-1_i386.deb
verilator_3.801.orig.tar.gz
  to main/v/verilator/verilator_3.801.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/e1ogrfr-0005o5...@ries.debian.org

Accepted gnumed-client 0.7.4-1 (source all)

2010-05-25 Thread Andreas Tille

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 18 May 2010 10:14:02 +0200
Source: gnumed-client
Binary: gnumed-client gnumed-client-de gnumed-common gnumed-doc
Architecture: source all
Version: 0.7.4-1
Distribution: unstable
Urgency: low
Maintainer: Debian Med Packaging Team 
debian-med-packag...@lists.alioth.debian.org
Changed-By: Andreas Tille ti...@debian.org
Description: 
 gnumed-client - medical practice management - Client
 gnumed-client-de - medical practice management - Client for German users
 gnumed-common - medical practice management - common files
 gnumed-doc - medical practice management - Documentation
Closes: 581106
Changes: 
 gnumed-client (0.7.4-1) unstable; urgency=low
 .
   * New upstream version
   * debian/patches/20_bashism.patch: Fix bashism
 Closes: #581106
   * Drop the debconf configuration for group gnumed because according
 to upstream there is no use for it, thus removed
 debian/gnumed-common.{config,postinst,templates}
   * Drop the debconf configuration for GNUmed server because the
 client is able to actively select a server to connect to, thus
 removed debian/gnumed-client.{config,postinst,templates}
   * Removed debian/po directory because there are no debconf
 questions any more
Checksums-Sha1: 
 24ad209e3d688f99ee6e5c3d6d66e3b17603b37b 1458 gnumed-client_0.7.4-1.dsc
 0e61e771e0211bd8f84d138404a58981e6bc513e 9285316 
gnumed-client_0.7.4.orig.tar.gz
 99e5101e0a789215a7430044575167bb2bffdb26 15881 
gnumed-client_0.7.4-1.debian.tar.gz
 a75306dd2ca82a1fb58dd8eabedd6d80fe827b84 1058606 gnumed-client_0.7.4-1_all.deb
 5dcd6aa2e9da13bd478b8e659b2fad9866c6e2e4 12364 gnumed-client-de_0.7.4-1_all.deb
 6f7635cc91db5174e7fd4be632b38fd25c2a1576 132718 gnumed-common_0.7.4-1_all.deb
 b23926cb8df3a678a2e4cc97f70c0877a514831f 70104 gnumed-doc_0.7.4-1_all.deb
Checksums-Sha256: 
 1a7169391d1cd74ec4dc9c73d7a890c7ab60f96bfa3abd62c4f8c64a3e4445c0 1458 
gnumed-client_0.7.4-1.dsc
 718499421845823749d82bf10619ba74f8075f8f25fc6638e782f4566f6b0c88 9285316 
gnumed-client_0.7.4.orig.tar.gz
 4624387b9da5e93169642886a3bfd972638253286422243ac212ba1c65867daa 15881 
gnumed-client_0.7.4-1.debian.tar.gz
 dfa4d174a1f01aafc8d1e1a19eb879432d3f86866d3b5436bb99cb37cf900850 1058606 
gnumed-client_0.7.4-1_all.deb
 7edf5142aa05c147eafc03fb52c3303a6b1af6dccdebe51cc6480096c087f5c2 12364 
gnumed-client-de_0.7.4-1_all.deb
 1458362df1ab12f4c59e6c56cdce468f6b887b61ba0ff398cc10a0ec0eb5ead8 132718 
gnumed-common_0.7.4-1_all.deb
 fdea7de41900634ac380165ea9d0cbf39d84bb4f3a0368fa3c4fb6424920af42 70104 
gnumed-doc_0.7.4-1_all.deb
Files: 
 e077105e260f32ac5e3fc2598a2b5ddd 1458 misc optional gnumed-client_0.7.4-1.dsc
 6d6dfa05dc271c7b40873c0eac4bca55 9285316 misc optional 
gnumed-client_0.7.4.orig.tar.gz
 5927e132fe9ab8835579f229815dfd2b 15881 misc optional 
gnumed-client_0.7.4-1.debian.tar.gz
 a3a37f03de69568f13661cd3155a5564 1058606 misc optional 
gnumed-client_0.7.4-1_all.deb
 a8e8ab51f161a6e7b65c7efcbfcd0c2c 12364 misc optional 
gnumed-client-de_0.7.4-1_all.deb
 adb051276a22f8d0cdfa437ca0dec3c0 132718 misc optional 
gnumed-common_0.7.4-1_all.deb
 763d6699cc51489e5895fa0123c1c53f 70104 doc optional gnumed-doc_0.7.4-1_all.deb

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

iD8DBQFL+6U5YDBbMcCf01oRAtODAJ9S9E51TyiTOvQ+eFIrRcfUSupLpQCfcqRd
GESFn7xZC4G6+9n+wxMEoS8=
=5K6w
-END PGP SIGNATURE-


Accepted:
gnumed-client-de_0.7.4-1_all.deb
  to main/g/gnumed-client/gnumed-client-de_0.7.4-1_all.deb
gnumed-client_0.7.4-1.debian.tar.gz
  to main/g/gnumed-client/gnumed-client_0.7.4-1.debian.tar.gz
gnumed-client_0.7.4-1.dsc
  to main/g/gnumed-client/gnumed-client_0.7.4-1.dsc
gnumed-client_0.7.4-1_all.deb
  to main/g/gnumed-client/gnumed-client_0.7.4-1_all.deb
gnumed-client_0.7.4.orig.tar.gz
  to main/g/gnumed-client/gnumed-client_0.7.4.orig.tar.gz
gnumed-common_0.7.4-1_all.deb
  to main/g/gnumed-client/gnumed-common_0.7.4-1_all.deb
gnumed-doc_0.7.4-1_all.deb
  to main/g/gnumed-client/gnumed-doc_0.7.4-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/e1ogrgk-0005ty...@ries.debian.org

Accepted gnome-icon-theme-symbolic 2.30.0-1 (source all)