Re: Team uploads
On Tue Apr 07 10:38, Charles Plessy wrote: so in the end, can we use the “ * QA upload.” special first line for non-uploader uploads without breaking the QA infrastructure? That's wrong if the maintainer is not debian...@lists. Matt -- Matthew Johnson signature.asc Description: Digital signature
Re: UDD gatherer for DDTP translations (Was: Extended descriptions size)
On Sun, 5 Apr 2009, Martijn van Oosterhout wrote: While I'm not against the idea of version numbers (though it would have to be a list since a single translation may apply to dozens of versions) This might be discussed. it's not that hard to identify the description you want. What I often did was simply open up the description file to find the description I wanted to test, cut and paste it into another console running md5sum and that would be the md5 I needed to look for. Well, I did not said that it is actually hard and in UDD you can get this easily by SELECT md5(description || E'\n' || long_description || E'\n' ) AS md5 FROM packages WHERE ... but the actual method you are proposing might be not very reliable because of the importance of spacings (like the exact newlines etc). So comparing version numbers is faster in any case and *easily* doable for humans - even if you have the right md5 sum as you mentioned above - comparing it is also harder than a short version string. While the human readability is not my main concern I care more for the feature to directly compare Translations and Packages table with the available information rather than taking the detour over MD5 sums. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: lilo about to be dropped?
On Mon, 2009-04-06 at 18:46 +0200, Christian Perrier wrote: Quoting Frans Pop (elen...@planet.nl): I'm not sure where the original mail comes from, but IMO this should be From lilo package BTS which I was tracking for l10n purposes. So I just happened to notice William's answer to a bug report and thought it would be good for this to be discussed in public. Clearly, I didn't choose the right place to discuss and the topic has wider implications than just D-I, as the followups show. Good thing that you made the discussion wider. Don't we have some install paths that still depend on LILO? Yes: /boot on LVM is the main one. Anyway, even if we don't, I think we should track that lilo removal and coordinate with William, in order to stop providing lilo-installer. And, I think this should be mentioned as a release goal (dropping lilo). Either high priority if we have install paths depending on lilo, or normal priority otherwise. D-I release goal or Debian release goal [1]? Clearly Debian release goal. IMO the latter could well be justified as there will also need to be some kind of upgrade strategy for existing users that does not make uncontrolled changes on their hard disk or loses them the ability to boot alternative OSes on dual (or multi) boot systems. Which might be very tricky But, as William mentioned in his original mail, upstream activity seems to be low so we need to figure out if we want to keep yet another unmaintained software in Debian. What later puzzled me if the mention in non collaboratve upstream *if we don't drop Debian patches*. That's not exactly inactive upstream so it would be good to clarify the situation of lilo upstream. Lilo upstream is dead (no release in quite a while), but the lilo maintainer has also been seen as saying in various mailing lists etc, that since Debian patches lilo that he has no interest in helping to fix problems in our version. William signature.asc Description: This is a digitally signed message part
Re: Why do we have to support tmpfs for /var/run (policy changes in 3.8.1)
Gunnar Wolf wrote: It does achieve not having bogus information on. If your system crashed, some crappy daemons will refuse to start if /var/run/crappyserver.pid exists, or will try to communicate with their peers using /var/run/sloppydaemon.socket, possibly failing cleanly, but possibly leading to head-scratching In Debian policy: : The init.d scripts must ensure that they will behave sensibly : (i.e., returning success and not starting multiple copies of a : service) if invoked with start when the service is already running, : or with stop when it isn't, and that they don't kill : unfortunately-named user processes. this case is not cited in the examples, but I really think that *behave sensibly* cover also thiscase , i.e. after a crash a daemon should start, also if .pid exists. ciao cate -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: lilo about to be dropped?
* Frans Pop elen...@planet.nl [2009-04-07 02:54]: Martin Wuertele wrote: Actually lilo is installed by lenny d-i if you use root-sw-raid with LVM, even if your /boot is an differen partition/sw-raid. Therefore lilo should at least remain for sqeeze to ensure a proper upgrade path. I'm afraid you're mistaken here. Lenny D-I should (and AFAIK does) default to grub for that setup. /boot on normal partition or RAID1 + / on whatever combination of RAID+LVM is supported fine by grub. Unless there is some other factor that you've not mentioned D-I does not fall back to lilo for that. I wonder what it could be. I don't user XFS just plain ext3 and had to manually install grub for 2 recent setups. One is an IBM X3560 with harware-raid, /boot on one partitione, rest for lvm, the other is an X3220 with /boot on md0 and lvm on md1. For both D-I installed lilo. Yours Martin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Team uploads
Charles Plessy ple...@debian.org writes: Le Mon, Apr 06, 2009 at 11:51:54AM -0700, Russ Allbery a écrit : There still should be some humans in Maintainer/Uploaders who are taking primary responsibility for the package, but I think other team members should be able to do QA-style fixes and transition uploads without using NMU versioning or add themselves to Uploaders and hence imply that they're taking ongoing responsibility for the package. so in the end, can we use the “ * QA upload.” special first line for non-uploader uploads without breaking the QA infrastructure? No, that is reserved for orphaned packages and triggers other checks to ensure the maintainer is set appropriately. I think the conversation hasn't reached a conclusion yet about the right way to do this, but I doubt it would be reusing the key phrase for orphaned package uploads. -- 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
Re: Why do we have to support tmpfs for /var/run (policy changes in 3.8.1)
On Mon, 2009-04-06 at 20:42 +0200, Michael Biebl wrote:
Steve Langasek wrote:
I think he's referring to the fact that the FHS requires all files in
/var/run to be cleared on boot. We have an init script
(/etc/rcS.d/S36mountall-bootclean) that takes care of this at the system
level, though, on behalf of all packages; the trouble is it's a lot less
efficient, overall, to have to repeatedly clean /var/run on boot than it is
to just write it to a tmpfs and let the contents be lost on reboot.
I think that is one of them main questions:
Is it more efficient, to cleanup /var/tmp (i.e. remove everything besides
directories) on boot in a single place (mountall-bootclean), or is it more
efficient to use a tmpfs and let every package create it's run directory on
boot.
It's probably hard to tell without proper benchmarking.
Another possibility would be to recreate the directories
in /var/{run,lock} on boot in a centeral initscript. Each package could
ship a directory as template somewhere else which would be copied on
boot (after cleaning or mounting a tmpfs) to /var/{run,lock}. Or shell
script snippets could be used instead.
This would at least avoid having an initscript for the sole purpose of
creating those directories.
Jan
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Transition from libmysqlclient15 to libmysqlclient16
Hi, I plan to move MySQL 5.1 from experimental to unstable really soon now, MySQL 5.0 will be dropped from Debian at the same time. This means 215 packages need to be rebuild. There should be no changes necessary on these packages, a simple rebuild should do it. Norbert -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Writing symbols files for C++ libraries.
Hi!
I'm currently fighting with deb symbols files for a C++ library I'm
packaging, and I'd like to get some insight in how others are coping
with this task. In particular, I wonder how to get rid of symbols from
standard template instances that leak into the ABI, eg.
$ cat test.cpp
#include string
std::string foome(const std::string bar)
{
return foo + bar + foo;
}
$ g++ -fPIC -c test.cpp
$ readelf -Wds test.o | grep -v UND | grep -v HIDDEN | grep -E
'(FUNC|OBJECT)'
18: 23 FUNCWEAK DEFAULT9
_ZNSt11char_traitsIcE6lengthEPKc
22: 155 FUNCWEAK DEFAULT 11
_ZStplIcSt11char_traitsIcESaIcEESbIT_T0_T1_EPKS3_RKS6_
30: 104 FUNCWEAK DEFAULT 14
_ZStplIcSt11char_traitsIcESaIcEESbIT_T0_T1_ERKS6_PKS3_
33: 124 FUNCGLOBAL DEFAULT5 _Z5foomeRKSs
I can hide the operator+() and related instances from with a version
script, of course, but due to C++ name mangling they tend to be
arch-specific and thus hard to maintain. Does anyone know of a more
lightweight solution to limit visibility of template instances and
ensure a clean ABI for C++ libraries? What are the current best
practises when writing symbols files for C++ libraries, or is it simply
not recommended?
Regards,
Daniel.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Writing symbols files for C++ libraries.
On Tue, Apr 07, 2009 at 01:22:51AM +0200, Daniel Kobras kob...@debian.org
wrote:
Hi!
I'm currently fighting with deb symbols files for a C++ library I'm
packaging, and I'd like to get some insight in how others are coping
with this task. In particular, I wonder how to get rid of symbols from
standard template instances that leak into the ABI, eg.
$ cat test.cpp
#include string
std::string foome(const std::string bar)
{
return foo + bar + foo;
}
$ g++ -fPIC -c test.cpp
$ readelf -Wds test.o | grep -v UND | grep -v HIDDEN | grep -E
'(FUNC|OBJECT)'
18: 23 FUNCWEAK DEFAULT9
_ZNSt11char_traitsIcE6lengthEPKc
22: 155 FUNCWEAK DEFAULT 11
_ZStplIcSt11char_traitsIcESaIcEESbIT_T0_T1_EPKS3_RKS6_
30: 104 FUNCWEAK DEFAULT 14
_ZStplIcSt11char_traitsIcESaIcEESbIT_T0_T1_ERKS6_PKS3_
33: 124 FUNCGLOBAL DEFAULT5 _Z5foomeRKSs
I can hide the operator+() and related instances from with a version
script, of course, but due to C++ name mangling they tend to be
arch-specific and thus hard to maintain. Does anyone know of a more
lightweight solution to limit visibility of template instances and
ensure a clean ABI for C++ libraries? What are the current best
practises when writing symbols files for C++ libraries, or is it simply
not recommended?
Unfortunately, gcc upstream consider this as a feature, and not a bug:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36022
I found nothing better than using a version script. I'm lucky that the
library in question (WebKit) only really exports C symbols, and C++ is only
internal details, so I'm filtering everything that starts with _Z, now.
Mike
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522914: ITP: agda -- a dependently typed functional programming language and proof assistant
Package: wnpp Severity: wishlist Owner: Iain Lane la...@ubuntu.com * Package name: agda Version : 2.2.0 Upstream Author : Ulf Norell u...@chalmers.se * URL : http://wiki.portal.chalmers.se/agda/ * License : MIT/X11 Programming Lang: Haskell Description : a dependently typed functional programming language and proof assistant Agda is a dependently typed functional programming language: It has inductive families, which are like Haskell's GADTs, but they can be indexed by values and not just types. It also has parameterised modules, mixfix operators, Unicode characters, and an interactive Emacs interface (the type checker can assist in the development of your code). .. Agda is a proof assistant: It is an interactive system for writing and checking proofs. Agda is based on intuitionistic type theory, a foundational system for constructive mathematics developed by the Swedish logician Per Martin-Lf. It has many similarities with other proof assistants based on dependent types, such as Coq, Epigram and NuPRL. -- System Information: Debian Release: 5.0 APT prefers jaunty-updates APT policy: (500, 'jaunty-updates'), (500, 'jaunty-security'), (500, 'jaunty-backports'), (500, 'jaunty') Architecture: i386 (i686) This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
depending on obsolete packages
One finds packages depending on obsolete packages, e.g., # aptitude -F %p search ?obsolete | xargs -n 1 echo aptitude why|sh -x + aptitude why libicu38 i gimpDepends libwebkit-1.0-1 (= 1.0.1) i A libwebkit-1.0-1 Depends libicu38 (= 3.8-5) + aptitude why libltdl3 i php5-mcrypt Depends libltdl3 (= 1.5.2-2) + aptitude why libvolume-id0 i hal Depends libvolume-id0 (= 0.113-1~) + aptitude why linux-image-2.6.26-1-686 i linux-image-686 Depends linux-image-2.6.26-1-686 Bugs have been filed for all of them, but can't there be an automatic check added to the system to stop or warn somebody? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522924: ITP: agda-stdlib -- standard library for Agda - a dependently typed functional programming language and proof assistant
Package: wnpp Severity: wishlist Owner: Iain Lane la...@ubuntu.com * Package name: agda-stdlib Version : unreleased Upstream Author : Nils Anders Danielsson n...@cs.nott.ac.uk * URL : http://wiki.portal.chalmers.se/agda/agda.php?n=Libraries.StandardLibrary * License : MIT/X Programming Lang: Agda Description : standard library for Agda - a dependently typed functional programming language and proof assistant Agda is a dependently typed functional programming language: It has inductive families, which are like Haskell's GADTs, but they can be indexed by values and not just types. It also has parameterised modules, mixfix operators, Unicode characters, and an interactive Emacs interface (the type checker can assist in the development of your code). .. Agda is a proof assistant: It is an interactive system for writing and checking proofs. Agda is based on intuitionistic type theory, a foundational system for constructive mathematics developed by the Swedish logician Per Martin-Lf. It has many similarities with other proof assistants based on dependent types, such as Coq, Epigram and NuPRL. .. This package contains the standard library for Agda, which provides some modules for common programming- and proof-structuring idioms. Modules are included for algebra, category theory, coinduction, data types, the foreign function interface, induction, IO, relations, and sized types. -- System Information: Debian Release: 5.0 APT prefers jaunty-updates APT policy: (500, 'jaunty-updates'), (500, 'jaunty-security'), (500, 'jaunty-backports'), (500, 'jaunty') Architecture: i386 (i686) This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522921: ITP: haskell-ifelse -- Anaphoric and miscellaneous useful control-flow
Package: wnpp Severity: wishlist Owner: Marco Túlio Gontijo e Silva mar...@holoscopio.com * Package name: haskell-ifelse Version : 0.85 Upstream Author : Jeff R. Heard and Wren Thornton * URL : http://hackage.haskell.org/cgi-bin/hackage-scripts/package/IfElse * License : BSD Programming Lang: Haskell Description : anaphoric and miscellaneous useful control-flow This package provides a library for the Haskell programming language. See http://www.haskell.org/ for more information on Haskell. . This package provides control-flow functions to use with Monads. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: lilo about to be dropped?
Stephen Gran wrote: This one time, at band camp, William Pitcock said: The only way it is feasible to do so is to drop all of the Debian patches. Without this, upstream is not cooperative with us. Why is this? I think because of William Pitcock with: - his very strong words, - his attitude: perfect or nothing (in design, in management, ...), - his lack to listen upstreams and their needs: needs of other distributions, old compatibility needs, or simply time constrain and limited interest of upstream. ciao nenolod ;-) ciao cate -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Writing symbols files for C++ libraries.
Le mardi 07 avril 2009 à 11:57 +0200, Mike Hommey a écrit : I found nothing better than using a version script. I'm lucky that the library in question (WebKit) only really exports C symbols, and C++ is only internal details, so I'm filtering everything that starts with _Z, now. BTW, for such simple things, you can let libtool create the version script for you, using -export-symbols-regex. -- .''`. Debian 5.0 Lenny has been released! : :' : `. `' Last night, Darth Vader came down from planet Vulcan and told `-me that if you don't install Lenny, he'd melt your brain. signature.asc Description: Ceci est une partie de message numériquement signée
Re: lilo about to be dropped?
On Mon, Apr 06, 2009 at 11:10:25PM +0200, Iustin Pop wrote: On Mon, Apr 06, 2009 at 11:42:42AM -0500, William Pitcock wrote: On Mon, 2009-04-06 at 18:19 +0200, Vincent Zweije wrote: On Mon, Apr 06, 2009 at 06:06:38PM +0200, Mike Hommey wrote: || On Mon, Apr 06, 2009 at 08:02:04PM +0400, Dmitry E. Oboukhov un...@debian.org wrote: || I use lilo, I like lilo. || I don't like grub because it has unlogically config, unlogically || behavior, strange reconfig-system. I don't like the programs with || perverse intellect. Grub is not unixway. || || Which is more perverse to read a kernel? || - reading actual files from actual filesystems || - reading hardcoded blocks on the device I think this question should be: Which is more perverse to read without a kernel? The answer could still fall either way. No, the answer is always the second one. Err, why? I've seen grub failing more often, and heard way more report of this, than of lilo. Please explain why you say so. The grub installer also used to read the blockdevice while the filesystem was mounted, which is never the right answer. It has always seemed hackish to me, duplicating fs functionality (and not always correctly, e.g. related to journal replaying on ext3/xfs). A simple block list is just that. Run update-initramfs -u without running lilo. Oh, you boot on the old initramfs. Now remove the old initramfs and put some other files in /boot. Then you're likely to not be able to boot at all. That sure is better. Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: lilo about to be dropped?
On Mon, 2009-04-06 at 22:20 +0100, Stephen Gran wrote: This one time, at band camp, William Pitcock said: The only way it is feasible to do so is to drop all of the Debian patches. Without this, upstream is not cooperative with us. Why is this? See my other mail, basically, lilo upstream view is that our patches broke it and that we have to fix it ourselves. I've seen him on various threads saying basically that over the years. But regardless, a lilo release has not been made in some time. William signature.asc Description: This is a digitally signed message part
Re: RFA: acpi-support -- glue layer for translating laptop buttons, plus legacy suspend support
[Michael Biebl] As (co-)maintainer of pm-utils and hal, I'd prefer if we could work towards standardizing on one power management stack in Debian (and not install 3 by default [1]), i.e. I'd support in phasing out acpi-support and would gladly accept patches for hal and pm-utils which add (if there are) any missing bits from acpi-support. Perhaps hotkey-setup should be made obsolete too? Is it still work keeping? URL: http://packages.qa.debian.org/h/hotkey-setup.html . 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
Re: DEP-4: The TDeb specification.
On Mon, 06 Apr 2009 01:13:19 -0400 Filipus Klutiero chea...@gmail.com wrote: That would be a nice improvement, but let me suggest another implementation. To avoid introducing a second diff, why not updating the regular diff (in the case of non-native packages) but indicating that the package shouldn't be entirely rebuilt when uploading? This seems simpler. That also involves separate handling for native vs non-native packages. The DEP does not require that - the +t1.diff.gz is used for native and non-native. Any changes to the .diff.gz (or .tar.gz for native packages) uploaded by the maintainer would require a source rebuild in order to maintain the integrity of the archive - that is precisely what the DEP is trying to avoid. You can't have a source package in a state that says this isn't the source we actually used to build the binary. The source to build the .deb needs to be unchanged. The changes made to generate the .tdeb need to sit alongside the existing source package and have absolutely no effect on anything related to the binary packages or the source package uploaded by the maintainer. That breaks the existing source package in Debian - the .dsc referring to that .diff.gz has been signed by the maintainer and any changes will break that signature. Right - unless the .dsc is also updated. And if there is to be a tdiff, I don't see why .dsc-s wouldn't include the tdiff's digest. There will be a complementary dsc using the +t1 version suffix. That can work, though I don't see what you were trying to say. That there should be no update to the .dsc because the existing source package must not be altered, therefore the second .dsc with the +t1 version suffix. In the case of a TDeb update during a release freeze, the .dsc signed by the maintainer is already part of testing so the TDeb upload to unstable must not change that .dsc. (Whether the +t1.dsc is retained is a different issue - I suspect that we only actually need to retain the +t1.diff.gz but as any .dsc is tiny, it isn't a big issue either way.) Note that many packages containing translatable content won't need a +t1.diff.gz at all, if the current version in testing was made after making a call for translations and waiting to receive updates before the upload (subject to RC bug fixes requiring a change during the freeze). The +t1.diff.gz is a way to introduce new translations and translation updates for packages that could not be translated prior to the maintainer upload of the original '+t0' TDeb which itself is described in the source package uploaded by the maintainer. Outside a release freeze, it will be up to debian-i18n to coordinate TDeb uploads for each source package amongst the translation teams and possibly with the maintainer to make arrangements such that translation updates can be uploaded in a collective manner (typically using a deadline of some sort) or as part of the next maintainer upload. Whilst the DEP supports +t[0-9], it is envisaged that the need for +t2 and +t3 etc. should be rare. Package management tools need a way to tell a .deb from a .tdeb - the two need to be handled differently by tools like dak, britney, apt, dpkg, reprepro, deb-gview and others. Do you mean that package management tools need a way to tell a traditional/current .deb from a package containing what the DEP proposes to put in a .tdeb? In a similar way to udebs. The .tdeb needs to be handled differently by package management tools (things like reprepro and dak) so that uploads of TDebs can be made by translation teams, so that the existing source package is not affected, so that TDeb uploads can more easily be made during a release freeze without causing problems for archive management software and without needing the tools to look inside the TDeb or rely solely on a version suffix. udebs have different requirements for migration into testing (specific unblocks required with d-i approval), different locations under pool/main/ and different handling by archive software compared to standard .debs. TDebs have different requirements for migration into testing (TDebs migrate even if the package itself is frozen, as long as the version in testing matches that in unstable or the TDeb upload goes via testing-proposed-updates etc.), different handling by archive tools to retain the .diff.gz and the +t1.diff.gz and different upload restrictions. If you're only talking about the tdeb format per se, I don't understand your reasoning. Other tools may need to support the locale roots in the .tdeb - these changes will be easier if the tool can rely on these only existing in a .tdeb instead of occurring in random .debs but not in others. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgp3AHIXo2PQI.pgp Description: PGP signature
Re: Writing symbols files for C++ libraries.
On Tue, Apr 07, 2009 at 12:15:19PM +0200, Josselin Mouette j...@debian.org wrote: Le mardi 07 avril 2009 à 11:57 +0200, Mike Hommey a écrit : I found nothing better than using a version script. I'm lucky that the library in question (WebKit) only really exports C symbols, and C++ is only internal details, so I'm filtering everything that starts with _Z, now. BTW, for such simple things, you can let libtool create the version script for you, using -export-symbols-regex. The problem with libtool's option is that it is inclusive, i.e. what you give it will be exported, not hidden, which is sometimes much easier to handle. Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
D-I not using grub (was: lilo about to be dropped?)
Let's move this subthread back to d-boot. Reply-to set. Please let us know if you'd like to be CCed. Martin Wuertele wrote: * Frans Pop elen...@planet.nl [2009-04-07 02:54]: Martin Wuertele wrote: Actually lilo is installed by lenny d-i if you use root-sw-raid with LVM, even if your /boot is an differen partition/sw-raid. Therefore lilo should at least remain for sqeeze to ensure a proper upgrade path. I'm afraid you're mistaken here. Lenny D-I should (and AFAIK does) default to grub for that setup. /boot on normal partition or RAID1 + / on whatever combination of RAID+LVM is supported fine by grub. Unless there is some other factor that you've not mentioned D-I does not fall back to lilo for that. I wonder what it could be. I don't user XFS just plain ext3 and had to manually install grub for 2 recent setups. One is an IBM X3560 with harware-raid, /boot on one partitione, rest for lvm, the other is an X3220 with /boot on md0 and lvm on md1. For both D-I installed lilo. Next time you get in that situation, please add a 'set -x' in /var/lib/dpkg/info/grub-installer.isinstallable and then run it from one of the debug shells. That should tell you why D-I skips grub and falls back to lilo. Cheers, FJP -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: lilo about to be dropped?
Harald Braumann wrote: * configuration of grub2 is really a PITA You can't specify boot options per entry (there's only a global option in /etc/default grub, that applies to all entries). You may want to check bug 470398. The patch is probably outdated by now, though. Requiring bug/patch submitters to suscribe to a relatively active list is definitely the wrong thing to do, which is why the patch didn't make it upstream (and the maintainer, who is active upstream too, doesn't seem to care to do it himself). -- Felipe Sateler -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: lilo about to be dropped?
]] William Pitcock | Have you looked into ext2linux? It is intended to supercede lilo. I | think your usage requirements will be satisfied by it. It does not appear to exist in Debian? -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Team uploads
On Mon, 06 Apr 2009, Russ Allbery wrote: Charles Plessy ple...@debian.org writes: so in the end, can we use the “ * QA upload.” special first line for non-uploader uploads without breaking the QA infrastructure? No, that is reserved for orphaned packages and triggers other checks to ensure the maintainer is set appropriately. I think the conversation hasn't reached a conclusion yet about the right way to do this, but I doubt it would be reusing the key phrase for orphaned package uploads. The simplest solution would be to use * Team upload as a new key phrase to mark such packages. Cheers, -- Raphaël Hertzog Contribuez à Debian et gagnez un cahier de l'admin Debian Lenny : http://www.ouaza.com/wp/2009/03/02/contribuer-a-debian-gagner-un-livre/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522934: ITP: python-whoosh -- pure-Python full text indexing, search, and spell checking library
Package: wnpp Severity: wishlist Owner: Daniel Watkins dan...@daniel-watkins.co.uk * Package name: python-whoosh Version : 0.1.13 Upstream Author : Matt Chaput m...@whoosh.ca * URL : http://whoosh.ca * License : Apache Programming Lang: Python Description : pure-Python full-text indexing, search, and spell checking library Whoosh is a fast, pure-Python indexing and search library. Programmers can use it to easily add search functionality to their applications and websites. As Whoosh is pure Python, you don't have to compile or install a binary support library and/or make Python work with a JVM, yet indexing and searching is still very fast. Whoosh is designed to be modular, so every part can be extended or replaced to meet your needs exactly. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
tdiff (DEP-4: The TDeb specification.)
Neil Williams wrote: On Mon, 06 Apr 2009 01:13:19 -0400 Filipus Klutiero chea...@gmail.com wrote: That would be a nice improvement, but let me suggest another implementation. To avoid introducing a second diff, why not updating the regular diff (in the case of non-native packages) but indicating that the package shouldn't be entirely rebuilt when uploading? This seems simpler. That also involves separate handling for native vs non-native packages. The DEP does not require that - the +t1.diff.gz is used for native and non-native. Any changes to the .diff.gz (or .tar.gz for native packages) uploaded by the maintainer would require a source rebuild in order to maintain the integrity of the archive - that is precisely what the DEP is trying to avoid. You can't have a source package in a state that says this isn't the source we actually used to build the binary. The source to build the .deb needs to be unchanged. Yes, but the source package contains more than the source used to build the traditional binary packages. It also contains (potentially) source for translation debs. As long as the only source changed is the source for the translation debs, the traditional binary packages don't need to be rebuilt. The changes made to generate the .tdeb need to sit alongside the existing source package and have absolutely no effect on anything related to the binary packages or the source package uploaded by the maintainer. Per what I wrote above, I don't see anything preventing the source changes for translation debs to be integrated in the traditional diff (again, in the case of non-native packages). That breaks the existing source package in Debian - the .dsc referring to that .diff.gz has been signed by the maintainer and any changes will break that signature. Right - unless the .dsc is also updated. And if there is to be a tdiff, I don't see why .dsc-s wouldn't include the tdiff's digest. There will be a complementary dsc using the +t1 version suffix. That can work, though I don't see what you were trying to say. That there should be no update to the .dsc because the existing source package must not be altered, therefore the second .dsc with the +t1 version suffix. In the case of a TDeb update during a release freeze, the .dsc signed by the maintainer is already part of testing so the TDeb upload to unstable must not change that .dsc. I don't see a problem preventing the traditional .dsc to be changed. Changing the .dsc does not imply that the existing source package must be altered. The .dsc could be updated in testing. (Whether the +t1.dsc is retained is a different issue - I suspect that we only actually need to retain the +t1.diff.gz but as any .dsc is tiny, it isn't a big issue either way.) I think it should be retained; small issue, indeed. To sum up, I still don't see anything that imposes introducing a tdiff, even to avoid rebuilding the traditional binary packages. But, I'm starting to see tdiff is probably a good idea anyway for security reasons. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
.tdeb format (DEP-4: The TDeb specification.)
Package management tools need a way to tell a .deb from a .tdeb - the two need to be handled differently by tools like dak, britney, apt, dpkg, reprepro, deb-gview and others. Do you mean that package management tools need a way to tell a traditional/current .deb from a package containing what the DEP proposes to put in a .tdeb? In a similar way to udebs. The .tdeb needs to be handled differently by package management tools (things like reprepro and dak) so that uploads of TDebs can be made by translation teams, so that the existing source package is not affected, so that TDeb uploads can more easily be made during a release freeze without causing problems for archive management software and without needing the tools to look inside the TDeb or rely solely on a version suffix. Yes. I think a translation package could simply be identified by a control field. Say Translates: foo or, if Translates would only list the source package, Translation: Yes If you're only talking about the tdeb format per se, I don't understand your reasoning. Other tools may need to support the locale roots in the .tdeb - these changes will be easier if the tool can rely on these only existing in a .tdeb instead of occurring in random .debs but not in others. But these locale roots would only exist in .tdeb-s. In .deb-s, there wouldn't be such locale roots. If we're wondering whether we should introduce a .tdeb format, we shouldn't reason that that there will be a need for .tdeb if .tdeb is introduced. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Improvements to ‘debian/watch’ for fetching from VCS
On Sat, Apr 04 2009, Noah Slater wrote: On Sat, Apr 04, 2009 at 01:35:17PM -0600, Raphael Geissert wrote: opts=handler=svn http://domain.tld/svn/foo/... would do the right thing. What about uscan being able to use custom make targets in debian/rules? There could be a way to tell uscan to use the following: debian/rules get-orig-source debian/rules check-version This allows developers the flexibility to handle any situation, and doesn't bloat uscan by having to add all kinds of fancy handlers for different version control systems. As a concrete benefit, my nightly cron to check uscan for all my packages will be able to alert me about the ones pulled from repository revisions, all I would need to do is add a new check-version target. Why bloat debian/rules? ALl this can be done using the current mechanism of just adding a script into the watchfile, and does not tie down uscan to the debian checked out source. manoj -- Each person has the right to take the subway. Manoj Srivastava sriva...@debian.org http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Forthcoming changes in kernel-package
On Thu, Feb 26 2009, Theodore Tso wrote: On Fri, Feb 20, 2009 at 12:56:30PM -0600, Manoj Srivastava wrote: BTW, I have a set of patches you might want to consider. I'll file them in BTS if you're currently making make-kpkg. Please. I have been thinking about the request you made for debugging symbols being packaged, and now I do have some time to play with building kernels again, I would like to see that in Squeeze. Sorry for the delay; I've sent you the private patches I've been using for make-kpkg. Some of them are quite hackish, and some of they you may have fixed in other ways, so I won't feel bad at all if you need to significantly rework them before you can merge them into your master sources. Most of these bugs had been fixed, and all but one have been fixed by last night's upload into experimental. The only one remaining is the one about creating a new debuginfo package; I am torn between letting the debuginfo remain with the image package, but move the debug infromation from /lib/modules into /usr/ or /var; and to creating a whole new package just for the debugging information. manoj -- The Gordian Maxim: If a string has one end, it has another. Manoj Srivastava sriva...@debian.org http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Improvements to ‘debian/watch’ for fetching from VCS
On Thu, Apr 02 2009, Noah Slater wrote: On Fri, Apr 03, 2009 at 10:50:11AM +1100, Ben Finney wrote: That's the trouble though. AIUI, different VCSen have different ways of identifying a specific state of the working tree; we have not only revisions, but also tags, branches, threads, heads, and probably others I've forgotten. Should all of those be allowed? Is that too complex an interface? As for “latest”: is there an unambiguous “latest” for every repository? What does this mean with repositories that have simultaneous lines of history within the same location? Okay, but for the purposes of this file we only need two actions, right? Is the current version the latest one we're interested in, and how can we fetch the upstream source for the current version. If we let these two actions be scripted through a standard interface, it should work with any repository. If the current version is what we are interested, why not get it from the canonical site, the Debian archive? I am not seeing the sue case for not getting the sources distributed by Debian from Debian. People who do not trust the Debian archive, ought not to trust the Debian script, and go get the upstream using a trusted download agent on their own; so security is not the use case. By far the most common use case I can see is to get the latest upstream, and do whatver munging needs to be done to make it acceptable for Debian as a source archive. What am I missing? manoj -- Moore's Constant: Everybody sets out to do something, and everybody does something, but no one does what he sets out to do. Manoj Srivastava sriva...@debian.org http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Improvements to ‘debian/watch’for fetching f rom VCS
On Tue, Apr 7, 2009 at 11:06 PM, Manoj Srivastava wrote: What am I missing? One case I can think of; it is (possibly) common for sponsors to check that the result from get-orig-source matches the contents of the tarball uploaded to mentors by the sponsee. -- 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
Re: Forthcoming changes in kernel-package
Hi,
A few hours ago, a new version of kernel-package was uploaded to
Experimental. This is a major change, the new kernel-package is far
more nimble, more flexible, and supports people who make a minor change
to a kernel, or who update the kernel sources (via git or otherwise),
and want a minimal, simple, recompile.
79 files changed, 1776 insertions(+), 3706 deletions(-)
The full NEWS.Debian file is appended below, but I'll highlight
the major differences: This version does not support the official
images (which is OK, since the kernel team thinks kernel-package is
broken anyway, and have been deprecating it for a few years now), it
does not run a bootloader, or manage symlinks, or create an init ram fs
for you -- since the policies governing these actions were becoming too
rigid, and had to cater to the lowest common denominator.
Instead, the package comes with example scripts that can be
dropped into /etc/kernel/*.d directories to do all that, and more (you
can change the number of symlinks you keep, for example). Now you can
add actions to {pre,post}{inst,rm} stages of the package installation or
removal, independently, for image, header, source, and doc packages.
More importantly, the initramfs scripts provided work with the
make-kpkg images as well as the official images, and are thus better
than the script shipped with initramfs-tools themselves, as they offer
a super set of functionality.
This version of kernel-package also demonstrates how the
postsinst script communicates with the initramfs scripts so that no
initramfs is generated in case you do not want it (I personally compile
all modules in my non-laptop kernel, and thus do not need an
initramfs).
I have not yet seeded the env with the maintainer script
parameter arguments, but I'll put in what Frans suggested unless there
are objections.
Please take this for a spin. Kick the tires. I need helpe from
people who run Xen machines, since I do not use Xen, and would like to
make the Xen images work better.
manoj
kernel-package (12.001) experimental; urgency=low
* This is a major change in functionality; do not upgrade unless you are
prepared for the changes required on target machines.
* make-kpkg removes and re-creates ./debian on every invocation
This does make the kernel-package far more nimble; we now offer less
surprise to users who did not expect stampts that the kernel-packagge
used to not do duplicate work. Now, if you edit a couple of files in
the kernel source, and run make-kpkg, the kernel will build as
expected. There are no more version mismatch errors, and the kernel
version can be modified using localconfig as one desires. With this,
kernel-package can rountinely be used to build kernels out of the git
tree.
The con is that we no longer cater to official kernels, or to anyone who
expected content in ./debian to persist. At some point, there are plans
to implement an overlay directory that will shadow
/usr/share/kernel-package/ruleset, but that is not yet implemented.
* Get rid of the facility to patch kernel sources
The patch the kernel facility was adding complexity, and failing to
provide the flexibility required for a generic patching facility. It used
to be useful at one point, but in the modern parlance, witht he
widespread use of distribute version control systems, and various
facilities to manage source and patch them, the built in version was
clunky. This means the --added-patches option of make-kpkg is gone,
the work-around is to prepare the kernel sources _before_ calling
make-kpkg.
* Remove special case code for official kernels
For the longest tine (well, ever since Herbert Xu too over building
kernel images from me), kernel-package has carried specal case code
for official images. This has caused some problems, recently, since
the need to preserve ./debian has caused no end of problems when the
version changed out from under ./debian, or when people wanted to edit
a file and expected kernel-package to do a minimal recompile.
However, sometime in the Etch release cycle, the kernel team
deprecated kernel-package as the means of building official kernels,
and therefore, a full release cycle later, we can get rid of the
special case rules used for official packages. Also, this allows us to
drop ./debian at teh drop of a hart, and recreate it with an version
that reflects the current state of the kernel sources.
* No longer ship header debs that create symbolic links in /usr/src,
instead, ship an example shell script that replicated the old
behaviour. This script can then be deployed on the target machines,
and could be a part of a locally created kernel configuration package,
if one needs to deploy the same behavior across a cluster of
machines.
*
Re: Improvements to ‘debian /watch’ for fetching from VCS
On Tue, Apr 07, 2009 at 10:00:05AM -0500, Manoj Srivastava wrote: On Sat, Apr 04 2009, Noah Slater wrote: As a concrete benefit, my nightly cron to check uscan for all my packages will be able to alert me about the ones pulled from repository revisions, all I would need to do is add a new check-version target. Why bloat debian/rules? ALl this can be done using the current mechanism of just adding a script into the watchfile, and does not tie down uscan to the debian checked out source. Because this bloats the uscan implementation. GNU Make already lets us add these rules, and the only real difference, presuming that the rules would be of the same length no matter where you put them, is the file they are located in. -- Noah Slater, http://tumbolia.org/nslater -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: lilo about to be dropped?
On Mon, Apr 6, 2009 at 9:21 PM, William Pitcock neno...@sacredspiral.co.uk wrote: Lilo upstream is dead (no release in quite a while), but the lilo maintainer has also been seen as saying in various mailing lists etc, that since Debian patches lilo that he has no interest in helping to fix problems in our version. Ok but you could try to push those patches upstream. This is how grub has been improved and also parted. This works most of time. This way we reduce the amount of patches we keep in Debian and also you could try to get in touch with other distros to share the load and avoid reworking at same things. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Improvements to ‘debian /watch’ for fetching from VCS
On Tue, Apr 07, 2009 at 10:06:18AM -0500, Manoj Srivastava wrote: If the current version is what we are interested, why not get it from the canonical site, the Debian archive? I am a new maintainer, and I have sponsors for various packages. People can check out the source code, and run: debian/rules get-orig-source This works for all my packages, and is very handy for other people. -- Noah Slater, http://tumbolia.org/nslater -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: .tdeb format (DEP-4: The TDeb specification.)
On Tue, 07 Apr 2009 10:23:37 -0400 Filipus Klutiero chea...@gmail.com wrote: In a similar way to udebs. The .tdeb needs to be handled differently by package management tools (things like reprepro and dak) so that uploads of TDebs can be made by translation teams, so that the existing source package is not affected, so that TDeb uploads can more easily be made during a release freeze without causing problems for archive management software and without needing the tools to look inside the TDeb or rely solely on a version suffix. Yes. I think a translation package could simply be identified by a control field. Then every file-based operation has to query the contents of the file to know how to handle it. TDebs are sufficiently different internally that other tools can handle them more easily if the filename is clearly indicative. This is more important where there are lots of TDebs, so that is how .tdeb came into the Specification. In Emdebian, a package can have dozens of .tdeb files, obscuring the .deb files in a simple directory listing. With the modifications for Debian TDebs after DebConf and the resulting single TDeb per source package, this is not a problem for archive listings but it could still be a problem for other tools. Say Translates: foo or, if Translates would only list the source package, Translation: Yes I'm working on the patches for dpkg at the moment, I'm extending Thomas' code to support 'dpkg -c' etc. and it is looking like a field in DEBIAN/control will be necessary. I'm looking at putting a Languages: field inside DEBIAN/control that lists the locale roots supported by that TDeb. (The name of the field isn't material, Locale-roots: is more accurate than Languages: but not as suitable IMHO.) This field will be generated by dpkg-deb --tdeb -b so that it is always up to date. However, if I find a better way of obtaining the data that can be gleaned from using: `ar -t` with relevant parsing, then there will be no need for the field, at least on the part of dpkg. There is also a Package-Type: tdeb field which is used by dpkg-genchanges in the same way as Package-Type: udeb is done currently. I don't see that either of those predicate against a .tdeb extension when .udeb exists for the same reasons. If you're only talking about the tdeb format per se, I don't understand your reasoning. Other tools may need to support the locale roots in the .tdeb - these changes will be easier if the tool can rely on these only existing in a .tdeb instead of occurring in random .debs but not in others. But these locale roots would only exist in .tdeb-s. In .deb-s, there wouldn't be such locale roots. If we're wondering whether we should introduce a .tdeb format, we shouldn't reason that that there will be a need for .tdeb if .tdeb is introduced. Having .tdeb makes it simpler to handle TDebs on a variety of fronts but I really don't think that a control field is comparable in terms of functionality. We have .udeb, .tdeb is sufficiently clear and aids the handling of .tdeb by other packages - why restrict every operation to having to inspect the DEBIAN/control file every time? `dpkg -f $file Languages` is going to get tiresome every time, not to mention slow. (Package-Type is just a different string for the same thing, except that will require additional parsing for tdeb vs udeb.) -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ pgpyIJpOI03ny.pgp Description: PGP signature
Re: Team uploads
Raphael Hertzog hert...@debian.org writes: On Mon, 06 Apr 2009, Russ Allbery wrote: Charles Plessy ple...@debian.org writes: so in the end, can we use the “ * QA upload.” special first line for non-uploader uploads without breaking the QA infrastructure? No, that is reserved for orphaned packages and triggers other checks to ensure the maintainer is set appropriately. I think the conversation hasn't reached a conclusion yet about the right way to do this, but I doubt it would be reusing the key phrase for orphaned package uploads. The simplest solution would be to use * Team upload as a new key phrase to mark such packages. Can anyone think of any drawbacks to that? (We really need a document somewhere listing all these key phrases -- I wonder if that would be appropriate for Policy given how much software now cares.) -- 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
Re: tdiff (DEP-4: The TDeb specification.)
On Tue, 07 Apr 2009 09:57:30 -0400 Filipus Klutiero chea...@gmail.com wrote: (Could you add a blank line between the quoted reply and your content? It makes the content easier for me to read. Thanks.) Neil Williams wrote: On Mon, 06 Apr 2009 01:13:19 -0400 Filipus Klutiero chea...@gmail.com wrote: That would be a nice improvement, but let me suggest another implementation. To avoid introducing a second diff, why not updating the regular diff (in the case of non-native packages) but indicating that the package shouldn't be entirely rebuilt when uploading? This seems simpler. That also involves separate handling for native vs non-native packages. The DEP does not require that - the +t1.diff.gz is used for native and non-native. Any changes to the .diff.gz (or .tar.gz for native packages) uploaded by the maintainer would require a source rebuild in order to maintain the integrity of the archive - that is precisely what the DEP is trying to avoid. You can't have a source package in a state that says this isn't the source we actually used to build the binary. The source to build the .deb needs to be unchanged. Yes, but the source package contains more than the source used to build the traditional binary packages. It also contains (potentially) source for translation debs. As long as the only source changed is the source for the translation debs, the traditional binary packages don't need to be rebuilt. But the source package would still be the wrong source for the binaries that exist. The archive needs to contain the unique source package for the binaries that exist, modifying the source without modifying the binaries is not an option for legal reasons, as I understand it. The changes made to generate the .tdeb need to sit alongside the existing source package and have absolutely no effect on anything related to the binary packages or the source package uploaded by the maintainer. Per what I wrote above, I don't see anything preventing the source changes for translation debs to be integrated in the traditional diff (again, in the case of non-native packages). Why treat the two differently? Whether the package is native or non-native makes no difference to how the TDeb is generated or handled. It has a bearing on which packages will be handled at which stage of the transition to TDebs but nothing beyond that. That breaks the existing source package in Debian - the .dsc referring to that .diff.gz has been signed by the maintainer and any changes will break that signature. Right - unless the .dsc is also updated. And if there is to be a tdiff, I don't see why .dsc-s wouldn't include the tdiff's digest. There will be a complementary dsc using the +t1 version suffix. That can work, though I don't see what you were trying to say. That there should be no update to the .dsc because the existing source package must not be altered, therefore the second .dsc with the +t1 version suffix. In the case of a TDeb update during a release freeze, the .dsc signed by the maintainer is already part of testing so the TDeb upload to unstable must not change that .dsc. I don't see a problem preventing the traditional .dsc to be changed. Changing the .dsc does not imply that the existing source package must be altered. The .dsc could be updated in testing. If the .dsc is modified, the source package no longer matches the binaries that are in the archive that were built from the old .dsc. Just who/what is supposed to modify the existing .dsc anyway? The archive software? TDebs are not necessarily built from an unpacked source directory, they can be built by tools working just from the POT file and PO contributions. Yes, the +t0 TDeb, the one created by the maintainer, will have the normal source and the normal tools, there is nothing to say that +t1 would have the unpacked source available necessarily. Translators will often have the source in order to test the translation but the final +t1 TDeb will collate the contributions of several translators and several translation teams, via several sources. The +t1.dsc is likely to need to be signed but merging that with the existing .dsc could give the utterly misleading impression that the nominated l10n person doing the upload is somehow responsible for the binary packages that have not been touched but are affected by the change to the .dsc. This is another area where TDebs are quite different to normal .deb - there is nothing to say that dpkg-buildpackage has to be involved, none of the standard Debian build tools need exist other than dpkg itself (not even dpkg-dev, although that would be unusual). (Whether the +t1.dsc is retained is a different issue - I suspect that we only actually need to retain the +t1.diff.gz but as any .dsc is tiny, it isn't a big issue either way.) I
Re: RFA: acpi-support -- glue layer for translating laptop buttons, plus legacy suspend support
On Tue, Apr 07, 2009 at 01:26:18PM +0200, Petter Reinholdtsen wrote: [Michael Biebl] As (co-)maintainer of pm-utils and hal, I'd prefer if we could work towards standardizing on one power management stack in Debian (and not install 3 by default [1]), i.e. I'd support in phasing out acpi-support and would gladly accept patches for hal and pm-utils which add (if there are) any missing bits from acpi-support. Perhaps hotkey-setup should be made obsolete too? Is it still work keeping? URL: http://packages.qa.debian.org/h/hotkey-setup.html . That is also being phased out in Ubuntu. The only remaining functionality in that package for jaunty is setting /proc/acpi/video/*/DOS; we need to either confirm that this is handled somewhere else or determine an appropriate package to set this by default before dropping hotkey-setup. -- 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
Re: lilo about to be dropped?
On Tue, 2009-04-07 at 10:52 +0200, Giacomo A. Catenazzi wrote: Stephen Gran wrote: This one time, at band camp, William Pitcock said: The only way it is feasible to do so is to drop all of the Debian patches. Without this, upstream is not cooperative with us. Why is this? I think because of William Pitcock with: - his very strong words, - his attitude: perfect or nothing (in design, in management, ...), - his lack to listen upstreams and their needs: needs of other distributions, old compatibility needs, or simply time constrain and limited interest of upstream. ciao nenolod ;-) Actually, the damage was done years ago, long before I ever maintained lilo. But thanks for the flame. William signature.asc Description: This is a digitally signed message part
Re: lilo about to be dropped?
On Tue, 2009-04-07 at 13:06 -0300, Otavio Salvador wrote: On Mon, Apr 6, 2009 at 9:21 PM, William Pitcock neno...@sacredspiral.co.uk wrote: Lilo upstream is dead (no release in quite a while), but the lilo maintainer has also been seen as saying in various mailing lists etc, that since Debian patches lilo that he has no interest in helping to fix problems in our version. Ok but you could try to push those patches upstream. This is how grub has been improved and also parted. This works most of time. This way we reduce the amount of patches we keep in Debian and also you could try to get in touch with other distros to share the load and avoid reworking at same things. lilo is officially unmaintained now. The canonical website of lilo now points to a 404 error page, see http://lilo.go.dyndns.org/ . So at this point, our only option seems to be taking over upstream lilo maintainance ourselves (which could be a good thing in some ways, I am not denying that), or find a way to transition these use-cases to grub/grub2/extlinux. However, if we are to maintain lilo ourselves, then we need to flesh out exactly what usecases we're going to be using it for. I recommend if we go that route that we come up with a list of improvements that we want to see and get to hacking. If some of the people who like lilo a lot got around to helping with a fork, we could create a much less buggy bootloader than the current lilo. Alternatively, we can just leave it and let it become another XMMS. I don't like this solution very much. William signature.asc Description: This is a digitally signed message part
Re: lilo about to be dropped?
William Pitcock neno...@sacredspiral.co.uk (07/04/2009): Alternatively, we can just leave it and let it become another XMMS. I don't like this solution very much. Beware, gtk3 is coming, so you'd better update lilo to no longer depend on gtk2! Mraw, KiBi. signature.asc Description: Digital signature
Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby
Package: wnpp Severity: wishlist Owner: Sebastien Delafond s...@debian.org * Package name: jruby1.2 Version : 1.2.0 Upstream Author : The JRuby Team * URL : http://jruby.codehaus.org/ * License : tri-license CPL/GPL/LGPL Programming Lang: Java Description : 100% pure-Java implementation of Ruby JRuby is tightly integrated with Java to allow the embedding of the interpreter into any Java application with full two-way access between the Java and the Ruby code. -- System Information: Debian Release: 5.0 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'oldstable'), (500, 'stable'), (1, 'unstable') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby
On Tue, Apr 07, 2009 at 12:09:56PM -0700, Sebastien Delafond wrote: Package: wnpp Severity: wishlist Owner: Sebastien Delafond s...@debian.org * Package name: jruby1.2 Version : 1.2.0 Upstream Author : The JRuby Team * URL : http://jruby.codehaus.org/ * License : tri-license CPL/GPL/LGPL Programming Lang: Java Description : 100% pure-Java implementation of Ruby JRuby is tightly integrated with Java to allow the embedding of the interpreter into any Java application with full two-way access between the Java and the Ruby code. Why do we need jruby1.0, jruby1.1 and now jruby1.2 ? Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Why do we have to support tmpfs for /var/run (policy changes in 3.8.1)
Giacomo A. Catenazzi dijo [Tue, Apr 07, 2009 at 11:05:35AM +0200]: In Debian policy: : The init.d scripts must ensure that they will behave sensibly : (i.e., returning success and not starting multiple copies of a : service) if invoked with start when the service is already running, : or with stop when it isn't, and that they don't kill : unfortunately-named user processes. this case is not cited in the examples, but I really think that *behave sensibly* cover also thiscase , i.e. after a crash a daemon should start, also if .pid exists. Strong +1. This is, however, unrelated to whatever happened at boot - If the daemon crashed during regular system usage and it is started again, it should start regardless if there are any pidfiles lying around. -- Gunnar Wolf - gw...@gwolf.org - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522984: ITP: magics++ -- Meteorological plotting software
Package: wnpp Severity: wishlist Owner: Alastair McKinstry mckins...@debian.org * Package name: magics++ Version : 2.6.4 Upstream Author : ECMWF software.servi...@ecmwf.int * URL : http://www.ecmwf.int/products/data/software/magics++.html * License : Apache license, version 2. Programming Lang: C, Fortran Description : Meteorological plotting software Magics++ is the latest generation of the ECMWF's Meteorological plotting software MAGICS. Although completely redesigned in C++, it is intended to be as backwards-compatible as possible with the Fortran interface. Besides its programming interfaces (Fortran and C), Magics++ offers MagML, a plot description language based on XML aimed at automatic web production. . The library supports the plotting of contours, wind fields, observations, satellite images, symbols, text, axis and graphs (including boxplots). . Data fields to be plotted may be presented in various formats, for instance GRIB 1 and 2 code data, Gaussian grid, regularly spaced grid and fitted data. Input data can also be in BUFR and NetCDF format or retrieved from an ODB database. . The produced meteorological plots can be saved in various formats, such as PostScript, EPS, PDF, GIF, PNG, SVG and KML. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: lilo about to be dropped?
On Tue, Apr 07, 2009 at 07:36:40AM +0200, Mike Hommey wrote: On Mon, Apr 06, 2009 at 11:10:25PM +0200, Iustin Pop wrote: On Mon, Apr 06, 2009 at 11:42:42AM -0500, William Pitcock wrote: On Mon, 2009-04-06 at 18:19 +0200, Vincent Zweije wrote: On Mon, Apr 06, 2009 at 06:06:38PM +0200, Mike Hommey wrote: || On Mon, Apr 06, 2009 at 08:02:04PM +0400, Dmitry E. Oboukhov un...@debian.org wrote: || I use lilo, I like lilo. || I don't like grub because it has unlogically config, unlogically || behavior, strange reconfig-system. I don't like the programs with || perverse intellect. Grub is not unixway. || || Which is more perverse to read a kernel? || - reading actual files from actual filesystems || - reading hardcoded blocks on the device I think this question should be: Which is more perverse to read without a kernel? The answer could still fall either way. No, the answer is always the second one. Err, why? I've seen grub failing more often, and heard way more report of this, than of lilo. Please explain why you say so. The grub installer also used to read the blockdevice while the filesystem was mounted, which is never the right answer. It has always seemed hackish to me, duplicating fs functionality (and not always correctly, e.g. related to journal replaying on ext3/xfs). A simple block list is just that. Run update-initramfs -u without running lilo. Oh, you boot on the old initramfs. Now remove the old initramfs and put some other files in /boot. Then you're likely to not be able to boot at all. That sure is better. Are you complaining that lilo allows one to shot oneself in the foot? Because that how it looks like. My point is that in controlled environments, lilo looks to be more stable. Not for desktop usage, not for update-iniramfs usage without knowing what needs to be done. Again, my point is (like the grand-grand-parent), that the answer differs by application. grubs is not always better. regards, iustin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby
On Apr/07, Mike Hommey wrote: Why do we need jruby1.0, jruby1.1 and now jruby1.2 ? so multiple versions of jruby can be simultaneously installed on a system, like with python2.x, ruby1.x, etc ? Cheers, --Seb -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby
+ Sebastien Delafond (Tue, 07 Apr 2009 13:08:17 -0700): On Apr/07, Mike Hommey wrote: Why do we need jruby1.0, jruby1.1 and now jruby1.2 ? so multiple versions of jruby can be simultaneously installed on a system, like with python2.x, ruby1.x, etc ? The question was, rather: why would a user want to install jruby1.0 or jruby1.1 instead of jruby1.2? What purpose does it serve having three different versions in the archive instead of one, or two at most? Thanks, -- - Are you sure we're good? - Always. -- Rory and Lorelai -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby
On Tue, Apr 07, 2009 at 01:08:17PM -0700, Sebastien Delafond wrote: On Apr/07, Mike Hommey wrote: Why do we need jruby1.0, jruby1.1 and now jruby1.2 ? so multiple versions of jruby can be simultaneously installed on a system, like with python2.x, ruby1.x, etc ? While I see why it can be needed for python, I fail to see how it is important for jruby... Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby
On Apr/07, Adeodato Simó wrote: The question was, rather: why would a user want to install jruby1.0 or jruby1.1 instead of jruby1.2? What purpose does it serve having three different versions in the archive instead of one, or two at most? jruby1.0 will indeed be removed shortly from the archive, so we can move forward without accumulating too many versions of jruby. Cheers, --Seb -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby
On Tue, Apr 07, 2009 at 01:40:54PM -0700, Sebastien Delafond wrote: On Apr/07, Adeodato Simó wrote: The question was, rather: why would a user want to install jruby1.0 or jruby1.1 instead of jruby1.2? What purpose does it serve having three different versions in the archive instead of one, or two at most? jruby1.0 will indeed be removed shortly from the archive, so we can move forward without accumulating too many versions of jruby. But why a need for two versions at a time ? AFAICS, jruby 1.2 supports both ruby 1.8 *and* 1.9, as jruby 1.1 does, so why would jruby 1.1 still be needed ? Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby
On Apr/07, Mike Hommey wrote: While I see why it can be needed for python, I fail to see how it is important for jruby... to have 2 versions of jruby available ? I guess so you can at least, for instance, try the new one on your existing jruby code without removing the old one, for instance ? Are you advocating for only one instance of jruby at all times in the archive ? If so, why ? Cheers, --Seb -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: lilo about to be dropped?
On Mon, 06 Apr 2009 10:24:54 -0500
William Pitcock neno...@sacredspiral.co.uk wrote:
On Mon, 2009-04-06 at 16:17 +0200, Harald Braumann wrote:
Yes, I do and it works without problems. There are some
inconveniences, though, with grub2, which might make some stick
with LILO:
The LVM support in LILO is hideously broken, so these arguments do not
really matter.
Works for me.
It only works in certain conditions and is known to
break horribly if you have say, a kernel spanning multiple PVs.
Only a true idiot boots off an LVM volume anyway,
You're too nice. Anyway, boot is the least important partition. Any
live CD or USB installation will do to recover.
since there is risk of metadata corruption, etc.
What metadata are you talking about, and what's it got to do with the
boot partition?
The is no simple configuration file that one could edit. You have to
write scripts to add entries.
/boot/grub/{menu.lst,grub.conf} is hard to edit...?
No, but since grub2 doesn't use those, your statement is moot. So are
the following.
You can't specify the default entry (only the number of the entry,
which changes if a new kernel is installed) and there is no
vmlinuz/vmlinuz.old (unless you add a script that adds these
entries)
default X in the config file, and setdefault, works for me.
You can't specify boot options per entry (there's only a global
option in /etc/default grub, that applies to all entries).
Sure you can, just don't use update-grub(1) and update it yourself
instead. Same as lilo, really.
William
harry
signature.asc
Description: PGP signature
Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby
On Apr/07, Mike Hommey wrote: But why a need for two versions at a time ? AFAICS, jruby 1.2 supports both ruby 1.8 *and* 1.9, as jruby 1.1 does, so why would jruby 1.1 still be needed ? As I said in my other mail, for transition reasons; backward-compatibility is something many people like to *try* before actually taking the leap. Cheers, --Seb -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby
On Tue, Apr 07, 2009 at 02:17:09PM -0700, Sebastien Delafond wrote: On Apr/07, Mike Hommey wrote: But why a need for two versions at a time ? AFAICS, jruby 1.2 supports both ruby 1.8 *and* 1.9, as jruby 1.1 does, so why would jruby 1.1 still be needed ? As I said in my other mail, for transition reasons; backward-compatibility is something many people like to *try* before actually taking the leap. Backward compatibility apply for ruby 1.8 vs ruby 1.9. I don't see it applying between jruby 1.1 and jruby 1.2, except for bugs. Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: lilo about to be dropped?
I demand that William Pitcock may or may not have written... [snip] So at this point, our only option seems to be taking over upstream lilo maintainance ourselves (which could be a good thing in some ways, I am not denying that), I say go for it... or find a way to transition these use-cases to grub/grub2/extlinux. Assuming, for the moment, that extlinux is equivalent to syslinux at least as far as configuration goes, then I see that some lilo configuration options which I use or have had use for appear to be missing: addappend optional password restricted [snip] I recommend if we go that route that we come up with a list of improvements that we want to see and get to hacking. If some of the people who like lilo a lot got around to helping with a fork, we could create a much less buggy bootloader than the current lilo. For me, lilo works fine as it is. If I see something which affects me, I'll at least have a look at it; no guarantees, though, since there's a lot of stuff here with which I'm not familiar. Alternatively, we can just leave it and let it become another XMMS. I don't like this solution very much. /AOL. -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | Let's keep the pound sterling Beauty seldom recommends one to another. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Improvements to ‘debian/watch’ for fetching from VCS
(Why was Manoj's message also sent individually to me?) On 07-Apr-2009, Manoj Srivastava wrote: If the current version is what we are interested, why not get it from the canonical site, the Debian archive? The Debian archive is *not* the canonical location for the upstream's original source. The upstream's repository (whether VCS or static files or whatever they make available) is the canonical location. Debian's archive might be more consistent and convenient, but it's an intermediary source for most packages, *not* canonical. I am not seeing the sue case for not getting the sources distributed by Debian from Debian. People who do not trust the Debian archive, ought not to trust the Debian script, and go get the upstream using a trusted download agent on their own; so security is not the use case. Trust isn't binary. One use case is to confirm what re-packing of an original source archive has been done. Another is to verify whether perhaps *upstream* has fiddled with the original source archive since Debian packaged it. Yet another is to get an original source archive that hasn't yet made it into Debian's archive. By far the most common use case I can see is to get the latest upstream, and do whatver munging needs to be done to make it acceptable for Debian as a source archive. What am I missing? It's not at all unusual for me to *not* want to get the latest version precisely because I'm not ready to package that version, or because it is worse (FSVO worse) than the version specified in ‘debian/changelog’. -- \ “Science shows that belief in God is not only obsolete. It is | `\also incoherent.” —Victor J. Stenger, 2001 | _o__) | Ben Finney b...@benfinney.id.au -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Improvements to ‘debian /watch’ for fetching from VCS
On Wed, Apr 08, 2009 at 09:04:21AM +1000, Ben Finney wrote: (Why was Manoj's message also sent individually to me?) On 07-Apr-2009, Manoj Srivastava wrote: If the current version is what we are interested, why not get it from the canonical site, the Debian archive? The Debian archive is *not* the canonical location for the upstream's original source. The upstream's repository (whether VCS or static files or whatever they make available) is the canonical location. Debian's archive might be more consistent and convenient, but it's an intermediary source for most packages, *not* canonical. Debian's archive might contain DFSG modified orig tarballs anyway, right? It's not at all unusual for me to *not* want to get the latest version precisely because I'm not ready to package that version, or because it is worse (FSVO worse) than the version specified in ‘debian/changelog’. Yes, I more often find myself wanting to just get the current tarball. -- Noah Slater, http://tumbolia.org/nslater -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Writing symbols files for C++ libraries.
On Tue, Apr 07, 2009 at 12:15:19PM +0200, Josselin Mouette wrote: Le mardi 07 avril 2009 à 11:57 +0200, Mike Hommey a écrit : I found nothing better than using a version script. I'm lucky that the library in question (WebKit) only really exports C symbols, and C++ is only internal details, so I'm filtering everything that starts with _Z, now. BTW, for such simple things, you can let libtool create the version script for you, using -export-symbols-regex. Have you used this option successfully with a C++ library? In this case, libtool creates input for the linker option -retain-symbols-file rather than a version script like it does with C libs. In my tests, -retain-symbols-file only affected static symbols, but didn't touch the list of dynamic symbols. Which is quite pointless for my use case. Is this a known bug/misfeature or might I by doing something wrong here? Regards, Daniel. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Writing symbols files for C++ libraries.
Daniel Kobras schrieb: On Tue, Apr 07, 2009 at 12:15:19PM +0200, Josselin Mouette wrote: Le mardi 07 avril 2009 à 11:57 +0200, Mike Hommey a écrit : I found nothing better than using a version script. I'm lucky that the library in question (WebKit) only really exports C symbols, and C++ is only internal details, so I'm filtering everything that starts with _Z, now. BTW, for such simple things, you can let libtool create the version script for you, using -export-symbols-regex. Have you used this option successfully with a C++ library? In this case, libtool creates input for the linker option -retain-symbols-file rather than a version script like it does with C libs. In my tests, -retain-symbols-file only affected static symbols, but didn't touch the list of dynamic symbols. Which is quite pointless for my use case. Is this a known bug/misfeature or might I by doing something wrong here? libtool's -export-symbols(-regex) only works with C libraries afaik. For C++ libs the only way I know of is to use GCC's visibility support [1]. Cheers, Michael [1] http://gcc.gnu.org/wiki/Visibility -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: autoconf method in ifupdown
Hi! On Sun, 2009-03-29 at 18:00:14 +0100, Thomas Preud'homme wrote: I was looking a method to just have ipv6 with autoconf network and found this patch http://mlblog.osdir.com/linux.debian.devel.ipv6/2005-05/msg00012.shtml This link didn't seem to work, got this instead: http://lists.debian.org/debian-ipv6/2005/05/msg00012.html Does anybody know the answer of upstream dev to this patch proposition ? Checking the ifupdown bug reports, it does not seem this ever got submitted. It might make sense to file one with the patch. regards, guillem -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFC: Better formatting for long descriptions
Hi! On Mon, 2009-03-23 at 16:23:12 -0700, Daniel Burrows wrote: I don't have the energy to push this any more, but I should probably at least refer to my previous attempt to standardize bulleted lists: http://lists.debian.org/debian-devel/2005/12/msg00531.html You might find it useful, or not. At least it more or less documents current practice in aptitude (I think there have been some tweaks since then; if anyone cares I could go research what they are and dig them up). There's been a wiki page trying to track this, including packages which formatting was proving problematic: http://wiki.debian.org/Aptitude::Parse-Description-Bullets=true regards, guillem -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Team uploads
Matthew Johnson dijo [Mon, Apr 06, 2009 at 08:24:44AM +0100]: It is a useful concept, but I would like to consider them as special case NMUs rather than special case MUs. Quite apart from the issue of deciding whether or not something is 'team maintained' in all cases, if you are a member of the team and you are making uploads to the package, then you should just add yourself to uploaders, surely...? That said, the option so far which is least bad is Team Upload in the same way as QA Upload, i.e. no NMU version number, no NMU procedures, no delay, etc, just something to ack the mismatch of changed-by and uploaders/maintainer. In the pkg-perl group, at least, it is not at all uncommon that a team member (usually not a DD) works on a package and tags it as ready for upload. And then a DD just comes along, checks it, builds and uploads - without having worked with it. It is not precisely a sponsored upload, but a team activity for both. So, yes, we have usually worked aroud it by adding both the people who did the work and the DD to Uploaders: Still, even if the package is group-maintained, it is good to be able to note who is most familiar or has worked most with the package - And the current scheme does not properly represent it (save for parsing debian/changelog) -- Gunnar Wolf - gw...@gwolf.org - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby
Sebastien Delafond dijo [Tue, Apr 07, 2009 at 01:59:00PM -0700]: On Apr/07, Mike Hommey wrote: While I see why it can be needed for python, I fail to see how it is important for jruby... to have 2 versions of jruby available ? I guess so you can at least, for instance, try the new one on your existing jruby code without removing the old one, for instance ? Are you advocating for only one instance of jruby at all times in the archive ? If so, why ? Do the Jruby versions somehow map to the Ruby versions? If I'm not mistaken, Jruby (and IronRuby) versions aimed at compatibility with specific Ruby language releases - and the only Ruby language specification is the main implementation itself. So, does JRuby 1.2 provide a bigger/different API than 1.0? Which one is closer to the main implementation 1.8? 1.9? Now, if JRuby 1.2 (say) implements 1.9 and JRuby 1.0 implements 1.8, possibly the (so far main) implementation should be renamed to only provide libruby1.8, so that also JRuby can satisfy it? -- Gunnar Wolf - gw...@gwolf.org - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#522996: ITP: jruby1.2 -- 100% pure-Java implementation of Ruby
Sebastien Delafond dijo [Tue, Apr 07, 2009 at 02:17:09PM -0700]: On Apr/07, Mike Hommey wrote: But why a need for two versions at a time ? AFAICS, jruby 1.2 supports both ruby 1.8 *and* 1.9, as jruby 1.1 does, so why would jruby 1.1 still be needed ? As I said in my other mail, for transition reasons; backward-compatibility is something many people like to *try* before actually taking the leap. Umh... For our users (yes, those following stable releases), do you want to provide an not-exactly-bleeding-edge-but-stable and one quite-old versions? Why? What's the gain? -- Gunnar Wolf - gw...@gwolf.org - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Improvements to ‘debian/watch’ for fetching from VCS
On Tue, Apr 07 2009, Ben Finney wrote: (Why was Manoj's message also sent individually to me?) On 07-Apr-2009, Manoj Srivastava wrote: If the current version is what we are interested, why not get it from the canonical site, the Debian archive? The Debian archive is *not* the canonical location for the upstream's original source. The upstream's repository (whether VCS or static files or whatever they make available) is the canonical location. Debian's archive might be more consistent and convenient, but it's an intermediary source for most packages, *not* canonical. As far as Debian is concerned, it is: this is the orig.tar.gz that the diff.gz needs to be applied to in order to get the Debian package in the archive. Whatever is upstream may or may not produce the package we have (it could have been corrupted, updated, or whatever). I am not seeing the sue case for not getting the sources distributed by Debian from Debian. People who do not trust the Debian archive, ought not to trust the Debian script, and go get the upstream using a trusted download agent on their own; so security is not the use case. Trust isn't binary. One use case is to confirm what re-packing of an original source archive has been done. Another is to verify whether perhaps *upstream* has fiddled with the original source archive since Debian packaged it. Yet another is to get an original source archive that hasn't yet made it into Debian's archive. Most of htese checks, while laudable, ought not to bload either uscan, or debian/rules, since these are far off topic, in my opinion. By far the most common use case I can see is to get the latest upstream, and do whatver munging needs to be done to make it acceptable for Debian as a source archive. What am I missing? It's not at all unusual for me to *not* want to get the latest version precisely because I'm not ready to package that version, or because it is worse (FSVO worse) than the version specified in ‘debian/changelog’. I think that is usually an uncommon case. And we ought to be coding to the common case, while not making the uncommon cases impossible. manoj -- Ours is a world of nuclear giants and ethical infants. General Omar N. Bradley Manoj Srivastava sriva...@debian.org http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted dphys-swapfile 20061020-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 19 Mar 2009 13:34:14 +0100 Source: dphys-swapfile Binary: dphys-swapfile Architecture: source all Version: 20061020-2 Distribution: unstable Urgency: low Maintainer: Gürkan Sengün gur...@phys.ethz.ch Changed-By: Gürkan Sengün gur...@phys.ethz.ch Description: dphys-swapfile - Autogenerate and use a swap file Closes: 502200 Changes: dphys-swapfile (20061020-2) unstable; urgency=low . * Apply patch to remove maximal swapfile size. (Closes: #502200) Thanks to Jacob Elder for the patch. * Update my email address. * Bump standards version. * Bump debhelper version. * Update debian/copyright. * Move Homepage field in debian/control. Checksums-Sha1: 115d66ec23513d6e3395b5c31e11629308df1999 1088 dphys-swapfile_20061020-2.dsc 72f4fc2de4cc2f3a98d5ae8b0ff9a5668484fb1b 3561 dphys-swapfile_20061020-2.diff.gz 292fea6cb917bbf221746b79a3d4de555919941d 9560 dphys-swapfile_20061020-2_all.deb Checksums-Sha256: 651a3914e98094cf87e5df96aec0fe827bbbc6171534272184eda587b0c9c47a 1088 dphys-swapfile_20061020-2.dsc 41939101e1484842d27598f1cfc8b95b9cb386062fa57f3bed4b13efd9e4cadf 3561 dphys-swapfile_20061020-2.diff.gz 929979e011d149260311c8b844194ca538b7a8f53342f9fbdb419ec8972c66aa 9560 dphys-swapfile_20061020-2_all.deb Files: c411c8e2bb475416100b397790c7d57f 1088 admin optional dphys-swapfile_20061020-2.dsc a7e8b601e49110c119468d9abd447a81 3561 admin optional dphys-swapfile_20061020-2.diff.gz 4d948655303d3d572774779e299a6e8a 9560 admin optional dphys-swapfile_20061020-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkna5/0ACgkQ+ZNUJLHfmlcMkQCfQxd5c8yKlrYWlr3G7pyOmFYj P7MAoIoiwtik3Iuf2sX2oV6TmKaFH519 =ZPti -END PGP SIGNATURE- Accepted: dphys-swapfile_20061020-2.diff.gz to pool/main/d/dphys-swapfile/dphys-swapfile_20061020-2.diff.gz dphys-swapfile_20061020-2.dsc to pool/main/d/dphys-swapfile/dphys-swapfile_20061020-2.dsc dphys-swapfile_20061020-2_all.deb to pool/main/d/dphys-swapfile/dphys-swapfile_20061020-2_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted openafs 1.4.10+dfsg1-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 06 Apr 2009 15:49:34 -0700 Source: openafs Binary: openafs-client openafs-kpasswd openafs-fileserver openafs-dbserver openafs-doc openafs-krb5 libopenafs-dev openafs-modules-source libpam-openafs-kaserver openafs-dbg Architecture: source all i386 Version: 1.4.10+dfsg1-1 Distribution: unstable Urgency: high Maintainer: Russ Allbery r...@debian.org Changed-By: Russ Allbery r...@debian.org Description: libopenafs-dev - AFS distributed filesystem development libraries libpam-openafs-kaserver - AFS distributed filesystem kaserver PAM module openafs-client - AFS distributed filesystem client support openafs-dbg - AFS distributed filesystem debugging information openafs-dbserver - AFS distributed filesystem database server openafs-doc - AFS distributed filesystem documentation openafs-fileserver - AFS distributed filesystem file server openafs-kpasswd - AFS distributed filesystem old password changing openafs-krb5 - AFS distributed filesystem Kerberos 5 integration openafs-modules-source - AFS distributed filesystem kernel module source Closes: 521518 521745 522451 Changes: openafs (1.4.10+dfsg1-1) unstable; urgency=high . * New upstream release. - OPENAFS-SA-2009-001: Avoid a potential kernel memory overrun if more items than requested are returned from an InlineBulk or BulkStatus message. (CVE-2009-1251) - OPENAFS-SA-2009-002: Avoid converting negative errors into invalid kernel memory pointers. (CVE-2009-1250) - Preliminary support for 2.6.30 kernels. - Dynamic vcache allocation support to deal with inotify vcache pinning. - Do appropriate locking for CellServDB in /proc. - Use +dfsg instead of .dfsg for saner version sorting. * Debian's 2.6.29 packages no longer include symlinks from the architecture-specific header tree to the common header tree and instead overlay both header trees using kbuild. Change the Autoconf probes to always use kbuild and generate stub headers in the paths that OpenAFS expects that include the linux headers. Patch from Aaron M. Ucko. (Closes: #521745) * Build PIC versions of libafsauthent and libafsrpc and install them in libopenafs-dev for use when AFS code should be embedded into shared libraries. Patch from Garrett Wollman. * Update CellServDB to 2008-11-07 version. (Closes: #522451) * Update debian/watch for +dfsg naming instead of .dfsg. * Update standards version to 3.8.1 (no changes required). * Translation updates: - Japanese, thanks Hideki Yamane. (Closes: #521518) Checksums-Sha1: 12d858e118b5a41b97c61628ea33aee93c710b4a 1454 openafs_1.4.10+dfsg1-1.dsc cefd4c63412212fe14a5872fdba4dd428c0bb45d 7986072 openafs_1.4.10+dfsg1.orig.tar.gz 5dc6cfc9e60da4eaf7824459c6ee98024ad4cd1e 124323 openafs_1.4.10+dfsg1-1.diff.gz dfb183ad4b4e5f09d0db136283dc83edb5daa8cd 2715490 openafs-doc_1.4.10+dfsg1-1_all.deb 1c4b7f69ed0460d9fda00674b2cf6c6720b46dea 2970244 openafs-client_1.4.10+dfsg1-1_i386.deb a803fb602f5ad57d39984bf3e9529131050942c3 273612 openafs-kpasswd_1.4.10+dfsg1-1_i386.deb 8f87a0e30b957c920e4340202a36e3f17d14b341 1061770 openafs-fileserver_1.4.10+dfsg1-1_i386.deb 1fce957571fc56dba9dd0217f27ec61d73d84737 573006 openafs-dbserver_1.4.10+dfsg1-1_i386.deb f6a516a55ab48ffb5e74c744aef4a0db71170d90 252408 openafs-krb5_1.4.10+dfsg1-1_i386.deb 840c3b65350b1f28142c550641d1c768fe991038 2134822 libopenafs-dev_1.4.10+dfsg1-1_i386.deb c86c0b6b56e761d34dc04108169b9ae39a219b8e 888362 openafs-modules-source_1.4.10+dfsg1-1_i386.deb b0dbb6fd1f4f8ed546da92f5a1a3da0621655ee3 428224 libpam-openafs-kaserver_1.4.10+dfsg1-1_i386.deb 11aa7e0b9fe149b901d005c6e1468643cfa56404 2760134 openafs-dbg_1.4.10+dfsg1-1_i386.deb Checksums-Sha256: e75dfc27179311584ee332645800c625dd944cab7140fb6940159a889116e046 1454 openafs_1.4.10+dfsg1-1.dsc 5d4ea6a19559760963f8c8b9fbf38a16a81803d14ff891c5a5276b685de0a087 7986072 openafs_1.4.10+dfsg1.orig.tar.gz 457fb9559d3124464f0a2d938c2e3401717f9e2a431a5587da905cea82886229 124323 openafs_1.4.10+dfsg1-1.diff.gz 1772bf6af333684d83d2c5a1bab52946c5c448835982a618a0576eb562c16e06 2715490 openafs-doc_1.4.10+dfsg1-1_all.deb 33f356f2ef4114aadc8e4c3d4d35beb5a46af678d1def5837f453d1b1fa5b7a9 2970244 openafs-client_1.4.10+dfsg1-1_i386.deb df1630bac6412e0515c1680689dc6ce0d0eab2ee9e17cff2d20386dd9cdcd580 273612 openafs-kpasswd_1.4.10+dfsg1-1_i386.deb 452aa9bdf23ffe42cf7bccd825114f05d0711b1522efe2383c23c6c1c5615435 1061770 openafs-fileserver_1.4.10+dfsg1-1_i386.deb bf852bb177453a1d81ab4b4e28a104c250dc4fa8c21dd47c56d62f1d5f012188 573006 openafs-dbserver_1.4.10+dfsg1-1_i386.deb 26df14ccd05f6ca97a6dfbcd8f7675d36ca52a6085cd466a24f1aef503d9e8ac 252408 openafs-krb5_1.4.10+dfsg1-1_i386.deb e7f999d07eb6843f68078563c1f8da352ce9cc6624fbc65fb144411b47593f35 2134822 libopenafs-dev_1.4.10+dfsg1-1_i386.deb
Accepted xfmpc 0.1.0-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 08:01:32 +0200 Source: xfmpc Binary: xfmpc Architecture: source amd64 Version: 0.1.0-1 Distribution: unstable Urgency: low Maintainer: Debian Xfce Maintainers pkg-xfce-de...@lists.alioth.debian.org Changed-By: Yves-Alexis Perez cor...@debian.org Description: xfmpc - graphical GTK+ MPD client Changes: xfmpc (0.1.0-1) unstable; urgency=low . * New upstream release. * debian/compat bumped to 7. * debian/control: - update debhelper build-dep to 7. - update standards version to 3.8.1. * debian/rules: - add -Wl,-z,-defs -Wl,--as-needed to LDFLAGS. Checksums-Sha1: f08425c570e324ec5c6d0431928850f60ef0ae86 1417 xfmpc_0.1.0-1.dsc 2277b6cac966b0a13e17460c60192b3e9a80fb5c 376140 xfmpc_0.1.0.orig.tar.gz d610a84a76fab1c20dfa4183be5bc25ce93c59f5 1600 xfmpc_0.1.0-1.diff.gz a93d644cb5db815d83d06eb65a1fbb7cd324f0c9 63872 xfmpc_0.1.0-1_amd64.deb Checksums-Sha256: fb4539b98bb50190c3a94a2d1f0fd78288fa9a9d06bd76a159b1f4efdd4353cf 1417 xfmpc_0.1.0-1.dsc e25ded5412f27dd601a57aeb9752a382f1df70fc3e3d8642b10e3640c42aa678 376140 xfmpc_0.1.0.orig.tar.gz 102bc8db0b4d10575bf58f5a1c8dbd92f3ace9025d4d43d9b450db9338101cdb 1600 xfmpc_0.1.0-1.diff.gz 652331d82b0058a298496c82488ca7337c435792d6008415f5a21bc71c6f5493 63872 xfmpc_0.1.0-1_amd64.deb Files: 3731cafc5c50917770e57a4014897aaa 1417 sound optional xfmpc_0.1.0-1.dsc 94b573b1e1f15409803ba397a6b533d1 376140 sound optional xfmpc_0.1.0.orig.tar.gz 64d78f1596c9bc4b22526ac56488e04b 1600 sound optional xfmpc_0.1.0-1.diff.gz 320c7b85f88ce7d61ca7da58e80b3ed1 63872 sound optional xfmpc_0.1.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkna79cACgkQTUTAIMXAW67xkgCcDHHeJcLfVlIsRsoJNv/fpK41 D1wAoLeAzzaRwegZvxx8ZNYay/aReGWV =6Cv0 -END PGP SIGNATURE- Accepted: xfmpc_0.1.0-1.diff.gz to pool/main/x/xfmpc/xfmpc_0.1.0-1.diff.gz xfmpc_0.1.0-1.dsc to pool/main/x/xfmpc/xfmpc_0.1.0-1.dsc xfmpc_0.1.0-1_amd64.deb to pool/main/x/xfmpc/xfmpc_0.1.0-1_amd64.deb xfmpc_0.1.0.orig.tar.gz to pool/main/x/xfmpc/xfmpc_0.1.0.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted netplug 1.2.9.1-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 08:45:41 +0200 Source: netplug Binary: netplug Architecture: source amd64 Version: 1.2.9.1-1 Distribution: unstable Urgency: low Maintainer: Philipp Matthias Hahn pmh...@debian.org Changed-By: Philipp Matthias Hahn pmh...@debian.org Description: netplug- network link monitor daemon Changes: netplug (1.2.9.1-1) unstable; urgency=low . * New upstream version. - includes socketlen_t fix. Checksums-Sha1: ddb640341741d5eff800d154e99fec50b3c7ec95 1000 netplug_1.2.9.1-1.dsc 84b44b5ed463ebdbc4bcdd32a794f375777d1a76 24573 netplug_1.2.9.1.orig.tar.gz 7c44e40ee235a461b2e8ea3e249e0b0ad5a031bf 3089 netplug_1.2.9.1-1.diff.gz 5cf7312d5bf910ebdcc2af75af6fd309bb0081a2 22806 netplug_1.2.9.1-1_amd64.deb Checksums-Sha256: bc1ee872135202f1bd615352dee654de80636049065c6c4f7e1b015d921e8aa7 1000 netplug_1.2.9.1-1.dsc cf40f68e4d5112e1b50ff182c2ab622175939feea862bc2b337b43a0762f3ed9 24573 netplug_1.2.9.1.orig.tar.gz aee4dd3b6845f5fa75804af9be1d309017a313a6f07cbef4691bf0113a40f671 3089 netplug_1.2.9.1-1.diff.gz b1c5db0f0bf5080fa48a6cb00e6c0cf1368562b426b799f131e650a16dadcac2 22806 netplug_1.2.9.1-1_amd64.deb Files: 08bfc81e52a04909a5bc37065cd2c54c 1000 net optional netplug_1.2.9.1-1.dsc af68f6adf769ef23a4512bc5851835f7 24573 net optional netplug_1.2.9.1.orig.tar.gz 32e5f85eb1ede123a12c010dbf169879 3089 net optional netplug_1.2.9.1-1.diff.gz d6c6acdaaa50ad44ec02172d34a1ad8b 22806 net optional netplug_1.2.9.1-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkna9w8ACgkQYPlgoZpUDjkO7wCgnWf8xSUeNkGNui8uSPe+k6za 3MUAoKUjDReBa7Ku5NBfW6uFdqmsk6Jy =pBFn -END PGP SIGNATURE- Accepted: netplug_1.2.9.1-1.diff.gz to pool/main/n/netplug/netplug_1.2.9.1-1.diff.gz netplug_1.2.9.1-1.dsc to pool/main/n/netplug/netplug_1.2.9.1-1.dsc netplug_1.2.9.1-1_amd64.deb to pool/main/n/netplug/netplug_1.2.9.1-1_amd64.deb netplug_1.2.9.1.orig.tar.gz to pool/main/n/netplug/netplug_1.2.9.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
Accepted gnome-settings-daemon 2.24.1-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 08:48:36 +0200 Source: gnome-settings-daemon Binary: gnome-settings-daemon gnome-settings-daemon-dev Architecture: source amd64 Version: 2.24.1-2 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Josselin Mouette j...@debian.org Description: gnome-settings-daemon - daemon handling the GNOME session settings gnome-settings-daemon-dev - Headers for building applications communicating with gnome-settin Closes: 511905 Changes: gnome-settings-daemon (2.24.1-2) unstable; urgency=low . [ Josselin Mouette ] * Improve package descriptions. Mention XSETTINGS. Closes: #511905. * Upload to unstable. . [ Loic Minier ] * Suggest x11-xserver-utils as gnome-settings-daemon attempts to run xrdb by default and logs a warning when that fails. * Suggest gnome-screensaver as gnome-settings-daemon attempts to start it by default and logs a warning when that fails. * Suggest metacity | x-window-manager as gnome-settings-daemon attemts to start a window manager and logs a warning when that fails. Checksums-Sha1: 0514fa602c80f90c22120407d5067d5ae2e916a5 1801 gnome-settings-daemon_2.24.1-2.dsc bbedbf32d8034c55a20b86c25025ee38e0c8454d 488227 gnome-settings-daemon_2.24.1-2.diff.gz d1fea14c9c4ab74e4893ac9309766cf39d801ef9 625146 gnome-settings-daemon_2.24.1-2_amd64.deb 1118116514e4b56424fcba22fa5e76437943fb1d 33240 gnome-settings-daemon-dev_2.24.1-2_amd64.deb Checksums-Sha256: 18bbfce8f24d218d1f124af47a14d98c00e7538b6d5d630f4023f0c690cc 1801 gnome-settings-daemon_2.24.1-2.dsc 5e125ade5dada421b48d27ed5a01b3dd4dab031e9c0d1203e2db9a049e82b562 488227 gnome-settings-daemon_2.24.1-2.diff.gz 7ee8398e4dcb148889be68db2644d9ac1eebbaad157de27c19c2a5b6c6b8337c 625146 gnome-settings-daemon_2.24.1-2_amd64.deb 6db5ec0daa19b02b66e47339e9d9669766145712e9dc5f7b8e6af8d395f6e8e7 33240 gnome-settings-daemon-dev_2.24.1-2_amd64.deb Files: 10d4af8907a9f9980904c39df9536aa0 1801 gnome optional gnome-settings-daemon_2.24.1-2.dsc e900f18c7220b878c28e5e3d3d52f290 488227 gnome optional gnome-settings-daemon_2.24.1-2.diff.gz 2098e6ee74a95eddc5156a838ad5e8bd 625146 gnome optional gnome-settings-daemon_2.24.1-2_amd64.deb a519d5c1948948818d7bba0d9ec8c94c 33240 gnome optional gnome-settings-daemon-dev_2.24.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2vm+rSla4ddfhTMRApYfAJ92TgkIVARa8TECgeJdhfI8NS7uugCgnoOF SutDuTJ2QUEVqp8LEn0cLgQ= =mTUj -END PGP SIGNATURE- Accepted: gnome-settings-daemon-dev_2.24.1-2_amd64.deb to pool/main/g/gnome-settings-daemon/gnome-settings-daemon-dev_2.24.1-2_amd64.deb gnome-settings-daemon_2.24.1-2.diff.gz to pool/main/g/gnome-settings-daemon/gnome-settings-daemon_2.24.1-2.diff.gz gnome-settings-daemon_2.24.1-2.dsc to pool/main/g/gnome-settings-daemon/gnome-settings-daemon_2.24.1-2.dsc gnome-settings-daemon_2.24.1-2_amd64.deb to pool/main/g/gnome-settings-daemon/gnome-settings-daemon_2.24.1-2_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted gnome-desktop 2.24.3-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 15 Mar 2009 15:21:12 +0100 Source: gnome-desktop Binary: gnome-about gnome-desktop-data libgnome-desktop-2-7 libgnome-desktop-dev Architecture: source all amd64 Version: 2.24.3-1 Distribution: unstable Urgency: low Maintainer: Ondřej Surý ond...@debian.org Changed-By: Josselin Mouette j...@debian.org Description: gnome-about - The GNOME about box gnome-desktop-data - Common files for GNOME 2 desktop apps libgnome-desktop-2-7 - Utility library for loading .desktop files - runtime files libgnome-desktop-dev - Utility library for loading .desktop files - development files Changes: gnome-desktop (2.24.3-1) unstable; urgency=low . * Build-depend on libglib2.0-doc and libgtk2.0-doc to ensure proper xrefs. * New upstream release. * 90_relibtoolize.patch: regenerate for the new version. * Upload to unstable!!1!omgwtfbbq Checksums-Sha1: 8ded0077a42b46968871cfab498c41a87f95da15 1667 gnome-desktop_2.24.3-1.dsc 4293eff6a080b618ac684aead75b6502be2e5a95 2114776 gnome-desktop_2.24.3.orig.tar.gz 9ad48a18a65313bf84a395d63544df6c66f27c54 516879 gnome-desktop_2.24.3-1.diff.gz 728ac76ce41477cf649ba5e574f6571511435ab8 204710 gnome-about_2.24.3-1_all.deb 6e1ce205503ec2626c2635ca3dae8296ed1ba255 818594 gnome-desktop-data_2.24.3-1_all.deb 03c8027c1508094700bc9d62d8da2b28ff3bdda3 113860 libgnome-desktop-2-7_2.24.3-1_amd64.deb b3c73ba15debe5995fb788c9573463ab951abe70 150022 libgnome-desktop-dev_2.24.3-1_amd64.deb Checksums-Sha256: 77cf5a816adcbc6aba89c1ed98f4bfa65a9e823f64afc01168bd90033f52e753 1667 gnome-desktop_2.24.3-1.dsc b3ffbc8bfc07c1deef9570eeab76d07333c3c4b5bb3e0d904dc073e127e65b92 2114776 gnome-desktop_2.24.3.orig.tar.gz dfd70778389a73606b3b537149e51bb8404f3c184f1c0b0478c4f6202ef0511b 516879 gnome-desktop_2.24.3-1.diff.gz 50aa0aac0aa9ecf6c7d9290c3679e82541be0318fb4bc0b299f2c39445b97f4b 204710 gnome-about_2.24.3-1_all.deb dfcc82f18177d1b0a9629918265abb60127170187925facddcbfd48cdddaf776 818594 gnome-desktop-data_2.24.3-1_all.deb b54448ed5b1cf77b320ac469de52fbb50a171451ae10895060cb32b07de5370f 113860 libgnome-desktop-2-7_2.24.3-1_amd64.deb 327e939bd7d68bfa6fd27aa025410fa29739f25041dd29d2f3d316ea1ad10609 150022 libgnome-desktop-dev_2.24.3-1_amd64.deb Files: 2b7e930eba422f8155ffacc82df68d98 1667 gnome optional gnome-desktop_2.24.3-1.dsc e32c3f01eda06a85d26fd21b81eb8730 2114776 gnome optional gnome-desktop_2.24.3.orig.tar.gz 50eea3ff83285f51ceb8099d84f8e072 516879 gnome optional gnome-desktop_2.24.3-1.diff.gz 6cc579c42671104d64559117504eaf12 204710 gnome optional gnome-about_2.24.3-1_all.deb 5ca91ce481f4b86fcc5c3b7f89c557b4 818594 gnome optional gnome-desktop-data_2.24.3-1_all.deb 6d11c8cc1c1994e0ba4378cadb8f8866 113860 libs optional libgnome-desktop-2-7_2.24.3-1_amd64.deb 697fbd7ceffc31e3948d0c70a70b3ebf 150022 libdevel optional libgnome-desktop-dev_2.24.3-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2vPprSla4ddfhTMRApUPAJwP2uKmJXGArRoQCG2ORleARgTFyQCgmduh NnbPVOtK/PeIFN2M2Awg1W4= =0LPt -END PGP SIGNATURE- Accepted: gnome-about_2.24.3-1_all.deb to pool/main/g/gnome-desktop/gnome-about_2.24.3-1_all.deb gnome-desktop-data_2.24.3-1_all.deb to pool/main/g/gnome-desktop/gnome-desktop-data_2.24.3-1_all.deb gnome-desktop_2.24.3-1.diff.gz to pool/main/g/gnome-desktop/gnome-desktop_2.24.3-1.diff.gz gnome-desktop_2.24.3-1.dsc to pool/main/g/gnome-desktop/gnome-desktop_2.24.3-1.dsc gnome-desktop_2.24.3.orig.tar.gz to pool/main/g/gnome-desktop/gnome-desktop_2.24.3.orig.tar.gz libgnome-desktop-2-7_2.24.3-1_amd64.deb to pool/main/g/gnome-desktop/libgnome-desktop-2-7_2.24.3-1_amd64.deb libgnome-desktop-dev_2.24.3-1_amd64.deb to pool/main/g/gnome-desktop/libgnome-desktop-dev_2.24.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
Accepted libgnomekbd 2.24.0-2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 08:37:20 +0200 Source: libgnomekbd Binary: libgnomekbd-dev libgnomekbd3 libgnomekbd-common gkbd-capplet Architecture: source all amd64 Version: 2.24.0-2 Distribution: unstable Urgency: low Maintainer: Loic Minier l...@dooz.org Changed-By: Josselin Mouette j...@debian.org Description: gkbd-capplet - GNOME Panel applet for libgnomekbd libgnomekbd-common - GNOME library to manage keyboard configuration - common files libgnomekbd-dev - GNOME library to manage keyboard configuration - development file libgnomekbd3 - GNOME library to manage keyboard configuration - shared library Changes: libgnomekbd (2.24.0-2) unstable; urgency=low . * Upload to unstable. * Standards version is 3.8.1. Checksums-Sha1: a4a5c012b74e325e13fdfb6566e56e9f22f61bb2 1478 libgnomekbd_2.24.0-2.dsc 59cfa14ca3d791d0a16646268a9ee02899b0b8e4 3731 libgnomekbd_2.24.0-2.diff.gz 30e933351d3dc34b1ba0ff385a837e9e0ff2d3cb 116856 libgnomekbd-common_2.24.0-2_all.deb aa0c1a744e612fca79d399f00ce490066a1f 52326 libgnomekbd-dev_2.24.0-2_amd64.deb a51cd335027d6fd26efebce048d55246f1f818b1 49892 libgnomekbd3_2.24.0-2_amd64.deb ca670e02b0fa5cf9a03095ad59e31efc52512b3b 23170 gkbd-capplet_2.24.0-2_amd64.deb Checksums-Sha256: d5f6de9899e08bb6d3c64c1b45a14fd5806b3e6553c5a24518d16fc9564ac2ae 1478 libgnomekbd_2.24.0-2.dsc a7cafb423fedcf6ed2f35810518e70f9299da985f0cad2cec2efe7fcff09a316 3731 libgnomekbd_2.24.0-2.diff.gz daad68dcbdcafc4bbef74d253f82bb0cb010509173a321b5d5ecb6884caae652 116856 libgnomekbd-common_2.24.0-2_all.deb 386757952325b3650d0b903faf5b6aee542a94436bffb16fa8372f771bf7a42d 52326 libgnomekbd-dev_2.24.0-2_amd64.deb 31c7ca6454057dcbe698d0c0b57f0aafead22d704235e1b66458e7d696562659 49892 libgnomekbd3_2.24.0-2_amd64.deb 5dfaf6eba8346402c605c54430bfb9a46412aa4085535b3c95c15a73ec597834 23170 gkbd-capplet_2.24.0-2_amd64.deb Files: 870bd0779fa027a5eb13d606edd0ac52 1478 gnome optional libgnomekbd_2.24.0-2.dsc d71228d5afead72deea25ac991a92d30 3731 gnome optional libgnomekbd_2.24.0-2.diff.gz 906e330d6e1005cca3eea75d01e9bfdc 116856 libs optional libgnomekbd-common_2.24.0-2_all.deb 0b3657f2191f307c88474c833786868b 52326 libdevel optional libgnomekbd-dev_2.24.0-2_amd64.deb 76f6dafd65cc2f0cca883d7673f13aeb 49892 libs optional libgnomekbd3_2.24.0-2_amd64.deb 59b95b930bb957eda3937207f109d85f 23170 gnome optional gkbd-capplet_2.24.0-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2vairSla4ddfhTMRAqVQAJ9YY4RwKzMxenO7g9W4X2Qa9/aNEgCeOHIk bZGMK+iG6ASt91bLiFwsjc4= =FW+R -END PGP SIGNATURE- Accepted: gkbd-capplet_2.24.0-2_amd64.deb to pool/main/libg/libgnomekbd/gkbd-capplet_2.24.0-2_amd64.deb libgnomekbd-common_2.24.0-2_all.deb to pool/main/libg/libgnomekbd/libgnomekbd-common_2.24.0-2_all.deb libgnomekbd-dev_2.24.0-2_amd64.deb to pool/main/libg/libgnomekbd/libgnomekbd-dev_2.24.0-2_amd64.deb libgnomekbd3_2.24.0-2_amd64.deb to pool/main/libg/libgnomekbd/libgnomekbd3_2.24.0-2_amd64.deb libgnomekbd_2.24.0-2.diff.gz to pool/main/libg/libgnomekbd/libgnomekbd_2.24.0-2.diff.gz libgnomekbd_2.24.0-2.dsc to pool/main/libg/libgnomekbd/libgnomekbd_2.24.0-2.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted qemu 0.10.2-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 07:37:15 +0200 Source: qemu Binary: qemu libqemu-dev Architecture: source amd64 Version: 0.10.2-1 Distribution: unstable Urgency: low Maintainer: Aurelien Jarno aure...@debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: libqemu-dev - static libraries and headers for QEMU qemu - fast processor emulator Changes: qemu (0.10.2-1) unstable; urgency=low . [ Aurelien Jarno ] * New upstream stable release. Checksums-Sha1: 9306a89b8fd9dbc691a8502eaafedb97708e0267 1719 qemu_0.10.2-1.dsc 22cf43d52d6c6be6d4df9e089be44a4c6ffdd120 3101437 qemu_0.10.2.orig.tar.gz e3f2170bfef7a1d0725b3caa818f54ecae7fca0c 33767 qemu_0.10.2-1.diff.gz df70c6b839144e88f6ecdfd6ba9beb1b4fc40392 15808054 qemu_0.10.2-1_amd64.deb 8072ffddc4391f2afe1e772b57ba3872218df11b 4829798 libqemu-dev_0.10.2-1_amd64.deb Checksums-Sha256: 77df5a0fe4f3f95f6c7f7bead02c575e7689b32d9bf2d42f41ac2e7e6c34fa83 1719 qemu_0.10.2-1.dsc 1ae3e5611bfa4d19c687519a5aa97435e0f8f8976857a1fab1e410910b68c0d3 3101437 qemu_0.10.2.orig.tar.gz a5d96cca72aad8187919e0cd53396df9f4d91435c82aae9306628a1492a023a7 33767 qemu_0.10.2-1.diff.gz b90f931774fcea8af6ab1021e497114545ca4e917a0174a1a95103f7fa43efaa 15808054 qemu_0.10.2-1_amd64.deb bcd86044007b293870709e04fc2842ae60443b031b73eaa6e4fcf6717aae1888 4829798 libqemu-dev_0.10.2-1_amd64.deb Files: b8ba1ac43d38fd46f244681905c45b36 1719 misc optional qemu_0.10.2-1.dsc 4142f9be55c99e1bc60adaed9b0ef857 3101437 misc optional qemu_0.10.2.orig.tar.gz 22da7c109ade3fb55364d72886a0b78d 33767 misc optional qemu_0.10.2-1.diff.gz d1ced100b2df38c84c7df1ae9a901e18 15808054 misc optional qemu_0.10.2-1_amd64.deb 8ada18a0f54d3f385aa5049e990afd80 4829798 libdevel optional libqemu-dev_0.10.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2wF8w3ao2vG823MRAkYhAJ0S2ASXSkeX2wUf2z/3qs5tX+3h3gCeMDT1 gZU6LUa8d8/UmFwL+R6HxX8= =mRTA -END PGP SIGNATURE- Accepted: libqemu-dev_0.10.2-1_amd64.deb to pool/main/q/qemu/libqemu-dev_0.10.2-1_amd64.deb qemu_0.10.2-1.diff.gz to pool/main/q/qemu/qemu_0.10.2-1.diff.gz qemu_0.10.2-1.dsc to pool/main/q/qemu/qemu_0.10.2-1.dsc qemu_0.10.2-1_amd64.deb to pool/main/q/qemu/qemu_0.10.2-1_amd64.deb qemu_0.10.2.orig.tar.gz to pool/main/q/qemu/qemu_0.10.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
Accepted control-center 1:2.24.0.1-2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 09:11:09 +0200 Source: control-center Binary: gnome-control-center capplets-data libgnome-window-settings1 libgnome-window-settings-dev gnome-control-center-dev Architecture: source all amd64 Version: 1:2.24.0.1-2 Distribution: unstable Urgency: low Maintainer: Marco Cabizza marc...@gmail.com Changed-By: Josselin Mouette j...@debian.org Description: capplets-data - configuration applets for GNOME 2 - data files gnome-control-center - utilities to configure the GNOME desktop gnome-control-center-dev - utilities to configure the GNOME desktop libgnome-window-settings-dev - Utility library for getting window manager settings (headers) libgnome-window-settings1 - Utility library for getting window manager settings Closes: 510172 Changes: control-center (1:2.24.0.1-2) unstable; urgency=low . [ Josselin Mouette ] * Depend on gnome-settings-daemon = 2.24. Closes: #510172. * Standards version is 3.8.1. * Upload to unstable. . [ Emilio Pozuelo Monfort ] * debian/rules, debian/shlibs.local: Call dh_makeshlibs for libgnome- window-settings1 instead of using shlibs.local. It was likely there to workaround dpkg-dev setting ignoring the dependency from the Depends line and using that of dpkg-shlibdeps, but it's no longer the case. As a side effect, this makes the shlibs file be versioned as it should be. . [ Loic Minier ] * Demote the scrollkeeper dep of capplets-data to a Suggest on rarian-compat | scrollkeeper; the scrollkeeper dep seems to have been added around 2002 due to use of scrollkeeper-update in the postinst. Checksums-Sha1: 07c86814f8319e1736c7db48552b2e66fa570541 2296 control-center_2.24.0.1-2.dsc 15f1272d6a229337742aa4b881f06573c8237d7a 210076 control-center_2.24.0.1-2.diff.gz 84cda6fc15c767be5c63cc329213c6cb49a4705b 2145764 capplets-data_2.24.0.1-2_all.deb f88d2ebaf2f92ecdb08265c31a1e98da7f286a6b 105576 libgnome-window-settings-dev_2.24.0.1-2_all.deb ac0f267b4573dda0f06756661e686bc79165b720 103090 gnome-control-center-dev_2.24.0.1-2_all.deb 857a759b4aaa1351d53b8900debad2c92ad1c52c 458576 gnome-control-center_2.24.0.1-2_amd64.deb 186c359413cff4130066d56729b1c8551d632dee 113258 libgnome-window-settings1_2.24.0.1-2_amd64.deb Checksums-Sha256: cb9ac725b489d3447ec6d46f36779e18b135afe6764ed6bf08eacd9e8de9c3be 2296 control-center_2.24.0.1-2.dsc 61a28b27060dcd99125da3733bb15be7e34afe1bf4cc5b1aaf6637c61c5807df 210076 control-center_2.24.0.1-2.diff.gz 9cbf0e0020e51c3a4f96b1ce5352bb76a07b17241986c3ffc252d2ed004ffaf6 2145764 capplets-data_2.24.0.1-2_all.deb 78ab91a9bcf7451d319eaadf249451d50d20b1c6181e9cacc90e1b86c9b5925c 105576 libgnome-window-settings-dev_2.24.0.1-2_all.deb 1bda11bd52c61853ad5c02ac05392e27d5a9aa13eb11c20dadc9f35ab8807d0c 103090 gnome-control-center-dev_2.24.0.1-2_all.deb b03d344551fc05bb57ad98032b34d1f6894c17063711b6eb2440e0dda090467b 458576 gnome-control-center_2.24.0.1-2_amd64.deb 86dbe186f5bb1974aaf5a0a0224112a086868b398fcd8e68907c1879eba44f9d 113258 libgnome-window-settings1_2.24.0.1-2_amd64.deb Files: c9ca6c58fd830ebff29a9affe602a661 2296 gnome optional control-center_2.24.0.1-2.dsc f98cba6f653900398a77ac4e88abb22d 210076 gnome optional control-center_2.24.0.1-2.diff.gz e00c4a9b234480a43262da28dd11c18d 2145764 gnome optional capplets-data_2.24.0.1-2_all.deb 4564a2c814a21c80e921517032eb386a 105576 libdevel optional libgnome-window-settings-dev_2.24.0.1-2_all.deb 0be721e7adbcfc32ea07c143995d76bb 103090 devel optional gnome-control-center-dev_2.24.0.1-2_all.deb 4d0408cdab61d193a49dec3b635c122d 458576 gnome optional gnome-control-center_2.24.0.1-2_amd64.deb f5829b052a7e71dce513b3f1b72fdd6f 113258 libs optional libgnome-window-settings1_2.24.0.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2wHgrSla4ddfhTMRApdQAKDmkfA+5RfJ55r917VPKrjGFQppRACfXzm1 QFpgYoJ1u3X7Nk8OJtVdZP4= =0HJ7 -END PGP SIGNATURE- Accepted: capplets-data_2.24.0.1-2_all.deb to pool/main/c/control-center/capplets-data_2.24.0.1-2_all.deb control-center_2.24.0.1-2.diff.gz to pool/main/c/control-center/control-center_2.24.0.1-2.diff.gz control-center_2.24.0.1-2.dsc to pool/main/c/control-center/control-center_2.24.0.1-2.dsc gnome-control-center-dev_2.24.0.1-2_all.deb to pool/main/c/control-center/gnome-control-center-dev_2.24.0.1-2_all.deb gnome-control-center_2.24.0.1-2_amd64.deb to pool/main/c/control-center/gnome-control-center_2.24.0.1-2_amd64.deb libgnome-window-settings-dev_2.24.0.1-2_all.deb to pool/main/c/control-center/libgnome-window-settings-dev_2.24.0.1-2_all.deb libgnome-window-settings1_2.24.0.1-2_amd64.deb to pool/main/c/control-center/libgnome-window-settings1_2.24.0.1-2_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted redland-bindings 1.0.8.1-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 00:24:21 -0700 Source: redland-bindings Binary: librdf-perl python-librdf librdf-ruby php5-librdf Architecture: source i386 Version: 1.0.8.1-2 Distribution: unstable Urgency: low Maintainer: Dave Beckett daj...@debian.org Changed-By: Dave Beckett daj...@debian.org Description: librdf-perl - Perl language bindings for the Redland RDF library librdf-ruby - Ruby 1.8 language bindings for the Redland RDF library php5-librdf - PHP5 language bindings for the Redland RDF library python-librdf - Python language bindings for the Redland RDF library Closes: 402612 Changes: redland-bindings (1.0.8.1-2) unstable; urgency=low . * Use new sections ruby, php for librdf-ruby and php5-librdf respectively. * Merge features from ubuntu packaging. Thanks to Matthias Klose (not taking linker -Wl,--as-needed since that makes dyloading fail to pull in raptor symbols): debian/rules: - get python lib dir from distutils - make dh_pycentral use symlinks debian/python-librdf.examples: - add data/dc.rdf to examples dir and adjust example.py to point to it (Closes: #402612) * Patch python/Makefile.in so it can allow the include dir to be overridden by the particular python version build in debian/rules using PYTHON_INCLUDES Checksums-Sha1: 0e9bebc01d04d349fb1630fc49bdb70a09c4ccb8 1396 redland-bindings_1.0.8.1-2.dsc 84ca1b94155918541b31d3e5c5a7d6ca0e4e7d93 7269 redland-bindings_1.0.8.1-2.diff.gz ab89707c23670b325ae8cd9fd85b019bebde2d69 144536 librdf-perl_1.0.8.1-2_i386.deb bc6424c5acefbe8b7ea0bd61049ff4dfe53f0f19 109340 python-librdf_1.0.8.1-2_i386.deb edd03594d786b1f31076d716b8164a975ac3e9a6 56650 librdf-ruby_1.0.8.1-2_i386.deb fc72a70ed45bc49ed7515504b888a69d8d4528fc 44070 php5-librdf_1.0.8.1-2_i386.deb Checksums-Sha256: 053b08e5abdc2d10dc0e1c337979381bcfa42c0ae8514f9a52a3386257708daf 1396 redland-bindings_1.0.8.1-2.dsc c39e4c52f4354c8ab3a935d8e4a9946c4f941f114dd7b413913d0a6782ae1a2b 7269 redland-bindings_1.0.8.1-2.diff.gz 453deda4d8857b73fb4dae7c332acef6b0bb1bc6098992780dfbd43bfab97288 144536 librdf-perl_1.0.8.1-2_i386.deb 4aa4a9f1340a4db4c48c4d7b66e8aa1bc7e2ce0961bf8fda98984c9b4bb671b8 109340 python-librdf_1.0.8.1-2_i386.deb 1231c406f20a4871a40160be0e0a1176227c0af17de3a8487403c5eedfa62c62 56650 librdf-ruby_1.0.8.1-2_i386.deb 1e9f8d8de88922e577aa6fe342edac4258174b03618543229e1fc95ee616e84b 44070 php5-librdf_1.0.8.1-2_i386.deb Files: 3f62d6057d3ccef36b2ae201d16e205c 1396 devel optional redland-bindings_1.0.8.1-2.dsc 1c9dd7ed29700a3fa94819890fec2c0e 7269 devel optional redland-bindings_1.0.8.1-2.diff.gz 194b365d872e474cc2f863adea90d12c 144536 perl optional librdf-perl_1.0.8.1-2_i386.deb 9ee2ac23e48e8304627796e6c1af9d64 109340 python optional python-librdf_1.0.8.1-2_i386.deb d9e2672d3fa1dc1a76d1a92d6a8eae10 56650 ruby optional librdf-ruby_1.0.8.1-2_i386.deb f5c0d1646c27114b68bcbfa573e6 44070 php optional php5-librdf_1.0.8.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2wCSQ+ySUE9xlVoRAi6HAKCmSN+w0WhinfjfhUnhj7kri2zRwwCfT0jn mRl5fkGGpV7nAzrSOd5ZZxk= =CbqY -END PGP SIGNATURE- Accepted: librdf-perl_1.0.8.1-2_i386.deb to pool/main/r/redland-bindings/librdf-perl_1.0.8.1-2_i386.deb librdf-ruby_1.0.8.1-2_i386.deb to pool/main/r/redland-bindings/librdf-ruby_1.0.8.1-2_i386.deb php5-librdf_1.0.8.1-2_i386.deb to pool/main/r/redland-bindings/php5-librdf_1.0.8.1-2_i386.deb python-librdf_1.0.8.1-2_i386.deb to pool/main/r/redland-bindings/python-librdf_1.0.8.1-2_i386.deb redland-bindings_1.0.8.1-2.diff.gz to pool/main/r/redland-bindings/redland-bindings_1.0.8.1-2.diff.gz redland-bindings_1.0.8.1-2.dsc to pool/main/r/redland-bindings/redland-bindings_1.0.8.1-2.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted cfitsio3 3.140-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 09:37:44 +0200 Source: cfitsio3 Binary: libcfitsio3-dev libcfitsio3-dbg libcfitsio3 libcfitsio3-doc Architecture: source all amd64 Version: 3.140-1 Distribution: unstable Urgency: low Maintainer: Aurelien Jarno aure...@debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: libcfitsio3 - shared library for I/O with FITS format data files libcfitsio3-dbg - library for I/O with FITS format data files (debugging symbols) libcfitsio3-dev - static library for I/O with FITS format data files libcfitsio3-doc - documentation for cfitsio Changes: cfitsio3 (3.140-1) unstable; urgency=low . * New upstream version. * Upgrade Standard-Version to 3.8.1 (no changes). Checksums-Sha1: ae7490c68f491958ee894c0e5ee4043e13fef846 1036 cfitsio3_3.140-1.dsc 54c10c83e1edc9901229169b3aba337677e468a7 2903379 cfitsio3_3.140.orig.tar.gz 3229b1a7811ce12408ed051e9ec855d5d738b9a0 13920 cfitsio3_3.140-1.diff.gz 5af6a783f22184005b343a29f9a4c7b56fad9735 1216518 libcfitsio3-doc_3.140-1_all.deb 14b4f5b2c70ab9b6ea729bd9d77955cac47f6f62 693560 libcfitsio3-dev_3.140-1_amd64.deb 75ba6a32491eb7dd72da37c70bea9a567d5afd03 734020 libcfitsio3-dbg_3.140-1_amd64.deb 5d1e373038184f7c527ea5e4fc698b8181a4f498 582568 libcfitsio3_3.140-1_amd64.deb Checksums-Sha256: a5206085a88d3d815a4bbcde2eb8662dab37e24a1dd6daca64670120f81f93db 1036 cfitsio3_3.140-1.dsc d45e253d513d8df331a0294d243460773c57f9045878c8b79efbc7427c873d96 2903379 cfitsio3_3.140.orig.tar.gz 60e838802b7ae517eac3bd414bd8e7cee34d79783a5fb5fd30b6ffadee6fc752 13920 cfitsio3_3.140-1.diff.gz 41d1d6239203147c6acc87e91c24f8bf2507f99722268a472090cf39ed594180 1216518 libcfitsio3-doc_3.140-1_all.deb 0bdc681d47c5af250bca4487ad640d9e88185c66d9e3b2bce3158c9b6516c11c 693560 libcfitsio3-dev_3.140-1_amd64.deb 98978d71e51ec3b434f8b7105876c5af80753c45d0be1a682fb6b5b5c67c906f 734020 libcfitsio3-dbg_3.140-1_amd64.deb 0f100f735e0e635a0f239bea510a76aaec1577298c329a877988afa73fc2f17b 582568 libcfitsio3_3.140-1_amd64.deb Files: 4b01caa743c520d12c15f56ca34cbc74 1036 devel optional cfitsio3_3.140-1.dsc 881c0bd1a70e8679cd8d271b19f3f29d 2903379 devel optional cfitsio3_3.140.orig.tar.gz f5911a6315db4456410c4c3ab874252a 13920 devel optional cfitsio3_3.140-1.diff.gz 07b4311fe066c101ef9f7db310f32acb 1216518 doc optional libcfitsio3-doc_3.140-1_all.deb 0713b00d3bcf008b8053abbc550dc583 693560 libdevel optional libcfitsio3-dev_3.140-1_amd64.deb 6ee96db9cbd40b57e92f6143503d7c74 734020 devel extra libcfitsio3-dbg_3.140-1_amd64.deb 9c4f0c0e8299c8b5dd894cf15b84611e 582568 devel optional libcfitsio3_3.140-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2whQw3ao2vG823MRAofqAKCKO6/U8hpZxtwMZJuSpt/VawffYgCcDGeV EOy9K1BWxHmhbQa3jmZa3Ag= =pwiL -END PGP SIGNATURE- Accepted: cfitsio3_3.140-1.diff.gz to pool/main/c/cfitsio3/cfitsio3_3.140-1.diff.gz cfitsio3_3.140-1.dsc to pool/main/c/cfitsio3/cfitsio3_3.140-1.dsc cfitsio3_3.140.orig.tar.gz to pool/main/c/cfitsio3/cfitsio3_3.140.orig.tar.gz libcfitsio3-dbg_3.140-1_amd64.deb to pool/main/c/cfitsio3/libcfitsio3-dbg_3.140-1_amd64.deb libcfitsio3-dev_3.140-1_amd64.deb to pool/main/c/cfitsio3/libcfitsio3-dev_3.140-1_amd64.deb libcfitsio3-doc_3.140-1_all.deb to pool/main/c/cfitsio3/libcfitsio3-doc_3.140-1_all.deb libcfitsio3_3.140-1_amd64.deb to pool/main/c/cfitsio3/libcfitsio3_3.140-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
Accepted compiz-fusion-plugins-main 0.8.2-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 06 Apr 2009 23:03:15 +0200 Source: compiz-fusion-plugins-main Binary: compiz-fusion-plugins-main Architecture: source amd64 Version: 0.8.2-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-plugins-main - Compiz Fusion plugins - main collection Changes: compiz-fusion-plugins-main (0.8.2-1) unstable; urgency=low . * New upstream release * update Standards-Version to 3.8.1 * add gbp.conf for use with git-buildpackage Checksums-Sha1: 19d6e070bdec442bd83dfd572083b19c946d7a19 1464 compiz-fusion-plugins-main_0.8.2-1.dsc 1ba0a928a547153d31393ec6c1f06eb5781e69f1 1352531 compiz-fusion-plugins-main_0.8.2.orig.tar.gz f38862785e0e330e3d0451ef69de99a60c517b93 2881 compiz-fusion-plugins-main_0.8.2-1.diff.gz 7fb8b02904b5b56bcba27798ff840a9af3694ae6 1840134 compiz-fusion-plugins-main_0.8.2-1_amd64.deb Checksums-Sha256: d81945d719918d7affdf98795da863f531c28274b58ef3f946747fd148e5f8e2 1464 compiz-fusion-plugins-main_0.8.2-1.dsc 85e0eaa4419adef8e3dd5003316db4ca80046ea2f4f92eab3b6b328eaa420f83 1352531 compiz-fusion-plugins-main_0.8.2.orig.tar.gz 2e493493359c5759f30aebdb920e0c7ba248f176f5d3f5b28c0ec9937485cdbf 2881 compiz-fusion-plugins-main_0.8.2-1.diff.gz 2bffe81edfae2d0a38ef835b614cc7c7c94ee942c9efb4a007d3d43c938ae2c3 1840134 compiz-fusion-plugins-main_0.8.2-1_amd64.deb Files: 49b7ca88898f3b8adaf183fe6a0f16a4 1464 x11 extra compiz-fusion-plugins-main_0.8.2-1.dsc 2252c378c494b5286d3d045b112f3a03 1352531 x11 extra compiz-fusion-plugins-main_0.8.2.orig.tar.gz 0444cc8b6f50664007b1f57adfef05db 2881 x11 extra compiz-fusion-plugins-main_0.8.2-1.diff.gz d9743c2fc058f73b742615acb94c7bc0 1840134 x11 extra compiz-fusion-plugins-main_0.8.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2xOyynjLPm522B0RAnDqAJ9+7rl/KXKrMhDRKUxhRxKv6KygvgCfRNBe V1AwQhSqu99QbvF0zOinSc8= =4+R0 -END PGP SIGNATURE- Accepted: compiz-fusion-plugins-main_0.8.2-1.diff.gz to pool/main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.8.2-1.diff.gz compiz-fusion-plugins-main_0.8.2-1.dsc to pool/main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.8.2-1.dsc compiz-fusion-plugins-main_0.8.2-1_amd64.deb to pool/main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.8.2-1_amd64.deb compiz-fusion-plugins-main_0.8.2.orig.tar.gz to pool/main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.8.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
Accepted compizconfig-backend-kconfig 0.8.2~git20090205.82ea41ec-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 05 Apr 2009 22:39:07 +0200 Source: compizconfig-backend-kconfig Binary: compizconfig-backend-kconfig Architecture: source amd64 Version: 0.8.2~git20090205.82ea41ec-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compizconfig-backend-kconfig - Compiz Fusion configuration system - kconfig backend Changes: compizconfig-backend-kconfig (0.8.2~git20090205.82ea41ec-1) unstable; urgency=low . * New upstream release. * Switch upstream source from kconfig to kconfig4 (KDE4 version). * Update debian/rules for new upstream (cmake) build system * Remove autoconf etc deps and replace them with cmake. * add build-depends and modify build system to use quilt - New force-link-against-lX11.patch: force linking with -lX11 Checksums-Sha1: 4cabb927d675338aec348529b3ef5fcefbbb7fb9 1447 compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1.dsc 57e5a52dd7ef0c05617678f55d6cf5d38c0b59db 22038 compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec.orig.tar.gz bb02db29db855fd2d0803dac469afa957379775c 2514 compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1.diff.gz eb773930e1308eac3090bb34f5b749518894b0a4 33942 compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1_amd64.deb Checksums-Sha256: 0755646fb4445cd7d0e45e8f06b20ebd478b6953329abd1fa0cb7c7de95b1207 1447 compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1.dsc 78b149f68383ade16887050da423945109d8f04c374e01e6ab54ba89b8e9f031 22038 compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec.orig.tar.gz f027967f359894d5a2143f691d405899fdcb9599c992c853d5da10785a7de92d 2514 compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1.diff.gz 25ff40ec5460b90ead44f498d3b13d6f686cda1bdd385b0fb16fc3456bfaff32 33942 compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1_amd64.deb Files: c39cea03a7f5d01994cfab3c728ee7b3 1447 x11 extra compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1.dsc dfd061d577ba6c17b8cefcebf97d37ab 22038 x11 extra compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec.orig.tar.gz 6d9c032c5f1707c0506e93c74c1237a3 2514 x11 extra compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1.diff.gz d4169b87d9a7c8fe46462d65e404ff59 33942 x11 extra compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2xOxynjLPm522B0RAhSBAJ0eF+Rfsm/EsTrwFELuFRQzRF4CMACfVdsn 2FlVf6qSfqwN0s40OwZD+V4= =5kJN -END PGP SIGNATURE- Accepted: compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1.diff.gz to pool/main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1.diff.gz compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1.dsc to pool/main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1.dsc compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1_amd64.deb to pool/main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec-1_amd64.deb compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec.orig.tar.gz to pool/main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.8.2~git20090205.82ea41ec.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
Accepted plasma-widget-weather 1.0.0-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 11:38:17 +0300 Source: plasma-widget-weather Binary: plasma-widget-weather Architecture: source amd64 Version: 1.0.0-2 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian .org Changed-By: Modestas Vainius modes...@vainius.eu Description: plasma-widget-weather - Plasma weather widget (with forecast display support) Changes: plasma-widget-weather (1.0.0-2) unstable; urgency=low . * Replace complex debhelper scripts with simplier cmake.mk. * Upload to unstable. * Bump Standards-Version to 3.8.1. Checksums-Sha1: 856bc6f60b6813a028be7456531e12349fb86b38 1456 plasma-widget-weather_1.0.0-2.dsc e599bebd3debb59c720d609c82f61126c4b68bb1 3870 plasma-widget-weather_1.0.0-2.diff.gz b501c8d41e4ec445f1eae7c4fcacddeab720a354 72262 plasma-widget-weather_1.0.0-2_amd64.deb Checksums-Sha256: 950c83e1a963990c68acdb2c284dcccebfdd40e217e59686dcf250d022648231 1456 plasma-widget-weather_1.0.0-2.dsc 5cba99d029bd8f6c32f98c4773b5d3ddf2f99bbace0a954b91b036bc62f103e4 3870 plasma-widget-weather_1.0.0-2.diff.gz fe1bd874e19032e2510c82979a778778f37aef816c8ffb57826b586b9658d317 72262 plasma-widget-weather_1.0.0-2_amd64.deb Files: 6459f1f4a4c3ef03baf28b72454d6195 1456 kde optional plasma-widget-weather_1.0.0-2.dsc 5e2d22388507c1bf3119889314635c7b 3870 kde optional plasma-widget-weather_1.0.0-2.diff.gz 5d78374a7d2eefb2ce39f7c858fb1fdd 72262 kde optional plasma-widget-weather_1.0.0-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknbE50ACgkQHO9JRnPq4hRLSQCfdxDvYfJxD+nYh3BsbspG6UEY uuIAoNlNA5M9tCR1Hp9olRavuNysh1fv =EtT1 -END PGP SIGNATURE- Accepted: plasma-widget-weather_1.0.0-2.diff.gz to pool/main/p/plasma-widget-weather/plasma-widget-weather_1.0.0-2.diff.gz plasma-widget-weather_1.0.0-2.dsc to pool/main/p/plasma-widget-weather/plasma-widget-weather_1.0.0-2.dsc plasma-widget-weather_1.0.0-2_amd64.deb to pool/main/p/plasma-widget-weather/plasma-widget-weather_1.0.0-2_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted compiz-fusion-bcop 0.8.2-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 05 Apr 2009 22:16:11 +0200 Source: compiz-fusion-bcop Binary: compiz-fusion-bcop Architecture: source all Version: 0.8.2-1 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-bcop - Compiz Fusion option code generator Changes: compiz-fusion-bcop (0.8.2-1) unstable; urgency=low . * New upstream release * add gbp.conf for use with git-buildpackage * lintian fixes: - update Standards-Version to 3.8.1 - build binary in binary-indep, not binary-arch Checksums-Sha1: 74b614746e91260b76adfbd145346996d9fec813 1092 compiz-fusion-bcop_0.8.2-1.dsc b2ac59f747442eed114ac60afa38f0d3491671ec 17709 compiz-fusion-bcop_0.8.2.orig.tar.gz 8a08cf83970f84cdecee53ff9014536191d68ca7 2047 compiz-fusion-bcop_0.8.2-1.diff.gz ac9e9fb95f003a275d433ecf3ba5df3dd66db14d 9448 compiz-fusion-bcop_0.8.2-1_all.deb Checksums-Sha256: 8434caae983e5e0d3adf91fc4407e883a00c1998bc9044e02df1f4e4f763440f 1092 compiz-fusion-bcop_0.8.2-1.dsc 00bcbb278a0eb5b63381b845876fc4b8f1b58be20b2e36a21c13c233d04af178 17709 compiz-fusion-bcop_0.8.2.orig.tar.gz 175745fe6de9c8d88197f6046b51ef9550313f99c76c41b4abb6ea3c776eff52 2047 compiz-fusion-bcop_0.8.2-1.diff.gz 25c8f2c5072cbf361c18edb7ca9a2667b8f627d75735126f4a64365e6b2ad4ad 9448 compiz-fusion-bcop_0.8.2-1_all.deb Files: f7c0d285f7c991bddc53e25ed46a37b9 1092 x11 extra compiz-fusion-bcop_0.8.2-1.dsc f2152da99a8bf61f9a498b24a5077ea1 17709 x11 extra compiz-fusion-bcop_0.8.2.orig.tar.gz d0c6d5fc20eb7f197bb346ef9f54ca41 2047 x11 extra compiz-fusion-bcop_0.8.2-1.diff.gz e5be83b0f18b82dfb43204f85fc34bb8 9448 x11 extra compiz-fusion-bcop_0.8.2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2xOxynjLPm522B0RArPRAJsESSK93VPBE+/o0Y8E37iW5bjakACeITlh aLJiGZtHkNI7GzoPdRMbU3A= =anh0 -END PGP SIGNATURE- Accepted: compiz-fusion-bcop_0.8.2-1.diff.gz to pool/main/c/compiz-fusion-bcop/compiz-fusion-bcop_0.8.2-1.diff.gz compiz-fusion-bcop_0.8.2-1.dsc to pool/main/c/compiz-fusion-bcop/compiz-fusion-bcop_0.8.2-1.dsc compiz-fusion-bcop_0.8.2-1_all.deb to pool/main/c/compiz-fusion-bcop/compiz-fusion-bcop_0.8.2-1_all.deb compiz-fusion-bcop_0.8.2.orig.tar.gz to pool/main/c/compiz-fusion-bcop/compiz-fusion-bcop_0.8.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
Accepted compiz-fusion-plugins-extra 0.8.2-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 08:56:36 +0200 Source: compiz-fusion-plugins-extra Binary: compiz-fusion-plugins-extra Architecture: source amd64 Version: 0.8.2-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-plugins-extra - Compiz Fusion plugins - extra collection Changes: compiz-fusion-plugins-extra (0.8.2-1) unstable; urgency=low . * New upstream release. * Add gbp.conf for use with git-buildpackage. * Add build-dep on libglu1-mesa-dev Checksums-Sha1: 6ec21fc485fef83cedf55a96029bf28d58a85ae5 1484 compiz-fusion-plugins-extra_0.8.2-1.dsc 04432b73b80e8ec3a75495bfe07221e1704df4aa 3480249 compiz-fusion-plugins-extra_0.8.2.orig.tar.gz b886f62d897485611968279aa2b762a542db6201 4049 compiz-fusion-plugins-extra_0.8.2-1.diff.gz fb6e7e27a39359f403a0e8af5891b36ae8a3f248 3223498 compiz-fusion-plugins-extra_0.8.2-1_amd64.deb Checksums-Sha256: 8290681be4572e68882b6a109b28ddf158ae7888e06412afdf7cc12eead57615 1484 compiz-fusion-plugins-extra_0.8.2-1.dsc 9ab6ecffcdcb9559583e65d22e71589fc14ec16979fa198488d66464c91e3940 3480249 compiz-fusion-plugins-extra_0.8.2.orig.tar.gz 21f8b177354e63d4d8ada3e02012e4fe75350ef3bdeb5dc3bf023912a21a251c 4049 compiz-fusion-plugins-extra_0.8.2-1.diff.gz 16a634e8bfc574b6ce5f219feef28be7ce0eb3cfdfc7647cfe3922fd56bf89e4 3223498 compiz-fusion-plugins-extra_0.8.2-1_amd64.deb Files: 6e7710c2e17f6e01d8172b645018594a 1484 x11 extra compiz-fusion-plugins-extra_0.8.2-1.dsc 4d4311217da6b8f443d9e4e390a0f5c1 3480249 x11 extra compiz-fusion-plugins-extra_0.8.2.orig.tar.gz 55dda6af51c72f60c3da04a84e78a977 4049 x11 extra compiz-fusion-plugins-extra_0.8.2-1.diff.gz 44905bc8e7a09068905cbbed78e9957f 3223498 x11 extra compiz-fusion-plugins-extra_0.8.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2xOyynjLPm522B0RAqHiAJwLfzQYBqA4zkwV3mCxW0Zx3wS0swCfUjV3 a3GDMxuGdARUsrj9ze4wsvQ= =g2e7 -END PGP SIGNATURE- Accepted: compiz-fusion-plugins-extra_0.8.2-1.diff.gz to pool/main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.8.2-1.diff.gz compiz-fusion-plugins-extra_0.8.2-1.dsc to pool/main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.8.2-1.dsc compiz-fusion-plugins-extra_0.8.2-1_amd64.deb to pool/main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.8.2-1_amd64.deb compiz-fusion-plugins-extra_0.8.2.orig.tar.gz to pool/main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.8.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
Accepted compiz 0.8.2-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 01 Apr 2009 00:00:10 +0200 Source: compiz Binary: compiz compiz-core compiz-dev compiz-gtk compiz-kde compiz-gnome compiz-plugins libdecoration0 libdecoration0-dev Architecture: source all amd64 Version: 0.8.2-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz - OpenGL window and compositing manager compiz-core - OpenGL window and compositing manager compiz-dev - OpenGL window and compositing manager - development files compiz-gnome - OpenGL window and compositing manager - GNOME window decorator compiz-gtk - OpenGL window and compositing manager - Gtk window decorator compiz-kde - OpenGL window and compositing manager - KDE window decorator compiz-plugins - OpenGL window and compositing manager - plugins libdecoration0 - Compiz window decoration library libdecoration0-dev - Compiz window decoration library - development files Changes: compiz (0.8.2-1) unstable; urgency=low . * new upstream release. * update location of compiz-gnome desktop file * add new app desktop file for compiz to compiz-core * update build-deps to use kdebase-workspace-dev * add build-dep on libxslt1-dev * disable kde3 decorator and enable kde4 decorator * include a gbp.conf for use with git-buildpackage * bump the libdecoration0 shlibs version to 0.8.2 * update compiz-manager to upstream's 223180bf * Obsolete patches now removed: - disable-libx11-xcb-support.patch - xscreensaver-damage-fix.patch - compiz-manager-posixly-correct.patch * Lintian fixes: - update Standards-Version to 3.8.1 - add misc:Depends to compiz Checksums-Sha1: 9554bdcfa4497a58e4db5161d57a45dfb4058288 1839 compiz_0.8.2-1.dsc bf01dd7983684c0736c98aaee2a40c836b3c2fda 1336740 compiz_0.8.2.orig.tar.gz 8f96e87ce1f8dee7aa6bcde685f2fe249f0b2b3b 19587 compiz_0.8.2-1.diff.gz 826b2c1f4fa14357cdeb188926bba1d6f0f7bd7e 27548 compiz_0.8.2-1_all.deb 55cbbd0b9d9b3cdd6c4327d190b4c7be4363e577 1036296 compiz-core_0.8.2-1_amd64.deb 9bcdbef5803fde12a264f8d8933a0c1f07ea2e64 56738 compiz-dev_0.8.2-1_amd64.deb 7764fcfbb4c6ecf8606dbbc2a47ad4257fed1603 88890 compiz-gtk_0.8.2-1_amd64.deb ec800aa8a375f3135c3bcc53a2122a9b239f5a78 103102 compiz-kde_0.8.2-1_amd64.deb 0992a23e20b81a5e463e2344632ba21da6a6da99 39306 compiz-gnome_0.8.2-1_amd64.deb 78d441caa714deb9e574e16543e99477f6fbf520 508628 compiz-plugins_0.8.2-1_amd64.deb 1aa0415b16cd0a2db664b0bc49d545f2a9983b2d 47416 libdecoration0_0.8.2-1_amd64.deb 5ae09928a50f0d71a0347f0dd4203d23fb328c38 36180 libdecoration0-dev_0.8.2-1_amd64.deb Checksums-Sha256: 56f82e4525306d2e5ddc88740028c1b5a66282aacc7359ea5fe4d15ae8a8e935 1839 compiz_0.8.2-1.dsc e8b02c9816c070874055a91ab82c344c8cabb3c890f8be892d845cbfc099f4ba 1336740 compiz_0.8.2.orig.tar.gz 9b622e42f9446bb5cd8ad735c38942284059f761635a80dfc156dc2a0a818cf1 19587 compiz_0.8.2-1.diff.gz 6e968676e21661e3c265623a41dfdd2dbdf2b777fa70bdf0709304346e707da2 27548 compiz_0.8.2-1_all.deb 2728c5ea77a722c2e047244b529acfed4a77b6a1d6ca42ab35cb4f869f96c8e0 1036296 compiz-core_0.8.2-1_amd64.deb 4c583ac257dd651868309f00c3ff892b973d95a5cf48c31d6199b0c79bb91001 56738 compiz-dev_0.8.2-1_amd64.deb 217c07b2583a0fb3a75804c0b210177a850e7eae6894f731c4a7818245251ad2 88890 compiz-gtk_0.8.2-1_amd64.deb 6b43b60b30bce0dc12f52556a0bd36827a7b4f77678bb398d5701357652fb143 103102 compiz-kde_0.8.2-1_amd64.deb a1e8b9bde0a4438810c4d3405cf6ded651057cc7537cdcddce613459a7530a5b 39306 compiz-gnome_0.8.2-1_amd64.deb 53012c51acfdf6eff673a22e15d1d820a785a8576941ee38fba9377219cf4a84 508628 compiz-plugins_0.8.2-1_amd64.deb 381a036f6a199b3af8df12e1b832ee4b1c371095b0b56af6afe2c2b03ca478f4 47416 libdecoration0_0.8.2-1_amd64.deb 4dbd0fa1d5592f56848a482424c9771b1b497f455d1a0b0ad2ccd78840e651b9 36180 libdecoration0-dev_0.8.2-1_amd64.deb Files: 333ddc25a6a1430675ee197a58a3b07f 1839 x11 optional compiz_0.8.2-1.dsc 7a1a1098fcec1e8a734c1bae7e923809 1336740 x11 optional compiz_0.8.2.orig.tar.gz b3e033d434a86b4e6123268446fe6198 19587 x11 optional compiz_0.8.2-1.diff.gz 482370e83d7bcf42db8470af8f908c7b 27548 x11 optional compiz_0.8.2-1_all.deb 1d4fb7cb4ae333dbb00557aeedc13a42 1036296 x11 optional compiz-core_0.8.2-1_amd64.deb cfd98c4994ba500abf39d0aca42bb70e 56738 x11 optional compiz-dev_0.8.2-1_amd64.deb c1dff330bd37f19c8f57de56d27fc508 88890 x11 optional compiz-gtk_0.8.2-1_amd64.deb aa9889b0f4d7f967e00a7fed1d635f68 103102 x11 optional compiz-kde_0.8.2-1_amd64.deb f36e195a23020f8409a3867a4cf5a9d6 39306 x11 optional compiz-gnome_0.8.2-1_amd64.deb 264006d7cb3420a41eec8aec0c5ed119 508628 x11 optional compiz-plugins_0.8.2-1_amd64.deb 9a483d829f8d7e681a5c94ff2de940a3 47416 x11 optional libdecoration0_0.8.2-1_amd64.deb f2657b90db9572c5672d54a90b5dbc78 36180 libdevel optional libdecoration0-dev_0.8.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version:
Accepted compizconfig-backend-gconf 0.8.2-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 05 Apr 2009 22:27:13 +0200 Source: compizconfig-backend-gconf Binary: compizconfig-backend-gconf Architecture: source amd64 Version: 0.8.2-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compizconfig-backend-gconf - Compiz Fusion configuration system - gconf backend Changes: compizconfig-backend-gconf (0.8.2-1) unstable; urgency=low . * New upstream release. * add gbp.conf for use with git-buildpackage * update compiz related build-deps to 0.8.2 * update Standards-Version to 3.8.1 Checksums-Sha1: 6f99f00cec7db6a60cde430e7c93339d66318e40 1307 compizconfig-backend-gconf_0.8.2-1.dsc 6a07b0fa4f709f00b6ffb8b0337346d3460ffc1d 20947 compizconfig-backend-gconf_0.8.2.orig.tar.gz 93cb11588b776e64251361a09472037ebb98f03f 2200 compizconfig-backend-gconf_0.8.2-1.diff.gz 6c90073e4ed67deb5dacb1e307167ea5cf1e7e0a 17926 compizconfig-backend-gconf_0.8.2-1_amd64.deb Checksums-Sha256: 2c5f2513efcd35963a68d5a82a9db19bd548fca346fe1f13e54004e16c769883 1307 compizconfig-backend-gconf_0.8.2-1.dsc 97e3e1d92b70399768b5b6cb1190e2f431bcdbea34c0901c04febb0646a83edc 20947 compizconfig-backend-gconf_0.8.2.orig.tar.gz 6f33397595c6cae7a5a3976f3782d181b8038e85f6526f9b53a8cd3c0d4b2434 2200 compizconfig-backend-gconf_0.8.2-1.diff.gz 7e83d2b97e9ad4fcc6af21a1e2dc30757744628c5eb1ab00a8a4e9e1e4e5022d 17926 compizconfig-backend-gconf_0.8.2-1_amd64.deb Files: 0871213098d3e798c852f42ea3f2cc5a 1307 x11 extra compizconfig-backend-gconf_0.8.2-1.dsc 0487978e1059d5f3239246208508f42f 20947 x11 extra compizconfig-backend-gconf_0.8.2.orig.tar.gz 4d2e6934f63d0be9ce8a7f786d646561 2200 x11 extra compizconfig-backend-gconf_0.8.2-1.diff.gz 707471cfd8bfb78ce237fe7cdd4ee8c4 17926 x11 extra compizconfig-backend-gconf_0.8.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2xOxynjLPm522B0RAtO4AJ9KWgJCxTm+xK0sgZzUMwu53kWpKwCdEtUy DP9HuluOxl52+24fxOZayUk= =8lmz -END PGP SIGNATURE- Accepted: compizconfig-backend-gconf_0.8.2-1.diff.gz to pool/main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.8.2-1.diff.gz compizconfig-backend-gconf_0.8.2-1.dsc to pool/main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.8.2-1.dsc compizconfig-backend-gconf_0.8.2-1_amd64.deb to pool/main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.8.2-1_amd64.deb compizconfig-backend-gconf_0.8.2.orig.tar.gz to pool/main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.8.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
Accepted ccsm 0.8.2-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 10:27:35 +0200 Source: ccsm Binary: compizconfig-settings-manager Architecture: source amd64 Version: 0.8.2-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compizconfig-settings-manager - Compizconfig Settings Manager Changes: ccsm (0.8.2-1) unstable; urgency=low . * New upstream release. * add gbp.conf for use with git-buildpackage * update/massage local patches which are still needed Checksums-Sha1: f84659c1d2edc77ca272733b36924f12938e26f1 1155 ccsm_0.8.2-1.dsc 450da4fbe6b2c74951a0aff6bae2ef07b97e4b3f 615384 ccsm_0.8.2.orig.tar.gz 22c0d7c507193e68412b39a8e0f2d75f1d1349d8 4006 ccsm_0.8.2-1.diff.gz a98d2d331402a5a071e462864e9e63ea762ab38f 637228 compizconfig-settings-manager_0.8.2-1_amd64.deb Checksums-Sha256: 6b782998e3e70b1d8de428df651fc56b51fd014b99d2cb6735d0dd97ef239d86 1155 ccsm_0.8.2-1.dsc 82f13633e5d06cdc8269017483c2745bcde30a1422bebbf8d576f1012d3bba42 615384 ccsm_0.8.2.orig.tar.gz b6d7b669a19c46a29e6bfd15cd19b6dc8dabcd1aacf8f17c55d6f943d978a8f9 4006 ccsm_0.8.2-1.diff.gz 2ceedc3002e97e9343c07a069686a1ba10b6db76f2cc8664bb046ba3eb33e097 637228 compizconfig-settings-manager_0.8.2-1_amd64.deb Files: 9c0fc64b6dbde183a3da374fbf130461 1155 x11 extra ccsm_0.8.2-1.dsc 6a84e730f7f408cd0d0f5294f6bee6ee 615384 x11 extra ccsm_0.8.2.orig.tar.gz 06da75e61506c301d647b78c9d5fc3f9 4006 x11 extra ccsm_0.8.2-1.diff.gz 317a74d0b052f64bd9f8244850fb74c9 637228 x11 extra compizconfig-settings-manager_0.8.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2xOwynjLPm522B0RAi1CAJ40dyrKK9KbJu1rHIarerwQX2PAigCggiYB FcclZDmbPhwlkjQ+IFbH4Ls= =jcYr -END PGP SIGNATURE- Accepted: ccsm_0.8.2-1.diff.gz to pool/main/c/ccsm/ccsm_0.8.2-1.diff.gz ccsm_0.8.2-1.dsc to pool/main/c/ccsm/ccsm_0.8.2-1.dsc ccsm_0.8.2.orig.tar.gz to pool/main/c/ccsm/ccsm_0.8.2.orig.tar.gz compizconfig-settings-manager_0.8.2-1_amd64.deb to pool/main/c/ccsm/compizconfig-settings-manager_0.8.2-1_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted compiz-fusion-plugins-unsupported 0.8.2-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 09:52:31 +0200 Source: compiz-fusion-plugins-unsupported Binary: compiz-fusion-plugins-unsupported Architecture: source amd64 Version: 0.8.2-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-plugins-unsupported - Compiz Fusion plugins - unsupported collection Changes: compiz-fusion-plugins-unsupported (0.8.2-1) unstable; urgency=low . * New upstream release * gbp.conf for use with git-buildpackage * bump compiz-related build-deps to = 0.8.2 * gbp.conf for use with git-buildpackage * bump compiz-related build-deps to = 0.8.2 * add build-dep on -plugins-main * include the compiz-elements.h header file though it may not be necessary Checksums-Sha1: 69e0a4f384d259d90dbbf86b71074a72f3778a84 1572 compiz-fusion-plugins-unsupported_0.8.2-1.dsc 566b2336b5eb24f766ebe0b9bdae7940b377f088 1278010 compiz-fusion-plugins-unsupported_0.8.2.orig.tar.gz 3bd10c5b3ce0fa01b60a3e64a4da8d4f17cb9bd6 2748 compiz-fusion-plugins-unsupported_0.8.2-1.diff.gz fd570201b6fb42bdb32ef7232f80edf2634069d2 1313450 compiz-fusion-plugins-unsupported_0.8.2-1_amd64.deb Checksums-Sha256: 0ca52ed6d261b312007041c482a15953c689e54105351b50eea8231f53e796a1 1572 compiz-fusion-plugins-unsupported_0.8.2-1.dsc 97768be52f531242298cd5ad7ff060b22e4f633feb30e19df7e9383995585abf 1278010 compiz-fusion-plugins-unsupported_0.8.2.orig.tar.gz 3be733d29e20d0d6a2f52ce70b3ee62cf57a63fc50ab35f1dd7f21d2a5cc0571 2748 compiz-fusion-plugins-unsupported_0.8.2-1.diff.gz af034916b35566892dd0557b310bedcba7f7af08d11d9148c196381944cbea03 1313450 compiz-fusion-plugins-unsupported_0.8.2-1_amd64.deb Files: 151c663c80df8d3571c47a3067d16494 1572 x11 extra compiz-fusion-plugins-unsupported_0.8.2-1.dsc 4512915d047f22c13f820db18adf7ef0 1278010 x11 extra compiz-fusion-plugins-unsupported_0.8.2.orig.tar.gz 461b6d5e2ca4eb144405c6559dd34339 2748 x11 extra compiz-fusion-plugins-unsupported_0.8.2-1.diff.gz 7b5d15b587ae767b4b2a3ffc0c1a95a2 1313450 x11 extra compiz-fusion-plugins-unsupported_0.8.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2xOyynjLPm522B0RAgLMAJwKYYdtFGV/KvdPLWU9uph5Bi0UWQCeIcY8 h26BEkJhdRhjPdl6XJo223g= =xYCK -END PGP SIGNATURE- Accepted: compiz-fusion-plugins-unsupported_0.8.2-1.diff.gz to pool/main/c/compiz-fusion-plugins-unsupported/compiz-fusion-plugins-unsupported_0.8.2-1.diff.gz compiz-fusion-plugins-unsupported_0.8.2-1.dsc to pool/main/c/compiz-fusion-plugins-unsupported/compiz-fusion-plugins-unsupported_0.8.2-1.dsc compiz-fusion-plugins-unsupported_0.8.2-1_amd64.deb to pool/main/c/compiz-fusion-plugins-unsupported/compiz-fusion-plugins-unsupported_0.8.2-1_amd64.deb compiz-fusion-plugins-unsupported_0.8.2.orig.tar.gz to pool/main/c/compiz-fusion-plugins-unsupported/compiz-fusion-plugins-unsupported_0.8.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
Accepted compizconfig-python 0.8.2-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 10:18:42 +0200 Source: compizconfig-python Binary: python-compizconfig Architecture: source amd64 Version: 0.8.2-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: python-compizconfig - Compizconfig bindings for python Changes: compizconfig-python (0.8.2-1) unstable; urgency=low . * New upstream release. * add gbp.conf for use with git-buildpackage * add gbp.conf for use with git-buildpackage * bump compiz-related build-deps to 0.8.2 Checksums-Sha1: dce7f27835089050c7b5bbd09d79f4a5dbc7 1450 compizconfig-python_0.8.2-1.dsc 488963ef66b8992dbd86e04303215bec08fe729d 17513 compizconfig-python_0.8.2.orig.tar.gz d1044a7e735ae79777fa15381fcf991d682da5dc 2787 compizconfig-python_0.8.2-1.diff.gz 3148abd7ca9d3791fa8ea755183ceb40989a13d8 90138 python-compizconfig_0.8.2-1_amd64.deb Checksums-Sha256: 8c21ccbc17943694b62f9d7d7ab69b251248902f609f7c322f1aed7d4f9d6d8a 1450 compizconfig-python_0.8.2-1.dsc 21719724a9b372d41613797d0d4506172acca33aa8195a606d9ef3bb8ef726eb 17513 compizconfig-python_0.8.2.orig.tar.gz d8c86950c7ab38c35b8ef2b04f073774d07c66601f5511ffdaaffbed2e1b3311 2787 compizconfig-python_0.8.2-1.diff.gz 20d3ca7b7f068348d0f3e1f74adaf679abdfe9d3dbe3dc9e4ea75c4a4bbebf28 90138 python-compizconfig_0.8.2-1_amd64.deb Files: c3ccb4ffd06557b02a54efd282a8dd6d 1450 x11 extra compizconfig-python_0.8.2-1.dsc f31ccddd6c94aa22deb1a99c807bb5ca 17513 x11 extra compizconfig-python_0.8.2.orig.tar.gz 96bfa23363229bd76b98a8252d5f4012 2787 x11 extra compizconfig-python_0.8.2-1.diff.gz b5280202afdc556c3b324fb33d214488 90138 x11 extra python-compizconfig_0.8.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2xOxynjLPm522B0RAioxAJ9j25tw73DA2v7c5sbYgavbeRNd1gCfZtl+ F24CwuHrc9KZZE/t1UStb4I= =NZpB -END PGP SIGNATURE- Accepted: compizconfig-python_0.8.2-1.diff.gz to pool/main/c/compizconfig-python/compizconfig-python_0.8.2-1.diff.gz compizconfig-python_0.8.2-1.dsc to pool/main/c/compizconfig-python/compizconfig-python_0.8.2-1.dsc compizconfig-python_0.8.2.orig.tar.gz to pool/main/c/compizconfig-python/compizconfig-python_0.8.2.orig.tar.gz python-compizconfig_0.8.2-1_amd64.deb to pool/main/c/compizconfig-python/python-compizconfig_0.8.2-1_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted gnome-screensaver 2.24.1-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 11:28:17 +0200 Source: gnome-screensaver Binary: gnome-screensaver Architecture: source amd64 Version: 2.24.1-2 Distribution: unstable Urgency: low Maintainer: Guilherme de S. Pastore gpast...@debian.org Changed-By: Josselin Mouette j...@debian.org Description: gnome-screensaver - GNOME screen saver and locker Changes: gnome-screensaver (2.24.1-2) unstable; urgency=low . * Upload to unstable. * Standards version is 3.8.1. Checksums-Sha1: a9a77be449cb966e84147261d6f056d100972b24 1954 gnome-screensaver_2.24.1-2.dsc c57eb2d9147c79b64d2efabb54927ec473b5a379 9089 gnome-screensaver_2.24.1-2.diff.gz b01b2d41adc18a1a843ef9ae36cb48883344d4c0 1937392 gnome-screensaver_2.24.1-2_amd64.deb Checksums-Sha256: 115e0a5bbe0681b7adcc975095d1313b4bb90322d73cfda63c5bed4f99b5e4fd 1954 gnome-screensaver_2.24.1-2.dsc 2d7d0286ba6e404b0f8ec4e71cb5a65d165cebdedfa5bce25fdd210ac994a4ab 9089 gnome-screensaver_2.24.1-2.diff.gz 4cbb4fcd91cee7e01eeb2628a0cf91c5173bd11ac7adcee29a5777633ee0dc95 1937392 gnome-screensaver_2.24.1-2_amd64.deb Files: 605c495421db2c3ab0eb4cb539dab66c 1954 gnome optional gnome-screensaver_2.24.1-2.dsc 562b9d5e834b7e0138de881e5f69f5a8 9089 gnome optional gnome-screensaver_2.24.1-2.diff.gz 6d1ae7398ba71b04e0ce1d1cee9672d0 1937392 gnome optional gnome-screensaver_2.24.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2yGdrSla4ddfhTMRAruRAJ9AH8qikIL9XgRo7Na5QBJw6ZUNWACgmeoK kkzqYJGPZKIfh3zwyLh4z+M= =7n/o -END PGP SIGNATURE- Accepted: gnome-screensaver_2.24.1-2.diff.gz to pool/main/g/gnome-screensaver/gnome-screensaver_2.24.1-2.diff.gz gnome-screensaver_2.24.1-2.dsc to pool/main/g/gnome-screensaver/gnome-screensaver_2.24.1-2.dsc gnome-screensaver_2.24.1-2_amd64.deb to pool/main/g/gnome-screensaver/gnome-screensaver_2.24.1-2_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted evolution-webcal 2.24.0-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 13:22:10 +0200 Source: evolution-webcal Binary: evolution-webcal Architecture: source amd64 Version: 2.24.0-1 Distribution: unstable Urgency: low Maintainer: Debian Evolution Maintainers pkg-evolution-maintain...@lists.alioth.debian.org Changed-By: Josselin Mouette j...@debian.org Description: evolution-webcal - webcal: URL handler for GNOME and Evolution Changes: evolution-webcal (2.24.0-1) unstable; urgency=low . * New upstream release. * Add myself to uploaders. * Bump build-dependency on intltool. * Standards version is 3.8.1. Checksums-Sha1: 45797d2e906333de972e3da55c799d9ca6886f36 1591 evolution-webcal_2.24.0-1.dsc 8c9f447d1d3807c3293a59a8b967591524a37ed2 188936 evolution-webcal_2.24.0.orig.tar.gz 57e98fed53f0a35892f146bbdbe63b9d834f6887 2726 evolution-webcal_2.24.0-1.diff.gz a77ed4467aabca6ec91fe18762348d689aa7f636 99466 evolution-webcal_2.24.0-1_amd64.deb Checksums-Sha256: af23e19e340be3122da27f9bd19f258693b9861b8a80278633ed2b21087ea6d4 1591 evolution-webcal_2.24.0-1.dsc 6fe579c5e0f778cc17ef6837361b3752347de91e880f81362ee90961adb30b5d 188936 evolution-webcal_2.24.0.orig.tar.gz f3e1edb999b2e1bac929012941e7ead8795390a05a8166e47d1b673b7f59019f 2726 evolution-webcal_2.24.0-1.diff.gz 203632946a36c88d2f913094348b48246799e8bf518b9cfa2c26a9a16d71509d 99466 evolution-webcal_2.24.0-1_amd64.deb Files: 7410c94cfe8a2e7e421e6e2f6490b13d 1591 gnome optional evolution-webcal_2.24.0-1.dsc 641068bd0a2cca6f47c0af9833690859 188936 gnome optional evolution-webcal_2.24.0.orig.tar.gz 62f4c10dffd6c46a31a28925eaf727a2 2726 gnome optional evolution-webcal_2.24.0-1.diff.gz 3dd1bcc15ef74056a972f6de22a6be12 99466 gnome optional evolution-webcal_2.24.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2zgorSla4ddfhTMRAl05AKDHhhGT6cr7J1WyFDwPweHDf4qZkQCgrD08 n/mclRYSe53FRmX/Ne3mh9c= =zYqR -END PGP SIGNATURE- Accepted: evolution-webcal_2.24.0-1.diff.gz to pool/main/e/evolution-webcal/evolution-webcal_2.24.0-1.diff.gz evolution-webcal_2.24.0-1.dsc to pool/main/e/evolution-webcal/evolution-webcal_2.24.0-1.dsc evolution-webcal_2.24.0-1_amd64.deb to pool/main/e/evolution-webcal/evolution-webcal_2.24.0-1_amd64.deb evolution-webcal_2.24.0.orig.tar.gz to pool/main/e/evolution-webcal/evolution-webcal_2.24.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
Accepted lbzip2 0.15-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 05 Apr 2009 22:23:48 +0200 Source: lbzip2 Binary: lbzip2 Architecture: source amd64 Version: 0.15-1 Distribution: unstable Urgency: low Maintainer: Laszlo Ersek la...@elte.hu Changed-By: Laszlo Ersek la...@elte.hu Description: lbzip2 - parallel bzip2 filter Changes: lbzip2 (0.15-1) unstable; urgency=low . * New upstream release. From the upstream ChangeLog: - fix a (theoretically occurring) wrongful premature EOF error in the single-worker decompressor, - clean up buffer sizes for IO-friendliness and logical independece, - document the derivation of the multiple-workers decompressor's splitter block size, - enable users to track peak memory usage with malloc_trace.pl. * Follow upstream's change from -O3 to -O2 in debian/rules. - Since lbzip2 is multi-threaded, -fpredictive-commoning (enabled at -O3) seems scary. - See also Don Armstrong's mail 20090217002744.gp25...@rzlab.ucr.edu (http://lists.debian.org/debian-mentors/2009/02/msg00155.html). Checksums-Sha1: d2dac392241f2191aa7fcc03a9d80610bc865a38 976 lbzip2_0.15-1.dsc f547ddbb39e4fcceb25c3ebdd586aa8a053a4ae0 62774 lbzip2_0.15.orig.tar.gz 8f608d108e99607160d4c4dc242f59cede11da26 3838 lbzip2_0.15-1.diff.gz 482dafc77d9fc7eff06b781b5fca5271e0c6c054 43004 lbzip2_0.15-1_amd64.deb Checksums-Sha256: e3af71861239db625d88662739726c627b556c3bcd54908d4a3ecbc7d5a614be 976 lbzip2_0.15-1.dsc 4b49477a4854984520995d75dab7bdc4abcb4e463a949df3db4cf635f8dadb5e 62774 lbzip2_0.15.orig.tar.gz 0b376f1b9c8cf2858a79be8985c5638d92fceaea4f0e0654abd87d8b9412962a 3838 lbzip2_0.15-1.diff.gz 9defecc22b29b775640089b9fd865ab03f0d8dd62730758535df6b1b695a96cd 43004 lbzip2_0.15-1_amd64.deb Files: 9d9dad973cb30910a37d5da04202285c 976 utils extra lbzip2_0.15-1.dsc 39e37c777860de36dd0c621c525f8bdb 62774 utils extra lbzip2_0.15.orig.tar.gz a31bea3c8895c4bee7d31b5ec7f97e25 3838 utils extra lbzip2_0.15-1.diff.gz 26cca99caaf75ca8297c811f0e3b45e5 43004 utils extra lbzip2_0.15-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknbOJAACgkQ5Sc9mGvjxCM0xQCfdH3w1mZKbHAAjd7dT6q/VKhq +VIAn131vg3VTxW6Vow5x+9032ZyErfY =coW8 -END PGP SIGNATURE- Accepted: lbzip2_0.15-1.diff.gz to pool/main/l/lbzip2/lbzip2_0.15-1.diff.gz lbzip2_0.15-1.dsc to pool/main/l/lbzip2/lbzip2_0.15-1.dsc lbzip2_0.15-1_amd64.deb to pool/main/l/lbzip2/lbzip2_0.15-1_amd64.deb lbzip2_0.15.orig.tar.gz to pool/main/l/lbzip2/lbzip2_0.15.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
Accepted krusader 2.0.0beta2+svn6253-1 (source i386 amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 11:13:44 +0200 Source: krusader Binary: krusader krusader-dbg Architecture: amd64 i386 source Version: 2.0.0beta2+svn6253-1 Distribution: unstable Urgency: low Maintainer: Fathi Boudra f...@debian.org Changed-By: Fathi Boudra f...@debian.org Description: krusader-dbg - debugging symbols for krusader krusader - twin-panel (commander-style) file manager Changes: krusader (2.0.0beta2+svn6253-1) unstable; urgency=low . * Upload to Sid. * Bump compat/debhelper to 7. * Bump Standard-Version to 3.8.1 (no changes needed). * New snasphot from svn revision 6253. * Build against kdelibs5-dev (= 4.2.0). * Switch to pkg-kde-tools. Checksums-Sha1: 27e84a488d9ae68b56a66d3f0a7261ad806e9535 4572240 krusader_2.0.0beta2+svn6253.orig.tar.gz 2c03ba49df70180dc30be400d5b0068c2cae5898 9213628 krusader-dbg_2.0.0beta2+svn6253-1_i386.deb 321db2fb99fa0e8e415d1868ce25c2e9085f1eeb 4276968 krusader_2.0.0beta2+svn6253-1_amd64.deb 34f85ea205f5ca53235264a240bd2088335b314f 4200334 krusader_2.0.0beta2+svn6253-1_i386.deb 9d2d7eee2ea497e3103da579ef961ec0f24eb176 9318754 krusader-dbg_2.0.0beta2+svn6253-1_amd64.deb c7aac084ce030a8899bde2878a1bee815c3531ea 1533 krusader_2.0.0beta2+svn6253-1.dsc c439c03636bf715a87b7b31f01f6fe0bb1e97f07 6305 krusader_2.0.0beta2+svn6253-1.diff.gz Checksums-Sha256: 250d4536470e5f4afe41e12983f877fd775aca7d594fdffabbbce5b93a558ad3 9213628 krusader-dbg_2.0.0beta2+svn6253-1_i386.deb 3ea7260151c681f5367c2cb7e6e7b7c9f879c7c355822188b9b48a42d578e5c5 9318754 krusader-dbg_2.0.0beta2+svn6253-1_amd64.deb 6bc0ac75ee62415d4540019bd063034337eb460bbde34904ecb73f1d9f8defcd 4572240 krusader_2.0.0beta2+svn6253.orig.tar.gz 6edd0275b86af443593f4a85d25777ba7aa2c21f198fe72574ed0031bfab2591 4200334 krusader_2.0.0beta2+svn6253-1_i386.deb 605567ebe991c098f9e90f500345cc3932c37f565dd1895e52dad4fc6683826f 1533 krusader_2.0.0beta2+svn6253-1.dsc aab367394e33db75893add09a944ba2f39c238868ca6724d3fcb2bb46450464a 4276968 krusader_2.0.0beta2+svn6253-1_amd64.deb bf50fd005365eefa0794cafe95a51178c8e9cce0d43004befb9198bc174e8158 6305 krusader_2.0.0beta2+svn6253-1.diff.gz Files: 63c4253632de85c8073d10b63d81eb31 6305 kde optional krusader_2.0.0beta2+svn6253-1.diff.gz 6d5ae31da497c4e84568c77f1310ed1e 4572240 kde optional krusader_2.0.0beta2+svn6253.orig.tar.gz 78f123f5a782243d48db97051d55a47f 9213628 debug extra krusader-dbg_2.0.0beta2+svn6253-1_i386.deb 7ef9e50a27c9c9936bf1954dc74c4b98 9318754 debug extra krusader-dbg_2.0.0beta2+svn6253-1_amd64.deb 83bd4df7c0d91b01dc1e6164ebdea9ae 4276968 kde optional krusader_2.0.0beta2+svn6253-1_amd64.deb 923019c87be7e3b7720b4416ec710ff0 4200334 kde optional krusader_2.0.0beta2+svn6253-1_i386.deb 6a9012369602f81e938b6c348c37e07e 1533 kde optional krusader_2.0.0beta2+svn6253-1.dsc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iJwEAQECAAYFAknbMyIACgkQjPU19mqlcvd+LAP/aZvEMUEVCkcFwoXxboHqtdMY jfoeDBG4Z7y1C4T0oC6jAyfObU6Y6HlwLU5/qZMUm/ZzRvdDPopm1QiMOTDT0P05 tU56sUTCOnvPcPJOG+hNmMh7T/Q+n7FjIbNw9QODahsl1RUv79fWUpZAM9nOZMJX ji0kAJNDnbe6/hLRNZg= =uR2u -END PGP SIGNATURE- Accepted: krusader-dbg_2.0.0beta2+svn6253-1_amd64.deb to pool/main/k/krusader/krusader-dbg_2.0.0beta2+svn6253-1_amd64.deb krusader-dbg_2.0.0beta2+svn6253-1_i386.deb to pool/main/k/krusader/krusader-dbg_2.0.0beta2+svn6253-1_i386.deb krusader_2.0.0beta2+svn6253-1.diff.gz to pool/main/k/krusader/krusader_2.0.0beta2+svn6253-1.diff.gz krusader_2.0.0beta2+svn6253-1.dsc to pool/main/k/krusader/krusader_2.0.0beta2+svn6253-1.dsc krusader_2.0.0beta2+svn6253-1_amd64.deb to pool/main/k/krusader/krusader_2.0.0beta2+svn6253-1_amd64.deb krusader_2.0.0beta2+svn6253-1_i386.deb to pool/main/k/krusader/krusader_2.0.0beta2+svn6253-1_i386.deb krusader_2.0.0beta2+svn6253.orig.tar.gz to pool/main/k/krusader/krusader_2.0.0beta2+svn6253.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
Accepted eel2 2.24.1-2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 13:37:40 +0200 Source: eel2 Binary: libeel2-dev libeel2-2.24 libeel2-data Architecture: source all amd64 Version: 2.24.1-2 Distribution: unstable Urgency: low Maintainer: Josselin Mouette j...@debian.org Changed-By: Josselin Mouette j...@debian.org Description: libeel2-2.24 - Eazel Extensions Library (for GNOME2) libeel2-data - Eazel Extensions Library - data files (for GNOME2) libeel2-dev - Eazel Extensions Library - development files (GNOME2) Changes: eel2 (2.24.1-2) unstable; urgency=low . * Upload to unstable. * Standards version is 3.8.1. Checksums-Sha1: 63167b8867e53da1b2815e761388f7cb2201f59b 1513 eel2_2.24.1-2.dsc 133ded04ed220fe3b3c510512513aaeb4e991915 168739 eel2_2.24.1-2.diff.gz e90ea8f2d94b14e45b43c88d29f5ee249f0469cd 170320 libeel2-data_2.24.1-2_all.deb 38b6e0fdc1c23ad6aa662529ab4f0788a16ada6b 118616 libeel2-dev_2.24.1-2_amd64.deb 2b4dfc67bc41bfff523db1d62aa56a4e44f2106f 267204 libeel2-2.24_2.24.1-2_amd64.deb Checksums-Sha256: c9d807ac9c41ea794925028f8c7a5fe28cca49b6108be1e448a08c98544fd1e4 1513 eel2_2.24.1-2.dsc d23223ba404231d51af8992a23cd773baed0f36ed17232892705c4674ab9c114 168739 eel2_2.24.1-2.diff.gz ce717c7c109ff89b461d70d5a54c88d4c247c7200b112bd8b1831350466f14f4 170320 libeel2-data_2.24.1-2_all.deb ff023b12158a01bb745fdaa55b4183b13063b9c8322953cd5c6db254d0615462 118616 libeel2-dev_2.24.1-2_amd64.deb a704370aa6ed7e00920b4fae970dff66ad2c3015cf8a25abec472648ebebce44 267204 libeel2-2.24_2.24.1-2_amd64.deb Files: a097fc2ceb0ec27e8b133450132d6e1b 1513 devel optional eel2_2.24.1-2.dsc fac06d2e0e08f2d7db138af225deb7dc 168739 devel optional eel2_2.24.1-2.diff.gz c031b57a3783d077df6eafa51b91631b 170320 libs optional libeel2-data_2.24.1-2_all.deb d5efb28ddf75ba8d233eff19c2528d67 118616 libdevel optional libeel2-dev_2.24.1-2_amd64.deb bf2e8d9c2e24a3d4a48aacc4aeec965e 267204 libs optional libeel2-2.24_2.24.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2zxzrSla4ddfhTMRAluqAJ9m+D9yL795DjbftOCFDCVDDtydFwCcD04L ii7z9hLE4GzPdMdiUvvjpmo= =KA6/ -END PGP SIGNATURE- Accepted: eel2_2.24.1-2.diff.gz to pool/main/e/eel2/eel2_2.24.1-2.diff.gz eel2_2.24.1-2.dsc to pool/main/e/eel2/eel2_2.24.1-2.dsc libeel2-2.24_2.24.1-2_amd64.deb to pool/main/e/eel2/libeel2-2.24_2.24.1-2_amd64.deb libeel2-data_2.24.1-2_all.deb to pool/main/e/eel2/libeel2-data_2.24.1-2_all.deb libeel2-dev_2.24.1-2_amd64.deb to pool/main/e/eel2/libeel2-dev_2.24.1-2_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted usb-modeswitch 0.9.7~beta1-1 (source powerpc)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 30 Mar 2009 19:44:55 +0200 Source: usb-modeswitch Binary: usb-modeswitch Architecture: source powerpc Version: 0.9.7~beta1-1 Distribution: experimental Urgency: low Maintainer: Didier Raboud did...@raboud.com Changed-By: Didier Raboud did...@raboud.com Description: usb-modeswitch - mode switching tool for controlling flip flop USB devices Changes: usb-modeswitch (0.9.7~beta1-1) experimental; urgency=low . * 0.9.7beta new upstream release. Major code clean up, optional success control (both suggested by Daniel Cooper), new devices * New build system (not used in Debian yet). * New option to enable success control (--success) - Manpage updated * New devices - Option iCON 210,401 - Vodafone K3760 - ZTE MF636 (aka Telstra / BigPond 7.2 Mobile Card) - Sierra Wireless Compass 597 - MobiData MBD-200HU - Hyundai Mobile MB-810 * Bump Standards to 3.8.1. No changes needed. Checksums-Sha1: 63e96d567d6d66a36399e5516f96110834c0e792 1125 usb-modeswitch_0.9.7~beta1-1.dsc 6653b890a2e290355033c04caa8fdd4e1965741e 29582 usb-modeswitch_0.9.7~beta1.orig.tar.gz a85eda967400d77fef1d51307fd9a87e095936b2 6221 usb-modeswitch_0.9.7~beta1-1.diff.gz 15b147cb8d9995966171678fe32d76490d2d20fb 27276 usb-modeswitch_0.9.7~beta1-1_powerpc.deb Checksums-Sha256: c846a95f736ce56509cbf8a7bcb3a5216f0c9ef38c43d1e8013595430f89da19 1125 usb-modeswitch_0.9.7~beta1-1.dsc 86e24eefddfc16941bb299820fdc888ee4320f4309438beecec3d751d86b17f6 29582 usb-modeswitch_0.9.7~beta1.orig.tar.gz c93de1005f69a3de472484d83fbdc55d48b7751f790f3f8067106254d06c2d1a 6221 usb-modeswitch_0.9.7~beta1-1.diff.gz 172c8a20ad3a1642b7a73d6a7cc6789978e9022b66dc61ceb314e71df185aa8c 27276 usb-modeswitch_0.9.7~beta1-1_powerpc.deb Files: e27a6611d3fc7d46fff3fc036bfeb434 1125 comm extra usb-modeswitch_0.9.7~beta1-1.dsc e7aa983a13bf35b0258c2fb06a08cd3d 29582 comm extra usb-modeswitch_0.9.7~beta1.orig.tar.gz a74f01e7dcd0608861e49654760eb6ee 6221 comm extra usb-modeswitch_0.9.7~beta1-1.diff.gz bb0a327930a4d614ad6ac682687314e1 27276 comm extra usb-modeswitch_0.9.7~beta1-1_powerpc.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknbPOUACgkQI2xgxmW0sWLeXwCcDVpqumA83xjvbTmGleQhwf1W 78cAoKltkbomqeIHjvL0+bbNuOJoMz3J =Dz0/ -END PGP SIGNATURE- Accepted: usb-modeswitch_0.9.7~beta1-1.diff.gz to pool/main/u/usb-modeswitch/usb-modeswitch_0.9.7~beta1-1.diff.gz usb-modeswitch_0.9.7~beta1-1.dsc to pool/main/u/usb-modeswitch/usb-modeswitch_0.9.7~beta1-1.dsc usb-modeswitch_0.9.7~beta1-1_powerpc.deb to pool/main/u/usb-modeswitch/usb-modeswitch_0.9.7~beta1-1_powerpc.deb usb-modeswitch_0.9.7~beta1.orig.tar.gz to pool/main/u/usb-modeswitch/usb-modeswitch_0.9.7~beta1.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
Accepted knemo 0.5.2-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 21:42:37 +1000 Source: knemo Binary: knemo Architecture: source i386 Version: 0.5.2-1 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian.org Changed-By: Mark Purcell m...@debian.org Description: knemo - network interfaces monitor for KDE's systray Closes: 433061 466025 482591 Changes: knemo (0.5.2-1) unstable; urgency=low . * New upstream release - Closes: #466025, #482591, #433061 Checksums-Sha1: 91e314a519bf63dbb7d14bdaaca63ad6ac0d7e2d 1297 knemo_0.5.2-1.dsc f6016233e87a0203eeaea150845ef99636788f19 484676 knemo_0.5.2.orig.tar.gz 5fc06854ae9e50102a6bdadf67c0923aab338234 6811 knemo_0.5.2-1.diff.gz a2b023c09943cc5869fce18979faaae3073c0067 562984 knemo_0.5.2-1_i386.deb Checksums-Sha256: 49cfa6c2b0928e31190bc6fa756309c679b7b16b99d4b2822ee03fe730d0c68d 1297 knemo_0.5.2-1.dsc ad61dafe4fbafe4ce5c684d65560b72472a9d994f37b76c9c169fecfc6ae7194 484676 knemo_0.5.2.orig.tar.gz e65d892682078b0f470926893fb202f10040ee116d345a6bbd079c037f497cb1 6811 knemo_0.5.2-1.diff.gz 61224a9bbfd376de958ee4bbb248ad940d1bb23ae0c80eb9ab5ddfd13e8c76b5 562984 knemo_0.5.2-1_i386.deb Files: 7ae67529583ba11c3a2768953c31eef2 1297 kde optional knemo_0.5.2-1.dsc ab4c9519f5dcfe46530edf3d9f24b647 484676 kde optional knemo_0.5.2.orig.tar.gz 3327a8fa0d267d9160219ce5eec8b2dd 6811 kde optional knemo_0.5.2-1.diff.gz 69939ee2c0054aea305e52b676566f48 562984 kde optional knemo_0.5.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknbPJ8ACgkQoCzanz0IthJxqgCfTWDkCYBf6sE/4wzJz5zxleB3 v9sAn359IUDSFe0uY6Bzpd9bdl3bVLLt =koyS -END PGP SIGNATURE- Accepted: knemo_0.5.2-1.diff.gz to pool/main/k/knemo/knemo_0.5.2-1.diff.gz knemo_0.5.2-1.dsc to pool/main/k/knemo/knemo_0.5.2-1.dsc knemo_0.5.2-1_i386.deb to pool/main/k/knemo/knemo_0.5.2-1_i386.deb knemo_0.5.2.orig.tar.gz to pool/main/k/knemo/knemo_0.5.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
Accepted gnome-applets 2.24.3.1-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 13:05:43 +0200 Source: gnome-applets Binary: gnome-applets-data gnome-applets gnome-applets-dbg Architecture: source all amd64 Version: 2.24.3.1-1 Distribution: unstable Urgency: low Maintainer: Guilherme de S. Pastore gpast...@debian.org Changed-By: Josselin Mouette j...@debian.org Description: gnome-applets - Various applets for GNOME 2 panel - binary files gnome-applets-data - Various applets for GNOME 2 panel - data files gnome-applets-dbg - Various applets for GNOME 2 panel - binary files with debugging s Changes: gnome-applets (2.24.3.1-1) unstable; urgency=low . * gnome-applets.preinst: don’t remove the statoverride upon first installation. * New upstream release. * Standards version is 3.8.1. * Recommend policykit-gnome. * gnome-applets.preinst: add missing #DEBHELPER# * Fix section for gnome-applets-dbg. Checksums-Sha1: 34b97424cff02f8f130a760e82a9c30c5c1b9a88 2468 gnome-applets_2.24.3.1-1.dsc 0e58ceb9b590795df5947ab1b244c4451cc24523 10426311 gnome-applets_2.24.3.1.orig.tar.gz fe4a65019afa673bc93b9603dc58861901b4fdfe 199576 gnome-applets_2.24.3.1-1.diff.gz aec334553200af5f2f6f8c98aeceaa43ff6311d0 10996202 gnome-applets-data_2.24.3.1-1_all.deb 2a51c083ca71bac2bd63c3a05e76461833c45632 349624 gnome-applets_2.24.3.1-1_amd64.deb 3ed9bc67216bea3a21e32975f4adbd64995d28a7 770830 gnome-applets-dbg_2.24.3.1-1_amd64.deb Checksums-Sha256: 2a82e7a1103c28740e8a21ce2815d16ed47e2c0badf48c836a9127d32830971d 2468 gnome-applets_2.24.3.1-1.dsc c7ec1f9d33b86a3c1428664ad3a49425368090c16397efb9349b46fac1547b0a 10426311 gnome-applets_2.24.3.1.orig.tar.gz d8eea44f2cd8ad72897fab3c4b1c5061f062167a7429a5df80efa86a47b2babe 199576 gnome-applets_2.24.3.1-1.diff.gz a9e27401be56c340539f85b0b4a19675439b5745431640dfc2f45311f851ae33 10996202 gnome-applets-data_2.24.3.1-1_all.deb 6ff5e5de89a84e2d32b3c12b406b78caa3c5181d5fbb170434a345b0ca3b9bdb 349624 gnome-applets_2.24.3.1-1_amd64.deb d63cb3a4c5c4475671fdbb7bda9e863d6e60a1aec05797b1a2f4ec7d9e8ec893 770830 gnome-applets-dbg_2.24.3.1-1_amd64.deb Files: 073890d7a8d4fe7cf70faa7266751533 2468 gnome optional gnome-applets_2.24.3.1-1.dsc 1c40b72e81ceee7bb5de221ce95e50f6 10426311 gnome optional gnome-applets_2.24.3.1.orig.tar.gz 5675b880c19f3d8dc5e7687750327902 199576 gnome optional gnome-applets_2.24.3.1-1.diff.gz 81caf79453d7d9465d0e53b93d0f4ec9 10996202 gnome optional gnome-applets-data_2.24.3.1-1_all.deb a4d97020583dc88ea4ceb30dcd2db1f0 349624 gnome optional gnome-applets_2.24.3.1-1_amd64.deb 86cd5d844261ab2462e59fbbbeab91ce 770830 debug extra gnome-applets-dbg_2.24.3.1-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2zkIrSla4ddfhTMRAso3AKC4O5pAZ+ke3OhjVSWL/bi6mX9hLQCfZ00l i6Uqf9avsfYnOtR3a93vKFE= =SBNK -END PGP SIGNATURE- Accepted: gnome-applets-data_2.24.3.1-1_all.deb to pool/main/g/gnome-applets/gnome-applets-data_2.24.3.1-1_all.deb gnome-applets-dbg_2.24.3.1-1_amd64.deb to pool/main/g/gnome-applets/gnome-applets-dbg_2.24.3.1-1_amd64.deb gnome-applets_2.24.3.1-1.diff.gz to pool/main/g/gnome-applets/gnome-applets_2.24.3.1-1.diff.gz gnome-applets_2.24.3.1-1.dsc to pool/main/g/gnome-applets/gnome-applets_2.24.3.1-1.dsc gnome-applets_2.24.3.1-1_amd64.deb to pool/main/g/gnome-applets/gnome-applets_2.24.3.1-1_amd64.deb gnome-applets_2.24.3.1.orig.tar.gz to pool/main/g/gnome-applets/gnome-applets_2.24.3.1.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted libxklavier 3.7-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 13:53:06 +0200 Source: libxklavier Binary: libxklavier12 libxklavier12-dev Architecture: source amd64 Version: 3.7-2 Distribution: unstable Urgency: low Maintainer: Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org Changed-By: Josselin Mouette j...@debian.org Description: libxklavier12 - X Keyboard Extension high-level API libxklavier12-dev - Development files for libxklavier Closes: 498182 503539 Changes: libxklavier (3.7-2) unstable; urgency=low . [ Loic Minier ] * Drop xbase-clients alternate dep. * Fix typo s/iso-cods/iso-codes/; thanks Alban Browaeys; closes: #498182. . [ Deng Xiyue ] * Use POSIX standard regex classes in sed trick in debian/rules. . [ Josselin Mouette ] * Set the GNOME team as primary maintainer. Closes: #503539. * Build-depend on libglib2.0-doc to ensure proper xrefs. * Upload to unstable; drop check-dist include. * Standards version is 3.8.1. Checksums-Sha1: 3884a851b7d2753145bdebb54d4a6cbf0eb52c58 1339 libxklavier_3.7-2.dsc a72799a419950b6738675212ca2f95d244595fad 5965 libxklavier_3.7-2.diff.gz cdc87c53861e42162ad07923861ebee9b831ed22 57062 libxklavier12_3.7-2_amd64.deb 07490a005bbb0839292f5c5bdb43e9f85cf6acef 91144 libxklavier12-dev_3.7-2_amd64.deb Checksums-Sha256: dca7a4ad4a71271dad790074d7fd098606a0d812a05b5b7d9935ea9ac4d2814b 1339 libxklavier_3.7-2.dsc 994c0165cbd1d64e837bffc9c52f493bef37e709bcb3e18342373d84b736cc3f 5965 libxklavier_3.7-2.diff.gz f3cecfcf35e332bf90094702debafe88c73ba15f74a7dc5df93d699384fa0e97 57062 libxklavier12_3.7-2_amd64.deb 770ff31d2a6668da19a614df88ab491abd1060c788c5d3a9833f642b6f75aae7 91144 libxklavier12-dev_3.7-2_amd64.deb Files: 5d9e111b72bffc33e016bc4afc21650e 1339 libs optional libxklavier_3.7-2.dsc b7bf1eaf27c32c2ece59ef8185d89ea8 5965 libs optional libxklavier_3.7-2.diff.gz 987976b24a49efaafafa828738fd4388 57062 libs optional libxklavier12_3.7-2_amd64.deb c9ea172f5bf7e04f806fcea66b658ba5 91144 libdevel optional libxklavier12-dev_3.7-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ20BZrSla4ddfhTMRAh0TAJ9glHZosqm6TTNNrBgCvUGYEYV8cQCg1nQj CkbilzSAPrAOHT3w7NOAuvw= =yzY4 -END PGP SIGNATURE- Accepted: libxklavier12-dev_3.7-2_amd64.deb to pool/main/libx/libxklavier/libxklavier12-dev_3.7-2_amd64.deb libxklavier12_3.7-2_amd64.deb to pool/main/libx/libxklavier/libxklavier12_3.7-2_amd64.deb libxklavier_3.7-2.diff.gz to pool/main/libx/libxklavier/libxklavier_3.7-2.diff.gz libxklavier_3.7-2.dsc to pool/main/libx/libxklavier/libxklavier_3.7-2.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted zodb 1:3.6.0-4 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 07 Apr 2009 11:33:08 +0200 Source: zodb Binary: python-zodb Architecture: source amd64 Version: 1:3.6.0-4 Distribution: unstable Urgency: low Maintainer: Debian/Ubuntu Zope Team pkg-zope-develop...@lists.alioth.debian.org Changed-By: Fabio Tranchitella kob...@debian.org Description: python-zodb - set of tools for using the Zope Object Database (ZODB) Changes: zodb (1:3.6.0-4) unstable; urgency=low . * debian/patches/py2.6.dpatch: updated, to make it really working. * debian/rules: added --prefix=/usr to setup.py. Checksums-Sha1: b339f95332cab009c3ede0295e8a3a8395403247 1167 zodb_3.6.0-4.dsc de18580bf68bd5cf8b7c7b2d89864c8e3b18110e 7233 zodb_3.6.0-4.diff.gz 9c64a1661e6b171ae06e2ccbebcd6cda6c3155a8 1276430 python-zodb_3.6.0-4_amd64.deb Checksums-Sha256: 19f5934d7d46d32172f734ca694a18661a573ba68e10a7ef638e3a4e057362ea 1167 zodb_3.6.0-4.dsc 49da2b41644e792c19302f4ddfdecd95fe7f3445f99fe40a2e5ba76dfb54bd1b 7233 zodb_3.6.0-4.diff.gz 642873cc28339430f49b815dfd9d13db75421f883637af2f87f7d574ab2645a2 1276430 python-zodb_3.6.0-4_amd64.deb Files: dfe363ae1be4d1c7f73f89f8623c48c2 1167 python optional zodb_3.6.0-4.dsc cf61c9225aaf9c2ea726c231f8824e85 7233 python optional zodb_3.6.0-4.diff.gz 43300582bc9044a2a072e6425b031715 1276430 python optional python-zodb_3.6.0-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknbHqcACgkQK/juK3+WFWQAsQCfciD4L9/d9jbQ+orvGWkyPLR0 rO4AnjwecnJxO4JJ3mm2bdLHh6v0duTY =Xuri -END PGP SIGNATURE- Accepted: python-zodb_3.6.0-4_amd64.deb to pool/main/z/zodb/python-zodb_3.6.0-4_amd64.deb zodb_3.6.0-4.diff.gz to pool/main/z/zodb/zodb_3.6.0-4.diff.gz zodb_3.6.0-4.dsc to pool/main/z/zodb/zodb_3.6.0-4.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted libcompizconfig 0.8.2-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 05 Apr 2009 21:47:59 +0200 Source: libcompizconfig Binary: libcompizconfig-dev libcompizconfig0 Architecture: source amd64 Version: 0.8.2-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: libcompizconfig-dev - Configuration settings library for compiz-fusion - development fi libcompizconfig0 - Configuration settings library for compiz-fusion Changes: libcompizconfig (0.8.2-1) unstable; urgency=low . * New upstream release. * Add gbp.conf for use with git-buildpackage * Add build-dep on libprotobuf-dev and protobuf-compiler. * Update Standards-Version to 3.8.1 * Remove usr/share/compizconfig from libcompizconfig0.install * update build-dep version against compiz-dev Checksums-Sha1: f2742546bb4d902f0d13448fcad977dc2de9f17d 1235 libcompizconfig_0.8.2-1.dsc d836328aac6a5ddde7c30c49d7e092eb5706d04d 70213 libcompizconfig_0.8.2.orig.tar.gz d0cbde50dff17621b181c6e0cdad8bd122362b99 3454 libcompizconfig_0.8.2-1.diff.gz f22f8c55770bdc7148bdb38334b625966e829967 134610 libcompizconfig-dev_0.8.2-1_amd64.deb 586eae93847baf31c4cf8cf74f93260ae611ac7e 122608 libcompizconfig0_0.8.2-1_amd64.deb Checksums-Sha256: 8156203300e361c233a5ce1c7e45ea839b54baab7cb45078831e84803e8a049d 1235 libcompizconfig_0.8.2-1.dsc e0b7bdc893922a66edeccc27f1711222c126ff02b1c1733b080e0ead1b4ecfcd 70213 libcompizconfig_0.8.2.orig.tar.gz ca03423a0c1e8b086c90ec4f9fbff0722bf3637b1ffb686bc339d83d63a40489 3454 libcompizconfig_0.8.2-1.diff.gz 042f9afd13b08e0ee356caba2993c955e8c375a4a47bca37f723744b42c62ba8 134610 libcompizconfig-dev_0.8.2-1_amd64.deb 5daae3e098eea54fd7237a8c042258640bc19d440bbde09eed619b460cfe8e2c 122608 libcompizconfig0_0.8.2-1_amd64.deb Files: f0ab5642b8b4c99859cd2cd4e3a5a043 1235 libs extra libcompizconfig_0.8.2-1.dsc 93c932d3d0cf21c1f38c4a48e5561f59 70213 libs extra libcompizconfig_0.8.2.orig.tar.gz 73454fde7e097097d33fe1e1b8f93b42 3454 libs extra libcompizconfig_0.8.2-1.diff.gz 5364391d5e389bae7a99d7a864c34f11 134610 libdevel extra libcompizconfig-dev_0.8.2-1_amd64.deb eac5a1778852093708054908979db1a4 122608 libs extra libcompizconfig0_0.8.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFJ2xOyynjLPm522B0RAsZFAJ0awTIkE48j/rZYmR57DHfsm2BrdgCeMa3t LXlfP41eBnuV4ErSaXkpvAo= =H6CI -END PGP SIGNATURE- Accepted: libcompizconfig-dev_0.8.2-1_amd64.deb to pool/main/libc/libcompizconfig/libcompizconfig-dev_0.8.2-1_amd64.deb libcompizconfig0_0.8.2-1_amd64.deb to pool/main/libc/libcompizconfig/libcompizconfig0_0.8.2-1_amd64.deb libcompizconfig_0.8.2-1.diff.gz to pool/main/libc/libcompizconfig/libcompizconfig_0.8.2-1.diff.gz libcompizconfig_0.8.2-1.dsc to pool/main/libc/libcompizconfig/libcompizconfig_0.8.2-1.dsc libcompizconfig_0.8.2.orig.tar.gz to pool/main/libc/libcompizconfig/libcompizconfig_0.8.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
