Re: About new source formats for packages without patches
Hi! On Fri, 2010-03-26 at 09:25:38 +0100, Raphael Hertzog wrote: On Fri, 26 Mar 2010, Neil Williams wrote: Now all I need is for dpkg to accept that the absence of debian/source/format is declarative of source format 1.0. That's the case _for now_. packages don't need to be changed merely to state the obvious. They need because the dpkg maintainers have decided that it might not be the case indefinitely. Few things first. I don't think we should “ever” remove extraction support for older formats (be it source or binary), we should be able to easily analyze older content. We might want to remove creation support for older formats at some point in the *distant* future, though. And I don't really see any problem with that, we routinely remove support for deprecated stuff all over the place in Debian, given proper transition periods. I understand Raphaël's eagerness to see a fast switch, given his investment on the new formats, and as I obviously consider them a big improvement too. But I don't think it's appropriate to rush it, when we are just at the beginning of being able to use newer source formats, when there's still things being polished on them, for easier use, for different workflows, etc; when higher level tools support is still immature. It has neither seemed appropriate some of the excessively combative, aggressive and personal comments recently seen, when I think there's been will to accommodate for changes to the formats and tools. So, even if the uptake seems pretty fast, I agree it's still too soon to even show warnings. Once (and if) the archive has switched a big proportion, then we can start warning that the format needs to be explicit (lintian mostly, dpkg-source's current warning is not really visible anyway so I think it's fine to leave it there). And only when a tiny fraction is still using 1.0, and only then, we can _consider_, after appropriate debate, a possible plan for a removal of source format 1.0 creation. regards, guillem -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519062140.ga19...@gaara.hadrons.org
Re: SRWare Iron: Chromium without the data-mining
On Wed, May 19, 2010 at 2:39 AM, Ryan Oram r...@infinityos.net wrote: From the Ubuntu mailing list, in case of you aren't subscribed there: On Tue, May 18, 2010 at 8:27 PM, Dane Mutters dmutt...@gmail.com wrote: I think some of you would be interested in reading this page that (allegedly) documents some of the (allegedly) somewhat shady beginnings of Iron: http://neugierig.org/software/chromium/notes/2009/12/iron.html If this information is correct, then I heavily question that Iron is a worthwhile project/fork at all, as opposed to being a way to garner publicity and money from fear mongering and (amusingly enough) Google advertisements on their web page. --Dane I wasn't aware of this when I posted this thread on the mailing list. I still feel, however, the suggestion and DNS-prefetching features be made opt-in. Take it to upstream and let this thread end. And please don't crosspost the -devel lists of multiple Linux distributions. Cheers Arthur
Re: SRWare Iron: Chromium without the data-mining
On Wednesday 19 May 2010 02:39:00 Ryan Oram wrote: I wasn't aware of this when I posted this thread on the mailing list. I still feel, however, the suggestion and DNS-prefetching features be made opt-in. What do you mean by opt-in? I have searched and the only meaning i could find was about subscribing mailing lists. There are checkboxes for those in the configuration window. I haven't tried if they actually do something btw. Bye -- Salvo Tomaselli signature.asc Description: This is a digitally signed message part.
Re: SRWare Iron: Chromium without the data-mining
On Tue, May 18, 2010 at 08:39:00PM -0400, Ryan Oram wrote: From the Ubuntu mailing list, in case of you aren't subscribed there: On Tue, May 18, 2010 at 8:27 PM, Dane Mutters dmutt...@gmail.com wrote: I think some of you would be interested in reading this page that (allegedly) documents some of the (allegedly) somewhat shady beginnings of Iron: http://neugierig.org/software/chromium/notes/2009/12/iron.html If this information is correct, then I heavily question that Iron is a worthwhile project/fork at all, as opposed to being a way to garner publicity and money from fear mongering and (amusingly enough) Google advertisements on their web page. --Dane I wasn't aware of this when I posted this thread on the mailing list. I still feel, however, the suggestion and DNS-prefetching features be made opt-in. opt-in like in the Options dialog ? Show suggestions for navigation errors Use a suggestion service to help complete searches and URLs typed in the address bar Use DNS pre-fetching to improve load performance There is even a learn more link above all these that points to http://www.google.com/support/chrome/bin/answer.py?answer=114836hl=en Mike -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519071557.ga4...@glandium.org
Re: Re: Parallellizing the boot in Debian Squeeze - ready for wider testing
On Mon, May 17, 2010 at 03:06:10PM +0100, Scott James Remnant wrote:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543420#10
This pretty much proves my point. I was never sent these patches,
instead Debian kept them to itself and never attempted to get them
upstream.
Well, we can hardly argue the contrary in this specific case.
My personal impression is however that for that package, there is just a
lack of manpower: Michael has not replied to the bug report since
September and I know via personal communication that Martin is very busy
ATM, and generally looking for co-maintainers. So don't take this
personal (/ don't overgeneralize) and remember that you can follow what
happens with upstart in Debian by subscribing to the PTS for it. More
generally, I guess that the current maintainers would welcome some
additional helping hands *g*.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
Re: APT do not work with Squid as a proxy because of pipelining default
Petter Reinholdtsen p...@hungry.com writes: [Roger Lynn] But apt has been using pipelining for years. Why has this only just become a problem? It has been a problem in Debian Edu for years. Just recently I figured out the cause and a workaround. And FWIW I have experienced this problem for years too, but never figured out why until this discussion came up. And I do want to claim more than common user knowledge of http proxy servers. Still, it never occured to me that my spurious apt problems could be caused by proxies. And no, it's not just squid - I've been seeing the exact same at work where the office network have some intercepting proxy solution from websense. Anyway, this is definitely the type of problem that can and do exist for years without that necessarily causing a massive number of bug reports against apt. I still do not think that is an argument against fixing it? Can we please agree that in the real world 1) RFC1123 beats any other standard: Be liberal in what you accept, and conservative in what you send, and 2) http proxy servers cannot always process pipelined requests due to the complexity this adds (complexity is always bad for security), and 3) http clients cannot know whether their requests are proxied ? The sum of these three points is that a http client should never send pipelined requests. Bjørn -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87vdak5lkg@nemi.mork.no
Re: SRWare Iron: Chromium without the data-mining
]] Mike Hommey | opt-in like in the Options dialog ? «opt-in» usually means «requires active effort to be enabled», so in this case, disabled by default. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87hbm440s8@qurzaw.linpro.no
shutdown on power button?
I have noticed that the default configuration is to shutdown the computer when the power button is pressed. But on normal desktop installations, the DE will handle the event and take the appropriate actions. I also think that on non-desktop it should be the admin to decide whether if this behaviour is wanted (i have news of a server that went down because someone put a box near the power button and shortly pressed it with the box itself). So maybe this default should be reviewed? Bye -- Salvo Tomaselli signature.asc Description: This is a digitally signed message part.
Re: shutdown on power button?
On 2010-05-19, Salvo Tomaselli tipos...@tiscali.it wrote: So maybe this default should be reviewed? I doubt it's the default. You have to install acpid to get this behaviour, at least in VMs. Kind regards, Philipp Kern -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnhv7kg7.gg0.tr...@kelgar.0x539.de
Re: shutdown on power button?
On Wednesday 19 May 2010 13:56:55 Philipp Kern wrote: I doubt it's the default. You have to install acpid to get this behaviour, at least in VMs. It is, i just turned off my laptop (installed in march) for mistake, and i dindn't install manually acpid. Bye -- Salvo Tomaselli signature.asc Description: This is a digitally signed message part.
Re: APT do not work with Squid as a proxy because of pipelining default
On Wed, May 19, 2010 at 10:42:55AM +0200, Bjørn Mork wrote: 2) http proxy servers cannot always process pipelined requests due to the complexity this adds (complexity is always bad for security), and This is bullshit. It's *VERY* easy to support pipelining: parse one request at a time, and until you're done with a given request, you just stop to watch the socket/file-descriptor for reading (IOW you let the consecutive request live in the kernel buffers). Such an implementation of course doesn't benefit from the pipelining wins, but it works just fine. In addition to that, multiplying the tcp connections means more file descriptors to be used at the http-server side, which is way inferior to pipelining. If squid fails when apt uses pipelining then squid is to be fixed. I'd say that mentioning in the README.Debian of apt that disabling the pipelining may help is fine, but disabling it by default is wrong. Pipelining is defined in the RFC since the nineties ffs... -- ·O· Pierre Habouzit ··Omadco...@debian.org OOOhttp://www.madism.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519124134.gc20...@madism.org
Re: APT do not work with Squid as a proxy because of pipelining default
Pierre Habouzit madco...@madism.org writes: On Wed, May 19, 2010 at 10:42:55AM +0200, Bjørn Mork wrote: 2) http proxy servers cannot always process pipelined requests due to the complexity this adds (complexity is always bad for security), and This is bullshit. It's *VERY* easy to support pipelining: parse one request at a time, and until you're done with a given request, you just stop to watch the socket/file-descriptor for reading (IOW you let the consecutive request live in the kernel buffers). Yeah, you make it sound easy. I'm sure those writing proxy servers are just stupid. Bjørn -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87r5l83tsv@nemi.mork.no
Re: shutdown on power button?
On Wed, May 19, 2010 at 01:23:05PM +0200, Salvo Tomaselli wrote: I have noticed that the default configuration is to shutdown the computer when the power button is pressed. You might want to check which software did react on the button. But on normal desktop installations, the DE will handle the event and take the appropriate actions. Right, if you do not have a DE running, one way to react on the power button is using acpid *and* acpi-support-base. I also think that on non-desktop it should be the admin to decide whether if this behaviour is wanted (i have news of a server that went down because someone put a box near the power button and shortly pressed it with the box itself). So what do you propose? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519131908.ga3...@hyperion.credativ.de
Re: snapshot.debian.org implications for you
On 18/05/10 04:13, Raphael Hertzog wrote: On Tue, 18 May 2010, Peter Palfrader wrote: On Wed, 12 May 2010, Felipe Sateler wrote: Would it be feasible to have some sort of automation surrounding this? Breaches that are fixed by a subsequent upload will very likely contain some strings in the changelog: strip, distributable, dfsg-free or non-free. Also, a significant part of the breaches would have to be fixed by a repacked tarball. Thus, detecting changes in the version string (adding dfsg or repack) would give a good pointer on packages that need to go from snapshot.debian.org. Maybe. Hard to tell. Do you want to try it? Unfortunately, I do not have time these days, so I can't commit myself to it. Most of the repackaging is done because we don't _want_ to redistribute those files not because we do not have the right to redistribute them. [citation needed] My perception of the matter is the other way around. The check would be mostly useless IMO. We can't really know until it has been tried. -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ht0pfd$69...@dough.gmane.org
Re: snapshot.debian.org implications for you
On Wed, 19 May 2010, Felipe Sateler wrote: Most of the repackaging is done because we don't _want_ to redistribute those files not because we do not have the right to redistribute them. [citation needed] My perception of the matter is the other way around. Take the case of stripped RFC, we can't modify them, hence they are non-free for us and we don't want to carry them. But they are distributable and having them on snapshot.d.o hurts nobody. The same goes for any other non-free material that upstream includes on purpose (as opposed to by mistake). Say a PDF documentation or a logo or even a GFDL doc with invariants. Cheers, -- Raphaël Hertzog Like what I do? Sponsor me: http://ouaza.com/wp/2010/01/05/5-years-of-freexian/ My Debian goals: http://ouaza.com/wp/2010/01/09/debian-related-goals-for-2010/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519140834.gb16...@rivendell
Re: shutdown on power button?
On Wednesday 19 May 2010 15:19:08 Michael Meskes wrote: On Wed, May 19, 2010 at 01:23:05PM +0200, Salvo Tomaselli wrote: I have noticed that the default configuration is to shutdown the computer when the power button is pressed. You might want to check which software did react on the button. /etc/acpi/powerbtn-acpi-support.sh Right, if you do not have a DE running, one way to react on the power button is using acpid *and* acpi-support-base. But if i have it (and most of the time this is the case) it's just very annoying having configured kde to lock the screen and then seeing the screen being locked and then the computer being turned off. So what do you propose? Do not react to it. Also consider that acpid was not installed manually on my system, but much likely suggested by some other package, so i was kind of unaware of its presence. Bye -- Salvo Tomaselli signature.asc Description: This is a digitally signed message part.
Re: shutdown on power button?
On 19 May 2010 14:10, Salvo Tomaselli tipos...@tiscali.it wrote: It is, i just turned off my laptop (installed in march) for mistake, and i dindn't install manually acpid. It's not acpid that shuts down the computer on power button, it's acpi-support-base (installed by default) If you pressed the power button of you laptop, and the laptop shut down (cleanly!), I don't think you can call this an unreasonable behaviour. On the contrary, changing the default could lead to thermal damage (people press the power button and put the computer in the backpack expecting it to be off in a few seconds). There has been already quite a discussion in Debian about this matter (see e.g #444676); I don't think starting it all over again is a sensible thing to do. Cheers, Luca -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikubsrti3xh6sqyxbqzx7c62u60fe3feaqez...@mail.gmail.com
Re: shutdown on power button?
On 19 May 2010 16:10, Salvo Tomaselli tipos...@tiscali.it wrote: Right, if you do not have a DE running, one way to react on the power button is using acpid *and* acpi-support-base. But if i have it (and most of the time this is the case) it's just very annoying having configured kde to lock the screen and then seeing the screen being locked and then the computer being turned off. Mmm, you are saying that you are running KDE, with the KDE power manager; that you have configured KDE not to switch the computer off on power button; and that nonetheless the computer goes off when you press it? This would be definitely a bug, not intended behaviour. Cheers, Luca -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktiktwr9ljiqksbg3imw0mgctqobt7huznyqza...@mail.gmail.com
Re: [Debian-eeepc-devel] Ethernet not working on 1005HA
On 19 May 2010 16:09, Abhishek Dasgupta abh...@gmail.com wrote: Just upgraded to the latest bits from squeeze, and ethernet is not working here. Tried modprobing atl1c but that did not change anything. Ethernet was working before the upgrade. Anyone else has this problem? See bug #573607 The kernel fixing the problem has been uploaded to sid, but has not migrated yet (and it won't soon); I guess you could cherry-pick it from unstable or get back to the older one. Cheers, Luca -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktilmzt1hgzusdy9a6nnpypq7fj7bmfz7kya1x...@mail.gmail.com
Re: shutdown on power button?
On Wednesday 19 May 2010 16:14:41 Luca Niccoli wrote: I don't think you can call this an unreasonable behaviour. But as every good luser i opened powerdevil and set it to lock the screen, so for me it was totally unreasonable since it did something else than what i had manually configured to do. Then i reminded that i had it installed again recently and that i forgot to disable it from the script. Bye -- Salvo Tomaselli signature.asc Description: This is a digitally signed message part.
Re: shutdown on power button?
On Wednesday 19 May 2010 16:17:49 Luca Niccoli wrote: Mmm, you are saying that you are running KDE, with the KDE power manager; that you have configured KDE not to switch the computer off on power button; and that nonetheless the computer goes off when you press it? That is exactly what i am saying. This would be definitely a bug, not intended behaviour. Not kde's but i would say. Bye -- Salvo Tomaselli signature.asc Description: This is a digitally signed message part.
Re: shutdown on power button?
On 19 May 2010 16:30, Salvo Tomaselli tipos...@tiscali.it wrote: But as every good luser i opened powerdevil and set it to lock the screen, so for me it was totally unreasonable since it did something else than what i had manually configured to do. Then it's a bug in acpi-support-base, since the powerbtn script is supposed to exit without action if power devil is running. File it to the BTS please. Cheers, Luca -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktilqzjawamqyrnzeofmexlg_fjy2d_hupbex1...@mail.gmail.com
Re: shutdown on power button?
On 19 May 2010 16:38, Luca Niccoli lultimou...@gmail.com wrote: File it to the BTS please. Hint: since you already found out that the culprit was /etc/acpi/powerbtn-acpi-support.sh, running $reportbug /etc/acpi/powerbtn-acpi-support.sh would have automatically filed a bug against the package that owns it. In general, even if you don't know which package is responsible, it's better to file a bug against a possible one and then let the maintainer reassign it than write on debian-devel, that it's not meant for bug reporting. Cheers, Luca -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktiljtnce-iwvyzd2lvyp_gn7crjyecyxvyqht...@mail.gmail.com
Re: shutdown on power button?
On Wednesday 19 May 2010 16:42:12 Luca Niccoli wrote: that it's not meant for bug reporting. I actually thought it was the intended behaviour... Bye -- Salvo Tomaselli signature.asc Description: This is a digitally signed message part.
How to set ulimit (nofile) for a daemon
Hi, HBase needs a high nofile limit. What would be the preferred way to set the limit for the HBase daemons? Just call ulimit in the initscript? The java process is started by daemon (Debian package daemon). Thank you, Thomas Koch, http://www.koch.ro -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201005191746.54540.tho...@koch.ro
Re: APT do not work with Squid as a proxy because of pipelining default
Robert Collins robe...@robertcollins.net writes: Well, I don't know why something has 'suddenly' become a problem: its a known issue for years. The HTTP smuggling [http://www.watchfire.com/resources/HTTP-Request-Smuggling.pdf] attacks made that very obvious 5 years ago now. Reading that I don't think that is really a pipelining issue. You do not need pipelineing for it to work. The real problem is keep-alive. The connection isn't destroyed after each request so you can put multiple requests into the stream and exploit different brokenness in different parsers along the way. Take the first example from the pdf [http://www.cgisecurity.com/lib/HTTP-Request-Smuggling.pdf for non-stale link]: You send the first request to the proxy which it passes along: POST http://SITE/foobar.html HTTP/1.1 Host: SITE Connection: Keep-Alive Connection-Type: application/x-www-from-urlencoded Content-Length: 0 Content-Length: 44 [CRLF] GET /poison.html HTTP/1.1 Host: SITE Bla: [space after the Bla:, but no CRLF] As the paper says the SunONE Proxy uses the second Content-Length entry while SunONE W/S uses the first. So server replies with foobar.html and after it is done it starts reading the second request starting at GET and stalls because the request is incomplete. Then you send the second request to the proxy: GET http://SITE/page_to_poison.html HTTP/1.1 Host: SITE Connection: Keep-Alive [CRLF] And the server responds with poison.html while the proxy caches that under page_to_poison.html. Note that I did not pipeline the requests to the proxy. And still I managed to poison it. I also didn't need the server to pipeline responces, only to not fail if multiple requests are send without waiting for the first to complete. Something that is required for HTTP/1.1 conformance. Pipelining just makes more of those attacks possible, those where the first parser sees multiple requests while the second sees only one. http://en.wikipedia.org/wiki/HTTP_pipelining has a decent overview. That nicely shows how much better pipelining is for the performance. Its nice an interesting that some recent software has it on, but that is generally because the authors don't realise how broken it is, IMNSHO :). -Rob I think you have failed to show that pipelining is broken. What seems broken is Keep-Alive. Do you suggest we stop using Keep-Alive to prevent broken parsers from being exploited? Make a full 3-way handshake for every request? MfG Goswin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8739xnvpj2@frosties.localdomain
Re: APT do not work with Squid as a proxy because of pipelining default
On 2010-05-19, Goswin von Brederlow goswin-...@web.de wrote: Reading that I don't think that is really a pipelining issue. You do not need pipelineing for it to work. The real problem is keep-alive. The connection isn't destroyed after each request so you can put multiple requests into the stream and exploit different brokenness in different parsers along the way. Those are bugs in the servers that allow that output, though. I think you have failed to show that pipelining is broken. What seems broken is Keep-Alive. Do you suggest we stop using Keep-Alive to prevent broken parsers from being exploited? Make a full 3-way handshake for every request? I think we would want keep-alive with a pipeline depth of 1 (i.e. send the new request after the old one was processed). I'd rather think that TCP slow start is a problem if you avoid keepalive than the full 3-way handshake (which is annoying too). Concurrent requests put an unreasonable load onto the mirrors, so we should avoid that. Kind regards, Philipp Kern -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnhv842i.j97.tr...@kelgar.0x539.de
Re: SRWare Iron: Chromium without the data-mining
I demand that Ryan Oram may or may not have written... http://www.srware.net/en/software_srware_iron_chrome_vs_iron.php This should become a full open source project with a community behind it. With Mozilla disregarding H.264, the community needs a full browser capable of H.264 video playback without the privacy issues of Chrome. xine-plugin, given any browser with NPAPI. [snip] -- | Darren Salt| linux at youmustbejoking | nr. Ashington, | Toon | using Debian GNU/Linux | or ds,demon,co,uk| Northumberland | back! | URL:http://www.youmustbejoking.demon.co.uk/ (PGP 2.6, GPG keys) Hello! I'm Bounder of Adventure! -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/511f5de218%li...@youmustbejoking.demon.co.uk
Re: APT do not work with Squid as a proxy because of pipelining default
Bjørn Mork bj...@mork.no writes: Petter Reinholdtsen p...@hungry.com writes: [Roger Lynn] But apt has been using pipelining for years. Why has this only just become a problem? It has been a problem in Debian Edu for years. Just recently I figured out the cause and a workaround. And FWIW I have experienced this problem for years too, but never figured out why until this discussion came up. And I do want to claim more than common user knowledge of http proxy servers. Still, it never occured to me that my spurious apt problems could be caused by proxies. And no, it's not just squid - I've been seeing the exact same at work where the office network have some intercepting proxy solution from websense. Anyway, this is definitely the type of problem that can and do exist for years without that necessarily causing a massive number of bug reports against apt. I still do not think that is an argument against fixing it? Can we please agree that in the real world 1) RFC1123 beats any other standard: Be liberal in what you accept, and conservative in what you send, and 2) http proxy servers cannot always process pipelined requests due to the complexity this adds (complexity is always bad for security), and 3) http clients cannot know whether their requests are proxied ? The sum of these three points is that a http client should never send pipelined requests. Wrong, at least from arguments 2 and 3. A HTTP/1.1 conforming server or proxy is free to process pipelined requests serially one by one. The only requirement is that it does not corrupt the second request by reading all available data into a buffer, parsing the first request and then throwing away the buffer and thereby discarding the subsequent requests in that buffer. It is perfectly fine for the server to parse the first request, think, respond to the first request and then continue to parse the second one. Note that that behaviour in the server already gives a huge speed increase. It cuts away the round trip time between the last responce and the next request. For static web content the speedup of processing pipelined requests truely in parallel is neglible anyway. Only dynamic pages, where formulating the responce to a request takes time, would benefit by working on multiple responces on multiple cores. And those are probably busy handling requests from other connections. So I wouldn't expect servers to actually to parallel processing of pipelined requests at all. And your argument 1 applies perfectly to fixing squid by the way. It should accept pipelined requests and then it can proces them one by one and send them non pipelined if it likes. It should NOT corrupt the requests/responces. So just from your argument 1 APT should default not to pipeline and squid should be fixed. MfG Goswin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87wruzuaca@frosties.localdomain
Re: APT do not work with Squid as a proxy because of pipelining default
Bjørn Mork bj...@mork.no writes: Pierre Habouzit madco...@madism.org writes: On Wed, May 19, 2010 at 10:42:55AM +0200, Bjørn Mork wrote: 2) http proxy servers cannot always process pipelined requests due to the complexity this adds (complexity is always bad for security), and This is bullshit. It's *VERY* easy to support pipelining: parse one request at a time, and until you're done with a given request, you just stop to watch the socket/file-descriptor for reading (IOW you let the consecutive request live in the kernel buffers). Or user space buffers. You would not want to parse the requests by using read(fd, buf, 1). Yeah, you make it sound easy. I'm sure those writing proxy servers are just stupid. Bjørn It is that easy. For a proxy call it de-pipeline-isation. In a proxy this behaviour would destroy the benefit of pipelining. But not the data. The hard part is writing the proxy so that it still pipelines the requests to the server. There you get the increased complexity for security and bandwith limiting. But that is not required for HTTP/1.1 conformance and an actually working setup. MfG Goswin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87r5l7ua12@frosties.localdomain
Re: SRWare Iron: Chromium without the data-mining
On Wed, May 19, 2010 at 3:15 AM, Mike Hommey m...@glandium.org wrote: opt-in like in the Options dialog ? Show suggestions for navigation errors Use a suggestion service to help complete searches and URLs typed in the address bar Use DNS pre-fetching to improve load performance There is even a learn more link above all these that points to http://www.google.com/support/chrome/bin/answer.py?answer=114836hl=en Mike Yes, I just feel those options should be unchecked by default. I have filled a bug upstream: http://code.google.com/p/chromium/issues/detail?id=44527 Thanks, Ryan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimbj1fcf1g5nn0z2d0hdhq4lyzqefuql1mak...@mail.gmail.com
Re: Parallellizing the boot in Debian Squeeze - ready for wider testing
On Sun, May 09, 2010 at 13:27:08 +0200, Marc Haber wrote: On Sat, 8 May 2010 11:47:40 +0200, Julien Cristau jcris...@debian.org wrote: As far as I'm concerned, faster boot is irrelevant. Using an init daemon that actually does its job of supervising services, and lets us get rid of most of the stupidity and boilerplate of init scripts, otoh, is overdue. What is so bad about init scripts? - no supervision - bloated, as every action need to be implemented in the script, and therefore slow and error prone - no adjustable user permissions - no clean evironment Just to mention some of the issues. I don't know if upstart solves all of them, though. Regards, Tino -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519170713.ga18...@mac.home
Re: UPG and the default umask
For the record: I've changed the umask setting in /etc/profile to this: if [ `id -u` -ge 1000 ]; then umask 002 else umask 022 fi which is fully consistent with Debian policy when it says that user accounts, by default, start at uid 1000. So, this is now a very simple rule (umask 002) with a very simple exception (not an user account), and I'm now confortable enough with it to not ask it to be moved elsewhere (PAM or login.defs). Some people proposed complex code to determine whether UPG was in use for system users. Such thing would be an exception to the exception and as such I think it would be a bad thing, as it would make things a lot more complex without any real gain. Thanks. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.1.10.1005191903510.17...@cantor.unex.es
Re: shutdown on power button?
On Wed, May 19, 2010 at 04:17:49PM +0200, Luca Niccoli wrote: This would be definitely a bug, not intended behaviour. I absolutely agree. This code is used to find out of powerdevil is running: for p in $(pidof kded4); do test -r /proc/$p/environ || continue local DBUS_SESS=$(cat /proc/$p/environ | grep -a -z DBUS_SESSION_BUS_ADDRESS=) test $DBUS_SESS != || continue (su - $(ps -o user= $p) -s /bin/sh -c $DBUS_SESS dbus-send --print-reply --dest=org.kde.kded /kded org.kde.kded.loadedModules | grep -q powerdevil) return 0 done Could you please try to debug this so we can find out why it didn't work for you? I know for sure that it used to work. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519173011.gc12...@hyperion.credativ.de
Re: UPG and the default umask
On 05/19/2010 11:25 AM, Santiago Vila wrote: For the record: I've changed the umask setting in /etc/profile to this: if [ `id -u` -ge 1000 ]; then umask 002 else umask 022 fi [snip] Some people proposed complex code to determine whether UPG was in use for system users. Such thing would be an exception to the exception and as such I think it would be a bad thing, as it would make things a lot more complex without any real gain. I suggested this, which I don't think is complex. However, what you have suggested should work just fine. if [ $(id -un) = $(id -gn) ] [ $UID -gt 99 ]; then umask 0002 else umask 0022 fi The logic is simple, IMO: if the group name and the user name match, it's UPG. If UPG and it is not a system user, then set the umask to 0002. Otherwise, set to 0022. I don't know if that logic will match any additional cases (unless user accounts are created under ID 1000), however, so we should be good with your simpler logic on just matching the UID. Speaking of which, because of NFS, should matching just the UID -ge 1000 a good idea? Other systems start their accounts at 500, and matching UID is critical in NFS environments. Just a thought. -- . O . O . O . . O O . . . O . . . O . O O O . O . O O . . O O O O . O . . O O O O . O O O signature.asc Description: OpenPGP digital signature
Re: UPG and the default umask
On 2010-05-19, Aaron Toponce aaron.topo...@gmail.com wrote: I suggested this, which I don't think is complex. However, what you have suggested should work just fine. if [ $(id -un) =3D $(id -gn) ] [ $UID -gt 99 ]; then umask 0002 else umask 0022 fi id -n might cause network accesses, if NSS is configured to do so. Is there a precedent in profile for this? (I don't see any, just id -u which calls getuid.) The logic is simple, IMO: if the group name and the user name match, it's UPG. If UPG and it is not a system user, then set the umask to 0002. Otherwise, set to 0022. When I do newgrp group it's still UPG and the umask should still be 2, no? This check would change my umask. I don't know if that logic will match any additional cases (unless user accounts are created under ID 1000), however, so we should be good with your simpler logic on just matching the UID. Right. Kind regards, Philipp Kern -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnhv8da1.kea.tr...@kelgar.0x539.de
Re: APT do not work with Squid as a proxy because of pipelining default
#include hallo.h * Robert Collins [Tue, May 18 2010, 02:02:59PM]: Given that pipelining is broken by design, that the HTTP WG has And if not? Counter example, it seems to work just fine with my apt-cacher-ng proxy, at least bug reports related to that have appeared for about a year now. increased the number of concurrent connections that are recommended, and removed the upper limit - no. I don't think that disabling pipelining hurts anyone - just use a couple more concurrent connections. And here I disagree. Dealing with a dozen connections instead of having the requests in the pipeline can require much more resources on the proxy side. Regards, Eduard. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519184903.ga3...@rotes76.wohnheim.uni-kl.de
Re: UPG and the default umask
On 05/19/2010 01:00 PM, Philipp Kern wrote: When I do newgrp group it's still UPG and the umask should still be 2, no? This check would change my umask. If the new default group is named something other than your username, it's no longe UPG. UPG is only if the user name and group name match, and the user is the only member of that group. So, to answer your question, if your username was foo and you belonged to group foo, of which you are the only member, then you do a newgrp bar for foo, foo is no longer in a UPG situation, so his umask should be 0022 at that point. -- . O . O . O . . O O . . . O . . . O . O O O . O . O O . . O O O O . O . . O O O O . O O O signature.asc Description: OpenPGP digital signature
Re: UPG and the default umask
On 19/05/10 18:25, Santiago Vila wrote: For the record: I've changed the umask setting in /etc/profile to this: if [ `id -u` -ge 1000 ]; then Should we also be catering for the reserved globally allocated UIDs in the range 6-64999 with this check (Policy §9.2.2)? Regards, Roger -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bf437f2.2090...@codelibre.net
Re: UPG and the default umask
On 2010-05-19, Aaron Toponce aaron.topo...@gmail.com wrote: On 05/19/2010 01:00 PM, Philipp Kern wrote: When I do newgrp group it's still UPG and the umask should still be= 2, no? This check would change my umask. If the new default group is named something other than your username, it's no longe UPG. UPG is only if the user name and group name match, and the user is the only member of that group. Sorry, I assumed that UPG is a system-wide concept and that I could just change to my collaboration group and have a useful umask there too. So we only cater for the setgid flag on directories? Kind regards, Philipp Kern -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnhv8efm.l1r.tr...@kelgar.0x539.de
Re: UPG and the default umask
On Wed, May 19, 2010 at 3:10 PM, Aaron Toponce aaron.topo...@gmail.com wrote: On 05/19/2010 01:00 PM, Philipp Kern wrote: When I do newgrp group it's still UPG and the umask should still be 2, no? This check would change my umask. If the new default group is named something other than your username, it's no longe UPG. UPG is only if the user name and group name match, and the user is the only member of that group. So, to answer your question, if your username was foo and you belonged to group foo, of which you are the only member, then you do a newgrp bar for foo, foo is no longer in a UPG situation, so his umask should be 0022 at that point. Except /etc/profile won't be sourced again unless newgrp - group is used, right? -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega james...@debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimillfzkvbwdk2ruzmldg88pjmjtvhskvuyl...@mail.gmail.com
Re: UPG and the default umask
On 05/19/2010 01:20 PM, Philipp Kern wrote: Sorry, I assumed that UPG is a system-wide concept and that I could just change to my collaboration group and have a useful umask there too. So we only cater for the setgid flag on directories? The newgrp command changes your default group. The default group is what is applied to files when you create them. So, if you change your default group to a collaborative group, then realize that they will have access to those files you create outside of the collaboration directory. The better way to approach this, would be to just append the collaborative group to the user, but keep his private group as his default group. -- . O . O . O . . O O . . . O . . . O . O O O . O . O O . . O O O O . O . . O O O O . O O O signature.asc Description: OpenPGP digital signature
Re: UPG and the default umask
On 05/19/2010 01:25 PM, James Vega wrote: Except /etc/profile won't be sourced again unless newgrp - group is used, right? Correct, or the user issues a new login shell after the change has been made. -- . O . O . O . . O O . . . O . . . O . O O O . O . O O . . O O O O . O . . O O O O . O O O signature.asc Description: OpenPGP digital signature
Re: APT do not work with Squid as a proxy because of pipelining default
Goswin von Brederlow goswin-...@web.de writes: A HTTP/1.1 conforming server or proxy This is not the real world... is free to process pipelined requests serially one by one. The only requirement is that it does not corrupt the second request by reading all available data into a buffer, parsing the first request and then throwing away the buffer and thereby discarding the subsequent requests in that buffer. It is perfectly fine for the server to parse the first request, think, respond to the first request and then continue to parse the second one. Yes, this can be done. But you should ask yourself what proxies are used for. The serializing strategy will work, but it will make the connection slower with a proxy than without. That's not going to sell many proxy servers. Note that that behaviour in the server already gives a huge speed increase. It cuts away the round trip time between the last responce and the next request. For static web content the speedup of processing pipelined requests truely in parallel is neglible anyway. Only dynamic pages, where formulating the responce to a request takes time, would benefit by working on multiple responces on multiple cores. And those are probably busy handling requests from other connections. So I wouldn't expect servers to actually to parallel processing of pipelined requests at all. This is true for a web server. It is only true for a proxy server if it can either forward a pipelined request or parallelize it. That's where we get the complexity. If you keep your simple serial strategy, then a pipelined request will be slower than a parallel one. And your argument 1 applies perfectly to fixing squid by the way. It should accept pipelined requests and then it can proces them one by one and send them non pipelined if it likes. It should NOT corrupt the requests/responces. Sure. Squid should be fixed. But I'm afraid fixing squid in Debian won't fix all the http proxies around the world. So just from your argument 1 APT should default not to pipeline and squid should be fixed. Good. Bjørn -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87wruz1xn7@nemi.mork.no
Re: UPG and the default umask
Hi! Some people proposed complex code to determine whether UPG was in use for system users. Such thing would be an exception to the exception and as such I think it would be a bad thing, as it would make things a lot more complex without any real gain. The gain would be a guard against accidental 002 umasks in non-UPG environments, which I'm quite sure will happen. Either because admins do not read the release notes or because they forget to do the change on one of their newly-installed machines despite reading the release notes. On the other hand, other distributions already use default 002 umask unconditionally and I'm not aware of any complaints. So admins in non-UPG environments using these distros seem to be able to cope with it. However, there might be stronger expectations about Debian's default security-related settings, which might explain the harsh wordings chosen by some opponents of this change. WM -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ht1j0f$m8...@dough.gmane.org
Re: UPG and the default umask
On Wed, 19 May 2010 22:51:25 +0200, Willi Mann foss...@wm1.at wrote: The gain would be a guard against accidental 002 umasks in non-UPG environments, which I'm quite sure will happen. Either because admins do not read the release notes or because they forget to do the change on one of their newly-installed machines despite reading the release notes. I also think, that the current check is far to less... Nevertheless may I suggest to stop any further active changes in that issue (UPG/umask) until this discussion here is over and final decision has been made. Or is that already, the case? At least I've had the impression that neither mine, nor the arguments of some other people (Harald, Peter, etc.) were even answered here. On the other hand, other distributions already use default 002 umask unconditionally and I'm not aware of any complaints. So admins in non-UPG environments using these distros seem to be able to cope with it. The reason could be that people simply don't recognise, that they might have compromised their own security... and those who know what happens don't complain. However, there might be stronger expectations about Debian's default security-related settings, Well... I guess you can forget about that. which might explain the harsh wordings chosen by some opponents of this change. Funny that you notice it I was (off list) mailed by some people and harshly insulted with words I better don't repeat here,... and not even for technical reasons, as stated, but just because I don't bow to what is considered the majority. And from all of us here: I wish you happy painting, Chris. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/39a6ceb8f92bb5718dc558d118c57...@imap.dd24.net
Bug#582308: ITP: mango-lassi -- Share mouse and pointer with other computers
Package: wnpp Severity: wishlist Owner: Kartik Mistry kar...@debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * Package name: mango-lassi Version : 001 Upstream Author : Lennart Poettering mz...@0pointer.net, Sven Herzberg * URL : http://github.com/herzi/mango-lassi/ * License : GPL-2+ Programming Lang: C Description : Share mouse and pointer with other computers Mango-lassi lets you to share mouse and pointer with other computers using Avahi. It has features like: * Fully peer-to-peer. All Mango Lassi instances are both client and server at the same time. Other hosts may enter or leave a running session at any time. * No need to open X11 up for the network * You have a 50% chance that for your setup you don't need any configuration at all. In the case of the other 50% you might need to swap the order of your screens manually in a simple dialog, because Mango Lassi didn't guess correctly which screen is left and which screen is right. * libnotify integration so that it tells you whenever a desktop joins or leaves your session. * Shows a nice OSD on your screen when your screen's input is currently being redirected to another screen. * Uses all those nifty GNOME APIs, like D-Bus-over-TCP, Avahi, libnotify, Gtk,.. * Supports both the X11 clipboard and the selection, supporting all content types, and not just simple text -- i.e. you can copy and paste image data between Gimp on your screens. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkv0U6cACgkQoRg/jtECjI0tnQCgnxkkiXX9za0pxk/zU92f1/kM x2wAn0oo8mpcuqg84eBArGDavVqP7zPM =BOgx -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519211016.31532.21460.report...@localhost
Re: UPG and the default umask
btw: What happened to the idea of movin umask completely away from /etc/profile? I mean regardless of the discussion about UPGs and which value is the best default for umask, I found it to be a good idea to drop it there. Can someone please explain me the reason why login.defs isn't used for that? Cheers, Chris. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/08ab89016e3f8352697e1a4700582...@imap.dd24.net
Re: UPG and the default umask
On 05/19/2010 03:11 PM, Christoph Anton Mitterer wrote: Or is that already, the case? At least I've had the impression that neither mine, nor the arguments of some other people (Harald, Peter, etc.) were even answered here. You've only mentioned that SSH won't operate if the write bit is set on the keys or anything under the ~/.ssh/ directory. Can you explain how an ssh client failing to connect to an external ssh server because of the umask is compromising security on the system? Also, can you please provide an extra carriage return between your reply and the quoted text? Reading your replies is a bit annoying. The reason could be that people simply don't recognise, that they might have compromised their own security... and those who know what happens don't complain. Please explain how people's security is compromised because their umask is 0002 instead of 0022. I'm still waiting for this FUD to be backed up. -- . O . O . O . . O O . . . O . . . O . O O O . O . O O . . O O O O . O . . O O O O . O O O signature.asc Description: OpenPGP digital signature
Bug#582315: ITP: pyrit-cuda -- NVIDIA CUDA support for Pyrit
Package: wnpp Severity: wishlist Owner: Christian Kastner deb...@kvr.at * Package name: pyrit-cuda Version : 0.3.0 Upstream Author : Lukas Lueg lukas.l...@gmail.com * URL : http://code.google.com/p/pyrit/ * License : GPLv3 + linking exceptions for OpenSSL and CUDA Programming Lang: C, Python Description : NVIDIA CUDA support for Pyrit This package provides a python extension for Pyrit, enabling support for NVIDIA CUDA. It is being distributed separately because of its dependency on non-free software. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519214014.2819.74126.report...@sid64.sbx
Re: UPG and the default umask
On Wed, 19 May 2010 15:22:04 -0600, Aaron Toponce aaron.topo...@gmail.com wrote: You've only mentioned that SSH won't operate if the write bit is set on the keys or anything under the ~/.ssh/ directory. Can you explain how an ssh client failing to connect to an external ssh server because of the umask is compromising security on the system? Simply read the mails and those from the other critics again, it's not only annoying for myself to repeat things over and over again but also for everybody else to read it again. Nevertheless just saying everything's fine or you only complained about ssh won't really solve the issues, but just help to wave these changes through. Also, can you please provide an extra carriage return between your reply and the quoted text? Reading your replies is a bit annoying. Any other wishes to please your MUA? Different character encoding? MIME? Please explain how people's security is compromised because their umask is 0002 instead of 0022. I'm still waiting for this FUD to be backed up. See above, or do you wish a larger paper discussing the issues?! ^^ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7f276af2e79987201aa98eaecb317...@imap.dd24.net
Re: snapshot.debian.org implications for you
On 19/05/10 10:08, Raphael Hertzog wrote: On Wed, 19 May 2010, Felipe Sateler wrote: Most of the repackaging is done because we don't _want_ to redistribute those files not because we do not have the right to redistribute them. [citation needed] My perception of the matter is the other way around. Take the case of stripped RFC, we can't modify them, hence they are non-free for us and we don't want to carry them. But they are distributable and having them on snapshot.d.o hurts nobody. The same goes for any other non-free material that upstream includes on purpose (as opposed to by mistake). Say a PDF documentation or a logo or even a GFDL doc with invariants. I was under the impression that snapshots.debian.org main had to respect the same rules as ftp.debian.org main. If that is true, you cannot then leave RFCs or other non-free material there. If not, then you are probably right. -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ht1nod$94...@dough.gmane.org
Re: How to set ulimit (nofile) for a daemon
On 19/05/10 11:46, Thomas Koch wrote: Hi, HBase needs a high nofile limit. What would be the preferred way to set the limit for the HBase daemons? Just call ulimit in the initscript? The java process is started by daemon (Debian package daemon). Thank you, Thomas Koch, http://www.koch.ro Create an exclusive user for your daemon, and drop a file in /etc/security/limits.d with the following contents: daemonuser - nofile somenumber You should probably ask via debconf before doing it, though. - Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ht1o7k$en...@dough.gmane.org
Re: UPG and the default umask
On Wed, 19 May 2010, Roger Leigh wrote: On 19/05/10 18:25, Santiago Vila wrote: For the record: I've changed the umask setting in /etc/profile to this: if [ `id -u` -ge 1000 ]; then Should we also be catering for the reserved globally allocated UIDs in the range 6-64999 with this check (Policy §9.2.2)? Hmm, good question. Can you give me an example of an uid which has been allocated that way? Perhaps I should follow policy more closely, yes, but that would mean using the range 1000-2 only, not 1000-5, as 3-5 is reserved (whatever that means). If an admin which runs out of UIDs in his system modifies /etc/adduser.conf, will he remember to modify the upper bound in /etc/profile as well? -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.deb.1.10.100526430.8...@kolmogorov.unex.es
Re: UPG and the default umask
On Wed, May 19, 2010 at 09:11:54PM +, Christoph Anton Mitterer wrote:
Nevertheless may I suggest to stop any further active changes in that
issue (UPG/umask) until this discussion here is over and final
decision has been made.
Sorry, but Debian is a do-ocracy first, and a democracy then. AFAICT you
do not maintain any of the involved packages, so thus far your best
attempt has been to convince the maintainer of your ideas, which is a
reasonable course of action.
As of now, you've posted 30 messages in 4 days, arguably often repeating
the same arguments; apparently, you did not manage to convince the
maintainer to change his decision. If I were at your place, I would have
realized by now that continuing along this pattern won't achieve much
more.
Now, I'm deeply sorry you got insults in private mail, that's surely not
appropriate.
In spite of that, from here you have the following choices: (1) engage
the democracy part of Debian in an attempt to overrule the maintainer
decision (note that you would need some DDs to support that course of
action), (2) give up (possibly changing your distribution of choice due
to this change, which would make me sad), (3) continue your previous
pattern.
Among these choices, I gently ask you not to pursue the latter.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
Re: How to set ulimit (nofile) for a daemon
On Wed, May 19, 2010 at 06:20:35PM -0400, Felipe Sateler wrote: HBase needs a high nofile limit. What would be the preferred way to set the limit for the HBase daemons? Just call ulimit in the initscript? The java process is started by daemon (Debian package daemon). Thank you, Thomas Koch, http://www.koch.ro Create an exclusive user for your daemon, and drop a file in /etc/security/limits.d with the following contents: daemonuser - nofile somenumber This is the wrong answer to the question how do I set ulimits for a daemon process? /etc/security/limits.d is only processed by pam_limits, which has no reason to be in the path for service startup. You should probably ask via debconf before doing it, though. No, you shouldn't do that either. -- 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 signature.asc Description: Digital signature
Re: APT do not work with Squid as a proxy because of pipelining default
Hi all, i don't want to interrupt your battles so feel free to ignore me, but i want to raise some questions (for you and me) none the less: The notice about the - in the eyes of the writer of this manpage section - broken squid version 2.0.2 in the apt.conf manpage was changed the last time in 2004, so the issue isn't new. The manpage at least claims that this squid version is broken also in respect to other cache control settings. I don't know a single bit about squid but a search for squid pipeline turns up some documentation about a pipeline_prefetch setting: Available in: 3.12.73.HEAD2.HEAD3.02.6 To boost the performance of pipelined requests to closer match that of a non-proxied environment Squid can try to fetch up to two requests in parallel from a pipeline. http://www.squid-cache.org/Doc/config/pipeline_prefetch/ For somebody without knowledge this looks like as any version in debian should be able to handle a pipeline - otherwise this setting wouldn't make much sense… The default value for the APT option above is btw 10 and in apt #413324 we have a claim that squid works well with a value of 5 or even 8 -- so it is maybe just a bug in handling too much pipelined requests? Or something comparable to what happened in #541428 regarding lighttpd and pipelining (timeout)? (i am just shooting into the dark) Also, then we talk here about pipelines and her usage keep in mind that APTs http usage is special compared to an implementation and usage in a browser: We have a trust chain available so we should be on the save side security wise, the number of debian archives is limited and most of them should be on a sane webserver (if not i would not have much trust in the archive…) and especially on apt-get update we have either a lot of cache hits (file has not changed) or a lot of very small files (Release, Index and maybe pdiff) to transfer. New package updates come from the same archive most of time and most packages are relatively small, too, but having an upgrade including at least 500 packages is relatively common… On the other hand APTs http client isn't as nice as he could be in terms that he could fallback to non-pipeline, retry or whatever. (and i wouldn't be too surprised if this would turn out to be an APT bug) As we all know APT is a debian native tool and the base of a whole bunch of other stuff so beside ranting about his shortcomings we could also work on patches as the people with enough knowledge to do this seems to be already around in this thread. Thanks in advance and best regards, David Kalnischkies P.S. Sry Luigi Gangitano for cc'ing, but i don't know if you follow the thread and i included too often squid in the mail to not direct the mail into your direction. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinq0j1fd78p200qihsq5ctv3qmbwd8srxgje...@mail.gmail.com
Re: How to set ulimit (nofile) for a daemon
On 19/05/10 18:32, Steve Langasek wrote: On Wed, May 19, 2010 at 06:20:35PM -0400, Felipe Sateler wrote: HBase needs a high nofile limit. What would be the preferred way to set the limit for the HBase daemons? Just call ulimit in the initscript? The java process is started by daemon (Debian package daemon). Thank you, Thomas Koch, http://www.koch.ro Create an exclusive user for your daemon, and drop a file in /etc/security/limits.d with the following contents: daemonuser - nofilesomenumber This is the wrong answer to the question how do I set ulimits for a daemon process? /etc/security/limits.d is only processed by pam_limits, which has no reason to be in the path for service startup. cron, atd and schroot load pam_limits. Is that wrong? Or something else I'm not getting? -- Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ht1q1e$k0...@dough.gmane.org
Re: How to set ulimit (nofile) for a daemon
On Wed, May 19, 2010 at 06:51:25PM -0400, Felipe Sateler wrote: This is the wrong answer to the question how do I set ulimits for a daemon process? /etc/security/limits.d is only processed by pam_limits, which has no reason to be in the path for service startup. cron, atd and schroot load pam_limits. Is that wrong? Or something else I'm not getting? These daemons load pam_limits *when running on behalf of other users*. That's an entirely different scenario than running a daemon per se. -- 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 signature.asc Description: Digital signature
Bug#582321: TAG: dirsum -- commandline directory summary
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: itp Severity: wishlist Version: 0.4; * Package name : dirsum Version : 0.4 Upstream Author : Dirk Bartley bartle...@chartermi.net * URL: http://code.dyne.org/?r=dirsum * License: GNU GPL Description: Dirsum is a command line tool to assist sorting out which directories in a filesystem contain the most bytes. It will sort all of the subdirectories of a selected path according to the total bytes of all files in them, including recursion through further subdirectories and mounted partitions. - -- jaromil, dyne.org developer, http://jaromil.dyne.org GPG: B2D9 9376 BFB2 60B7 601F 5B62 F6D3 FBD9 C2B6 8E39 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQQcBAEBCAAGBQJL9GfkAAoJEAslGzkIl3JRUzEgAKOpEnZGKvwoK09wrQPBaN3x 0/XzQp9KSStqom6Vy8bw3fS1qWpUCPGN+EsJH37CD4ptlz6aoApY1I00a8rjX5Qi AbA4WcDrl0P2Y+hkw9yT+9heJcAMaPfS+ViU5xNbt1h8+Jb2cMoMNBapDwB33ZYA f1jsSiMUTdZxvn+00OJwyqyh5iCqTJwQlo0F9EINt6zQUzsKLUGJ/4nVsQbWxA/x oi/84xPNoFW/CB5Y2VkLdv8UaRhoXf9kgjh2rM5Fe0LDALoMVcByuOOz/78HIfI1 ibg7rSeOAnSkQaNLRqFW2tIN4R9DxQ4ryiYeWeQfTGz1TALcm3ywwgbhVPVOii2Y KaHfjhaEu2c4z+gwnKbDuj4DOaYKvPVuTbn+jICy9fVH/5NA2Sa5WwwFnARX56PC sxqGAYHaXtJFHDMQtCBsZywTxkjkBOIF/gEkJU1MXXa6hSA9DG4QglQhK+T3sQZr 7dcD1x8owDqceqoRLg0lm7hzuQ3EBUlbNO+E54wNBkyT9WMSiXekuKAgsQn9v/Ut 6h/AWjX6RiQS0oiIXINEBsUDrA7/dlLUpUO+5vR4/4K33AbnKy8N8spDPpwE/WDH Nh8IXC6qz6jUfzYJneDgfjFUxnpUhO4UKAtlAutVVJumdPmKTQ9MAXFuNATGIbBi Qqq2N3rQtJ6PdNqRS+IGS0nXse2QCiao2HBILc6GuSUwdIQDGQ5ivCNSpu4X3Sjh dsm889Wa14jFyoXUjSqKDWlxs7aEDjGmVESDmq3rB5Ix87z+lnrkrIhLf7qvF7K5 Bmedou6Oon4zIMgvrjrB2Nh3UJID2Aj7NOCm05csOKwFYpluRDrOA6OxQUbO2zGC /7TbCV/qPH28XjpavM0f4RFVRwJsHEIA7WhSfUYXXub8lSyovgBAvRJWhdRcSYnU nVKW1p7HImGvvReLIp1JjktceV2+C/nQq/LsvyUPoLgdIgHJH+GKG/drMZdK6tmg ffeb+6f6YtMLEMyh+xRwfFP760mLKOAQM/g2atuIPn02yvzr2RVX8RIsmpv8enz2 r3jVVd/UHzwOJQjhS9AosPgrTgqDz2Xle735ZtH1FpBTp6H+/DYi3jmi+BW4w9YR GxkPTAqPZnaJAkkJJJMPoc+RL/f9h//7nNgeIMoKhpfpGCEYRPx1eYD5RwhnFCTS 6nUDbQPtaRFENKw2wGzbCJrG3DO6A/Et+tM35zv0M2yIKUUaRQv2xSEnqsuV671u 6+m1TFOKBEdppx8KxNU2Qcc0EvsBzOnNq5KIEGT5ZLL+olgmjfbHpecikoXW2VAC B36iFGrBPnb/0HkbC5W7wKCdU7ZIh8o3cvSULNsMAAjtAbLgxG/J5ZaGM0EHDR8= =ci2i -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519223625.ga19...@dyne.org
Re: UPG and the default umask
On Mon, May 17, 2010 at 04:00:57AM +0200, Thomas Hochstein wrote: Felipe Sateler schrieb: I mean, is there a reason for why I would want a non-UPG system? What about a hosting environment where you need to have user files world-readable (HTML documents or (PHP) scripts readable by www-data), but don't want them readable by other customers? You could achieve that by putting all customers in a common group (users) and setting the files 604 or the like. I think that in a UPG environment you could achieve the same (at least in the case when there is a certain directory in which all those users create their files, like /var/www/ or something) with a combination of a common group, umask 072, and a setgid bit (and most likely a sticky bit too to prevent deletions) on the shared directory. -- Stanislav -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519232410.ga32...@kaiba.homelan
Re: snapshot.debian.org implications for you
On Wed, 19 May 2010, Felipe Sateler wrote: On 19/05/10 10:08, Raphael Hertzog wrote: On Wed, 19 May 2010, Felipe Sateler wrote: Most of the repackaging is done because we don't _want_ to redistribute those files not because we do not have the right to redistribute them. [citation needed] My perception of the matter is the other way around. Take the case of stripped RFC, we can't modify them, hence they are non-free for us and we don't want to carry them. But they are distributable and having them on snapshot.d.o hurts nobody. The same goes for any other non-free material that upstream includes on purpose (as opposed to by mistake). Say a PDF documentation or a logo or even a GFDL doc with invariants. I was under the impression that snapshots.debian.org main had to respect the same rules as ftp.debian.org main. If that is true, you cannot then leave RFCs or other non-free material there. If not, then you are probably right. The only requirement for files distributed via snapshot.d.o is that we are allowed to distribute them. And probably we also want to require that anybody else is allowed to do the same. Snapshot is a history of our various ftp trees. If we make mistakes we should correct them, but we should not go back and re-write history unless we have to due to legal reasons. Cheers, weasel -- | .''`. ** Debian GNU/Linux ** Peter Palfrader | : :' : The universal http://www.palfrader.org/ | `. `' Operating System | `-http://www.debian.org/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519233221.gg13...@anguilla.noreply.org
Re: How to set ulimit (nofile) for a daemon
In article 20100519225812.gb28...@dario.dodds.net you wrote: These daemons load pam_limits *when running on behalf of other users*. That's an entirely different scenario than running a daemon per se. In the case of a java process started with an init script, it would be su doing the pam chain typically. For the daemon package I think it is not using pam sanely. Too bad it does not support setting ulimits directly. Gruss Bernd -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201005192330.o4jnubi3076...@neskaya.eckenfels.net
Re: UPG and the default umask
On 19/05/2010 23:22, Santiago Vila wrote: On Wed, 19 May 2010, Roger Leigh wrote: On 19/05/10 18:25, Santiago Vila wrote: For the record: I've changed the umask setting in /etc/profile to this: if [ `id -u` -ge 1000 ]; then Should we also be catering for the reserved globally allocated UIDs in the range 6-64999 with this check (Policy §9.2.2)? Hmm, good question. Can you give me an example of an uid which has been allocated that way? I'm not aware of any, TBH. It's just a case where future use might cause potential vulnerabilities if not catered for as for UIDs 1000 since you'd be using 0002 where 0022 would be expected. Perhaps I should follow policy more closely, yes, but that would mean using the range 1000-2 only, not 1000-5, as 3-5 is reserved (whatever that means). If an admin which runs out of UIDs in his system modifies /etc/adduser.conf, will he remember to modify the upper bound in /etc/profile as well? Maybe the above check should source /etc/adduser.conf and use the values LAST_SYSTEM_UID and LAST_UID (or default to 0022 and then enable and 0002 umask if in the range FIRST_UID to LAST_UID which is a bit simpler): UMASK=0022 # In a UPG setup, relax umask to 0002. if [ $(id -u) -ge $FIRST_UID -a $(id -u) -le $LAST_UID ]; then UMASK=0002 fi umask $UMASK Regards, Roger -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bf472b4.5090...@codelibre.net
Re: UPG and the default umask
Le Wed, May 19, 2010 at 01:10:25PM -0600, Aaron Toponce a écrit : UPG is only if the user name and group name match, and the user is the only member of that group. Hi Aaron and everybody, is there any ‘official’ definition of UPG, for instance the first document presenting the concept after it was finalised? I was looking for such a reference for the patch to the release notes but could not find one. By the way, for following the corrections of the Debian documentations as well as the bugs found by changing the umask, I suggest to use the following wiki page: http://wiki.debian.org/umask Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100519235440.gb13...@kunpuu.plessy.org
Re: How to set ulimit (nofile) for a daemon
Thomas Koch tho...@koch.ro writes: HBase needs a high nofile limit. What would be the preferred way to set the limit for the HBase daemons? Just call ulimit in the initscript? That's what I'd do. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87632j1lcw@windlord.stanford.edu
Re: How to set ulimit (nofile) for a daemon
On Wed, 19 May 2010, Russ Allbery wrote: Thomas Koch tho...@koch.ro writes: HBase needs a high nofile limit. What would be the preferred way to set the limit for the HBase daemons? Just call ulimit in the initscript? That's what I'd do. I'd suggest having it in /etc/default/hbase (or whatever gets sourced by the init script) so that it's easily modifiable by the user. [I'd wonder slightly at why it needs a high nofile, but...] Don Armstrong -- With one simple pill we cured unhappiness and art -- a softer world #437 http://www.asofterworld.com/index.php?id=437 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100520003354.gd4...@teltox.donarmstrong.com
Re: How to set ulimit (nofile) for a daemon
On Thu, May 20, 2010 at 01:30:37AM +0200, Bernd Eckenfels wrote: In article 20100519225812.gb28...@dario.dodds.net you wrote: These daemons load pam_limits *when running on behalf of other users*. That's an entirely different scenario than running a daemon per se. In the case of a java process started with an init script, it would be su doing the pam chain typically. *Typically*, you would run the process using start-stop-daemon -u instead of su, so again ther would be no PAM stack. -- 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 signature.asc Description: Digital signature
Re: APT do not work with Squid as a proxy because of pipelining default
On Wed, May 19, 2010 at 03:28:00PM +0200, Bjørn Mork bj...@mork.no was heard to say: Pierre Habouzit madco...@madism.org writes: This is bullshit. It's *VERY* easy to support pipelining: parse one request at a time, and until you're done with a given request, you just stop to watch the socket/file-descriptor for reading (IOW you let the consecutive request live in the kernel buffers). Yeah, you make it sound easy. I'm sure those writing proxy servers are just stupid. There are lots of easy features that my own software doesn't support, and I don't think I'm particularly stupid. It just means I have less than an infinite amount of time. Daniel -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100520010845.ga16...@emurlahn.burrows.local
Re: APT do not work with Squid as a proxy because of pipelining default
Philipp Kern tr...@philkern.de writes: On 2010-05-19, Goswin von Brederlow goswin-...@web.de wrote: Reading that I don't think that is really a pipelining issue. You do not need pipelineing for it to work. The real problem is keep-alive. The connection isn't destroyed after each request so you can put multiple requests into the stream and exploit different brokenness in different parsers along the way. Those are bugs in the servers that allow that output, though. I think you have failed to show that pipelining is broken. What seems broken is Keep-Alive. Do you suggest we stop using Keep-Alive to prevent broken parsers from being exploited? Make a full 3-way handshake for every request? I think we would want keep-alive with a pipeline depth of 1 (i.e. send the Obviously I did not mean to disable Keep-Alive. :) new request after the old one was processed). I'd rather think that TCP slow start is a problem if you avoid keepalive than the full 3-way handshake (which is annoying too). Concurrent requests put an unreasonable load onto the mirrors, so we should avoid that. Kind regards, Philipp Kern How about useing pipelining and if it breaks retry without pipelining and inform the user of it? If it occurs frequently the user will eventually notice the message and configure a depth of 1. So 2 changes: 1) cope with the error graciously and 2) explain what is probably happening. That way most people would get the speed benefit and installations would still not break when broken software is encountered. MfG Goswin PS: That doesn't mean squid shouldn't be fixed too. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87d3wrnqyi@frosties.localdomain
Bug#582345: ITP: libhash-fieldhash-perl -- Perl module implementing a lightweight field hash
Package: wnpp Severity: wishlist Owner: Ivan Kohler ivan-deb...@420.am Owner: Ivan Kohler ivan-deb...@420.am * Package name: libhash-fieldhash-perl Version : 0.10 Upstream Author : Goro Fuji gfuji(at)cpan.org * URL : http://search.cpan.org/dist/Hash-FieldHash/ * License : Perl Programming Lang: Perl Description : Perl module implementing a lightweight field hash Hash::FieldHash provides the field hash mechanism which supports the inside-out technique. You may know Hash::Util::FieldHash. It's a very useful module, but too complex to understand all the functions. This is an alternative to H::U::F with following features: Simpler interface Hash::FieldHash provides a few functions: fieldhash() and fieldhashes(). That's enough. Higher performance Hash::FieldHash is faster than Hash::Util::FieldHash, because its internals use simpler structures. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100520040331.27426.23717.report...@skydancer.freeside.biz
Re: UPG and the default umask
On 05/19/2010 03:48 PM, Christoph Anton Mitterer wrote: See above, or do you wish a larger paper discussing the issues?! ^^ So FUD it is. At least you're consistent. -- . O . O . O . . O O . . . O . . . O . O O O . O . O O . . O O O O . O . . O O O O . O O O signature.asc Description: OpenPGP digital signature
Re: APT do not work with Squid as a proxy because of pipelining default
Bjørn Mork bj...@mork.no writes: Goswin von Brederlow goswin-...@web.de writes: A HTTP/1.1 conforming server or proxy This is not the real world... is free to process pipelined requests serially one by one. The only requirement is that it does not corrupt the second request by reading all available data into a buffer, parsing the first request and then throwing away the buffer and thereby discarding the subsequent requests in that buffer. It is perfectly fine for the server to parse the first request, think, respond to the first request and then continue to parse the second one. Yes, this can be done. But you should ask yourself what proxies are used for. The serializing strategy will work, but it will make the connection slower with a proxy than without. That's not going to sell many proxy servers. Sure. I was talking about conformance. A proxy / server that screws that up deserves to be shot. And from the description of the probem this part actualy works in squid, people WOULD have noticed otherwise. Squids problem seems to be that it does break later when processing the responce. But that is a guess from the description of the problem. Still no tcpdump of what actually happens posted. Note that that behaviour in the server already gives a huge speed increase. It cuts away the round trip time between the last responce and the next request. For static web content the speedup of processing pipelined requests truely in parallel is neglible anyway. Only dynamic pages, where formulating the responce to a request takes time, would benefit by working on multiple responces on multiple cores. And those are probably busy handling requests from other connections. So I wouldn't expect servers to actually to parallel processing of pipelined requests at all. This is true for a web server. It is only true for a proxy server if it can either forward a pipelined request or parallelize it. That's where we get the complexity. If you keep your simple serial strategy, then a pipelined request will be slower than a parallel one. But no slower than without pipelining. I was talking specifically about server and not porxy for a reason by the way. :) And your argument 1 applies perfectly to fixing squid by the way. It should accept pipelined requests and then it can proces them one by one and send them non pipelined if it likes. It should NOT corrupt the requests/responces. Sure. Squid should be fixed. But I'm afraid fixing squid in Debian won't fix all the http proxies around the world. Lets start with the beam in our eye before we go chasing moths in other peoples. So just from your argument 1 APT should default not to pipeline and squid should be fixed. Good. Let me clarify this. Apt should default not to pipeline in stable. That is the trivial workaround for the problem. In unstable something better can be tried, like detect when pipelining fails and automatically fall back to depth 1. But defaulting to depth 1 till someone programs that is an option too. Bjørn MfG Goswin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/877hmznqgs@frosties.localdomain
Bug#582346: ITP: libobject-id-perl -- Perl module providing a unique identifier for any or every object
Package: wnpp Severity: wishlist Owner: Ivan Kohler ivan-deb...@420.am Owner: Ivan Kohler ivan-deb...@420.am * Package name: libobject-id-perl Version : 0.1.0 Upstream Author : Michael G Schwern schw...@pobox.com * URL : http://search.cpan.org/dist/Object-ID/ * License : Perl Programming Lang: Perl Description : Perl module providing a unique identifier for any or every object This is a unique identifier for any object, regardless of its type, structure or contents. Its features are: * Works on ANY object of any type * Does not modify the object in any way * Does not change with the object's contents * Is O(1) to calculate (ie. doesn't matter how big the object is) * The id is unique for the life of the process * The id is always a true value -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100520041019.27451.89581.report...@skydancer.freeside.biz
Re: APT do not work with Squid as a proxy because of pipelining default
David Kalnischkies kalnischkies+deb...@gmail.com writes: Hi all, i don't want to interrupt your battles so feel free to ignore me, but i want to raise some questions (for you and me) none the less: The notice about the - in the eyes of the writer of this manpage section - broken squid version 2.0.2 in the apt.conf manpage was changed the last time in 2004, so the issue isn't new. The manpage at least claims that this squid version is broken also in respect to other cache control settings. I don't know a single bit about squid but a search for squid pipeline turns up some documentation about a pipeline_prefetch setting: Available in: 3.12.73.HEAD2.HEAD3.02.6 To boost the performance of pipelined requests to closer match that of a non-proxied environment Squid can try to fetch up to two requests in parallel from a pipeline. http://www.squid-cache.org/Doc/config/pipeline_prefetch/ For somebody without knowledge this looks like as any version in debian should be able to handle a pipeline - otherwise this setting wouldn't make much sense The default value for the APT option above is btw 10 and in apt #413324 we have a claim that squid works well with a value of 5 or even 8 -- so it is maybe just a bug in handling too much pipelined requests? Or something comparable to what happened in #541428 regarding lighttpd and pipelining (timeout)? (i am just shooting into the dark) Also, then we talk here about pipelines and her usage keep in mind that APTs http usage is special compared to an implementation and usage in a browser: We have a trust chain available so we should be on the save side security wise, the number of debian archives is limited and most of them should be on a sane webserver (if not i would not have much trust in the archive ) and especially on apt-get update we have either a lot of cache hits (file has not changed) or a lot of very small files (Release, Index and maybe pdiff) to transfer. New package updates come from the same archive most of time and most packages are relatively small, too, but having an upgrade including at least 500 packages is relatively common Do I hear an idea in there? Use pipelineing for small stuff (header check, Release, Release.gpg, pdiff, dsc) but then default to depth 1 for the big files (Packages.gz, debs, orig.tar.gz). On the other hand APTs http client isn't as nice as he could be in terms that he could fallback to non-pipeline, retry or whatever. (and i wouldn't be too surprised if this would turn out to be an APT bug) As we all know APT is a debian native tool and the base of a whole bunch of other stuff so beside ranting about his shortcomings we could also work on patches as the people with enough knowledge to do this seems to be already around in this thread. Thanks in advance and best regards, David Kalnischkies P.S. Sry Luigi Gangitano for cc'ing, but i don't know if you follow the thread and i included too often squid in the mail to not direct the mail into your direction. MfG Goswin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8739xnnq7x@frosties.localdomain
Re: APT do not work with Squid as a proxy because of pipelining default
Daniel Burrows dburr...@debian.org writes: On Wed, May 19, 2010 at 03:28:00PM +0200, Bjørn Mork bj...@mork.no was heard to say: Pierre Habouzit madco...@madism.org writes: This is bullshit. It's *VERY* easy to support pipelining: parse one request at a time, and until you're done with a given request, you just stop to watch the socket/file-descriptor for reading (IOW you let the consecutive request live in the kernel buffers). Yeah, you make it sound easy. I'm sure those writing proxy servers are just stupid. There are lots of easy features that my own software doesn't support, and I don't think I'm particularly stupid. It just means I have less than an infinite amount of time. Daniel That isn't a problem. The problem arises when you start to support the feature but mess it up. Processing pipelined requests one by one is easy but slow. Processing them in parallel is hard but faster. But please do make sure it works before you do. :) MfG Goswin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87y6ffmbka@frosties.localdomain
Accepted evolution-data-server 2.30.1-4 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 May 2010 01:22:40 +0200 Source: evolution-data-server Binary: evolution-data-server evolution-data-server-common evolution-data-server-dev evolution-data-server-dbg libedataserver1.2-11 libedataserver1.2-dev libcamel1.2-14 libcamel1.2-dev libebook1.2-9 libebook1.2-dev libedataserverui1.2-8 libedataserverui1.2-dev libedata-book1.2-2 libedata-book1.2-dev libecal1.2-7 libecal1.2-dev libedata-cal1.2-7 libedata-cal1.2-dev libegroupwise1.2-13 libegroupwise1.2-dev libgdata1.2-1 libgdata1.2-dev libgdata-google1.2-1 libgdata-google1.2-dev libebackend1.2-0 libebackend1.2-dev Architecture: source all amd64 Version: 2.30.1-4 Distribution: unstable Urgency: low Maintainer: Debian Evolution Maintainers pkg-evolution-maintain...@lists.alioth.debian.org Changed-By: Yves-Alexis Perez cor...@debian.org Description: evolution-data-server - evolution database backend server evolution-data-server-common - architecture independent files for Evolution Data Server evolution-data-server-dbg - evolution database backend server with debugging symbols evolution-data-server-dev - Development files for evolution-data-server (metapackage) libcamel1.2-14 - The Evolution MIME message handling library libcamel1.2-dev - Development files for libcamel libebackend1.2-0 - Utility library for evolution data servers libebackend1.2-dev - Utility library for evolution data servers (development files) libebook1.2-9 - Client library for evolution address books libebook1.2-dev - Client library for evolution address books (development files) libecal1.2-7 - Client library for evolution calendars libecal1.2-dev - Client library for evolution calendars (development files) libedata-book1.2-2 - Backend library for evolution address books libedata-book1.2-dev - Backend library for evolution address books (development files) libedata-cal1.2-7 - Backend library for evolution calendars libedata-cal1.2-dev - Backend library for evolution calendars (development files) libedataserver1.2-11 - Utility library for evolution data servers libedataserver1.2-dev - Utility library for evolution data servers (development files) libedataserverui1.2-8 - GUI utility library for evolution data servers libedataserverui1.2-dev - GUI utility library for evolution data servers (development files libegroupwise1.2-13 - Client library for accessing groupwise POA through SOAP interface libegroupwise1.2-dev - Development files for libegroupwise libgdata-google1.2-1 - Client library for accessing Google POA through SOAP interface libgdata-google1.2-dev - Client library for accessing Google POA (development files) libgdata1.2-1 - Client library for accessing Google POA through SOAP interface libgdata1.2-dev - Client library for accessing Google POA (development files) Closes: 582148 582150 Changes: evolution-data-server (2.30.1-4) unstable; urgency=low . * debian/control: - adjust eds-dev dependencies. closes: #582150, #582148 Checksums-Sha1: 166a726549e4c83fba16f5cb956a236209424886 3415 evolution-data-server_2.30.1-4.dsc c530ce237e94b2d1c5cad709d62e9933c3a94100 24004 evolution-data-server_2.30.1-4.diff.gz 4d8fd9332dd1551fcdc8d56b359a09931f3d7501 2293298 evolution-data-server-common_2.30.1-4_all.deb b1d47bb9a380483fd992dcc64eaa5f3937ad8c1c 699352 evolution-data-server_2.30.1-4_amd64.deb 5a5efaf745e759ba446e8fcd9c6f846b1784df7c 105752 evolution-data-server-dev_2.30.1-4_amd64.deb a258d09ad5dd3f4c0759fe91cad55855c990d47e 3190832 evolution-data-server-dbg_2.30.1-4_amd64.deb f3030fd721d5ee66cbc513ed51f615d7ad5e3553 181334 libedataserver1.2-11_2.30.1-4_amd64.deb be4daba717cd8d439d2024f8b6f82806a81aa7e9 199154 libedataserver1.2-dev_2.30.1-4_amd64.deb c96d6e8484acfd9e28a2e6256dbced803af8d6ba 503150 libcamel1.2-14_2.30.1-4_amd64.deb ef4d9716300c48b345bae5647a3d257351139568 488240 libcamel1.2-dev_2.30.1-4_amd64.deb 05637fb47ae504baa17ca8aa6dc8f1cbf209582f 175292 libebook1.2-9_2.30.1-4_amd64.deb b768dc3d2ff925eb8141e24cf3c7533c09332bb2 186434 libebook1.2-dev_2.30.1-4_amd64.deb 90d992665b1ac6fde26e6206d6c0b364c27a2c0f 198800 libedataserverui1.2-8_2.30.1-4_amd64.deb a73929c675ada7dfb7e5f92f0084adc41f285edb 157144 libedataserverui1.2-dev_2.30.1-4_amd64.deb 38bbd176c63f497b96c2499e3761096247692547 145462 libedata-book1.2-2_2.30.1-4_amd64.deb 5ded6b91b25ff6c6c959d9ae3cc46e33829acc6b 155498 libedata-book1.2-dev_2.30.1-4_amd64.deb d539c36cee48a462b7fd75a026f376289bc913ad 197050 libecal1.2-7_2.30.1-4_amd64.deb 0890b9ad2539a187e04a4a9134c22c4d455d98ff 189158 libecal1.2-dev_2.30.1-4_amd64.deb e216564b68e8c690f25d740116a779989b6844e9 159304 libedata-cal1.2-7_2.30.1-4_amd64.deb 4ff8e8b09b37bd7ccf607735741a309a29050097 166000 libedata-cal1.2-dev_2.30.1-4_amd64.deb 354a47a882c6d54bde90a963f62d07579c282103 174768 libegroupwise1.2-13_2.30.1-4_amd64.deb b6be0ed0c55a50e5e4332002d60adcb33f0d48e8 114888
Accepted evolution-exchange 2.30.1-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 May 2010 07:51:48 +0200 Source: evolution-exchange Binary: evolution-exchange evolution-exchange-dbg Architecture: source amd64 Version: 2.30.1-2 Distribution: unstable Urgency: low Maintainer: Debian Evolution Maintainers pkg-evolution-maintain...@lists.alioth.debian.org Changed-By: Yves-Alexis Perez cor...@debian.org Description: evolution-exchange - Exchange plugin for the Evolution groupware suite evolution-exchange-dbg - Exchange plugin for Evolution with debugging symbols Closes: 582205 Changes: evolution-exchange (2.30.1-2) unstable; urgency=low . * Brown paper bag release. * debian/control: - update depend/conflict for 2.30. closes: #582205 Checksums-Sha1: ff65f1bbef2928594eacdedcf5a80d50e61745e3 2973 evolution-exchange_2.30.1-2.dsc daf64ef38ca6a06e4d4d8cf6de450139b689e58d 6851 evolution-exchange_2.30.1-2.diff.gz 0b02b0a3d45adb97fb111090b8f9aac44267d30b 1753600 evolution-exchange_2.30.1-2_amd64.deb 6533e67a2e2d1024e953736af89888e15aa1294a 1739640 evolution-exchange-dbg_2.30.1-2_amd64.deb Checksums-Sha256: e82640dfa284c067d2b916ae2be18cbb221bdcd519e455e00060a236a020c0a6 2973 evolution-exchange_2.30.1-2.dsc c7f53df72b194501bc6fd69740a04c2d64e12d5169de50acfa15d20b04d8492b 6851 evolution-exchange_2.30.1-2.diff.gz 93d56ee2fc9cf70d5c3181ab602c589c311ca93902675fe1fde7f5c8f33b394d 1753600 evolution-exchange_2.30.1-2_amd64.deb 9ab7fb2d18e7a900bb20c7af8b2fbed64614b68f529d409048f9c5866bc71ed9 1739640 evolution-exchange-dbg_2.30.1-2_amd64.deb Files: e4eb53b66be440ae7ec2c14dba8fcc62 2973 gnome optional evolution-exchange_2.30.1-2.dsc c0dab59a9972064bd8d5cec8d4fdb389 6851 gnome optional evolution-exchange_2.30.1-2.diff.gz eb713975b891bbbc8ba7c122337355a9 1753600 gnome optional evolution-exchange_2.30.1-2_amd64.deb d6bf9b9c83c811add8a5845432fba24a 1739640 debug extra evolution-exchange-dbg_2.30.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCgAGBQJL84FyAAoJEDBVD3hx7wuogBEQAItS1+X3NRIFOp/1yj3TM8+K XPzO8v4/8e0brG7Iw8ykdXQurAk3VxANQO84+Wq3D8nmW6OUmQ9etLo4VZxJDyb2 YJV1eEKBgzTVBBgwhAdTeuFQa4Gm/3v/jPv63yOF2C1EYUtCXFTA9abT+jzP6vqu G8qGSJqfxC+EcIX09A8SjTIMfhxpSAVLvockM+1EYeKBNx8vtu51WuYToao0hvzz 4WhzWbnqgxhF0jhFSPhzfc2yv1V/Lj+81vGNg56f4Ah+9pnHftETfmI7IucWEtDg GC1ppNvhDG44ZUWSxQPx5tH418a096bcaDixGuti5BvRW9sdP0HPz0BjkzWw/q3e 68zs/3u6JsU2nROs1lX0gnTQceaVQDIUW7kXIiJdps5XzaaF6E64D1srZvLEhy5r eHfDdDcmk+qyyExBjXh1z5knCjgCG0duSuQMM+Uhd4wh8L2umQkGV47WuvU7MQK/ GK3nX0jK52gRsAQEZtFS5H7+maUaUZ0AsrWbhfqE+7PNvD/dE5D7sv1OiOuzlETi 7O3rF+KS5rIn5FPvDrxyMFp9KEF/nTW04Jmvydzg5QtMQcKIW4rXqkL4M/gmP49C 5JVeYjmoKtCfSYWBSOkUE8sBrl7NzsImfSlFoiG2LZWrjcGy933RAxeTIXNeqajD wKcIg84Bszgb1EetLYap =lZMx -END PGP SIGNATURE- Accepted: evolution-exchange-dbg_2.30.1-2_amd64.deb to main/e/evolution-exchange/evolution-exchange-dbg_2.30.1-2_amd64.deb evolution-exchange_2.30.1-2.diff.gz to main/e/evolution-exchange/evolution-exchange_2.30.1-2.diff.gz evolution-exchange_2.30.1-2.dsc to main/e/evolution-exchange/evolution-exchange_2.30.1-2.dsc evolution-exchange_2.30.1-2_amd64.deb to main/e/evolution-exchange/evolution-exchange_2.30.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 Archive: http://lists.debian.org/e1oecqc-0008tb...@ries.debian.org
Accepted skrooge 0.7.1-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 19 May 2010 08:40:03 +0300 Source: skrooge Binary: skrooge skrooge-common Architecture: source amd64 all Version: 0.7.1-1 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team pkg-kde-ext...@lists.alioth.debian.org Changed-By: Fathi Boudra f...@debian.org Description: skrooge- personal finance manager for KDE skrooge-common - Skrooge architecture independent files Closes: 582184 582185 Changes: skrooge (0.7.1-1) unstable; urgency=low . * New upstream release. * Drop 97_fix_target_link_libraries.diff - merged upstream. * Update debian/control: - Bump kdelibs5-dev build-dependency. - Add libqt4-sql-sqlite dependency. (Closes: #582185) * Add debian/watch file. Thanks to Felix Geyer. (Closes: #582184) Checksums-Sha1: 2a4b980284689ff2b32f005c53397330bc222148 1495 skrooge_0.7.1-1.dsc adc0813707652a267968c76f6264ca07ff5c3158 7586945 skrooge_0.7.1.orig.tar.bz2 054cdc77e74807b6b1f03f2cfd4427ece3ffaef8 2943 skrooge_0.7.1-1.debian.tar.gz ce47384d47963e52c616a503d0c743b534d3bdea 1590404 skrooge_0.7.1-1_amd64.deb 88b75f918ba2c2d1edd608c7424c8de68bf2279a 6187882 skrooge-common_0.7.1-1_all.deb Checksums-Sha256: d5d9d0cff44a1c13a466a5e56f0df1ae858091d94640b36ac56cfcbf1c831551 1495 skrooge_0.7.1-1.dsc 72ce26483c33e9a275960ef33bf71d305197fb3ca5bfc67a08750b7d24810213 7586945 skrooge_0.7.1.orig.tar.bz2 4301dbe843f619d3c7a82b9050cf1965c869138d71305ea4b89c6b680dee9fdf 2943 skrooge_0.7.1-1.debian.tar.gz 049f137aa18d662759d2419db819e219cc8aa1561c4b2b37b075e3a94b845785 1590404 skrooge_0.7.1-1_amd64.deb 59ed61294b66cad46d5c2a6b6cedf9373b9ddc8a3d66ea366bad8b0fe785de85 6187882 skrooge-common_0.7.1-1_all.deb Files: eeb62d53cfb64cad7df9e25adcec244c 1495 kde optional skrooge_0.7.1-1.dsc 403e6ae9775066c99e42e8c6381a3ff3 7586945 kde optional skrooge_0.7.1.orig.tar.bz2 20ceeccba72162210d11c986941fa590 2943 kde optional skrooge_0.7.1-1.debian.tar.gz 962b338cc5db6bf91a0afac3fb473500 1590404 kde optional skrooge_0.7.1-1_amd64.deb 0b9004148fad061e65b07073760a1420 6187882 kde optional skrooge-common_0.7.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iJwEAQECAAYFAkvzf6oACgkQjPU19mqlcvfyDgP8DFXJFvUt5mGaho0kCC018YH/ OjLy5fLAqJSXoHMd4W4LiNJds/SnVRbvARV1Utb8OctifyOwt8uiTOiwk5z2oUlD iUMnontf7d2nBX7F8Rr2PxPFKLEeIKjqkIt6q5lRL6l3m6kD4X2hON8g+C6hB6Ix p7SIeMJm3zmZ3FY8tz0= =RjQc -END PGP SIGNATURE- Accepted: skrooge-common_0.7.1-1_all.deb to main/s/skrooge/skrooge-common_0.7.1-1_all.deb skrooge_0.7.1-1.debian.tar.gz to main/s/skrooge/skrooge_0.7.1-1.debian.tar.gz skrooge_0.7.1-1.dsc to main/s/skrooge/skrooge_0.7.1-1.dsc skrooge_0.7.1-1_amd64.deb to main/s/skrooge/skrooge_0.7.1-1_amd64.deb skrooge_0.7.1.orig.tar.bz2 to main/s/skrooge/skrooge_0.7.1.orig.tar.bz2 -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oecrv-e5...@ries.debian.org
Accepted dpkg 1.15.7.2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 19 May 2010 07:57:14 +0200 Source: dpkg Binary: libdpkg-dev dpkg dpkg-dev libdpkg-perl dselect Architecture: source amd64 all Version: 1.15.7.2 Distribution: unstable Urgency: low Maintainer: Dpkg Developers debian-d...@lists.debian.org Changed-By: Guillem Jover guil...@debian.org Description: dpkg - Debian package management system dpkg-dev - Debian package development tools dselect- Debian package management front-end libdpkg-dev - Debian package management static library libdpkg-perl - Dpkg perl modules Closes: 568123 575158 575410 578002 578635 579722 579724 580774 580984 581315 Changes: dpkg (1.15.7.2) unstable; urgency=low . [ Raphaël Hertzog ] * Update dpkg-buildflags to respect $XDG_CONFIG_HOME and to use $XDG_CONFIG_HOME/dpkg/buildflags.conf by default. * Update deb-substvars(5) to codify how variables containing multiple lines must be managed. * Fix boolean evaluation of Dpkg::Version so that version 0 evaluates to false and dpkg-shlibdeps can strip the minimal version specification. Closes: #579724 Document this behaviour in the API and add non-regression test to ensure it's kept. * Let dpkg-buildflags error out when a required parameter is missing. Closes: #579722 * Add Bug-Ubuntu field in DEP-3 template provided in the automatic header of patches in 3.0 (quilt) source packages. Thanks to Benjamin Drung bdr...@ubuntu.com for the patch. Closes: #578002 * Update deb-override(5) by removing references to usage of sections to place the packages on the mirrors and by indicating that the Debian policy offers a list of allowed values for section and priority. Closes: #575410 * Update reference to triggers.txt.gz in dpkg-trigger(1) and deb-triggers(5) to match the new location. Closes: #580774 * Drop mention of PKG_CONFIG_LIBDIR in dpkg-buildpackage(1), the feature has been removed in 1.15.6. * Rename /usr/lib/dpkg/maintscript-helper into /usr/bin/dpkg-maintscript-helper, it is a public interface even if working around known limitations. * Add supports command to dpkg-maintscript-helper to ensure the wanted command is supported before calling it. . [ Guillem Jover ] * Add powerpcspe support to ostable and triplettable. Thanks to Sebastian Andrzej Siewior sebast...@breakpoint.cc and Kyle Moffett kyle.d.moff...@boeing.com. Closes: #568123, #575158 * Fix dpkg --root by properly stripping again the root directory from the path of the maintainer script to execute. Closes: #580984 * On Linux use sync() instead of an fsync() per file on deferred extraction, to workaround performance degradation on ext4. Closes: #578635 . [ Gerfried Fuchs ] * Fix syntax error in dpkg-name. Closes: #581315 Checksums-Sha1: 420ab2514738462b7b10213a3de84dff13df4dd6 1221 dpkg_1.15.7.2.dsc 50e0f02d136df495f28ab522c7afc79f1dc8126e 4921845 dpkg_1.15.7.2.tar.bz2 f6b0eb3be544d0fabb54ce41843048c0645a77ae 377240 libdpkg-dev_1.15.7.2_amd64.deb c9df22429998e8b19e7d99674fce687df519d695 1918510 dpkg_1.15.7.2_amd64.deb b694bd54de2b8166c72e5820c744f7ca3111fd20 792554 dselect_1.15.7.2_amd64.deb 515a0a45eb4bf1d2b4ecbc1fbb2fd5fd74dcc07c 407772 dpkg-dev_1.15.7.2_all.deb fb1db2c154d53dc896b665bf36200a634097bb47 582860 libdpkg-perl_1.15.7.2_all.deb Checksums-Sha256: 6db728bc70b1e99732f8f7801ce5760b5fccb1143d90b8d863b1e99b87474aa7 1221 dpkg_1.15.7.2.dsc d3235cbcd5580c4b8d83b6dcf3ab71a076178bcca327c1339a1f95a8324103a5 4921845 dpkg_1.15.7.2.tar.bz2 b635959be15b837a4e3ffddb61ef606e8ae523ea8f77a42dd3bcf856d892975d 377240 libdpkg-dev_1.15.7.2_amd64.deb eb4499b7d46a275f23307f2ac2100c8b635884be2ca58d7d5fe2afdaebb72e0b 1918510 dpkg_1.15.7.2_amd64.deb b38f2454ae934d7c35e9404686c02290b54b941556643fde465d41d22116c0e1 792554 dselect_1.15.7.2_amd64.deb 889c3311165f370e1251b00fec283b94f73c09add812bd2e20756bf94e16a0f7 407772 dpkg-dev_1.15.7.2_all.deb 4d08e26e78a64771c334623ced12a62e58ab36c9f811b68dfacfe64acbaaf7b4 582860 libdpkg-perl_1.15.7.2_all.deb Files: 0153b46014452aad73a53e76698a19b1 1221 admin required dpkg_1.15.7.2.dsc bcd5c89035049352df03ebc75464e807 4921845 admin required dpkg_1.15.7.2.tar.bz2 b3ecd33aa1fb9b2650fa5bc5ff16c5a7 377240 libdevel optional libdpkg-dev_1.15.7.2_amd64.deb 44002bb70fda5c3275b6801f62a45664 1918510 admin required dpkg_1.15.7.2_amd64.deb 0fb773d6db419958469662c075bd83fd 792554 admin optional dselect_1.15.7.2_amd64.deb efb65b21888ab7f4ca4bc4b1448c6d8e 407772 utils optional dpkg-dev_1.15.7.2_all.deb 980504122618351c753737f4f1925bd2 582860 perl optional libdpkg-perl_1.15.7.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvzgfEACgkQuW9ciZ2SjJuSdgCg91mEwlOV6P6mWK8fjX/l4dxG +fwAoPOGKwSe3i7GxFSFN5CvTusw1oy+ =vTo4 -END PGP SIGNATURE- Accepted: dpkg-dev_1.15.7.2_all.deb to main/d/dpkg/dpkg-dev_1.15.7.2_all.deb
Accepted qemu-kvm 0.12.4+dfsg-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 18 May 2010 22:43:54 +0200 Source: qemu-kvm Binary: qemu-kvm qemu-kvm-dbg kvm Architecture: source i386 Version: 0.12.4+dfsg-1 Distribution: unstable Urgency: low Maintainer: Jan Lübbe jlue...@debian.org Changed-By: Jan Lübbe jlue...@debian.org Description: kvm- dummy transitional package from kvm to qemu-kvm qemu-kvm - Full virtualization on x86 hardware qemu-kvm-dbg - Debugging info for qemu-kvm Closes: 558029 565573 574051 574073 575628 578154 578846 Changes: qemu-kvm (0.12.4+dfsg-1) unstable; urgency=low . [ Michael Tokarev ] * New upstream minor/stable release 0.12.4, incorporating the following patches: avoid_creating_too_large_iovecs_in_multiwrite_merge.patch net:-remove-broken-net_set_boot_mask-boot-device-validation.diff block:-free-iovec-arrays-allocated-by-multiwrite_merge.diff bail-out-when-VCPU_CREATE-fails.diff * add madv_mergeable-for-old-kernheaders-hack.diff, mostly to help bpo builds (it is to enable KMS even when compiled against old kernel headers, when running on recent-enough kernel) * fix kvm transitional package to have Priority: extra * also fix kvm transitional package to properly run with reportbug, and simplify the bug-script and use dh_bugfiles to install them. * adedd isa-refine-irq-reservations.patch from Gerd Hoffmann (closes: #574051) * added be_more_specific_in_-mem-path_error_messages.diff trivial patch to be more specific when throwing errors. (closes: #574073) * bump debhelper build-depend version to 7.2.3 due to dh_bugfiles. * net:-remove-broken-net_set_boot_mask-boot-device-validation.diff (to let it to boot from network using new -netdev syntax, cherry- picked from stable) (closes: #575628) * block:-free-iovec-arrays-allocated-by-multiwrite_merge.diff to fix a memory leak in virtio-blk implementation * rehash 04_use_etc_kvm_kvm-ifup.patch - apparently the #defines are now in two places, remove one of them and patch another * bail-out-when-VCPU_CREATE-fails.diff - new patch to make kvm to behave a bit nicely if vcpu_create fails: before it were just segfaulting. (closes: #558029) * give-useful-error-messages-when-tap-open-fails.diff: when manipulation of /dev/net/tun fails, give some more useful error messages. (closes: #578154) * document -incoming option (document--incoming-option.diff). (closes: #565573) * (preliminary) fix for usb keyboard keymap, usbkbd-menu-logo-keys.diff. (closes: #578846) Checksums-Sha1: 4048eede4580ce31e6cf9b2a041f4ecdbc85c96e 1613 qemu-kvm_0.12.4+dfsg-1.dsc 942751448c7905d245448ac3b015a7970200d8b9 3800176 qemu-kvm_0.12.4+dfsg.orig.tar.gz 45f48a8bd259011704ac3ac425c38c2546556b82 280453 qemu-kvm_0.12.4+dfsg-1.diff.gz 427fbebfd322121b037ddd9e6b8ce7d1587e4396 1486910 qemu-kvm_0.12.4+dfsg-1_i386.deb 3d3e99fea0c5fe4b4ec0cbe47a0f9f1337664139 2781082 qemu-kvm-dbg_0.12.4+dfsg-1_i386.deb 97b84602dc2d0845df90874ffd035c3a5d12d86b 10026 kvm_0.12.4+dfsg-1_i386.deb Checksums-Sha256: 3771ad46f9eda38a4d5485d7eb9498312436f1ff041219557d22be2d83255298 1613 qemu-kvm_0.12.4+dfsg-1.dsc b8545175542812c67c1b8bfbec887a54dedfccfbbca21515b93fcdbe9c982932 3800176 qemu-kvm_0.12.4+dfsg.orig.tar.gz f3f8bb38be9c94ae25155b560c52a8ae05f8fd6a86c2a1270e86313933ac46b9 280453 qemu-kvm_0.12.4+dfsg-1.diff.gz 5ef81ce77e5c7cc7b5400370f2af99949a66aad821fb74d4a4101cb5138f303f 1486910 qemu-kvm_0.12.4+dfsg-1_i386.deb 904b8ca37cdb081d274261ef1a8a61a74b3978742f96e6a230ad7a3c15a1e1f1 2781082 qemu-kvm-dbg_0.12.4+dfsg-1_i386.deb 8706c2175477f79844c09cfe516332cddd4fece52172dc21ea3dec4b5e335a8e 10026 kvm_0.12.4+dfsg-1_i386.deb Files: 40eb49dc0f3423d75ffddb93b2b3c0f7 1613 misc optional qemu-kvm_0.12.4+dfsg-1.dsc 085ce47a92f571093b4e86142e1eed83 3800176 misc optional qemu-kvm_0.12.4+dfsg.orig.tar.gz cc704f41c3ef816c549526f662a9d524 280453 misc optional qemu-kvm_0.12.4+dfsg-1.diff.gz 72685358f8cd9fc1fd42125db5bf6371 1486910 misc optional qemu-kvm_0.12.4+dfsg-1_i386.deb 8c2528b38b83c5765f88d52dd28aa317 2781082 debug extra qemu-kvm-dbg_0.12.4+dfsg-1_i386.deb 274127d351746f7f7d6aee3f59230d62 10026 oldlibs extra kvm_0.12.4+dfsg-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvzhvMACgkQioOL5NhIDy66VQCeMKtxF1Hs/GTGd4RS+uWoZEG+ FKEAn15CXca2+oJPuvNUw7P52RM7GoeO =Q6mc -END PGP SIGNATURE- Accepted: kvm_0.12.4+dfsg-1_i386.deb to main/q/qemu-kvm/kvm_0.12.4+dfsg-1_i386.deb qemu-kvm-dbg_0.12.4+dfsg-1_i386.deb to main/q/qemu-kvm/qemu-kvm-dbg_0.12.4+dfsg-1_i386.deb qemu-kvm_0.12.4+dfsg-1.diff.gz to main/q/qemu-kvm/qemu-kvm_0.12.4+dfsg-1.diff.gz qemu-kvm_0.12.4+dfsg-1.dsc to main/q/qemu-kvm/qemu-kvm_0.12.4+dfsg-1.dsc qemu-kvm_0.12.4+dfsg-1_i386.deb to main/q/qemu-kvm/qemu-kvm_0.12.4+dfsg-1_i386.deb qemu-kvm_0.12.4+dfsg.orig.tar.gz to
Accepted gsfonts 1:8.11+urwcyr1.0.7~pre44-4.1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Jan 2010 22:25:22 +0900 Source: gsfonts Binary: gsfonts Architecture: source all Version: 1:8.11+urwcyr1.0.7~pre44-4.1 Distribution: unstable Urgency: low Maintainer: Masayuki Hatta (mhatta) mha...@debian.org Changed-By: Kenshi Muto km...@debian.org Description: gsfonts- Fonts for the Ghostscript interpreter(s) Closes: 582113 Changes: gsfonts (1:8.11+urwcyr1.0.7~pre44-4.1) unstable; urgency=low . * Non-maintainer upload. * Replace defoma with update-gsfontmap. (closes: #582113) Checksums-Sha1: d6e7eede233883cec1daf663b48b5d0b9eedc304 1945 gsfonts_8.11+urwcyr1.0.7~pre44-4.1.dsc 7475918f9a702c83c20c371cdf17ba51a86d4671 6524 gsfonts_8.11+urwcyr1.0.7~pre44-4.1.diff.gz 78ad5e22b75326ab5e71729512b468ab14d32c9b 3367288 gsfonts_8.11+urwcyr1.0.7~pre44-4.1_all.deb Checksums-Sha256: 0b5ca511d607ad25ed8c30885d2c3ffb69b7a74d74e9946d167d5d2738000b29 1945 gsfonts_8.11+urwcyr1.0.7~pre44-4.1.dsc 7c8875ee741fa75f4dd20a388b481e12286d4a72b8d699133e31bca5092f97f0 6524 gsfonts_8.11+urwcyr1.0.7~pre44-4.1.diff.gz bd2c94d0df133533e43e7e47b9ff5cd91779a53d088237a57b774a4c51e135db 3367288 gsfonts_8.11+urwcyr1.0.7~pre44-4.1_all.deb Files: 0db94f5a41332f9a2dde507ebfb6b83f 1945 text optional gsfonts_8.11+urwcyr1.0.7~pre44-4.1.dsc f1d53ec61e6f8a42e9cc11611736618c 6524 text optional gsfonts_8.11+urwcyr1.0.7~pre44-4.1.diff.gz 963d85a174d801fd236686414bc65dbc 3367288 text optional gsfonts_8.11+urwcyr1.0.7~pre44-4.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBCgAGBQJL84lIAAoJEB0hyD3EUuD8YKMQAJ6rhZvh32FY/qicR9nXEp37 7MTkf6zQUbi0oUUt1D2UmYuEhQ0hPzB3Yz71iHrQKvw3NLiy6XXPz94M3BzLK+ki 1m0wfa6IemSJyTiN1d4JTWEh0ylfkbyXJ+51liU2nkyLxizqQ1ASQjOXOAZqUQL3 FFoxaQ0iV5vZp0Y6ObjTExvAaNqh46OIgUisbW3fn9sXtruANfdJJb1Wr43okr8t m3AmRIzYtWOJVeLp4ahG0LkDZn5F5LEJJQHaDIvq/2M6keP4WP2gsQ0MQ92f+7gG RW85sjIK4YUhjXJZBXJ6TrLz2bAv5mSRAysmRLMdsL9E4lZ3dAP6vK5sLIicnqyq MFhUERXTGFFV7zq5u/agZKOwFBZFkuqTet0t0DwhdTRuepygZCgmyMcf2Sd5fTim pbU0SsflO7YRzpYoDicxUgPEgqa0Neal69HvTU31wswURmWOaX7zUcx9A5GFVcYK Y/6WONxV1PkpROiEG4bRVTjCVo9704FCNPYEb0XiaYR4TSz7Bt8sY3Prf34bgKZd 7284/JTPfHOgozm3tARbKpCi5LaqOg7OCCzMokFyL/5EV2h8gYM8Kgd3s63xFcUH dtiOvA55h0I7EdOx0FhPZR1ElMF3Qqe1aGKPcc8vTuXjikiExX2mBIrCHtl0+ClG YON9ypgId/d/Dc+97liS =XQI6 -END PGP SIGNATURE- Accepted: gsfonts_8.11+urwcyr1.0.7~pre44-4.1.diff.gz to main/g/gsfonts/gsfonts_8.11+urwcyr1.0.7~pre44-4.1.diff.gz gsfonts_8.11+urwcyr1.0.7~pre44-4.1.dsc to main/g/gsfonts/gsfonts_8.11+urwcyr1.0.7~pre44-4.1.dsc gsfonts_8.11+urwcyr1.0.7~pre44-4.1_all.deb to main/g/gsfonts/gsfonts_8.11+urwcyr1.0.7~pre44-4.1_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oedi8-0002el...@ries.debian.org
Accepted dkimproxy 1.2-5 (source all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 19 May 2010 16:07:50 +0800
Source: dkimproxy
Binary: dkimproxy
Architecture: source all
Version: 1.2-5
Distribution: unstable
Urgency: low
Maintainer: Thomas Goirand tho...@goirand.fr
Changed-By: Thomas Goirand tho...@goirand.fr
Description:
dkimproxy - an SMTP-proxy that signs and/or verifies emails, using the Mail::
Closes: 525665
Changes:
dkimproxy (1.2-5) unstable; urgency=low
.
* v1.2-5: Now depends on the ssl-cert package.
* v1.2-5: Added the dkimproxy user to the ssl-cert group.
* v1.2-5: Using root:ssl-cert for the dkimproxy keys ownership
(Closes: #525665).
* v1.2-5: Symlink /var/lib/dkimproxy/private.key and
/etc/ssl/private/dkimproxy.key
* v1.2-5: Bumped Standard-Version
* v1.2-5: Now shipping only one version of the daemons manpage, as since the
upstream author generate its own it was shipped twice in dkimproxy 1.2-x.
* v1.2-4: Fixed the $DOMAIN part of the init.d script.
* v1.2-4: Corrected a typo in debian/defaults
* v1.2-4: Added --min_servers param description in the dkimproxy manpage.
* v1.2-4: Added DKIMPROXY_{IN,OUT}_MIN_SERVERS option in debian/defaults and
the init.d script now uses it. Default is set to 5, which is optimized for
a single core server, as discuss in upstream mailinglist.
Checksums-Sha1:
279a78f273e40411b07e7e3882066992c1c4374d 1110 dkimproxy_1.2-5.dsc
a54e9e4eae8ede4b00f01ef09731f25a10526818 11154 dkimproxy_1.2-5.diff.gz
aa30e427761afe9ca40b56cde5be4ad7a55a92a5 37142 dkimproxy_1.2-5_all.deb
Checksums-Sha256:
6165bea8462755474bac35060ee119c2e916873ec83c3e839a2eec2a534d 1110
dkimproxy_1.2-5.dsc
afe061eaa3521130dac3b6637cee500e81d3739649f4be4ff5fe0c4432310129 11154
dkimproxy_1.2-5.diff.gz
432ee925b0a8fd2f5e9eabf41321cef029254deabe55a0dca095893813a127ba 37142
dkimproxy_1.2-5_all.deb
Files:
b65bcb3f6081dca11e3a42e1c981e462 1110 mail optional dkimproxy_1.2-5.dsc
a3175f0605a0f7ccacd8442e683fa8bd 11154 mail optional dkimproxy_1.2-5.diff.gz
b86cdef1b7881b98b3cc4e7a7adcea49 37142 mail optional dkimproxy_1.2-5_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkvzrV4ACgkQl4M9yZjvmkkm+wCgyDD5F0T/segxysHCFqBj5XwB
7pcAoKUP+hawlLxC7Bev5QliqqacQG32
=9LaN
-END PGP SIGNATURE-
Accepted:
dkimproxy_1.2-5.diff.gz
to main/d/dkimproxy/dkimproxy_1.2-5.diff.gz
dkimproxy_1.2-5.dsc
to main/d/dkimproxy/dkimproxy_1.2-5.dsc
dkimproxy_1.2-5_all.deb
to main/d/dkimproxy/dkimproxy_1.2-5_all.deb
--
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1oefwd-0005ud...@ries.debian.org
Accepted lusernet.app 0.4.2-5 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Wed, 19 May 2010 10:42:03 +0300
Source: lusernet.app
Binary: lusernet.app
Architecture: source i386
Version: 0.4.2-5
Distribution: unstable
Urgency: low
Maintainer: Debian GNUstep maintainers
pkg-gnustep-maintain...@lists.alioth.debian.org
Changed-By: Yavor Doganov ya...@gnu.org
Description:
lusernet.app - News reader for GNUstep
Closes: 581956
Changes:
lusernet.app (0.4.2-5) unstable; urgency=low
.
* debian/patches/07_missing-includes.dpatch: Simplify a bit and fix
FTBFS with gnustep-base/1.20.0 (Closes: #581956).
* debian/compat: Set to 7.
* debian/control (Build-Depends): Bump debhelper accordingly. Remove
version requirement for libgnustep-gui-dev.
(Section): Change to `gnustep'.
(Depends): Add ${gnustep:Depends}.
(Description): Extend.
(Standards-Version): Compliant to 3.8.4 as of this release.
(Vcs-Arch): New field.
* debian/LuserNET.desktop: Set version to 1.0.
* debian/rules: Export GNUSTEP_MAKEFILES and remove gs_make usage.
(OBJCFLAGS): Do not define; use debug=yes conditionally.
(install): Replace dh_clean -k with dh_prep.
* debian/source/format:
* debian/README.source:
* debian/watch: New file.
Checksums-Sha1:
8ffa5400ce08851ddc97e8cfc5bb8aec5206ebd5 1282 lusernet.app_0.4.2-5.dsc
c7ba42e48ef20ea174d71459c5f268a3d0afc707 16233 lusernet.app_0.4.2-5.diff.gz
ab91f1cb8fa54958865029c5c199677e61489f0f 144940 lusernet.app_0.4.2-5_i386.deb
Checksums-Sha256:
de982d6d1587cb98a7337fea292c0dd7b9f73a3cab4633c4ee3256e3ef70a65f 1282
lusernet.app_0.4.2-5.dsc
a34e1a9692267889feeac50185a442e28dbb0ac220789d0c5968bd400263c3a1 16233
lusernet.app_0.4.2-5.diff.gz
3440b4119865b65c6008c37d9fec924afd91cfbeda753c9ce85d38785edd3921 144940
lusernet.app_0.4.2-5_i386.deb
Files:
a05176c0ee8dc41f93d82bbc02d6254e 1282 gnustep optional lusernet.app_0.4.2-5.dsc
0922c62a973a962f441fd11725265818 16233 gnustep optional
lusernet.app_0.4.2-5.diff.gz
6e29e4ee093b0119b9b521e029034354 144940 gnustep optional
lusernet.app_0.4.2-5_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkvzrJ4ACgkQnXjXEYa8KlAJtgCaAigXb78BmD8ZCWt41yDGCqtz
6p8An0WJ5fJHuq9C6a4ei31EdTaTicK+
=8Rff
-END PGP SIGNATURE-
Accepted:
lusernet.app_0.4.2-5.diff.gz
to main/l/lusernet.app/lusernet.app_0.4.2-5.diff.gz
lusernet.app_0.4.2-5.dsc
to main/l/lusernet.app/lusernet.app_0.4.2-5.dsc
lusernet.app_0.4.2-5_i386.deb
to main/l/lusernet.app/lusernet.app_0.4.2-5_i386.deb
--
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1oegif-0007lk...@ries.debian.org
Accepted postgis 1.5.1-2 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 May 2010 14:21:37 +0200 Source: postgis Binary: postgresql-8.4-postgis postgis libpostgis-java Architecture: source i386 all Version: 1.5.1-2 Distribution: unstable Urgency: low Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org Changed-By: Francesco Paolo Lovergine fran...@debian.org Description: libpostgis-java - geographic objects support for PostgreSQL -- JDBC support postgis- geographic objects support for PostgreSQL -- common files postgresql-8.4-postgis - geographic objects support for PostgreSQL 8.4 Changes: postgis (1.5.1-2) unstable; urgency=low . * Added generator.dpatch to avoid a buffer overflow on alpha due to a too narrow buffer apparently. Checksums-Sha1: bbc27fc393438ee91e58b6c23855510785ed2d1d 1538 postgis_1.5.1-2.dsc eb9efee761d6146951165047a655861c0dee8a5f 13852 postgis_1.5.1-2.diff.gz a97499808fcdd59429c146528bbce3d06b19555a 679854 postgresql-8.4-postgis_1.5.1-2_i386.deb a049dcb7e57bf855ac3b77b75c4b942401322938 491032 postgis_1.5.1-2_i386.deb e07d97898c80a6ef3e087782efa711f1714d3615 371970 libpostgis-java_1.5.1-2_all.deb Checksums-Sha256: 9e77483df9dd51c3ce10fed58d9d1dafdcc6e5f13737a0bae9c74b4647467c1e 1538 postgis_1.5.1-2.dsc 0a1ff958f4d7cce607fc2a6faa2b9f6a156b9bf7b706f061c195d98d13b51d61 13852 postgis_1.5.1-2.diff.gz 96764d5b37594fd1da43c839cac0c47709840c2471a54e8426e32459c6713bf0 679854 postgresql-8.4-postgis_1.5.1-2_i386.deb 928161fb3a849862afbb29eb928d80ae6be194f590878a497e4e2ab59ba73926 491032 postgis_1.5.1-2_i386.deb 1fd9a2ac794ed8a24fc4f1ea165122c4a38b8656d3197ba00239afb16c3f0dbf 371970 libpostgis-java_1.5.1-2_all.deb Files: 309bec23a46d9ffe74d5f50cb11ecef7 1538 misc optional postgis_1.5.1-2.dsc 996279ea285c467db3d66f3966ebf52f 13852 misc optional postgis_1.5.1-2.diff.gz 5038830d417e4a929eb3d7e9edf2e81b 679854 misc optional postgresql-8.4-postgis_1.5.1-2_i386.deb 21eeaf6360ddd2d2ed51998ab585d862 491032 misc optional postgis_1.5.1-2_i386.deb 459589de602903c5eebc41c97e1d9a3c 371970 science optional libpostgis-java_1.5.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvzpZ4ACgkQpFNRmenyx0cI+gCg591bS5P2Ze8m8mpKexlB7ugw kGMAoK1c4kZS1i4931F4fnhE6RV/9Wca =pz33 -END PGP SIGNATURE- Accepted: libpostgis-java_1.5.1-2_all.deb to main/p/postgis/libpostgis-java_1.5.1-2_all.deb postgis_1.5.1-2.diff.gz to main/p/postgis/postgis_1.5.1-2.diff.gz postgis_1.5.1-2.dsc to main/p/postgis/postgis_1.5.1-2.dsc postgis_1.5.1-2_i386.deb to main/p/postgis/postgis_1.5.1-2_i386.deb postgresql-8.4-postgis_1.5.1-2_i386.deb to main/p/postgis/postgresql-8.4-postgis_1.5.1-2_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oegvr-56...@ries.debian.org
Accepted preview.app 0.8.5-8 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 18 May 2010 18:56:43 +0200 Source: preview.app Binary: preview.app Architecture: source i386 Version: 0.8.5-8 Distribution: unstable Urgency: low Maintainer: Federico Gimenez Nieto fgime...@coit.es Changed-By: Federico Gimenez Nieto fgime...@coit.es Description: preview.app - General purpose image viewer for GNUstep Closes: 581970 581971 Changes: preview.app (0.8.5-8) unstable; urgency=low . * Added debian/patches/compilation-errors.patch: Fix FTBFS with gnustep-gui/0.18.0 (Closes: #581970) * debian/rules: noopt modifications to work with gnustep-make/2.4.x (Closes: #581971) * debian/control: bumped Standards-Version: 3.8.4 (no changes needed) Checksums-Sha1: d5aa15133a265731f5eb6ad51260e62f0cf4185b 1081 preview.app_0.8.5-8.dsc 021fdd2f7038e36d9fb385c260315ea2c53a7c5d 5146 preview.app_0.8.5-8.debian.tar.gz 231ffa50b072fd5d9bef23ff5f231fdf4a9cc191 81408 preview.app_0.8.5-8_i386.deb Checksums-Sha256: 9a70122de01a726814ee76067d7641e8ede5af6632a692f6a00ff51e6407acca 1081 preview.app_0.8.5-8.dsc fc539ea26b176255c778e587387aa3785c6aebdc5acf3323912a17940a1f4aa6 5146 preview.app_0.8.5-8.debian.tar.gz 88cbd0d973ac9e72a0e7322283116abef327114f8728ff22fd3ce9a9725f396b 81408 preview.app_0.8.5-8_i386.deb Files: 4ce181d53ecf2e0d15eab00d565430a9 1081 gnustep optional preview.app_0.8.5-8.dsc 9bb8f3dacaeb15000389c8c52179f1a0 5146 gnustep optional preview.app_0.8.5-8.debian.tar.gz 84fa9dc52baaa4c6ea8502d331c6c41e 81408 gnustep optional preview.app_0.8.5-8_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvzrKQACgkQnXjXEYa8KlClbQCfXOgZN2K1yu8Vd5WOQusShUKc sc8AoIEkVQciomFUDfeRJ34o2Ru04Pud =n173 -END PGP SIGNATURE- Accepted: preview.app_0.8.5-8.debian.tar.gz to main/p/preview.app/preview.app_0.8.5-8.debian.tar.gz preview.app_0.8.5-8.dsc to main/p/preview.app/preview.app_0.8.5-8.dsc preview.app_0.8.5-8_i386.deb to main/p/preview.app/preview.app_0.8.5-8_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oegwb-bc...@ries.debian.org
Accepted libpam-mklocaluser 0.1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 May 2010 19:54:09 +0200 Source: libpam-mklocaluser Binary: libpam-mklocaluser Architecture: source all Version: 0.1 Distribution: unstable Urgency: low Maintainer: Debian Edu Developers debian-...@lists.debian.org Changed-By: Petter Reinholdtsen p...@debian.org Description: libpam-mklocaluser - Configure PAM to create a local user if it do not exist already Changes: libpam-mklocaluser (0.1) unstable; urgency=low . * Initial release. Checksums-Sha1: 9918cac6836f77a9ab7b80f42782986ac115cb20 995 libpam-mklocaluser_0.1.dsc 0acdac05024fdb03a5f078066f4baae4b5449c51 4143 libpam-mklocaluser_0.1.tar.gz 573354b19eb2a4e5a6cb631652cdd8cab765e549 4500 libpam-mklocaluser_0.1_all.deb Checksums-Sha256: 57877609865b117edfa2f21059c652cbc8a6b905945d8fea4e93e186f0657115 995 libpam-mklocaluser_0.1.dsc d3c46a4a13e8200b458f0594b34c2446c32f3db6a3616fc46f0a2c0dbb22e9a2 4143 libpam-mklocaluser_0.1.tar.gz d820dc1aaa5a3a1cff6bb292734152b7892de73c28dda80af488058bbe4ee36a 4500 libpam-mklocaluser_0.1_all.deb Files: fa1f836130edc437feb3c43442fed5ff 995 misc optional libpam-mklocaluser_0.1.dsc b118dc17c1252165ce357f3a1d2ffa81 4143 misc optional libpam-mklocaluser_0.1.tar.gz 868d4ec11067f72991f3e6bf567002ce 4500 misc optional libpam-mklocaluser_0.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFL8YLq20zMSyow1ykRAiTxAJ9rIu9wTrYt0dF+FVJpb/FBwwEGVgCfWWbu aDqHq6LmbIkz0sA0tXiKyTY= =Fe0v -END PGP SIGNATURE- Accepted: libpam-mklocaluser_0.1.dsc to main/libp/libpam-mklocaluser/libpam-mklocaluser_0.1.dsc libpam-mklocaluser_0.1.tar.gz to main/libp/libpam-mklocaluser/libpam-mklocaluser_0.1.tar.gz libpam-mklocaluser_0.1_all.deb to main/libp/libpam-mklocaluser/libpam-mklocaluser_0.1_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oeh2n-0003fo...@ries.debian.org
Accepted libpam-mklocaluser 0.2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 19 May 2010 11:08:19 +0200 Source: libpam-mklocaluser Binary: libpam-mklocaluser Architecture: source all Version: 0.2 Distribution: unstable Urgency: low Maintainer: Debian Edu Developers debian-...@lists.debian.org Changed-By: Petter Reinholdtsen p...@debian.org Description: libpam-mklocaluser - Configure PAM to create a local user if it do not exist already Changes: libpam-mklocaluser (0.2) unstable; urgency=low . * Correct typo in pam-configs entry causing the PAM module to fail. Checksums-Sha1: b4164c7e4d9ecb545c0adda3107979ee9cf22a1b 995 libpam-mklocaluser_0.2.dsc fec4f7cae92e491a7d80610c96f9a639ed78b3cc 4188 libpam-mklocaluser_0.2.tar.gz 1f1c0ee787dc107a6b48812b2e559dc43bae635d 4590 libpam-mklocaluser_0.2_all.deb Checksums-Sha256: 29a12603bb1bd0cf500d6fb339be0027f9e37a6475c3124103a8228e60ae20b1 995 libpam-mklocaluser_0.2.dsc 57b9515a3571e1be0b0451686677f28410510a27433ed0f5fba754ad9170204e 4188 libpam-mklocaluser_0.2.tar.gz 75e24a4780bf28d3e8621e161d2a9e2522fa865556f759d6e96449a52749df30 4590 libpam-mklocaluser_0.2_all.deb Files: c656bdc621569513b1b4597f4009dc73 995 misc optional libpam-mklocaluser_0.2.dsc a5600a49c00f3808c7877d2b3985d4d8 4188 misc optional libpam-mklocaluser_0.2.tar.gz f75a36d0a2d58f793307534dd1b7d6cf 4590 misc optional libpam-mklocaluser_0.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFL86s620zMSyow1ykRAjM0AJsG9jO+kHxRNdirOJxZ8flUHcWRwgCeJOHp 6WehU4X8yPQjKLqaZcY1yIk= =FyKp -END PGP SIGNATURE- Accepted: libpam-mklocaluser_0.2.dsc to main/libp/libpam-mklocaluser/libpam-mklocaluser_0.2.dsc libpam-mklocaluser_0.2.tar.gz to main/libp/libpam-mklocaluser/libpam-mklocaluser_0.2.tar.gz libpam-mklocaluser_0.2_all.deb to main/libp/libpam-mklocaluser/libpam-mklocaluser_0.2_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oeh2f-0003k2...@ries.debian.org
Accepted libpam-script 1.1.3-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 16 May 2010 13:43:26 +0200 Source: libpam-script Binary: libpam-script Architecture: source i386 Version: 1.1.3-1 Distribution: unstable Urgency: low Maintainer: Martijn van Brummelen mart...@brumit.nl Changed-By: Martijn van Brummelen mart...@brumit.nl Description: libpam-script - Pam module which allows executing a script Closes: 484289 Changes: libpam-script (1.1.3-1) unstable; urgency=low . * Initial release (Closes: #484289). * Added man-page patch to fix lintian warning. * Added README.Debian. Checksums-Sha1: 7309c7acd1dca512eb4d6e2491d8dbbc98a0dc2f 1801 libpam-script_1.1.3-1.dsc 28152acc12aa44be4f9415d70b2ac0beeae744af 432515 libpam-script_1.1.3.orig.tar.gz 07b739ea06110cbd3e7204d81d024c768e80d6df 3370 libpam-script_1.1.3-1.debian.tar.gz 74161a2789cb8082b681dae483bd465f3943c8b7 20018 libpam-script_1.1.3-1_i386.deb Checksums-Sha256: 8626fa435baf46fadfbaa4b33548a2f559f13a1dceaee7d899a62168f56b36e3 1801 libpam-script_1.1.3-1.dsc 0bc00e3981d1aaf7d3e9acef6f301645d1f46f9bab07d71b7b65ec54cac74a29 432515 libpam-script_1.1.3.orig.tar.gz cd73418de445859bc2684ca83008d439a816547f9f59f98d354c8c23752d7ccd 3370 libpam-script_1.1.3-1.debian.tar.gz 0ac8b4353a0599ed34d64425db49a8ca341b4e798c04657ec8e687053ce88ffb 20018 libpam-script_1.1.3-1_i386.deb Files: fb4fb795805be583102f0e6e41f873b3 1801 admin extra libpam-script_1.1.3-1.dsc 0335de4b4475b15f2ed2521c761ed718 432515 admin extra libpam-script_1.1.3.orig.tar.gz 4a0919c237babb19bbcf5989266aba40 3370 admin extra libpam-script_1.1.3-1.debian.tar.gz b4742dfcf5f062cf8b40b0442bd8904d 20018 admin extra libpam-script_1.1.3-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCgAGBQJL8AZcAAoJEKv/7bJACMb5VecQAJz3OVFopKyXtH3kKAuH8YFa djsaCu0vxcqS8FVI28rfBPhyVrSUD6znf24vSLh0v0o4vJO+54hMv09mrBT5X7C4 bbLpR5L5LsNKVd90NAst7ZIMGyo2iabmIi/cT8DFSvYCfr9cWKKtyyvUh0GeeHj4 WigpXQiCRrbR/4JB16Hwoae2oCbg0XgK7m0wIi0hkLMgmaezFkmODF3a75yn1GUe SnABJyJ3dLZlkl/h6NEaS4Kk1FCtHBJ0oyLve7ImIzsR45/BJI6EzGoZWAJ93HvC n+2KWFRQKYcQI3YZJ299vFc/ZmCXZChRdwbi4MHaUHo36l/QbPVY11huKeqW4/bK JS6mPY8GCQLAl59zX8uMceol4ygvHGgR8NU+fSAOizAIW0g9teZo6IAIrMIE0Z5D oI8v66OuSb2zZ7edarcxaD2a/4E009+QDtNPRiCM7tAA48fyeO5w+ItR9NUM2j1k k9VVIrmV2df7nCRlpgVrmpnpDl8ZjCzqdWXev3qHNlqxPW7Y90DN9wlto3U4YvXT eRFEWJpmSdlA1Sc1UUEzAA3UlWh/OnMTt5ldAHeR4xlm1yyp20gY1sSoXl3U1W58 0rPufG+kgD4aXiayMXj7Zl4N+OgBgoEDrQ2qwwh+LsXwxgpF4ngIUH9bfxwufcI+ dJ2lTfIqTbFHNxen1VXz =494m -END PGP SIGNATURE- Accepted: libpam-script_1.1.3-1.debian.tar.gz to main/libp/libpam-script/libpam-script_1.1.3-1.debian.tar.gz libpam-script_1.1.3-1.dsc to main/libp/libpam-script/libpam-script_1.1.3-1.dsc libpam-script_1.1.3-1_i386.deb to main/libp/libpam-script/libpam-script_1.1.3-1_i386.deb libpam-script_1.1.3.orig.tar.gz to main/libp/libpam-script/libpam-script_1.1.3.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oeh2z-0003mq...@ries.debian.org
Accepted xen 4.0.0-1~experimental.1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 06 May 2010 15:47:38 +0200 Source: xen Binary: xen-docs-4.0 libxenstore3.0 libxen-dev xenstore-utils xen-utils-4.0 xen-hypervisor-4.0-amd64 xen-hypervisor-4.0-i386 Architecture: source all amd64 Version: 4.0.0-1~experimental.1 Distribution: experimental Urgency: low Maintainer: Debian Xen Team pkg-xen-de...@lists.alioth.debian.org Changed-By: Bastian Blank wa...@debian.org Description: libxen-dev - Public headers and libs for Xen libxenstore3.0 - Xenstore communications library for Xen xen-docs-4.0 - Documentation for Xen xen-hypervisor-4.0-amd64 - The Xen Hypervisor on AMD64 xen-hypervisor-4.0-i386 - The Xen Hypervisor on i386 xen-utils-4.0 - XEN administrative tools xenstore-utils - Xenstore utilities for Xen Changes: xen (4.0.0-1~experimental.1) experimental; urgency=low . * New upstream version. * Rename source package to xen. * Build depend against iasl and uuid-dev. * Disable blktap2 support, it links against OpenSSL. * Update copyright file. Checksums-Sha1: 9ae6931af82a458c52f9bc6c9959a06c4c53 1593 xen_4.0.0-1~experimental.1.dsc aadfa4bda44c00be6ac8e5c10a2bd1003c04f042 9130396 xen_4.0.0.orig.tar.gz 823827f850009cbf79fb5d1c29538ceae403b800 32317 xen_4.0.0-1~experimental.1.debian.tar.gz 94bbe6dc538ccdcacfcd7bf3bb547df92f928484 1314146 xen-docs-4.0_4.0.0-1~experimental.1_all.deb dd0cbb71b66c468c4a15983ec2502da07948a980 675872 xen-hypervisor-4.0-amd64_4.0.0-1~experimental.1_amd64.deb 4214ec616d678ffe964895c6e9537a2cedbbda99 267426 libxen-dev_4.0.0-1~experimental.1_amd64.deb e7dce913c3395055ea52a12802f54f5f20381b12 19832 libxenstore3.0_4.0.0-1~experimental.1_amd64.deb fcd839f568e6012b1d64b515738f5e49abcbfce9 1169330 xen-utils-4.0_4.0.0-1~experimental.1_amd64.deb 09b3ecdb4702dacc57ac106f70e3a14778beecdd 17378 xenstore-utils_4.0.0-1~experimental.1_amd64.deb Checksums-Sha256: de80f3807014072183e695977f703d20be0ab419d85ead5f089eb6c44ee1e4c9 1593 xen_4.0.0-1~experimental.1.dsc 90e2a145902959e3631bf88567413cc1732fce388992610a3d85cb6e96996ff1 9130396 xen_4.0.0.orig.tar.gz 94dc867eeb8efc01408af206ad13cce316db405611771856fe2b7bfc9f49744e 32317 xen_4.0.0-1~experimental.1.debian.tar.gz b6908a6175febca7db35b8ec1e1070c733525a786bfa2652de000285bea23009 1314146 xen-docs-4.0_4.0.0-1~experimental.1_all.deb 898ddae7e97d808948c45a52804b9260b6aa0af54dd99d6b299b0b793180940c 675872 xen-hypervisor-4.0-amd64_4.0.0-1~experimental.1_amd64.deb e650aa95f702b57024ad4834e7d02450df13589ef70fbae71f3067ef84bb53e5 267426 libxen-dev_4.0.0-1~experimental.1_amd64.deb 942ad41529820d7ea5342cdd69bf1abcf06ac64897004b6adab0ad2b1827c5d2 19832 libxenstore3.0_4.0.0-1~experimental.1_amd64.deb 9cdba0bf5a658546c969234896af3872bed4f76ae49f669ea0312854bb90f59e 1169330 xen-utils-4.0_4.0.0-1~experimental.1_amd64.deb ec972b983aa51d8857483296a61fe1914ae84f4c0c1f8140e06251dad9f7fdf8 17378 xenstore-utils_4.0.0-1~experimental.1_amd64.deb Files: 8a15c263edb5211470d450a3d0d75715 1593 kernel optional xen_4.0.0-1~experimental.1.dsc d9afa7a97498c4eba710fd36fd548392 9130396 kernel optional xen_4.0.0.orig.tar.gz b8e011ecf8f3139cdc6c788e4b180cb7 32317 kernel optional xen_4.0.0-1~experimental.1.debian.tar.gz 89fac5d2b9206b8ed19a049c9a24c1ae 1314146 doc optional xen-docs-4.0_4.0.0-1~experimental.1_all.deb 20c629501d078e931c3d02528fb5009f 675872 kernel optional xen-hypervisor-4.0-amd64_4.0.0-1~experimental.1_amd64.deb d4f67d16c3c253250efc318c66ffb6ac 267426 libdevel optional libxen-dev_4.0.0-1~experimental.1_amd64.deb 9affa286d1398bc9477aaf328794b532 19832 libs optional libxenstore3.0_4.0.0-1~experimental.1_amd64.deb e6e8e2bcafbb3c62f109975405c7fcd2 1169330 kernel optional xen-utils-4.0_4.0.0-1~experimental.1_amd64.deb 3feec58c41b5b54a44768ab967c204df 17378 admin optional xenstore-utils_4.0.0-1~experimental.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkviy4UACgkQLkAIIn9ODhGqWwCfR4UVcqag6ifa9RIUE7sozAEf uqkAoKaCMlgaC9oziC3Hy1J0r2ag0kDR =OPes -END PGP SIGNATURE- Accepted: libxen-dev_4.0.0-1~experimental.1_amd64.deb to main/x/xen/libxen-dev_4.0.0-1~experimental.1_amd64.deb libxenstore3.0_4.0.0-1~experimental.1_amd64.deb to main/x/xen/libxenstore3.0_4.0.0-1~experimental.1_amd64.deb xen-docs-4.0_4.0.0-1~experimental.1_all.deb to main/x/xen/xen-docs-4.0_4.0.0-1~experimental.1_all.deb xen-hypervisor-4.0-amd64_4.0.0-1~experimental.1_amd64.deb to main/x/xen/xen-hypervisor-4.0-amd64_4.0.0-1~experimental.1_amd64.deb xen-utils-4.0_4.0.0-1~experimental.1_amd64.deb to main/x/xen/xen-utils-4.0_4.0.0-1~experimental.1_amd64.deb xen_4.0.0-1~experimental.1.debian.tar.gz to main/x/xen/xen_4.0.0-1~experimental.1.debian.tar.gz xen_4.0.0-1~experimental.1.dsc to main/x/xen/xen_4.0.0-1~experimental.1.dsc xen_4.0.0.orig.tar.gz to main/x/xen/xen_4.0.0.orig.tar.gz xenstore-utils_4.0.0-1~experimental.1_amd64.deb to main/x/xen/xenstore-utils_4.0.0-1~experimental.1_amd64.deb
Accepted cricket 1.0.5-12 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 19 May 2010 12:18:41 +0200 Source: cricket Binary: cricket Architecture: source all Version: 1.0.5-12 Distribution: unstable Urgency: low Maintainer: Christian Marillat maril...@debian.org Changed-By: Christian Marillat maril...@debian.org Description: cricket- Program for collection and display of time-series data Closes: 171410 176957 581949 Changes: cricket (1.0.5-12) unstable; urgency=low . * touch /etc/cricket/config/Defaults in the postinst this seems to fix this bug. Thanks to Arnaud de Bossoreille de Ribou (Closes: #171410). * Remove perl-suid dependency (Closes: #581949). * Document in manpage that cricket-compile don't need command line options (Closes: #176957). Checksums-Sha1: 5d51870fc3e3c2311d1511619e403ecb19b10c14 955 cricket_1.0.5-12.dsc def7a0a49b43c24bb908ef40d0060c45c9c76be4 21610 cricket_1.0.5-12.diff.gz b0e15d19bab0b9035116f3638ea1caf7bb42b4fa 389780 cricket_1.0.5-12_all.deb Checksums-Sha256: 106ec4335ec17751581c8e985f4f9ad39687d7e48ac68f97fd31f0644fc12524 955 cricket_1.0.5-12.dsc c4d67703c673829b507639eefe950bf482cbe8f0c66138859e8cdf9c216313bc 21610 cricket_1.0.5-12.diff.gz dcd0d89e52954aa15edf489ecb963a007af296bc42565a8f60c4ba0738aed16f 389780 cricket_1.0.5-12_all.deb Files: e966ce1af89c1ee1143b188835435c46 955 net extra cricket_1.0.5-12.dsc e6efe487a8984aaf64ee18fb640c9624 21610 net extra cricket_1.0.5-12.diff.gz 91d43c742bd0610669e75ca3070aa254 389780 net extra cricket_1.0.5-12_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFL872vB9xWPR9BuQcRAoyZAJ4pMmTyKpkNdNVegZxgxnMfverM+QCffMGb vI7l8MFE5QfzL5d7wGZ8fpk= =32kQ -END PGP SIGNATURE- Accepted: cricket_1.0.5-12.diff.gz to main/c/cricket/cricket_1.0.5-12.diff.gz cricket_1.0.5-12.dsc to main/c/cricket/cricket_1.0.5-12.dsc cricket_1.0.5-12_all.deb to main/c/cricket/cricket_1.0.5-12_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oeh45-0004kf...@ries.debian.org
Accepted cssutils 0.9.6-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 18 May 2010 17:13:01 +0200 Source: cssutils Binary: python-cssutils python-cssutils-doc python-encutils Architecture: source all Version: 0.9.6-1 Distribution: unstable Urgency: low Maintainer: Debian Python Modules Team python-modules-t...@lists.alioth.debian.org Changed-By: Loïc Minier l...@debian.org Description: python-cssutils - CSS Cascading Style Sheets parser and builder python-cssutils-doc - CSS Cascading Style Sheets parser and builder - API documentation python-encutils - Encoding detection collection for Python Changes: cssutils (0.9.6-1) unstable; urgency=low . * Bump up Standards-Version to 3.8.4. * Use my @debian.org address in control. * Merge new upstream release from Ubuntu. Checksums-Sha1: df3f509ded1b3acea3cbe3ffc339c2a951c19203 1266 cssutils_0.9.6-1.dsc d7cc67f1fc7640a1d0d33152859f2842e8b9054e 428334 cssutils_0.9.6.orig.tar.gz 1fd2db7724311fc46cf9f20d7843dba4c87c111a 3003 cssutils_0.9.6-1.diff.gz 2b252bdd84f2c3cbb0eb81fe982dec56d6191c3e 160942 python-cssutils_0.9.6-1_all.deb 8d13d2e13309e710f8b8107c6aad1a471eda723c 183852 python-cssutils-doc_0.9.6-1_all.deb 4d501ff1e885cc966d0d8bae1f526a3f87a5dd27 45024 python-encutils_0.9.6-1_all.deb Checksums-Sha256: 07d59b07deae36b8e662a14b93f53891c329408e1b0e2b58bec1285c8c03eeb4 1266 cssutils_0.9.6-1.dsc c43b85f59958cb75a601bea26cf5152b81ac515e7d3eca3ea35727feeb19031f 428334 cssutils_0.9.6.orig.tar.gz ec0513e3f9a80191a003c381709ec859520bac44fba7072a52f6237090ba153b 3003 cssutils_0.9.6-1.diff.gz 575e2c14669a2cb117efe0895ea103780748edab5b4ab0e58c0b02ac0437d0e0 160942 python-cssutils_0.9.6-1_all.deb 4673163bfd25676a4076defe3e5596e21cd9a9ba5e904fb4604eb26eb429afc9 183852 python-cssutils-doc_0.9.6-1_all.deb f9cc09675c8962e0c227ab0228a4dd2b5c1107b01e508b6e4e74c8b482f8b4c4 45024 python-encutils_0.9.6-1_all.deb Files: bd129b7e96fe60fa82c9f4978d21c99c 1266 python optional cssutils_0.9.6-1.dsc 1073891225ee20c6ee466a4f3b2458ba 428334 python optional cssutils_0.9.6.orig.tar.gz 5711b9d30e4da4273902b04acb656c7e 3003 python optional cssutils_0.9.6-1.diff.gz c26e05853cefbc2089c57e7297513425 160942 python optional python-cssutils_0.9.6-1_all.deb e97144cef21ce066953ae107c29c9119 183852 doc optional python-cssutils-doc_0.9.6-1_all.deb 690209223b6c3434037b9554963803fb 45024 python optional python-encutils_0.9.6-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvzxNQACgkQ4VUX8isJIMDlNQCgjxcXPwvZTXvTN2R/uedbUWhR peMAoKe7BJE4Y4jMcInd8hqF36IzNZ2m =Xb1+ -END PGP SIGNATURE- Accepted: cssutils_0.9.6-1.diff.gz to main/c/cssutils/cssutils_0.9.6-1.diff.gz cssutils_0.9.6-1.dsc to main/c/cssutils/cssutils_0.9.6-1.dsc cssutils_0.9.6.orig.tar.gz to main/c/cssutils/cssutils_0.9.6.orig.tar.gz python-cssutils-doc_0.9.6-1_all.deb to main/c/cssutils/python-cssutils-doc_0.9.6-1_all.deb python-cssutils_0.9.6-1_all.deb to main/c/cssutils/python-cssutils_0.9.6-1_all.deb python-encutils_0.9.6-1_all.deb to main/c/cssutils/python-encutils_0.9.6-1_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oeh4q-0004oq...@ries.debian.org
Accepted ggcov 0.8.2-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 19 May 2010 10:11:49 +0100 Source: ggcov Binary: ggcov Architecture: source i386 Version: 0.8.2-1 Distribution: unstable Urgency: low Maintainer: Alastair McKinstry mckins...@debian.org Changed-By: Alastair McKinstry mckins...@debian.org Description: ggcov - Graphical tool for displaying gcov test coverage data Closes: 581477 Changes: ggcov (0.8.2-1) unstable; urgency=low . * New upstream release. Obsolete patches: gcc44_fixes.patch, compile_fixes.patch, ignore_tests.patch * Remove bashisms from debian/rules. Closes: #581477. * Standards-Version: 3.8.4; no changes required. Checksums-Sha1: a7dca2dfa89300c8791dc3daf9c170b2c3cb54b3 1107 ggcov_0.8.2-1.dsc 912e6f162072f22cfddcde0c43db04949e68ef64 450569 ggcov_0.8.2.orig.tar.gz 35c1d3dc21fabee274e8daa058106bf681923e13 15349 ggcov_0.8.2-1.debian.tar.gz cbbd1b6413df5b7fbbb16b3f7a48ea6705523c5e 281230 ggcov_0.8.2-1_i386.deb Checksums-Sha256: 0ce7d66ec00158bdb6c0cb40a7c9fc63381135ff51451d5473b92701b1e760b2 1107 ggcov_0.8.2-1.dsc 8fcd011db6ea3f461d26edd0bec1e8daf1e7ea731dd8080bce043a6b15f07c3e 450569 ggcov_0.8.2.orig.tar.gz bed20df2ab4ca5f41d350e0f493b81a0b213893fe7f5ee0496896190b50639d5 15349 ggcov_0.8.2-1.debian.tar.gz 4dd53864f1494041585b3ade3f78493dfbf10ca9abfdf6c562e3cdba3e98cd4e 281230 ggcov_0.8.2-1_i386.deb Files: 62b6654b8bb283a02a6647043ad7b617 1107 devel optional ggcov_0.8.2-1.dsc bac5b117b6901160810e239373d6ee0a 450569 devel optional ggcov_0.8.2.orig.tar.gz ffc02770b608e376e3a2993dce7f4b12 15349 devel optional ggcov_0.8.2-1.debian.tar.gz eb6de4454fdbae64bbb19af04ba02e19 281230 devel optional ggcov_0.8.2-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFL88AAQTK/kCo4XFcRAsJ1AJ9FAgLWooHGudKAMIYWOmDVqFZHOwCgnP5i zAT5q+u4CE7h0ee83UvnxXI= =HjtH -END PGP SIGNATURE- Accepted: ggcov_0.8.2-1.debian.tar.gz to main/g/ggcov/ggcov_0.8.2-1.debian.tar.gz ggcov_0.8.2-1.dsc to main/g/ggcov/ggcov_0.8.2-1.dsc ggcov_0.8.2-1_i386.deb to main/g/ggcov/ggcov_0.8.2-1_i386.deb ggcov_0.8.2.orig.tar.gz to main/g/ggcov/ggcov_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 Archive: http://lists.debian.org/e1oeh5y-0004zl...@ries.debian.org
Accepted sibyl-installer 1.17 (source mipsel)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 09 May 2010 22:47:02 +0200 Source: sibyl-installer Binary: sibyl-installer Architecture: source mipsel Version: 1.17 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-b...@lists.debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: sibyl-installer - Install the SiByl boot loader on your disk (udeb) Changes: sibyl-installer (1.17) unstable; urgency=low . [ Aurelien Jarno ] * Add myself to uploaders. * Upgrade to debhelper v7. * Bump Standard-Versions to 3.8.4. Checksums-Sha1: b49b733fa783727e4655d8e5a69c0ca43ae1b49b 900 sibyl-installer_1.17.dsc 73fe6ee2626192fc27ccecbf798cb16fa05a9f8a 37115 sibyl-installer_1.17.tar.gz 39e488724bb67f1acc5c6e8be9e49894ba88871a 17578 sibyl-installer_1.17_mipsel.udeb Checksums-Sha256: 8fb4f952f3cc557a6d91e61f2363f8840f8bf5b844eaf3dd929f112207d8db2a 900 sibyl-installer_1.17.dsc 6faf071f5afbf619840fc8c254180a244ebe68daa57ce6b99b8a1ece23e1c3e3 37115 sibyl-installer_1.17.tar.gz b7e30d5a6b5f79bda60317082dc4d6f20166768e058f3829b1033ef4dc3d9d80 17578 sibyl-installer_1.17_mipsel.udeb Files: 3a9d6be6eecadcec84a5ab9aba818918 900 debian-installer standard sibyl-installer_1.17.dsc 5ed861be393e78b72dc3ef9d411097de 37115 debian-installer standard sibyl-installer_1.17.tar.gz 9f6501c92f8a94401c93f639691196dc 17578 debian-installer standard sibyl-installer_1.17_mipsel.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFL5x/dw3ao2vG823MRAunwAJ47RwaudI/n/tz+HCyPbxGjv9dSvgCeOzw6 jY9jN0vOtfaOBC+9fPefflA= =wT71 -END PGP SIGNATURE- Accepted: sibyl-installer_1.17.dsc to main/s/sibyl-installer/sibyl-installer_1.17.dsc sibyl-installer_1.17.tar.gz to main/s/sibyl-installer/sibyl-installer_1.17.tar.gz sibyl-installer_1.17_mipsel.udeb to main/s/sibyl-installer/sibyl-installer_1.17_mipsel.udeb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oehgt-0005lw...@ries.debian.org
Accepted nusoap 0.9.5-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 27 Apr 2010 10:26:09 +0200 Source: nusoap Binary: libnusoap-php Architecture: source all Version: 0.9.5-1 Distribution: experimental Urgency: low Maintainer: Olivier Berger olivier.ber...@it-sudparis.eu Changed-By: Olivier Berger olivier.ber...@it-sudparis.eu Description: libnusoap-php - SOAP toolkit for PHP Changes: nusoap (0.9.5-1) experimental; urgency=low . * New upstream version. Should fix PHP 5.3 deprecation warning issues. Checksums-Sha1: 059c19875a254e0db3565c95ed268fba09c810eb 1021 nusoap_0.9.5-1.dsc ee3974b403341b2d74cc4805095f0d42d0920c55 158416 nusoap_0.9.5.orig.tar.gz 0d26ce110b1bf869c63981b5f6838ffb7e24405d 3455 nusoap_0.9.5-1.debian.tar.gz 7d1210a5a27bf6b80aecc77ff265642c165b4790 95202 libnusoap-php_0.9.5-1_all.deb Checksums-Sha256: fc194a03c404bf3e7cfb2d4957bfcfd6829b094f9c980ad9632b3cc7809c1b66 1021 nusoap_0.9.5-1.dsc c37a8b1bc0cb87fc4b41fb2e69b3fa87df39bf8a444c372c22277e939f6f6505 158416 nusoap_0.9.5.orig.tar.gz fc4e393d8cec96d84af25cc1a2e7627bbb63040b8ff173fd9c9ead1d18623108 3455 nusoap_0.9.5-1.debian.tar.gz 5928362946b80e51b7cbf692fac2f531a301c14e7506ef12f495d9ba9a41ada5 95202 libnusoap-php_0.9.5-1_all.deb Files: 37337bb5349cd14644b1743e91033fc1 1021 php optional nusoap_0.9.5-1.dsc 56ec9d6ad7df3a0696b3041f6801edb8 158416 php optional nusoap_0.9.5.orig.tar.gz 4e5a9e6e7dc3be4720d446fbdb0ce497 3455 php optional nusoap_0.9.5-1.debian.tar.gz d40d3ee8f877c37b7551657591f8489b 95202 php optional libnusoap-php_0.9.5-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkvzxqIACgkQTx4JB6685x+cHQCgrH7wUolvoMw6YOL4bhuTrXmu RpgAnRj7vzLrBSKODGgrZ7XnjJe+UeNs =oXAr -END PGP SIGNATURE- Accepted: libnusoap-php_0.9.5-1_all.deb to main/n/nusoap/libnusoap-php_0.9.5-1_all.deb nusoap_0.9.5-1.debian.tar.gz to main/n/nusoap/nusoap_0.9.5-1.debian.tar.gz nusoap_0.9.5-1.dsc to main/n/nusoap/nusoap_0.9.5-1.dsc nusoap_0.9.5.orig.tar.gz to main/n/nusoap/nusoap_0.9.5.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oehky-0005j5...@ries.debian.org
Accepted linux-kernel-di-mipsel-2.6 1.18 (source mipsel)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 11 May 2010 19:49:14 +0200 Source: linux-kernel-di-mipsel-2.6 Binary: kernel-image-2.6.32-3-sb1-bcm91250a-di nic-shared-modules-2.6.32-3-sb1-bcm91250a-di ppp-modules-2.6.32-3-sb1-bcm91250a-di cdrom-core-modules-2.6.32-3-sb1-bcm91250a-di scsi-core-modules-2.6.32-3-sb1-bcm91250a-di scsi-modules-2.6.32-3-sb1-bcm91250a-di scsi-common-modules-2.6.32-3-sb1-bcm91250a-di loop-modules-2.6.32-3-sb1-bcm91250a-di ipv6-modules-2.6.32-3-sb1-bcm91250a-di nls-core-modules-2.6.32-3-sb1-bcm91250a-di ext4-modules-2.6.32-3-sb1-bcm91250a-di isofs-modules-2.6.32-3-sb1-bcm91250a-di jfs-modules-2.6.32-3-sb1-bcm91250a-di reiserfs-modules-2.6.32-3-sb1-bcm91250a-di xfs-modules-2.6.32-3-sb1-bcm91250a-di fat-modules-2.6.32-3-sb1-bcm91250a-di md-modules-2.6.32-3-sb1-bcm91250a-di multipath-modules-2.6.32-3-sb1-bcm91250a-di usb-modules-2.6.32-3-sb1-bcm91250a-di usb-storage-modules-2.6.32-3-sb1-bcm91250a-di fb-modules-2.6.32-3-sb1-bcm91250a-di input-modules-2.6.32-3-sb1-bcm91250a-di sata-modules-2.6.32-3-sb1-bcm91250a-di crypto-modules-2.6.32-3-sb1-bcm91250a-di crypto- dm-modules-2.6.32-3-sb1-bcm91250a-di squashfs-modules-2.6.32-3-sb1-bcm91250a-di rtc-modules-2.6.32-3-sb1-bcm91250a-di kernel-image-2.6.32-3-r5k-cobalt-di nic-shared-modules-2.6.32-3-r5k-cobalt-di ppp-modules-2.6.32-3-r5k-cobalt-di loop-modules-2.6.32-3-r5k-cobalt-di ipv6-modules-2.6.32-3-r5k-cobalt-di nls-core-modules-2.6.32-3-r5k-cobalt-di ext4-modules-2.6.32-3-r5k-cobalt-di jfs-modules-2.6.32-3-r5k-cobalt-di reiserfs-modules-2.6.32-3-r5k-cobalt-di xfs-modules-2.6.32-3-r5k-cobalt-di fat-modules-2.6.32-3-r5k-cobalt-di nfs-modules-2.6.32-3-r5k-cobalt-di md-modules-2.6.32-3-r5k-cobalt-di multipath-modules-2.6.32-3-r5k-cobalt-di crypto-modules-2.6.32-3-r5k-cobalt-di crypto-dm-modules-2.6.32-3-r5k-cobalt-di squashfs-modules-2.6.32-3-r5k-cobalt-di kernel-image-2.6.32-3-4kc-malta-di ppp-modules-2.6.32-3-4kc-malta-di ide-modules-2.6.32-3-4kc-malta-di cdrom-core-modules-2.6.32-3-4kc-malta-di loop-modules-2.6.32-3-4kc-malta-di ipv6-modules-2.6.32-3-4kc-malta-di nls-core-modules-2.6.32-3-4kc-malta-di ext4-modules-2.6.32- 3-4kc-malta-di isofs-modules-2.6.32-3-4kc-malta-di jfs-modules-2.6.32-3-4kc-malta-di reiserfs-modules-2.6.32-3-4kc-malta-di xfs-modules-2.6.32-3-4kc-malta-di fat-modules-2.6.32-3-4kc-malta-di md-modules-2.6.32-3-4kc-malta-di multipath-modules-2.6.32-3-4kc-malta-di usb-modules-2.6.32-3-4kc-malta-di usb-storage-modules-2.6.32-3-4kc-malta-di input-modules-2.6.32-3-4kc-malta-di sata-modules-2.6.32-3-4kc-malta-di crypto-modules-2.6.32-3-4kc-malta-di crypto-dm-modules-2.6.32-3-4kc-malta-di squashfs-modules-2.6.32-3-4kc-malta-di Architecture: source mipsel Version: 1.18 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-b...@lists.debian.org Changed-By: Aurelien Jarno aure...@debian.org Description: cdrom-core-modules-2.6.32-3-4kc-malta-di - CDROM support (udeb) cdrom-core-modules-2.6.32-3-sb1-bcm91250a-di - CDROM support (udeb) crypto-dm-modules-2.6.32-3-4kc-malta-di - devicemapper crypto module (udeb) crypto-dm-modules-2.6.32-3-r5k-cobalt-di - devicemapper crypto module (udeb) crypto-dm-modules-2.6.32-3-sb1-bcm91250a-di - devicemapper crypto module (udeb) crypto-modules-2.6.32-3-4kc-malta-di - crypto modules (udeb) crypto-modules-2.6.32-3-r5k-cobalt-di - crypto modules (udeb) crypto-modules-2.6.32-3-sb1-bcm91250a-di - crypto modules (udeb) ext4-modules-2.6.32-3-4kc-malta-di - EXT4 filesystem support (udeb) ext4-modules-2.6.32-3-r5k-cobalt-di - EXT4 filesystem support (udeb) ext4-modules-2.6.32-3-sb1-bcm91250a-di - EXT4 filesystem support (udeb) fat-modules-2.6.32-3-4kc-malta-di - FAT filesystem support (udeb) fat-modules-2.6.32-3-r5k-cobalt-di - FAT filesystem support (udeb) fat-modules-2.6.32-3-sb1-bcm91250a-di - FAT filesystem support (udeb) fb-modules-2.6.32-3-sb1-bcm91250a-di - Frame buffer support (udeb) ide-modules-2.6.32-3-4kc-malta-di - IDE drivers (udeb) input-modules-2.6.32-3-4kc-malta-di - Input devices support (udeb) input-modules-2.6.32-3-sb1-bcm91250a-di - Input devices support (udeb) ipv6-modules-2.6.32-3-4kc-malta-di - IPv6 driver (udeb) ipv6-modules-2.6.32-3-r5k-cobalt-di - IPv6 driver (udeb) ipv6-modules-2.6.32-3-sb1-bcm91250a-di - IPv6 driver (udeb) isofs-modules-2.6.32-3-4kc-malta-di - ISOFS filesystem support (udeb) isofs-modules-2.6.32-3-sb1-bcm91250a-di - ISOFS filesystem support (udeb) jfs-modules-2.6.32-3-4kc-malta-di - JFS filesystem support (udeb) jfs-modules-2.6.32-3-r5k-cobalt-di - JFS filesystem support (udeb) jfs-modules-2.6.32-3-sb1-bcm91250a-di - JFS filesystem support (udeb) kernel-image-2.6.32-3-4kc-malta-di - Linux kernel binary image for the Debian installer (udeb) kernel-image-2.6.32-3-r5k-cobalt-di - Linux kernel binary image for the Debian installer (udeb) kernel-image-2.6.32-3-sb1-bcm91250a-di - Linux kernel binary image for the Debian installer (udeb)
Accepted gtk-sharp2 2.12.10-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 18 May 2010 00:00:41 +0100 Source: gtk-sharp2 Binary: gtk-sharp2 gtk-sharp2-examples gtk-sharp2-gapi libglib2.0-cil libglib2.0-cil-dev libgtk2.0-cil libgtk2.0-cil-dev libglade2.0-cil libglade2.0-cil-dev monodoc-gtk2.0-manual Architecture: source all amd64 Version: 2.12.10-1 Distribution: unstable Urgency: low Maintainer: Debian CLI Libraries Team pkg-cli-libs-t...@lists.alioth.debian.org Changed-By: Jo Shields direct...@apebox.org Description: gtk-sharp2 - GTK# 2.10 suite, CLI bindings for GTK+ gtk-sharp2-examples - sample applications for the GTK# 2.10 toolkit gtk-sharp2-gapi - C source parser and C# code generator for GObject based APIs libglade2.0-cil - CLI binding for the Glade libraries 2.6 libglade2.0-cil-dev - CLI binding for the Glade libraries 2.6 libglib2.0-cil - CLI binding for the GLib utility library 2.12 libglib2.0-cil-dev - CLI binding for the GLib utility library 2.12 libgtk2.0-cil - CLI binding for the GTK+ toolkit 2.12 libgtk2.0-cil-dev - CLI binding for the GTK+ toolkit 2.12 monodoc-gtk2.0-manual - compiled XML documentation for GTK# 2.10 Changes: gtk-sharp2 (2.12.10-1) unstable; urgency=low . * New upstream release * debian/rules: + Bump API version to 2.12.10 * debian/control: + Bump Standards to 3.8.4 (no changes needed) * debian/source/format: + Force Debian source format 1.0 * debian/rules: + Write a get-orig-source rule * debian/watch: + Get rid of evil debian uupdate line which breaks packaging work on Ubuntu * debian/patches/01_dllmaps.dpatch: + Refreshed Checksums-Sha1: 22f3c4648d53dfcc62b6c382c3e477a552096165 1989 gtk-sharp2_2.12.10-1.dsc 6d737c031c4aa33a0b4f82b66ed2129a86361245 2301680 gtk-sharp2_2.12.10.orig.tar.gz 8b77db40a80fcdf66e0c85258f1da63528827a5f 14251 gtk-sharp2_2.12.10-1.diff.gz 48c52986799ab1502f1f650116af1400732f77e6 139522 gtk-sharp2_2.12.10-1_all.deb 6dc121b2366770865d147b151934b97ae213f5b9 408796 gtk-sharp2-examples_2.12.10-1_all.deb 18f311ed868555ec7e802b5dbb038ff150001a88 2369142 monodoc-gtk2.0-manual_2.12.10-1_all.deb 506e98989c014f3210b06c9473e03cf5f8d702b1 205220 gtk-sharp2-gapi_2.12.10-1_amd64.deb 1310d865c78976349a120d41b0bcb26534bc64c3 185454 libglib2.0-cil_2.12.10-1_amd64.deb 6449e30a22d9ca2f82d49defcbc0daad7f5a1037 140338 libglib2.0-cil-dev_2.12.10-1_amd64.deb 98d036c0614ab26285e76b31177a9963e229fe28 754250 libgtk2.0-cil_2.12.10-1_amd64.deb ab6cb0581130917e3225d72044e94b9ca39125e5 294102 libgtk2.0-cil-dev_2.12.10-1_amd64.deb c8ff7e5bd5fe453e669991bd3c3b0d8c341835dc 158266 libglade2.0-cil_2.12.10-1_amd64.deb 9cc229e2d7004a400505b67937c26514024f73d1 142768 libglade2.0-cil-dev_2.12.10-1_amd64.deb Checksums-Sha256: d3b784ef8d43ba4c950feb5fc1fc47730fdc8841d5c8eb863601e0a445a18f3a 1989 gtk-sharp2_2.12.10-1.dsc 8cffad11a5bd285f130d4a7ac70d8ee1d8071a128b0a1a577d8f92cb04dba5f8 2301680 gtk-sharp2_2.12.10.orig.tar.gz e5b409dee7724d50b7486c69748161e6c63a118c37177f688d49fe2801944c50 14251 gtk-sharp2_2.12.10-1.diff.gz 5ad786c61bae3a90ab4ce4262c124cf6e4efcb02fcffd03c6963885ddfc7378f 139522 gtk-sharp2_2.12.10-1_all.deb 08db8fdb8f72d18db215f85ce774efaefbb7a4f235cccab8dc3069f7f8cc62ac 408796 gtk-sharp2-examples_2.12.10-1_all.deb ba65995d69db241948bce7769e80265394156c6c68b7786d2f23a0b0f2782909 2369142 monodoc-gtk2.0-manual_2.12.10-1_all.deb 59860f75a4181aad0ebb6c9e866c9a782a03048827ceb061659b54393f54fafd 205220 gtk-sharp2-gapi_2.12.10-1_amd64.deb a51573700a47f1e2390fc84f2ffb7ac881da77ba1697e0256599d0f13498de0e 185454 libglib2.0-cil_2.12.10-1_amd64.deb c25fd1f9865b3079bccb714b082f4bdc0684239f7f76d91692fba1239d64cc6c 140338 libglib2.0-cil-dev_2.12.10-1_amd64.deb 465777039b29bfd1c74ad577059e6b73ee51f768b6cd20ffa810860ceab72349 754250 libgtk2.0-cil_2.12.10-1_amd64.deb b0080fb561f1e0b3abbd9532b66ede88fd3fa4b6f890edf4cc9c2fbc2d82b60d 294102 libgtk2.0-cil-dev_2.12.10-1_amd64.deb 60f72c9b49b2e03460d34ffbce91dc747cfb468c8ac949db8b5933c3786dc469 158266 libglade2.0-cil_2.12.10-1_amd64.deb fa0b2a398f879d9c1416841373b03bb7b2ebdde9bf5e3934af1e58d64d610fd1 142768 libglade2.0-cil-dev_2.12.10-1_amd64.deb Files: 99f8f513648328a37dae6c55a4c149bc 1989 libs optional gtk-sharp2_2.12.10-1.dsc 4da921affb952fc5d4044251706beacb 2301680 libs optional gtk-sharp2_2.12.10.orig.tar.gz 6901a22df37421b16b5fc7268ab369cd 14251 libs optional gtk-sharp2_2.12.10-1.diff.gz a8f056302533b27edee8989ca948edb0 139522 libs optional gtk-sharp2_2.12.10-1_all.deb fa6181cf6331a39e8c5afa89dabe5973 408796 libs optional gtk-sharp2-examples_2.12.10-1_all.deb 6bd1b85f6f9a5b3d5be9d9eb1bf31ea8 2369142 doc extra monodoc-gtk2.0-manual_2.12.10-1_all.deb c38152ce770c656c0ac82c3d05ad2829 205220 libs optional gtk-sharp2-gapi_2.12.10-1_amd64.deb c602ef3e0e6515983cf933a1d7e3620d 185454 libs optional libglib2.0-cil_2.12.10-1_amd64.deb f9624f15e22799560fde633623a150d3 140338 libs optional
Accepted fluxbox 1.1.1-8 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Format: 1.8 Date: Wed, 19 May 2010 12:42:11 +0200 Source: fluxbox Binary: fluxbox Architecture: source amd64 Version: 1.1.1-8 Distribution: unstable Urgency: low Maintainer: Dmitry E. Oboukhov un...@debian.org Changed-By: Denis Briand de...@narcan.fr Description: fluxbox- Highly configurable and low resource X11 Window manager Closes: 550466 554386 Changes: fluxbox (1.1.1-8) unstable; urgency=low . [Paul Tagliamonte] * Bumped the deb stds version. . [Denis Briand] * Upgrade libmagickcore-extra to libmagickcore3-extra build-dep. * Add source/format file. * Fix FTBFS with binutils-gold (Closes: #554386). * Fix hyphen-used-as-minus-sign in fbrun and fbsetbg man pages. * Allow centering fbrun popup (Closes: #550466). Thanks to Ulrich Eckhardt for his patch. * Debian Maintainer Upload is now allowed. Checksums-Sha1: bb5055f34b9aa1723f63b7da3d4aefd008d5e038 1491 fluxbox_1.1.1-8.dsc c21be657344c15d4a67e2a1e30b6ecf6ab694094 32631 fluxbox_1.1.1-8.diff.gz 9597d75d4da5028c9efd8c36215a535faae941f8 1504886 fluxbox_1.1.1-8_amd64.deb Checksums-Sha256: c9777b318a1df562cc0837b5a7d05776f68be0e7803189e2433cdf1d9eb40e61 1491 fluxbox_1.1.1-8.dsc a65adc252013d52ae638c15d54a72392e75239ba219b64f5f2b186b01c4b468c 32631 fluxbox_1.1.1-8.diff.gz 1a361061a7dec638df6fa9c0b12844201ba0268f17a7c80f47ec184b68b842a4 1504886 fluxbox_1.1.1-8_amd64.deb Files: d7e9d2ed96866d77dd092bd95beb9003 1491 x11 optional fluxbox_1.1.1-8.dsc 688cde806de0046cbbf11ee0df7f2043 32631 x11 optional fluxbox_1.1.1-8.diff.gz fee1a9011d17e42d22a5c66d0edea332 1504886 x11 optional fluxbox_1.1.1-8_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEAREDAAYFAkvzzTUACgkQq4wAz/jiZTek5gCeM7+/TcgV7Udx/5hPdbunfeo2 htAAn3oS9fEhPyzH3YrmZGxjw9zTuEIi =BsNU -END PGP SIGNATURE- Accepted: fluxbox_1.1.1-8.diff.gz to main/f/fluxbox/fluxbox_1.1.1-8.diff.gz fluxbox_1.1.1-8.dsc to main/f/fluxbox/fluxbox_1.1.1-8.dsc fluxbox_1.1.1-8_amd64.deb to main/f/fluxbox/fluxbox_1.1.1-8_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oehjx-vw...@ries.debian.org
Accepted linux-ftpd 0.17-30 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 09 May 2010 16:17:20 +0200
Source: linux-ftpd
Binary: ftpd
Architecture: source i386
Version: 0.17-30
Distribution: unstable
Urgency: low
Maintainer: Alberto Gonzalez Iniesta a...@inittab.org
Changed-By: Mats Erik Andersson mats.anders...@gisladisker.se
Description:
ftpd - File Transfer Protocol (FTP) server
Closes: 580251
Changes:
linux-ftpd (0.17-30) unstable; urgency=low
.
* Migration to format 3.0 (quilt).
+ Identified source code patches:
+ debian/patches/01-from_hamm.diff
+ debian/patches/02-from_sarge.diff
+ debian/patches/03-from_etch.diff
+ debian/patches/10-ftpd_csrf.diff
* Standard 3.8.4, debhelper compatibility 7:
+ Using dh_prep.
* debian/control:
+ Build depend includes ${misc:Depends} and 'debhelper (= 7).
+ Source homepage stanza pointing to download site.
* debian/watch: New file.
* debian/postinst: Suppress error message if '/etc/inetd.conf' is missing.
+ Print a hint to the example xinetd configuration, if applicable.
* debian/ftpd.examples:
+ debian/ftpd.xinetd: Configuration for use with xinetd.
* Prepare migration to IPv6 support:
+ debian/rules: Use compiler flag '-fno-strict-aliasing'.
+ debian/patches/14-adjust_infrastruct.diff: New file.
+ debian/patches/16-family_independence.diff: New file.
* Implement active IPv6 support: (Closes: #580251)
+ debian/patches/20-support_ipv6.diff: New file.
+ debian/NEWS: New file.
+ debian/README.Debian: A short explanation is added.
* Uninitialized va_list causes segmentation faults on amd64:
+ debian/patches/24-failing_va_list.diff: New file.
* [lintian] maintainer-script-without-set-e:
+ debian/{preinst,prerm,postinst,postrm} modified.
* [lintian] debian-rules-ignores-make-clean-error:
+ debian/rules modified.
* agi: Added Mats Erik Andersson as Uploader.
Checksums-Sha1:
0f97297e870458f953d9c056a8f758642e2cdea3 1156 linux-ftpd_0.17-30.dsc
8f900f18111b46b8348cb3b95b59e816f4fbc79e 32038 linux-ftpd_0.17-30.debian.tar.gz
c6b829a787b4021607df9a6a75ddcfcb611adb1d 46836 ftpd_0.17-30_i386.deb
Checksums-Sha256:
85f96c928fe112654bfdebbf07676ad25ef75cd9deb75f98786ec249107745cb 1156
linux-ftpd_0.17-30.dsc
76cc2aa6b3d9b1833880c49582304e3f91f966d9042bbac75075e439d20a9963 32038
linux-ftpd_0.17-30.debian.tar.gz
9bc911726994a2e138eb48f62024028a2f401676f5ef3f369a2d6291cf34329e 46836
ftpd_0.17-30_i386.deb
Files:
b243b989196dbf27eac6e935c3b5a5f2 1156 net extra linux-ftpd_0.17-30.dsc
151a490ca593c66ac09dc524827043fb 32038 net extra
linux-ftpd_0.17-30.debian.tar.gz
c21ff1058adfeebbab58c7060fbec507 46836 net extra ftpd_0.17-30_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkvzxjAACgkQxRSvjkukAcNv3QCgg8wMcYEfU3Fr9tx52nAumcXb
P8IAn3++dOYeB+cHgvx0e2Ru9/Boijes
=m/Hz
-END PGP SIGNATURE-
Accepted:
ftpd_0.17-30_i386.deb
to main/l/linux-ftpd/ftpd_0.17-30_i386.deb
linux-ftpd_0.17-30.debian.tar.gz
to main/l/linux-ftpd/linux-ftpd_0.17-30.debian.tar.gz
linux-ftpd_0.17-30.dsc
to main/l/linux-ftpd/linux-ftpd_0.17-30.dsc
--
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1oehln-c1...@ries.debian.org
Accepted ffc 0.9.2-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 19 May 2010 13:06:27 +0200 Source: ffc Binary: python-ffc Architecture: source all Version: 0.9.2-3 Distribution: unstable Urgency: low Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org Changed-By: Johannes Ring joha...@simula.no Description: python-ffc - compiler for finite element variational forms Closes: 581897 Changes: ffc (0.9.2-3) unstable; urgency=low . * debian/control: Add python-dolfin to Suggests (closes: #581897). Checksums-Sha1: 5e63fd9354aada89a50855953c937d31caeef2f2 1967 ffc_0.9.2-3.dsc ca213d735db0b98ef751852f25126c86041f7807 13830 ffc_0.9.2-3.diff.gz 7e77d56bd7d3783cbfc6e4098d122c5292ddc49d 543400 python-ffc_0.9.2-3_all.deb Checksums-Sha256: 8196ea235968636f8c548ef5e48e572c9ea21e2b35d89cd158b6e4886d6f508f 1967 ffc_0.9.2-3.dsc 5a17fb6d6e74174a650d7e7784509557a9a20278fa246f1bc50e3729a7325c7b 13830 ffc_0.9.2-3.diff.gz fb2ab154f8133f53c37f7ecf2b9d2ecc0b0239a8b867b22317dbcc1c730e3209 543400 python-ffc_0.9.2-3_all.deb Files: 1063663520728da33478f25a248e253c 1967 python extra ffc_0.9.2-3.dsc 32d69bb6be749105d774f679ac1e8dba 13830 python extra ffc_0.9.2-3.diff.gz 66c31ddde3dbfe45518225b84755db94 543400 python extra python-ffc_0.9.2-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQIVAwUBS/PPc4sTRN6fgH8UAQL3wA//TMjYaI2NyNM6GhpSIEKxS8h4EXi6ARg7 lekKHonod0GGoPBTsF6EDR+Lsobiyr+366rNYcRfIXo1/a7n3CqxCRciNHMJn96w tRyQYg2Pdk7RFcY2iJygsoQpeIH0MOyduAT3/zQB2KiK/F8tP5bQkbkAwP/MUg9/ BKijqaa4YDeduwv8oZCWRYHAZ6QVVQ9XfhGm5Qe0igi+b6T0v+ZYslOFCpnPY+SE PnqB3Wn5DU82lu22aDcUMYl4VORbA5/8A5fCzN7/QbNkLXd+kYzUA1zQEZq/tH3V cbeP+RlS8MtR5gBmpc9EXcO/bVYj84QnNJgrQtZqA0A2/NVCPDiTKfJwNFUwoe+q HRcoyGRzdQHR3CgDSToLM+m3xKDXP0JPGt43lu+Tc/BxbUM7CWaD5GJc09hWOP1b zQKYaSYHOqvrZ2CacDtHmX++8crz1V4yXQgH+oUwTKqsPvJCnjhWmgBBPASBuZHT /nw2gS1qQjsiLk4oyqNDWpAnVuPtSYfhLojzE4TRpvjVKZN44c850kT8Mhnw0/13 kqVB2NNHQa/+k/bRxBrpe1H67zMpSgzzuwSDL3ro1aUHc2a9sCqYjHaSSujsk2GJ JXdZNjIt/Ds8FwMYdwDK/1DYEPymtybmMzrnXWPCGMnA82fp1RsNiaGXElzdAmR6 xhMv3JEOWMY= =KQP2 -END PGP SIGNATURE- Accepted: ffc_0.9.2-3.diff.gz to main/f/ffc/ffc_0.9.2-3.diff.gz ffc_0.9.2-3.dsc to main/f/ffc/ffc_0.9.2-3.dsc python-ffc_0.9.2-3_all.deb to main/f/ffc/python-ffc_0.9.2-3_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oehyt-0001ls...@ries.debian.org
