Re: Golang >= 1.12 in Buster?
Hi, On Sat, Apr 13, 2019 at 09:54:18PM +0800, Shengjing Zhu wrote: > FWIW, golang-1.12 was removed from buster, because the RT think > there're too many golang for buster[1]. there's no logic in that, and especially with the introduction of this new feature, which the Go community has awaited for so long, I think it's a perfect way to blast your legs off. It's a bit like removing Python 3 because there were so many Python2 versions already. Or how about removing Python2 altogether, then? > [1] https://tracker.debian.org/news/1024215/golang-112-removed-from-testing/ Thank you for the pointer! I strongly think that this decision very wrong and should be reversed. If the RT absolutely insist on cutting down the number of Go versions, I am not opposed to see eg. golang-1.11 go, however, as I don't see a compelling case for having it. But others may disagree. In this way, I fully agree with Eric on this matter. Cheers, Toni
Golang >= 1.12 in Buster?
Hello, I just figured that Buster is, from the current POV, going to ship with Golang 1.11. While I am new to Go, I figured that we should probably have a newer version of Golang in Buster, as they are now doing versioned dependencies, but only starting with 1.12 or 1.13 (not quite sure about the difference here). This seems to be rapidly adopted by projects out there, so having only older versions of Golang is becoming useless quite soon. One project which I am trying to work on, coredns, already does not compile with anything older than 1.12. I know we are in freeze already, but I still need to ask, whether there might be a freeze exception, or how we are going to remedy this situation? Cheers, Toni
Accepted tcpwatch-httpproxy 1.3.1-3 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 04 Aug 2018 21:31:50 +0200 Source: tcpwatch-httpproxy Binary: tcpwatch-httpproxy Architecture: source all Version: 1.3.1-3 Distribution: unstable Urgency: medium Maintainer: Toni Mueller Changed-By: Toni Mueller Description: tcpwatch-httpproxy - TCP monitoring and logging tool with support for HTTP 1.1 Closes: 904772 Changes: tcpwatch-httpproxy (1.3.1-3) unstable; urgency=medium . * add dependency (closes: #904772) Checksums-Sha1: d6c1dcffc9f60a98bcae49644a664984664b9c6d 1848 tcpwatch-httpproxy_1.3.1-3.dsc d1eb31f6285dcbe8cc64696a2d3216237e52caf6 5284 tcpwatch-httpproxy_1.3.1-3.debian.tar.xz 5e2746444157e6931fb374dbfb16c3748440448a 17020 tcpwatch-httpproxy_1.3.1-3_all.deb 421f35ee20eb78b3c7266480312c5ef1f559cf81 6581 tcpwatch-httpproxy_1.3.1-3_amd64.buildinfo Checksums-Sha256: d01c352786376a80590b7b00b13764cc3682d02b0ae58d25a66bc6dde29360d2 1848 tcpwatch-httpproxy_1.3.1-3.dsc f52c4b7406501efa3b2c5c058b6e7d91bdebf51fc220563250125ba2c0b64bfb 5284 tcpwatch-httpproxy_1.3.1-3.debian.tar.xz 76f0feff4fe55213331d1b99bdec4461299b11837050fc26e4ce8302adf7b9a4 17020 tcpwatch-httpproxy_1.3.1-3_all.deb 98357195fd0e4b9644d10a2d0d889eefc90eb4400924d479c6ee554474458637 6581 tcpwatch-httpproxy_1.3.1-3_amd64.buildinfo Files: 29cd6447996bad9903705c28ea2e0fc1 1848 net optional tcpwatch-httpproxy_1.3.1-3.dsc b226fdda2b74c4d46f278623aff87e85 5284 net optional tcpwatch-httpproxy_1.3.1-3.debian.tar.xz 13ffb9ac2d63983134707743a1c03dd2 17020 net optional tcpwatch-httpproxy_1.3.1-3_all.deb f82ffd0de69cb0ddb97620bee9c62a81 6581 net optional tcpwatch-httpproxy_1.3.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEEHfahn8pT+XNT8/NdigpIh0aHr08FAltmBWgQHHRvbmlAZGVi aWFuLm9yZwAKCRCKCkiHRoevTxbzD/9WYN1Qj/7mMANvQ2i3AAGLEH5R+jCQe6s4 GUu9edaENcJc4qS/Cx+1o4YwsmRM+oB6e5b/Q8sdAGq892/Rd8tV4sNXPBj+gPDN vE612JyAqDzJGuSkwq8RHy/+MWibILPz52H3wVP7fcOU3TCzq7OtFx+BDBmalu2L NyNhhyq7v+UuQzLy61ItAkmBRGhviGSM4Mst4PT0TgZhsUSnVy9Dxk885cm1gQhM wuEUu4ISvWLMIIni2+FUd7G+4xiM468SW4KDuUpSFnRb/sgXyge3K1FJdr56AS6F yrUqh2jnpLu5tGeI4sXiA74T3hxZbeW0VVenLcfr/MKQK94KlQtcejYV4gxMJuMN 8AhHwZYna82gTvXCdJhU7kCMz/4Mk092bJNyW7kGoggKzJOyHOpsOo5BCj4Qhzcs pY1r+J97qQatN0m22MpPaHsQoji7ifWmqOi2U8qq0PA0Gm5YsqwvLaYfAEYJzdZF mWMPqaOzs5YdrbD5VK29v3pTulHWkos1iQDbZUEnaSMtsujZVrN1C7dRTCXTBpsc XO3CTV48XWDFcWxGxfdMmNKZqsY3sfCnhZqEZxi1F6+Wzo1J9snCj00+p9GQq7Hn PkkrN+Qlfu91sKKWj2ownzwDoHXfwVMbqbGnPj4t1CGPZP+60xF1w9HecRZH2S12 NdPeRfopVg== =qLJR -END PGP SIGNATURE-
Re: Concerns to software freedom when packaging deep-learning based appications.
Hi, On Thu, Jul 12, 2018 at 04:20:05PM +0200, Georges Khaznadar wrote: > 4- if no commercial machine exists at a "fair price", to train the >neural network in a reasonable amount of time, the publisher of Y >must lend a machine to fulfill the GPL requirements. I don't think so. Otherwise, noone would publish anything at opencores.org or similar, or else someone might sue them for a lithography machine. And certainly, there would not be any OpenSparc T1 layouts from Oracle. Just my late 0.02 cents, Toni
Re: ISO download difficult (was: Debian Stretch new user report (vs Linux Mint))
On Fri, Dec 29, 2017 at 04:22:23PM +0500, Andrey Rahmatullin wrote: > My point is you shouldn't educate with lies and half-truths. Good point. Then you get to do it the correct way. Deal? Cheers, --Toni++
Re: ISO download difficult (was: Debian Stretch new user report (vs Linux Mint))
On Thu, Dec 28, 2017 at 10:13:52AM +0500, Andrey Rahmatullin wrote: > On Wed, Dec 27, 2017 at 11:00:38PM +0100, Toni Mueller wrote: > > link to a page suggesting free hardware over similar non-free hardware > > There is no such thing. There is only non-free hardware without updates > for its software. "Whatever". My main point is imho to both make it easier for people to run Debian on their computers and educate them at the same time. I hope that my approach would achieve that goal, but after spending a lot of time with this thread, other approaches like including everything in an ISO and then installing only the required bits also sound promising. Cheers, --Toni++
Re: ISO download difficult (was: Debian Stretch new user report (vs Linux Mint))
Hi, On Fri, Dec 01, 2017 at 02:39:12PM +0100, W. Martin Borgert wrote: > Every time I need a Debian ISO, it takes me minutes to find it. > I didn't even know, that there were an ISO with non-free firmware. > > There should be a beautiful ISO download page, e.g. > https://www.debian.org/download[s]/ > with all architectures and supported releases, similar to > https://www.ubuntu.com/download > or > https://linuxmint.com/download.php I wasn't really aware of the distinction and just noticed that I so far got by with the free ISOs. But I also found that most newbies who are being hooked on Mint or Ubuntu, are very unlikely to change to Debian, but instead tend to blame any problems on Linux as a whole. Arguing about freeness is probably not helpful for these people because they will most likely simply not understand the point, and what makes free hardware so much better. Therefore, in my opinion, using a more end user oriented language is advised. I would therefore like to suggest some change to the first page (get.debian.org) along these lines. Despite the wording, though, it can be viewed to massively encourage users to use non-free hardware, because it makes it much easier accessible: Debian CDs == Standard Images/Free Software Images If you want to install a VM or have fairly free/simple/old hardware (better wording required, preferably with a link enumerating compatible hardware), you are encouraged to use these images: Link to our free ISOs. Special Hardware/Non-Free Software Images - We do not advocate using non-free hardware, but would still like to enable you to use Debian. If your hardware includes any of these components: (link to a page with hardware requiring non-free firmware), you may need to use these images (link to the ISOs including non-free software), but we encourage you to look at (link to Free Software statements/explanations) and maybe look into suggested hardware choices (link to a page suggesting free hardware over similar non-free hardware). Cheers, --Toni++
Re: Bug#849703: ITP: ansible-doc -- Documentation for Ansible
Hi Harlan, On Sat, Dec 31, 2016 at 01:07:44PM -0500, Harlan Lieberman-Berg wrote: > It's been a while since we made the decision not to pull from upstream's > git; Toni, I'd be happy to work with you on seeing if it's doable now. I think I have a suitable package now, being as cheap as possible, but it's off your git tree, which I took from https://anonscm.debian.org/git/collab-maint/ansible.git I had to change some things, though: * retrofit the docsite directory * adjust debian/control * adjust debian/rules It's for 2.4.1, and it's lintian clean. My changes build both packages. How can I best upload this stuff without disrupting yours, and without creating an entirely new repository? TIA! Cheers, --Toni++
Re: Can we kill net-tools, please?
Hi, I'm confused... On Thu, Dec 29, 2016 at 09:01:51PM +0500, Andrey Rahmatullin wrote: > On Thu, Dec 29, 2016 at 10:30:26AM -0500, Theodore Ts'o wrote: > >Ifconfig has been deprecated; you should probably use "ip a show > >dev lo" instad of the shorter and more convenient "ifconfig lo" > ... and often wrong The BSD ifconfig can do this with ease, and since ages, too. Why is the Linux ifconfig _so_ different? Forking for the sake of it? Eg adding an IPv6 address: # ifconfig em0 inet6 address alias and removing it: # ifconfig em0 inet6 address -alias Just asking. Cheers, --Toni++ PS: http://man.openbsd.org/OpenBSD-current/man8/ifconfig.8
Re: Bug#849703: ITP: ansible-doc -- Documentation for Ansible
On Tue, Jan 03, 2017 at 09:14:59PM -0500, Harlan Lieberman-Berg wrote: > Toni Mueller <t...@debian.org> writes: > > I found them only on PyPI. Did you find them elsewhere? > > We get them from releases.ansible.com. Are the docs in the tarballs in > PyPi? Nope, there are only man pages. Cheers, --Toni++
Re: Bug#849703: ITP: ansible-doc -- Documentation for Ansible
Hi! A happy new year, everyone! On Sat, Dec 31, 2016 at 01:07:44PM -0500, Harlan Lieberman-Berg wrote: > Unfortunately, we don't build ansible off of the git repository, but > rather from the released tarballs. I found them only on PyPI. Did you find them elsewhere? > It's been a while since we made the decision not to pull from upstream's > git; Toni, I'd be happy to work with you on seeing if it's doable now. Let's get the -doc package into stretch first if it's not too late already. Cheers, --Toni++
Re: Bug#849703: ITP: ansible-doc -- Documentation for Ansible
Hi Evgeni, On Fri, Dec 30, 2016 at 10:44:50PM +0100, Evgeni Golov wrote: > On Fri, Dec 30, 2016 at 12:58:02AM +0100, Toni Mueller wrote: > > documentation. This package aims to supply the documentation in HTML > > form offline, so one should not need to go to the aoupstream website to > > read it. > > Which source is this built from? > Do you basically want a mirror of https://docs.ansible.com/ansible/ in > a Debian package? I am building from a git clone of the ansible repository, and, more specifically, from the tag v2.2.0.0-1. > > Yours truly frequently suffers under bad network conditions, which make > > reading the website infeasible or outright impossible, so I think the > > package is useful. > > If it is more than ansible-doc , then it certainly is. My network conditions vary greatly, but too frequently, they are not good enough to access anything on the Internet. Working on that, but still, having a local copy of everything is very desirable from my POV. > I just wonder whether it is sensible to built it from an own source, > and not from the ansible source itself. I found a very easy way to build everything from the ansible source, at least for this tag. Cheers, --Toni++
Bug#849703: ITP: ansible-doc -- Documentation for Ansible
Package: wnpp Severity: wishlist Owner: Toni Mueller <t...@debian.org> * Package name: ansible-doc Version : 2.2.0.0-1 Upstream Author : RedHat <i...@ansible.com> * URL : http://www.ansible.com/ * License : GPL-3 Programming Lang: HTML, JavaScript Description : Documentation for Ansible Currently, the Ansible package in Debian lacks proper offline documentation. This package aims to supply the documentation in HTML form offline, so one should not need to go to the aoupstream website to read it. Yours truly frequently suffers under bad network conditions, which make reading the website infeasible or outright impossible, so I think the package is useful. I hope I can collaborate with the maintainer of the ansible package to maintain this package.
update fonts etc. in HTML pages
Hi, I'm working on packaging for a -doc package and find, that the original code generated, in this case by Sphinx, contains unwanted references to fonts hosted outside, eg. at Google, and other unwanted stuff. For the bulk of the JavaScript, I found Debian packages that allow me to create the desired "/javascript/..." style link. But for the fonts, I don't know what to do, except for removing the references. I don't like this solution because we seem to have some of the fonts in our repository already. It feels like a waste to not use them. If you have tips to share, that would be great! Cheers, --Toni++
Accepted funkload 1.17.1-2 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 18 Dec 2016 14:57:02 +0100 Source: funkload Binary: funkload funkload-doc Architecture: source all Version: 1.17.1-2 Distribution: unstable Urgency: low Maintainer: Toni Mueller <t...@debian.org> Changed-By: Toni Mueller <t...@debian.org> Description: funkload - web testing tool funkload-doc - web testing tool (documentation package) Changes: funkload (1.17.1-2) unstable; urgency=low . * Commit Debian 3.0 (quilt) metadata * remove the bogus .egg-info directory * do not install the demo files, they are in .../examples Checksums-Sha1: d44668dd0f05bf9d404c6af75bc5c667975c3d08 1795 funkload_1.17.1-2.dsc 83b8cd234d15cb54b24d82fa980a8b2d0ef2bc27 6008 funkload_1.17.1-2.debian.tar.xz 2de5327d08eeea5fab5cdd086ac41f8e95b3 122302 funkload-doc_1.17.1-2_all.deb 9772b9f3c2f47ba1520d08fcc1fb8b9e319569d1 111590 funkload_1.17.1-2_all.deb Checksums-Sha256: 27611abb920ef77c050df21e8d3ea7dbb699c80976c1a173d2645bc01009197e 1795 funkload_1.17.1-2.dsc e16d0ee92159284d07b40ed99f073d368d1a68f55217056d3b93a4973bbbe921 6008 funkload_1.17.1-2.debian.tar.xz 79af26ea4d95d4be1b28ce0842c99d6f5eec66fb152ae147dfc60569ebd1f1b1 122302 funkload-doc_1.17.1-2_all.deb 8def92291a2f318ad9820fe807603e5dfc799de7781617464269ab1749acf5a0 111590 funkload_1.17.1-2_all.deb Files: 08590d4a83a2201b636f296e6a5798bb 1795 web extra funkload_1.17.1-2.dsc 584637fb3d3031e11720dab0c28a9c70 6008 web extra funkload_1.17.1-2.debian.tar.xz 40b53d9733cc817ba92cf793f710cf0f 122302 doc extra funkload-doc_1.17.1-2_all.deb 84343bfca8a603ee16713a1e5c4058c9 111590 web extra funkload_1.17.1-2_all.deb -BEGIN PGP SIGNATURE- iQItBAEBCgAXBQJYVpcuEBx0b25pQGRlYmlhbi5vcmcACgkQigpIh0aHr0/cVw/9 Ew5z6h30KTeRGysYduDfkuqEwXrh4WGpRFKJ4PsjPBOumzNMBoVz7nx50ofANF9z n0nZdWQb53yCP2WjPMM9NLGWuspWAeWT+n3tfsl0GaiGgxyyXiRY7vzuc2IJYK/u DyFDHN7FRlU7n07em/E7DlDNYskSYsnQ4d3s8m2o166I8xPXwbNQDcXSc3YkPmCB D4cveqbdMhZ4Xr1OS0Fv8A9Xg/1RmZNyC7U62k5XwPYW3Nh29pyV6IRz4LQftbGS YsFye7deEHCHQhxe9lJWEY8++qVYxSUWTqVR5w61yQqOYhdYnl7DpuV3/0OyD7eA FLzmhtzunrUbw6zpu52h99xiFzvU3+Zs2TxxStCIJogvqqrM4z9wth8RkhxoMYjy PqBJ2tKJ95D3F2Z4BDzNq0KH6JugpHIkTKTensbEyV8lDrTRh+OkOBWESsalN6+c LEL3G/kUvb3ueQ2IHjm+7rPyGgX0v2w1MxQO2kBJhVN001fnN/OTd4nhOqP2nj9X YIk+BJOakP9vGtTXLU1LI7vPRocYCZNJ1SUt0Vcnt88mOAqmEynUKHLlz5ogr/Op lJY4YygoCr3jy9A6x4VA+s2M/6hoeNu/jAoRTOGMkJwl3kdIvEzIeyEYHusKZ10L Wsr+/UYhyoealBAYYeGb8BvkZ26GOdQSYBusdEHK08s= =xgPm -END PGP SIGNATURE-
Accepted funkload 1.17.1-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 18 Dec 2016 03:35:48 +0100 Source: funkload Binary: funkload funkload-doc Architecture: source all Version: 1.17.1-1 Distribution: unstable Urgency: medium Maintainer: Toni Mueller <t...@debian.org> Changed-By: Toni Mueller <t...@debian.org> Description: funkload - web testing tool funkload-doc - web testing tool (documentation package) Changes: funkload (1.17.1-1) unstable; urgency=medium . * new upstream version * new packaging Checksums-Sha1: 74d4581b355a0b23c9ac18b2a8d062f720731425 1795 funkload_1.17.1-1.dsc 077fedd42dcf151edf6fa4ecde4e733e222d1f6f 197338 funkload_1.17.1.orig.tar.gz 1e0f4114f5797ac30f595aa2dfabbeb8e3e087c7 5688 funkload_1.17.1-1.debian.tar.xz a08f1fc05963ec4ad6acc0acf3c0167c2e148d18 111218 funkload-doc_1.17.1-1_all.deb 936d49a1ed37a6b18c410ad441ad072b04849105 111966 funkload_1.17.1-1_all.deb Checksums-Sha256: c1ed601ee4bd059a755ab14e3bfae702eae75f24ce613a1c1e065dd5220401ec 1795 funkload_1.17.1-1.dsc 566414f90186a8dd6bb77ac8bad05620a5c0f8ed4ce3c6a61028c61930959bca 197338 funkload_1.17.1.orig.tar.gz 5779176d01d099f7cda50d00907335c75f86cc05297bef5590b4a8419e581a6c 5688 funkload_1.17.1-1.debian.tar.xz d9dbc2a7ad172e585d06034d6442060ba206d7622d02cdc380d2d985ed67b520 111218 funkload-doc_1.17.1-1_all.deb a8d2220218139c35eb9b741c2e49f7583c3baf895214c15084fd7ec861af5bb9 111966 funkload_1.17.1-1_all.deb Files: 20f39c290a9907769f3c48b0164f7848 1795 web extra funkload_1.17.1-1.dsc 4ef6e71281792cee1ec94235f1b35fb1 197338 web extra funkload_1.17.1.orig.tar.gz 9abeec8f7be8385f8bae15c38eba71bb 5688 web extra funkload_1.17.1-1.debian.tar.xz f661ec64e6698b649bd22153ce307dd1 111218 doc extra funkload-doc_1.17.1-1_all.deb a1dffe3ad5a94e7fa0c2dbb42806f9e9 111966 web extra funkload_1.17.1-1_all.deb -BEGIN PGP SIGNATURE- iQItBAEBCgAXBQJYVf61EBx0b25pQGRlYmlhbi5vcmcACgkQigpIh0aHr0+WqQ/7 BoruIs83O+S5UVKP0lL3Dei3Hilr4sQz4tv4VNjCsbeWNk3SyZVln3g+2kcyzRDL iCnlWTazZ2GneI45xPT4q0PY4UlTy+qgOGO4qLDZMk54Y5E66/cr3Es4yd5y2u9e PsTS4q5QYCPjQM5wyCmRAmXXY5XG2hXVY1EXOfjOWBEcOwh3m/8RIY0p3yIf8HeQ +v30iP7pJAVTBoGtaGbO/wRmnKEt12thKYXeVmwlAHUaKFX0tanYAVikSjVz0vJx FwCwmQBK1LsN10n4bUdC3vAFoDiReIO818c7Z2FT+ccMTOxleqt3iH4K5q7rvgLp 5ICZiu0PGq59pmnpAuszCjiS/i0ktZcNtiQapGtIi85zOMbndMbJnC78cA3e8IS7 OVOGPUkUyks9EN8//Mugcc6kTYnhUmuiio5OcXIe2OlWuQGWC6mr8bG1L/g0Rln0 JjsjbIuDBACvTXfTguOsUGkJM3kRgsP/KNKKn6/QLX/uo+9hWft9wUKboQPgIMKa KjyxGMBczEPJ0OSf8qsRONOz/Ppc3FNBIjlYEYtWqZr1uhb1TFzhnLl1ykbvdXx8 yV5qChds1Bi/wLZtU5eMk81f0aYa1aWtmJ7z3O0BnY2scM3L3nT+SoLafjKt8E7c 97xiOHFsriB98xegySicfh7gKu77GAwMl27YFyFBNK0= =fTcT -END PGP SIGNATURE-
Accepted tcpwatch-httpproxy 1.3.1-2 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 28 Aug 2016 19:59:14 +0800 Source: tcpwatch-httpproxy Binary: tcpwatch-httpproxy Architecture: source all Version: 1.3.1-2 Distribution: unstable Urgency: medium Maintainer: Toni Mueller <t...@debian.org> Changed-By: Toni Mueller <t...@debian.org> Description: tcpwatch-httpproxy - TCP monitoring and logging tool with support for HTTP 1.1 Closes: 835701 Changes: tcpwatch-httpproxy (1.3.1-2) unstable; urgency=medium . * Added missing dependency (closes: #835701) Checksums-Sha1: 31a6f6a9f3cf7ff80bec83848c246b982d3fae8e 1809 tcpwatch-httpproxy_1.3.1-2.dsc 6035a2c411f217cd25d4a72470518e8a5d7ff4bf 5240 tcpwatch-httpproxy_1.3.1-2.debian.tar.xz 3067c315c56dbd8cf287371a0738d74d9e272ad7 17070 tcpwatch-httpproxy_1.3.1-2_all.deb Checksums-Sha256: a49549cd36798fb8c755301087d1a3fecef39c2530bca2727e273383fc13f27a 1809 tcpwatch-httpproxy_1.3.1-2.dsc 5f6cdc9e1cdaf3691a7d0e6159f28d2dd5799dd64e2af8774e464bbf468bb6eb 5240 tcpwatch-httpproxy_1.3.1-2.debian.tar.xz dc681ff4580482b8c5a45de88dc1bae266dd90e522563d111394398c74d8978a 17070 tcpwatch-httpproxy_1.3.1-2_all.deb Files: c3d039aeffa2121a1291aa724c1e72c0 1809 net optional tcpwatch-httpproxy_1.3.1-2.dsc 476d44d20541ec9565a0c1540655d88f 5240 net optional tcpwatch-httpproxy_1.3.1-2.debian.tar.xz 8622fe847dfcee31c4713188ba1e628c 17070 net optional tcpwatch-httpproxy_1.3.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJXwtQBAAoJEIoKSIdGh69PtO0P/i4MFXiezCKVinlXWeBn0PnC DVSDhlSN2Rx8HFVPBVIx3O+p/kS2QbPTjac4zB4IrSyll8e5ZOTKooMnKJqCfO6M m+kQ44LsK0WYmfthQxGRT5rX1R3JDfAeTU6XfVOJF/qgLCI5Wl/+50MooSoUjbtJ K6bw549S35kh21nOodal9DrT5e88G3LgCzZfcH7MO79CX86NWI9eU0XmsrCOzH9f 0oHqPMhmn64HEtCtLMc7rrnMIeJJT3ONP/FdAPCk0V5sX0XHxlSpQSDu1xEbCZz5 Kx27h7ZMlNsVzWxKl52teyM9IlW8lsqrGfumKEHMnkVYLABnAz+6nqPWziUC4qRQ gJPUVCfkNS7af0aVjYD03HI9OO6PV3rFtiFexZC5EUiBC7ra6IaDw4iLBIWDbjEm xQyYKf7qY1XwHqedGHsnqVmIsdnEf3BUKKKuBXw4V2hF9TjeVtDbmuTm3aKoWPfQ nsXhUA7zxXP/X2yGTF3WpqL7wYVWc3bcfWA5UXc/BtBoHQp4ylBZQ2UwXOl9ygFp zyK9qhEb2YYH1BzWskDaSAHRHpJqc4QGwum2ldU+DBSbuZg6iKhk3TzxOYZEDG4f 31hkbQKdS4MPnQxbyC6UTRyIImvvYgN8fCHQz9EagbDuJb/akXeWaUqmmNLhyueg O398baS198vJSXyumlj8 =kcWG -END PGP SIGNATURE-
Accepted tcpwatch-httpproxy 1.3.1-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 21 Aug 2016 13:59:59 +0800 Source: tcpwatch-httpproxy Binary: tcpwatch-httpproxy Architecture: source all Version: 1.3.1-1 Distribution: unstable Urgency: low Maintainer: Toni Mueller <t...@debian.org> Changed-By: Toni Mueller <t...@debian.org> Description: tcpwatch-httpproxy - TCP monitoring and logging tool with support for HTTP 1.1 Closes: 776969 Changes: tcpwatch-httpproxy (1.3.1-1) unstable; urgency=low . * new upstream version * new packaging (closes: #776969) * change obsolete syntax for potential Python3 compatibility Checksums-Sha1: cc6d4dfaf0105cc9d1d43614462814aaaf6ae98f 1790 tcpwatch-httpproxy_1.3.1-1.dsc 91d4563cb64e9c3f07c18ae39cefd33111e052c8 14154 tcpwatch-httpproxy_1.3.1.orig.tar.gz 64f5b7629f05928ecb6821e1c38a58846bf9880f 5200 tcpwatch-httpproxy_1.3.1-1.debian.tar.xz 495ae60fb216e6f5e8b28ccec95b2f4373cf2adc 17028 tcpwatch-httpproxy_1.3.1-1_all.deb Checksums-Sha256: 2ae95da715476b4db548ec7a758a3b0d4784656bd5f5c6531bd4bd4095e0a058 1790 tcpwatch-httpproxy_1.3.1-1.dsc 0f24e0cb5d822596ca32f703cb95f7cb9a005001c1783f5227db10976f80da9c 14154 tcpwatch-httpproxy_1.3.1.orig.tar.gz fb767654de598d09deacb756c2f9a8fa7d6037c359109a0e62d230d37aabb63c 5200 tcpwatch-httpproxy_1.3.1-1.debian.tar.xz 99d457e0d94b155ecb29806b69eb2460f6b8c15ff6160d1c24cce958454b1d41 17028 tcpwatch-httpproxy_1.3.1-1_all.deb Files: 583d88d38c3e7f51e380bd606973ea4c 1790 net optional tcpwatch-httpproxy_1.3.1-1.dsc 0f9f1f9d303c8ed6fc533849dc84eb38 14154 net optional tcpwatch-httpproxy_1.3.1.orig.tar.gz 4c99c014e6782bffc661a2a38da62802 5200 net optional tcpwatch-httpproxy_1.3.1-1.debian.tar.xz c428bfb317c87139c805afd741744123 17028 net optional tcpwatch-httpproxy_1.3.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJXuUOgAAoJEIoKSIdGh69Pw0sQAJSMIxUASzhAnLy3uDKLnGfk ZWWg3Uvmg7Kdup6IQxoOEbgYSy0bdJxxjzk+OwaNG2ekhQfWmu2H7lrLt3okl7Qj fNTGMlRDlr+tW+cNuU+dfBeG3aOlfeTWtpc/5IyXwiCw3pt0CKZgL+rOQN7ZS+7y bkKaAkLhlwOCbDUp7LWw3t85hFaW+aLS2MQBrrO/XL0t+wXAQcwsg+w4GLihLzTy WNBBHCb+ixNbIVgMxZv6Rg13dLThorif1IcF1CGYfn+jdbwsQmwNZB/v+x6ZcwMp hoaQlkLeE1aRWyX01czGao9s8h2tFgAcwg76o9403bSP3nAhdXs2/pAurHH/9s7X 2osyFqyzCjA5ScKG0kVQ7Qqu1Xh9e1CQimcyKEopx7IYfza70A9TUVs83OELr1PP iplvV5+FQQEQiXOOwXinqEHbDC9gO/SKrsbm4QGP69FlEZdqmLMmuyBJGRCDLs9m wyIGDoowR+f7Uk+Jyh8RPXDTokEYR7z5K8t2QgAe1speEhq5JVkVXFvct/3QBQjP z1XgwKdVnIwhso2tm6VyYDPZaipzNZZYBlPWHVNQ7Z7pWYhyN9F9ODcVoU8IzYnD QjUu9ifca/NRHaKwEiE63DJvkuykUnRtOnHEAq+ZVKrmf/aENGLNrxhxxXjbIWD+ V0MqcQv0jMP+Nw0noFc7 =TTRu -END PGP SIGNATURE-
Re: enforced systemd services (was: Misc Developer News (#37))
Hi Marc, On Tue, Nov 25, 2014 at 10:54:39AM +0100, Marc Haber wrote: On Tue, 25 Nov 2014 10:04:06 +0100, Arturo Borrero Gonzalez arturo.borrero.g...@gmail.com wrote: On 25 November 2014 at 02:22, Paul Wise p...@debian.org wrote: [13] http://0pointer.net/public/systemd-nluug-2014.pdf This seems pretty interesting. Indeed. Do we really have to pull that from a video or presentation slides? Is this part of the official systemd docs anywhere? yes, this is in the official docs, somewhere. I had the pleasure to plough through them a few weeks ago. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141125103300.ga17...@lappi1.office.oeko.net
Accepted iptables-converter 0.9.5-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 16 Jun 2014 21:33:31 +0200 Source: iptables-converter Binary: iptables-converter iptables-converter-doc Architecture: source all Version: 0.9.5-1 Distribution: unstable Urgency: low Maintainer: Johannes Hubertz johan...@hubertz.de Changed-By: Toni Mueller t...@debian.org Description: iptables-converter - convert iptables-commands from a file to iptables-save format iptables-converter-doc - sphinx documentation for iptables-converter Closes: 748635 748638 Changes: iptables-converter (0.9.5-1) unstable; urgency=low . * [63bdb0d] illegal characters '$()' no longer lead to faulty output * [3efcb8b] short inputfile should be valid except for a variable * [d36c02b] short inputfile should be valid except for a function. Thanks to Guido for the bugreport Closes: #748638 * [302e5f9] tests now proof for shell varaibles and functions * [2369725] manpages updated and corrected for exit status * [202d159] copied and adapted from iptables-converter * [5098422] version set to 0.9.5 * [8379d72] ip6tables_converter.py added * [7708973] adapted to additional tests for shell vars, funcs * [aa690f8] sphinx-doc updated, errors with functions and variables mentioned * [1ff76c9] version changed to 0.9.5 * [0751002] Improve package description. Closes: #748635 Checksums-Sha1: 82d115143fb3915d90463da36b1c23eb586251d4 2023 iptables-converter_0.9.5-1.dsc a26b1f1ed28356d2633bea685bb83c66ab4a74a4 31669 iptables-converter_0.9.5.orig.tar.gz d664a52ea64b0e1a3318e6fa1f0f99f516b6bfae 3280 iptables-converter_0.9.5-1.debian.tar.xz d8651e3613ea01020fb125f598a5ae6a9ded0637 8674 iptables-converter_0.9.5-1_all.deb a4f4bb80bc14f6317f12e89bb9153ceab9c640f7 23446 iptables-converter-doc_0.9.5-1_all.deb Checksums-Sha256: 99a389241f5051512fe7de2f34a26b1006a586132da85920178d36a5d254f3aa 2023 iptables-converter_0.9.5-1.dsc 972896ee6d4205f7ac1b617065959e4de72b36558830a5965ef77e58653af4c0 31669 iptables-converter_0.9.5.orig.tar.gz 148be8491f3b9a308f9655e03959af0d261e367fcb191e6e651a8df7cad0d477 3280 iptables-converter_0.9.5-1.debian.tar.xz 9171a684ba61048ef1962e89ffe3382ec18849ab2c5b2e7aa38897e2541a3d12 8674 iptables-converter_0.9.5-1_all.deb f9ae7c38ed322081b4eb17029d554df1375075bd8a254ab6f1ec20163a3d53fd 23446 iptables-converter-doc_0.9.5-1_all.deb Files: 4d823f383d62bb5588e0aaf0ba1b2e37 8674 utils optional iptables-converter_0.9.5-1_all.deb 91f49982e0548a7f102488a2c3fc0b33 23446 doc optional iptables-converter-doc_0.9.5-1_all.deb e6d0647fd02e9f28aa199f2cd2531dbe 2023 utils optional iptables-converter_0.9.5-1.dsc 120613e52a112298a95db401bea8c8a8 31669 utils optional iptables-converter_0.9.5.orig.tar.gz 9090fe2f4ebc29a5f5ef9af1cc5e95f3 3280 utils optional iptables-converter_0.9.5-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJT8SCDAAoJEIoKSIdGh69PW5kP/3S9+0J0cogqDH1kLjGPU3PV ixKist9WbLzswnhNvsxkDb+n7gMApgv/Aqr11XNbDuJy3kO+lF9bBEFnK08tWrSB igklK9/rNXhfo0YeCgC+4lOMAIH0PDra0xDfO6nuJSdzD1Wf3rvGdyBpTWzZO2am qipzm5+TuOhDgGUYyLrYtubuwzJwnsV41GKcfAPGSe1TUVURkgu0Rg+8ICQd0dIc npKQJwhc86yLyrvp9M37iMHs4xAC4+FWZYF6fYWfMK5oXQjRyew13HV3imBgIq+g PCoxmNShp2625MdkP6kdeJSjmJsDIQPI7dOk/JmrTLwZOOcsv0hYtaMQDe0rLpae 5BOoLs2bY1ukG93GFWJ9qCBVBLahTClBEsSWnnyEfafd/vtb+x7YCZ5nGJykrjKX eOQGB49NtVmNnoQbL7E0dznNqNRocnHpr/EPDlGnLZtWoe4/Kkg9AMH9NwyWpq5J f5ZYpR13fVBxvQVon/sPVGdfNDGRY89UHUNsVG/7R5Cx4yJ53khqDRVRvdApdizD OqvbQPC1dO4f/UObR5NovzpCkeBwLzO9h8uJK4UlVacORWdlAT+msJfuFULie11o /m+zbtl4k0p56A3Z6Dh44wOakQXyTpn8ehSFGpvmYakAKIkXQAKcpKkbopn3TC5D zT2K5s/mUHCSKW9vcOJy =P0M4 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xj8jm-0001lv...@franck.debian.org
Re: Bug#754513: ITP: libressl -- SSL library, forked from OpenSSL
On Tue, Jul 15, 2014 at 07:43:27AM +0200, Andreas Metzler wrote: That turns smaller adjustments in applications into developing entirely different interfaces for each application, while GnuTLS itself still lacks a lot of features. Do you have any reference for this? I have not followed this closely but historically GnuTLS seemed to do very well feature wise (e.g. early TLS 1.2 support). I was referring to the paper from utexas, linked to in a different post, but mistakenly counted the errors listed there (7 out of 16) as missing features. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140715094106.ga18...@spruce.wiehl.oeko.net
Re: Bug#754513: ITP: libressl -- SSL library, forked from OpenSSL
On Mon, Jul 14, 2014 at 01:32:40PM -0700, Russ Allbery wrote: In the world in which BSD software is linked with LibreSSL and the license exceptions have not been changed to allow OpenSSL-derived software, now (due to the way that Debian applies this rule transitively) GPL software can't link against BSD-licensed libraries that link with LibreSSL, even though previously this wouldn't be a problem due to the OpenSSL exception. This seems like a very bad thing to me. Imho, this is a non-issue, due to the simple fact that we are not yet shipping LibreSSL, and due to the fact that LibreSSL is still very young. It took time to get the OpenSSL exception from upstreams, and over time, maybe, there will be LibreSSL exceptions as well. Or the code will be re-done to a point where the OpenSSL license might be dropped. So far, LibreSSL is young enough so upstreams simply had no time to amend their licenses, if they would want to allow LibreSSL, too. Whatever. It would be very bad if we would be forced to switch to LibreSSL right now, but we aren't. No need to panic, really. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140715201840.ga29...@spruce.wiehl.oeko.net
Re: Bug#754513: ITP: libressl -- SSL library, forked from OpenSSL
Hi Thomas, On Sun, Jul 13, 2014 at 11:52:24AM +0800, Thomas Goirand wrote: On 07/12/2014 08:46 PM, Toni Mueller wrote: As libressl is currently under heavy development, it is imho not to be expected to have that stable ABI you are asking for. Well, I don't agree with this view. If LibreSSL pretends to be a replacement for OpenSSL, then they should care about being ABI compatible, but they are only partially compatible already. The one thing that appears to stick out is that libressl has *no* support for egd, and on purpose (ie, it will not come back). And the other is arc4random(). so we can easily switch from one implementation to the other. Just like for MariaDB / MySQL in fact (not sure if these are still ABI compatible though). If that's not the case, then it looses a lot of its purpose. As Kurt wrote, GNUTLS becomes a better alternative then. If your application does not use things which are deemed deprecated, then it should be quite compatible, but by ripping out tons of old stuff, they of course also break something, at some point. The whole API becomes smaller simply because of that (I don't think this will be offset by the added features in other areas, like adding better cipher suites). As for GnuTLS, all I read so far is that it requires a *lot* of work to make a single application which has been developed together with OpenSSL, compatible with GnuTLS, because apparently almost everything differs to the point that it is unfeasible or impossible to have a compatibility layer. That turns smaller adjustments in applications into developing entirely different interfaces for each application, while GnuTLS itself still lacks a lot of features. At the face of it, that sounds like it is at least an order of magnitude more work, but likely even much more than that. And add to that that GnuTLS apparently works incorrectly almost half of the time (which translates to a significant security *downgrade* in my eyes), there is a huge amount of work set for those who would really try to fix it (ignoring the row between the upstream author and the FSF aside for the moment). OTOH, one guy already switched his entire Linux system over, so far with no visible adverse effects. And then? This gives no clue if he had to rebuild everything that build-depended on OpenSSL... That I don't know, but I have posed this question to the guy who made that statement. I'll keep you posted. On 07/13/2014 01:15 AM, Russ Allbery wrote: If you start using both for different packages, then you end up with shared libraries conflicting over which libssl they want to use, and then bad things start happening. Exactly! I fully agree with you on this. I do not think that accidentically using one library when one wanted to use the other will be an issue. FWIW, I've been told that a separate libressl.so is in the making, and if so, binary incompatibility can be taken for granted. This reminds me issues I had with mod-log-sql linked to MySQL and php as well, and when they were built against different versions... BOOM! I certainly do *not* want this kind of things to happen in Debian. Therefore, I'd very much prefer if we used OpenSSL *or* LibreSSL, but not have the choice between the 2, otherwise, that's a recipe for disaster. Ummm... what was BOOM exactly, please? Because within a release, OpenSSL (letter) versions should all be compatible with each other. Please don't upload LibreSSL to Sid *ever*, unless we collectively decide that we are switching away from OpenSSL (and for which a discussion would have to start). Well... as I said, I'm first and foremost planning to get it into experimental, and then we can see what it really is, fix the packaging etc.pp., and evaluate the package along the way. And while I hold the OpenBSD developers in very high esteem, I am still a bit wary that the package might be not as secure as we wish it to be, and therefore guess that we want to evaluate the package thoroughly for some time before the discussion about switching over can even start in a reasonable manner. Having said that, I value all of your input, but feel not halfway as much trigger happy as some of you seem to think I am. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140714184831.ga12...@spruce.wiehl.oeko.net
Re: Bug#754513: ITP: libressl -- SSL library, forked from OpenSSL
Hi Jeroen, On Sun, Jul 13, 2014 at 12:22:49PM +0200, Jeroen Dekkers wrote: At Sat, 12 Jul 2014 14:46:45 +0200, Toni Mueller wrote: Ok, but for whatever reason, they have an imho not as shiny track record, as has OpenBSD. Which is no wonder, given all the revelations we have had recently, but hey, sometimes one has to make a decision. OpenSSL was part of OpenBSD before they created the LibreSSL fork, so how isn't OpenSSL part of the OpenBSD track record? it is in the way that they include it, and it also contributed a significant amount of all patches that were required over the years, but the typical way OpenBSD operates - from my perspective - is, they include something (eg. Sendmail), and once they get fed up with it for whatever reason, unless they find something acceptable out there (eg. nginx instead of Apache, or nsd(?)+unbound instead of BIND), they start to roll their own. A few releases later, the old stuff is being demoted or removed entirely (eg. for RAIDframe - softraid, the switchover period where you could choose was more than four years, afair). Such changes do happen in a disruptive manner, as there is usually nothing that aids you in converting your setup from the old to the new software. It depends on how you look at it. If you see the OpenSSL API as something that isn't really well designed then other libraries not copying the API is actually a good thing. Yes and no, but if it is more than ten times the amount of work, it is likely never getting done, for the simple reason that everyone is lacking resources. You forget one of the big problems with OpenSSL that LibreSSL doesn't fix: the license. Granted. Due to the amount of inherited code, it can't. We'll see how things evolve as the amount of inherited code will dwindle. It actually makes the mess even bigger, given that some of the GPL exceptions only talk about the OpenSSL library and don't exempt OpenSSL-derived code. So even if LibreSSL is a drop-in for OpenSSL we can't replace OpenSSL with LibreSSL for those projects. Yes. Thanks for pointing this out. You also forget to list two other TLS libraries: * NSS, in my opinion the biggest downside of NSS is that it includes NSPR. This both increases the code size a lot and makes the API less nice if I remember correctly. Hmmm... yes. I was under the impression that not very many people were using it, but looking at my system, NSS + NSPR ~ 3,5MB, while libssl1.0.0 comes in at ~3MB. Add ~1MB for sqlite3 and zlib1g in the case of NSS... * PolarSSL, which I really like from a technical point of view. Featurewise it is pretty complete (the only major feature it doesn't implement is DTLS AFAICS), while being one tenth the size of OpenSSL / GnuTLS: https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations#Code_size_and_dependencies PolarSSL is also used by OpenVPN-NL, the hardened OpenVPN version that is used by the Dutch government. The downsides are that it looks like it doesn't have a stable API and contributing needs copyright assignment because it is dual-licensed. It still gets 5 out of 16 answers wrong, as per the comparison sheet included here: https://www.cs.utexas.edu/~shmat/shmat_oak14.pdf Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140714200800.gb12...@spruce.wiehl.oeko.net
Re: Bug#754513: ITP: libressl -- SSL library, forked from OpenSSL (addendum)
On Mon, Jul 14, 2014 at 10:08:01PM +0200, Toni Mueller wrote: On Sun, Jul 13, 2014 at 12:22:49PM +0200, Jeroen Dekkers wrote: OpenSSL was part of OpenBSD before they created the LibreSSL fork, so how isn't OpenSSL part of the OpenBSD track record? it is in the way that they include it, and it also contributed a significant amount of all patches that were required over the years, but the typical way OpenBSD operates - from my perspective - is, they include something (eg. Sendmail), and once they get fed up with it for whatever reason, unless they find something acceptable out there (eg. nginx instead of Apache, or nsd(?)+unbound instead of BIND), they start to roll their own. A few releases later, the old stuff is being demoted or removed entirely (eg. for RAIDframe - softraid, the switchover period where you could choose was more than four years, afair). Such changes do happen in a disruptive manner, as there is usually nothing that aids you in converting your setup from the old to the new software. After a period of settling in, the alternatives are usually much less troublesome than their respective predecessors, and typically produce less security problems. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140714201159.gc12...@spruce.wiehl.oeko.net
Re: Bug#754513: ITP: libressl -- SSL library, forked from OpenSSL
Hi Kurt, [ I have trimmed the Cc list - we are all on devel@, anyway, right? ] On Sat, Jul 12, 2014 at 02:15:13PM +0200, Kurt Roeckx wrote: On Sat, Jul 12, 2014 at 01:53:45PM +0200, Toni Mueller wrote: On Sat, Jul 12, 2014 at 01:25:47PM +0200, Kurt Roeckx wrote: What are you doing with the binaries, include files, man pages, ...? Will they conflict with the ones from openssl? my intention is to package this stuff so one can have both openssl and libressl installed in parallel. libressl currently has libraries with these sonames: libssl.so.26 libcrypto.so.29 I don't really like it, since it could potentionally clash with the ones provided by openssl. But it seems unlikely that openssl will ever use that as soname. I had the feeling openbsd didn't care much about ABI stability, and that being at 26 and 29 already doesn't give me a good feeling either. I hope you don't have to go and change the binary package names each time you upload a new version. Actually, these version numbers typically correspond with the version numbers in the rest of their system. As libressl is currently under heavy development, it is imho not to be expected to have that stable ABI you are asking for. OTOH, one guy already switched his entire Linux system over, so far with no visible adverse effects. I was never very happy with it either. But it has very recently changed, and I think it's going in the right direction. I'm now also in the openssl development team. Good. That does help to improve my trust with it. I'm not really sure what you mean by this. I'm pretty sure the openssl development team has a pretty good understanding of security and I don't see anybody adding a backdoor in it. Ok, but for whatever reason, they have an imho not as shiny track record, as has OpenBSD. Which is no wonder, given all the revelations we have had recently, but hey, sometimes one has to make a decision. FWIW, I have well over a decade of very good experience with OpenBSD Not everybody has the same experience with them. Yes. Not everybody has an intention to use LibreSSL, either, but regarding crypto, they usually know their stuff well above average. See eg. their OpenSSH, which has seen very widespread adoption. I think GnuTLS is actually a better alternative and wish there were more people developing and using it. But developing GnuTLS is a full-time job, and then there's the control problem with the FSF - you are certainly aware about the problems the original upstream ran into when he wanted to break loose from the FSF (for a reason I have forgotten). LibreSSL is a much lower-hanging fruit, as it is supposed to be mostly, or entirely, plug-compatible with OpenSSL. To me, the playing field largely looks like this atm: * GnuTLS, with an API incompatible with OpenSSL, thus requiring huge amounts of work to make significant use of it. * MatrixSSL, which once had a dubious license, and which still did not come out too well in the SSL lib comparison I recently saw (see the list archive), * the now newly staffed OpenSSL project, with their mixed track record (eg. FIPS), and now * LibreSSL, which sounds much like an OpenSSL on a diet, and with some exercise, and promising thrust behind it, but mostly simply a drop-in. And I guess the BoringSSL people will chime in sooner or later, too... Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140712124645.gb10...@spruce.wiehl.oeko.net
Re: Bug#754513: ITP: libressl -- SSL library, forked from OpenSSL
Hi, On Sat, Jul 12, 2014 at 07:43:44AM +0200, Marco d'Itri wrote: On Jul 12, Toni Mueller supp...@oeko.net wrote: * Package name: libressl I am highly doubtful at best. in which respect, and why? What are your plans exactly? My plan is to first build the package(s) and upload to experimental, so people can start to play with it. Would it have the same SONAME of openssl and conflict+provide it? I would like to make it co-installable with OpenSSL, but in general, this should be a drop-in replacement until APIs really diverge in a visible way. Yes, it would provide 'openssl', but I intend to place them into a different directory, so you might have to use LD_PATH to get them. Whether it has to conflict with openssl, I'll figure out that later, if otherwise the case would arise that a binary might get libssl from one package, and libcrypto from the other. So far, it looks like a recompile could be necessary. But since the upstream package has seen the light of day only yesterday (see http://article.gmane.org/gmane.os.openbsd.announce/186 for the announcement), things are not yet stable. For the technical side of the discussion, you can read http://dir.gmane.org/gmane.os.openbsd.tech). Would it be a totally different library which packages would build-depend on? Packages currently build-depending on openssl should be able to build-depend on openssl-dev | libressl-dev. For recent versions of OpenSSH, it already works, and another user writes: Just switched my slackware 14.1 box over to libressl instead of openssl and it's working great so far, no problems at all. So I guess usability is already good. But imho, it does have to stand the test of time, and receive independent review, and much more exposure. Which is one reason why I think it is a very good idea to expose it to the Debian and related communities. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140712130429.gc10...@spruce.wiehl.oeko.net
Bug#754513: ITP: libressl -- SSL library, forked from OpenSSL
Package: wnpp Severity: wishlist Owner: Toni Mueller t...@debian.org * Package name: libressl Version : 2.0.0 Upstream Author : The OpenBSD project, the OpenSSL project et al. * URL : http://www.libressl.org/ * License : BSD, OpenSSL, SSLeay, Public Domain. Programming Lang: C Description : SSL library, forked from OpenSSL LibreSSL strives to maintain API compatibility with OpenSSL, but do away with all the cruft. After a long series of OpenSSL problems, recently highlighted by the infamous Heartbleed bug, a group inside OpenBSD decided to fork OpenSSL and adapt the code to modern coding standards. Along the way, a lot of compatibility with older architectures and toolchains was discarded. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140711220627.24261.14073.report...@spruce.wiehl.oeko.net
Re: default messaging/VoIP client for Debian 8/Jessie
On Tue, Apr 01, 2014 at 04:07:24PM +0800, Thomas Goirand wrote: BTW, it'd be nice to have a backport of Jitsi. Not sure how much work that would be though (there must be lots of java dependencies...). I recently installed 2.5.5190-1 on Wheezy without much trouble, but imho, the operational issues are much bigger than the possible dependencies (eg. no roster on amd64). Not sure how I to usefully contribute, though... their Wiki basically says (my perception only) spend your days with us, or go away. Kind regards, --Toni++ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140412232536.ga20...@spruce.wiehl.oeko.net
Accepted iptables-converter 0.9.3-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 19 Feb 2014 14:45:51 +0100 Source: iptables-converter Binary: iptables-converter iptables-converter-doc Architecture: source all Version: 0.9.3-1 Distribution: unstable Urgency: low Maintainer: Johannes Hubertz johan...@hubertz.de Changed-By: Toni Mueller t...@debian.org Description: iptables-converter - convert set of iptables-commands to iptables-save format iptables-converter-doc - sphinx documentation for iptables-converter Closes: 712263 Changes: iptables-converter (0.9.3-1) unstable; urgency=low . * Bump version number to force source upload. * Closes: #712263 Checksums-Sha1: 8a6fcdb665f93dbd939dc16f529e9c313316cd09 2009 iptables-converter_0.9.3-1.dsc 35aca0c771428bb0c4448f60019377a55e3968b4 26209 iptables-converter_0.9.3.orig.tar.gz e1c050bef94deac6afeaae892ce041be80c69fd5 3096 iptables-converter_0.9.3-1.debian.tar.xz 899dbb0ef481c6395ec8b53db348b0f61c622f6c 6628 iptables-converter_0.9.3-1_all.deb 8c6be7b567f470f06078fc80581d2e9193dda109 24772 iptables-converter-doc_0.9.3-1_all.deb Checksums-Sha256: db8f9184656f483a990fb189e01577848d96bc6151ffb298e32c0ccdbf71d7cc 2009 iptables-converter_0.9.3-1.dsc 9f9efa4b898ce164bb1df4e88c68ebc2ff081a11d0e0a0b2fe0891e066128256 26209 iptables-converter_0.9.3.orig.tar.gz 1988be7991140dba64d469f0019f3217ec2f50f384a347b229bbfa0addca3703 3096 iptables-converter_0.9.3-1.debian.tar.xz c5b312e91ce1d85f33edb58d4a35631f57bf3a95b449bb42787fef205cd64658 6628 iptables-converter_0.9.3-1_all.deb 41b7d8031ed2d984843f34b8fb97d8668743339918b9b9b44b990e9944e5e989 24772 iptables-converter-doc_0.9.3-1_all.deb Files: f20c996330704792db97c615fd19e0dd 2009 utils optional iptables-converter_0.9.3-1.dsc 45b4024c31737d7507ece0a26fbe0919 26209 utils optional iptables-converter_0.9.3.orig.tar.gz ee595cee8907c7a2ab5ac52dee5b2746 3096 utils optional iptables-converter_0.9.3-1.debian.tar.xz b67a6b90eb1198dc0936a080e03006f1 6628 utils optional iptables-converter_0.9.3-1_all.deb 8f385e891a21505aee4be9a5b0127185 24772 doc optional iptables-converter-doc_0.9.3-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJTBLqEAAoJEIoKSIdGh69PHRcP/0+G+x0VEQwhA+0zyMKFiU0d U3j7M+30Cc03bjWRW1rgGCx9dl2xCt9qIWkS48Txv67VD2p3AWB7UFkSfgh/Hk7P 8/rUxwiY8S90Btf2bL0Ib2DDDbG69jUfia3ePxV+juoHbJCJf1j3gYBxs2tnXFZ0 W4V95f4wcfikl05yeF7D+VS4WVR7hN70qLTIiQz6dM8VlUKhW/QmbgOJ22erYv6n ODIMwkLL41WmK2mJ9w23z7OGv5aM2dLAQDdwvjWzDac3M7Us3e294vk9+hBY2SWs jgVtLPDaABnBQlSH3zt3T4mmfzuQCEn/tOz1tCXVRM3gYBz9UznFa+xgVEAPHTW0 Og4cxHLnpz8pxkE3hP8TocMlnw9XnSV4NFx68RYRaN5nWm8cLYN2NRw0HyC/Nr1A hGmJfg2QE9V7F7ivT4UGvC5CFyezzZk31PdstesVlUNGNot0AKsyIaJfVf3S1GcM nZdTOj5E3wNOrcV7tfrN1BroYZH6j3obhcfpxGfiKggGbEmxx9fx4Sc1B4QtboRD 8KlyJeehRgJXhY5yMriyUOyNc5jV6EHTDS1Q8i/JMXd4T45Ixybm6Kv5+bEHAYB2 5WX4lFhasmNvfPA8cq+Kp853pgYReQFYFsUvBFyasAhC9LFK3hueFzDXgQ0ka8sM +9X3wMcoNVlS5jkMEx80 =hSej -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1wgoly-000382...@franck.debian.org
Re: /bin/sh (was Re: jessie release goals)
On Sat, May 11, 2013 at 08:44:30PM +0100, Roger Leigh wrote: ... forcing the rest of the world to conform to our worldview. One desktop environment, and an awful one at that, dictating the init system we use is a complete farce. Debian is a lot bigger than GNOME, and if we have to, I'd vote for junking it entirely. As much as I liked GNOME over competing desktops in the past, this time I have to fully agree with this statement of yours. Kind regards, --Toni++ -- 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/20130514131241.ga10...@spruce.wiehl.oeko.net
Re: Linux Future
Hi, On Wed, Jan 23, 2013 at 05:12:59AM +0600, Andrey Rahmatullin wrote: On Tue, Jan 22, 2013 at 12:06:16PM +0100, Pau Garcia i Quiles wrote: This blogpost is months old but it makes some interesting reflections: http://www.pappp.net/?p=969 https://plus.google.com/u/0/115547683951727699051/posts/74r518xVUNH LOL! Actually, I find this reply to the PAPPP post largely invalid because LP does not address the fact that these pipes and sockets are no longer the official interface for random third-party tools to talk to, but only used as internal communication mechanisms, using likely ever-changing and much less than standard D-Bus documented protocols. Talking to those sockets/pipes is much akin programming with Undocumented Windows in your hand, then get the blame if something breaks because you didn't use the one officially blessed API. IOW, it's inherently unreliable, and a doomed approach. Oh, and I think it *does* matter whether something is Unix or not. There are even bodies to evolve the Unix spec, if needs be (arguably yes in some areas, but not in all). If you don't agree, consider the viability of ReactOS, which is (afaik) free software, too, or the way the traditional Unices evolved. Kind regards, --Toni++ -- 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/20130224180059.ga5...@spruce.wiehl.oeko.net
Re: Really, about udev, not init sytsems (was: Gentoo guys starting a fork of udev)
Hi, On Fri, Nov 16, 2012 at 02:09:51AM +0800, Thomas Goirand wrote: On 11/14/2012 11:12 AM, Thomas Goirand wrote: The full thread is here: http://thread.gmane.org/gmane.linux.gentoo.project/2262 This thread was originally about udev, yet everyone is starting again the systemd / upstart / sysv-rc war. I think we can agree that we don't about I, for one, wholeheartedly welcome the fork, as I hope that this will help getting back some of the modularity in Linux that was there, once upon a time, and which contributed to making Linux a robust platform - sometime in the past. Kind regards, --Toni++ -- 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/20121124155750.ga14...@spruce.wiehl.oeko.net
Re: Really, about udev, not init sytsems (was: Gentoo guys starting a fork of udev)
On Sat, Nov 24, 2012 at 05:15:25PM +0100, John Paul Adrian Glaubitz wrote: If both Ubuntu and Gentoo would just go with the rest of the community and accept systemd, we wouldn't have to bother whether udev runs without systemd or not. I would highly prefer a system where I can take small bites if I want to, and where components are as portable as possible, and as it stands, I am very uncomfortable with systemd, too. It's certainly interesting, but having a hard dependency on it is imho a no-no. Please take a step back, look at the bigger picture, and tell me whether you think that we, as Debianites, or as Free Software Advocates, are still heading in the right direction: 1. What does it mean if more and more software is required to run a Linux system, in the various scenarios, and losing the ability to swap components w/o major kernel hackery? So far, being highly modular was a way to contain the complexity, and finish off bugs. It's not only more eyeballs to catch them, it's also the complexity that makes it increasingly hard for people to understand what's going on in the first place, so the problem of having the required knowledge, that you highlighted in your message, will only get worse and worse with tighter integration. 2. What does it mean if more and more software only runs on Linux? 3. What does it mean that - my claim/experience - more and more Linux software is simply broken (see Gnome for a popular example, but I have more)? I don't see anyway why something as low-level as udev should be highly portable in the first place. Maybe, but I do see why systemd must not be a hard dependency of the Linux kernel, and if systemd is basically the user-space part of udev, and both can't live without each other, then something is fundamentally wrong in the design. IMHO. Kind regards, --Toni++ PS: Please don't Cc' me, I'm on the list. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121124170302.gb10...@spruce.wiehl.oeko.net
Accepted scim-tables 0.5.12-1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 10 Oct 2012 15:36:15 +0800 Source: scim-tables Binary: scim-modules-table scim-tables-zh scim-tables-ja scim-tables-ko scim-tables-additional Architecture: source i386 all Version: 0.5.12-1 Distribution: unstable Urgency: low Maintainer: Tz-Huan Huang tzh...@gmail.com Changed-By: Toni Mueller t...@debian.org Description: scim-modules-table - generic tables IM engine module for SCIM platform scim-tables-additional - miscellaneous input method data tables for SCIM platform scim-tables-ja - Japanese input method data tables for SCIM platform scim-tables-ko - Korean input method data tables for SCIM platform scim-tables-zh - Chinese input method data tables for SCIM platform Closes: 499558 689335 Changes: scim-tables (0.5.12-1) unstable; urgency=low . * new upstream release. Closes: #689335, Closes: #499558. * debian/control - add vcs-git and vcs-browser. - add intltool to Build-Depends. * debian/*.png.uu: merged by upstream, removed. Checksums-Sha1: 1fd1132517cabd70f5becefd52393754e3721b84 2263 scim-tables_0.5.12-1.dsc 373e4668650ab4447d2ee18a90436903777326f5 6699148 scim-tables_0.5.12.orig.tar.gz ab0081ebee17d375cd75a7917124a665cf742e43 8075 scim-tables_0.5.12-1.debian.tar.gz ae286800f40a36467a0946bc4001bcf4b61f7559 331936 scim-modules-table_0.5.12-1_i386.deb 48dc334a4d5b24d864ed98fbfd8cef5d40d34f0e 6097190 scim-tables-zh_0.5.12-1_all.deb 03d25ceb290b249352696a1360774bedf3af5ea6 136656 scim-tables-ja_0.5.12-1_all.deb 7f9baa80e20fabf96592bf076b8970269a0e6c5d 218284 scim-tables-ko_0.5.12-1_all.deb a5af23ae387ad67e4137292ad9a6cc3b515d4374 114666 scim-tables-additional_0.5.12-1_all.deb Checksums-Sha256: 85dbf93f34ea70c1e489824ce161e49ce2986fd6ce25cd03bbccc635832b133e 2263 scim-tables_0.5.12-1.dsc 3976d62997b26f36f27b6cd37461be8e649a3f3bc45aa4606c6c9146528c4d49 6699148 scim-tables_0.5.12.orig.tar.gz d5f6954bead67969c5d98e13322d9696f4078914b168ac4b8c8ec15c5ee36dcc 8075 scim-tables_0.5.12-1.debian.tar.gz 740c6d6cfd559a755147e76cbe2f293a3be3b4d98d29f6e51865ce21c130ae08 331936 scim-modules-table_0.5.12-1_i386.deb 999703a96cfd04a5db27cf8c3ce2c24ea59f564054619f1d9e7adc295e593c3f 6097190 scim-tables-zh_0.5.12-1_all.deb 8a907de47713d58b569831fae991cf80627d2519dc08d0938d810a329835e939 136656 scim-tables-ja_0.5.12-1_all.deb aed80e383438af7402eebf755224e580caeb42809b7a03f7b1a3c41de5ce3b98 218284 scim-tables-ko_0.5.12-1_all.deb f859623308497d87dd6f9569f94f7b66f8a5f530d16c3bf3dee07ea8944a476f 114666 scim-tables-additional_0.5.12-1_all.deb Files: 782bf5fcf8d49b2f4f191bef1d0aefed 2263 utils optional scim-tables_0.5.12-1.dsc 8e2a2c927b0a593a34654f85b0d04f5d 6699148 utils optional scim-tables_0.5.12.orig.tar.gz 0853a3473ec963a8413fb35e0c742eb5 8075 utils optional scim-tables_0.5.12-1.debian.tar.gz 4b6a48c779da41215805563dc0fcac99 331936 utils optional scim-modules-table_0.5.12-1_i386.deb f10ee30b9906bb3097fa20ca909d5720 6097190 utils optional scim-tables-zh_0.5.12-1_all.deb ff73390f2ca03efbc8bdd2861953cb92 136656 utils optional scim-tables-ja_0.5.12-1_all.deb daf2262e81127da9ceca36b5fa0a7984 218284 utils optional scim-tables-ko_0.5.12-1_all.deb 3811c1ccbcbe8e9e0e37934508bd8c80 114666 utils optional scim-tables-additional_0.5.12-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQgIJrAAoJEIoKSIdGh69POEwP/RqLuFT8BehdTCEzJv31t2Iu Fg7VQEhM16ecQHU2QRtvJpPwu+tDqlWweDALEHvCI25AQ28otwu7co+JFdR5dG3A T/SX5ZNGOZznYKi43XOmCYr42WB81H0GvOiV7MXTfnOuo00kkELsl8YYA2G0Uwed 7uBeJmrN74buLumPSO6k4CZ9psucTNktOM9S++8Y+PctaZL/331qwG5+rWC+yZ4Y XLbTvmmcH69D2MvOoKjdNIrW4K9lCikfql8XmwjTrn9uJGH80H5bCvRoiPI8vSQK SAaaVrvf1779lgrK5Zg028BjRDq9a7vsV8Z+LdmRdty3PpFeC3yHXoRtEZGdz0rh tfap9BpLpfWcIVePMauFeELeJGrF/+AKE8/M6K7EyTJslqpv8aYHGbCgcKz+aJRu Isgi0vhBn4cozKZ584RvtnuX4lThgGT8rlvkuzLlLzluRKUxJ1FexgEd6XwgBSy1 yX6PhGeqIUcPu/Ih7jp2BmizTnCcqJK2Zo0t5qpwzeYKVShkHyRcFOWFLHBu11k0 9FoYolTsWX7vXa83/xW9UEAGk7rnXBedSjaS7nfSvVf/F1zYAROU4+zRR9d6y1PK Yxoq7C0+gNvJJhi6aaH0jhoCDYiagVC17eaRZcj7UbawySDChyunQUIHwjEXZdqq YNzu/geSd8YJ6qebpNPn =6C6u -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1toysy-0001vq...@franck.debian.org
Accepted scim-tables 0.5.11-1 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 06 Jul 2012 16:07:01 +0800 Source: scim-tables Binary: scim-modules-table scim-tables-zh scim-tables-ja scim-tables-ko scim-tables-additional Architecture: source i386 all Version: 0.5.11-1 Distribution: unstable Urgency: low Maintainer: Tz-Huan Huang tzh...@gmail.com Changed-By: Toni Mueller t...@debian.org Description: scim-modules-table - generic tables IM engine module for SCIM platform scim-tables-additional - miscellaneous input method data tables for SCIM platform scim-tables-ja - Japanese input method data tables for SCIM platform scim-tables-ko - Korean input method data tables for SCIM platform scim-tables-zh - Chinese input method data tables for SCIM platform Changes: scim-tables (0.5.11-1) unstable; urgency=low . * new upstream release. Checksums-Sha1: 0c1ac0cede525bea5afa63c3e0109e8bb518703b 2126 scim-tables_0.5.11-1.dsc 25dd1fcc809f57671e7df369f4011c14ba225b6b 4100056 scim-tables_0.5.11.orig.tar.xz 5c4ae88f5c586170304e50ace3e6cda86ff39848 15454 scim-tables_0.5.11-1.debian.tar.gz cb4e1b252049c25ddcb8e70bcdcdb60b83f87bd4 332930 scim-modules-table_0.5.11-1_i386.deb 592c308f0c5f35ad58986c42ccb08a1ba8372ccf 6097166 scim-tables-zh_0.5.11-1_all.deb 818ea0ed75d291e2afbdee0f0defb04ff9eb2182 136590 scim-tables-ja_0.5.11-1_all.deb d3a231e05ed03c9914cdb1292ec6215c33aa90e1 218224 scim-tables-ko_0.5.11-1_all.deb 805df8d381c4a21be617dffbfd842b8d8fc1ecad 114812 scim-tables-additional_0.5.11-1_all.deb Checksums-Sha256: 6dd46ac17ccdb0bcd5a6e603948be0a03dbbedce1f0a7a96a921ef89347e05bd 2126 scim-tables_0.5.11-1.dsc db42c360a46eb8f6ef2ad687577634196f3c12be87c913cad2e29d91fc92ecfa 4100056 scim-tables_0.5.11.orig.tar.xz 607803bb6f283e1853678f12dce7d517d53df7ef4a2703e356e10a748c9f6489 15454 scim-tables_0.5.11-1.debian.tar.gz 2824c692df76c8aaef4c817837ada49c13bc433c1a8b33749897179942c3460a 332930 scim-modules-table_0.5.11-1_i386.deb 67a4b7b2be52c89b046ddc97b2a4447a4c90946834743e61a6492f6de4da0881 6097166 scim-tables-zh_0.5.11-1_all.deb 3dab84e7a9ac9d0a47f56b67860960a927b53d87f02f74bb1b0820a8d4ca1f26 136590 scim-tables-ja_0.5.11-1_all.deb af0f127e77da64cfd60d622e6724b35329550212a7477e3c73b09399e13727d6 218224 scim-tables-ko_0.5.11-1_all.deb e5c94ae6d1f6b8edad0afabf2aac7319a9400f135548e0d4b1a0cb4bc299f884 114812 scim-tables-additional_0.5.11-1_all.deb Files: a4f1c4db0381f26cecd395aae25c910a 2126 utils optional scim-tables_0.5.11-1.dsc cce89b88cf52da2ed8428debc2f5f5c1 4100056 utils optional scim-tables_0.5.11.orig.tar.xz dc4bb76d297c630dd812bd7e1899dd75 15454 utils optional scim-tables_0.5.11-1.debian.tar.gz 380a4bb50efe7d5a40cd7789babefc54 332930 utils optional scim-modules-table_0.5.11-1_i386.deb 1a5b80d5707845e55ca1f3bef083be39 6097166 utils optional scim-tables-zh_0.5.11-1_all.deb b16dc11af38b8e017990db97dc6653fc 136590 utils optional scim-tables-ja_0.5.11-1_all.deb d6e3af67d5d64094733d3dffd4a6ee61 218224 utils optional scim-tables-ko_0.5.11-1_all.deb 579c9c1ecf9e0ede7a367988463997c2 114812 utils optional scim-tables-additional_0.5.11-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP+GaIAAoJEIoKSIdGh69P+T0P/RfkCBKZ4CFm48XFh52+wXv3 DEYex1q+WiIrHYtB+HySp6Txat045gcicZERj+CNMMDKXdgIItoKFsCGwGEss0FL 5eDFRHwIkwEFGQ/Lt2JvJxGYSNLlUpimD+H+/XmrvA3SrrbAhMeNptppClMRlRE/ SAb4Cv7xuYm5qsbN0iTeLIDp7NOLYpeJlnMXeRtCXedL6XSWzBU4Pm0niFeLYIP8 YP7+MzbsOBmFAG29k0zoV3SakOI0PSrGaLBLpPBtibiNn74fJ8ryWPbYBYuAMbKe 7iJovPTrkmKd7QQIkMvPuxYYvMK9arHZ7zoo3pjGDdq65YHC2962sT6bf0XQODDg WBXjbnq0ObAbHG2C81rHANLyMVHwnlv1wxJseQ9imOcz+pyXuAGya0wuUPBso3oL gxmSajtTMwBMxgm6aC+3UZKuw9EmDl5/Zyp9Eiii77X0uCeTg8viKlqu8Eb/MdhS wbbvHD5qE/MXbkMsf4Kd/I7F/ow2jkGFiN9rJ/QQB5YiMsxFLxZ4KwJGNIDx/ILW O3Tks4aoSvqc1h0qmlLTbzLABaJzsllnfG8XCaEE5i9J18iI2gxVQoT0VdC0M05h 1xeC3sw4InGQuLTZazBIbukP7GwW86HfKyoBwWOuU7Ty89sZt1o5pNG8T6pGa0hN VF6C1om+L4XdA+tjmpMt =kmPT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1sreui-000505...@franck.debian.org
scim: problems with libclutter-imcontext*
Hi,
while working on scim, we found that there's a problem that appears to stem from
libclutter-imcontetext-0.1-dev apparently not being multi-arch'ed. I quote from
an email by Tz-Huan:
-- cut
The scim try to figure out the module directory of clutter-imcontext
in these ways:
* search clutter-libdir via `$PKG_CONFIG --variable=libdir
clutter-imcontext-0.1`,
if it successes, set the module directory to
$clutter-libdir/clutter-imcontext/immodules
* otherwise, set the module directory to $libdir/clutter-imcontext/immodules
(libdir is passed when running configure script, so it should be
/usr/lib/${MULTI_ARCH_PATH}
in debian).
In testing, libclutter-imcontext-0.1-dev doesn't multi-archified itself
(http://packages.debian.org/testing/i386/libclutter-imcontext-0.1-dev/filelist),
so scim get /usr/lib from the first step (pkg-config way) and set
the module directory to
/usr/lib/clutter-imcontext/immodules.
However, libclutter-imcontext-0.1-dev does multi-archified in sid
(http://packages.debian.org/sid/i386/libclutter-imcontext-0.1-dev/filelist)
so scim get /usr/lib/${MULTI_ARCH_PATH} from pkg-config and set the module
directory to /usr/lib/${MULTI_ARCH_PATH}/clutter-imcontext/immodules.
-- cut
What would be the preferred way to solve this problem, please?
TIA!
Kind regards,
--Toni++
--
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/20120708122849.ga17...@spruce.wiehl.oeko.net
Re: Improving our response to duplicate packages in Debian
Hi, On Sat, Jun 30, 2012 at 08:41:07AM +0200, Michael Hanke wrote: I think this is approaching the problem from the wrong end. Instead of preserving the status quo and asking oracles to predict the future we should have better means of _removing_ software that has proven to be inferior of an equivalent alternative in Debian. The advantage is that we have objective criteria to be able to make an informed decision -- not a guess based on heuristics and opinion. The disadvantage is that it imposes work on other volunteers -- but see below... well, what do you have in mind? If you happen to think along the lines of bug count per package, that's easily challenged (imho), and defining equivalent is also far from providing an objective criterion. On top of that, I happen to appreciate the choice I have in Debian, instead of the only one true way to do things. Just think of the equivalence between KDE and Gnome, or vim and emacs, for a start. Imho, going that road is the fastest way to wind down our user base to less than a third of the current size. I also think that Craig and Russel are right about the incentives and risks for newcomers not being able to scratch their itch, and failing in a core project. May I ask what are the driving reasons behind the advocated change with respect to our tradision are? Kind regards, --Toni++ -- 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/20120701221120.ga27...@spruce.wiehl.oeko.net
Accepted funkload 1.16.1-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 30 Jun 2012 23:24:09 +0200 Source: funkload Binary: funkload funkload-doc Architecture: source all Version: 1.16.1-3 Distribution: unstable Urgency: high Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: funkload - web testing tool funkload-doc - web testing tool (documentation package) Closes: 659232 Changes: funkload (1.16.1-3) unstable; urgency=high . * added the dependency (Closes: #659232) Checksums-Sha1: bed264da718ce200ad159fc282765d4c7f0c8d24 1770 funkload_1.16.1-3.dsc fc919cb56b6ddbcdc14ec2715384008668b6f8e0 9729 funkload_1.16.1-3.debian.tar.gz 83dd48e8d1ea65a6a1e16d65b0318e4a7d4ef973 111208 funkload_1.16.1-3_all.deb 39fe737557ddfa0cb9198cd7684ddc7ffbb8cea8 107692 funkload-doc_1.16.1-3_all.deb Checksums-Sha256: 85ba163e5e09f543b6cb1cbd49b18e8d3fe109529bf09c8f735756dcff3c02ad 1770 funkload_1.16.1-3.dsc 296182f4e20c133e7f327dd3e16b383173d5bdfc5a47227a088fbca9627fc93d 9729 funkload_1.16.1-3.debian.tar.gz 69bfbf223768e051aab12f2a902756bc1c8b757e09e45e018b1137e23bc746e5 111208 funkload_1.16.1-3_all.deb 77026dbe91be13c67e48c85d3ee3923866ab8ea5e3f6441a2bda67bbbed076df 107692 funkload-doc_1.16.1-3_all.deb Files: a70b8f42ae139ed3810f9537b58dd773 1770 web extra funkload_1.16.1-3.dsc 41d3b8dbb4dd4840dbd7389c72f72103 9729 web extra funkload_1.16.1-3.debian.tar.gz 4fd5bcca6e4faef52e6c957402b988fb 111208 web extra funkload_1.16.1-3_all.deb 8bdc82b2af4da653e25201e371fddb98 107692 doc extra funkload-doc_1.16.1-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP728sAAoJEIoKSIdGh69P4ioP/jmElueGCShvmL18zDXxWUVz 9ZTMe+970pHQQxl03UM61nHr5eLb11ttErCvrFKDbeQMgsx6G+OCNhiSjnvm1T5p lTQW6Yk8gQGUXf0xlXhmigS4n3ALauzWZxDBRFnw4LOssPBRCx9Q2sfrppkCKr/o NKq+wNVzKNyQJzm1f8p7XYp7HhGrTPZqm4az+O8lQur5C4L5yV24LO3M5/09nMxW GDPbV3gJB3OBUVHCYuHpWm7yZDhAHS+6HurwwL3nPYD0iL67CthFkZBv7zyN5kja 0/3xDJZaohQiYnDqYdwVHMvUXjFfJo1yB0qN5hR5Ehd7xUxsU66AGMRSNdqFCW+7 L+Y+PVZoXEsG2KU9VSDSeqU0BPlgvWcD8DFor9l9hZUW9VLxlPB9L9dQPtWC96SP A/u+u1YPvsT6ExfmKQprjmDRBP5D88gCgV0hVl9NdwWKEW4ieZCRGJuCAHiYAX5q HURLe++tQaMquk0MIFydFtYliWERpKK5o7g9MfHZ4h+4vzNpsCkWlZx9JEu3obU4 LPofilD7TfK2uo150AXeAhb7YPigPBcilery8rUVNT0J5lHMN8ExIet+nXoY3uPG PnLVra7b2bUlGSVGCzICOzjzR/F5hZ9B+IZbIi+u2I6oHVyXlcxC7ie2Rxpb6dMa H6/Mo/H2QlFYHMDHTuOq =zCYp -END PGP SIGNATURE- Accepted: funkload-doc_1.16.1-3_all.deb to main/f/funkload/funkload-doc_1.16.1-3_all.deb funkload_1.16.1-3.debian.tar.gz to main/f/funkload/funkload_1.16.1-3.debian.tar.gz funkload_1.16.1-3.dsc to main/f/funkload/funkload_1.16.1-3.dsc funkload_1.16.1-3_all.deb to main/f/funkload/funkload_1.16.1-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/e1sl6vc-00057q...@franck.debian.org
scim and assorted packages
Hi, today I received an email from the FTP masters that a pacakge that is highly relevant to me, has been pulled from Debian. I understand that most folks are now looking at that ibus stuff (which is imho not ready for prime time, yet), but would like to understand better how a package with only 1 normal and 2 minor bugs can be pulled, and... how I can stay at the front of this. /me tries to carve out some time to aid in scim packaging, which still has a *much*, *much* wider range of supported languages and scripts than ibus (saying ibus is a replacement for scim is an euphemism, at best). Kind regards, --Toni++ -- 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/20120627173010.ga12...@spruce.wiehl.oeko.net
Accepted funkload 1.16.1-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 25 Jun 2012 18:12:50 +0200 Source: funkload Binary: funkload funkload-doc Architecture: source all Version: 1.16.1-2 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: funkload - web testing tool funkload-doc - web testing tool (documentation package) Closes: 678043 Changes: funkload (1.16.1-2) unstable; urgency=low . * symlink the JS libraries (Closes: #678043) Note that this only works if the user actually installed the Recommends: . Checksums-Sha1: 8659b5001674e5e6a43afa784f60333cca7f82b0 1770 funkload_1.16.1-2.dsc 96b82ac7eeb608966ee9e3629e34a2bb0306449b 9762 funkload_1.16.1-2.debian.tar.gz 232a43ce4293845758d7ce16cdbb16027135e69b 56 funkload_1.16.1-2_all.deb 752646de0e6068f0921b253e9a1ed9e0a0dc1136 107646 funkload-doc_1.16.1-2_all.deb Checksums-Sha256: aff7de28887fbb6027e35188dac646220cef5b167d7cb96b14cfe05ae3d22434 1770 funkload_1.16.1-2.dsc cf672668d7792d39b3b412c4ce0833c5212973c2cd7dd59745bb2e9504c0c121 9762 funkload_1.16.1-2.debian.tar.gz 7226180e25709d067a4c91e6f1f0216ed0fc3df8fe4abece1f839f8443e0b03d 56 funkload_1.16.1-2_all.deb a8a11836ac48d9e39875b4ffd19ea1870604d42a946db1d3e3a75517f8d1c3e4 107646 funkload-doc_1.16.1-2_all.deb Files: 647582acf333e88140f550dacf36ad5d 1770 web extra funkload_1.16.1-2.dsc 0992fd0c9aa41f70cc2280a0f79d214c 9762 web extra funkload_1.16.1-2.debian.tar.gz 4d46aacad4ecb73b4a2be51534b3f46b 56 web extra funkload_1.16.1-2_all.deb 95c33182ca947faac9af524e9820e172 107646 doc extra funkload-doc_1.16.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP6JI6AAoJEIoKSIdGh69PtZAP/0tkMFt/e11MU+A9XYvo89lg 9mYST6X1DCH0R6diyN1cZHbemmU4ncjeESEq8sr6nj/9vzrvI8YguoEyS1wG6iWZ agkme/bbe0ZGQGt7A0iv+B0102C/PMJy3bA7dR/N6aKy9YJ5OnW6VZM6/ME3KkBb k38binXw8gd5I1rWjtg0V/2z5/JeeATX5Db62KvzKfKWpsp5+sFVHQhKzOxPDp5F h0CiI/5ibbX4ADjVpQ6umSsXDchJyVqFVOoVKl9xhKlHDy7ddm4B55+nNsKhPCyT OCfc3PJbDsSI3U1jmvSv9cARJD46835d5A3R8Py4gUACuLU2+jaO+GO+cujOo/3N MLbjDxedTa3m9q7nueVEpTnxH09Yf3m1x3j3Ycg2x7U0VbzTf7CmuTi/dgVzU3NT Ci5jyAoiKR0KAf5WXYrbSVJ3LlodzhobcS5JnwI7kY/+HiH3ppAiNyvzNZ471J5X WlRkvl/Emrxp0S/gJkkaiK/mfMSqGgV4YtVLCbacQeCcp8hDYuCgFE4xen+yBM3s ow9bM2lrcnm+jRIJwcEedbeTtzUPcvLRwYnajKjwTW1yi8tnIY0B4Riyvsq1XQhC CbM5tqw5ow7S7ev5rn+D8q58U4AhWJc1XjpGfagAo91sYcHaRYzvEHNeZOC4WkaS TcHg8fM2Gj5emMWyAlne =t9UM -END PGP SIGNATURE- Accepted: funkload-doc_1.16.1-2_all.deb to main/f/funkload/funkload-doc_1.16.1-2_all.deb funkload_1.16.1-2.debian.tar.gz to main/f/funkload/funkload_1.16.1-2.debian.tar.gz funkload_1.16.1-2.dsc to main/f/funkload/funkload_1.16.1-2.dsc funkload_1.16.1-2_all.deb to main/f/funkload/funkload_1.16.1-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/e1sjcsi-0005mo...@franck.debian.org
Accepted roundup 1.4.20-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 14 Jun 2012 22:09:29 +0200 Source: roundup Binary: roundup Architecture: source all Version: 1.4.20-1 Distribution: unstable Urgency: low Maintainer: Kai Storbeck k...@xs4all.nl Changed-By: Toni Mueller t...@debian.org Description: roundup- an issue-tracking system Changes: roundup (1.4.20-1) unstable; urgency=low . * New upstream release. * New Maintainer: Kai Storbeck k...@xs4all.nl * Incorporated previous NMU by Gregor Herrmann and Daniel T Chen * patch history-user-escape: dropped - applied upstream (fixed in 1.4.20, issue2550684) * patch fix-email-representation: dropped - applied upstream (fixed in 1.4.19, issue2550691) (1.4.18-1 stated to fix issue2550540, but meant issue2550691) * patch debian-changes-1.4.18-1: dropped - correct a packaging mistake * patch 12_manpage_hyphen_minus.patch: created - correct a lintian warning about upstream manpages * patch 00_licensefiles: created - to correct a lintian warning about upstream license files * fix debian native manpages for the same lintian warnings * Upped standards-version to 2.9.3 * CDBS dropped in favour of debhelper and dh_python2 * Supply a symlink to libjs-jquery's jquery.js Checksums-Sha1: d029e1c1030b50ddead52ebbc5f0fe70784cb77b 1771 roundup_1.4.20-1.dsc 82ee89399caa671c7f3e23e62abc5bf3622a9a48 2127168 roundup_1.4.20.orig.tar.gz 52ad43fa9da20860d7ecff046239b0219bbec967 63638 roundup_1.4.20-1.debian.tar.gz 5cabbdf926e99cbdae4a220fe8c4cff0881858ac 1529284 roundup_1.4.20-1_all.deb Checksums-Sha256: 48a233b372870ddf7f9e5463268a9674cf09f4e2bbbf1761955273891fd22e64 1771 roundup_1.4.20-1.dsc a38a2f4bdf1076f2107de683f1d4e10450edaf94a1be9438198a5cb2241a13a2 2127168 roundup_1.4.20.orig.tar.gz 87e2841496e70b5390dff164d6b3f2c2ad834ea354692394a554c197334a739f 63638 roundup_1.4.20-1.debian.tar.gz 27c6f2a74566f67e503bbc939389b75e611e98d4dc24dca4211804bb9b12995f 1529284 roundup_1.4.20-1_all.deb Files: 89420e0c863737b73451802af251c775 1771 web optional roundup_1.4.20-1.dsc 0672d3435ddb784fcec05a4123faa009 2127168 web optional roundup_1.4.20.orig.tar.gz 5b29c3f1693ce1cac36a626fb883143e 63638 web optional roundup_1.4.20-1.debian.tar.gz c175d11753963315bbe2fd406e40c20e 1529284 web optional roundup_1.4.20-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP35eIAAoJEIoKSIdGh69PVQ0P/1zmCK+cqPPQzRTsFlBZFiE8 FNwjwMUwuad8Hi9y0czTHzUHIK27A+/mvMIX8jJlM50PLVwnvy+CPIbqj2rhQRWg f/iwvA+UFRR9E8gRdTF+TMHTqXmdFJ/WyCTHoePFY+3CBwejQ5XXvDBtC6B7khWw ptJ5WrHt5AdP0vgWWXUEMwPxXOjry+0kr6brv6oQZ7nRY6xI7l+YnBsumyQwKcLE e7t1WYNFFziSEWfI0gyZAOcUDDuj50P1xtwi0ELB3b0AmRFdDwa9mUEk5YBY2E6w fBR7FTwonnNU3kNOXBC77NndJ+0K7kFX8E/7G1ZrcLK0/qL4Ocpb6C2PVkWT9JUj aRHm3+emCCr3T3gufdYbCMy7jLbRtOYBUMxyW7MrPPdtQHKn+rku/hG4IyHvvP2C zZ6KNGIys46AG+5ZTJUXPG/SBNcbHuDFwGho+Dwv0QzxT6vYJD9FUPC72KCXRQeQ q9QXUBPE46vTcwCEbLRsQ9lH+C10qicI5Qk+ZXmmrPBaCZ80OTYHoZPSjZC0eztP Gg5wab4bXcHMoegppAcNdOQWJ5U+Y+Y94Ys3QJ3x6c8RB69ZqqFNsRT7ghrRUrmz gSHoGnACR1Sg7BdrPrw0ukYYTGVwex/El8cLy1DZ8tqKdUFUf4ImXdYDwLoXG+Q6 jr/3764z0EQO6YZrWor6 =w0DW -END PGP SIGNATURE- Accepted: roundup_1.4.20-1.debian.tar.gz to main/r/roundup/roundup_1.4.20-1.debian.tar.gz roundup_1.4.20-1.dsc to main/r/roundup/roundup_1.4.20-1.dsc roundup_1.4.20-1_all.deb to main/r/roundup/roundup_1.4.20-1_all.deb roundup_1.4.20.orig.tar.gz to main/r/roundup/roundup_1.4.20.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/e1sgjcf-00031u...@franck.debian.org
Re: Re: Is Debian affected by the recent MySQL sql/password.c flow?
Hi, On Mon, Jun 11, 2012 at 10:53:50PM +0200, Peter Pöschl wrote: Seems you overlooked this: Debian Unstable 64-bit 5.5.23-2 I just tried on my 32bit machine, and didn't get in in some 50.000 attempts. Also, the squeeze versions are listed under unaffected, which is what reduces the stress level. Kind regards, --Toni++ -- 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/20120612214337.ga26...@spruce.wiehl.oeko.net
Re: gnome is completely f^Mmessed up
On Fri, Jun 08, 2012 at 02:26:23PM +0200, Florian Reitmeir wrote: Norbert Preining wrote: is this only me or do I have the feeling that we are going down the trench with Gnome? ... Is this a joke? Are we going to release that in June/July/whenever? i use gnome too, and for me its working very stable, and gnome3 is way better than gnome2. I've recently tried to use Gnome, too, but while I got the (probably) standard menus, I could not get it to work. Eg. I had 10-30 seconds for every reaction to anything, like moving the mouse. Opening a menu, if it would open, took much longer, but clicking on anything didn't work at all (ie, the menu folded again, but there was no other reaction that I could see. At last, I managed to kill the session and use something else again. Anything else that I tried so far, including KDE, looked rock-solid and lightning fast in comparison. Kind regards, --Toni++ -- 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/20120610014758.ga32...@spruce.wiehl.oeko.net
Re: Idea: mount /tmp to tmpfs depending on free space and RAM
On Mon, Jun 04, 2012 at 06:34:57AM +0300, Serge wrote: 2012/6/3 Toni Mueller wrote: First, there can be rather large session directory, you probably don't want ~365595 files to be always eating your RAM. Well, I much rather want that, or store the session data in memcache, which is almost the same thing, only with a different label. Memcache? (0_o) Imho, that's even worse than store it on tmpfs, since memcache can just push your data off the cache and you'll get it lost even without reboot. I can think of session data in memcache only as some hack for load-balanced servers, Not to be debated - yes, using memcached does create a headache or two, but also solves problems that are otherwise hard. Yes, reboots are rare enough (every few weeks at most) to ignore their adverse side effect on user's sessions - at least in my use cases. but it requires careful memory configuration, otherwise users may find themselves logged off in the middle of a chat. No objections here. Mind you, all these things are done to *prevent* the application from going to disk, and force it to stay in RAM. And that's exactly what I want. You already have a filesystem cache for that. Session data stays in RAM if it is used. But it does not get lost when inactive for a few hours. Well, it doesn't. I have copious memory in a box that is highly underused ( 50%), but still find that interesting files, or file system data, are deleted from that cache. Which leads to very high access times in case I need this data. Plain users I've seen expect their session to stay alive for days. I.e. they have just checked the forum and then turned off PC. When tomorrow they turn it on they expect to be still logged in. Hmmm. First, I'd say that this assumption on their behalf is wrong. Secondly, over here, people tend to be forcefully disconnected at least every 24 hours, forcing a new client IP, anyway. There is no sane way to keep users logged in under these circumstances. They expect this to be true for everything (forums, blogs, web-email, etc). It's a disaster for them to be logged off, it takes hours to find a piece of paper where they wrote the password. They become angry if 10 minutes ago they were logged in and now they aren't, they don't care that I had to reboot the server. Looks like you have a vastly different user population, who also use a vastly different software. My clients' software packages just automatically re-connect, and re-login if possible, in the background. Even Outlook can do it. Not to mention flakey DSL or mobile connections that break your connection more frequently than that. It could be that your users are different. Looks like it, yes. Hardeding[1] stuff, you could get your soft faster just by specifying your exact arch (-march=native). Also for example -fomit-frame-pointer option for x86 can make short functions twice shorter and faster... Uh. Mentioning hardening and suggesting omit-frame-pointer in one sentence makes me shiver. No, I don't optimize for performance at that level, but rather go for portability and safety, if possible. Also, a quick Google search turns up this - maybe out of date - article: http://timetobleed.com/gcc-optimization-flag-makes-your-64bit-binary-fatter-and-slower/ Also, from http://gcc.gnu.org/onlinedocs/gcc-4.6.2/gcc/Optimize-Options.html#Type-punning, it's unclear to me whether omit-frame-pointer will interfere with stack protection schemes, or which one takes precedence. I usually resort to trust in my fellow DDs to do the right things in this area... Kind regards, --Toni++ -- 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/20120604094820.ga18...@spruce.wiehl.oeko.net
Accepted funkload 1.16.1-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 13 May 2012 00:10:08 +0200 Source: funkload Binary: funkload funkload-doc Architecture: source all Version: 1.16.1-1 Distribution: unstable Urgency: medium Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: funkload - web testing tool funkload-doc - web testing tool (documentation package) Closes: 627785 630236 643124 Changes: funkload (1.16.1-1) unstable; urgency=medium . * new upstream * medium because of fix to the build process (closes: #643124) * migrated to using git-buildpackage * added python-webunit to the dependency list (closes: #627785) thanks to Benoit Delbosc * fixed path to demo code (closes: #630236) thanks to Vincent Férotin * split out docs package, which is now using Sphinx * dropped CDBS build dependency * dropped individual documentation building dependencies Checksums-Sha1: 161b2ccbf6f2451426afa96ad4cfe93438a48a2f 1770 funkload_1.16.1-1.dsc 48ada07dfa951f5dd9bc1555f25fb0b6f0bccd16 186031 funkload_1.16.1.orig.tar.gz 7c30c46387ab4cf32fb55e2a5c806d2a94f5ba10 9736 funkload_1.16.1-1.debian.tar.gz e4df8877ef2323fb0cb7137e1ec2d8173785c980 111058 funkload_1.16.1-1_all.deb c1cc4f1669706c523fbce8049c0b039624a4b286 107500 funkload-doc_1.16.1-1_all.deb Checksums-Sha256: 483c4decba4319641203c61994b2ca3114f75c3fb75ed63dde9b6aa3328d81bf 1770 funkload_1.16.1-1.dsc e268a6209e3c225b1af7474031c10c3f92cd28ea8a1226facb5987cde026fb58 186031 funkload_1.16.1.orig.tar.gz 26c56e7d81de33b493c859666309b966d813a4992e1e1187d45e7d6b03524ed0 9736 funkload_1.16.1-1.debian.tar.gz 152f8572c6228727563c51642be63bb120b1a2a354209b6d184f117799bd2edb 111058 funkload_1.16.1-1_all.deb beb1287c7131f827b856339c9ebe5baaa70ce312fdf2ab157265bc27607a57b2 107500 funkload-doc_1.16.1-1_all.deb Files: 91ab4a1a70ef593e7235120d37c178c9 1770 web extra funkload_1.16.1-1.dsc d2e5e5098e332c75b02825ed4318e49c 186031 web extra funkload_1.16.1.orig.tar.gz af6565587a5061c37dc1d9709d902932 9736 web extra funkload_1.16.1-1.debian.tar.gz 1ca41da1d591ca51d8f5096fc50bc6f6 111058 web extra funkload_1.16.1-1_all.deb ecd8b1aba1736fb46ee26f90360c354b 107500 doc extra funkload-doc_1.16.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPy1p7AAoJEIoKSIdGh69PVFIP+wbP70mp94sxEjpls7oT77Cj t5sm8S7hb/b29Rm+okMRx5ifbCJY0NGLOSoRRUN+M0tP3SZ/BFepDigFJjJxBlNQ JHzTOftOtCvjJO57l9nrMhSfaCqzeYs3NsCRqi0gU0HpIvFacJXbjZgqcGQcsVDi 1KJroN7xOSM6Eec7OrFSYm/u0vkpUj117Qv6YQlpSGVrCICo24Z5iI2our8dehxw csPm5KUB4RnNHgtkZXcYVlkNmvFtx5crxEgIk3/FQC4QQE8wm/crpvYl33wCMBvR u6Q7FMJdXPoNdlXZ08gqbny0EhKcacQkKqVTzzTuoRnzZcwNilsnrcCeUeeKYZRU rJWyZIzYJOiJk4jRvcGylp+75gqj/LWMq1/76NJI6CDgGTsWEBdDwjDc/QF0UYEr SdNhsf5iOhKYNY0FJo1q4qABcU8IpQf+05D8TFmfpm4ElBoUi4oOF2r1xK+YlT3F Y8vI6vW0iv/jmbWiPRjLhxFRnEg15+D0HcFYubmr9pr3ZDNjKNmm3nHVl2Vw8VNs V9lg/mN39T8iivfvE9NMvXvJoXkJlxZDPQRWYR0tkcOtKInSsM/CzUXJNesq2ZrW WYIEtF9fNRjxe4CcTIg92m7x5E2zSeHPrCDBN/UwwJLk/oeZG5NItWpPUAPcOcB4 5PsuAqYxmSF1cQH+a9c8 =tx8S -END PGP SIGNATURE- Accepted: funkload-doc_1.16.1-1_all.deb to main/f/funkload/funkload-doc_1.16.1-1_all.deb funkload_1.16.1-1.debian.tar.gz to main/f/funkload/funkload_1.16.1-1.debian.tar.gz funkload_1.16.1-1.dsc to main/f/funkload/funkload_1.16.1-1.dsc funkload_1.16.1-1_all.deb to main/f/funkload/funkload_1.16.1-1_all.deb funkload_1.16.1.orig.tar.gz to main/f/funkload/funkload_1.16.1.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1sbeeg-0004iu...@franck.debian.org
Re: Starting services automatically after install
On Sun, Jun 03, 2012 at 08:21:34AM +0200, Bernhard R. Link wrote: * Aaron Toponce aaron.topo...@gmail.com [120602 16:26]: However, I am calling into question the validity of starting a service by default post-install. I think it introduces security concerns, possible headaces on the local LAN, and just unnessary work for the administrator. Other than if you don't want a service, don't install the package agrument, I don't understand why services _should_ be started by default post-install. Try to see it from the other side: I don't understand why you would a like a service not started by default. I would like to install the software, but have my own startup procedure in many cases. Also, it's much easier to just install a package in order to start reading the man pages, than manually grabbing the package file, manually unpacking it somehwere as a user, and then manually touring the included documentation. So yes, I will most likely run the software at some point, but frequently prefer to conduct some in-depth studies first - sometimes, a Debian package deviates considerably from upstream's or other distributions' conventions. The daemon is there to be run, so running it is the most sensible approach in almost all cases[1]. Since we obviously can't agree on *how* the service is to be run, one could just ask the user, eg., in the case of a printing service: I just installed the file sharing service. Do you want to start sharing immediately (will allow other people to access files/media/printers)? But for a more real-world example, consider slapd, which also starts immediately, but is imho quite unlikely to be configured appropriately by Joe Average User who doesn't understand that he needs to start Samba before being able to share his files, and which is impossible to configure appropriately by answering debconf questions in the first place? If a service comes with a default config that can be a real security concern, then that alone needs fixing. Many services come, eg. Apache comes with it, too (and eg. grabs all sockets it can, one of my pet peeves). As administrator I also prefer that I just have to copy a config and install the package. Anything not run by default (or at last by default once its configuration is complete) means I have to tweak another config file, which is uncessary annoying work. You have to say something like '/etc/init.d/service restart', anyway, after you put your own config into place. What's so much different from saying '/etc/init.d/service start' instead, in such a case? Asking the unwitting user and providing a default answer of 'yes' should solve the problem, imho - the slightly more experienced user can then at least opt for 'no'. Kind regards, --Toni++ -- 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/20120603094024.ga28...@spruce.wiehl.oeko.net
Re: Starting services automatically after install
On Sat, Jun 02, 2012 at 08:21:02AM -0600, Aaron Toponce wrote: Enabling services on external interfaces by default is indeed a bug, IMO, especially things like SSH, DHCP, SMTP or Bind (which has a long history of security problems). sidetracking SSH is imho the one exeption to the rule, provided it has PermitRootLogin set to either no or without-password, instead of yes. Kind regards, --Toni++ -- 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/20120603100444.gb28...@spruce.wiehl.oeko.net
Re: Idea: mount /tmp to tmpfs depending on free space and RAM
On Sat, Jun 02, 2012 at 05:11:16PM +0300, Serge wrote: 2012/6/2 Toni Mueller wrote: Eg. web application's session data very frequently goes there, and/or the sysadmin wants it to go onto a tmpfs. First, there can be rather large session directory, you probably don't want ~365595 files to be always eating your RAM. Well, I much rather want that, or store the session data in memcache, which is almost the same thing, only with a different label. Mind you, all these things are done to *prevent* the application from going to disk, and force it to stay in RAM. And that's exactly what I want. Second, session data MUST NOT be lost on reboot by default. Why not? I could not care less for the loss of session data every once in a while. People will log in again if their CMS backends really logged them out because of that, if anything, but session data is created for about every visitor, or spider, that hits the site(s), and will be forcefully cleaned up by cron-jobs, anyway. Not my code, so blame someone else. So even without /tmp, sysadmin should not put session data on tmpfs. I am unconvinced. You can store your session data wherever you like, but I prefer RAM. There're different admins, however... Yes, looks like it. No need to. You only need to add -pipe to your *FLAGS. You don't build software with default autotools flags (-g -O2) anyway, I guess. Well, usually I do, except that I usually only compile C friends, not write it. Kind regards, --Toni++ -- 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/20120603204546.gb18...@spruce.wiehl.oeko.net
Re: Starting services automatically after install
Hi Bernhard, On Sun, Jun 03, 2012 at 01:51:33PM +0200, Bernhard R. Link wrote: * Toni Mueller t...@debian.org [120603 11:41]: Since we obviously can't agree on *how* the service is to be run, one could just ask the user, eg., in the case of a printing service: The print servers I looked at did not allow remote access by default since somewhen in the 90ties. I was only cobbling together an example for the mechanism for asking the user I had in mind. Office stuff is not my usual realm of work, and printing services are office stuff. What has slapd to do with samba and why don't you want it run? Since you were talking about samba, and since LDAP is the standard network-wide address book mechanism usually in place, I consider slapd a standard office ingredient like samba (I've used it for different purposes for several years, but decided to part with it). As stated, the reason why a stock slapd installation is not that useful, is that it is extremely hard to do some schema chances, should you have the need for them, after the database has been installed, and that ACLs and such are outside of the realm of the package installation. So if you need one of a non-standard schema, a custom ACL, or something else, like replication, you are (afair) out of luck with just the debconf-powered postinst, and need to hand-tune the configuration. Running with the default database is at least a nuisance in this situation. actually I'd be quite confused if slapd had not been already running after installing... Huh??? Sorry, you have to explain this. Do you claim apache has a security concern in its default config? No, but for me, it has a usability problem in the default config. But then, I'm doing away with it as best as I can, anyway. That I do not have to do it? Either I have copied the config first or for a full install that will get a reboot anyway when deployed. The common case is probably more like I want service X, now I install the package and see how I can configure it to suit my needs. In the meantime, one has to prevent the service from doing anything unwanted. If you have a config before installing the software, we are talking about a completely different use case that would likely include a lab setup as well. I don't ask that Debian be optimized for that case. Asking the unwitting user and providing a default answer of 'yes' should solve the problem, imho - the slightly more experienced user can then at least opt for 'no'. That's called policy.d. (though I feel like repeating others here). Thanks for pointing it out. I'll take a look. Kind regards, --Toni++ -- 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/20120603210052.gc18...@spruce.wiehl.oeko.net
Re: Starting services automatically after install
Hi Phil, On Fri, Jun 01, 2012 at 07:49:03PM +0100, Philip Hands wrote: The Debian approach has always been to not install anything that you don't intend to use. I have brought up this topic in the past, too. Summary: I often do want the Debian-packaged software on my systems, but use it entirely differently from what the package maintainer had in mind when he created the package. Eg. restring services to certain IPs, configure ACLs, change locations, running not under init but runit instead, whatever. It is also to ensure that if you do choose to install something, it should be doing something useful by the end of the install (if possible, security considerations allowing). I can actually do that. Please note that this problem only ever affects services, and the person who is going to run a service will have to do one additional action if the service is not being started right away (start it if he is satisfied with the default configuration), whereas everyone with different requirements, and it's very easy to run into such a situation, will have to scramble to avoid doing that. Makes unattended operations more difficult, imho. the user for configuration questions -- RedHat just want the software to install, whereas Debian wants it to be useful, so may need to ask questions. The package maintainer can do only so much to make a package useful right away, and certainly not cover many interesting cases from the real world, due to lack of time, or also imagination, or expertise. Both approaches are valid, and are mostly a matter of taste. If you are using a distribution that uses one assumption, it's not useful to start introducing packages that work on the opposite assumption. I was never under the assumption that it was Debian's policy that made the system this way, but only the superiour packaging system that enables this kind of configuration to be done at package-install-time. And what if you had set the debconf value for the user interface to noninteractive? Start the service, anyway? It's just safer to not start the service immediately after installation. Eg. when I recently installed some nova* packages on one system, they destroyed that system because of missing/wrong configuration and the unability to cope with the situation they found, but nevertheless cheerfully started immediately, anyway, with no way for me to anticipate and/or prevent that situation... major bummer (I'm just recovering from it)! If you don't like the assumptions, you are much better off switching to a distribution that you prefer, rather than trying to persuade the overwhelming majority of the people that like the current assumptions, and use Debian because of those assumptions, that they should change their minds because they are supposedly wrong for liking it that way. These are *quite* strong words, imho. Whoever wasn't aware of these assumtions, or doesn't have a dedicated opinion, would probably object to being pocketed like this. I also think that there are more, other reasons for choosing Debian, not only this habit. Kind regards, --Toni++ -- 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/20120602111809.ga20...@spruce.wiehl.oeko.net
Re: Moving /tmp to tmpfs makes it useless
Hi Thomas, On Sat, Jun 02, 2012 at 07:33:26PM +0800, Thomas Goirand wrote: All the complaints about /tmp as tmpfs come down to one simple issue: The size of the tmpfs isn't chosen well. It would be more constructive to find a better heuristic for the size there. No. The complain is that it will never be big enough for some cases. If you tell me that it should be twice as big as now, then I'll tell you: what if we have to handle files twice as big as what you thought to begin with? that problem applies to disks as well, and especially to small / partitions, if you don't have /tmp somewhere else. If we are talking by making /tmp its own file system, that's ok, but if we are talking about manually relocating it to (say) /var/tmp, then we've made exactly as much progress as we would have made by making it tmpfs by default: We then require the user to manually intervene and change the default. don't force it to all users as a default which might break and that some users wont understand. This is just too risky to have some users saying linux is crap, libreoffice can't open big PPT files, it gets horribly slow, then crashes the whole system so much that I have to reboot. Probably that's wrong, but it's still going to be the comments of our users. You certainly can't cover all edge cases, and especially non-technical users have just too many ways to break any system, as well as usually being too rash to investigate. My suggested fix for this problem is to install a ~/tmp upon account creation, and set the TEMP environment variable in, say, /etc/environments. That *should* fix up all cases except for rogue applications that don't honour $TEMP. We can then proceed to fix these over time, while not demanding too many changes to the general setup. And fwiw, the user's home is supposed to be big enough for all such cases where the user is non-technical, but still his own systems administrator - the case you are highlighting. Kind regards, --Toni++ -- 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/20120602114619.gb20...@spruce.wiehl.oeko.net
Re: Idea: mount /tmp to tmpfs depending on free space and RAM
On Fri, Jun 01, 2012 at 07:00:52PM +0300, Serge wrote: Well, nobody named the benefits yet. Just the problems. There were a Well, I named one on 28th of May. Did you read it? Kind regards, --Toni++ -- 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/20120602115220.gc20...@spruce.wiehl.oeko.net
Re: Moving /tmp to tmpfs makes it useless
On Mon, May 28, 2012 at 08:26:52AM -0400, Weldon Goree wrote: at some point). Much better developers than me seem to have formed this opinion too (cf browsers' behavior while it waits for you to tell it what to do with an unknown content-type: it's a disk-based pipe to whatever program you pick to open it, except now it's a memory-based pipe, and I think /tmp on tmpfs is breaking those developers' expectations). As for Iceweasel, there is a bug in Mozilla's database that addresses exactly this problem. In the overwhelming number of cases of people downloading large files via their web browser, these files are going to end up somewhere in their homes, anyway, so the initial downloaded fragments should be stored there. Although I haven't paid attention to that bug as of late, I do remember seeing some activity going on there, and I think the Mozilla developers have been finally convinced to adopt a different strategy. I'd be more comfortable with tmpfs if it could be quota'd with standard quota tools. If this part goes to your home, it's automatically quota'ed. Having /var/run on a tmpfs may be a good idea, though. Gah! I want *somewhere* I can park stuff on disk. Why are people so against that? Nobody is against that, only that you insist on using /tmp for it, which is imho not a good assumption to make. we going to do? Right now on my Squeeze laptop I have /lib/init/rw, /dev/shm, and /tmp. Do we really need more things that look like on-disk directories but aren't? (Then again I'm still grumpy about sysfs.) Though actually /var/run makes more sense than /tmp, since it's pretty much just for pids and sockets. Without doing much (that I can remember) to my box, I see this on Testing: $ mount|grep tmpfs udev on /dev type devtmpfs (rw,relatime,size=4018332k,nr_inodes=205757,mode=755) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=804880k,mode=755) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=307200k) tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,relatime,size=1609760k) $ Enjoy! dropping arbitrarily large files into it (I'm looking at you, Iceweasel...) and as long as there's *some* section of actual disk somewhere that's 1777. As I said, there was /usr/tmp, but I think it was shot down. But I suggest /srv/tmp or something like that. Kind regards, --Toni++ -- 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/20120530002030.ga32...@spruce.wiehl.oeko.net
Re: Moving /tmp to tmpfs makes it useless
Hi, On Fri, May 25, 2012 at 02:22:24AM +0300, Serge wrote: What's a temporary file? Really, why would applications temporarily store its data in a file? They do that to *free some memory*. Placing those files back to memory renders the whole process of writing the file useless. If the files are small and can stay in memory why would application save it to file? how, or why, would an application know that I have enough memory to keep it all there, while you don't? The fail-safe way to code an application without copious special-casing is to use a file and then let the systems administrator decide what to do with it. If the application insists on keeping everything in memory, the systems administrator can, at best, add more swap, but if it uses a file, he can decide either way. Since it's only reasonable to store large data sets in temporary files, standard sets no size limits for these files. So if application's author had actually read FHS he should expect these directories to handle large files. It's not, see below. Also, most of the time, /tmp goes into / (on smaller systems), and is thus typically *very* much limited in space. Granted, the user can relocate /tmp to another place later, once he became aware of the limit... Running out of space in /tmp should be a one-time event for any system that one installs, since thereafter, /tmp will have enough space configured for the desired purposes. No need to make it non-tmpfs. Who uses /tmp = Let's check the real world and see what applications actually use /tmp. And the most important thing: file managers, browsers, image editors, cd burners — these are not some rare scientific stuff, but a common programs, that most people use every day. Putting them on a small tmpfs will break them. Putting them on large tmpfs may slow down or freeze the system due to heavy swapping. I wanted to make the argument that php uses /tmp as the session save path (it used to be there), but discovered, that someone has re-configured that to now be in /var/lib/php5, so I'd say put that on a tmpfs as well. Lots of small files with frequent accesses... whoever wants those on a real disk?!? is to extend partitioner with a new option Configure tmpfs partitions. That option should allow to mount anything as tmpfs (not just /tmp, but also /var/run, /media, /opt or whatever the user might want). It would be nice to have the `size` option there as well. Having /var/run on a tmpfs may be a good idea, though. Q: I extremely care about my / fs and want to use it as rarely as possible. A: There're a lot of options: * symlink or mount-bind /tmp to i.e. /home/tmp * have /tmp on a separate partition (common and probably best solution) * you hate partitions? make /home/tmp_ext3fs.img and loop-mount it. That would solve your problem without making your system unstable because of high memory usage, or break programs because of no free space in /tmp. It used to be /usr/tmp in olden days, just to have that out of / and give it more space at the same time, too. One might also consider to then merge /tmp with /var/tmp, eg. by way of symlinking them, as the one who is strapped on memory, might as well be strapped on Internet bandwidth to download that unfinished ISO that blew up his /tmp on tmpfs, then re-getting the rest of it after rebooting... Q: /tmp on tmpfs increases apps performance. A: What apps? Real apps don't write files during performance-critical operations. Even if they do, they write large files. And large files are Dead wrong. Eg. web application's session data very frequently goes there, and/or the sysadmin wants it to go onto a tmpfs. Q: gcc writes small files in /tmp A: usually it does not, especially when used with -pipe option Changing all (generated?) Makefiles floating around out there, and getting the changes committed upstream to actually benefit from that is easier than using a tmpfs, of course. That's it. Thanks for reading. PS: should I had filled this as a bugreport? I request that the bug be tagged wontfix. Kind regards, --Toni++ -- 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/20120528110346.ga19...@spruce.wiehl.oeko.net
Re: Packaging on GitHub ?
On Sun, May 27, 2012 at 05:58:55PM +, Thorsten Glaser wrote: Charles Plessy dixit: upstream source moved to GitHub, and we would like to try to maintain the Debian package there as well. This is not a good idea: http://mako.cc/writing/hill-free_tools.html MUCH seconded. Thanks for sharing the link! Kind regards, --Toni++ -- 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/20120528111603.gb19...@spruce.wiehl.oeko.net
Re: big .debian.tar.xz - EG Wordpress
On Wed, May 16, 2012 at 05:53:11PM +0800, Paul Wise wrote: On Wed, May 16, 2012 at 5:45 PM, Russell Coker wrote: Would it be possible to have somewhere on the Debian servers for storing such files so that they can be referenced in a README file or something rather than sent to everyone? I'm sure that most people who build a Wordpress package won't use them. If I downloaded a source package and didn't get source I would be most unimpressed. Seconded! If you say download some, and ignore the others in most cases, please consider that in the case you really find out that you need the source, you'll most likely be offline, and cannot do much about it (Murphy's laws apply generously). So I'd say, better get the whole chunk in one go to be safe. Imho, much of the value of being entitled to have source is in actually having it, instantanously, as opposed to merely having a legal option to get it somehow, sometime. Of course, YMMV. Kind regards, --Toni++ -- 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/20120517101054.ga10...@spruce.wiehl.oeko.net
Re: big .debian.tar.xz - EG Wordpress
On Thu, May 17, 2012 at 03:56:25PM +0100, Jon Dowland wrote: Hopefully you've got the build-dependencies too. Which, if the source packages were split off into other packages, you'd then pull in. Being able to read the source code can often get you quite far already, but yes, usually, I want all the build dependencies and a locally runnable copy, 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/20120517161426.gb10...@spruce.wiehl.oeko.net
Re: Wheezy release: CDs are not big enough any more...
Hi, On Mon, May 14, 2012 at 09:34:39AM -0700, Steve Langasek wrote: So to use the image you need either a DVD or a USB stick, and if you're using a write-once DVD you're perhaps wasting the unused space; but the download time and install footprint are still kept low and in the range of what a CD would give. my biggest gripe with DVDs is that they decay so quickly. A DVD, being only a few months old, has already a high risk of being non-functional, while a CD easily lasts more than a year. Kind regards, --Toni++ -- 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/20120515093147.ga4...@spruce.wiehl.oeko.net
Re: Bug#672695: wordpress: no sane way for security updates in stable releases
On Sun, May 13, 2012 at 09:56:17AM -0700, Russ Allbery wrote: packaging and security issues and is because we need N independent installations per server for different groups that can vary separately and That's one reason why packaged versions of web apps are quite often useless at my workplace, too. We're finding it very hard to use the packaged versions of large web application frameworks for a variety of reasons. One of the big ones is that web developers seem to expect a very fast upgrade cycle that's hard The requirement for fast upgrade cycles partly stems from the huge attack surface that Internet-facing web apps have. It also stems from the generally short turnaround times for new releases of software and applications built on top of said web apps, as users keep demanding more and newer features. to support in Debian; another is that it is really helpful for web applications to be able to give an entirely independent installation to each major site rather than trying to share the same code. For another Ack. That's also one factor driving the demand for virtual servers (xen, kvm, you-name-it). Just my 0.02 cents... Kind regards, --Toni++ -- 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/20120514130420.ga8...@spruce.wiehl.oeko.net
openvz, was: Re: Bug#672695: wordpress: no sane way for security updates in stable releases
On Mon, May 14, 2012 at 04:23:27PM +0200, Adam Borowski wrote: This reminds me: is anyone going to bring back vserver or openvz in some I'm for having openvz back, then. Can we have this in a separate thread, please? Kind regards, --Toni++ -- 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/20120514143723.gb8...@spruce.wiehl.oeko.net
Re: Bug#672695: wordpress: no sane way for security updates in stable releases
On Mon, May 14, 2012 at 03:53:25PM +0100, Ben Hutchings wrote: On Mon, May 14, 2012 at 04:23:27PM +0200, Adam Borowski wrote: This reminds me: is anyone going to bring back vserver or openvz in some form? Ola Lundqvist o...@inguza.com had plans to do this in an OpenVZ-hosted repository. Sounds good... Otherwise, wheezy would end up with no containers. Xen does kernel virtualization and thus takes an order of magnitude more memory, lxc is not supposed to be secure (it provides a chroot with usage limits, but no isolation). User IDs and capabilities aren't yet properly namespaced. So you can't create a container-root user to manage the container from the inside, and you can't rent out a container as a VPS. But that's a major application of this technology. That doesn't mean we have 'no containers'. But in practice, it means that many users have to migrate, or abstain from upgrading. Or will lxc be completely ready for Wheezy? Kind regards, --Toni++ -- 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/20120514145840.gc8...@spruce.wiehl.oeko.net
Re: Bug#672695: wordpress: no sane way for security updates in stable releases
Hi, On Sun, May 13, 2012 at 11:26:26AM +0100, Ben Hutchings wrote: The value is the same as for most packages: it's easy to install and easy to upgrade (I assume; I don't use Wordpress). Yes, the expected if someone in Debian would want to make that effort, I'd say that Wordpress and the like should go to squeeze-updates (volatile was a better name, imho). But then, to be useful, some serious work would probably have to go into the package, as just running it on top of Apache + mod_php seems to be one of the least desirable options. Kind regards, --Toni++ -- 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/20120513121201.gb20...@spruce.wiehl.oeko.net
Re: On init in Debian
On 03/17/2012 01:40 PM, Philip Hands wrote: On Sat, 17 Mar 2012 18:23:57 +0800, Thomas Goirand z...@debian.org wrote: NAME=package-binary-file DESC=package daemon description [ -e . /usr/share/sysv-lib/debsysv-lib ] debsysv-init-lib $@ I'm happy to help with that ... although, I doubt we're the first people to think of something like this, and it would be a shame to ignore an existing solution. OpenWRT does something quite interesting, which is that they have an /etc/rc.common and then make the init scripts start thus: Any others? As you are contemplating non-Linux systems anyway, maybe this might be of interest to you, too: http://www.openbsd.org/cgi-bin/cvsweb/src/etc/rc.d/ -- Kind regards, --Toni++ -- 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/4f72da81.7070...@debian.org
Re: leaks in our only-signed-software fortress
On 02/18/2012 11:48 AM, Thomas Koch wrote: What about a debhelper script that receives an URL (or set of mirror URLs) and a SHA1 and does the download and check? If you're going this way, try to peek at the *BSD's ports systems, specifically their 'distinfo' files. SHA1 is not enough, imho. -- Kind regards, --Toni++ -- 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/4f440fb6.5020...@debian.org
Accepted python-webunit 1:1.3.10-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 21 Feb 2012 00:53:38 +0100 Source: python-webunit Binary: python-webunit Architecture: source all Version: 1:1.3.10-2 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: python-webunit - Unit testing for web apps with code that acts like a web browser. Changes: python-webunit (1:1.3.10-2) unstable; urgency=low . * Re-did the archive after moving to git, building it to verify the work. * Standards update to 3.9.2. Checksums-Sha1: a5e07c472b47f4c648b93e2e748591f241374228 1156 python-webunit_1.3.10-2.dsc 2e4c6697abf72af528db0263afb6c40b27a2820c 3058 python-webunit_1.3.10-2.debian.tar.gz 751512b2381f19bd777468864b327fadaadb5c75 28338 python-webunit_1.3.10-2_all.deb Checksums-Sha256: 6eaa58c8bcfb8f20b4a3f58c16530252336cd595784246691d2a33835d8381b8 1156 python-webunit_1.3.10-2.dsc c6fb06da4eba780d091b8d64de223c69b20606c6051e8fe2be557829f1bb1490 3058 python-webunit_1.3.10-2.debian.tar.gz 112abd0ddb1bfb9cca56b3dc00d664835e0e4840efa562cf0024f82fb2a5 28338 python-webunit_1.3.10-2_all.deb Files: 47a1998bf434e83e9cda1934e5d0ed02 1156 python optional python-webunit_1.3.10-2.dsc e8e5f639bd2147a556c1b1c896bcb9a8 3058 python optional python-webunit_1.3.10-2.debian.tar.gz 9fa1ec27170d144aa28e7356e8ec0c47 28338 python optional python-webunit_1.3.10-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk9C42cACgkQfoEUoHXLGtI+9ACdEOOZvOZm3Mr4RpaX8hY+9PW8 O/kAnifmWsJnoBVKj5l72LkEbEYmOUpE =1YUB -END PGP SIGNATURE- Accepted: python-webunit_1.3.10-2.debian.tar.gz to main/p/python-webunit/python-webunit_1.3.10-2.debian.tar.gz python-webunit_1.3.10-2.dsc to main/p/python-webunit/python-webunit_1.3.10-2.dsc python-webunit_1.3.10-2_all.deb to main/p/python-webunit/python-webunit_1.3.10-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/e1rzdfx-0004jb...@franck.debian.org
Re: from / to /usr/: a summary
On 12/21/2011 11:55 AM, Russell Coker wrote: Nowadays 100G disks are small by laptop standards and for desktops 1TB is about the smallest that anyone would buy. Focussing on the desktop is the core of this - imho - misguided idea. I'd still like to be able have a small, self-contained, Debian that I can run on about anything. /usr is where all the real bloat (Gnome etc.) lies, which may or may not be available, and if you eg. consider your favourite phone storage, that's 512MB internally, or similar, with /home presumably on an external storage (SD card). Things have changed a lot since the FSSTD first came out. Indeed. Nowadays, we should support a much wider range of devices, not just computers the size of refrigerators. -- Kind regards, --Toni++ -- 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/4f004b35.2040...@debian.org
Re: 486 still being sold NEW / was Re: Increasing minimum 'i386' processor
On 11/21/2011 07:52 PM, Ben Hutchings wrote: Since we're theorising, rather than talking about actual users, my theory is that these are sold as replacements for installed systems, which will run the exact same software as the original - not Debian 7.0. It would be silly to start a new deployment reliant on parts that have already been EOL'd. I may be mistaken, but the CPUs listed there are not original Intel, but some clones that still could or could not be in production. Seeing that these 486-class devices specify DDR2 as their memory interface suggests that they are really not that old. -- Kind regards, --Toni++ -- 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/4edeac94.3090...@debian.org
Accepted roundup 1.4.18-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 14 Jun 2011 15:20:29 +0200 Source: roundup Binary: roundup Architecture: source all Version: 1.4.18-1 Distribution: unstable Urgency: medium Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: roundup- an issue-tracking system Closes: 605882 616637 Changes: roundup (1.4.18-1) unstable; urgency=medium . * new upstream 1.4.18 (closes: #605882) * closes several security holes * replaced deluser and delgroup by userdel and groupdel, thanks to Holger Levsen (closes: #616637). * added debian/pyversions, but a little stricter than upstream * unified included jQuery libraries to be 1.4.2, but ignore the existing Debian package for the moment. * Fixes for upstream issues 2550540 and 2550684 Checksums-Sha1: b5a635bbba0e3962216382a50f2c6fb3be28703a 1044 roundup_1.4.18-1.dsc 4e54f8cd585ddab163b621ff2dd8545636d605bc 2526143 roundup_1.4.18.orig.tar.gz 3f1c8e467a6f8ba99239336bcf716755da0aceb4 64155 roundup_1.4.18-1.debian.tar.gz 1cd375ecc0dcc29e4a9e8839d0079b9c321cea79 1690362 roundup_1.4.18-1_all.deb Checksums-Sha256: e44c2005f9dfed4d08f32b92152c8b430e0bb1ccb1b76bc95df813b265cb6dad 1044 roundup_1.4.18-1.dsc 993434286eb64e1f553c31d57b8bb3a72a5b1472a7845a0a7d40a9674a29e335 2526143 roundup_1.4.18.orig.tar.gz 2882f738f744e63dfe4410316cae9b476752227dd7ac4e94923a2c9a66d93c31 64155 roundup_1.4.18-1.debian.tar.gz e9d5706ca48b5766652f1219472860b28bc76c228179d0fa4c0432a7b0161a0b 1690362 roundup_1.4.18-1_all.deb Files: abc06e2d7d17b63e988561306e061dc8 1044 web optional roundup_1.4.18-1.dsc e2a0a433ace12eb615cec43ec61f68cf 2526143 web optional roundup_1.4.18.orig.tar.gz 693d2ceb8bac66cede6499b4f35de768 64155 web optional roundup_1.4.18-1.debian.tar.gz 8b7bf1ea5d8d9fb72ea675e725f36abb 1690362 web optional roundup_1.4.18-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFN943tfoEUoHXLGtIRAvkBAKDPqigdBH5STfrkq8cIOnQLhFsDIgCgjJGA r+GSbresOFrm6DUixbYIeD0= =3ErU -END PGP SIGNATURE- Accepted: roundup_1.4.18-1.debian.tar.gz to main/r/roundup/roundup_1.4.18-1.debian.tar.gz roundup_1.4.18-1.dsc to main/r/roundup/roundup_1.4.18-1.dsc roundup_1.4.18-1_all.deb to main/r/roundup/roundup_1.4.18-1_all.deb roundup_1.4.18.orig.tar.gz to main/r/roundup/roundup_1.4.18.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/e1qwwms-0003dr...@franck.debian.org
Re: MBF alert: packages with very long source / .deb filenames
Hi, On Fri, 25.03.2011 at 14:17:06 +, Steve McIntyre st...@einval.com wrote: If we really want to meet the spec, we should be aiming for 64 characters, but that affects 98 packages and I'm not *too* bothered about it since testing shows no issues thus far. I'm tempted to file: * serious bugs on the packages over 90 characters * normal bugs on those over 80 * wishlist bugs on those over 64 Thoughts? just a shot into the dark: Would it be feasible, or at least possible, to file bug reports with upstream to have the permissible length of filenames officially extended? I mean, everyone has started to use long file names, haven't they? Kind regards, --Toni++ -- 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/20110410171942.19993.qm...@oak.oeko.net
Re: Misc Developer News (#24)
Hi, On Sun, 07.11.2010 at 11:45:05 +0800, Paul Wise p...@debian.org wrote: Screenshots on packages.d.o --- You may have noticed that packages.d.o now includes screenshots[1] with a link to a the Debian screenshots site[2]. Where a screenshot isn't available a No screenshot available image invites users to submit screenshots. I guess the majority of packages don't lend themselves to have a screenshot. All libraries, and many daemons, come to mind. Would it be possible to exclude the screenshot feature for such packages? It always takes some time to find the no screenshot available image, which makes the p.d.o site even slower than it already is. Kind regards, --Toni++ -- 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/20101117101020.12662.qm...@oak.oeko.net
Accepted postfix-cluebringer 2.0.10-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 15 Aug 2010 13:05:15 +0200 Source: postfix-cluebringer Binary: postfix-cluebringer postfix-cluebringer-pgsql postfix-cluebringer-mysql postfix-cluebringer-sqlite3 postfix-cluebringer-webui Architecture: source all Version: 2.0.10-1 Distribution: unstable Urgency: low Maintainer: Nikolai Lusan niko...@lusan.id.au Changed-By: Toni Mueller t...@debian.org Description: postfix-cluebringer - anti-spam plugin for Postfix postfix-cluebringer-mysql - metapackage for mysql support in postfix-cluebringer postfix-cluebringer-pgsql - metapackage for postgresql support in postfix-cluebringer postfix-cluebringer-sqlite3 - metapackage for sqlite3 support in postfix-cluebringer postfix-cluebringer-webui - anti-spam plugin for Postfix Closes: 577270 Changes: postfix-cluebringer (2.0.10-1) unstable; urgency=low . [Nikolai Lusan niko...@lusan.id.au] * Initial release (Closes: #577270). * Add system user and group 'cluebringer'. * Add Readme.Debian for webui package. * Switch to dpkg-source 3.0 (quilt) format. . [Toni Mueller t...@debian.org] * Updated to current standards version * ripped out all dbconfig-common stuff * added some upstream patches Checksums-Sha1: 69ae7ff5f38df62a59abd7601b2c1965b3202ea1 1268 postfix-cluebringer_2.0.10-1.dsc a2f0c9954e64dd74056913deb861b9559a45b3df 133135 postfix-cluebringer_2.0.10.orig.tar.gz ecdf1e0fce38b8385ff5b0d12d8327195dd58455 20880 postfix-cluebringer_2.0.10-1.debian.tar.gz 1de616103a9fc1e6e8803f648a361166d016a4d0 72392 postfix-cluebringer_2.0.10-1_all.deb 64ad4e7dd741b99b45c84b5e5c6a7a2b6b518760 16964 postfix-cluebringer-pgsql_2.0.10-1_all.deb 3e47a219fb339d4edd93b4a7bd24c9f941300742 16962 postfix-cluebringer-mysql_2.0.10-1_all.deb f08b4ec7691a5d4717702ad76366d8d074a773eb 16954 postfix-cluebringer-sqlite3_2.0.10-1_all.deb ef409190c3a1774fe4ec29736415cf28554d7281 84726 postfix-cluebringer-webui_2.0.10-1_all.deb Checksums-Sha256: 96a6d91d26a194b13cbbf6aa431e9fc3d96a188afe2650cec9f15a58e0d9aa0c 1268 postfix-cluebringer_2.0.10-1.dsc fb202ada6490562ce3221df43cd9402d20f395b280eee559231b24983e8281c2 133135 postfix-cluebringer_2.0.10.orig.tar.gz cca1162680485203c56c6ead3f62067d1d3bceef6bd0e49c7ddd0f41b08886cf 20880 postfix-cluebringer_2.0.10-1.debian.tar.gz 15e81df28bd4a548a63fd7eb6819485a13b9d2b25e0c03cbb8ea9db9177c3a7c 72392 postfix-cluebringer_2.0.10-1_all.deb 496cad34cb32fe53e03f929aa602d56ad2624d0ef958ac1841d5439fd6cc59b4 16964 postfix-cluebringer-pgsql_2.0.10-1_all.deb 0b3b280fbda7059e2fc23eb5213cf5e2759c6ac3fc203e56fbb06256c9e7b66b 16962 postfix-cluebringer-mysql_2.0.10-1_all.deb 9a945f9f5f94d7e45f17256a7c492ee6774ae938a349b5b538738707776e9de8 16954 postfix-cluebringer-sqlite3_2.0.10-1_all.deb b7c47c696b3c1dd3fd9310312d0e5005348d8fa0e241e1ff289c9dc89f7079bf 84726 postfix-cluebringer-webui_2.0.10-1_all.deb Files: 9fc11f87431ad5865ad23ebc0c05b157 1268 mail optional postfix-cluebringer_2.0.10-1.dsc eb6b9040cd323f58b7223d1994a52964 133135 mail optional postfix-cluebringer_2.0.10.orig.tar.gz 82450f635d3d06abf05bcca09ea73fc9 20880 mail optional postfix-cluebringer_2.0.10-1.debian.tar.gz 96c207e9a3f244cb479de34136ea1667 72392 mail optional postfix-cluebringer_2.0.10-1_all.deb 57333a8891d837e9ae8e859ebf574e88 16964 mail optional postfix-cluebringer-pgsql_2.0.10-1_all.deb 9c8543c708593a2a9e6ae450622e0ec9 16962 mail optional postfix-cluebringer-mysql_2.0.10-1_all.deb 7b833a281608911b4b91b08c458b38d1 16954 mail optional postfix-cluebringer-sqlite3_2.0.10-1_all.deb f72821593ca830c4be3a6a317d441c94 84726 mail optional postfix-cluebringer-webui_2.0.10-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMZ+BjfoEUoHXLGtIRAnQzAKDdL8rgsm6dCmDka5vcsTiKLGDsWgCcDmc9 WyeMImzBZb+fACOayYS4Ook= =Fje0 -END PGP SIGNATURE- Accepted: postfix-cluebringer-mysql_2.0.10-1_all.deb to main/p/postfix-cluebringer/postfix-cluebringer-mysql_2.0.10-1_all.deb postfix-cluebringer-pgsql_2.0.10-1_all.deb to main/p/postfix-cluebringer/postfix-cluebringer-pgsql_2.0.10-1_all.deb postfix-cluebringer-sqlite3_2.0.10-1_all.deb to main/p/postfix-cluebringer/postfix-cluebringer-sqlite3_2.0.10-1_all.deb postfix-cluebringer-webui_2.0.10-1_all.deb to main/p/postfix-cluebringer/postfix-cluebringer-webui_2.0.10-1_all.deb postfix-cluebringer_2.0.10-1.debian.tar.gz to main/p/postfix-cluebringer/postfix-cluebringer_2.0.10-1.debian.tar.gz postfix-cluebringer_2.0.10-1.dsc to main/p/postfix-cluebringer/postfix-cluebringer_2.0.10-1.dsc postfix-cluebringer_2.0.10-1_all.deb to main/p/postfix-cluebringer/postfix-cluebringer_2.0.10-1_all.deb postfix-cluebringer_2.0.10.orig.tar.gz to main/p/postfix-cluebringer/postfix-cluebringer_2.0.10.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
Re: recovering from compromised keys
Hi, On Thu, 23.09.2010 at 15:13:06 +0100, Simon McVittie s...@debian.org wrote: Needing an unencrypted /boot just means you have to distrust /boot after you lose and then regain control of your laptop. this probably means that you have to do this everytime you've set the device aside, or after you wake up in the morning, because there's probably only half as much fun for three-letter agencies if you *know* that they (or someone, the thief) interfere(s). -- Kind regards, --Toni++ -- 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/20100924123154.32494.qm...@oak.oeko.net
Re: Downloading Testing with Jigdo unsupported?
On Tue, 24.08.2010 at 22:12:37 +0800, Paul Wise p...@debian.org wrote: Probably you are looking for this? http://cdimage.debian.org/cdimage/weekly-builds/i386/jigdo-cd/ Yes. The link to this isn't published prominently, but I found it at last. Thank you! -- Kind regards, --Toni++ -- 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/20100824151537.19166.qm...@oak.oeko.net
Downloading Testing with Jigdo unsupported?
Hi, I was under the impression that Testing installer images should be auto-generated on a weekly basis. Now I look at http://www.debian.org/CD/jigdo-cd/, and at http://cdimage.debian.org/cdimage/squeeze_di_alpha1/i386/jigdo-cd/ and find that the images are all actually several months old, while at this place http://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/ images are fresh. What gives? Kind regards, --Toni++ -- 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/20100823184204.23253.qm...@oak.oeko.net
Accepted roundup 1.4.15-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 17 Aug 2010 21:41:10 +0200 Source: roundup Binary: roundup Architecture: source all Version: 1.4.15-3 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: roundup- an issue-tracking system Changes: roundup (1.4.15-3) unstable; urgency=low . * Fix typo (closes upstream issue 2550665) The typo prevents users from registering. Checksums-Sha1: af5e38292110162a7261fb336c82713e85502356 1044 roundup_1.4.15-3.dsc 07de5073cc501b573c9a328e2e7f5bb7c073f775 25548 roundup_1.4.15-3.debian.tar.gz 83606832f35046ad5718d20745dce3e469b7cc23 1364342 roundup_1.4.15-3_all.deb Checksums-Sha256: d6698295e640040aeed2519fb7ff8db61f33b7e622540672f42925bba6c55637 1044 roundup_1.4.15-3.dsc a6b03680dff49dfbac355e826561ec2e7d0ee481f7fdaff9354dfe228af1e5b6 25548 roundup_1.4.15-3.debian.tar.gz 7db395fb9e48e531b6419a60e86a3fc54c37b023a960c2501a799b06e325922d 1364342 roundup_1.4.15-3_all.deb Files: c1a050c2201b8b8690ee813154e081eb 1044 web optional roundup_1.4.15-3.dsc 131788298be7dd07905a6ca1f3913157 25548 web optional roundup_1.4.15-3.debian.tar.gz 174b6c00c1fc6bf790af123f8cf0624c 1364342 web optional roundup_1.4.15-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMaum1foEUoHXLGtIRAtlDAKDU21sRdZPXfx3BTNqCd8Q/sSrsSQCfa0NG bZLQdDHTNsSdpPXIzlTQeUg= =Mik8 -END PGP SIGNATURE- Accepted: roundup_1.4.15-3.debian.tar.gz to main/r/roundup/roundup_1.4.15-3.debian.tar.gz roundup_1.4.15-3.dsc to main/r/roundup/roundup_1.4.15-3.dsc roundup_1.4.15-3_all.deb to main/r/roundup/roundup_1.4.15-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/e1olt7k-0004o0...@franck.debian.org
Raw Idea: one more control field for sponsors
Hi, while working on a package I'm going to sponsor, it occurred to me with all the DD, DM and sponsoring going on, that I'd like to have a field in debian/control, like eg. Bugs-To: some...@debian.org, ... to have some...@debian.org automatically subscribed to the bugs for this package, much in the same vein as the 'Uploaders:' field works. I have found out that there are other ways to get at the bug reports for some random package, but this could probably simplify things from the perspective of a sponsor. I would also like to know whether you think it is a good idea that a sponsor be automatically subscribed to the bugs for all packages he sponsors. Kind regards, --Toni++ -- 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/20100811090138.14674.qm...@oak.oeko.net
Re: Raw Idea: one more control field for sponsors
Hi, On Wed, 11.08.2010 at 17:48:09 +0300, Eugene V. Lyubimkin jac...@debian.org wrote: Toni Mueller wrote: in debian/control, like eg. Bugs-To: some...@debian.org, ... This is the info which IMHO belongs to PTS and should stay there. after rethinking the issue, I agree that it's better to not add a field to the debian/control file. Originally, I thought it would simplify things, but I'm no longer convinced. -- Kind regards, --Toni++ -- 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/20100811211823.3697.qm...@oak.oeko.net
Accepted funkload 1.13.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 08 Aug 2010 19:24:57 +0200 Source: funkload Binary: funkload Architecture: source all Version: 1.13.0-1 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: funkload - web testing tool Closes: 592079 Changes: funkload (1.13.0-1) unstable; urgency=low . * new upstream release * moved to new packaging scheme * fixed debian/control (closes: #592079) Checksums-Sha1: c147281975caf7d04af8540941e1523d9e4d03a5 1068 funkload_1.13.0-1.dsc 6b13844255ce108eb2f08a6e9bcb1bc9bc89b473 120101 funkload_1.13.0.orig.tar.gz 2dad5b5cf84150d4468c5231763a93efdd460e43 28696 funkload_1.13.0-1.debian.tar.gz b03ba4ed9d005efc4542a266d44a30b74d23c919 163876 funkload_1.13.0-1_all.deb Checksums-Sha256: 506c7f8de40695b9ba7a3a2a2f1231b15cf2d8c660f13c566c2c6c16e5637c4d 1068 funkload_1.13.0-1.dsc 39439301985994440ed9778106d5c0ec4286af062e9073b79f0437f6b887a1ee 120101 funkload_1.13.0.orig.tar.gz 938fab6180c2cff463f1cc3643708b9e27cb8a90524ba438ee370e2b62a35acd 28696 funkload_1.13.0-1.debian.tar.gz 623cf4c05e5560f071ef33f796bd5adb16fc6d3df70e4a3e16fa9e4a57296102 163876 funkload_1.13.0-1_all.deb Files: e3f7b52b3c48fca0cf95dfe23900e81f 1068 web extra funkload_1.13.0-1.dsc 2018bf702dd30b30174af2d97cae66b1 120101 web extra funkload_1.13.0.orig.tar.gz 2e165085845b13891b4ef843e2bdb73d 28696 web extra funkload_1.13.0-1.debian.tar.gz b91fdca9b70bcdffcc4aa4937f66dee4 163876 web extra funkload_1.13.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMYDGGfoEUoHXLGtIRAiO4AJ4q25CJ8DW+IN6ZlZ+ok/PX3zcjsACg0/UC QuzNWY1q+FgVYHmcsyCezAI= =Aqlt -END PGP SIGNATURE- Accepted: funkload_1.13.0-1.debian.tar.gz to main/f/funkload/funkload_1.13.0-1.debian.tar.gz funkload_1.13.0-1.dsc to main/f/funkload/funkload_1.13.0-1.dsc funkload_1.13.0-1_all.deb to main/f/funkload/funkload_1.13.0-1_all.deb funkload_1.13.0.orig.tar.gz to main/f/funkload/funkload_1.13.0.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1oivji-sw...@franck.debian.org
Accepted roundup 1.4.15-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 08 Aug 2010 17:52:11 +0200 Source: roundup Binary: roundup Architecture: source all Version: 1.4.15-2 Distribution: unstable Urgency: medium Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: roundup- an issue-tracking system Changes: roundup (1.4.15-2) unstable; urgency=medium . * fixing programming errors, upstream issue 2550661 * correcting packaging error which omitted several conffiles Checksums-Sha1: 6199a6a0e28f986431cf03e27377a617ba1f8629 1053 roundup_1.4.15-2.dsc 0ac4b3529141a43832137d445e8b08843daf63eb 25205 roundup_1.4.15-2.debian.tar.gz 6c472ffa64db0d8194a2628e43ad67199053f6f5 1364278 roundup_1.4.15-2_all.deb Checksums-Sha256: 9a6ce3a503febaac9bf6c881a7b4de68b5f08a976af81722130d4add6dc32af6 1053 roundup_1.4.15-2.dsc 2dc9b17accbfd2cd5662a0c8a84dba7e70b1a4446c765deaee3212bfb58da4fd 25205 roundup_1.4.15-2.debian.tar.gz 79bac7bd2288ff24824b9b447d017cb5c6c0ffc1340b239a1b05ffa900ec867b 1364278 roundup_1.4.15-2_all.deb Files: bf23a3c2870d5fa70c0cb4e5313aa473 1053 web optional roundup_1.4.15-2.dsc d27c8031661c0f55603f1e9b40fa938a 25205 web optional roundup_1.4.15-2.debian.tar.gz 4226d025812b04e383d7884684d6c60e 1364278 web optional roundup_1.4.15-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMXtdpfoEUoHXLGtIRAiQ7AJwJjK9NKK+dEcnSM1p1ZyE78+S48QCfcfaz Ar8ak+ZGTP0izw31JcqErzg= =WOrT -END PGP SIGNATURE- Accepted: roundup_1.4.15-2.debian.tar.gz to main/r/roundup/roundup_1.4.15-2.debian.tar.gz roundup_1.4.15-2.dsc to main/r/roundup/roundup_1.4.15-2.dsc roundup_1.4.15-2_all.deb to main/r/roundup/roundup_1.4.15-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/e1oi8ye-00069z...@franck.debian.org
Accepted roundup 1.4.15-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 07 Aug 2010 16:47:00 +0200 Source: roundup Binary: roundup Architecture: source all Version: 1.4.15-1 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: roundup- an issue-tracking system Changes: roundup (1.4.15-1) unstable; urgency=low . * New upstream * Switch to dpkg-source 3.0 (quilt) format * Appropriated patches which predate my maintainership of this package (sorry, I'm still fighting with the tools). Please send corrections my way. Checksums-Sha1: 0a43c21823de6fba778cb5dc649423d56f232295 1047 roundup_1.4.15-1.dsc 98cd2e1ae5edd795a2b2c83d5f9854704855721b 1440997 roundup_1.4.15.orig.tar.gz 0d4e2378c1b2d25951f16cf49484f45459eb8ca9 25463 roundup_1.4.15-1.debian.tar.gz bb10604fbc4bb4f32602d46f0e9241a63744e561 1362542 roundup_1.4.15-1_all.deb Checksums-Sha256: b1ec5cd6808e9a39bf9d3c729afa07b4c38a01d5038c098c1eac7c7fdc4c8130 1047 roundup_1.4.15-1.dsc 5dd652b96abbfff4be57a7d39c7fc126f69f86058c2f6d4aefbb2d6d96bf02d9 1440997 roundup_1.4.15.orig.tar.gz 1f7597a58847bf223077a2ad95b0b83aad959f7cd1ebdeb29351c96e1dcea0b4 25463 roundup_1.4.15-1.debian.tar.gz 53b367597c7cc2bf33a2fc0f86efa7c050c0af69c726ed7025f1760e21710efe 1362542 roundup_1.4.15-1_all.deb Files: d0a60f041d50b03790dad6ea363ed132 1047 web optional roundup_1.4.15-1.dsc 65af27f02ff0aef9d6babc7373d426b9 1440997 web optional roundup_1.4.15.orig.tar.gz 1b0e658f0b2f6371049247292e99d186 25463 web optional roundup_1.4.15-1.debian.tar.gz dea751da006d00a2ded375b629691b9f 1362542 web optional roundup_1.4.15-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMXYvFfoEUoHXLGtIRArTOAJ9ngCI84P/Adl2r2pH/9vVD9XFzWQCgtj82 nn7VZ5Du/P/rCaGVM2at7Yw= =Pqqj -END PGP SIGNATURE- Accepted: roundup_1.4.15-1.debian.tar.gz to main/r/roundup/roundup_1.4.15-1.debian.tar.gz roundup_1.4.15-1.dsc to main/r/roundup/roundup_1.4.15-1.dsc roundup_1.4.15-1_all.deb to main/r/roundup/roundup_1.4.15-1_all.deb roundup_1.4.15.orig.tar.gz to main/r/roundup/roundup_1.4.15.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ohmys-000870...@franck.debian.org
Accepted python-webunit 1:1.3.10-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 07 Aug 2010 19:19:09 +0200 Source: python-webunit Binary: python-webunit Architecture: source all Version: 1:1.3.10-1 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: python-webunit - Unit testing for web apps with code that acts like a web browser. Changes: python-webunit (1:1.3.10-1) unstable; urgency=low . * new upstream * updated to new packaging format 3.0 (quilt) Checksums-Sha1: c126aabdc1419b0f113cc6ceaa70bb32ae3ef579 1074 python-webunit_1.3.10-1.dsc 42e62b8f4680006dcc577e49e7e192a5c0249ada 23111 python-webunit_1.3.10.orig.tar.gz af84325c00340b6d5e5688bba591f218263e19e6 3065 python-webunit_1.3.10-1.debian.tar.gz 21bdce62c7357035000971496b6e22e54e8a2b98 28062 python-webunit_1.3.10-1_all.deb Checksums-Sha256: b91bc13d0afce5efe62d2935b6f636ef5d4afe352f77f85742e29fe096c5e672 1074 python-webunit_1.3.10-1.dsc 7202d855db0f501f8a59995ec0b4913ce227c52e7d93766dfa71348fdac68603 23111 python-webunit_1.3.10.orig.tar.gz 19bac0610ce19ed9e009c2764538727fadbdf136872dff7a4153385ea6cffd30 3065 python-webunit_1.3.10-1.debian.tar.gz 9b2f22d0d6535a3fab30633d54a3af21cbfd6c820b73264f980fd19c1fe6b457 28062 python-webunit_1.3.10-1_all.deb Files: f460678e8de25fb20efa40d7ad1e9a56 1074 python optional python-webunit_1.3.10-1.dsc 9ad536608a4e4d2ec19da8529683149e 23111 python optional python-webunit_1.3.10.orig.tar.gz 0629cefeb971042eb245fa20a67db1c5 3065 python optional python-webunit_1.3.10-1.debian.tar.gz f78c4dc893c4803f6f0daa209cd951fd 28062 python optional python-webunit_1.3.10-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMXZd2foEUoHXLGtIRAgELAKDPLBqudxerU4PP9P9ipQ2dv0jpOACgmx2u 2bU2pEaOxAQWR1+9iqoEUR4= =Ucya -END PGP SIGNATURE- Accepted: python-webunit_1.3.10-1.debian.tar.gz to main/p/python-webunit/python-webunit_1.3.10-1.debian.tar.gz python-webunit_1.3.10-1.dsc to main/p/python-webunit/python-webunit_1.3.10-1.dsc python-webunit_1.3.10-1_all.deb to main/p/python-webunit/python-webunit_1.3.10-1_all.deb python-webunit_1.3.10.orig.tar.gz to main/p/python-webunit/python-webunit_1.3.10.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/e1ohnji-0005tf...@franck.debian.org
Re: Xen for Squeeze, 3.4 or 4.0
Hi, I know that I'm a bit late... On Thu, 10.06.2010 at 17:54:28 +0200, Bastian Blank wa...@debian.org wrote: My personal preference would be to go with 4.0. If it's one, then I opt for 4.0. Thank you very much! Kind regards, --Toni++ -- 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/20100719104308.5890.qm...@oak.oeko.net
Bug#560244: ITP mysql-cluster
Package: wnpp Severity: wishlist Owner: Toni Mueller t...@debian.org * Package name: mysql-cluster Version : 7.1.3 Upstream Author : Oracle * URL : http://dev.mysql.com * License : GPLv2 Programming Lang: C, C++ Description : cluster-enabled version of the MySQL database system Some time ago, MySQL upstream separated the development of the regular MySQL server, and MySQL-Cluster. Since, the Debian MySQL-Packagers Team has dropped the support for clustering from the regular MySQL server package. This package is inteded to fill the gap and bring MySQL cluster support back to Debian. Any help, esp. by the MySQL Packagers Team, would be MUCH appreciated. Kind regards, --Toni++ -- 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/20100615153304.32279.qm...@oak.oeko.net
Accepted roundup 1.4.13-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 02 May 2010 17:36:05 +0200 Source: roundup Binary: roundup Architecture: source all Version: 1.4.13-3 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: roundup- an issue-tracking system Closes: 579927 Changes: roundup (1.4.13-3) unstable; urgency=low . * adapt to new Xapian API, thanks to Olly Betts (closes: #579927) Checksums-Sha1: 54d1a219b8b43e3002e9cd8e0b4d3d44ce245cad 1035 roundup_1.4.13-3.dsc 2af6956f635f7661cea7a0de291408d301e739ba 22944 roundup_1.4.13-3.diff.gz 53c8b1683ca76293bf5550fe557ec9f08d3863a4 1362936 roundup_1.4.13-3_all.deb Checksums-Sha256: a060dc9dabf006919aabe17dc0adeea80437fa49008e282ac2f0aa9223343c77 1035 roundup_1.4.13-3.dsc 28310510a122a91c46642dce4655800e75e55c17f9f8585394f325de910b8512 22944 roundup_1.4.13-3.diff.gz 809164572579863a6548585efa57c06691e1ad91287c474084e9b1de78c8 1362936 roundup_1.4.13-3_all.deb Files: 3d5aaa0b03a4c9955576bddfe66c5afa 1035 web optional roundup_1.4.13-3.dsc bcd28a80b3f3fccb695dd8e991a0e7ac 22944 web optional roundup_1.4.13-3.diff.gz bcfa8c3ab12c47edc931fcc3b4300185 1362936 web optional roundup_1.4.13-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFL3x0cfoEUoHXLGtIRAqa4AJ9OXS+FMy3Kaeekg3uLgFp/0ouLDgCfTwc8 BDtGYTPP4DmoEiCKCpBJHyA= =oq+h -END PGP SIGNATURE- Accepted: roundup_1.4.13-3.diff.gz to main/r/roundup/roundup_1.4.13-3.diff.gz roundup_1.4.13-3.dsc to main/r/roundup/roundup_1.4.13-3.dsc roundup_1.4.13-3_all.deb to main/r/roundup/roundup_1.4.13-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/e1o91ew-0004tl...@ries.debian.org
Accepted funkload 1.11.0-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 02 May 2010 22:00:21 +0200 Source: funkload Binary: funkload Architecture: source all Version: 1.11.0-3 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: funkload - web testing tool Closes: 579743 Changes: funkload (1.11.0-3) unstable; urgency=low . * adds python-setuptools (closes: #579743) Checksums-Sha1: 2d7fd7c450eb43f2afe5dde1430839fd93f1fe80 1043 funkload_1.11.0-3.dsc 85de8f260bfaacb555806d4f9dbef674cda0f2f6 103455 funkload_1.11.0-3.diff.gz 5fe91ab06dca773d7cd0e9cd43dd43a30933dd45 151138 funkload_1.11.0-3_all.deb Checksums-Sha256: a50accec7a6e3cedbf9ed444a8b10a52a7e676bf11aa453c22c48f6fe6905f9e 1043 funkload_1.11.0-3.dsc d40b7cf6efd5324e8ae935eee5ca1fb770d8253e70da1bd90ff39ce7f5563f97 103455 funkload_1.11.0-3.diff.gz 7cbaebb8c41c65f2f89e183ed43483a4c847f0d6967df5be4f5ef89f53b2e8f3 151138 funkload_1.11.0-3_all.deb Files: 086623d953f82e46bf64e28bbffdba0e 1043 web extra funkload_1.11.0-3.dsc 3c23cf45dbc43a7cc006023fc48f97cc 103455 web extra funkload_1.11.0-3.diff.gz 3d412fcb87e917c8170695baea21f3bd 151138 web extra funkload_1.11.0-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFL3dtYfoEUoHXLGtIRAupRAKC2waBpXljhO1avppZsL6WoHTT+ZgCgjTbf u//PGkDGVZX9PqRcSNlcu+E= =GJJP -END PGP SIGNATURE- Accepted: funkload_1.11.0-3.diff.gz to main/f/funkload/funkload_1.11.0-3.diff.gz funkload_1.11.0-3.dsc to main/f/funkload/funkload_1.11.0-3.dsc funkload_1.11.0-3_all.deb to main/f/funkload/funkload_1.11.0-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/e1o8h5k-0006ix...@ries.debian.org
Accepted funkload 1.11.0-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 02 May 2010 22:08:53 +0200 Source: funkload Binary: funkload Architecture: source all Version: 1.11.0-4 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: funkload - web testing tool Changes: funkload (1.11.0-4) unstable; urgency=low . * correct build error Checksums-Sha1: 09b57fd6ad8685335a0a0e2464e97ec4a3c21dda 1040 funkload_1.11.0-4.dsc cde2b6b2778b4ccfafbdda1b216695c07cc09ae3 27848 funkload_1.11.0-4.diff.gz 516a8fdbc3a541b15e7c0fc89d4c6d11dd54876b 151172 funkload_1.11.0-4_all.deb Checksums-Sha256: 31be7f20b1c8b44db8f42b085ee83c9e4e9a084204bf1b8d53af24c7765ec266 1040 funkload_1.11.0-4.dsc 88efb303035218454278668d2c12fd773ec9d1ac81de63323c3a02471740cd4c 27848 funkload_1.11.0-4.diff.gz e7321bf6c1b1ea72f716a22881d45a1007733684d238a642a06a1f37a403fc0d 151172 funkload_1.11.0-4_all.deb Files: 92d2256393e7dad925e976e20b404055 1040 web extra funkload_1.11.0-4.dsc d5bf2d2ba20db7da0b0298c22fcdaa88 27848 web extra funkload_1.11.0-4.diff.gz 74dcb4f074f23b3f595dfb9ccf3b852d 151172 web extra funkload_1.11.0-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFL3eDbfoEUoHXLGtIRAiT+AKCQGVb8IkXo8vodDFOzKEzrYjhhVACdHTvh YGsYow7ZLIeHofflsKVlzzE= =v07Y -END PGP SIGNATURE- Accepted: funkload_1.11.0-4.diff.gz to main/f/funkload/funkload_1.11.0-4.diff.gz funkload_1.11.0-4.dsc to main/f/funkload/funkload_1.11.0-4.dsc funkload_1.11.0-4_all.deb to main/f/funkload/funkload_1.11.0-4_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/e1o8h5g-0006lm...@ries.debian.org
Accepted roundup 1.4.13-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 24 Apr 2010 22:54:28 +0200 Source: roundup Binary: roundup Architecture: source all Version: 1.4.13-2 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: roundup- an issue-tracking system Closes: 577184 577186 Changes: roundup (1.4.13-2) unstable; urgency=low . * unbreak upgrades * remove reference to Sqlite2 (closes: #577184) * adapt the README.Debian to the current state of affairs (closes: #577186) Checksums-Sha1: 1f7cbebdb9fc41a5135e545c3407fedf89029bf1 1035 roundup_1.4.13-2.dsc c060d4e708c5278a7e60e8986b6a66bf5beb8c11 22639 roundup_1.4.13-2.diff.gz f57713c15775b1fe07937606ec9b9d7ea029a380 1362910 roundup_1.4.13-2_all.deb Checksums-Sha256: 71a111b2c377a5a6581b8cd0112cb70b5f3ccaf152878e4883f1d744eb9f2e5e 1035 roundup_1.4.13-2.dsc 499a5a5ac4b2b18646a8981843a3c7d06dc5b042f2bbe0a37c00227d156687dc 22639 roundup_1.4.13-2.diff.gz c5d3e9992f89ae5bdda2bddde50c2b1816b382c3393f40faa02bb29df3242240 1362910 roundup_1.4.13-2_all.deb Files: 12edc7a09864b9ec56e6529b14897e50 1035 web optional roundup_1.4.13-2.dsc 0373acf773041a2b4cfad37eeaf1f7cf 22639 web optional roundup_1.4.13-2.diff.gz 1c9db1266d450fbbf630c1be03db063e 1362910 web optional roundup_1.4.13-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFL01vxfoEUoHXLGtIRAmGJAKCEdr2wgL7/7A0CHpHAAvormht8sACeJgEM KjagBAhu2gb94fuj+sMtkRg= =SLl7 -END PGP SIGNATURE- Accepted: roundup_1.4.13-2.diff.gz to main/r/roundup/roundup_1.4.13-2.diff.gz roundup_1.4.13-2.dsc to main/r/roundup/roundup_1.4.13-2.dsc roundup_1.4.13-2_all.deb to main/r/roundup/roundup_1.4.13-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/e1o5mzl-0005ko...@ries.debian.org
Re: taxbird co: please provide updates via volatile
Hi, On Fri, 09.04.2010 at 19:30:43 +0200, Emilio Pozuelo Monfort po...@debian.org wrote: On 09/04/10 10:05, Toni Mueller wrote: I suggest that updates to taxbird and its dependencies are provided via volatile. Why do you mail -devel and not taxb...@p.d.o or the maintainer or the bts? I was unaware of the 'taxb...@p.d.o' mail address, and thought that someone else than the original maintainer(s) should do the work. -- Kind regards, --Toni++ -- 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/20100410085948.21004.qm...@oak.oeko.net
taxbird co: please provide updates via volatile
Hi, I suggest that updates to taxbird and its dependencies are provided via volatile. Reason: Users of taxbird have to comply with certain legal requirements, and eg. Lenny's version of taxbird is unfit to create tax reports for this year, while the version in Testing pulls in a significant number of other (Gnome?) stuff, which I find undesirable. I would therefore like to see taxbird updates via volatile, so that users of Stable can actually use it during the lifetime of the release. FWIW, I've created a (rough) backport that's available from my p.d.o homepage. Kind regards, --Toni++ -- 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/20100409080556.29077.qm...@oak.oeko.net
Accepted roundup 1.4.13-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 04 Apr 2010 01:45:05 +0200 Source: roundup Binary: roundup Architecture: source all Version: 1.4.13-1 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: roundup- an issue-tracking system Changes: roundup (1.4.13-1) unstable; urgency=low . * new upstream Checksums-Sha1: 716fc6858d1221b4284a9821dc356b81585f9945 1035 roundup_1.4.13-1.dsc e3426c03cbdd5ad7e1dc768531ec09ff774b6b00 1435278 roundup_1.4.13.orig.tar.gz 8086a04cd3c1ce44526d102466124db193fd617b 22391 roundup_1.4.13-1.diff.gz 675b8ca2e203fd5e542bdb45bc59ce264062f7d1 1362492 roundup_1.4.13-1_all.deb Checksums-Sha256: 54cb8cc258469fe69db17ff2872d41048074fdd5813e30f0df4da8844c784d9c 1035 roundup_1.4.13-1.dsc 561b2a8939f601e596a00c83893aba164b9526c05948ee46c633d6440d80536f 1435278 roundup_1.4.13.orig.tar.gz 107a030e6f3ef3af2857bb577005ae89db82b592c25394019752b3f8fd6a5fa4 22391 roundup_1.4.13-1.diff.gz 1f7a8a23a6c6b2338d4f9e3a6688abf9e920ecdf47b92ab4647dfadf80e1a799 1362492 roundup_1.4.13-1_all.deb Files: 5af9ab2eba13e40556ab34d3de418c29 1035 web optional roundup_1.4.13-1.dsc 18d0b6ae08ab9943f5f5fb0a1f8cbe8c 1435278 web optional roundup_1.4.13.orig.tar.gz 390246f5f5622f9f7e8e20975bf98bce 22391 web optional roundup_1.4.13-1.diff.gz b5bd3f37e137942606ad087cb236d908 1362492 web optional roundup_1.4.13-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLuhdefoEUoHXLGtIRAnoEAKCLr9G+e2MKBxGnp5PFfsDJ9SW3TgCeNE+P 60y0U1a8NwXkwN8Tbue28+U= =mOs2 -END PGP SIGNATURE- Accepted: roundup_1.4.13-1.diff.gz to main/r/roundup/roundup_1.4.13-1.diff.gz roundup_1.4.13-1.dsc to main/r/roundup/roundup_1.4.13-1.dsc roundup_1.4.13-1_all.deb to main/r/roundup/roundup_1.4.13-1_all.deb roundup_1.4.13.orig.tar.gz to main/r/roundup/roundup_1.4.13.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/e1nyqcy-xg...@ries.debian.org
Re: Best practices for development workstations
Hi, On Wed, 31.03.2010 at 08:46:01 +0100, Holger Levsen hol...@layer-acht.org wrote: On Dienstag, 30. März 2010, Marco Túlio Gontijo e Silva wrote: squid! (Or any other normal http proxy. I don't recommend any apt-proxy solution...) Can you explain why? apt-proxy had issues when I tried (as well as others, which I cannot rememeber now), me too. Apt-proxy has a very unpleasant tendency to simply hang every now and then, and has almost been declared deprecated. approx iirc requires to changes /etc/apt/sources list, squid always Yes. You need to point your sources.list to the apt-proxy instance. worked for me and never had issues, squid is useful for more then just proxying apt repositories, squid can be set up as a transparent proxy quite easily, updating a full/partial mirror usually takes more bandwidth then just using a proxy. Actually, squid has its own slew of problems. Eg. I've yet to see a machine where Squid runs reliably under anything resembling a reasonable load, instead of falling over frequently, and it can be difficult to have the features work that you want in such a setting. Eg. Lenny's version of Squid doesn't work for me on Lenny. I'm currently test-driving apt-cacher-ng, which has it's own bag of problems so far, but seems to be lighter and so far more reliable than apt-proxy. Kind regards, --Toni++ -- 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/20100403154808.5655.qm...@oak.oeko.net
Re: Xen, Squeeze, and Beyond
On Sat, 27.02.2010 at 21:59:39 +0100, Tollef Fog Heen tfh...@err.no wrote: ]] Faidon Liambotis | Beyond that, I've also seen filesystem corruption when using live | migration and the filesystem cache hasn't been disabled -- an almost | undocumented directive of libvirt's XML. | | All in all, I'm wondering how people can call this stable. I would guess at most people not using live migration and so never hitting those kinds of problems. I have not used live migration, either, but unless Michael Tokarev's efforts turn out to be fruitful, I'll be out of KVM due to much bigger problems than a non-working live migration, and at that point, Xen would be the only alternative. Thanks to Faidon for the heads-up on the heads-up on this migration problem! Kind regards, --Toni++ -- 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/20100321174025.27505.qm...@oak.oeko.net
Re: Bits from the release team: Release schedule; the RT needs YOU
Hi, On Mon, 08.02.2010 at 20:13:48 +0100, Marc Brockschmidt h...@debian.org wrote: we wish to freeze only after the number of these bugs has dropped below the mark of 300. As you can see on the usual overview pages [RC-Bugs], great decision, imho. Work towards fixing these bugs is greatly appreciated. We will use our release superpowers to aggressively remove leaf packages from testing (in fact, another round of removals happened on the weekend). What's the current policy about NMUs, then? Kind regards, --Toni++ -- 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/20100215181552.20911.qm...@oak.oeko.net
Accepted funkload 1.11.0-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 03 Feb 2010 01:04:29 +0100 Source: funkload Binary: funkload Architecture: source all Version: 1.11.0-1 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: funkload - web testing tool Changes: funkload (1.11.0-1) unstable; urgency=low . * new upstream, compatible with both webunit 1.3.8 and 1.3.9 Checksums-Sha1: 68506950b9bd31d3708e77575c27c063815f2f2f 1041 funkload_1.11.0-1.dsc 450b93139710c344490ccc89a202f9953d3f9c1b 117912 funkload_1.11.0.orig.tar.gz 7199965407aa675dbdcb47aa6df7d19ed410c6fd 101738 funkload_1.11.0-1.diff.gz f8d7c45427015ce448e0eda52760b1fccfc883ed 149866 funkload_1.11.0-1_all.deb Checksums-Sha256: 742e1d9ecfb46d885593a9d15a2717e794602bbe6afe4fd35b49f5d3409278af 1041 funkload_1.11.0-1.dsc f8d0c7fa648100f70b7a81bb9ad79b3543da6cf8cf1df943d80cdbfd006fcc48 117912 funkload_1.11.0.orig.tar.gz aa8c806f1950edac38783c9918aab75d0a942d6ffbb9d1408d11a2fc520d57be 101738 funkload_1.11.0-1.diff.gz 190530115a27a2ebab43a24cb5ab9e8859a6f87eb734a1503cc6fe7c1bfa0594 149866 funkload_1.11.0-1_all.deb Files: 3fe4ddfd268fcb739887ac5d92f1c44c 1041 web extra funkload_1.11.0-1.dsc 7a91442674ba4955326f7e16707558fb 117912 web extra funkload_1.11.0.orig.tar.gz 48c658d5f8d90aa457353f20c2bd3500 101738 web extra funkload_1.11.0-1.diff.gz d2e8588827e2a7d004d925779903cb3d 149866 web extra funkload_1.11.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAktqsdYACgkQfoEUoHXLGtJS0gCfdfLjLvK75MkCP5v7Khzxfcv4 h1EAoNw4KHSzYI1YQQs8JodySlX0p6Nz =Y4w4 -END PGP SIGNATURE- Accepted: funkload_1.11.0-1.diff.gz to main/f/funkload/funkload_1.11.0-1.diff.gz funkload_1.11.0-1.dsc to main/f/funkload/funkload_1.11.0-1.dsc funkload_1.11.0-1_all.deb to main/f/funkload/funkload_1.11.0-1_all.deb funkload_1.11.0.orig.tar.gz to main/f/funkload/funkload_1.11.0.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted funkload 1.11.0-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Feb 2010 13:41:02 +0100 Source: funkload Binary: funkload Architecture: source all Version: 1.11.0-2 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: funkload - web testing tool Changes: funkload (1.11.0-2) unstable; urgency=low . * removed obsolete file Checksums-Sha1: 459d2881a07328a4e330064f6f171f9bddbcf83c 1038 funkload_1.11.0-2.dsc 466816636ddc02bcdf8f6206dd810751bdc6fc10 26080 funkload_1.11.0-2.diff.gz a069aa79fefc460acf3b2a3ddac6b6fc9cc389de 149234 funkload_1.11.0-2_all.deb Checksums-Sha256: 800470cb91c40e9d3576fde72541d3dd7909cb5e785cdb12ab099de27d88204b 1038 funkload_1.11.0-2.dsc e0077cd509fc39ec022e095a157732e0b67a6f13dac7967243726f73b21665a7 26080 funkload_1.11.0-2.diff.gz b0f8e7198566bb7e48267884c116b5fb65083b8e41401ec90f5c40ddad326116 149234 funkload_1.11.0-2_all.deb Files: 528bd04ad903fa33cc28a2672b46125b 1038 web extra funkload_1.11.0-2.dsc f1b20f1c849703b4361c7a640ccdfe24 26080 web extra funkload_1.11.0-2.diff.gz 0915b095a8389a1e2a68494bbd10d933 149234 web extra funkload_1.11.0-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAktqsqkACgkQfoEUoHXLGtJLkACeLuraI0q9dgsG7Ob7ZbqBoGmC VDYAnilEDWrFKHOwrptZTfgTPXfzz3Rs =LRBy -END PGP SIGNATURE- Accepted: funkload_1.11.0-2.diff.gz to main/f/funkload/funkload_1.11.0-2.diff.gz funkload_1.11.0-2.dsc to main/f/funkload/funkload_1.11.0-2.dsc funkload_1.11.0-2_all.deb to main/f/funkload/funkload_1.11.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
Accepted sec 2.5.3-1+nmu1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 28 Jan 2010 18:05:35 +0100 Source: sec Binary: sec Architecture: source all Version: 2.5.3-1+nmu1 Distribution: unstable Urgency: low Maintainer: Jaakko Niemi li...@debian.org Changed-By: Toni Mueller t...@debian.org Description: sec- Simple Event Correlator Closes: 539808 Changes: sec (2.5.3-1+nmu1) unstable; urgency=low . * Non-maintainer upload with permission from maintainer * New upstream (Closes: #539808) Checksums-Sha1: d14a46908d5e81995a6b6bcf378fbb1283cdb89e 930 sec_2.5.3-1+nmu1.dsc 0d29f5c780f4a5e77f6dfa9c0b89a1761b466e7d 86918 sec_2.5.3.orig.tar.gz a7750925b4a4d4f94bac549a93d2ed540a98e176 3059 sec_2.5.3-1+nmu1.diff.gz 2cb5c0c9cf18dd46d61b162b0e2a25b3d714 85576 sec_2.5.3-1+nmu1_all.deb Checksums-Sha256: b33037980bb9e7c771ed6c9a9bd01667aa703d07f009490fe7287a5ded59fb5c 930 sec_2.5.3-1+nmu1.dsc 93b1be1078e100271e4feb484de7ba76c0cffa5abfd6d84e790f784e9c969329 86918 sec_2.5.3.orig.tar.gz e403bcc611bb1b539d67b7c713373b590ea6811a28c6fd6f715a97ca686930aa 3059 sec_2.5.3-1+nmu1.diff.gz e53f722d792f0a47221be9810ac7869b87ead666c67c7fa8c6f0f3ca6b0dca48 85576 sec_2.5.3-1+nmu1_all.deb Files: 056663f947e4f2eabb3e637dab5fe78d 930 utils optional sec_2.5.3-1+nmu1.dsc 11bb84273daf24d265a96624ab6413ca 86918 utils optional sec_2.5.3.orig.tar.gz 205fea4528cad7cd366942ec31c93625 3059 utils optional sec_2.5.3-1+nmu1.diff.gz ecdbb1f256b8f3e7f9adb31c447097df 85576 utils optional sec_2.5.3-1+nmu1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAktotrQACgkQfoEUoHXLGtKTbACgmpPd8zQ10NqU+kjbp5SiaOaO E/gAoLd7VabVY50GmmmG3w5XEVWhsHke =UhAI -END PGP SIGNATURE- Accepted: sec_2.5.3-1+nmu1.diff.gz to main/s/sec/sec_2.5.3-1+nmu1.diff.gz sec_2.5.3-1+nmu1.dsc to main/s/sec/sec_2.5.3-1+nmu1.dsc sec_2.5.3-1+nmu1_all.deb to main/s/sec/sec_2.5.3-1+nmu1_all.deb sec_2.5.3.orig.tar.gz to main/s/sec/sec_2.5.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
Accepted roundup 1.4.11-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 24 Dec 2009 15:27:20 +0100 Source: roundup Binary: roundup Architecture: source all Version: 1.4.11-1 Distribution: unstable Urgency: high Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: roundup- an issue-tracking system Closes: 284394 Changes: roundup (1.4.11-1) unstable; urgency=high . * new upstream * fixes a security hole * amended README.Debian (closes: #284394) Checksums-Sha1: 257292676122491d271e3ebb44dfbb1d3971f3cd 1042 roundup_1.4.11-1.dsc d49b85e3e0c6e750e25ee40f870b531884f39571 1264096 roundup_1.4.11.orig.tar.gz b214a8f67ce62286b7978d5394cacee72c36d8d3 22111 roundup_1.4.11-1.diff.gz 97a9f246657867b8f5ee778d360c58df17d633c9 1173614 roundup_1.4.11-1_all.deb Checksums-Sha256: c8223480ada26e4e5e267c641ea2243b93cc8b13a3b7f76446257629d2e08a69 1042 roundup_1.4.11-1.dsc b893c8399ba90ff25539eb8bb27656af9d081f28e31a747a0677f9aad7e74a5d 1264096 roundup_1.4.11.orig.tar.gz b3002c8f5d2bd7fb84fccf110c1b2bc2a565e7c8d9d41adcca67c0ef3299f435 22111 roundup_1.4.11-1.diff.gz 10024cf5a9ffe46bceee0d06adb170d0a14c402644c5ecc1f3a751901a5a05e5 1173614 roundup_1.4.11-1_all.deb Files: 6b9f1296fc7cc76ca4745bd5ab5270b6 1042 web optional roundup_1.4.11-1.dsc 4f04c27d2990d1b15e7b782eacbb36bf 1264096 web optional roundup_1.4.11.orig.tar.gz 1a18701afd4d2928830bf6dad68ec47e 22111 web optional roundup_1.4.11-1.diff.gz b68c42f8ef8466fa2db67b2ebafd792f 1173614 web optional roundup_1.4.11-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkszjVYACgkQfoEUoHXLGtL8qgCgijAj3+eYXjllcigVYu8f/Vgl ZREAoKHzFuVzE5gA9ZOObigi5dj42uS8 =cGNS -END PGP SIGNATURE- Accepted: roundup_1.4.11-1.diff.gz to main/r/roundup/roundup_1.4.11-1.diff.gz roundup_1.4.11-1.dsc to main/r/roundup/roundup_1.4.11-1.dsc roundup_1.4.11-1_all.deb to main/r/roundup/roundup_1.4.11-1_all.deb roundup_1.4.11.orig.tar.gz to main/r/roundup/roundup_1.4.11.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted roundup 1.4.10-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 02 Dec 2009 18:42:53 +0100 Source: roundup Binary: roundup Architecture: source all Version: 1.4.10-2 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: roundup- an issue-tracking system Changes: roundup (1.4.10-2) unstable; urgency=low . * fixed a typo Checksums-Sha1: a48318b76cc1ccdfa6820c1303de39b60a7109d4 1000 roundup_1.4.10-2.dsc a59aa509e6d9d063aadf78c8bd2d1fbd6b946a3d 21616 roundup_1.4.10-2.diff.gz 6dc0e0fe5b3846993a0664157af9360d11dfc45e 1346332 roundup_1.4.10-2_all.deb Checksums-Sha256: 927163a5fc3b8e0721b377229af64ce10d446bed7c2923fc4469337091ffc781 1000 roundup_1.4.10-2.dsc ec0f4183910cb020242c734ce9e093ebfa6c97fe210dfe8203fed6caec9591e4 21616 roundup_1.4.10-2.diff.gz 6c8ca562dc63e959b1b88ed24e71c9117ce7444eeb2d9fb64465eda7217c1004 1346332 roundup_1.4.10-2_all.deb Files: 205c94612fb9250c5ef2342827a42f12 1000 web optional roundup_1.4.10-2.dsc 480bf1f01abfd71cc4d55ece98e0f428 21616 web optional roundup_1.4.10-2.diff.gz b30b59edb32cac21bff347f6fe2bcdfa 1346332 web optional roundup_1.4.10-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAksXkT0ACgkQfoEUoHXLGtIw5QCcCjn4cJDyw1I1rsMiw3aIHtd4 +VUAn3dK6k+1m3qM2qPqxnd4ICuRV2d/ =e8Sn -END PGP SIGNATURE- Accepted: roundup_1.4.10-2.diff.gz to main/r/roundup/roundup_1.4.10-2.diff.gz roundup_1.4.10-2.dsc to main/r/roundup/roundup_1.4.10-2.dsc roundup_1.4.10-2_all.deb to main/r/roundup/roundup_1.4.10-2_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted roundup 1.4.10-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 01 Dec 2009 10:31:23 +0100 Source: roundup Binary: roundup Architecture: source all Version: 1.4.10-1 Distribution: unstable Urgency: low Maintainer: Toni Mueller t...@debian.org Changed-By: Toni Mueller t...@debian.org Description: roundup- an issue-tracking system Changes: roundup (1.4.10-1) unstable; urgency=low . * New upstream Checksums-Sha1: 712eb212fae56786a5f53e541f257f6f91b3f745 1000 roundup_1.4.10-1.dsc 5889b5ce9b8672e3b7481f82d469c2fca64e84c2 1639125 roundup_1.4.10.orig.tar.gz a3a776ecee1d4532f75f29541f9ae462d9f86964 21600 roundup_1.4.10-1.diff.gz cae71253f8bac374bcc8bbb2e4bbf13eaabd607d 1346346 roundup_1.4.10-1_all.deb Checksums-Sha256: f21745347d6f92b9c6f44903511ee405091e964f902c97b61fec9220664e6feb 1000 roundup_1.4.10-1.dsc 9a921c7fd60e430d0fbc5f74fb078ac400129f36434ac33230036e64834bfe28 1639125 roundup_1.4.10.orig.tar.gz fcc78b9071a3cb52650ab3e83fc5e90d465e410a3c961193b67805c1c08661be 21600 roundup_1.4.10-1.diff.gz 96f674bd44608730cbc8ef2c5fe48032ab9d785da4162cdd510afe4999b587a8 1346346 roundup_1.4.10-1_all.deb Files: aece33dac01c847f309bbd703a70caf8 1000 web optional roundup_1.4.10-1.dsc d58f877d4031aecdf5ebd8920211f48a 1639125 web optional roundup_1.4.10.orig.tar.gz a6702fd74d0d43ec4d30be98a46941af 21600 web optional roundup_1.4.10-1.diff.gz 75e364b6f9e5665899ef168886cbcccb 1346346 web optional roundup_1.4.10-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAksU+usACgkQfoEUoHXLGtKvlQCdHYRcMYXDYFiG/1AwQARLaoGc nkEAoIvI3bwkABpBmRf7If89LzUipb7D =VvzZ -END PGP SIGNATURE- Accepted: roundup_1.4.10-1.diff.gz to main/r/roundup/roundup_1.4.10-1.diff.gz roundup_1.4.10-1.dsc to main/r/roundup/roundup_1.4.10-1.dsc roundup_1.4.10-1_all.deb to main/r/roundup/roundup_1.4.10-1_all.deb roundup_1.4.10.orig.tar.gz to main/r/roundup/roundup_1.4.10.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
