Re: booststrapping /usr-merged systems (was: Re: DEP 17: Improve support for directory aliasing in dpkg)
On Fri, 09 Jun 2023 22:14:16 +0200, Helmut Grohne wrote: > On Fri, Jun 09, 2023 at 02:42:25PM -0500, Richard Laager wrote: > > Because you want to support non-usr-merged systems, e.g. for derivatives? > > dpkg is used in any different contexts. A very simple example of a > non-merged system would be Debian stretch. For another dpkg really is > being used for things that are not based on Debian. While it is the > Debian package manager, it has uses beyond dpkg has (thus far) stayed > away from imposing policy on the filesystem layout. Refusing to delete /bin etc. doesn't mean that dpkg imposes any policy on the filesystem layout. The change would also be small enough that it would be easy to disable it, but I can't think of any usage of dpkg for which that would be needed. > > They aren't going to want to delete /bin either, so I don't see how a > > special-case preventing deletion of /bin would be problematic. > > Indeed. However, if you actually manage to trigger this, it can be very > surprising. Your hard coded list would also contain /lib32, /libx32 and > /libo32. Then you install some mipsen packages, remove them and wonder > why /libo32 does not go away. piuparts is definitely unhappy at this > point. I am quite sure that this behaviour would break something. What I > am not sure about is whether accepting such breakage is a reasonable > trade-off. I can't really think of anything that would break with having an extra directory or symlink around. And if base-files ships the symlinks they would always be there and piuparts would be happy. > > Later, whatever replaces /lib64 with a symlink needs to deal with this, but > > that's not significantly different than whatever it was going to do anyway, > > right? Just do this: > > > > 1. Whatever safety checks are appropriate. > > 2. Unless already verified to be identical by #1, hardlink > > /lib64/ld-linux-x86-64.so.2 to /usr/lib64/ld-linux-x86-64.so.2. This might > > be just a particular instance of the more general case of hardlink > > everything from /lib64 into /usr/lib64. > > 3. Unlink everything from /lib64. > > 4. Unlink /lib64. > > 5. Symlink /lib64 to /usr/lib64 > > I think we start from the premise that /lib64 already is a symlink and > as long as libc6 actually ships /lib64 (even if empty), dpkg won't > delete it. What we will not get here is getting rid of the aliasing and > we will also be unable to ship /lib64 as a symlink in any data.tar > (since that would be a directory vs symlink conflict, which has > unpack-order-dependent behaviour, which is bad). But if all packages in trixie are changed to not ship /lib64 anymore, there wouldn't be a conflict in trixie anymore? If we have the following situation: - We change dpkg to never delete /bin, /lib, /lib32, /lib64, /libo32, /libx32, and /sbin. We can also change dpkg in bookworm to not do this so that we are sure that when upgrading to trixie we have a dpkg that won't delete any of these symlinks. - All packages in trixie are changed to have their files moved to /usr. - Base-files will include the symlinks In the case of bootstrapping no trixie package will have any files in /bin etc. so there wouldn't be a directory vs symlink conflict. From what I understood we need to change the bootstrap protocol to make sure that base-files is unpacked before anything is run so that /bin/sh and ld-linux.so are available. To me that seems to be a simple change to make and it should also be possible to make this small change in the bootstrapping tools in bookworm. In the case of upgrading we already have all the symlinks in the filesystem. Installing base-files when there are still packages installed with files in /bin etc. shouldn't be a problem as far as I understand it. And we changed dpkg to never delete the symlinks when no package ships the /bin directory anymore so it also shouldn't be a problem if all packages that used to ship /bin etc/ are upgraded before base-files is upgraded. Kind regards, Jeroen Dekkers
Standards compliance (Was: Re: Bug#1035904: dpkg currently warning about merged-usr systems (revisited))
On Mon, 15 May 2023 02:42:27 +0200, Luca Boccassi wrote: > > On Mon, 15 May 2023 at 01:14, Russ Allbery wrote: > > > An obvious specific example of such a system would be one that didn't > > merge /usr and thus only had /lib64/ld-linux-x86-64.so.2 and not any other > > path, but that's just one obvious example. There may be others; the whole > > point of an ABI is that you do not change things like this, not even if > > you can't personally imagine why your change wouldn't be harmful. There's > > a whole process for changing an ABI that involves everyone else agreeing > > as well, and unless one goes through that process, the ABI is what it is. > > Debian not building ABI-compliant binaries would be highly surprising. > > That's self-evidently not true, as there are other distributions where > that already happens, it's been already mentioned. Besides, we are not > talking about sacred religious texts - the point is making things > work. If they do, is it _really_ non-compliant/incompatible? The point of a standard is definitely not that people ignore it and do things that are in direct contradiction with the standard. The point of a standard is that people agree on a specification and will also follow that specification. Something working and something being compliant are different concepts. Software can be compliant and not working and software can also be non-compliant and working. Something that is in direct contradiction with a standard is definitely non-compliant. Whether it works or not is not relevant for that. Kind regards, Jeroen Dekkers
Accepted sogo 4.0.5-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 15 Jan 2019 10:14:20 +0100 Source: sogo Binary: sogo sogo-common Architecture: source Version: 4.0.5-2 Distribution: unstable Urgency: medium Maintainer: Debian SOGo Maintainers Changed-By: Jeroen Dekkers Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files Closes: 914524 Changes: sogo (4.0.5-2) unstable; urgency=medium . * Add patch to not use OpenSSL when we are configured to use GnuTLS (closes: #914524). * Add patch to unset MAKEFLAGS and MFLAGS in configure. Checksums-Sha1: 66a64e591e88a6ab50e27cb76bbab8f57ee4541e 1964 sogo_4.0.5-2.dsc 6a1ff179513b24960694cb5b054095409ebc7157 15124 sogo_4.0.5-2.debian.tar.xz 8631a42e28c53cfff3993cab784bc812c837382f 8624 sogo_4.0.5-2_source.buildinfo Checksums-Sha256: a52e98f2d1df8deddda0b1c829ad0b1f6614ccb29419ffe37fd3fac7e9850f90 1964 sogo_4.0.5-2.dsc 6ad89b054b5b4e3a83fd6f74fdb2fa7415f348ae624c8d275a18adb3e74e8010 15124 sogo_4.0.5-2.debian.tar.xz 3b4def21af5f86b333ad0845e681a576b9d4a3e86c14a1934aeebc35b6f75a5e 8624 sogo_4.0.5-2_source.buildinfo Files: 490dc4356335fadcbaf5659fd1299ac2 1964 mail optional sogo_4.0.5-2.dsc 3c8141a9901845e6cfef8a996d7065cb 15124 mail optional sogo_4.0.5-2.debian.tar.xz 274875096d2d8f1b19e38dbf7141c128 8624 mail optional sogo_4.0.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQHGBAEBCAAwFiEEDYDquwRHblQslAjhCtspnB8TfJ8FAlw9wVUSHGplcm9lbkBk ZWtrZXJzLmNoAAoJEArbKZwfE3yfHNgL/RBXlekuQaFBIXKKrYkTMglk9PTUd2mf lmq5SOeGLx8auefNJiSKCP7VYpaF3zdK4w9Kptx0rEP56YD0jbfqOX7bJTDGLQtb d88fG6kVbdCkwKJoLsn9ZTsfdvpbB6Di7gcoMYW73SCFKRhB/BbyDMTxYmxJp4YC taSrrz7Hzd9T5HsyomI1IWD/Ba5QHVxIJj8BlsBWiB+RIfde8R8oTcBcdbCBVhGW m5bNhp3goUO1jy6D3KOS0QphSViP8nFeJ2viPHY60zHJDaS+a2ndFw6mQoooz+o+ BdV60KHcjpei+BmkiQ9CeN5NzgHCEFmRsi+0QHtj9yK0CLouHHpiZo6H1b/+fN9L SlbUvSNot2SJOWmQjrLgnJC6YbemfUttMVAUVao+NvoAiok+6wYAhyAgeJhCB7U9 pJId+ucjEfA4sYwM7M5qiVW5LLsQqsCAZGJb68THFLb4DE1Dk0wa4rSbO2o52eyT QmkE9ndv/wQNVRtsC1Q8UArZ/py/1XHqbQ== =8zVE -END PGP SIGNATURE-
Accepted sope 4.0.5-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 14 Jan 2019 22:35:43 +0100 Source: sope Binary: libsope1 libsope-dev Architecture: source Version: 4.0.5-2 Distribution: unstable Urgency: medium Maintainer: Debian SOGo Maintainers Changed-By: Jeroen Dekkers Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) Changes: sope (4.0.5-2) unstable; urgency=medium . * Add patch to unset MAKEFLAGS and MFLAGS in configure. Checksums-Sha1: 6be90b3c96dc8a8d97712afe73859be778d4ff81 1930 sope_4.0.5-2.dsc 8a98b62b29aaba4e257dbaf581c60bcdecba53d5 5840 sope_4.0.5-2.debian.tar.xz 21534ef3beda1a9623645a8c5ab4087ffc432ca1 7890 sope_4.0.5-2_source.buildinfo Checksums-Sha256: 332df3c80e7e892cf5e584d44dfa0f47de85fe4727fb910b712b64dd9f573d42 1930 sope_4.0.5-2.dsc 87d23cafac9a4e63398efb629d1809a8b15a67b4de55d4a673d0cdd1839fc1f3 5840 sope_4.0.5-2.debian.tar.xz f5f6e0777e9b93b1ccc160f9a5ff8a2918ef62799b22cf78950fb92f5fd970e5 7890 sope_4.0.5-2_source.buildinfo Files: c5bf35fc52c59faf292ae3bdbf2698f0 1930 libs optional sope_4.0.5-2.dsc 5bc08df9e40c220d2cded1acd92b81d3 5840 libs optional sope_4.0.5-2.debian.tar.xz ab88d6513f1a59ad92240c912d4971df 7890 libs optional sope_4.0.5-2_source.buildinfo -BEGIN PGP SIGNATURE- iQHGBAEBCAAwFiEEDYDquwRHblQslAjhCtspnB8TfJ8FAlw9CIgSHGplcm9lbkBk ZWtrZXJzLmNoAAoJEArbKZwfE3yfrTsL+wdquJWCHDqg40eATc8VzV8DBdeh24W1 gAY/U+OAQm6byVW0Hdy0BQFw8/eNNwrWCRyHuwgl7z8ZMOcv5tERlX3BEFHvTsQ5 ZicdHfYc0/7BHZWsUH33rlQnWh9MsPdVUKc/SH+TXSI4mWMUhWYjwDvKLOV+toLo OVwRgq1SqcKr6a4Ik1Cv6Tsf8CprBb5KyK/kvnx7wR8dqg+FBjZ+2NY1xDJi0yG3 HfD7j+uVd7zlHvOO1YqGhfRjAvpG9z9UXvEVWEfZA4AkJEK04tMP/WkNXxBbcyxf o92tRGctseouYX1zuhq4oiCeD/9r/hYcFvjGLUqZ57BHbH8Del7dLMVFbF9CPQLW xfgZu31dp35zuoAgPBBL3vP7Ie1YvI0F4VFHyTXxeuH8Gj+Ov/0KcgbwOfWyuYPD fjPPcrHPycCc7Zf0ztmUbkBRzkukQWLCrddmkhG0+kg+uWp9T6FTvdZPdRhXL3hd MppDG8ih08RVqNLvjkZ9KONs9MPUuPrnbg== =vnkR -END PGP SIGNATURE-
Accepted sbjson 2.3.2-4 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 13 Jan 2019 22:30:40 +0100 Source: sbjson Binary: libsbjson2.3 libsbjson-dev Architecture: source Version: 2.3.2-4 Distribution: unstable Urgency: medium Maintainer: Debian SOGo Maintainers Changed-By: Jeroen Dekkers Description: libsbjson-dev - Objective-C JSON library (development files) libsbjson2.3 - Objective-C JSON library Changes: sbjson (2.3.2-4) unstable; urgency=medium . [ Jordi Mallach ] * Update Vcs-* fields after migration to salsa.debian.org. . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field * d/control: Deprecating priority extra as per policy 4.0.1 . [ Jeroen Dekkers ] * Trim trailing whitespace. * Use secure URI in Homepage field. * Bump Standards-Version to 4.3.0. No changes needed. * Set pristine-tar to True in debian/gbp.conf. Checksums-Sha1: 27adda46a9a629c97884d1b551a2745d21d06ce0 1909 sbjson_2.3.2-4.dsc a43a00243a02242eef52672ad305e7825a98917b 5504 sbjson_2.3.2-4.debian.tar.xz 28fcfa5c7e059c1731e691fbdb3405809f5a7abb 6656 sbjson_2.3.2-4_source.buildinfo Checksums-Sha256: 383058075428c1d65102b8adc330c45dd6b17ff220f94c2706d643410874b62a 1909 sbjson_2.3.2-4.dsc 9795ff07d07ef9f32bde0c8a216e803ee68bc7b841744ea44f37fc7a1d13b6f9 5504 sbjson_2.3.2-4.debian.tar.xz 54f365803c505190698aaf6825979c43aed7fb6f7d8ab316859d87882d9694a1 6656 sbjson_2.3.2-4_source.buildinfo Files: 05c779ee0b4412c24bfd63c36821fb5c 1909 libs optional sbjson_2.3.2-4.dsc a941cfea834ff8299ada1cc656693c88 5504 libs optional sbjson_2.3.2-4.debian.tar.xz ca96462367e851d4a15e52c3bcc51f4d 6656 libs optional sbjson_2.3.2-4_source.buildinfo -BEGIN PGP SIGNATURE- iQHGBAEBCAAwFiEEDYDquwRHblQslAjhCtspnB8TfJ8FAlw7r44SHGplcm9lbkBk ZWtrZXJzLmNoAAoJEArbKZwfE3yf7cYMAKbpprPy4WzjpF4XljcsKDcVMr5lsKUK GI1WvuTODohJRNtKE318TI869rS02g1468HJm66bqqLklxNQogU0nah5XG/4YEP6 mHYztEFJn9u/6sJHdzvcmYC+D1ykw+vmvrBJcpcG0fukWVd0P7CpiNgS1hhMsG0W 6Dvt2DM5JVaG5FBTXdMTsd+E0wSU9htNcDMwRFkqJrK50BqTLNEY9pBMqTz/ipSq owh3MzWCNqA9lLSh1fuT+hFu/YbQTyglmHRbbDJbR9BHDL0YqRN17xfIoCsDqnad ytI97Bvc5X1HiE78yIb5JvFhRliikJsJpunjMkVzPmSB9my3HCpbi6GcPKX3Z7cX JMi8acrDkIKfJLZsiaKTrSquVGVhIx5KPvEsjT/PkH8hXrUyYE5kdhjKXK9xW7+p M9lvWVBSAWksM5fuzKA/b4RIzNr8G9B3fMDgh18lgov/dv0okZvNQkFdtULvkk3k BlrybxAkfPyQwZRwghEgv5eboATF+FaQHg== =ICsc -END PGP SIGNATURE-
Re: Debian Stretch new user report (vs Linux Mint)
On Mon, 04 Dec 2017 12:31:14 +0100, Jonathan Dowland wrote: > > On Fri, Dec 01, 2017 at 08:28:49AM +, Simon McVittie wrote: > > I doubt there was any such decision, except by not knowing there was a > > decision that could be made. The official, fully Free ISO (which is OK > > for VMs and some embedded systems, but normally a trap for the PCs we > > expect new users to be using) is the one you get when you point a browser > > to debian.org and click the prominent "Download Debian" link. The one > > with the firmware is hidden behind a door marked "beware of the leopard" > > because we don't want to be seen to be endorsing or recommending non-free > > software. > > Simon, your mail has really motivated me to stick my head up a bit, > because I'm really uncomfortable with the status quo with this exact > issue in Debian, and although I think it will be very difficult and > quite possibly painful, I think something needs to change, and your mail > has helped me to face up to that. > > IMHO, we need to go (more) one way or the other. We either reaffirm that > firmware is in-scope for our DFSG values and stop compromising it with > the non-free install images, or we look to revise the DFSG in line with > modern realities and can "promote" the status of the installer images > with firmware. That seems much harder: there have been brave efforts > to reform the DFSG before, not least by Ian; and they have not > succeeded. However, I think the project is healthier in one way from > those days, we've weathered some fierce debates and I think we've grown > as a project in the way we communicate together to resolve problems. I don't think we have to change the DFSG. The DFSG defines what is free software and in my opinion it is pretty clear that firmware is software and therefore non-free firmware is non-free software. The Social Contract already says that our priorities are our users *and* free software and also acknowledges that users might require non-free software. It also says we will provide an integrated system of high-quality materials. It doesn't say that free software is of higher priority. As normal with foundation documents there is room for interpretation. In my opinion changing the Debian website such that in every place we list both an installation image with and without non-free firmware wouldn't be in conflict with the Social Contract. We mention non-free software in other places too, for example if I search for software on packages.debian.org I also get non-free packages. The installer also asks whether you want to install non-free software. (But that is maybe only in expert mode? I always run the installer in expert mode so I am not sure what the normal questions are.) So it is already okay to ask the user whether the user wants to install non-free software, but the problem is that it is pretty difficult to download non-free software if you need that non-free software for your network connection. I don't see why solving this chicken-and-egg problem by prominently providing installation images with such firmware wouldn't be an acceptable compromise. Also not updating the processor microcode by default is in my opinion in direct conflict with that users are our priority and that "we will provide an integrated system of high-quality materials", but that's probably a slightly different subject because it is not required to be on the installation medium. Kind regards, Jeroen Dekkers
Re: Debian Stretch new user report (vs Linux Mint)
On Mon, 04 Dec 2017 13:21:49 +0100, Ben Finney wrote: > > Jonathan Dowland <j...@debian.org> writes: > > > Are *you* using non-free firmware? > > The machines sold by, for example, ThinkPenguin, work with the latest > Debian release, without non-free software. There's one example, which > responds to the rhetoric of that question. So can you point me to the free versions of the Intel microcode, the Intel Management Engine, BIOS, firmware of the wireless chip, the firmware of the hard disk, etc. that's running on that laptop? Just because software comes pre-installed doesn't mean it is free. And if it is also impossible to replace the software you also can't update it with a free version so the user has even less freedom than when you can replace the software with something else. Kind regards, Jeroen Dekkers
Re: What's a safe way to have extensions in chromium in Debian?
At Wed, 22 Mar 2017 12:03:02 +0100, Enrico Zini wrote: > now we have extensions disabled in Chromium by default. If I did my > homeworks correctly, that prevents Chromium from phoning home by > default, and prevents a previous scenario where extensions could be > installed but not upgraded, becoming security issues over time. > > Now, suppose I need an extension, what is the proper way to have it in > Debian, so that it gets upgraded when needed? With that proper way, what > amount of phoning home is going to happen? > > Since this looks like it's going to be a major issue with stretch, can I > have some authoritative wiki page / FAQ entry that tells me how I can > deal with it cleanly, and that I can easily send to confused people? If we already know this is going to be major issue, why aren't we doing the sensible thing and enable extensions by default instead of disabling it and then having to explain again and again how to enable it because the majority of our users will at least want to use an adblocker? And browsing the web without any extensions is probably a way bigger privacy invasion than the phoning home the extension system does, so disabling it by default seems to be just privacy theater to me. (I.e. it's a inconvenient measure that gives a feeling that Debian does something for privacy but in practice doesn't really do much to achieve that, similar to security theater) Kind regards, Jeroen Dekkers
Re: "Dear Customer" spam in the BTS
At Wed, 26 Oct 2016 13:43:31 +0200, Tomas Pospisek wrote: > I've recently received "Dear Customer" spam on a bug of mine. I've > searched the BTS [1], and there are many, many, many of these spam > postings in the BTS, see f.ex. [2]. > > I think it doesn't make sense to press "this bug log contains spam" on > each of those pages. Better would be to go directly to the archive and > delete such posts directly from there. > > I know I have once tried to do that - I think with a bit of advice from > Don Armstrong but it never went anywhere. > > Has anyone tried to do such a thing yet (methodically clean the bug > archive of spam)? Where and how could I start such an effort? How would > I get read/write access to the BTS archive? Spam e-mails like these that contain a zip with a windows executable can easily be blocked based on file extension using the foxhole rules for clamav (http://sanesecurity.com/foxhole-databases/). And clamav can probably also be used to automatically clean the bug archive of such messages. Kind regards, Jeroen Dekkers
Accepted sope 3.0.2-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 09 Apr 2016 15:15:55 +0200 Source: sope Binary: libsope1 libsope-dev Architecture: source Version: 3.0.2-1 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers <jer...@dekkers.ch> Changed-By: Jeroen Dekkers <jer...@dekkers.ch> Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) Closes: 813269 Changes: sope (3.0.2-1) unstable; urgency=medium . * [c17021f9] New upstream release. (Closes: #813269) * [e975d858] Bump Standards-Version to 3.9.8, no changes needed. * [7c77abfc] Create automatic dbgsym package instead of the manual libsope1-dbg. Checksums-Sha1: 11812e6ce5899ef8a176c237b496be3f0feddeff 1661 sope_3.0.2-1.dsc 2372f6234cf022eb87e98d6149455deab2e14793 2275515 sope_3.0.2.orig.tar.gz 1ffe3139bbf06733ae26156458a077a80040f0ee 4704 sope_3.0.2-1.debian.tar.xz Checksums-Sha256: 3482f6897de07b91727ece75bb30ce9cb1826a5e9f28ab4b899d5d25c56da481 1661 sope_3.0.2-1.dsc 62adad635d386b0f7531c40f88cd314b267fbaa873c8d0b78204c399123f4ef1 2275515 sope_3.0.2.orig.tar.gz 2507187d8552842d1474ad90ce05d5af1cdca5a0a34158f0b997d04b8a9df7e8 4704 sope_3.0.2-1.debian.tar.xz Files: e48bef6fa31d6f7a7bd3a08eeab5a6b4 1661 libs optional sope_3.0.2-1.dsc bba4d7cf030cd42d56bf8cb74879dd93 2275515 libs optional sope_3.0.2.orig.tar.gz 40576e13a9e31def8fab71dc68640e90 4704 libs optional sope_3.0.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJXCQvjAAoJEDGCUpfTb5CB6QkH/3Ie3ckaPLNll+k+uRfTzq8I EogdyeRChdyPKopLsUuMk1TqnO0lYTL+Yb7aSdOas2aqSrOnqxw40wcuqsKL7LpP me/S0gsTW73KH1MAEZ4jMRbcab8DkTvo/hVIflDi79Ievz6nmU4CBjCNyTCfbrNw k0sZQ1TnmdYmPTbTclDfckYj5MZ0ST85kfV+4j966xmsWIUxVe7ZuHXvRMWDBgnC 2lNmTh8rGqPzU18BsyHbOjjxpa5yCH4hj6M+PPjVN3hBKWznbTjYaw2a4+hCcgPd cpHAQsoGit9OpGejzpedJ7+66umLqeqKoSxnZ7CR5bCN28MDL1dN+iKanTkMyPc= =w5f3 -END PGP SIGNATURE-
Re: [Mailman-Developers] Let's try to package mailman3 in Debian!
At Mon, 22 Feb 2016 02:50:44 +0100, Malte Swart wrote: > - The default configuration uses postfix, needing postmap to run mailman > aliases (which is called automatically on mailman create). So the package > should recommend/suggests postfix. If mailman 3 works with any MTA in the same way as mailman 2 then it should do same as mailman 2 and recommend "default-mta | mail-transport-agent" and should not suggest or recommend postfix. Kind regards, Jeroen Dekkers
Re: Putting default config files in /usr [was; (newbie) Disruptive LIRC package update.]
At Wed, 11 Nov 2015 18:14:26 +0100, Marc Haber wrote: > > On Wed, 11 Nov 2015 17:29:31 +0100, Ole Streicher <oleb...@debian.org> > wrote: > >Paul Wise <p...@debian.org> writes: > >> I expect systemd users in other distributions would appreciate a > >> feature to track changes in the default configuration too. > > > >Many programs have builtin defaults that are used when they are not > >overwritten by a configuration file. How do you track the change of > >these defaults during the program evolution, and how is this different > >from a evolving default configuration in /usr/lib/? > > It is custom that the configuration file contains comments and > documentation, says what is the default and usually contains a > commented out configuration option setting the default. I'd expect > these comments to change if the program's defaults change, which is > nicely caught by dpkg conffile handling. Documentation should be put in /usr/share/doc, not in /etc. I always find it annoying to have to review lots of comment changes in configuration files during upgrades instead of simply the options that actually changed. With big config files it often results in running "grep -v '^#'" to figure out what the actual differences between the old and new file are... > It does not help to look for corner cases where Debian is not better > than the competition, it still excels in the majority of cases and the > Pöttering-Way of handling configuration is inferior to the way we > usually do things. > > Once and for all we're doing _SOMETHING_ right, let's keep it that > way. That Debian has been doing management of configuration files better than other distributions doesn't mean it is perfect and we should never change anything again. It is still a good idea to look how things can be done better. And the way people administrate systems also change, nowadays it is for example a lot more common to put configuration in a configuration management system compared to 15 years ago. Kind regards, Jeroen Dekkers
Re: Decreasing packaging overhead
At Sun, 1 Nov 2015 12:33:19 -0800, Josh Triplett wrote: > > Thomas Goirand wrote: > > But good luck to teach good practices upstream. See Ross's reply: 120 > > packages are depending on this. > > It's more than that. Given tooling that doesn't have excessive overhead > for small packages, why call such packages "bad practices" in the first > place? The total amount of lines of all the files in the git repository is 161, there are 5 lines of code, so the overhead 3220%. Or if you want to measure in bytes, total files are 4515 bytes and index.js is 150 bytes which results in an overhead of 3010%. In my opinion that is excessive overhead. And that's just the overhead in bits. This package probably won't need any changes in the future, but packages with a few more lines of code might. What happens when the maintainer goes MIA and something needs to be fixed? Do we then get forks of libraries that have only 30 lines of code, everybody has to update their dependencies to get the fixed version, etc.? That is also overhead you wouldn't have with a standard library maintained by a group of developers. Kind regards, Jeroen Dekkers
Re: service failures should not fail dpkg installation [was: Re: promoting virtualbox-dkms to virtualbox pre-depends]
At Thu, 24 Sep 2015 08:11:48 -0400, Marvin Renich wrote: > > * Jeroen Dekkers <jer...@dekkers.ch> [150924 07:23]: > > At Wed, 23 Sep 2015 13:53:11 -0400, > > Marvin Renich wrote: > > > I think it should be documented in the developers reference that if you > > > attempt to start or restart a service in postinst, you should guard it > > > so that a failure in the service does not propagate to a failure of the > > > postinst. > > > > But then when something goes wrong when upgrading and the service > > doesn't (re)start apt/dpkg will report success but the service isn't > > running anymore. That also sounds wrong to me. Letting postinst fail > > might not be the best way to signal this, but to change that we need > > something else to let the user know that something went wrong. Just > > printing an error message isn't enough, because the user might not see > > that (for example when multiple packages are installed/upgraded and a > > later package asks some questions using dialog or when using > > unattended-upgrades). > > How does failing the upgrade solve anything? The upgrade should only > fail if the failure of the service to start was because something in the > upgrade itself was broken; this is rarely the case. I think it solves the problem of notifying the user that something went wrong quite clearly. Not in the correct way, I agree with that, but the solution to that should be to notify the user in a better way, not to stop notifying the user. Failing silently is worse than failing in the wrong way. > What makes this even worse is that when installing or upgrading a large > number of packages, this kind of incorrect failure sometimes affects > many completely unrelated packages. For an unattended upgrade, this is > so much worse than having one service that (for a correct reason) > refused to restart after the upgrade. Unattended-upgrades has the MinimalSteps option that splits upgrades in the smallest possible chunks so that isn't really a problem. > What you are looking for is a more prominent notification that a service > did not restart. But the current situation is like the "check engine" > light flashing when you are low on fuel; yes, it gets your attention, > but it is telling you the wrong thing. Yes, but the way to solve that is to flash a "low on fuel" light, not to stop notifying you and leaving you alone in the desert without fuel. And if a "low on fuel" light isn't possible, it's better to keep flashing the "check engine" light like it has been doing for the past 15 years. Kind regards, Jeroen Dekkers
Re: promoting virtualbox-dkms to virtualbox pre-depends
At Wed, 23 Sep 2015 13:53:11 -0400, Marvin Renich wrote: > I think it should be documented in the developers reference that if you > attempt to start or restart a service in postinst, you should guard it > so that a failure in the service does not propagate to a failure of the > postinst. But then when something goes wrong when upgrading and the service doesn't (re)start apt/dpkg will report success but the service isn't running anymore. That also sounds wrong to me. Letting postinst fail might not be the best way to signal this, but to change that we need something else to let the user know that something went wrong. Just printing an error message isn't enough, because the user might not see that (for example when multiple packages are installed/upgraded and a later package asks some questions using dialog or when using unattended-upgrades). Kind regards, Jeroen Dekkers
Unattended upgrade to 8.2 point release breaks cron when running systemd
I just found out that unattended upgrade to the 8.2 point release breaks cron when running systemd. This was already mentioned in the cron bug that is fixed in the point release, but somehow didn't get a followup then: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783683#57 The bug that is fixed is that cron.service had the default KillMode=control-group that kills all the processes in the control group when cron is restarted and the update fixes this by setting KillMode=process. The problem with unattended-upgrades or anything else that is started by cron and does the upgrade is that when it upgrades cron, then cron is stopped using the old configuration, killing unattended-upgrades and dpkg, leaving the system with a cron package in a broken state. So if you are running Jessie with systemd and have configured unattended-upgrades to also automatically install non-security updates then cron will very likely be broken on all your systems. You can fix it by running "dpkg --configure -a" and "apt-get --reinstall install cron". The good part is that only security updates are enabled by default by unattended-upgrades, but my guess is that I'm not the only one who has non-security updates enabled in unattended-upgrades. There is also no way for us to automatically fix this because cron isn't running anymore on those systems. How do we let people know that they need to check their systems and manually fix them by running "dpkg --configure -a" and "apt-get --reinstall install cron"? Because until they do they also won't get any automatic security updates... Kind regards, Jeroen Dekkers
Re: Security concerns with minified javascript code
At Tue, 1 Sep 2015 18:56:45 +0200, Raphael Hertzog wrote: > For me, the javascripts bits in wordpress/publican are not part of the > product, they are external libraries whose preferred form of use is > by embedding a copy of the library... that sucks but it's the way it is. > > I do not see significant value in extending my packaging to rebuild > the minified files from source as part of the wordpress/publican source > package. On the opposite, it has a significant cost: > - I have to add the sources when upstream does not ship them > (which is not a problem for many upstreams since the BSD-ish > licences do not require you to provide the sources) > - ensure the sources are in sync with the minified copy > (even when friendly upsreams provide the required sources > on our request, they sometimes updates only one the minified file > and forget about the sources in some other directory) > - if the minifier is not the same as upstream, it will create > a divergence with upstream and can always be a source of > suspicion when we report issues to upstream... I do see at least one very significant advantage of rebuilding: it's a lot easier to check that no malicious code is inserted. And if I understand you correctly you're shipping minified files modified by upstream for which there might not even be complete up-to-date source available at all, so how do you know that neither upstream nor someone who compromised the server used by upstream inserted any backdoor in the minified file? What you're saying is like it's fine to have a precompiled static auxiliary C library that get's linked into the big main program because making sure that you've got the correct corresponding source for that small library is hard, the whole world just uses the static library anyway and in case we do have the correct source then we probably don't use the exact same compiler as upstream so the object files would diverge from upstream. Doesn't that sound a bit ridiculous if we're talking about C? So why would it be okay if we're talking about javascript? Kind regards, Jeroen Dekkers
Re: Proposal v2: enable stateless persistant network interface names
At Wed, 3 Jun 2015 17:11:08 +0200, Stephan Seitz wrote: On Wed, Jun 03, 2015 at 12:01:34PM +0200, Martin Pitt wrote: However, on a desktop you don't ever care about the device names, and Of course you do. How will you use tcpdump or tshark without the device names? In most desktop setups a „tcpdump -i eth0” is the right command. I think people who know how to use tcpdump will also be able to type in ip addr to look up the device name they want to dump. Jeroen Dekkers -- 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/874mmnzzzu.wl-jer...@dekkers.ch
Accepted sogo 2.2.17a-1 (source amd64 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 26 Apr 2015 15:23:21 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg sogo-openchange Architecture: source amd64 all Version: 2.2.17a-1 Distribution: sid Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols sogo-openchange - Scalable groupware server - OpenChange backend Closes: 781971 Changes: sogo (2.2.17a-1) unstable; urgency=medium . * [426da082] New upstream release * [863f3b94] Update patches * [df7d5e92] Update version of libsope-dev build-depend * [fb4eeda7] Add patch from upstream git to make building with GnuTLS work again * [6c854296] Add virtual-mysql-server to suggests as alternative (Closes: #781971) * [d1bce1f6] Update debian/copyright * [552220e8] Add LSB Description field to init script Checksums-Sha1: 4fe64d8fe00581cfdfdbe88bfc13a33b18dba40e 1871 sogo_2.2.17a-1.dsc 26144d5127aa203e93b756610314cb370cd25c22 11605280 sogo_2.2.17a.orig.tar.gz f9bfbba82b1de436e9c5b3611fc3c16cf8973661 18216 sogo_2.2.17a-1.debian.tar.xz ffb551c30235c699167abec07674ffb976b1360c 1999882 sogo_2.2.17a-1_amd64.deb ac0a0e097ca3e0883b5b75ff6cb6cda5108bb3bd 1746678 sogo-common_2.2.17a-1_all.deb b7cb0287d32255688e61cb24cae13ff492fea8b6 4193970 sogo-dbg_2.2.17a-1_amd64.deb 86e0638e8ec6056f409a2e3fd0b2eef99e4029f7 1166830 sogo-openchange_2.2.17a-1_amd64.deb Checksums-Sha256: 2621db3562e9856dc5e3caafb8a7609fb998c6e0760b451c50f5408bc7b1de31 1871 sogo_2.2.17a-1.dsc ae80afd30d7fe269867e2a0c1534ce811ae67ce64053ae2fc77842cc7b298343 11605280 sogo_2.2.17a.orig.tar.gz d35743c3b2e9ac685b511090310366907b82d1e1f3e681c4de6a337fb359db3a 18216 sogo_2.2.17a-1.debian.tar.xz 6c0ac55d570234c575aa17a00021c70de7399f3ab89bb07b5714f46de590d14d 1999882 sogo_2.2.17a-1_amd64.deb a9d9b52d64f7386cd34de928f345a938ffc1c13b52027e8321a6b7c733d95368 1746678 sogo-common_2.2.17a-1_all.deb 28d05b4470f9551e3a6bdf7ca06d73e5f8f8b84ad1700c083eec20406cadb854 4193970 sogo-dbg_2.2.17a-1_amd64.deb 90b080e5e31b088fc881d6627478bf1be734727125ea03712418383436a40581 1166830 sogo-openchange_2.2.17a-1_amd64.deb Files: 021d146ed546ab87313a0e55fd1ac236 1871 mail optional sogo_2.2.17a-1.dsc d2717041656a2a8685b0da9c72d9078d 11605280 mail optional sogo_2.2.17a.orig.tar.gz 7a5c6e8cf6631b16543c147c767a3627 18216 mail optional sogo_2.2.17a-1.debian.tar.xz 8fc0205678ffd3d311f8ced18cbeab77 1999882 mail optional sogo_2.2.17a-1_amd64.deb 0628fa9ef615646655b84db5286b43e3 1746678 mail optional sogo-common_2.2.17a-1_all.deb c611e60ac1ca1e2bedffd9ffcb22c7de 4193970 debug extra sogo-dbg_2.2.17a-1_amd64.deb 1f154d3f801fed3cc11b8b6a2a171662 1166830 mail optional sogo-openchange_2.2.17a-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJVPPTyAAoJEDGCUpfTb5CBhncH/jGudNsp++sxV+86BSNRgmeP 3Tw+bHX3Wz+r5js0XIepVGfd7P8YsixBYkszqfInD5Ww03bC5SuUwMl0qo+8/kiq GZgj9h/KCn2gK+bqYoaBe5i/IDT5TneH459OLn879sAQjyNBTmX3VlL+ZpbrQ6Bf TBRkpGIgV/yACNfNLBuJhMS5hU/5OPQy5DMdjYM1LyvQNh3rt/SYttDt2tTkK9YR HfEa/QHiYcPFWCJv0UdDJO7vChyDTgDNBvfjELnRwngQ5ERObzQeN3GlTeq5l3xc Q5MNf0T1m0px2YVkXNCnP+nzqssyapawCzcCtHsKUkVLDrIJII07xu5FcjUpwm8= =EeYe -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/e1ympon-0007ct...@franck.debian.org
Accepted sope 2.2.17-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 25 Apr 2015 01:19:32 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.2.17-1 Distribution: sid Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (2.2.17-1) unstable; urgency=medium . * [2aeeedb5] New upstream release Checksums-Sha1: 2a177ad86449b35475abd5f95cd4b6381c478d30 1721 sope_2.2.17-1.dsc e11033324070cf41d22cfcb8015d4c658363afbf 2266219 sope_2.2.17.orig.tar.gz 19a8da2fe5f0b9b969cda4882b5f5a259b1b38eb 4608 sope_2.2.17-1.debian.tar.xz c4bad0862c64268bb077dfb5cb8d630e73534c80 1894856 libsope1_2.2.17-1_amd64.deb c8940904c5a07ca638bac2bf991d0d21574ed145 234156 libsope-dev_2.2.17-1_amd64.deb 56a37198c5be65a642d8de0487cfc50a8d79e93e 4345554 libsope1-dbg_2.2.17-1_amd64.deb Checksums-Sha256: 95c4e741768c2a69c048760b82c0486b64f816f21c7ed3eaa3cfea5a8571b720 1721 sope_2.2.17-1.dsc 2dc117a1a4ffb12769842c6938f953a5ccf6cf125a0cca6c57334d4923defc7e 2266219 sope_2.2.17.orig.tar.gz 133f6213c4ed15816fa89ca9355091d80774fe3f8946eb0ed010d98590654265 4608 sope_2.2.17-1.debian.tar.xz 3b137ae4b1de4846a620104da2dc6c07ffc75966d12d954a85d9703dcb652eb8 1894856 libsope1_2.2.17-1_amd64.deb d40ec147e5edaaa85707043efc65c0a62d5e8fe708710a156755d8ffe7c0f679 234156 libsope-dev_2.2.17-1_amd64.deb c9c756bd97864a4eab34c5c7aeb8fefa8494fa50b7d109d2f32c1c7a2fe97832 4345554 libsope1-dbg_2.2.17-1_amd64.deb Files: b1bfa436ded3540ff4427d4319d52e56 1721 libs optional sope_2.2.17-1.dsc dfdda424bf6a54a19f7b4ab6fde7ad67 2266219 libs optional sope_2.2.17.orig.tar.gz 14f30f1f94bc95c089128887f4c6908f 4608 libs optional sope_2.2.17-1.debian.tar.xz aae6b62eb08330eafc2cf2c57df43750 1894856 libs optional libsope1_2.2.17-1_amd64.deb 4d1ce3b58c0d604560061569ec338fc1 234156 libdevel extra libsope-dev_2.2.17-1_amd64.deb e8fcc8988a907e050b722d85d7dc054d 4345554 debug extra libsope1-dbg_2.2.17-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJVOue8AAoJEDGCUpfTb5CB0XYH/jLX+jw0odldMOhNvJtH2Wxc eh9nz/65A+HkKT8O74tPwswTE2ySRZVz+oZ0OC5b5XdZO4bfjl2snSMF5vb1od6+ nsTJkoP5GJRtGGQn4cYrAqbIRFhd82BweUfimuPd0BOf0//UsySxjYcUv2uI+Q08 VevRcqv15ocIgM+lh1noZ0p+ff10cPX816OtTPuXi+zdWdGBPvdPYByziX/SfCIE 3uTMR5o2YJhquTEV6vKDSYfQ+OJIuUFvQbUdNZX5FLPFg8spbqCHu8lOVtZbKkyo /7NwoGN3VzNnjpMPqhlsemoET2cDLMg84JpY4x+yk0mip4YBPHhcGU9urHlcPc0= =mtMi -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/e1ylokb-0004zu...@franck.debian.org
Re: Bug#781984: ITP: libnacl -- ctypes wrapper for libsodium
At Sun, 05 Apr 2015 22:12:02 +0200, David Douard wrote: Package: wnpp Severity: wishlist Owner: David Douard david.dou...@logilab.fr * Package name: libnacl Version : 1.4.2 Upstream Author : Thomas S Hatch tha...@saltstack.com * URL : https://libnacl.readthedocs.org/ * License : Apache 2.0 Programming Lang: Python Description : ctypes wrapper for libsodium This library is used to gain direct access to the functions exposed by Daniel J. Bernstein's nacl library via libsodium or tweetnacl. It has been constructed to maintain extensive documentation on how to use nacl as well as being completely portable. This package is a dependency for raet, the new transport layer for salt. I think it would be better to name the package python-libnacl to prevent confusion with nacl itself. -- 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/87d23ha71n.wl%jer...@dekkers.ch
Re: Work-needing packages report for Mar 27, 2015
At Tue, 31 Mar 2015 10:30:31 +0200, Fabian Greffrath wrote: Hi -devel, For the following packages help is requested: [... massive package list ...] is the list of packages that usually follows this line still useful for anybody? I mean, there are packages in it like e.g. grub2 for which help was requested 3972 days ago; that's more than a decade, folks! And still, the grub2 package is updated regularly and seems to be in a rather healthy and well-maintained state from my personal perception. There are some people doing their best to keep it working (kudos to them!), but grub2 still needs a lot more help. It currently has two open rc bugs blocking the Jessie release (and if you sort by bug number/age you see that it has the oldest and fourth oldest rc bug that's open in jessie+sid and doesn't have a patch). The total number of open bugs is 416 of which 113 are important. I think the signal-to-noise ration is rather low in this list. Maybe a rule should be added that packages are dropped after, say, one year after having requested help. If a package is still in a bad situation after this period of time, it may reapply for the list or should maybe get removed from testing. What do you say? Dropping packages that need help from the help-wanted list doesn't solve any problem, it only hides problems and makes it even less likely that packages that need help get help. And removing from testing isn't an option for packages for which no alternative exists such as grub. Regards, Jeroen Dekkers -- 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/87384lbgmc.wl%jer...@dekkers.ch
Accepted sope 2.2.14-1 (source amd64) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Jan 2015 14:42:55 +0100 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.2.14-1 Distribution: experimental Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (2.2.14-1) unstable; urgency=medium . * [694fef1a] New upstream release * [1b6c87c4] Remove patches merged upstream * [4da2e079] Bump Standards-Version to 3.9.6, no changes needed. Checksums-Sha1: de4a7c83cce8fbab2ec70a888c6d950259fe51ca 1721 sope_2.2.14-1.dsc f8c314b15237ff4c5cadca8a8e9b76b5986280a5 2266872 sope_2.2.14.orig.tar.gz c16b76546dd5957c86a44f32f1e545f099c03b69 4576 sope_2.2.14-1.debian.tar.xz 93ec91d7e56c31d985cb01fd9c5daf2cc08b3de1 1894732 libsope1_2.2.14-1_amd64.deb 27540fc1e6258462bc77b672c7739145d2bb198c 233054 libsope-dev_2.2.14-1_amd64.deb 77bc1e7f2ada9b4be0898a0727e938090c9ed84b 4346272 libsope1-dbg_2.2.14-1_amd64.deb Checksums-Sha256: 6aa345c1af598291579c0d6988a705ee179e7a0549807397faaa47779891ecf0 1721 sope_2.2.14-1.dsc 939095045f73700e27cb253128c72f5516328695b6528e9508d82e57eff284ea 2266872 sope_2.2.14.orig.tar.gz 9dad91fa5fc63e3074ed7d09a16e94fa4097194b0b1d63f63e196a08ae451938 4576 sope_2.2.14-1.debian.tar.xz 93f5e772ad76535f2bd64655a41820b9138ec15fc3e5b225236c389125cba7cd 1894732 libsope1_2.2.14-1_amd64.deb c09727ab52033b4118eb4339d8b5d74935b9fdbc7f906e0d20c0eb7fd11fffd4 233054 libsope-dev_2.2.14-1_amd64.deb 1ca45468612e6b64d9e8628e10647a44dec843cc8760c18ef81a32c521eb601c 4346272 libsope1-dbg_2.2.14-1_amd64.deb Files: dbe1f5d4a224ab695897d9c3f187d35e 1721 libs optional sope_2.2.14-1.dsc efce846ae52d71c8cebf91ca14a734b0 2266872 libs optional sope_2.2.14.orig.tar.gz b8bf0488ea500500a201dd7ac762bd95 4576 libs optional sope_2.2.14-1.debian.tar.xz bb85b47b2e28e10e4883e1d98e42a412 1894732 libs optional libsope1_2.2.14-1_amd64.deb f007bc70424276598fdbbb8a27daf919 233054 libdevel extra libsope-dev_2.2.14-1_amd64.deb f28135fffa9869c7716f7f7f22faf7b7 4346272 debug extra libsope1-dbg_2.2.14-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUxPbbAAoJEDGCUpfTb5CBHzsIAIvGltQqs7utk2t9fl6ZmWgS 027gUJyfnt8OlouYT400leX9UzCeyGtMe1SW3vUwykMreSgGfX8bI7KGvPNr26EK r3K/eMCSVYuYJDVArE9Skl8u3F6KMk3XGIdXHskxNeKM6ipL21F0JlUizf6zD1ap S48/zZQgHUenMH3Me4iemnlpotTAgGnAhIvoDfWmuiW6opG5Ae7pJjy0ILrracxg Y8piGY2HmaYhM0MYFrHSsz/CiQopAbHDsDuClvWC1opzoY9OqWVYmtQL5M+L4BM2 DGnNK1m07lvgJm4x/7rPZT70fIX+oBcFLinFHDBtTegW1PoXddStWV0+jk80SDQ= =8G1j -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/e1yfoyw-ey...@franck.debian.org
Accepted sogo 2.2.14-1 (source amd64 all) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 25 Jan 2015 22:42:41 +0100 Source: sogo Binary: sogo sogo-common sogo-dbg sogo-openchange Architecture: source amd64 all Version: 2.2.14-1 Distribution: experimental Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols sogo-openchange - Scalable groupware server - OpenChange backend Changes: sogo (2.2.14-1) experimental; urgency=medium . * [e1c02cf9] New upstream release * [2c109af6] Update version of libsope-dev build-depend * [fcf9733e] Bump Standards-Version to 3.9.6, no changes needed Checksums-Sha1: aa81fa9ed84d3ba7e39cc38826821fe35a3ec8ef 1864 sogo_2.2.14-1.dsc 832658016fa337b83c6fe815ac42a837c107dd66 11581370 sogo_2.2.14.orig.tar.gz c5ed9f675cfa28bd2ae9a2a54234c1e49176958c 14024 sogo_2.2.14-1.debian.tar.xz 1a1bda3160cb0c454b8047242d4ebb321b7ef738 1989256 sogo_2.2.14-1_amd64.deb b8cb0cac81c960b093817090bef51eb9ac03e534 1733354 sogo-common_2.2.14-1_all.deb 19d068926bb83ba9afd1581643b810dba44ce730 4181366 sogo-dbg_2.2.14-1_amd64.deb 829841d01874db0fc39adc34e511ed7b43524433 1162498 sogo-openchange_2.2.14-1_amd64.deb Checksums-Sha256: d98ca526b5cda89b04c3a32dca4923598af519fb0f2cf41f421f1565212d5670 1864 sogo_2.2.14-1.dsc c6d149f5ff5e256c5a68cbbe72fe20ff1b2edd6f5bebaaffad32d23783f6c708 11581370 sogo_2.2.14.orig.tar.gz c4b8ca8dfaee9ec4b0e8806e4a533e6713ca0be04e3ab1c833193639964289bc 14024 sogo_2.2.14-1.debian.tar.xz 350cc23de491e2f8fad49c2f27abff8cf6cde4f510ab4ecc396187349d19585b 1989256 sogo_2.2.14-1_amd64.deb 141560781d7ec4b8e5ab3082c73e88948b6a1f275c943911ce2ff525236f6a01 1733354 sogo-common_2.2.14-1_all.deb c9b92a7590aa63d350bdceb0d228d8ad02cae4fc2051367b1be87b887f5f5d72 4181366 sogo-dbg_2.2.14-1_amd64.deb e7882bcce997e82df486ee34c67b1b4bf105ebdebee07974725ea6002988c42c 1162498 sogo-openchange_2.2.14-1_amd64.deb Files: 75c7c40b7c4048a87b4503a1dd5aff1e 1864 mail optional sogo_2.2.14-1.dsc fee8cf317e2b8156cf08ea7044b83f21 11581370 mail optional sogo_2.2.14.orig.tar.gz e5c558515c959a0dd5544770382eae8f 14024 mail optional sogo_2.2.14-1.debian.tar.xz 530f84a304a237d975136581f3459716 1989256 mail optional sogo_2.2.14-1_amd64.deb ad09a792e8880ba90013a65877e31333 1733354 mail optional sogo-common_2.2.14-1_all.deb 412b652584d32938f10208f651a97044 4181366 debug extra sogo-dbg_2.2.14-1_amd64.deb 0b72088ccfd4d924682b31ea7eef8436 1162498 mail optional sogo-openchange_2.2.14-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUxWSsAAoJEDGCUpfTb5CBOxIH/R64UJ0wxegYO3eBhsIHQLE2 fHZ6wRgBLo5dBRZI5MgyaaeKvBdQvAISJg3TjwppQ1xDJoVtZu5eINa4bhcCVL0f S2tHUKq7S0qvXRW6dLZcWphDcqG81M76I9Ty3Ou2ZuDebTWhMPRE3K5uDPB/q+3b 5NrTFeR0yNyqC7RiGjC4C1lBcCeOJLr9FekKx9/16Bp5ndgAnDtSR6I63aDGSUwP fK7pGc/WfuNRZ1sBGpx1edlg4ojUAacXY771wh8VXxqVu2WBTVyKajJerlLphULz ioHovS/OUVBw2e5cXPXD5VWXhcQoyYscBf1mmyQH1KLTAJ6haJlRHSU3U8tLzDk= =VaDA -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/e1yfvhi-0007lf...@franck.debian.org
Accepted sogo 2.2.9+git20141017-1 (source amd64 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 25 Oct 2014 15:20:57 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg sogo-openchange Architecture: source amd64 all Version: 2.2.9+git20141017-1 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols sogo-openchange - Scalable groupware server - OpenChange backend Changes: sogo (2.2.9+git20141017-1) unstable; urgency=medium . * [6b0ddb8c] New upstream git snapshot 2.2.9+git20141017 Checksums-Sha1: 9e598a7b7de564a47ee728351af61f1771754a5f 1937 sogo_2.2.9+git20141017-1.dsc 92240721cb498efa20a7ccb5b3b099694373895e 6387504 sogo_2.2.9+git20141017.orig.tar.xz 320c67c105e32f3480909d6874b031bb96bd2d57 13960 sogo_2.2.9+git20141017-1.debian.tar.xz 0ef842db718c7f841a176052717602a654c25c37 1957420 sogo_2.2.9+git20141017-1_amd64.deb a5dc46279fdd0743927fe0f59c45d03f678b520f 1712096 sogo-common_2.2.9+git20141017-1_all.deb 884c6d0b14b28a6b5f0d8d3cc98e4638e716cfba 4140156 sogo-dbg_2.2.9+git20141017-1_amd64.deb 66d66c7e0688c9d56d8e94a63e795307b993dcba 1141936 sogo-openchange_2.2.9+git20141017-1_amd64.deb Checksums-Sha256: 5c49dcc6a2a0ffa064969d1ad00bd81d01bdbfdb7bfe44e1fca5f147d268407b 1937 sogo_2.2.9+git20141017-1.dsc 82a7a542a6ae7bfdae78704ceb17dd3b98c54a604590a1b47edafe36aac89dea 6387504 sogo_2.2.9+git20141017.orig.tar.xz 05d6b25ef49368bcebb4f3eb2a5f59ea3f6962beb6f697163b3f1a3b4dd28b1c 13960 sogo_2.2.9+git20141017-1.debian.tar.xz 31f65eafa4b57df8d99c4b042cc1c138c0b7b43a51328124f5944bed58d333de 1957420 sogo_2.2.9+git20141017-1_amd64.deb 79abd811340c426bbd5c0f8017deed566fce4e2b8a51fe75a7e83f1d10038132 1712096 sogo-common_2.2.9+git20141017-1_all.deb 12a8c2b2fac92832dcd89f96c4a3a1e6f79bc39e17a98f2f588718bfaabe71b4 4140156 sogo-dbg_2.2.9+git20141017-1_amd64.deb cd038577d50bb1e7bfc6bcd3c2ad96d121ac3608d34bc0bead649f366b9df334 1141936 sogo-openchange_2.2.9+git20141017-1_amd64.deb Files: 9355a67586fc4a23344915c0dc0d19c6 1937 mail optional sogo_2.2.9+git20141017-1.dsc 51ed22a6ed8413422050d34d0e81610c 6387504 mail optional sogo_2.2.9+git20141017.orig.tar.xz 6242ea7b8cd77cd2e4935f7507282fb9 13960 mail optional sogo_2.2.9+git20141017-1.debian.tar.xz 357741ea686f7ca95f13daa323718114 1957420 mail optional sogo_2.2.9+git20141017-1_amd64.deb 639976b1cf8338992e8f88865c93d0b9 1712096 mail optional sogo-common_2.2.9+git20141017-1_all.deb ed9005473993d5606a3a7501a96d7266 4140156 debug extra sogo-dbg_2.2.9+git20141017-1_amd64.deb 1ae01e5693bc2beee660d9b0b9ccd31d 1141936 mail optional sogo-openchange_2.2.9+git20141017-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUS6aRAAoJEDGCUpfTb5CB+y8IAILvySfkt2PhcCXaNTZdu9Bj hIB4NxoNSe9l+uKjn1/CykWuUS6WZ5EzzeTdSlYL4/xDySyyLytvISC69/+DAqhs VshBeV63T4fHBM1V3xKxf2eD9vdmIvd0KpG84bcpkEYcaAMR0ncvcZKboVtBOCvi M9smFHcIWo24qPnQ3z8uShVwFQbzPLiJ5SqFPYGQd+OMs/HPGsWIFxipSpYyPs3L H10X4ixjK69YHzOiKePhs0eIRZo9AOFaDJN0edT4YqhjjWEnOq8zV6YvRGpovaA+ k2bez3CukLUxPvuzPu8WEoILWFet6qCo0mfkGamvElPQ52U8GVXbvWwAUv1UCas= =QYqT -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/e1xi1ix-0002cz...@franck.debian.org
Re: piece of mind (Re: Moderated posts?)
At Mon, 13 Oct 2014 13:23:16 -0400, Miles Fidelman wrote: Henrique de Moraes Holschuh wrote: On Mon, 13 Oct 2014, Matthias Urlichs wrote: In any case, users _do_ have a say. They can force their systems to remain on sys5 init, or switch to a different distro if that should also turn out Which, I should add, is something we measure if the user installs popularity-contest and opts-in to its measurements. http://popcon.debian.org/ which sure seems to reinforce the popularity of sysvinit 18sysvinit 697126 583755 44903 63528 4940 19imagemagick671330 54630 97400 59765 459535 20pam664835 424521 161793 74475 4046 21evolution-data-server 661614 129835 138891 91065 301823 22perl 642831 412336 121683 76726 32086 23systemd630568 287748 54129 57693 230998 Then again, how much of that is simply an artifact of default initialization, vs. by choice, is unclear. Comparing those source packages is just comparing the previous essential sysvinit package against udev. If you want a better picture you should look at systemd-sysv versus sysvinit-core: 2335 systemd-sysv 19845 14413 925 4504 3 (Debian Systemd Maintainers) 4623 sysvinit-core 5634 4866 576 191 1 (Debian Sysvinit Maintainers) Sysvinit-core was introduced in jessie and systemd-sysv conflicts with sysvinit-core. Systemd-sysv is also available in wheezy, but there are 24486 reports from the popcon version 1.61 (testing/unstable) which means only about 1000 of the systemd-sysv installs seem to be from wheezy. So a big majority of the testing/unstable users don't seem to have a problem with systemd, just like a majority of the DDs don't have a problem with systemd or else we would already have had a GR. It would be nice if the minority which doesn't like systemd would just accept that systemd is the default init system in jessie and that the majority of developers and users don't seem to have any problem with that. Kind regards, Jeroen Dekkers -- 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/87wq83lt6p.wl%jer...@dekkers.ch
Accepted sope 2.2.9-2 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 13 Oct 2014 11:53:51 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.2.9-2 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Closes: 764474 Changes: sope (2.2.9-2) unstable; urgency=medium . * [2fee7766] Update arm64 patch. Thanks Edmund Grimley Evans. (Closes: #764474) Checksums-Sha1: 161209f62807cbff1229200a9255c732f14fdc49 1714 sope_2.2.9-2.dsc 238a67bc98378d8517770efac2ddf4f02a86a16e 5024 sope_2.2.9-2.debian.tar.xz e32ba00321a8ee541ac7702b92c2a70a61d9bb30 1887462 libsope1_2.2.9-2_amd64.deb bb0f4988f3fec8578732a6bcd42f4211b6bcde16 227706 libsope-dev_2.2.9-2_amd64.deb d311f8458c55d97ba16dec80edccb3a8305f04a4 4323970 libsope1-dbg_2.2.9-2_amd64.deb Checksums-Sha256: 76e4ffee693d17f74d715c558842e9f969bda76131c12d4bfa71fedccf6bab9d 1714 sope_2.2.9-2.dsc 9db035c66343fa33d8067ce1ad1b24d9d8d868e143f78fa4e6964e7e53aabc1f 5024 sope_2.2.9-2.debian.tar.xz 2d06f3018d1e67ea33176ffa9175e5fb21581d47d1e3fb7a495871cd0d7fa725 1887462 libsope1_2.2.9-2_amd64.deb 6fc7888ca5812c133d201c5522359922de23495acd9204199cb4d40cf0f126e9 227706 libsope-dev_2.2.9-2_amd64.deb 81505266c9bc701c2451671635e94c73dbca09d470aebc84922d83c784c4df68 4323970 libsope1-dbg_2.2.9-2_amd64.deb Files: 073bd4b1e0159e4f15635f5e6db17d08 1714 libs optional sope_2.2.9-2.dsc 9d07cc539cf914daea86cc301ed06522 5024 libs optional sope_2.2.9-2.debian.tar.xz f3d62b3ed0d576779eac1c91f7fccad0 1887462 libs optional libsope1_2.2.9-2_amd64.deb a507b69025daa9c2d96c561796182a4a 227706 libdevel extra libsope-dev_2.2.9-2_amd64.deb 6f4211d18b111f4941eb06164d24084d 4323970 debug extra libsope1-dbg_2.2.9-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUO6KDAAoJEDGCUpfTb5CBKFgH/04ANp7I7OWC3f91FV5pJdP7 X9+bdGpTnY1Hb1477y/YwsO5ukoHrh9F2nxBM3VHCC7nFs4Pdjpvm9X+S0fQErM3 xFAr2RHiNqQNMiN8YOjBANhh1DL8qN6kN5OMO7TWokOLFgSpPpPBJBBE/khz+0mw rjP2596iX9PhV0R5P6nqH8iQ4VmRlxMOfJ1czps7LOgxFuXvpuke6ecUGlQpKIZk 5M2JL5a5W7aGg8357y+PKqyJK5csFzLY83civ2CxYrh1PCzbvnb1BJc7VY9k4huD OmxHVX+ltZkKcULCkLCzaprLB5FlVeHIn4X7/Ve6UcsAD5izWkrTabSNTQH4K5M= =Qn1f -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/e1xdcjd-0001iq...@franck.debian.org
Accepted sogo 2.2.9+git20141009-1 (source amd64 all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 13 Oct 2014 16:45:20 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg sogo-openchange Architecture: source amd64 all Version: 2.2.9+git20141009-1 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols sogo-openchange - Scalable groupware server - OpenChange backend Closes: 754909 757949 759857 Changes: sogo (2.2.9+git20141009-1) unstable; urgency=medium . * [effac894] New upstream git snapshot 2.2.9+git20141009 (Closes: #754909, #759857) * [9890d799] Remove patches merged upstream * [035175e6] Update sope and openchange build-depends * [118c54a7] Add patch to remove build date from package * [c74b2830] Fix short names in copyright file * [286ab24c] Use logrotate script from upstream (Closes: #757949) Checksums-Sha1: 72d353e81ae5e014a3b674a55ed5b1d666e0e75e 1937 sogo_2.2.9+git20141009-1.dsc afcb8448df7a1946ad96fb7aefa854d2cd282133 6386832 sogo_2.2.9+git20141009.orig.tar.xz 818a2c122ec23e8c4de6b46101dce3d67b738237 13940 sogo_2.2.9+git20141009-1.debian.tar.xz 596d2deebee154d263f37be6e86931dc37cce81a 1957844 sogo_2.2.9+git20141009-1_amd64.deb 53d307816d01d1c351073f40cac50c438922e718 1712176 sogo-common_2.2.9+git20141009-1_all.deb 7b5a13614e3f2eb79db8fda28617d1cf5b5ea5ef 4140166 sogo-dbg_2.2.9+git20141009-1_amd64.deb c2cbd8d7a4de68707a3a05ecaa6f84a8ac6eb5d1 1141084 sogo-openchange_2.2.9+git20141009-1_amd64.deb Checksums-Sha256: e16adf2eec93b9e8f4d2b36e0abbb79733d175a5a7f47d62d73f0b025acaace8 1937 sogo_2.2.9+git20141009-1.dsc 9b0dbc012439101d5bf6ba9c0d3188940a6aa5b46311bb8ae3c9d5fabcf6883d 6386832 sogo_2.2.9+git20141009.orig.tar.xz b7dd1f527a66b58a792f50a4cbb775defe01ad8a7a660572e162295dd8e3c8a7 13940 sogo_2.2.9+git20141009-1.debian.tar.xz 050bc78a3bf171ae85343ba96c05adfd133ac5ee1b2db9ea7d4a9be0ac2cdf2e 1957844 sogo_2.2.9+git20141009-1_amd64.deb 79133df32da0563f0a92dc78b88a088b44fddf9a3499b07a7c45440ba9388b35 1712176 sogo-common_2.2.9+git20141009-1_all.deb 213a2fcd542096f77abbc9d472d90093ea5ed7f62e77c87679b01b993fbbc15e 4140166 sogo-dbg_2.2.9+git20141009-1_amd64.deb ea09c95f99387024f777f743e168479e701934fc73d63443def1ab16ad62162c 1141084 sogo-openchange_2.2.9+git20141009-1_amd64.deb Files: ac514e19a406b5d405337481cd1b7605 1937 mail optional sogo_2.2.9+git20141009-1.dsc 2dcdbdda958059a4f7395833b2891a47 6386832 mail optional sogo_2.2.9+git20141009.orig.tar.xz 5d5be8c1ec69cd9fede10dd831f479ee 13940 mail optional sogo_2.2.9+git20141009-1.debian.tar.xz 7cb425c5ee85d209a304f1892cfa305c 1957844 mail optional sogo_2.2.9+git20141009-1_amd64.deb be972a0b99b210781e97621328310d33 1712176 mail optional sogo-common_2.2.9+git20141009-1_all.deb 0bcbced60826bbc6bb0227c47b38b8f5 4140166 debug extra sogo-dbg_2.2.9+git20141009-1_amd64.deb 36eb59710a72b658c62e96b7d78c67cc 1141084 mail optional sogo-openchange_2.2.9+git20141009-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUO+kBAAoJEDGCUpfTb5CBh8kH/Ag3iuGGycnb/GMT4X4S3GfR iHMD5IMpRFvDfYiHDjVd0zewao3yEwLmhqivXQF2Qv8DNRCIEEKKYL1NCVirK3Ac SCvEpx7n59OvQMI+v78/oc5FlbuqWdVGWDt3muVojG5bjCoTBw3oK59rpsNwMGXT L2GvYbf6XSR6AJvlQx5M/dmvlMXFQgxTlwQjhgsuByjXVGqW/XU2eZ4RKeQjnVn0 TPMFnt5xRNcRuMx6x81hr2F1buZlB4X5Nm7+AvK30BoqNVGiOPNxtCY/p3ohOX9K 3Ukalry28wa9/y77MYHaWxSBbLpkDO03Ra3NoRe7CKNDkHadBEBmSd8wW0gxqxw= =ZLFf -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/e1xdhsd-0007vh...@franck.debian.org
Accepted sope 2.2.9-1 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 04 Oct 2014 21:24:51 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.2.9-1 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (2.2.9-1) unstable; urgency=medium . * [6e472429] New upstream release. * [f54b5e33] Add patch for arm64. Checksums-Sha1: ed8f62422c403a1c170b365837918d2caf24bbca 1714 sope_2.2.9-1.dsc 1d7e2603be2cf1458998858e8b7b2798609ff0ab 2262388 sope_2.2.9.orig.tar.gz 917d0b87d59247c5afc3f7c9ffb08c5a156f0581 4732 sope_2.2.9-1.debian.tar.xz d00b330fe367b1337bcce90485bda2a79afd12ca 1887530 libsope1_2.2.9-1_amd64.deb aa3e5b3d2625b1def7148beca91cd1155330f6dd 227616 libsope-dev_2.2.9-1_amd64.deb 21e6ead3b705842fab933487cd7408b4fb40cc86 4324782 libsope1-dbg_2.2.9-1_amd64.deb Checksums-Sha256: 9ef36457b8b876aeb415d5861e990dcd83d3e3c58b4ea111965a503fcb1864e0 1714 sope_2.2.9-1.dsc 3c8f6e844fd91047b07a0f594783ba2c738f4df6962b1247bf52ee44a20f5ab1 2262388 sope_2.2.9.orig.tar.gz 0e02ced7490eb4b7c732cbb3d6dddbf9dbb29539bf7c261588aa934b1da6d10a 4732 sope_2.2.9-1.debian.tar.xz a71a81af94a7ec20130b5cb59586f57d1246a0ae709c2ac099a74b1c0d23a80d 1887530 libsope1_2.2.9-1_amd64.deb 49f227dbdec056d50d168871fb8b4256503b01652fcfaf9fef88d59f51e0bb83 227616 libsope-dev_2.2.9-1_amd64.deb 316cece51d7d495331d79e9fa57a5f5f6f912cd45a36be62f568733c65354608 4324782 libsope1-dbg_2.2.9-1_amd64.deb Files: ff38b35397b86cb9b81b62c4be0b892f 1887530 libs optional libsope1_2.2.9-1_amd64.deb 5664c8942475f450fab86f730eb0d756 227616 libdevel extra libsope-dev_2.2.9-1_amd64.deb 76851e3aac394937b14f3976718607b3 4324782 debug extra libsope1-dbg_2.2.9-1_amd64.deb 34b3ac6edd24e980d6a5806750fb32f1 1714 libs optional sope_2.2.9-1.dsc a20d2a2e2466265e85294b107a113266 2262388 libs optional sope_2.2.9.orig.tar.gz 52f627d37892db2e85ad16a341c7adba 4732 libs optional sope_2.2.9-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJUMErxAAoJEDGCUpfTb5CBYp8H/A0UOXGOZBJo4uYpIx7JfQZF Ay7hxr6fYF9er59h+Ut8MMF3F9MfWX2jomZgj59AL/c3LOCih4sfy6OF3wrp4XVM l/WlnGaM/+Pe+znYnQ/HCMXIZW2o75bTRO+RrzRcJXWtAmPFG5TMTaL0OcDWrb7u LO4FQIi29qtzrW7BWgq3O1gC2RRECy56dqIrwlSVgNPmKlOwhUiuh20s8ezirzJI p4OVMj7O6jt68eV/ykVhpkzAghDLkY5Tvkj4tj0gXV75lUMZ5zXoTcBGTydZlaIh i1jrWk8AK2kowQKLqgUB9Yt2+R08vapgLShVwerZdZEpW7yWMjA/98EPlQzNhRU= =oVFJ -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/e1xav8j-0003kx...@franck.debian.org
Re: apache2 issues
At Tue, 23 Sep 2014 08:51:56 +0200, Jonas Smedegaard wrote: Quoting Brian May (2014-09-23 08:02:22) On 29 July 2014 19:04, Jeroen Dekkers [1]jer...@dekkers.ch wrote: As far as I can see this is a bug in the apache2 packaging. The httpd virtual package should be provided by the apache2 package, not the apache2-bin package, because the apache2-bin package doesn't provide a working webserver. Bug report I just filed about this: [2]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756361 Ok, this bug was fixed, leading me to re-investigate this again. It isn't very easy to specify what httpd-wsgi should mean, because some WSGI servers are full webservers with WSGI support such as apache and others like gunicorn are only supposed to run behind a proxying server such as apache or nginx (similar to for example php-fpm). So as far as I can see, the correct dependency should be: Depends: libapache2-mod-wsgi | httpd-wsgi, apache2 | httpd So it also possible to run other webservers. I just noticed there is still another potential problem. With the above, either libapache2-mod-wsgi (Python2 only) or libapache2-mod-wsgi-py3 (Python3 only) will satisfy the depends. Does this mean I should also depend on both python-* and python3-*? Even though only one will ever get used? What happens if the package only has Python2 or Python3 support, not both? To me, it is starting to look like we need two virtual packages for httpd-wsgi - one for Python2, and one for Python3. Then I can explicitly set use one my Depends (e.g. Python3), and not worry about supporting the other Python version (e.g. Python2). Isn't that an implementation detail? Is Python version relevant for the on-the-wire WSGI protocol? WSGI is an API, not a wire protocol. The Python version of the WSGI server would also be the Python version the code is run under, so we must distinguish between Python 2 and 3. The best way would probably be to specify that httpd-wsgi is for Python 2 and create a httpd-wsgi3 virtual package for Python 3. Jeroen Dekkers -- 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/87wq8uhio5.wl%jer...@dekkers.ch
Accepted sope 2.2.7-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 13 Aug 2014 17:35:52 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source Version: 2.2.7-1 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (2.2.7-1) unstable; urgency=medium . * [0fb5a480] New upstream release. Checksums-Sha1: 561e1a953254171264e449834817880a540ec26c 1714 sope_2.2.7-1.dsc 2e3be65f121d37f69fcc332b9c8b956cf94d85d0 2261984 sope_2.2.7.orig.tar.gz 254da760a6ccc3184b1e0789083b987e5ccd16ef 4408 sope_2.2.7-1.debian.tar.xz Checksums-Sha256: 408def7382d159fc35f82ca54ebd06f17ea9aad1bafabbc13ff02a6be5614661 1714 sope_2.2.7-1.dsc 06c7973fa11cb02c4255a861e0ee43007ccb7224e2c912fffe298d421191aa2c 2261984 sope_2.2.7.orig.tar.gz fa694b4a08e4bc5138fe024ea8316d68986b0c0e2d534522904685829f423e57 4408 sope_2.2.7-1.debian.tar.xz Files: 13e9c575b0e842a7f12192896f88bb64 1714 libs optional sope_2.2.7-1.dsc 54b2c2d2c4e2f6c7658a0ef77853e7b7 2261984 libs optional sope_2.2.7.orig.tar.gz 273395ba4a73013d1b185f78402a29d5 4408 libs optional sope_2.2.7-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJT64r1AAoJEDGCUpfTb5CB91QH/36qbu3saS4OFDAZoyYw6fCc H3hpvy2LeeDsQL1z6nHD2Cxwb0PqjT2mmNzswx0Q5t9P6iv8as4xRXZOT2Y6VEqa QW1ua3fsmXaLqjGbnbuZJ/Jh2LMWhh94TJ9rPLs6RPlvv7cl0i7PX7q8+Rlj3TQU GVXYUyS+KpoHOsS3BzDPR1LZzH1WzdkmFq/7vj3T5dWGJUNZCTPn8bT9rhQJxsOB 2pYG52fxqwY9AYg7Ytof3ywCgZVC9/wVg5UsfXNyl5HTYDwoHkEI0heWsPeDWdi2 nR+X2b3caOK5Kp/tStKk1Yt8mGG1TPT8RAS392HS9oyVpfKvZ/eU/YlETNCQ1uw= =mFn3 -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/e1xhbgj-0005wt...@franck.debian.org
Re: Bug#756521: ITP: kadeploy -- Scalable, efficient and reliable cluster provisioning solution
At Sat, 02 Aug 2014 14:35:33 +0100, Simon McVittie wrote: On 02/08/14 08:03, Charles Plessy wrote: A straightforward way is exemplified by the case of SSH, where the server keys are regenerated if they are absent. It then only takes to delete the keys when preparing images to avoid the problem of duplicated IDs or privacy leaks. D-Bus (/var/lib/dbus/machine-id) also regenerates its machine ID during boot if required, although systemd (/etc/machine-id) is not always able to do so (because it's pid 1, and our initramfs does not fsck the root filesystem, systemd typically starts before the root filesystem is read/write, but it wants to be able to have a machine ID immediately). As of jessie, each will copy the other's idea of the machine ID if it exists, or create a new one if not; in wheezy, systemd would copy the D-Bus machine ID, but D-Bus would create a new ID rather than copying the one from systemd. Some component still needs to know that those specific files should be reset when preparing a generic image, and how to reset them - for systemd it is actually better to truncate /etc/machine-id than to delete it, because if it exists as an empty file, systemd can do tricks with bind-mounts to mount a transient machine-id over the top, copying the one from dbus if available. Perhaps it would be good to define a reset-machine-state dpkg trigger or something; then tools like live-build could trigger it, and dbus could take responsibility for deleting /var/lib/dbus/machine-id when it is triggered? live-build etc. would have to keep their current hooks for now. I really like the idea proposed by the systemd developers: it should be possible to just remove /etc and/or /var and the system should boot and populate /etc and /var with the necessary files: http://0pointer.de/blog/projects/stateless.html Kind regards, Jeroen Dekkers -- 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/878un6mx6o.wl%jer...@dekkers.ch
Re: Bug#756172: ITP: ssh-cron -- cron-like job scheduler that handles ssh key passphrases
At Wed, 30 Jul 2014 22:17:43 -0700, tony mancill wrote: I contacted the upstream author (on the cc: - hi Frank), and his concern with the passphraseless key trigger mechanism is precisely that you don't have a passphrase. The key is unprotected and subject to theft/unauthorized use. This could potentially occur on the system that is (normally) the legitimate source of the trigger. But ssh-cron will need to have the passphrase to be able to use the key, so someone who can steal the key from ssh-cron can also steal the passphrase from ssh-cron. What is the added security benefit of storing a key and passphrase instead of a passphraseless key? -- 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/87ppglmbor.wl%jer...@dekkers.ch
Re: apache2 issues
At Tue, 29 Jul 2014 17:29:46 +1000, Brian May wrote: On 29 Jul 2014 16:44, Wouter Verhelst w...@uter.be wrote: No, I don't. What brian really wants is apache2 or apache2-bin. In the case of apache2-bin, he needs an additional dependency on libapache2-mod-wsgi. Really, it should be apache2 | libapache2-mod-wsgi, apache2 | apache2-bin to do so. Not sure I see how this is any better than just: libapache2-mod-wsgi, apache2 (Which is what lintian warned me against using) Installing libapache2-mod-wsgi and apache2-bin without apache2 is insufficient, for Apache support to work, I need /usr/share/apache2/apache2-maintscript-helper which requires apache2 to be installed. So we can replace that 2nd term with just apache2. As far as I can see this is a bug in the apache2 packaging. The httpd virtual package should be provided by the apache2 package, not the apache2-bin package, because the apache2-bin package doesn't provide a working webserver. Bug report I just filed about this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756361 Similarly, installing apache2 without libapache2-mod-wsgi would meet your depends but not really be satisfactory. Either way, it sounds like I should be ignoring Lintian. No, lintian is correct and should not be ignored. Depending on only apache2 makes it hard to run other webservers. There is a also httpd-wsgi virtual package: https://packages.debian.org/sid/httpd-wsgi A policy bug about what httpd-wsgi should provide is still open however: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588497 It isn't very easy to specify what httpd-wsgi should mean, because some WSGI servers are full webservers with WSGI support such as apache and others like gunicorn are only supposed to run behind a proxying server such as apache or nginx (similar to for example php-fpm). So as far as I can see, the correct dependency should be: Depends: libapache2-mod-wsgi | httpd-wsgi, apache2 | httpd So it also possible to run other webservers. Kind regards, Jeroen Dekkers -- 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/878unco7rv.wl%jer...@dekkers.ch
Re: Solutions for the Apache upgrade hell
At Wed, 23 Jul 2014 01:52:30 +0200,
Arno Töll wrote:
However, if you call aptitude --purge-unused:
- apt purges apache2.2-common. This calls apache2.2-common's postrm
purge, wiping all our configuration
- install apache2{-bin,-data}
- preinst apache2 detects an upgrade, but has no clue about the previous
state, because apt purged everything before we could look at it
- force removal of old modules as there is no apache2.2-common anymore
- postinst apache2 is a bit helpless and works through, but does not
treat the installation as new and does therefore not set system defaults
as it thinks we're upgrading
What about doing a stable update to apache2.2-common adding a
confirmation prompt to one of the maintainer scripts similar to the
confirmation prompt you get when you remove the kernel you are
currently running? Such a small change should be okay for stable.
We probably don't want to add a confirmation for every purge, but I
also don't know of an easy way to figure out that the package is (1)
purged and not only removed and (2) that is done because of the
upgrade. When postrm is called with purge the configuration files
are already removed, so that does't really help. Doing ps auxww |
grep purge is a bit hackish, but maybe it is good enough for what we
want to do.
With regards to detecting the upgrade, the first thing apt does is
purging apache2.2-common, so none of the other apache packages are
installed when that happens. Maybe it is good enough to check whether
the apache2-data packages is available? Detecting that the purge
happens after the upgrade can probably be done by checking which
package owns the configuration files.
Kind regards,
Jeroen Dekkers
--
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/87k374nurl.wl%jer...@dekkers.ch
Accepted sope 2.2.6-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 22 Jul 2014 16:33:46 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.2.6-1 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (2.2.6-1) unstable; urgency=medium . * [024cdc82] New upstream release. Checksums-Sha1: 37b51b0dcc8750a563ed32854ad8857f6f3ed876 1714 sope_2.2.6-1.dsc 9142a8226c9e7633c02217744c6cb06402212fa1 2261306 sope_2.2.6.orig.tar.gz ec1083e0aff74c0b56bb66797d68db48afe05f3b 4392 sope_2.2.6-1.debian.tar.xz 1bcc3ce2a65f6d6fe2030b7e45237764a1929ded 1878468 libsope1_2.2.6-1_amd64.deb 3fc6b5ae238b683a4a28c16a7e96ade78a1095ba 227942 libsope-dev_2.2.6-1_amd64.deb 4dd3147b392f09fb6c454a6ed3200ec7ad53cb04 4305192 libsope1-dbg_2.2.6-1_amd64.deb Checksums-Sha256: 2d0622ba58a581cff8fd2dececfa35fb08a3b24184b6186bd2fcd268242b4465 1714 sope_2.2.6-1.dsc 6f8cc0f0168eb8b38dab980d69e9ced24d26931b78c67ad8e15ce1ece0ccafd8 2261306 sope_2.2.6.orig.tar.gz baab88cbcb3f6fe54a7ecd9ab9cfda2045782479be7a30b2628a69a7006f4691 4392 sope_2.2.6-1.debian.tar.xz 5147752e18437461403106bdaedb43fe31e904350adcde27395cb6abe21076ea 1878468 libsope1_2.2.6-1_amd64.deb 3f596b39fb4a9e6c3539169d2ce27cee832ca2a3ab7f4854eec2bf138e0e1d07 227942 libsope-dev_2.2.6-1_amd64.deb f0934ab22281b1d6335cf8de8b9f6a05fe81fb9be8084f19192fbfdd53f46c19 4305192 libsope1-dbg_2.2.6-1_amd64.deb Files: a992a422304c5311b9832aeb58d96d86 1878468 libs optional libsope1_2.2.6-1_amd64.deb 192c66740f97c5a5dba86de5fd900449 227942 libdevel extra libsope-dev_2.2.6-1_amd64.deb 945f538eec1eb8992513ea6d642746f0 4305192 debug extra libsope1-dbg_2.2.6-1_amd64.deb c00d0780439f4bb4760de2fbc145cf27 1714 libs optional sope_2.2.6-1.dsc 6ef2d0c2cb2015c03971d06411138865 2261306 libs optional sope_2.2.6.orig.tar.gz 57f91cb5ad91baea755b8908ec5a1ed2 4392 libs optional sope_2.2.6-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTzoACAAoJEDGCUpfTb5CBiGgH+wYXVwaXNeLvsh7oUBYEI4Zh 6nYp0pT6vBUFsKnEgskO2iDsBzk8ML2LJPMsMNlmy0dItfTgx7ZLwxRMvKpSdt+k M5PBRbPOgDlLe9ATNvAdSKualijY38NKWzcwqwcAo/ndt6ce7Jqauz8TiNtMgz3p mIn5/+eFnxFOVpBWH3souy4TsYNrjEF4Po/1vBN3iBgOWGzU98QJyQ0W1iAXuztM K7nIBgBwFQYFy5onTbrwTEF18ff69Zkm4URMaClRZ4b0lYJaRP4EXl8XY4tSePBS 4MOdAH5/HkoI0/OZMt0uPK91whKuiRsvSI07XNXkjNfwqm/SdB5FxUrYbh0tW7g= =lF/Y -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/e1x9c8v-00077i...@franck.debian.org
Re: people.debian.org will move from ravel to paradis and become HTTPS only
At Sun, 20 Jul 2014 11:07:16 +0200, Wouter Verhelst wrote: Even ignoring that, assuming people trust that code off people.debian.org is safe, if they run a validating DNS resolver they don't run more of a risk than if they use only HTTPS. I don't really follow that. A validating DNS resolver only makes sure you connect to the right IP address. DANE can specifiy the certificate to use for HTTPS, but you can't forward HTTP requests to HTTPS with DANE as far as I know. In the case of HTTP a MITM attack can send a fake response to the HTTP request without the need for any key material/certificates or need to fake DNSSEC. For HTTPS it would need to have a certificate for people.debian.org that the client trusts. Kind regards, Jeroen Dekkers -- 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/87silwjo6w.wl%jer...@dekkers.ch
Re: Bug#754551: ITP: node-ms -- milliseconds conversion utility
At Sun, 13 Jul 2014 09:26:38 +0200, Vincent Bernat wrote: ❦ 12 juillet 2014 23:08 +0100, Steve McIntyre st...@einval.com : And I've got to ask: for the couple of trivial examples that Frederick pointed out - why on earth do these even exist as libraries instead of being inlined wherever they're needed? Because, in node, a library is cheap and the functionality get unit tested. That's why there are so many dependencies in this ecosystem. You have all the extra metadata, extra git repository, extra dependency tracking, etc. no matter how 'cheap' a library is. And as far as I understand npm (correct me if I'm wrong, I don't use npm very often), it will install dependencies in a nested way, so if app1 use library1 and library2, and both those libraries use tinylibrary1, tinylibrary2 and tinylibrary3, then those 3 tiny libraries will be installed both under library1 and library2. I wouldn't really call that cheap. -- 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/87wqbhy54i.wl%jer...@dekkers.ch
Re: Bug#754513: ITP: libressl -- SSL library, forked from OpenSSL
At Sat, 12 Jul 2014 14:46:45 +0200, Toni Mueller wrote: On Sat, Jul 12, 2014 at 02:15:13PM +0200, Kurt Roeckx wrote: 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. OpenSSL was part of OpenBSD before they created the LibreSSL fork, so how isn't OpenSSL part of the OpenBSD track record? 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. 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. * 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. You forget one of the big problems with OpenSSL that LibreSSL doesn't fix: the license. 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. 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. * 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. Kind regards, Jeroen Dekkers -- 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/87vbr1y2va.wl%jer...@dekkers.ch
Re: Solutions for the Apache upgrade hell
At Sun, 13 Jul 2014 13:17:24 +0200, Arno Töll wrote: What would you do in our situation? Side note 2: We kinda expected this situation and added a trapdoor in Wheezy [1], but it turned out, that even that is not good enough to prevent havoc with --purge-unused. It's not really ideal either, but another option would be doing an update in the next wheezy point release preparing this migration. For example moving the configuration files from apache2.2-common to apache2 or apache2.2-bin in wheezy shouldn't cause any problem and after the files have been moved apache2.2-common can be safely purged during upgrade. Moving them to apache2 package would mean you won't have to move them again in the upgrade to apache 2.4, but it would create a new and circular dependency of apache2.2-common on apache2. Given that apache2.2-common already depends on apache2.2-bin and there exists a transitional package in jessie it might be a better candidate. Then you would have to move it again in the jessie package, but I'm afraid there aren't any easy solutions. Kind regards, Jeroen Dekkers -- 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/87r41pxv50.wl%jer...@dekkers.ch
Accepted sope 2.2.5-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 08 Jul 2014 14:17:08 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.2.5-2 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Closes: 753153 Changes: sope (2.2.5-2) unstable; urgency=medium . * [6815e7fe] Build-depend on libgnutls28-dev. (Closes: #753153) Checksums-Sha1: 24b1bbbc1d7121f9fe71383b6009afa08d197b07 1714 sope_2.2.5-2.dsc b8373894b8e371ef7480d5d1fcf8a75065abeb3b 4376 sope_2.2.5-2.debian.tar.xz 65ee9b9dd00d6b0ce95d192a4b99fb7793e2099c 1877330 libsope1_2.2.5-2_amd64.deb 80cb1c12a6e8b95b203d29996593425997ac1b4b 227532 libsope-dev_2.2.5-2_amd64.deb 860b777a4906d63bef3e347508b7f8e1635ad7c5 4300290 libsope1-dbg_2.2.5-2_amd64.deb Checksums-Sha256: 6b225ca65bcd8a6eab79d2d1bed36d5235362e63bd559927e11c5a563340ef54 1714 sope_2.2.5-2.dsc 4095cbb810714bf33d951b2d2c990757cc347ee80f5f786cb720da3f20298bf4 4376 sope_2.2.5-2.debian.tar.xz 9d385ca96de43180d251ca246fe0fd01e4a2286259603667693a00a9c431befc 1877330 libsope1_2.2.5-2_amd64.deb 82f593383bb742ad16623acf72756aacc9b3dc6037a86c15541dc4ca8de12982 227532 libsope-dev_2.2.5-2_amd64.deb af8fc130107440bb2f64d664e6cb3fc5959861650e8cc27521d6dd2dd54e63b6 4300290 libsope1-dbg_2.2.5-2_amd64.deb Files: 7f60a3088c3f854a370fc71ad6c336a1 1877330 libs optional libsope1_2.2.5-2_amd64.deb 23dea3b39c1a1b5dbe8ba2312d6eb6f7 227532 libdevel extra libsope-dev_2.2.5-2_amd64.deb 5182e82590697eb84b43cc7a19a41192 4300290 debug extra libsope1-dbg_2.2.5-2_amd64.deb eb2372f6b497647419976c93a33bc46b 1714 libs optional sope_2.2.5-2.dsc 2250c7e70c58b7b4865388722a9183e2 4376 libs optional sope_2.2.5-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTu+PFAAoJEDGCUpfTb5CBUUoH+QEpnmRdSwTyvW2/t6GJmj/2 rAFWT9mOi+BDmh+k/ql5leW3Gj7XSyth9lQIT3cY3t6BOHexgjbshusos7KrAIOU E8/7WIjGQFRFJXkD2LH3AyG4Gf4P33XDkNffr44OF+RHiBBdsBFl9e5LQBgSXG9J WdYGBEWU2ZMGEOJO2V51zncw2vcqmbK6L6tfon3e/EypXAOpVsf0GNQJaKzdCLR8 YlSUTwLvQutpwmsoWyUW6/smWJYVVvHr0JQKPj3HtkGopwDrE1prHKlVFtNMfAAj lD6NDqH25Z7W/A+cezVQScgBEO4k4n47TyCluWoXOKVuWOWr6jGfUChYuCEeX1Q= =YEA4 -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/e1x4ube-0003gs...@franck.debian.org
Accepted sogo 2.2.5-2 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 08 Jul 2014 14:20:53 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg sogo-openchange Architecture: source amd64 all Version: 2.2.5-2 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols sogo-openchange - Scalable groupware server - OpenChange backend Closes: 754171 Changes: sogo (2.2.5-2) unstable; urgency=medium . * [7613c6cc] Build-depend on libgnutls28-dev. (Closes: #754171) Checksums-Sha1: 6a5abd72dec3f73a4b491f3477004bdd0091db87 1889 sogo_2.2.5-2.dsc 02a1bbd2d3aa81eeb573b9ed7475de85c037fee2 15120 sogo_2.2.5-2.debian.tar.xz f1761eb2163dd196f9f24dfff5ef74b1f79090b7 1923556 sogo_2.2.5-2_amd64.deb fec6897324bc56dc3d9ab909501da88a5221216a 1678750 sogo-common_2.2.5-2_all.deb 567c887430ff94577c402430dd520f750127bf23 4064826 sogo-dbg_2.2.5-2_amd64.deb 4a6478aeeeb28c9d83164dc708b853ec6c98db89 1120466 sogo-openchange_2.2.5-2_amd64.deb Checksums-Sha256: 17d37964a0fefc4777b0544fb97282d66b0ad546384113cac5952f81589b0107 1889 sogo_2.2.5-2.dsc 0b147a636f2c1d576a3608c55522f83e30a2e1c237ae2d4b7ae658dfeb736dba 15120 sogo_2.2.5-2.debian.tar.xz 7b841271a5dcb364ecb3afffe73890ab32c4acc3aba3a2ba46c02585585df070 1923556 sogo_2.2.5-2_amd64.deb 6a04bdfb50d4a954f4756de6f11e81b3d03c9202adf1f08dde765f9b3518d430 1678750 sogo-common_2.2.5-2_all.deb eb9b734306fcc795d580edc435cf4272176500da96c14c41bb9464c2b9ff 4064826 sogo-dbg_2.2.5-2_amd64.deb da9513599cdd704e393fd2ebffa45b7851d17f1c1badd16165fd3a8e58505e48 1120466 sogo-openchange_2.2.5-2_amd64.deb Files: 753d18a1910359adbb0287599c6e5d14 1923556 mail optional sogo_2.2.5-2_amd64.deb 30b0254d2eee1c2423d6ef22cc0049c7 1678750 mail optional sogo-common_2.2.5-2_all.deb ccacdda339bfefdc3131a7919af9a58f 4064826 debug extra sogo-dbg_2.2.5-2_amd64.deb c54803bfd59b814d88d31d0c16fe1631 1120466 mail optional sogo-openchange_2.2.5-2_amd64.deb 6790551806ed4f1e9d74918eb2c5a48e 1889 mail optional sogo_2.2.5-2.dsc c6ad6527bf5680996353397af980c7ff 15120 mail optional sogo_2.2.5-2.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTvCWeAAoJEDGCUpfTb5CBp7UIAKO0VMuJLDTufMXZ/GTYNlVy Glc0bswM6hBX6M/DCpR5hRUfrxN2ODYbyFiEFwpuZtsTdQEdk5i+/kK93AiV72d7 B7b9nIlY2+hWg//2WkWMSUirDIA84q+7j8e2/OZgfoBUovwcF7yVFFHhOXT46qTD s2Xm9dpfnEdW0rdLQzw3klpk4torAhynT3AUn4uIompqFSROE5YmbenBENuPXj9P PFqWBARbsjWk/CjHVE2qaOLW/9ITM3dxcagMjETeCMIOpVdeoKKJzlB8Y/1AL6QB ZOIHkHitLkO835aI/MPhr3HL9u5QCtWHEVlRSK30WTEiUxs2beuBAQNmsVP7Gmc= =cKbV -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/e1x4z4l-0007h0...@franck.debian.org
Accepted sogo 2.2.5-3 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 08 Jul 2014 21:12:12 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg sogo-openchange Architecture: source amd64 all Version: 2.2.5-3 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols sogo-openchange - Scalable groupware server - OpenChange backend Closes: 754212 Changes: sogo (2.2.5-3) unstable; urgency=medium . * [a0105ea6] Disable buggy TestVersit unit test. (Closes: #754212) Checksums-Sha1: f2896803d0ff1fccd25f73d166ad25ccf5ee63a8 1889 sogo_2.2.5-3.dsc 1a6121183bf26d2ee2e316785e804037353e2aa3 15316 sogo_2.2.5-3.debian.tar.xz 8f1cd607b5bfd760fbeb10a89decb39f52c01a06 1923558 sogo_2.2.5-3_amd64.deb c56e76ed6cf67975f92fdc32e2b62e49680e866f 1678790 sogo-common_2.2.5-3_all.deb aa4212a27f2042c009f286d3517681516d05f8f3 4065902 sogo-dbg_2.2.5-3_amd64.deb 6f1a65d4fcd5b3ae68cce481d62213304e395cfb 1120538 sogo-openchange_2.2.5-3_amd64.deb Checksums-Sha256: ff45097bba1b7f1f3e231aa12b13e52841d88a88772ca95206c26afe014abb83 1889 sogo_2.2.5-3.dsc af1eeb6682d0dc2c7528d9631770db3db4faabdae6369857d5712739892b96fd 15316 sogo_2.2.5-3.debian.tar.xz 426085bff3f2ab521dc1bf68f5bc93356b96918195b2cfa8f3f22a16c978db74 1923558 sogo_2.2.5-3_amd64.deb dd95930780c6eb3442c041aab8a9c0111a35250586e45eab3087982ab21241da 1678790 sogo-common_2.2.5-3_all.deb 26f352fb143a3b6108bdbd7f78ce0d780c03a567f4a97cfced75d2b5314d1ba9 4065902 sogo-dbg_2.2.5-3_amd64.deb fdaabfbbb69ecd2dbeb56ca1aa4e5952eb2e086758ae155ff7a971518648586e 1120538 sogo-openchange_2.2.5-3_amd64.deb Files: c96bb70c8fd536db25bdafeec3781978 1923558 mail optional sogo_2.2.5-3_amd64.deb 60c1ed106437c38cec3e4214c3a2ae2c 1678790 mail optional sogo-common_2.2.5-3_all.deb ed03ff322f98f09a6e9db6a44260f5c8 4065902 debug extra sogo-dbg_2.2.5-3_amd64.deb 6c094ae7c34f78667e8a2aa6d8dcb50e 1120538 mail optional sogo-openchange_2.2.5-3_amd64.deb 794c65732fc4454ff2fdadf8db0ccfc2 1889 mail optional sogo_2.2.5-3.dsc 6d1e0fbbbc258d4b103348dd0d02abf6 15316 mail optional sogo_2.2.5-3.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTvEchAAoJEDGCUpfTb5CBOMQH/jcGrZS2SXhaticTX1XeEjyp Mcu4IIXrK0nZiH6A8yGrl//3kL9AQxVPhAgExJbCf5Q/3iOukQKegZj6YLFp6oqe IcJT9SIL72qODpunAjmBJSRRMRLSUCL589YD82crAPduGocJRoX3dDtwHl6SHuHd rv3oubfT+sgj1gkXaLbOG1Ohsaxkb769Hix3HVeWDWPcUlj8jc8Q4uh74m+P5FO3 jM/PiMwd7f6L6mlVDmrH2jSShLDXYzX5R7XgwjQY2ev9hKMbMqV0U5L+0LG60yHd 1ThS4bT9LI/FO+vV8rrn65FNvckXQ2pElLte0xHDidNRqGzRdSE5XFHTpE95Nzs= =YDVd -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/e1x4boc-0002ut...@franck.debian.org
Re: Pinning vs. conflicting
At Thu, 03 Jul 2014 14:20:24 +0200, Juliusz Chroboczek wrote: You have not yet explained why apt pinning is not enough. Simply because apt is not the only way to install packages. Don't synaptic and/or whatever honor these pins too? I have no idea about synaptic, but there’s e.g. cupt (which works as apt replacement, but probably (didn’t check) handles its configs the same…) and dselect (which uses dpkg and thus is one level “below” apt, and cannot be reasonably expected to use apt’s configs). Isn't the proper solution to add blacklisting support to dpkg, then? No, the proper solution is pinning and that's already implemented. A quick search turns up a bug report about pinning in cupt, from which I conclude that cupt also implements it. Synaptic also implements it. And dselect is obsolete and doesn't even support things like multiarch (see #664893). It would also ask you to confirm installing extra packages if I remember correctly, but I haven't used dselect for a very long time. -- 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/87oax636tt.wl%jer...@dekkers.ch
Re: How to avoid stealth installation of systemd?
At Wed, 2 Jul 2014 00:13:31 +0100, Wookey wrote: +++ Lars Wirzenius [2014-07-01 18:34 +0100]: On Tue, Jul 01, 2014 at 04:23:01PM +0100, Wookey wrote: You get a choice of 'prevent-systemd' which stops it running as init but allows the -shim and libpam packages so that logind and the like will work. Or 'systemd-must-die' which conflicts with everything systemdish. Wookey, Please rename the systemd-must-die package to something neutral. Thank you. OK. I did rename the source package, but I liked the binary and thought anyone else who actually wanted this would enjoy it too, so it seemed appropriate despite not being entirely 'PC'. I think some people are failing to see the humour in this name (and Dawkins knows we could use some humour round this subject), but I guess if it's not going to be allowed then it's not going to be allowed. Yes, I also completely fail to see the humour, especially in the light of other remarks made on this list by the author of the systemd-must-die package[0]. I just can't stop making the connection between the statement that systemd *must* die and that suggestion... [0] https://lists.debian.org/debian-devel/2014/05/msg00585.html -- 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/871tu455ze.wl%jer...@dekkers.ch
Re: holes in secure apt
At Thu, 12 Jun 2014 18:35:39 +0200, Christoph Anton Mitterer wrote: On Thu, 2014-06-12 at 10:30 +0200, Thorsten Glaser wrote: The buildd-related software (and most people when doing manual builds with cowbuilder) uses “apt-get source foo” to download the file, fully assuming that apt-get ensures validation, so no “dscverify” is run on the sources downloaded by apt. (If someone uses dget, either dget is new enough to call dscverify, or they had better be doing that by hand.) Which is why we're possibly screwed already... even if the builds don't run as root... it seems like a rather easy way to get into the build hosts... and/or have forged source packages build and distributed. Just that NSA hasn't twittered yet that they didn't doesn't mean this is the case... So... @security-team: is there anything that is going to be done with respect to Debian's infrastructure? Or do we simply assume that noone tried that attack vector before? The security team is responsible for releasing security updates, not for securing Debian's infrastructure. See https://wiki.debian.org/Teams/Security for more information. And if you're really concerned with state actors backdooring Debian packages, then please take a look at reproducible builds: https://wiki.debian.org/ReproducibleBuilds. Securing all buildds and the personal machines of all developers against such sophisticated attackers is very difficult. Although we should of course do our best to keep everything secure, I think the best way to make sure there are no backdoors inserted when binary packages are built is to make it easy to verify they are built from the correct source package. The wiki page also has a nice Useful things you (yes, you!) can do list. -- 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/87d2ed6ro9.wl%jer...@dekkers.ch
Re: use of RDRAND in $random_library
At Thu, 12 Jun 2014 08:36:16 +0200, Matthias Urlichs wrote: That being said, sometimes you just need the binary equivalent of an uncompressible Lorem Ipsum text (dd if=/dev/urandom), but IMHO the kernel could (and should) provide a device for that. If you just want to overwrite something with random data, you can use shred instead of doing a dd from /dev/urandom. Shred uses an internal PRNG that should be fast enough: http://www.gnu.org/software/coreutils/manual/coreutils.html#Random-sources -- 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/87ha3q6zlx.wl%jer...@dekkers.ch
Accepted sope 2.2.5-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 07 Jun 2014 21:34:11 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.2.5-1 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (2.2.5-1) unstable; urgency=medium . * [25593ad7] New upstream release. Checksums-Sha1: fdee722e40312f8da5dadfbe0393d25805c4c457 1712 sope_2.2.5-1.dsc 75c36c389bd2c470f164cd2b19752587df9090be 2260654 sope_2.2.5.orig.tar.gz ef57651b496e818bb5ba55712b6604fa4913fe54 4344 sope_2.2.5-1.debian.tar.xz 887176f8b8c945baa020d1f09e8a2866f04f551c 1883246 libsope1_2.2.5-1_amd64.deb 455932ec9093cf9f203abd54f5e0331fa1ca3ff9 227466 libsope-dev_2.2.5-1_amd64.deb ee06e3a77fe1abbe1e5817f19fb3243ea67c4ce1 4270318 libsope1-dbg_2.2.5-1_amd64.deb Checksums-Sha256: 5a07298ef560081c460cb27710495bfb7f12727738a7a7b10b038226dacc6f94 1712 sope_2.2.5-1.dsc cff207b27589bc4eddd4628762a69a5e37aa5cc97ae02c42ee770143e6664252 2260654 sope_2.2.5.orig.tar.gz 401b3884b78657aebc7d174adad33b0c0b7999f972a8976bfae3b70ef0f623a3 4344 sope_2.2.5-1.debian.tar.xz 6311278fe9f658567e498447b28a54d72ab085e13f5174d1017b4db3a294bf9a 1883246 libsope1_2.2.5-1_amd64.deb 7c7504fc5c29df0097b41e64553a8ef0c471b0efa53e6846b8c8c86bcee4a577 227466 libsope-dev_2.2.5-1_amd64.deb 3c313d77293acafc2c9acf21210515ff2931e9d7b781d78fe2bece0701009fdb 4270318 libsope1-dbg_2.2.5-1_amd64.deb Files: 770bc08c2618c22dadbc05c268dafb50 1883246 libs optional libsope1_2.2.5-1_amd64.deb 5f850c42342c5eba023b81bb09d7e07e 227466 libdevel extra libsope-dev_2.2.5-1_amd64.deb d5108c07b9c4a8899e81bede81ad36c9 4270318 debug extra libsope1-dbg_2.2.5-1_amd64.deb cb07833d4295550d1760181901b83f61 1712 libs optional sope_2.2.5-1.dsc d9570ef7cd8e862e1415e1ee07d1f870 2260654 libs optional sope_2.2.5.orig.tar.gz a3adf55e404344a97e273fc3f86573cf 4344 libs optional sope_2.2.5-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTk2o9AAoJEDGCUpfTb5CB2cUH/jekTY5a4IHKrcLdtlY3Ob28 V5IXQUZX3lIeqMZ/ndTC+ztZHRGCJfY2d0lltBNScNLZustNVdFhOqjEumw/O4XK nneFO++QfU8cbjkVj29r/9ZskARdSgL+Vfwb/cakPfCB+4SSPcJRO5fMFoWlsIhO ARR4esYBFM/Ee50gvjmYb6cFAkt2UlncRBR3BwYupD4QQL1+64WO/f7ziUHaV6HQ Edj6AqaXxULOSnYyljlm8fEaGgI+cvtDNywscKL/IQ5JUg4tes8AhqExdlo5sVbq RbcIpcRvJjeY+ddhwmFss7wMzmD/RLuvXhJuXvpuaDvjEVFN4dNFyWqI4fCMx/Q= =V+aW -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/e1wtmci-0003xr...@franck.debian.org
Accepted sogo 2.2.5-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 08 Jun 2014 01:47:37 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg sogo-openchange Architecture: source amd64 all Version: 2.2.5-1 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols sogo-openchange - Scalable groupware server - OpenChange backend Changes: sogo (2.2.5-1) unstable; urgency=medium . * [90b8c6d3] New upstream release * [6dc419c5] Update patches * [04a02370] Update version of libsope-dev build-depend * [010e6b08] Change /etc/sogo/sogo.conf group to sogo and mode to 0640 Checksums-Sha1: 3fc833763aab75956d01f3d1db1c10b857b4 1887 sogo_2.2.5-1.dsc 3b96200d61ec7b16fe1b34e9bf4f898a7281b322 5475064 sogo_2.2.5.orig.tar.gz aa8e057ee2eed7d52296457732fbcc6a7e32b37b 15096 sogo_2.2.5-1.debian.tar.xz f8c03c6af649f717c9db73803f4b5233e4557f23 1924744 sogo_2.2.5-1_amd64.deb 11a4ff7ff617c0949ed3f0b83b31f8d8673cfa91 1678696 sogo-common_2.2.5-1_all.deb 65b231d9e79f053d4ba4cbe77e359a7f878370f3 4073242 sogo-dbg_2.2.5-1_amd64.deb 40b66965d27575bf284b753f0872443aec373716 1121864 sogo-openchange_2.2.5-1_amd64.deb Checksums-Sha256: 1b1e6bd3fa11dc95c1a5c44b4db684c5ea003110c0bb5880e28eabdc2c02335e 1887 sogo_2.2.5-1.dsc 387ca092a204ebcdfc7d21c3560f75ed17d4d199c07ecb3c573a8829a131c888 5475064 sogo_2.2.5.orig.tar.gz 38f7db5182603adfe2ddb0a00bf65a383ad6bc67933f02c34f3189859f98aa9b 15096 sogo_2.2.5-1.debian.tar.xz 2ccf416baff49b79c16ca9dbd581fd7703c7eba4804925500fd702a1d9223e24 1924744 sogo_2.2.5-1_amd64.deb b7028d95de7c7bd0290547e452855e52569c75c92c258d3b5c5d6274f316af99 1678696 sogo-common_2.2.5-1_all.deb 74b48f7bd899ba458a2b9fa0f2517762079f95e947f5da5cb1749a4064627227 4073242 sogo-dbg_2.2.5-1_amd64.deb 7987645b84de66f536ad9ab2dea1a5823844f15fbe20eebb12ce502af3b701e5 1121864 sogo-openchange_2.2.5-1_amd64.deb Files: d278162762028488119d0404ab0bd72a 1924744 mail optional sogo_2.2.5-1_amd64.deb f7596d7096170f250e645beed168d731 1678696 mail optional sogo-common_2.2.5-1_all.deb 8508b099fcbea559accd4c60db3c4bbd 4073242 debug extra sogo-dbg_2.2.5-1_amd64.deb 1abdedb3c6de149890411957014c0495 1121864 mail optional sogo-openchange_2.2.5-1_amd64.deb 9cd72b2c180ef1e596a40056dd1d6c9a 1887 mail optional sogo_2.2.5-1.dsc 3581d38daae5101618acc661d4e06abd 5475064 mail optional sogo_2.2.5.orig.tar.gz aee9f87b478c423763ead1edbf08b308 15096 mail optional sogo_2.2.5-1.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCAAGBQJTk6VuAAoJEDGCUpfTb5CBUCwH/3ixFkEPd4EMOXCwGmzj83W4 uCr6cBV6slxiOb9VlFGvNaD5fC+/EUCZ/NiZYRtzbP0b3aviDaJqtXayzf1gZ1mo GlajIt/UE4E3/Ie50Gip5nqfjUOt8wIzZiM18dGhLFJ3D/J8yHtB41UG5+c67igC xycQy4ZVP6TOZ/iEKjVwEvqRXXead6sVIBV2sUO0UGIji/TFz+pOpOZt+8+D7LNF X9cVLXi6LHjx6Fvlqp13jSk8U6PdvPx/wqVxgW9RpIcxB/cA3DfT3I1dccIcsOu3 mdZ+axT0an1Lx/0+nbJ4YXealpMwjZbz6yZMMlNeUdDewtW3STHv++FCrLW49vc= =QaEg -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/e1wtqcr-00023d...@franck.debian.org
Re: Avoiding system d
Hi Carlos and Marc, At Mon, 12 May 2014 04:21:10 +0200, Carlos Alberto Lopez Perez wrote: On 11/05/14 09:18, Marc Haber wrote: Something along the lines of systemd is technically needed and a good idea, but the people behind it do not come along nice. Completely agree. While I also agree with that having read some responses of systemd developers developers that could have been nicer, I think it is ironic to call out the systemd developers for not being nice and then post statements like this: The systemd developers are responding to upstart and launchd and android init as things they must _defeat_, an establish a new standard by crushing all the competing implementations. This means developers who want gradual staged transitions, and thus ask questions like what if I don't want to switch yet, or how do I get the old behavior out of the new thing, are enemies of systemd. Those questions are anathema to the systemd plan for world domination, if you're not using their stuff already you're the enemy, a relic of history to be buried. We can't opt out and see how it goes, we must fight to stay where we are. The systemd developers are basically taking the Microsoft approach to development: they don't want you to have the option of NOT using their stuff. http://www.landley.net/notes.html#23-04-2014 Or this: At Sun, 11 May 2014 15:55:48 +0200, Marc Haber wrote: On Sun, 11 May 2014 14:50:55 +0200, Florian Lohoff f...@zz.de wrote: There is no way to avoid the userspace.exe blob Debian is soon made of. To be fair, the major Linuxes will soon be made of that. Red Hat wants it that way. Maybe you should think about how your fellow Debian developers who have no association with Red Hat but just think systemd is technically better and who are working hard to get systemd working right in Debian feel when reading such statements. And while we as Debian can't do much about upstream maintainers not being nice, we can at least try to set a good example by being nice ourself... Kind regards, Jeroen Dekkers -- 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/87oaz39qaj.wl%jer...@dekkers.ch
Re: systemd-fsck?
At Mon, 12 May 2014 12:16:48 +0200, Andrew Shadura wrote: On 12 May 2014 11:54, Josselin Mouette j...@debian.org wrote: Systemd is the default init system for jessie, and it should be listed as the first alternative. The fact that an alternative codepath exists for users with specific needs is nice for them, but it is not what we should focus our efforts on. As far as GDM is concerned, any bug reported with systemd-shim installed will be ignored. The bug script should probably be updated to that effect, BTW. This sort of behaviour is precisely why so many people not only dislike systemd, but also it's maintainers. Why are you blaming the systemd maintainers for decisions made by the GNOME maintainers about GNOME? Kind regards, Jeroen Dekkers -- 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/87ppjj9qsn.wl%jer...@dekkers.ch
Re: copyrighted embedded ICC profiles in images
At Sun, 11 May 2014 19:04:07 -0400, David Prévot wrote: Q. Are profiles copyrighted? A. ICC has no formal position on the use of profiles. It is really up to the software vendor. However, since the software vendor effectively holds copyright on the profile (which is specified in a tag) the licence to use their software permits them to prohibit public posting of profiles. One of their motivations could be that if such profiles could be freely exchanged it would limit the number of sales of their software. Also, from a technical perspective it is dangerous to publish such profiles for many devices. A profile for a printer, for example, is only valid for the substrate and inks for which it was made and it is for this reason that few device manufacturers publish profiles for their devices. Any ICC profile is produced using proprietary software. All ICC define is the nature of the tags, which tags are mandatory and which are optional, and how the data should be defined in them. The contents of the tables are vendor specific and each uses different algorithms. It is this that gives the vendor something which they can copyright. That isn't really a clear and useful answer, but what I read is that: - Algorithms to generate ICC profiles can be copyrighted. (More precise would be to a specific implementation of such algorithm can be copyrighted) - Proprietary software vendors could prohibit public posting of included profiles in their software license. But if profiles are copyrightable they would not have to explicitely prohibit such action. According to wikipedia (http://en.wikipedia.org/wiki/ICC_profile) an ICC profile is set of data that characterizes a color input or output device, or a color space. It looks like an ICC profile contains just facts and mere facts aren't copyrightable. Kind regards, Jeroen Dekkers -- 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/87lhu6ao0k.wl%jer...@dekkers.ch
Accepted sogo 2.2.3-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 13 Apr 2014 00:09:03 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg sogo-openchange Architecture: source amd64 all Version: 2.2.3-1 Distribution: experimental Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols sogo-openchange - Scalable groupware server - OpenChange backend Changes: sogo (2.2.3-1) experimental; urgency=medium . * [0837e058] New upstream release * [9dff26d8] Update patches to new upstream version * [40f1ddf6] Update version of libsope-dev build-depends to 2.2.3 * [770e90c9] Bump Standards version to 3.9.5 (no changes needed) * [87c0717d] Change VCS-* fields to their canonical URI * [2f95d6d8] Call dh_install with --list-missing --fail-missing * [53a018b3] Include tmpfiles.d/sogo.conf in sogo.install * [b70eaa27] Add patch to fix warnings from -Werror in OpenChange backend * [ea9345a1] Build OpenChange backend, add sogo-openchange package * [e71ff33c] Add patch to link correctly against libraries used * [a974b2c4] Add upstream patch to fix unit test * [4979ec49] Update debian/copyright Checksums-Sha1: 0ae57d20ced6391b843c5a338c50f7dfe5bc8979 2201 sogo_2.2.3-1.dsc 30abe279bcc40da200b93add854a7cbacd1feaa2 5431558 sogo_2.2.3.orig.tar.gz 1bf91a166d78ef6908f37215be57502bdb985cab 15464 sogo_2.2.3-1.debian.tar.xz fec349b8e6d27b113fd3ce285539cf9f742f78e0 1888184 sogo_2.2.3-1_amd64.deb c7e498d9ce1b4520daca94e66643df272238d826 1660142 sogo-common_2.2.3-1_all.deb 96827c0b60231c7027e1d8d933a7b51c63860341 4047148 sogo-dbg_2.2.3-1_amd64.deb 6652511934095d2dabd73442996779a6da160f49 1124970 sogo-openchange_2.2.3-1_amd64.deb Checksums-Sha256: 82e5f90463818b9aa79019b8a0a6a05c6f15b102a2a895ce7d4e055f89e3b96f 2201 sogo_2.2.3-1.dsc 1d01826bd904aae3626829f1cdc503081bed71252cb0679f86ef459536b0f992 5431558 sogo_2.2.3.orig.tar.gz fcf34529b0c422b3daffbc5c6808402a08454d092963b789c4a4e5f902cb55d5 15464 sogo_2.2.3-1.debian.tar.xz fd78a9e95fa963648e09f7462c9b3f3a58f4af6fc890e11eae134ac16e5b9e54 1888184 sogo_2.2.3-1_amd64.deb ca398b0cf2490ed268a17de610a57ea3095080ad96d4a0833cbb6c5bc90937a4 1660142 sogo-common_2.2.3-1_all.deb 4f45564588b2310363176f0eac7d6979e3ef3338e8c633e1a1607a70027c4774 4047148 sogo-dbg_2.2.3-1_amd64.deb 074d8f77a7c8f13763852bd2ee1549698278b5448320b5744ad5daf0672d21ff 1124970 sogo-openchange_2.2.3-1_amd64.deb Files: 6d2e82ce309af3f4772bfe0bf6ecaf2e 2201 mail optional sogo_2.2.3-1.dsc 880c90bf1f85441d97f6881224379492 5431558 mail optional sogo_2.2.3.orig.tar.gz a1da1da4d40fb37956125a55ee7cac84 15464 mail optional sogo_2.2.3-1.debian.tar.xz 0807a287de804ecdb7e7a2140dcf511e 1888184 mail optional sogo_2.2.3-1_amd64.deb 13d266953b1175f0860050f68b9df0fb 1660142 mail optional sogo-common_2.2.3-1_all.deb 450fcc7a40755e6f10ff2186d0648fa5 4047148 debug extra sogo-dbg_2.2.3-1_amd64.deb 30042fc764077235df8c422e2b714ca2 1124970 mail optional sogo-openchange_2.2.3-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJTTHJfAAoJEACAbyvXKaRX6kQP/1WYUwcSXbAWICxR2tcxi3Pf h/b+CLQ0pW0dUfjrTKoQBarv/21T5RNTCEJxkmBUcBSGBtZLKTuLWsBhayeL1/8v soTuM4bNbTSrwxAvcrB+qeMhhHHqqUu7FAk+nGQn5poM01n5baXKF2oSxOgVTOB2 FEvh9/cRwwuIQeIfOIgJxeT3v1alw2hTJgMldzTKm20NfmYm25eIOXtPKqpUB/gO SdkEi5yqz+UGv2PzdfUrafgj79yyxBJ9xo4LOLWbM/MgVOI2IuzO8Tej7OKfhFZx ySTbbz/CCZRBB+ZbBTh3aigNA2l+BcWNzMKOLrWi3it0YvAvJOv5PhvUI50woWkZ Y3wzLDWlnAM97sTAE3DNEVGF9uARAjj0GssD3ICma655ye/791rUJydQZDkVQgne +ZUAExsJwbsuFSEW5i5zeS42RZzxIkAqRwAXI4u3AhZG5pwfZnMceIdQ5nR6XhwA 1keKmw+sE16+QoxkxRm609tBKePCg/EA5Oxu4aJxjfHBC2pOl9hZX5B7gWBINXo7 rU6/ywYdR3zjqF5esmtalCZS/L2ul2PDlrBJNxi9yD3q7FIwlEdsa3b8HHTXVd93 5/rPlmUkrrLBGfnmWNnpVAbrvhGF9wTkMhGbz4yHZt6xnjn5dESeLg89mV/BgGey RV/XwD7OA0RM3T5n42G3 =ha1D -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/e1wgdih-0003ba...@franck.debian.org
Re: Bug#745872: ITP: profanity -- a console based XMPP client
At Sun, 27 Apr 2014 08:22:59 +0200, Dariusz Dwornikowski wrote: Dariusz Dwornikowski dariusz.dwornikow...@cs.put.poznan.pl writes: PKG_CHECK_MODULES([openssl], [openssl], [], [AC_MSG_ERROR([openssl is required for profanity])]) The resulting binary cannot be distributed. Could You elaborate on that ? Why would openssl ban the binary to be distributable ? The GPL and the OpenSSL license are incompatible. Thank You Russ, Would it be ok if upstream adds the clause as explained in [1] ? The upstream is very responsive and open to all suggestions, so it should not be a problem. [1] https://lists.debian.org/debian-legal/2004/05/msg00595.html Please use a wording that also grants permission to link to forks of OpenSSL such as LibreSSL, in case LibreSSL or another fork is preferred over OpenSSL in the future. You can take wget as an example: http://metadata.ftp-master.debian.org/changelogs/main/w/wget/wget_1.15-1_copyright Jeroen Dekkers -- 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/87lhupb47v.wl%jer...@dekkers.ch
Re: lintian source-is-missing for jquery -- was Re: Bug#744699: Frets On Fire bug report 744699
At Fri, 25 Apr 2014 14:58:35 +0200, Daniel Pocock wrote: There is no doubt in my mind that if the rules are not strict then sooner or later somebody will sneak something bad into some minified Javascript - maybe it will happen upstream and the DD won't even be aware of it. Yes, and that's why javascript shipped in binary packages should be build from source and we should not copy minified javascript files from upstream. I think there isn't much disagreement about that part. But if the minified javascript files in the upstream tarball aren't used when building the binary packages because the javascript libraries are already packaged in Debian, then it isn't possible that something bad sneaks in our packages. So why repack the upstream tarball? I don't really see any value in repacking every upstream tarball that has a minified copy of jQuery. Kind regards, Jeroen Dekkers -- 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/87mwf9bh4i.wl%jer...@dekkers.ch
Accepted sope 2.2.3-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 06 Apr 2014 19:31:49 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.2.3-1 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (2.2.3-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: 5e4bd15d53efb1b5dca91cf01b521817eef49003 1706 sope_2.2.3-1.dsc 54adbf62a4b839b07d6eba5ab6479798b07977fc 2258810 sope_2.2.3.orig.tar.gz 0d686b8a7484f630aa794102c19ce4e121865c1d 4288 sope_2.2.3-1.debian.tar.xz 7e4b64329a024cd2b3bdfc34dc245f840b0284cd 1879182 libsope1_2.2.3-1_amd64.deb 76dfe1575a6e85a17f47a3c6ef879b6562e176b4 226752 libsope-dev_2.2.3-1_amd64.deb bb09f5748aaf76aef50335128fb2f08cfd2139b2 4264144 libsope1-dbg_2.2.3-1_amd64.deb Checksums-Sha256: 6e5947b87b958862f3ebf9dbd26e99d14d2506989c1f0fcf741dc8886aeae891 1706 sope_2.2.3-1.dsc 8f6c9592d8d8093adb29fa7bb30a459f52ae0cc6701a663ac7b2d523b8aeb7ce 2258810 sope_2.2.3.orig.tar.gz 78eff9685c323471e11eb0f0f652b3947c72c98501d0facdae340b4aaed65b48 4288 sope_2.2.3-1.debian.tar.xz 77453cdd33c2e703e0545b92b67963053a491da470817c8aff69cdb5a7dca0c7 1879182 libsope1_2.2.3-1_amd64.deb fd424aa54671e8f2d3e4eedc3fbea509d948e06beeb9b55f5584c15041668a84 226752 libsope-dev_2.2.3-1_amd64.deb 5a933432a63e20d6c1c5f6cff1965d8cb3fa74355618105f22cad3063b627686 4264144 libsope1-dbg_2.2.3-1_amd64.deb Files: 44aa1fa6d3e5027b80663bcae08265bf 1706 libs optional sope_2.2.3-1.dsc 1e28e60b9e614d87d63f2e1472c0f05a 2258810 libs optional sope_2.2.3.orig.tar.gz 58723ab822090446e940424ee02ede7f 4288 libs optional sope_2.2.3-1.debian.tar.xz 51b3a7a838a7bea6bed4ef73f9c897da 1879182 libs optional libsope1_2.2.3-1_amd64.deb 99e5327b6ee7854399669a7ec1b98735 226752 libdevel extra libsope-dev_2.2.3-1_amd64.deb 77f6c1e2e965f04eae30ebdd1e495db5 4264144 debug extra libsope1-dbg_2.2.3-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQEcBAEBCAAGBQJTQZFuAAoJEDGCUpfTb5CBTl8H/1m3/sCpyIIbQHeQFScF9rUX KV+vnQDOc1ZmOwm0BQg1BuXjyMmWNbJrbVyJ0RRGouCRInQ4XSgxg4u0WDja32hY WD79UYVcxe9Ij7F/XgPvvHqr5yqlk/u2NsGoH/71+8x0YAkOIMdFL80Pw9yllqOf EtUIvOBq5IyJk9bbwkZ81RvrAaA9QZ3f3oY2BZSg2ZKqGQapY5sQK6Cn+xkChM9u 0b7+D/fbMOZ6WHo5lDpuMBhGfHxxbfihgosluoGhpuXZZLjXE/zMi1RJy471O8Ss HHQbLpmdHR3mMtPmQFXr3HHCz+pY1aoIcq3UePW7vVD/MJ8pyRC9TAab4GiaYGA= =o5fy -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/e1wwrcm-0005eo...@franck.debian.org
Accepted sope 2.2.2-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 28 Mar 2014 22:43:45 +0100 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.2.2-1 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (2.2.2-1) unstable; urgency=medium . * New upstream release. * Bump Standards-Version to 3.9.5, no changes needed. * Update VCS-* fields to use the canonical URI. Checksums-Sha1: 5e88d57c0c2499ee499657acfdac453d210191fb 1706 sope_2.2.2-1.dsc 6b3528f703d71c4ef99b142e2732aa134b77eef6 2258376 sope_2.2.2.orig.tar.gz 56d5b14fbf5abac3840d82ce6aca5bd6cc4473b2 4276 sope_2.2.2-1.debian.tar.xz 6b0ba100a3da6a466df38c16034f1d3b4aaad820 1879008 libsope1_2.2.2-1_amd64.deb 16c6a0f16b131a83dd89c59e345bb54b17175637 226142 libsope-dev_2.2.2-1_amd64.deb 4ea486fd79b1d7e109bb186011550feb6a781d8f 4263650 libsope1-dbg_2.2.2-1_amd64.deb Checksums-Sha256: 7304b6f6b8ab1f914fee12208ea2c3405f553fa1c5e4bfc5de3632cfb251a852 1706 sope_2.2.2-1.dsc 84e53cdb46f6542ce4164b56d4ab693b546213411316f03a8f70b25e550a2466 2258376 sope_2.2.2.orig.tar.gz 16a5f2ca5782b7f21caf18c25014dac34f15c5bea24696200774291210fa2917 4276 sope_2.2.2-1.debian.tar.xz 42eb25c9d0649711fcd8ba7e01f0e5da1521064b351a8de52b084da6a6eeeb9c 1879008 libsope1_2.2.2-1_amd64.deb effd99880177165e55ca5533e1f5efb63a8e4f130aa67d12751f41a1ef08da5c 226142 libsope-dev_2.2.2-1_amd64.deb 497cbaec713d020e3c24dca6224c3dc522f32f72b31f0b67ff99882477e57856 4263650 libsope1-dbg_2.2.2-1_amd64.deb Files: 495e7f91a858c23c4b346df571dfdac7 1706 libs optional sope_2.2.2-1.dsc 1edc66153bac004f6d04d8bb22c8f800 2258376 libs optional sope_2.2.2.orig.tar.gz 538a0ce670aff0d27dcc632ec5ad952e 4276 libs optional sope_2.2.2-1.debian.tar.xz 0cf6b1633e3c16dadcadd39874d88e26 1879008 libs optional libsope1_2.2.2-1_amd64.deb a818589c6a85db9c7fb60e743bdd74af 226142 libdevel extra libsope-dev_2.2.2-1_amd64.deb c970d3e9bfe1b439c9ddb033a8a567ad 4263650 debug extra libsope1-dbg_2.2.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQEcBAEBCAAGBQJTNfA9AAoJEDGCUpfTb5CBftQH/1gMTnNYeLLnA2LN+b3FbMva 87U4XmkGnhoc517IXL4aOvyfugRh5M1JWRXVO14+HZCpzhA19rkdjkeoZW398agc ebYwS+dfru4uKCrV2IKehxntoT+hHOeM143c1Fn5lg4QoLdZwtVQYJS0bU2czN7d x+YnkZ9mm+jr6PWBy82ne4wVYnmfSeb3WUCZhhL8urX3lXnq92/C+9XY+t94DnGS qR9/WSwKFRn4zNA9yN/TCkXRS5jH4h6mjlDWDdFwxCNgoPgL2PFSfbMUwPYfPGN2 cyonM+qQoyjDxNDPe5qpvAFo5Dp6eEIsh6ARJVEUZHde5yaR+9y9IEIGOXOWtQE= =ORep -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/e1wtesb-00060d...@franck.debian.org
Accepted sope 2.1.1-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 28 Dec 2013 17:40:18 +0100 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.1.1-1 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (2.1.1-1) unstable; urgency=medium . * New upstream release. Checksums-Sha1: c4499af4134640ee6ebb999618241500b38e8b88 1695 sope_2.1.1-1.dsc c64ff41455cf48f3ab98c25c5c01e78fa227e0b0 2256297 sope_2.1.1.orig.tar.gz 57a24d76b12b668a045ff8f192631ec090b6f886 4416 sope_2.1.1-1.debian.tar.gz ba5b92fa7809e0d9d3db98875a7e2120c36c4d3c 1878114 libsope1_2.1.1-1_amd64.deb a6d15464672bb18ec81da75343f97ca21ed6a47e 224080 libsope-dev_2.1.1-1_amd64.deb c383c004b899bb34768c9c9fc446e301c794968f 4261772 libsope1-dbg_2.1.1-1_amd64.deb Checksums-Sha256: 62158bd81ffd82dd48ae64189b2cd9e426bf52f72be1db47d89027afe491663e 1695 sope_2.1.1-1.dsc f9b9e5a056b7d318b5ba34826e8c199421718708ae31e94714a0a6f36f74355e 2256297 sope_2.1.1.orig.tar.gz be3ce5d6f41e1b0baf686317751219d707681db9d3a875eb0b366748f6121157 4416 sope_2.1.1-1.debian.tar.gz 5541f2e77f9a1f9897bd474b1b89fd6da1c99806fd9c14f1d6db3b44c6a86924 1878114 libsope1_2.1.1-1_amd64.deb 63cc1d6983195edfc9e81a650995580b4b37fc3ba4169bff57977e882cc9e22a 224080 libsope-dev_2.1.1-1_amd64.deb 954c3def4a36e874f443b35bb27af740f6249a1e2141ad99dd8c52dbe6d5248a 4261772 libsope1-dbg_2.1.1-1_amd64.deb Files: 9175eef480f6e640d9d6fa0f8b776ebd 1695 libs optional sope_2.1.1-1.dsc cd9363ed36aa7958ecd94451216e0671 2256297 libs optional sope_2.1.1.orig.tar.gz 731a815b16b93700cf393274a3425449 4416 libs optional sope_2.1.1-1.debian.tar.gz 0844fb22bc180100d28a05e25ca798de 1878114 libs optional libsope1_2.1.1-1_amd64.deb af7e0e382645e5fc245d556ba8edd7c7 224080 libdevel extra libsope-dev_2.1.1-1_amd64.deb ffd6057f120c7d2dd00c54b360108d3b 4261772 debug extra libsope1-dbg_2.1.1-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQEcBAEBCAAGBQJSvzjZAAoJEDGCUpfTb5CBXlIIAKKld91c8BC843Wuc6puUPkC tN1VVFWnpWNpsFdojukSatHSw7RSxaSDdtiFznSmiSx+y3dkzJIQc07GW3IuFf86 pvd+n9GJFUvLedyav1i4tL2b4iPMTS7qvweUh4ZSp0dLSNRMctiWutUaUl6N2xgs V4sF5Ft0CeCo979R7gnwRzPtBI2Kyxs/WKU0baQkLNB1MU4kHQ1dCvjWqtKBHBnk Irsar+OJz6mQqYFzZWvWL60sTiUus1Mp7cuNxF4NBsI4yzZk+99MM7rtGNida1c3 F14OkpHYSeHUKWgmMVxSXU86t9nMkV95Wi0fr6nDNcZPOelEi+XyOrH7uG0bg3g= =a+ad -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/e1vx1nc-0003sg...@franck.debian.org
Accepted sogo 2.1.1b-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 28 Dec 2013 23:15:41 +0100 Source: sogo Binary: sogo sogo-common sogo-dbg Architecture: source amd64 all Version: 2.1.1b-1 Distribution: unstable Urgency: medium Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols Closes: 732189 Changes: sogo (2.1.1b-1) unstable; urgency=medium . * New upstream release. (Closes: #732189) Checksums-Sha1: f818176aeaf9540a4c902f3e819f9d10e1907fdc 1700 sogo_2.1.1b-1.dsc b380010013d796252e1b0bdcf2bd791bcaadc519 5846822 sogo_2.1.1b.orig.tar.gz b915b7d0c548906ee6b0938925a1d4e2104e1a6c 11986 sogo_2.1.1b-1.debian.tar.gz 2d0f4e09cc180fc71b0cf188f13383b041c14c6c 1853744 sogo_2.1.1b-1_amd64.deb c286050e05f901c92ed069584c556a7154812330 1614746 sogo-common_2.1.1b-1_all.deb ba06e9ac91bc9620c4c91a11f180f59cd372e8cf 3102106 sogo-dbg_2.1.1b-1_amd64.deb Checksums-Sha256: a44490d3a12d6bf45312bc21a36911f312a08b59019098307f2243f964a835e2 1700 sogo_2.1.1b-1.dsc ec90ace24a20bbc2ba049fdfb224fa9ed49e461559b87035609305a9451bb3de 5846822 sogo_2.1.1b.orig.tar.gz 60fb706a17942f905087ae74294fa3312164da2da8a90bd7319cb6dfc1bd5874 11986 sogo_2.1.1b-1.debian.tar.gz 5713d598cb64dd9dba58665ddc1e68803fa957d355142eb7df02b887380cccda 1853744 sogo_2.1.1b-1_amd64.deb 5f139eb8c9a74c778b089b871e33bdc021117c9c1d1718f033d34ca6cbd61b9c 1614746 sogo-common_2.1.1b-1_all.deb 8793faa19c9379ada1a8c905ce25a08cc14107a1fe8ae67eb742a5557445848f 3102106 sogo-dbg_2.1.1b-1_amd64.deb Files: db808b2659225e7c9e9552fbf2ff8af1 1700 mail optional sogo_2.1.1b-1.dsc 88cd5e4236359d34d778095afe46bd97 5846822 mail optional sogo_2.1.1b.orig.tar.gz 96bc64c1d5984c0763e8a5769998887e 11986 mail optional sogo_2.1.1b-1.debian.tar.gz ef4afcaae3075f3bb97421b51b7db16e 1853744 mail optional sogo_2.1.1b-1_amd64.deb 799766b736f7fe225491482a6ce51147 1614746 mail optional sogo-common_2.1.1b-1_all.deb cdb6ede13736f4dbc19ace2b83476ced 3102106 debug extra sogo-dbg_2.1.1b-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQEcBAEBCAAGBQJSv1FHAAoJEDGCUpfTb5CBDycH/3h+7GAVAuTFAoyh3YRxBoMl CG18q6jQ4+CvB1EOGWfUXO6sUajCq0PCMxk2uhDo7uyKrcs3ekcJXiLrGFoVTZXm X5JjogPzzNBpRfOIfTWPA+GnJ1ggeB3PZsdFuxnsOmSzwrSFwpKkS4wi46XPMZiT 3M2qKPXLXahmNeeelwdn4PLfgQzcW9SnRqUDW1qN/xty8TAV7YsoQs1z4kwMca9M sL0iYBP1JXhtdcJFocW9i+logONCOTAx2B6JW4Z87vvvDHBelr0M+a9hE1OOQo7F CHM2fiKQd5MvKO95rDbGiWzoQ2YYrusolXBalT8Kzs6/AU1gz43Gb6h1eP3xtXA= =a1jh -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/e1vx2hm-0004cm...@franck.debian.org
Accepted sogo 2.0.7-2 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 26 Aug 2013 20:07:08 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg Architecture: source amd64 all Version: 2.0.7-2 Distribution: unstable Urgency: high Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols Closes: 720974 Changes: sogo (2.0.7-2) unstable; urgency=high . * Do not call make distclean if config.make does not exist, fixes FTBFS with latest debhelper. (Closes: #720974) Checksums-Sha1: d357588a774528638f0ee3d8e0069177b5055601 1693 sogo_2.0.7-2.dsc 29243c04340e09d72f088393d2b670eb4f7df0eb 12143 sogo_2.0.7-2.debian.tar.gz c56180e1cc9000a99b16fcc16c6656e7e5db1d22 1896202 sogo_2.0.7-2_amd64.deb 8621f2f69bb0efffa82686bb0809c05bdfcf52ba 1595404 sogo-common_2.0.7-2_all.deb 68de6f36c456d51733d6cc5a4b67d6c87a17ac0f 3294224 sogo-dbg_2.0.7-2_amd64.deb Checksums-Sha256: f1814650964218bcd4bada3ceecb3e52a6d531d0d84412350cabea593b986b33 1693 sogo_2.0.7-2.dsc 262f64f846c3b899d8fb081d1e99f1bf8df8233b02110f46f828c743f9e79813 12143 sogo_2.0.7-2.debian.tar.gz 46625d1c70c311621716a4fd910896cf3580b780f8411e46a9da51a353008529 1896202 sogo_2.0.7-2_amd64.deb 004bdc0f47324de79112040c6d42653a4d2b625d99be2aaae6b7746ae78ebeec 1595404 sogo-common_2.0.7-2_all.deb 314855148d1d3cd715062793d6c31506a85a7f491ecfbb1dfe5a41ca90c10e3a 3294224 sogo-dbg_2.0.7-2_amd64.deb Files: 9742c0df7605b0a551bc0cfa8fa5a838 1693 mail optional sogo_2.0.7-2.dsc 7249d63de0b2298f0b5909b9ecaeecf6 12143 mail optional sogo_2.0.7-2.debian.tar.gz 446a4035246425263fcabfe6d6c877d8 1896202 mail optional sogo_2.0.7-2_amd64.deb f20925d41e5c92ec75363a502d6c64ac 1595404 mail optional sogo-common_2.0.7-2_all.deb 30cc970cd3022235885d969df69b99f8 3294224 debug extra sogo-dbg_2.0.7-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJSG5uvAAoJEDGCUpfTb5CBb+AH/jT4pLcG6mfqw4C0E7r+y+Rl YN6ppfMt3Kf6NP3di/crak8fQs7LHLom7ebdzw+POuecE/VvE1Va30PbwFBU4gE9 PaU1p8PTXoNi3x0HktES1FBY+8UL3Fw2LrxynVXDADZNkSFLKUS5FRL+h+QjR841 jLjRDVxwOB9v7uBn7mw+lXTpHOnTVDlb9rgc7yjhp3Z2XVoFwpindGV/TIf5jqIK uS6t2XyzohrcO6I8jpx8Ng2Q3pL0/Bp8sVmR8ObxRrM9sA6IszqriLJe+iomFhJk 1lp+JeZGh0dv4pRdPRCjsFLY3mFzTLtmn+OgSSixu6GU+/jnqUy8E4vtBxBhaDE= =u0m2 -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/e1ve1ba-0001jg...@franck.debian.org
Accepted sogo 2.0.7-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 13 Aug 2013 20:32:13 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg Architecture: source amd64 all Version: 2.0.7-1 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols Changes: sogo (2.0.7-1) unstable; urgency=low . * New upstream release. * Update version of sope build dependency to 2.0.7. * Remove patch applied upstream: - 0001-Set-SOGoMailSpoolPath-to-var-spool-sogo-by-default Checksums-Sha1: 24d67bf6d9b64476ddf8ea2452fecb55de6a050d 1693 sogo_2.0.7-1.dsc 66e141a54bbb10cf40990e5b84e739936335 5694507 sogo_2.0.7.orig.tar.gz c0ce627aeb7645a021cbd79e84184e8f7850661e 12064 sogo_2.0.7-1.debian.tar.gz b293c7ad66b5225081c7ee0413bc9f0d638a617d 1897622 sogo_2.0.7-1_amd64.deb 7e30b13e42c467e0405f402f8e092236c3a60f02 1595246 sogo-common_2.0.7-1_all.deb 6cd8f3aa907efc2fecdc59a7d927dee46a18e152 3295102 sogo-dbg_2.0.7-1_amd64.deb Checksums-Sha256: 387e47611993b7544781251cd655096d207c0e1998abdac24f16d6fcfc55c0e1 1693 sogo_2.0.7-1.dsc 1197bbda16e5a7e94c70efe21428b34a1830be00bf605da633a8ee82adf4be5f 5694507 sogo_2.0.7.orig.tar.gz 8e9fd3d9f98d118de2c2a919433e3f935c63fd2f516c6bf75bb73c58168cbfb1 12064 sogo_2.0.7-1.debian.tar.gz f6ca03c84d54a56fc8b2c06b6228fd57c89608900a20b778860da5989bbf1d78 1897622 sogo_2.0.7-1_amd64.deb 9f1087f6c0ebb13e12281b749c9fafc717dfd9fa1cdb2ba364b2eca744c02af9 1595246 sogo-common_2.0.7-1_all.deb 59fa23f72d2560167944ba17f036a17800886eb6233207dbbaacfe58a0b7d440 3295102 sogo-dbg_2.0.7-1_amd64.deb Files: 4af3838d5c61319d1bb769cf21fcea8a 1693 mail optional sogo_2.0.7-1.dsc c666706e006a1b4312789cddce5da2ee 5694507 mail optional sogo_2.0.7.orig.tar.gz bc87a09ae7dec176d267ca3d48926137 12064 mail optional sogo_2.0.7-1.debian.tar.gz 6d50a22e7d62dc445ac58ceb52ce524d 1897622 mail optional sogo_2.0.7-1_amd64.deb 6b1ae420addc1d078c67e158d16d8fa0 1595246 mail optional sogo-common_2.0.7-1_all.deb fe3a2a082389aed0b62125510a8355e8 3295102 debug extra sogo-dbg_2.0.7-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJSCn6SAAoJEDGCUpfTb5CBrq8IAJG7bbw8w3Y2DNOfFYM52617 yEihXSm7GV4/s/mfFQVPIxoJ84JYSA7hgMbsYK9wU/a7i1sbbhwDssOGXs9KHpsA uP4cFBfY3obJFd5O7dJvFbaxCg8Fswdvkrgx/cIWQqR24riqaJvJghUQOrg2amMq BsfUGMXsaHa+5LacrneGjAjwHEKr/nwQ6Db7V7MQV1HDPWonu+h2Scja5hYnfT/I rH71RpalGJN/9Gmg7on7DRPFGRkctPYQhlavU4TIv6p+jmMQhODJr62GaISRLHv7 DVuz0Px7qc/63W8jzSy64QbUiPlPA8QnpYHXjFzRPz81WdGVGs1Z9gfNee7hZxE= =4JCv -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/e1v9jsv-0001xe...@franck.debian.org
Accepted sope 2.0.7-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 11 Aug 2013 20:18:06 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.0.7-1 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (2.0.7-1) unstable; urgency=low . * New upstream release. * Include updated watch file written by Bart Martens. Checksums-Sha1: 853983ba6785ae354481135c8215d61d24c2a389 1695 sope_2.0.7-1.dsc 3fc17d78fa2d8839459c185f2678fc3e67b4aafd 2250930 sope_2.0.7.orig.tar.gz e156225cbdf5bec7f18794314c4a8564f5d604a7 4399 sope_2.0.7-1.debian.tar.gz c74f0ee0c796412fff5eb919b059eb9d88fe8220 1871850 libsope1_2.0.7-1_amd64.deb b99ee368f07c1728f43b81c0264b2b9de53d461a 220172 libsope-dev_2.0.7-1_amd64.deb b8aee94b91c70c9edb89258916a1e2d5b1756d9b 4255142 libsope1-dbg_2.0.7-1_amd64.deb Checksums-Sha256: 74febb21aa5f57734e7fc4a0be9027d4a015dc97942484763bb7e7b91b4e7888 1695 sope_2.0.7-1.dsc fbbec2224ff7a654ee49b06700cbdac639e50953fdcee9ddf89202964c3fbf9b 2250930 sope_2.0.7.orig.tar.gz 55a93df04f216c1686375f4443dcc21fc7674bd90547a29e3040688230930a32 4399 sope_2.0.7-1.debian.tar.gz d7f2ab576da8fa0df69b335825b0fa059accbc50de1100194563c39ffdb47f48 1871850 libsope1_2.0.7-1_amd64.deb 3482519456ef89c31b4dae761b6f42202549fd688fd3288db1fe2459dea8776d 220172 libsope-dev_2.0.7-1_amd64.deb 682f39db7639b31d26165056208553d562356960c8ab8e311bda339a9cedfc70 4255142 libsope1-dbg_2.0.7-1_amd64.deb Files: f151e56a31881bca5c45d557f0865c28 1695 libs optional sope_2.0.7-1.dsc e0ad366c4337198aa710a8a2a6f02850 2250930 libs optional sope_2.0.7.orig.tar.gz d2ffd3d8835c928481a6819fedc25461 4399 libs optional sope_2.0.7-1.debian.tar.gz 0333a610170762a5458a26bd74b694a3 1871850 libs optional libsope1_2.0.7-1_amd64.deb a7d9dac407fb8ad0537a44f593bfd337 220172 libdevel extra libsope-dev_2.0.7-1_amd64.deb 8d77af6f229a3f8043d539edd85fbcc3 4255142 debug extra libsope1-dbg_2.0.7-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJSB9j8AAoJEDGCUpfTb5CBD0EIAIAq0k+mCz1QR2zy+y1bRPDQ HKMobwKjU5yzd/IPi6NhEeL55QsOfzzj1Da0xy/zNyWdaeb+9wEHobqgSCcZuKDP HJ/pFFNC4f8oOUX9cuzvWNnDJ6l1wNqTkkB1cBZcUliX5OpCKcWrtWemvLY7ea68 xf6va4Zdq8FmKUQBRvaCYpKXZFTa6RBLIhjTnNB6VT8c0O9zPLnFkGTirsPLu1kX b5Gw8aVaWGCIi19YhUp3qxojcexsh0Ycl0nc0bgN3KiwHzNfvnWofYM/xiLwA4cV 7J6B2DWJUniSgjZ8Uj3ZJ6YZstw6NLpTm0nBk7RKQoULhO/GHsUcTvYwbBf9vtI= =5hkM -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/e1v8ah2-0002nr...@franck.debian.org
Accepted sogo 2.0.5a-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 06 May 2013 02:04:16 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg Architecture: source amd64 all Version: 2.0.5a-1 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols Changes: sogo (2.0.5a-1) unstable; urgency=low . * New upstream release. * Include updated watch file written by Bart Martens. Checksums-Sha1: 885f86bec40043a872295b663ab3da362fd77a78 1700 sogo_2.0.5a-1.dsc a559ae03239968c847d364db1cc32996266d0bf1 5640595 sogo_2.0.5a.orig.tar.gz 7b2c534efac0777092283585e49763c5839d9095 12203 sogo_2.0.5a-1.debian.tar.gz 436aa6d60ec6e2bef13638abfb5f78817aa0ebc3 2239766 sogo_2.0.5a-1_amd64.deb 0d5429bbaacc2689eb7462c028b6f68784a826a0 1966134 sogo-common_2.0.5a-1_all.deb ddf17756b56e285bd8df2df935d7a5bd53a2eb99 3350022 sogo-dbg_2.0.5a-1_amd64.deb Checksums-Sha256: f592a51b1634751ca587eeeaa44f22932c36665e20203d0e24e77a6df539b669 1700 sogo_2.0.5a-1.dsc abcb3b426ea9adf3d9cc0cb116b40cb5de9bde54f319326725ce25f3d3c25b78 5640595 sogo_2.0.5a.orig.tar.gz d4774b36165626feb60600d0220d06fbf1383d6a4ba7bee5b9043ac0b12ed887 12203 sogo_2.0.5a-1.debian.tar.gz f173e1c6f8605350a2f5ef869eb0c5df5c9018ba3e0f514be5f923bde292a257 2239766 sogo_2.0.5a-1_amd64.deb 405d0b3c8d0a81c19192c4aa985b65f5fa4413b12ae1e61940c41f5579028e94 1966134 sogo-common_2.0.5a-1_all.deb 65844ff0f0d850d855f302f8d815b8e493990197fbcb44543875232ea3b92880 3350022 sogo-dbg_2.0.5a-1_amd64.deb Files: 2c73f7887aab118049eff4a3873d8abe 1700 mail optional sogo_2.0.5a-1.dsc b7b24adb22c52b974a1a4d08ae8c23df 5640595 mail optional sogo_2.0.5a.orig.tar.gz a61537d18dabf631828a9d337764da51 12203 mail optional sogo_2.0.5a-1.debian.tar.gz dc4e187cb610fe2d9de4b2e23c667c9b 2239766 mail optional sogo_2.0.5a-1_amd64.deb aea6b98657fef491485c7e3b96ef79fa 1966134 mail optional sogo-common_2.0.5a-1_all.deb 905fec921332aea3928f16a88ff6703c 3350022 debug extra sogo-dbg_2.0.5a-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJRhvWSAAoJEDGCUpfTb5CB9yEH/1QAM8Eq3DP3OvX+rseEj2Qh VWxPL4/YlG2bZZ/vMSv01GYPv97avZfvVv7QWTIs9Ynb5jSmAyhVueStJQmQofwJ uKeaOCJqCIO/WK8lx6L7ZE6LvLRJsCslyAWyh71Kmzu+LsqdlMqFNlRdgFkQTso5 TbVHCL2jqjfapBRMmHvQtQEyX2rt6tddL2IbTa/t5uG+ZIzKpxTdFL+8qFXGrXA8 HZ14oFtI5T48QLtbagiPKX/vCy5aNUgRp9MFhIivmZl8wi18ED7uDaygEkCOEJZr +cwBEzDquxJKrGfmOhW7QD9YTBNmIRmoKwOw+rhbQedGBUGXYZ3zjhojAd6X0Co= =fCSF -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/e1uz99v-0008og...@franck.debian.org
Accepted sogo 2.0.5-1 (source amd64 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 13 Apr 2013 16:08:45 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg Architecture: source amd64 all Version: 2.0.5-1 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols Closes: 677951 681797 682843 Changes: sogo (2.0.5-1) unstable; urgency=low . * New upstream release. * Remove patches applied upstream: - 0001-make-check - 0002-link-everything-correctly - 0003-Read-configuration-from-etc - 0004-Add-support-for-GnuTLS - 0007-Compile-daemon-as-PIE * Fix cronjob error after package removal. (Closes: #682843) * Update standards version to 3.9.4. * Enable SAML support. * Move sogo-backup.sh to /usr/sbin/sogo-backup and change backup location to /var/backups/sogo. Also change the locations in the cronjob. (Closes: #681797) * Use systemd-tmpfiles instead of tmpreaper for systems running systemd. (Closes: #677951) Checksums-Sha1: dbebafddc1d8d85618d83f318d8d3f218eb1db0e 1693 sogo_2.0.5-1.dsc 17c577baad3bc97b65f67d094094a35a91dadf69 5640421 sogo_2.0.5.orig.tar.gz 1f1f65131e54e0d695c4c80bc34ca0852f0f3071 12005 sogo_2.0.5-1.debian.tar.gz 5492e2cd655766c4ef168b8d16866aefd037f139 2238884 sogo_2.0.5-1_amd64.deb f835ff2bd30c539a8ace5e1f2eca0cd2bf459611 1965902 sogo-common_2.0.5-1_all.deb 65cf1ac32007cef849b758d16ba9e71bd08e91c2 3347954 sogo-dbg_2.0.5-1_amd64.deb Checksums-Sha256: f2c2551e24fbfe2bc6405c976b750590cc6e60b39929e26f5a5b9485497706d3 1693 sogo_2.0.5-1.dsc c110cc41077e1edc1b2e9131c988c42666f25b7cecb64011e66802845e898323 5640421 sogo_2.0.5.orig.tar.gz 28e13dad00f2cbc5cbbb935106190cbcd332ff3db73e981b81fb136f7648e8d3 12005 sogo_2.0.5-1.debian.tar.gz 3e385d6b40271d4bd57f0415764a6147a5d418e7df77a857768d4c880b7666ee 2238884 sogo_2.0.5-1_amd64.deb 8b97dc61c73735cc735a0ddf5bf4ac6e25d4a7d920e2d76e820890bfdc36c02b 1965902 sogo-common_2.0.5-1_all.deb 8be55e457392f32261a348781a2fc12f60010518df5fad1e3f0bc6719f746d51 3347954 sogo-dbg_2.0.5-1_amd64.deb Files: 1eb92a2adf5ee6e24baa54343a10d565 1693 mail optional sogo_2.0.5-1.dsc 0f90857234fd0cb931cff84fa2e79644 5640421 mail optional sogo_2.0.5.orig.tar.gz 69d05f03054b5c5934670eea87e01162 12005 mail optional sogo_2.0.5-1.debian.tar.gz 3383780de4ab62154903c64f18c9ffab 2238884 mail optional sogo_2.0.5-1_amd64.deb e1e3f0429a4fbd452cd943e1fe3d5cb0 1965902 mail optional sogo-common_2.0.5-1_all.deb 089e3bc2061ab130ebf09ef2ee65134e 3347954 debug extra sogo-dbg_2.0.5-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBCAAGBQJRaW4SAAoJEDGCUpfTb5CBkJQH/3BSZur5AN7pd85IS/8RLZGf vmrx4QFpA6AW/vQLQhHvVmN1lW2X/bTFKs0ex99akLFVTY052fuGw2m+iXoPdEt8 4FLeFZSq2FMaBjGwyU7lCRtF3rGEyU1+xHlaVRSxZeNtWrliU9ayBv1U1UChsD2B MFo2aVS7+rC6RIKjRiowt07LxCJSw5Xbul/Pw9LZ8PGneT8d/z26xWrhSkfQvj7e X52XFqSKnL547NymvG/hiv68MyTIEIu7+PEEFbk9hgKrrZpkdO4ww3GLIRP8ThyQ H+Kk3C04Ou4m6idxTZSVqEoIkxKhZeqipgwcCDCaJp1t63pgl/5B8zMeuo54eJ0= =iZRm -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/e1ur1nw-sv...@franck.debian.org
Accepted sope 2.0.5-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 12 Apr 2013 19:47:43 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.0.5-1 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (2.0.5-1) unstable; urgency=low . * New upstream release. Checksums-Sha1: 21350bbb014a9d7c6f390f090cf4486db8ac6232 1695 sope_2.0.5-1.dsc 28acefc777054876ba6a8a148cf67c012a23eb07 2249665 sope_2.0.5.orig.tar.gz 806ad09a0992e6f10188c3f3ee87e8bab77afe19 4318 sope_2.0.5-1.debian.tar.gz 7857f111c25d9562b4bee205252f417ee8e4a1d1 2625206 libsope1_2.0.5-1_amd64.deb 92331b7686e23ed615de932a285074050c4a9d62 249768 libsope-dev_2.0.5-1_amd64.deb 012795cb7f72b7f9c2c3cbf5b32fd03f5c5cb784 4797010 libsope1-dbg_2.0.5-1_amd64.deb Checksums-Sha256: 4bbd6ae27cfa6b7fd5ba5b03cb66db085036f9f8217b506fb77fa26d8720eca4 1695 sope_2.0.5-1.dsc c9246829ad57addb58e244e654bff86380f3ef6abff7153c4138c7a2c701ca5b 2249665 sope_2.0.5.orig.tar.gz 93e2d875919fe8e9da64c01833dfb301a59065ade3892584a05d0087d1e351d4 4318 sope_2.0.5-1.debian.tar.gz ddc1bffe9b9ca5909a1e9065dffd1260fbad1d10ab5ce94c63e24fa6b3d13ca1 2625206 libsope1_2.0.5-1_amd64.deb da1defe276cee2c34ed13ce491c8a4ece3d7ac135c1194ce25f4aedee0368804 249768 libsope-dev_2.0.5-1_amd64.deb e65b5c45eb0da7102426cdb3afb9d17446e2bbcd1b443e0d3b60b2e7b9000826 4797010 libsope1-dbg_2.0.5-1_amd64.deb Files: 3c84cc19d1939c9a44ad92225b6de5ec 1695 libs optional sope_2.0.5-1.dsc 94924e33de9f7d0e8781085a9cd6 2249665 libs optional sope_2.0.5.orig.tar.gz bce9007e193e4b3f5cc5a81e7dcf2b8c 4318 libs optional sope_2.0.5-1.debian.tar.gz 3f2ca73236148126d758a46705cf8a7d 2625206 libs optional libsope1_2.0.5-1_amd64.deb b1c48a1bf3c6af1c877cae5cfd0bc7ca 249768 libdevel extra libsope-dev_2.0.5-1_amd64.deb f29e2e019f70fb7b1b04eb688007873d 4797010 debug extra libsope1-dbg_2.0.5-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBCAAGBQJRaFz9AAoJEDGCUpfTb5CBikYH/AxRjtCvKzRnaU/x6d314TtP 5mtP7lz4woyaUmvOZyFzlwzyWs7ddTPoKakjHa2mQRoQjZ/gXMyBzYozzDM28O2c PL5K7duIV8GctqOB9u1uu/FVw7+N5B0+huLlhr6JxNBIZksufYbv/lMZAQGRnt7H /oE3BCaj9XXWpz+M7a+WwVuMrf2Rn0N5NmJbiuI/2DBvSsYSAL648DL0VR4oSiwi idW5TDNQjFEK0qsLUzbXx8LeqJFzdegmv63WJCUj8BSym7EQVOom1rDYqhufe7pU XRW/tb28qoa2sjkkPbfyizQ0Vom4SCVrwDwf7ozG3oH+gWpNDLX1xhqi917Sb94= =vmPW -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/e1uqjtr-0005lw...@franck.debian.org
Accepted sope 2.0.4b-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 14 Mar 2013 17:19:26 +0100 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 2.0.4b-1 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Closes: 680735 Changes: sope (2.0.4b-1) unstable; urgency=low . * New upstream release. * Fixes FTBFS on alpha. (Closes: #680735) * Remove patches applied upstream: - 0002-use-gnutls - 0003-close-all-fds-on-daemon-start - 0004-link-everything-correctly - 0006-Fix-FTBFS-on-arm - 0007-Remove-disabling-of-optimization * Call dh_makeshlibs with -V. * Update standards version to 3.9.4. Checksums-Sha1: 0a3cc525a1f16fd15ba30a1c0fdb98d6b8d5021f 1702 sope_2.0.4b-1.dsc c2443b39f152c201d8e34a9f2dbee2fda8753ad3 2248548 sope_2.0.4b.orig.tar.gz 48b1bc1da1e1be85c10303892041edf2175619b3 4307 sope_2.0.4b-1.debian.tar.gz 66b4e5c8bd254e62d7ac47c15755f2bbf6e0f54f 2624568 libsope1_2.0.4b-1_amd64.deb 339bae9a44bce0c5bf3e96983590f087db546c78 249458 libsope-dev_2.0.4b-1_amd64.deb 9dd7b86c21b003f1e3b37ea7368ffdd60345abaa 4795882 libsope1-dbg_2.0.4b-1_amd64.deb Checksums-Sha256: 0fec2ee4866ad374a9876fdd26757ee0bf5da75a4911a40870366b35e0428d36 1702 sope_2.0.4b-1.dsc d8ce4f69326b0789632f3f6f55507ef8507d10fc25bd9492ae3627378a8b3aec 2248548 sope_2.0.4b.orig.tar.gz e015f309667955469d42c38a28ab9f1f046dbea4b0cfabb5a0169304254d9271 4307 sope_2.0.4b-1.debian.tar.gz 8a6499975611831efff37017131931b76e5843dc3520f322f077d2cdabd3db30 2624568 libsope1_2.0.4b-1_amd64.deb af556a358bdc610d8f27b2d8599b2d4318067215fda7be163cb13c85ed5d7a19 249458 libsope-dev_2.0.4b-1_amd64.deb 2fa2ef8f1be3293b0f0a3f9eea78c415011ecd3960c137327d9695399e465be9 4795882 libsope1-dbg_2.0.4b-1_amd64.deb Files: ec73c04f32ed4fb43674322dc205432d 1702 libs optional sope_2.0.4b-1.dsc 0bd363c33c3a360fc6f5607293387b39 2248548 libs optional sope_2.0.4b.orig.tar.gz 07aaa6a7d810994a9fb2005b730e9a09 4307 libs optional sope_2.0.4b-1.debian.tar.gz 5b38fca42496d817daafbd0d0846d1d0 2624568 libs optional libsope1_2.0.4b-1_amd64.deb b51831a5be8898612c52193a6f3c79e7 249458 libdevel extra libsope-dev_2.0.4b-1_amd64.deb 82d6465e54acd810a791138eb5eebdc8 4795882 debug extra libsope1-dbg_2.0.4b-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBCAAGBQJRQgZcAAoJEDGCUpfTb5CBoAMIALDc2AQC7DTJ9/4uVUxxLaFA 7T/yUoVCqEzfFhyNhKc72JQ6FabklIQgrEoxP9jwCbPGcQffspleLDO0gCMBKETr sitn8UjBDI1UvCsFeFmotioT2SuRzdzsYyh76h46/Qk9cyzITRDffOa+0rz8IKt7 L+hFwWUq/r03v+AxFntQaqXOcWPP92k2UlVFGngjtOa1ITr+gbM0w2eup/d+BpKr 62USeQQTe16n2ZDtTo6pA3o4FjBwER20biPMXHZFD8trPii7inUaUH+BvheaXRbb T1eiLJnLbazBXg6I1jFlQ+8G09hD6PRFynthK/OJH99OywaCHU/irZwFMIhBX+s= =WSdJ -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/e1ugc19-0006hc...@franck.debian.org
Accepted sope 1.3.16-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 29 Jun 2012 20:53:29 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 1.3.16-1 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (1.3.16-1) unstable; urgency=low . * New upstream release. * Drop patches applied upstream: - 0006-Fix-compilation-on-GNU-kFreeBSD - 0008-Fix-stale-cache-issue-when-upgrading.patch - 0009-GNUstep-1.24-fix.patch * Build with hardening enabled. Checksums-Sha1: f0fc57ccab639228fff20716e6393eaa0a44fc47 1380 sope_1.3.16-1.dsc 32b1dc4e676919bf1a0eeb9603cf7a937c0810e5 2157287 sope_1.3.16.orig.tar.gz 6ac1c3af91113035ed368dc92da2316706fb8ecf 9659 sope_1.3.16-1.debian.tar.gz e5c130a7ddd29abc56f32c73ebbde06cfdb0c602 2570974 libsope1_1.3.16-1_amd64.deb 08f2361b2b24d98a74bf620f886e5b936cd0121c 174590 libsope-dev_1.3.16-1_amd64.deb 2e1da40d570b8d01b1f5fcda10fae3946e18b906 4741012 libsope1-dbg_1.3.16-1_amd64.deb Checksums-Sha256: 910434d6b4925650afe31ad456f5e259378cf81716f80200204841fb89577b0d 1380 sope_1.3.16-1.dsc 82c814f405870dfbfbedb3926a91c2d8d7e71e340ec10e08413d846c5cef2e79 2157287 sope_1.3.16.orig.tar.gz 382923b69a1eea1633b0bf2f2be9c228636056216ccd9fa3da94eb45cee8c8f3 9659 sope_1.3.16-1.debian.tar.gz 6e21cee6adf71a6a37a1358691ea782bfbd1422fb31bc9a598eb44f15bfb5cbd 2570974 libsope1_1.3.16-1_amd64.deb 400f8b3faa022a2e9d811f3f5f893fa642e80705200a43fd69db2ecc82c2f520 174590 libsope-dev_1.3.16-1_amd64.deb 1ef980b2ae6305b268720c347e96598191eff79a635e54442f9fa9aa8694b95e 4741012 libsope1-dbg_1.3.16-1_amd64.deb Files: ecada6ad411e08605bd2efb55d63d24a 1380 libs optional sope_1.3.16-1.dsc b20f64d058018bab4c8da4450824e956 2157287 libs optional sope_1.3.16.orig.tar.gz 13be7761de7b10b163699bb1df0e4aba 9659 libs optional sope_1.3.16-1.debian.tar.gz d5f7ac1294d604fabe87eaeac25de299 2570974 libs optional libsope1_1.3.16-1_amd64.deb 9aaeff22fa8161b8f798c01e86013c45 174590 libdevel extra libsope-dev_1.3.16-1_amd64.deb 664a63c24447e8173848644334663d88 4741012 debug extra libsope1-dbg_1.3.16-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlABnjwACgkQPa9Uoh7vUnZDqwCggAreJoKv+x/378Fns8J+35cS vXoAniYgJ+1sSxmg6TPP9UzkJYrYQhBU =t1Ms -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/e1sq5hw-0007pt...@franck.debian.org
Accepted sogo 1.3.16-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 30 Jun 2012 02:55:17 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg Architecture: source amd64 all Version: 1.3.16-1 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols Closes: 677119 678047 678099 Changes: sogo (1.3.16-1) unstable; urgency=low . * New upstream release. (Closes: #677119) - 0004-Add-support-for-GnuTLS.patch: Updated to new hashes in 1.3.16. - 0007-GNUstep-1.24-fix.patch: Removed, was backported from upstream. * Do not assume deluser is available in postrm. (Closes: #678099) * Suggest postgresql or mysql-server. (Closes: #678047) * Build with hardening - 0007-Compile-daemon-as-PIE.patch: Compile the daemon as a PIE. Checksums-Sha1: 77bc50f009bea7b732eef74de2aa861b09e1572c 1348 sogo_1.3.16-1.dsc 912ad2447f33b767e75527ae492711e46126d106 4930514 sogo_1.3.16.orig.tar.gz 893d75f71596701137b1f0ed1daf716492b5b1bd 19784 sogo_1.3.16-1.debian.tar.gz df7f15f43c6fabb1683dc79f481f56c2c8f7e750 1559398 sogo_1.3.16-1_amd64.deb 50f804ab64650cfb094210e9566e4b7df194eff2 1547128 sogo-common_1.3.16-1_all.deb fc3e64d0b50de78f0a9ed30a34ed6cfafaab10c5 2622298 sogo-dbg_1.3.16-1_amd64.deb Checksums-Sha256: bd9e8d105ce73e7a93ffe2c271d821f6856463c2b2139e22cdb1f2851b535d86 1348 sogo_1.3.16-1.dsc 115be27b7f7e9e386185190950cd9b048744b90dcbb225fbde1efedd58bc6775 4930514 sogo_1.3.16.orig.tar.gz 55faa4d97d96c63140e88ff78c2f657a8b7f7a667ef1e698f54f783db2a28cc9 19784 sogo_1.3.16-1.debian.tar.gz 865abd03d0982ba92ea4611313c9b0111f62cfaeaf3118d50a842c5a140341bc 1559398 sogo_1.3.16-1_amd64.deb 99e5ff238efcdcc8ba54afedd51a5d6a61a1a7930c5158cb1831450eca6cc532 1547128 sogo-common_1.3.16-1_all.deb 2f3b9968f3e5f54c1838b5ffa0c23dacbf6b25122ac32c1173e7c51ecac2a95c 2622298 sogo-dbg_1.3.16-1_amd64.deb Files: d2425d553fd6eb9ede7bfdb786036316 1348 mail optional sogo_1.3.16-1.dsc 7efd660274d2b8725115cbe2fe1667e9 4930514 mail optional sogo_1.3.16.orig.tar.gz 6a5d0820d74b7fc00ca62827282ccd29 19784 mail optional sogo_1.3.16-1.debian.tar.gz 4fc7023cf618077c5dc8853bf92f3118 1559398 mail optional sogo_1.3.16-1_amd64.deb 85fe28245de38d267933af3f4a781684 1547128 mail optional sogo-common_1.3.16-1_all.deb b07d3fe8dff3816fe5c73ffa7cc8f7c3 2622298 debug extra sogo-dbg_1.3.16-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlABoJwACgkQPa9Uoh7vUnb++QCghCHdrUbeOd/epzC5B93ARK8e MLEAmgNXdhBh3Pj+mfNeoex4gap5z+be =yhD0 -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/e1sq5wf-0001dl...@franck.debian.org
Accepted sbjson 2.3.2-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 29 Jun 2012 19:09:28 +0200 Source: sbjson Binary: libsbjson2.3 libsbjson-dev Architecture: source amd64 Version: 2.3.2-2 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsbjson-dev - Objective-C JSON library (development files) libsbjson2.3 - Objective-C JSON library Changes: sbjson (2.3.2-2) unstable; urgency=low . * Build with hardening enabled. * Correctly link with libobjc and libgnustep-base. Checksums-Sha1: f06b627dbd3b7e85424b7d48ec178d08e44ce5fc 1271 sbjson_2.3.2-2.dsc 04ddaa40fa029065964526e779eeb0946d03073a 5436 sbjson_2.3.2-2.debian.tar.gz da247af5650c911c68d25f7479205f2f44b7843f 18452 libsbjson2.3_2.3.2-2_amd64.deb db22b5d2ddb4ba01087519326fedc0271f877a17 5640 libsbjson-dev_2.3.2-2_amd64.deb Checksums-Sha256: 3ce0c5c93e0695beaae8fc046d6db39f98de59c1678380d9d9853353bfef0211 1271 sbjson_2.3.2-2.dsc b981ea6c64c8a4df5bedcb3e2175e692562d8613dc659d3207e5be01a0dc2660 5436 sbjson_2.3.2-2.debian.tar.gz 1496ce66f4cdb6c082a5935b051f2df257667f15277b462f3ce03cf2a6ba6123 18452 libsbjson2.3_2.3.2-2_amd64.deb 5eff8d0c3b4353694d3b0428370eb258ffbb83b79924c291171432302bc484a4 5640 libsbjson-dev_2.3.2-2_amd64.deb Files: 1de59041b36fe09b2cf300f1e9c2beaf 1271 libs optional sbjson_2.3.2-2.dsc e2c27efc6c13324e4649b258ced4fb10 5436 libs optional sbjson_2.3.2-2.debian.tar.gz 76d61b11c944d54299c90dd5e34751dc 18452 libs optional libsbjson2.3_2.3.2-2_amd64.deb 29679370e622da452a384e94fcdbadb6 5640 libdevel extra libsbjson-dev_2.3.2-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/xZ3MACgkQPa9Uoh7vUnZeDwCfSlJHWX2KTPTzk6Kdo/8oj4cU sVgAn1d0pN8qWJXoStp8aJtnAWShboTD =/3cL -END PGP SIGNATURE- Accepted: libsbjson-dev_2.3.2-2_amd64.deb to main/s/sbjson/libsbjson-dev_2.3.2-2_amd64.deb libsbjson2.3_2.3.2-2_amd64.deb to main/s/sbjson/libsbjson2.3_2.3.2-2_amd64.deb sbjson_2.3.2-2.debian.tar.gz to main/s/sbjson/sbjson_2.3.2-2.debian.tar.gz sbjson_2.3.2-2.dsc to main/s/sbjson/sbjson_2.3.2-2.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1sld03-0004of...@franck.debian.org
Accepted sogo 1.3.15a-2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 14 Jun 2012 14:28:31 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg Architecture: source amd64 all Version: 1.3.15a-2 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols Closes: 675201 675238 676161 Changes: sogo (1.3.15a-2) unstable; urgency=low . * 0007-GNUstep-1.24-fix.patch: - Fix to cope with changes in GNUstep 1.24. (Closes: #675201) * Fix the cron.daily job: - Delete the directories in a proper way. (Closes: #676161) - Test whether tmpreaper is still installed before executing it. (Closes: #675238) Checksums-Sha1: bcf15930adabee0f12e1aba0069f3ea1238ebd4c 1355 sogo_1.3.15a-2.dsc 82e0860899e976363e539f7dc65c419a3a5fc77a 19160 sogo_1.3.15a-2.debian.tar.gz 8dc1f47bc475e18862cd27b31ab57312e0e85dfe 1516616 sogo_1.3.15a-2_amd64.deb b4188c3d67309fdd5be56a045ff27742f6cbe3b6 1544382 sogo-common_1.3.15a-2_all.deb 11979d21da9b1a726ff1070f36749d14759acfaa 1515292 sogo-dbg_1.3.15a-2_amd64.deb Checksums-Sha256: 236bc1415ef5b7b36fc528ce820cf72ebff0bfc9dd08361a4f581dc5123cc30f 1355 sogo_1.3.15a-2.dsc b7105aee4e8d632f32b18510df5ede52cf242fb3878040150b132c9b2af22dcb 19160 sogo_1.3.15a-2.debian.tar.gz fb952584ec19fde4d1b3de035637940ffdecf62fb7c011ee55f4e0bf6a2cdd19 1516616 sogo_1.3.15a-2_amd64.deb 8a1b27a095680ab7e6a6b0c9df5f0bc7a7c81d0a5820d9a6f033b57b2590b53a 1544382 sogo-common_1.3.15a-2_all.deb 5ec1160710a62c9b033271715c21e46b8cc87246d646ac30cd8ddee1e4cc4240 1515292 sogo-dbg_1.3.15a-2_amd64.deb Files: 45e9fb41c679594e7e001601b77e7e1d 1355 mail optional sogo_1.3.15a-2.dsc 6af28c0c22defc45734f61ac53811a9d 19160 mail optional sogo_1.3.15a-2.debian.tar.gz cc060fb7d7c96094938ca8194d88cac1 1516616 mail optional sogo_1.3.15a-2_amd64.deb c342f2b89100e54871ec448414319284 1544382 mail optional sogo-common_1.3.15a-2_all.deb ae2a1041aca30819d7b8e913e030b7d6 1515292 debug extra sogo-dbg_1.3.15a-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/eZ6EACgkQPa9Uoh7vUnZ85gCfepdou2Lmkj+oTNT473SFMr0h dO4AnjpK4QVHWTV/QITntvBOeoMFF9yR =KxHS -END PGP SIGNATURE- Accepted: sogo-common_1.3.15a-2_all.deb to main/s/sogo/sogo-common_1.3.15a-2_all.deb sogo-dbg_1.3.15a-2_amd64.deb to main/s/sogo/sogo-dbg_1.3.15a-2_amd64.deb sogo_1.3.15a-2.debian.tar.gz to main/s/sogo/sogo_1.3.15a-2.debian.tar.gz sogo_1.3.15a-2.dsc to main/s/sogo/sogo_1.3.15a-2.dsc sogo_1.3.15a-2_amd64.deb to main/s/sogo/sogo_1.3.15a-2_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1sgp3v-0003xj...@franck.debian.org
Accepted sope 1.3.15-4 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 12 Jun 2012 01:08:07 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 1.3.15-4 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (1.3.15-4) unstable; urgency=low . * 0007-Fix-FTBFS-on-arm.patch: - Really fix FTBFS this time. Checksums-Sha1: e5ddf9ec3f48f8c556daa3193baae4fe237c395e 1360 sope_1.3.15-4.dsc 6805eecf7625461be04cbcfb4b234bd827b2af15 15240 sope_1.3.15-4.debian.tar.gz 5a2d3c14296b88d08813f7406a8c271265ac5164 2506674 libsope1_1.3.15-4_amd64.deb f81bf3f25fd5b84b654ab42ba72f3aa4f65f7551 174404 libsope-dev_1.3.15-4_amd64.deb 7b1f804b218eea6453bdd60b889d372c270bf9a6 2812646 libsope1-dbg_1.3.15-4_amd64.deb Checksums-Sha256: 8dcf85740d9da8cf39f439b71ba67193be2beef31ab3e45deb6302cc5ea2e07c 1360 sope_1.3.15-4.dsc bd000c7170c7e704968315a06b866437ef49a02815c8d63f269a10c64c7dfd88 15240 sope_1.3.15-4.debian.tar.gz 4f6fecafce7d12a03a3646eb3d1dff194364a7842cce7bf4c6044eb57b9a689d 2506674 libsope1_1.3.15-4_amd64.deb c03664db044a0b48a92bb0930b3e36a36f1e82946562b9f14ba4a95ce4da1bcd 174404 libsope-dev_1.3.15-4_amd64.deb 0dda259082962eca9cd822e2de8381bc1cc3934e3b74d64a1e016f4360d645ba 2812646 libsope1-dbg_1.3.15-4_amd64.deb Files: 70ef0654c1dc8e0440f607c5375bf50b 1360 libs optional sope_1.3.15-4.dsc d78084cae1e53e2a5092374e1cbd516b 15240 libs optional sope_1.3.15-4.debian.tar.gz db3d5c44020bd8110025e5b33bc49e27 2506674 libs optional libsope1_1.3.15-4_amd64.deb 1b84b3447812499d6a6ea788deecc7f9 174404 libdevel extra libsope-dev_1.3.15-4_amd64.deb 7757c74f488858f1079d076ca6b8c179 2812646 debug extra libsope1-dbg_1.3.15-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk/cRiIACgkQPa9Uoh7vUnbtcQCeOWDTEJ2kKOKiKDSzY5BXltz8 Y+sAoJfbjl4zmsqfwn0ZMfCfRy26K7l7 =vSKH -END PGP SIGNATURE- Accepted: libsope-dev_1.3.15-4_amd64.deb to main/s/sope/libsope-dev_1.3.15-4_amd64.deb libsope1-dbg_1.3.15-4_amd64.deb to main/s/sope/libsope1-dbg_1.3.15-4_amd64.deb libsope1_1.3.15-4_amd64.deb to main/s/sope/libsope1_1.3.15-4_amd64.deb sope_1.3.15-4.debian.tar.gz to main/s/sope/sope_1.3.15-4.debian.tar.gz sope_1.3.15-4.dsc to main/s/sope/sope_1.3.15-4.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1sfp4q-0001el...@franck.debian.org
Accepted sope 1.3.15-3 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 10 Jun 2012 22:05:37 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 1.3.15-3 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Changes: sope (1.3.15-3) unstable; urgency=low . * 0009-GNUstep-1.24-fix.patch: - Fix to cope with changes in GNUstep 1.24. . sope (1.3.15-2) unstable; urgency=low . * 0007-Fix-FTBFS-on-arm.patch: - Fix FTBFS on arm that was introduced in the last upstream version. * 0008-Fix-stale-cache-issue-when-upgrading.patch: - Cherry-pick patch from upstream that fixes problems with stale browser caches on upgrades. Checksums-Sha1: 51a17bf1f0bca30b0c9299e49dc0e74a286e9549 1360 sope_1.3.15-3.dsc eb1a42c4193c4272e1c00acb5a277b9c754282ad 15016 sope_1.3.15-3.debian.tar.gz 71ede7b0aa8de3c77a17a5fadd4b83ef1d40435c 2503556 libsope1_1.3.15-3_amd64.deb 7da776afe74298f836f22ff78fdd69e0bfc2b521 174814 libsope-dev_1.3.15-3_amd64.deb d6a86689329f72fd47597cf8526465e4f1be6cad 2809832 libsope1-dbg_1.3.15-3_amd64.deb Checksums-Sha256: a366803ab6b218f9229403af40e7f90896c1915ce64fc61c2da6ca30cbce30b2 1360 sope_1.3.15-3.dsc b2dd26bac1ab0ea7044f5740d8bfed73689cc9c271995fa2a69352d0358e37b4 15016 sope_1.3.15-3.debian.tar.gz 107ddc97b4c54b835de4ffc532ac4a13e22d1b21068f751ea009d98e1b42f689 2503556 libsope1_1.3.15-3_amd64.deb ca3053dc6aacb555e040449a0a3a6188868dc1056c879b6fc29df600e794c925 174814 libsope-dev_1.3.15-3_amd64.deb e60d2558bffc78008765b3033f2bfe50a8002c5e30ba10b2a8b2ba6571491525 2809832 libsope1-dbg_1.3.15-3_amd64.deb Files: 4bf787a0f9d032eff13cc49597d34c91 1360 libs optional sope_1.3.15-3.dsc c842fe09996d8d0e0914268461ea8589 15016 libs optional sope_1.3.15-3.debian.tar.gz 40e3f01368157af9d8170296c92e48c2 2503556 libs optional libsope1_1.3.15-3_amd64.deb 3607a5e777d2bd70cf0cd4f2853e38d6 174814 libdevel extra libsope-dev_1.3.15-3_amd64.deb 7b5e59fc8f0f896ad80e84a728669183 2809832 debug extra libsope1-dbg_1.3.15-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk/V54gACgkQPa9Uoh7vUnZ6SACcCWj+36AFDuzUmdtZ2VllfExz ooAAnjE+vex+GsjhjPV1ns4NoQSWw2F8 =RepM -END PGP SIGNATURE- Accepted: libsope-dev_1.3.15-3_amd64.deb to main/s/sope/libsope-dev_1.3.15-3_amd64.deb libsope1-dbg_1.3.15-3_amd64.deb to main/s/sope/libsope1-dbg_1.3.15-3_amd64.deb libsope1_1.3.15-3_amd64.deb to main/s/sope/libsope1_1.3.15-3_amd64.deb sope_1.3.15-3.debian.tar.gz to main/s/sope/sope_1.3.15-3.debian.tar.gz sope_1.3.15-3.dsc to main/s/sope/sope_1.3.15-3.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1se45r-0002hz...@franck.debian.org
Accepted sope 1.3.15-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 23 May 2012 16:46:35 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 1.3.15-1 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Closes: 674117 Changes: sope (1.3.15-1) unstable; urgency=low . * New upstream release. * Drop patches applied upstream: - 0006-Fix-compilation-with-Werror-format-security - 0007-gcc-4.7-build-fixes-from-http-www.sogo.nu-bugs-view * Make libsope-dev conflict with libgnustep-dl2-dev. (Closes: #674117) * Add patch 0006-Fix-compilation-on-GNU-kFreeBSD. Checksums-Sha1: 4debf7ee3ad5220848ea2a8f43eac3687f822d71 1357 sope_1.3.15-1.dsc 959e2f34d5e0c2fc62024e31725732ab7616fd11 2156546 sope_1.3.15.orig.tar.gz 66d06c3cd0138b331cc6b5b6bd527d569e6de212 8234 sope_1.3.15-1.debian.tar.gz 828861977ead5cc13c4e74e6ead72649193ecaf1 2505926 libsope1_1.3.15-1_amd64.deb 9e61641fbf81efe000dc07a0c0927fb58edc4d38 174282 libsope-dev_1.3.15-1_amd64.deb 90b045039e172787ada5112789c1c1bbad18ee2c 2809790 libsope1-dbg_1.3.15-1_amd64.deb Checksums-Sha256: 1164694d4c31979b8cf2be8e01b34bab0e1d119041b29ece1c78b8993aa5 1357 sope_1.3.15-1.dsc 99212b6082285df8ea8ecb54a894390ffd3e6177e6de5e84804e056670ee3242 2156546 sope_1.3.15.orig.tar.gz e5f56bf46b0fc070a492ec3f6ede1fdb55f849ff71da3e22794518757eec81ad 8234 sope_1.3.15-1.debian.tar.gz 478342d263c0acad061e20644727208b3f1a5650553e1700435258b5353b2a3c 2505926 libsope1_1.3.15-1_amd64.deb a0a55fc869ea99f627622b67d8590de4aec0465708934a64ab833b661f4b02b1 174282 libsope-dev_1.3.15-1_amd64.deb e6f682525471cb9c656712cdd065812f0b56b470ff91f81adadb976ccf3b6b2d 2809790 libsope1-dbg_1.3.15-1_amd64.deb Files: 229d3d89e952b7765a08416d9e80f019 1357 libs optional sope_1.3.15-1.dsc 1a4251da506f85ed356c46fda908ee85 2156546 libs optional sope_1.3.15.orig.tar.gz a6a8283d5be1fed0a18eef962240b38e 8234 libs optional sope_1.3.15-1.debian.tar.gz 6a944aa383c0578c0eea98c3fa2031f2 2505926 libs optional libsope1_1.3.15-1_amd64.deb b7b5b1d742c31ddd255d90e86de5f909 174282 libdevel extra libsope-dev_1.3.15-1_amd64.deb 8bea88114e8606e41d63dba2b92a4d90 2809790 debug extra libsope1-dbg_1.3.15-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk/DYMoACgkQPa9Uoh7vUnZ9cwCfbuHhvguuUD3Byq9gEPD63wQ4 TAsAoJgEkLAalP+l+7DC6lVgAkPwq6YT =IOOv -END PGP SIGNATURE- Accepted: libsope-dev_1.3.15-1_amd64.deb to main/s/sope/libsope-dev_1.3.15-1_amd64.deb libsope1-dbg_1.3.15-1_amd64.deb to main/s/sope/libsope1-dbg_1.3.15-1_amd64.deb libsope1_1.3.15-1_amd64.deb to main/s/sope/libsope1_1.3.15-1_amd64.deb sope_1.3.15-1.debian.tar.gz to main/s/sope/sope_1.3.15-1.debian.tar.gz sope_1.3.15-1.dsc to main/s/sope/sope_1.3.15-1.dsc sope_1.3.15.orig.tar.gz to main/s/sope/sope_1.3.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/e1syyf9-0004f8...@franck.debian.org
Accepted sogo 1.3.15a-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 23 May 2012 19:17:40 +0200 Source: sogo Binary: sogo sogo-common sogo-dbg Architecture: source amd64 all Version: 1.3.15a-1 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: sogo - Scalable groupware server sogo-common - Scalable groupware server - common files sogo-dbg - Scalable groupware server - debugging symbols Closes: 584073 Changes: sogo (1.3.15a-1) unstable; urgency=low . * Initial release. (Closes: #584073) Checksums-Sha1: c7bead7dd9862d889e7a798b5563e93be772a613 1355 sogo_1.3.15a-1.dsc 734f37546a3b91b92b23bbfe9ba073ab229ddbac 4889123 sogo_1.3.15a.orig.tar.gz 737b3753f2812f030f83d1e5f7d7a5516027b088 15900 sogo_1.3.15a-1.debian.tar.gz 793346e3c89fab41e0ec1a02a19049376699096e 1518990 sogo_1.3.15a-1_amd64.deb 7e1aca6c3665b2c7b769b735e3e61381d4020770 1522192 sogo-common_1.3.15a-1_all.deb ec552b9da627c62ba4ba28505f3b90df880902a0 1514578 sogo-dbg_1.3.15a-1_amd64.deb Checksums-Sha256: 599df7f01de30d42bc85b289be120f016929b1ecd6877f23d00bb1e95e21f4f9 1355 sogo_1.3.15a-1.dsc 3045dc81d6e75a92014c7b88f2729272ccf899660b3c3becf19467665084 4889123 sogo_1.3.15a.orig.tar.gz 5a9abe83b11f4bb215eb92e87ef917da7c32ea9692e20c9d17a25c1c7775681c 15900 sogo_1.3.15a-1.debian.tar.gz d5664ad5827e30c4125f88fd807eec9450f413febef6cd173c4872a95852d69f 1518990 sogo_1.3.15a-1_amd64.deb 201468a5a2bb628dc4903afeea7418519a69aad4eec41a5ba4148863659e5e8d 1522192 sogo-common_1.3.15a-1_all.deb 1f80d754e273471167912e4a5c31d6d95396dbed601a619db320d058b9052728 1514578 sogo-dbg_1.3.15a-1_amd64.deb Files: f14e4d338a8452ac9aca627ec7145a7a 1355 mail optional sogo_1.3.15a-1.dsc 982d3548311b27887b29fdde7476e9a0 4889123 mail optional sogo_1.3.15a.orig.tar.gz 440f7823ca1d23ae3133f9c1075de325 15900 mail optional sogo_1.3.15a-1.debian.tar.gz 66dfabe67baa2998fef1d514e5cee598 1518990 mail optional sogo_1.3.15a-1_amd64.deb 6c5794cf9cb5d51541f42506ff3bfe6f 1522192 mail optional sogo-common_1.3.15a-1_all.deb bedf514abe2d3d3a7680eed567424ebd 1514578 debug extra sogo-dbg_1.3.15a-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk/DbMAACgkQPa9Uoh7vUnZsLQCdFGBDsv8ASuK/U42JC3XBO7kV 4zoAn3dMtH9WHsLYO0aNJz0azakAbstn =jb0M -END PGP SIGNATURE- Accepted: sogo-common_1.3.15a-1_all.deb to main/s/sogo/sogo-common_1.3.15a-1_all.deb sogo-dbg_1.3.15a-1_amd64.deb to main/s/sogo/sogo-dbg_1.3.15a-1_amd64.deb sogo_1.3.15a-1.debian.tar.gz to main/s/sogo/sogo_1.3.15a-1.debian.tar.gz sogo_1.3.15a-1.dsc to main/s/sogo/sogo_1.3.15a-1.dsc sogo_1.3.15a-1_amd64.deb to main/s/sogo/sogo_1.3.15a-1_amd64.deb sogo_1.3.15a.orig.tar.gz to main/s/sogo/sogo_1.3.15a.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/e1sz5gq-0001qc...@franck.debian.org
Accepted sbjson 2.3.2-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 09 May 2012 15:18:17 +0200 Source: sbjson Binary: libsbjson2.3 libsbjson-dev Architecture: source amd64 Version: 2.3.2-1 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsbjson-dev - Objective-C JSON library (development files) libsbjson2.3 - Objective-C JSON library Closes: 672134 Changes: sbjson (2.3.2-1) unstable; urgency=low . * Initial release. (Closes: #672134) Checksums-Sha1: 6e3ba0c3e48af71774cfdc005019728227561450 1248 sbjson_2.3.2-1.dsc 8600b8aa32fd23911be2f83f4566322125189ada 42995 sbjson_2.3.2.orig.tar.gz ea2b008cb7a54b7a0650d036da41bae6755580e6 5272 sbjson_2.3.2-1.debian.tar.gz bd513c81e6f4b7c6268dcc0b3b21d4fbbb75a647 18144 libsbjson2.3_2.3.2-1_amd64.deb 9f47a38c89faf891f0f3fe81e2467d39884ccdd7 5532 libsbjson-dev_2.3.2-1_amd64.deb Checksums-Sha256: fc6729484c78a8d81de8dba00a4d6379a561dd6932d4175d31b1ca0ad2136a96 1248 sbjson_2.3.2-1.dsc a0741d7d3736ae20879aa779cacc8c05752b064387494e5eeb595f2dad98700e 42995 sbjson_2.3.2.orig.tar.gz 4e887a2f5cb369cf603a4669a236a09a7bcdc487f408366e9fe14025b9d5e4e6 5272 sbjson_2.3.2-1.debian.tar.gz 7dae4df436ebd57e4d54d12eb0315b38019b1b7eeaed5cea4e9a80e780de08be 18144 libsbjson2.3_2.3.2-1_amd64.deb 4d9d94d378a490ee29923052bcbc29d95795c5e43f8c47a60408f2bf8936a594 5532 libsbjson-dev_2.3.2-1_amd64.deb Files: 824cec2796ce3b9f1bdc25c3bcac4ff2 1248 libs optional sbjson_2.3.2-1.dsc 67c299ea3635b40f6c5b0ebad76c10b3 42995 libs optional sbjson_2.3.2.orig.tar.gz fb789ff5526f37b9ce9ca7e77bc5c8c2 5272 libs optional sbjson_2.3.2-1.debian.tar.gz 7a81e0a7ed12849d556ba19b14325eee 18144 libs optional libsbjson2.3_2.3.2-1_amd64.deb 822a17c2bc3deab0c588f749a07645de 5532 libdevel extra libsbjson-dev_2.3.2-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk+rxjMACgkQPa9Uoh7vUnYobgCgjrYe5blLayQ+nNLNqt6rMcI0 Xc8AniwyOsxf7TyJOHFJ4+T7VfkUSjl4 =VnK1 -END PGP SIGNATURE- Accepted: libsbjson-dev_2.3.2-1_amd64.deb to main/s/sbjson/libsbjson-dev_2.3.2-1_amd64.deb libsbjson2.3_2.3.2-1_amd64.deb to main/s/sbjson/libsbjson2.3_2.3.2-1_amd64.deb sbjson_2.3.2-1.debian.tar.gz to main/s/sbjson/sbjson_2.3.2-1.debian.tar.gz sbjson_2.3.2-1.dsc to main/s/sbjson/sbjson_2.3.2-1.dsc sbjson_2.3.2.orig.tar.gz to main/s/sbjson/sbjson_2.3.2.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1sw9lm-0002dm...@franck.debian.org
Accepted sope 1.3.14-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 09 May 2012 15:39:17 +0200 Source: sope Binary: libsope1 libsope-dev libsope1-dbg Architecture: source amd64 Version: 1.3.14-1 Distribution: unstable Urgency: low Maintainer: Jeroen Dekkers jer...@dekkers.ch Changed-By: Jeroen Dekkers jer...@dekkers.ch Description: libsope-dev - SKYRiX Object Publishing Environment (development files) libsope1 - SKYRiX Object Publishing Environment (shared libraries) libsope1-dbg - SKYRiX Object Publishing Environment (debugging symbols) Closes: 672175 Changes: sope (1.3.14-1) unstable; urgency=low . * Initial release. (Closes: #672175) Checksums-Sha1: 186d6e829121edef89cc73e39f79d613bcfccc07 1360 sope_1.3.14-1.dsc 5c86983362eecce0f17f8c82a16202e69ba55544 2156184 sope_1.3.14.orig.tar.gz 3780b6ff2cbc9a52a05345b6a8c28059047b6409 12580 sope_1.3.14-1.debian.tar.gz 9307a32c5a197c44960de4ddc1eca5310baccc56 2500276 libsope1_1.3.14-1_amd64.deb fc70987651ef9da7391e8aa956b60f7269d679c4 173598 libsope-dev_1.3.14-1_amd64.deb 2c2d140533599cc55af1124d14d66c85c64e0822 2806878 libsope1-dbg_1.3.14-1_amd64.deb Checksums-Sha256: 55a69e29b7a56eaf4c2a1b892facb83966fbbfd65ba3eef53867a4fecb500ca9 1360 sope_1.3.14-1.dsc 491c3a6318f2ed86e9e3721fea03c2dabff8b39245c75f71952173fceda9f2a7 2156184 sope_1.3.14.orig.tar.gz c5fb541bca59a38c200da69a07e8c8310a1163c5fdfa642e9db9aa13901aa535 12580 sope_1.3.14-1.debian.tar.gz 2549cced895147a33c5d04395cc4094af6c4a0d74c97ac86caffd40659e88533 2500276 libsope1_1.3.14-1_amd64.deb 68702677af6324b368fe4f4295dd66e3309f48f5f7c4369ba09770e58562548d 173598 libsope-dev_1.3.14-1_amd64.deb 12a9acbbe09d4cfbb3195bbd1729723c1d01c41a4f29c451f56e2bb4e2e9308b 2806878 libsope1-dbg_1.3.14-1_amd64.deb Files: cb9a1ee705210a4f667e7d496c6f3f56 1360 libs optional sope_1.3.14-1.dsc 21ea34d2d116c25fb3c8edffdb75cd8b 2156184 libs optional sope_1.3.14.orig.tar.gz 30ea8dcc354b6a40f6f46273ca14ac15 12580 libs optional sope_1.3.14-1.debian.tar.gz 9932046913466701b0eded8b0cffe07a 2500276 libs optional libsope1_1.3.14-1_amd64.deb 2c826bdedcf02fbb3d164c8e17b81cb7 173598 libdevel extra libsope-dev_1.3.14-1_amd64.deb e7a2689f2992bec645b16d02595070f4 2806878 debug extra libsope1-dbg_1.3.14-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk+s3DIACgkQPa9Uoh7vUnYpywCgmP9pLNKlN9UVIuDR39J7cEok q5wAoIx4c/9BeekiOfKbq069GFxrhVO9 =ft8Q -END PGP SIGNATURE- Accepted: libsope-dev_1.3.14-1_amd64.deb to main/s/sope/libsope-dev_1.3.14-1_amd64.deb libsope1-dbg_1.3.14-1_amd64.deb to main/s/sope/libsope1-dbg_1.3.14-1_amd64.deb libsope1_1.3.14-1_amd64.deb to main/s/sope/libsope1_1.3.14-1_amd64.deb sope_1.3.14-1.debian.tar.gz to main/s/sope/sope_1.3.14-1.debian.tar.gz sope_1.3.14-1.dsc to main/s/sope/sope_1.3.14-1.dsc sope_1.3.14.orig.tar.gz to main/s/sope/sope_1.3.14.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1swaex-00073v...@franck.debian.org
Bug#672134: ITP: sbjson -- Objective-C JSON library
Package: wnpp Severity: wishlist Owner: Jeroen Dekkers jer...@dekkers.ch * Package name: sbjson Version : 2.3.2 Upstream Author : Stig Brautaset * URL : http://stig.github.com/json-framework/ * License : BSD-3-clause Programming Lang: Objective-C Description : Objective-C JSON library A strict JSON parser and generator for Objective-C. It adds categories to existing Objective-C objects for a super-simple interface. More flexible APIs are also provided for added control. Reason for packaging is that this is a dependency of SOGo (ITP #584073), my current packaging can be found at https://github.com/dekkers/sbjson -- 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/20120508190942.32318.10897.report...@runge.dekkers.ch
Bug#672175: ITP: sope -- SKYRiX Object Publishing Environment
Package: wnpp Severity: wishlist Owner: Jeroen Dekkers jer...@dekkers.ch * Package name: sope Version : 1.3.14 Upstream Author : Inverse inc. * URL : http://www.sogo.nu * License : LGPL Programming Lang: Objective-C Description : SKYRiX Object Publishing Environment An extensive set of Objective-C frameworks which form a complete Web application server environment. Besides the Apple WebObjects compatible appserver that has been extended with Zope concepts, it contains a large set of reusable classes: XML processing (SAX, DOM), MIME/IMAP4 processing, LDAP connectivity, RDBMS connectivity, and iCalendar parsing. Reason for packaging is that this is a dependency of SOGo (ITP #584073), my current packaging can be found at https://github.com/dekkers/sope -- 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/20120508231524.1632.82885.report...@runge.dekkers.ch
Re: Bug#143209: ITP: switchconf -- Change network config for laptops
On Wed, Apr 17, 2002 at 07:21:07AM +0200, Tomas Pospisek's Mailing Lists wrote: On Tue, 16 Apr 2002, Sebastien J. Gross wrote: ? Package: wnpp Version: N/A; reported 2002-04-16 Severity: wishlist * Package name: switchconf Version : 0.0.1 Upstream Author : Sebastien J. Gross [EMAIL PROTECTED] * URL : http://www.sjgross.org/app/switchconf * License : GPL Description : Change network config for laptops switchconf allows nomad laptop users to easily change their configuration. This package is ready to be uploaded within a few hours. This would be what, package no 6, for switching laptop network config? *t This one does probably something different than the others. Somebody is willing to put time in it and I don't see that there is a problem wit that. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpn7zTN3PXDh.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Wed, Apr 10, 2002 at 10:29:56AM +0200, Torsten Landschoff wrote: On Tue, Apr 09, 2002 at 10:40:41PM +0200, Jeroen Dekkers wrote: s/refused/discouraged/ and I would agree. Isn't the goal of Debian providing a free system so users don't have to run any non-free software anymore? IMHO the we support non-free software clause was I think this is one of the goals of Debian. And in cases where there is free software that works good enough I will use it. But sometimes there is only non-free software for a task or the non-free program is a lot better than the free one. I like thinking with my gonads. I just want to have freedom. In such cases I sometimes decide to run the non-free tool if it saves me some time. After all I want to get my job done and I want to have some time left for leisure or for working on stuff like free software. You restrict yourself to get some leisure. Don't complain that you are restricted from doing something afterways when it doesn't work anymore and you don't have leisure anymore. Like you I want other people to use free software as well because then I hope not being asked about those silly opaque problems in proprietary programs anymore. Please don't see you want it like me. I like it because of moral things, you just because you get some advantages of it. If non-free software give you (short-term) advantages then you even use that. I would never do that because free software is always better in the long term. But I am not going to attack anybody because he likes the proprietary stuff better, not even if it is extreme silly to do so. If somebody tells me about yet another Outlook problem I will just smirk and go on to the next email. Yes, and I will tell him why he has this problems and that there is some solutions for it (namely using a good, free MUA). You just let the person helpless, I try to point him to the fix. However if you try to help somebody you should not be a debian developers because you said that non-free software is the problem and you are not allowed to say that according to the social contract. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpGuPzDzbiX0.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 05:49:55PM -0400, Stephen Frost wrote: * Jeroen Dekkers ([EMAIL PROTECTED]) wrote: Isn't the goal of Debian providing a free system so users don't have to run any non-free software anymore? No, no, nonono, no, no, no. 4. Our Priorities are Our Users and Free Software I'm done. Me too. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpsOmDVNnnQk.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Thu, Apr 11, 2002 at 03:13:57PM +0200, Torsten Landschoff wrote: On Thu, Apr 11, 2002 at 01:02:54PM +0200, Jeroen Dekkers wrote: In such cases I sometimes decide to run the non-free tool if it saves me some time. After all I want to get my job done and I want to have some time left for leisure or for working on stuff like free software. You restrict yourself to get some leisure. Don't complain that you are restricted from doing something afterways when it doesn't work anymore and you don't have leisure anymore. That's fine with me. At least I'll have a lot more leisure when using an available product instead of re-inventing the wheel. Even RMS used commercial software when the GNU software for it was not yet written. With your logic he would have written the Hurd kernel and gcc, libc, etc. before using a computer. And of course he would have written it in machine language since there was no sufficiently versatile free C compiler available. Software always used to be free. That changed, but RMS didn't change. I don't what software he used to write parts of GNU, but it could have been free, there was enough free software at time. Oh, and 1) the Hurd isn't a kernel 2) RMS has never written anything of it AFAIK. Like you I want other people to use free software as well because then I hope not being asked about those silly opaque problems in proprietary programs anymore. Please don't see you want it like me. I like it because of moral things, you just because you get some advantages of it. If non-free Please don't tell me why I am using free software. I am using it mostly for moral reasons and this is why I am in the Debian project after all - I want to give back to the community. You just said that you wanted other people to use free software because you probably won't get any questions about non-free software anymore. I don't consider that a moral reason, but if you also have other reasons, I take that back. software give you (short-term) advantages then you even use that. I would never do that because free software is always better in the long term. So please don't boot your PC. Or do you have a free BIOS installed? No, because it's unavoidable to have a non-free BIOS, read just what I said. But I am not going to attack anybody because he likes the proprietary stuff better, not even if it is extreme silly to do so. If somebody tells me about yet another Outlook problem I will just smirk and go on to the next email. Yes, and I will tell him why he has this problems and that there is some solutions for it (namely using a good, free MUA). You just let the person helpless, I try to point him to the fix. However if you try to help somebody you should not be a debian developers because you You never tried to help somebody. I haven't? You are only projecting your view on other persons and taking their freedom away. Where did I take anybodies freedom away? Please don't pick random sentences and use them on me. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpEjUAI7iNGb.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Thu, Apr 11, 2002 at 10:46:12AM -0500, Steve Langasek wrote: On Thu, Apr 11, 2002 at 05:33:16PM +0200, Jeroen Dekkers wrote: Oh, and 1) the Hurd isn't a kernel Wonderful news! Does this mean that we can expect the 'whine-the-linux-kernel-packages-should-all-have-linux-in-the-name-/whine' thread to not repeat itself? No, as woody is not yet released. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpJ4RpJzhoLC.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 06:38:13PM -0300, Henrique de Moraes Holschuh wrote: On Tue, 09 Apr 2002, Jeroen Dekkers wrote: But does that mean they can posts question about problems with that non-free software which are not related to Debian at all (the only relation is that the user runs Debian) to debian-devel? No. However, this mess all started because the *wording* in your message was such that one got the clear impression that 'non-free' was the problem, and not that the fact that he posted to debian-devel instead of debian-user was. Non-free is the problem here. The question should actually be posted to a vmware list. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpeBQpfpjWS2.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 07:54:54PM -0500, Donald J Bindner wrote: Well, I didn't expect to inspire such a vibrant thread! A couple of responses (not in anger, just adding some perspective). 1) free vs. non-free alternatives I use VMWare 2.0. If you think that bochs and Plex86 aren't viable alternatives yet, you can imagine the state of the world (2 years ago today) when I bought my license. At that time VMWare was being praised for bringing Linux into places where it never before existed. That's actually true. We should fix the free alternatives. :) I have since felt slightly cajoled by the company to buy upgrades that I didn't feel that I needed, and I resisted. I am content with what I have, and satisfied to wait until a free alternative becomes viable. When I can start Plex86, drop in a Windows NT install disk (or any other OS for that matter) and install a system from scratch, I will be pleased to do it. I am in the end a free software zealot. Yes, it was actually your own fault, but the problem is that there doesn't exist a good free alternative. There are a lot of outstanding plex86 patches and somebody from an university had interest in plex86. The project isn't dead and I hope you can happily run plex86 within a couple of months. And it won't have this kind of problems and it would just be possible to apt-get install plex86. :) 2) posting to ddevel I posted to ddevel for a few reason (perhaps in error, and I'm willing to concede that). - I read the list, and I have for a long time (so I don't actually need to be Cc:ed). - I was continuing a previous thread. The level seemed to be of a technical nature and relevant to the list. My question wasn't really of the user variety (how do I configure a fire wall, how do ... in dselect, etc.). Actual my point was that you should ask vmware for the patch, we can't provide it because it's non-free software. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpUKOVyxT1yu.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 07:49:49AM -0500, Steve Langasek wrote: On Tue, Apr 09, 2002 at 10:37:31AM +0200, Peter Mathiasson wrote: On Mon, Apr 08, 2002 at 11:47:42PM +0200, Jeroen Dekkers wrote: It's your own fault. You choosed to run non-free software, now you get the consequences. Debian doesn't support vmware, so go somewhere else with your vmware problems. (Debian does support plex86 and bochs, BTW) *sigh* Do you always need to repeat this? Do you really think it's a waste of bandwidth and processing power to let the vmware users discuss a problem caused by a change in _Debian_? Even though I haven't tried plex86 and bochs in about a year I've never heard anyone run Windows XP, FreeBSD, etc on any of them. Is it at all possible? Useable? Since when are Hurd fanatics concerned with minor details like usability and productivity? I've always been, so do all other Hurd developers AFAIK. Why do you think we don't care about usability and productivity? Or do you just like spreading lies? It's actually the other way around, almost all recent development in the Hurd is to make it more usable. AFAIK the Hurd developers always have been very productive. We never cared much about speed etc, because we are more concerned about usability and productivity. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgp1HmaFa9qgU.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 10:37:31AM +0200, Peter Mathiasson wrote: On Mon, Apr 08, 2002 at 11:47:42PM +0200, Jeroen Dekkers wrote: It's your own fault. You choosed to run non-free software, now you get the consequences. Debian doesn't support vmware, so go somewhere else with your vmware problems. (Debian does support plex86 and bochs, BTW) *sigh* Do you always need to repeat this? Yes. Do you really think it's a waste of bandwidth and processing power to let the vmware users discuss a problem caused by a change in _Debian_? First of all this isn't a Debian-specific change but a change in glibc. Second vmware isn't Debian. Third Debian goes about free software, vmware isn't. This is clearly the wrong list, either go to some vmware list or go to the glibc lists if you think it's a bug in glibc. And yes, I think vmware is a waste of processing power and bandwith. Those posts also waste my time. Even though I haven't tried plex86 and bochs in about a year I've never heard anyone run Windows XP, FreeBSD, etc on any of them. Is it at all possible? Useable? I got GNU/Linux to boot on plex86. The Hurd doesn't work on it at the moment (plex86 development is a bit stalled at the moment). IMHO it's very usable, bochs is more stable but slower. For all supported systems read the documentation of the packages. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpZ7c6Pu8ykD.pgp Description: PGP signature
Re: Debian's problems, Debian's future
On Tue, Apr 09, 2002 at 09:09:39AM +0200, Michael Bramer wrote: hello we sould stop this and start after woody again... On Thu, Mar 28, 2002 at 08:17:46PM +0100, Jeroen Dekkers wrote: On Thu, Mar 28, 2002 at 04:55:17PM +0100, Otto Wyss wrote: Sorry, diffs are simply silly! Use rsync with the uncompressed Packages file and diffs aren't necessary. Or use a packer which doesn't hinder rsync from saving (gzip --rsyncable). This isn't server friendly. no. sorry. I must say this: We can use rsync on the client site. - get a rsync-checksum file (use a fix block size) - make the check on the client site and - download the file partly per ftp/http - make the new file with the old and downloaded parts With this the server need only extra rsync-checksum files. IMHO it's better to make just diffs instead of extra rsync-checksum files and then having to download all parts of those files. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpmOLJmDBDJh.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 11:10:20AM -0400, Stephen Frost wrote: * Jeroen Dekkers ([EMAIL PROTECTED]) wrote: And yes, I think vmware is a waste of processing power and bandwith. Those posts also waste my time. Filtering them out would save you more time, bandwidth and processing power than replying in the manner you do. If your concern is with bandwidth, processing power and time then deleting based on a subject filter of 'vmware' would be the best solution. That isn't my biggest concern. If you'd rather waste more of your time, bandwidth and processing power then continue to reply to posts which talk about vmware, or Oracle or any number of non-free-software that people use. I don't think that advocating free software is a waste of those things. I seriously doubt there is anything which could be done to stop the posts from being sent here short of moderating the list and having a moderator who thinks they shouldn't be here. I don't think the list should be moderated myself, nor do I feel the posts are inappropriate. I don't think it's wrong saying that if they want to keep using their favourite non-free software they should post to some other mailinglist and that if they want help from Debian they should use free alternatives which are in Debian. (Well, somebody thought saying that is such a bad thing that he asked DAM to put my application on hold.) Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpJoziPUi0oc.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Wed, Apr 10, 2002 at 01:31:35AM +1000, Anthony Towns wrote: On Tue, Apr 09, 2002 at 04:30:54PM +0200, Jeroen Dekkers wrote: Do you really think it's a waste of bandwidth and processing power to let the vmware users discuss a problem caused by a change in _Debian_? First of all this isn't a Debian-specific change but a change in glibc. Second vmware isn't Debian. Third Debian goes about free software, vmware isn't. Fourth, we support the use of non-free software, and we provide infrastructure (such as our mailing lists) for non-free software packages. Vmware isn't even in Debian. This is truely a problem of vmware itself. IMHO this isn't something for debian-devel. Or do you want to make debian-devel a list where all Debian users can come with their problems running buggy non-free software? If you don't agree with Debian's social contract, perhaps you should be part of a project that's more philosophically acceptable to you. I agreed with the social contract, but I think it should be changed. Some parts are just wrong, other things are confusing. To talk about the social contract, our priorities are free software and our users. Somebody is having problems with non-free software. What is wrong with telling him that the kind of problems he's having is normal with non-free software and say that there are 2 free alternatives in Debian which would probably not have those problems? Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpQ32X6qRe7Y.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 11:46:33AM -0400, Stephen Frost wrote: * Jeroen Dekkers ([EMAIL PROTECTED]) wrote: That isn't my biggest concern. Apparently. This implies, of course, that the additional bandwidth due to those messages isn't the real problem. I never claimed that. I was asked if I considered those messages a waste of bandwith, I said that I think it's waste. Is it just so difficult to *read*? I don't think it's wrong saying that if they want to keep using their favourite non-free software they should post to some other mailinglist and that if they want help from Debian they should use free alternatives which are in Debian. I don't believe it's wrong to ask questions on a debian list when a change in debian causes a change in some application, be it a part of Debian or not. The answer was already given, it was a vmware-specific problem. I do think it's wrong to tell people to not ask questions on a debian list about a change in Debian. The question I replied to was truely vmware-specific. The guy I replied to doesn't make such a problem of my mail than almost anyone else on the list. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpiEVQyOQIDO.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 05:34:35PM +0200, Peter Mathiasson wrote: On Tue, Apr 09, 2002 at 04:30:54PM +0200, Jeroen Dekkers wrote: First of all this isn't a Debian-specific change but a change in glibc. Second vmware isn't Debian. Third Debian goes about free software, vmware isn't. This is clearly the wrong list, either go to some vmware list or go to the glibc lists if you think it's a bug in glibc. Okay. So now we're not going to discuss things because they are not debian specific? No. Even though I haven't tried plex86 and bochs in about a year I've never heard anyone run Windows XP, FreeBSD, etc on any of them. Is it at all possible? Useable? I got GNU/Linux to boot on plex86. The Hurd doesn't work on it at the moment (plex86 development is a bit stalled at the moment). IMHO it's very usable, bochs is more stable but slower. For all supported systems read the documentation of the packages. plex86 is Debian specific isn't it? Because, if it's not, I'm sure plex86 got some mailing list where you can move this. True, but then other people don't know that I've answered his question and might answer his question too if they aren't subscribed to the plex86 list. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpxpvg7OeZ2r.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Mon, Apr 08, 2002 at 11:47:42PM +0200, Jeroen Dekkers wrote: It's your own fault. You choosed to run non-free software, now you get the consequences. Debian doesn't support vmware, so go somewhere else with your vmware problems. (Debian does support plex86 and bochs, BTW) As this might be a bit too offensive I apologize if you read it that way. Here is an alternative wording which says what I actually meant (I never try to write a mail quickly just before I got to bed): This problem is very common for non-free software. If you want to avoid such problems, you could try one of the free alternatives in Debian, plex86 and bochs. Those might have other problems (like being slower) but you probably won't have the same problems you're having now. We can also help you with problems you are having with plex86 and bochs. If you insist on using vmware, we can't help you, you should go to the vmware guys when you've got problems. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpXha1GWjo4L.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 01:21:49PM -0500, Colin Watson wrote: On Tue, Apr 09, 2002 at 07:29:14PM +0200, Jeroen Dekkers wrote: On Wed, Apr 10, 2002 at 01:31:35AM +1000, Anthony Towns wrote: On Tue, Apr 09, 2002 at 04:30:54PM +0200, Jeroen Dekkers wrote: First of all this isn't a Debian-specific change but a change in glibc. Second vmware isn't Debian. Third Debian goes about free software, vmware isn't. Fourth, we support the use of non-free software, and we provide infrastructure (such as our mailing lists) for non-free software packages. Vmware isn't even in Debian. This is truely a problem of vmware itself. IMHO this isn't something for debian-devel. Or do you want to make debian-devel a list where all Debian users can come with their problems running buggy non-free software? What if they turned out to be caused by bugs in our free software? Telling them to go away then would be foolish, since we want to know about bugs, no matter how they were caused. Apparently this breakage was caused by a change in glibc. As a general rule, changes in the C library should not break any software, whether free or non-free. Sometimes this is not the case (e.g. StarOffice's use of private glibc symbols a few years ago), but bugs should be investigated rather than casually dismissed. Did you *read* the thread? The cause of the problem was already found, it was a vmware bug, vmware already provided patches but not for the version Donald was using. You don't have to tell me how glibc works, I develop it. To talk about the social contract, our priorities are free software and our users. Somebody is having problems with non-free software. What is wrong with telling him that the kind of problems he's having is normal with non-free software and say that there are 2 free alternatives in Debian which would probably not have those problems? Because it runs the risk of hiding real problems. Given that he'd already tried the free software and found it unusable for his purposes, it also sounds like you need to pick better times to advocate free software, or else spend your time improving that software instead so that you have a better chance of being able to advocate it in the future. I agree that my reply was not very friendly, I apologized for that. I was actually a bit tired and very busy skimming through all my mails and replying too fast (I know it's not a reason to be unfriendly, but it was the cause). *That's* what debian-devel is about - a list for improving the technical quality of Debian. Turning it into advocacy and other non-technical debates is the very reason why many of our best developers don't even bother to subscribe to this list any more. I think that's also because of other things, see below. (In that spirit, please direct non-technical followups to debian-project or private mail.) (This is for the list in general, not personally to you) And let people just say false things without correcting it? Really, I already wrote a couple of replies telling people that they should read first what I've actually said or what the problem was. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpPjFa2kE3mD.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 02:13:25PM -0400, Stephen Frost wrote: * Jeroen Dekkers ([EMAIL PROTECTED]) wrote: I agreed with the social contract, but I think it should be changed. Some parts are just wrong, other things are confusing. That certainly looks like a contradiction to me. How do you agree with it if you feel it's wrong? By knowing the date it was written and what they actually meant instead of what they actually have written down. (For example, they meant non-free but they wrote commercial). And I'm not the only one, I know more Debian developers who don't really support non-free and would rather see it removed. To talk about the social contract, our priorities are free software and our users. Somebody is having problems with non-free software. What is wrong with telling him that the kind of problems he's having is normal with non-free software and say that there are 2 free alternatives in Debian which would probably not have those problems? Nothing is wrong with that. However, that isn't what you said. I did say it, although a bit unfriendly. * Jeroen Dekkers ([EMAIL PROTECTED]) wrote: It's your own fault. You choosed to run non-free software, now you get the consequences. Debian doesn't support vmware, so go somewhere else ^ with your vmware problems. (Debian does support plex86 and bochs, BTW) That's the original message you sent which *is* wrong. Debian supports its users regardless of if they run non-free software or not. In fact, we specifically support their running of non-free software and we provide infrastructure (such as our mailing lists) for them. Does Debian support vmware? So if Debian does support that, where is it written down that Debian supports every piece of non-free software? Of course you can say that in the social contract says Thus, although non-free software isn't a part of Debian, we support its use, but if I interpret that correctly, it just means the non-free software packages provided by Debian. And this actually my major complaint with the social contract, it's too vague to actually agree or disagree with it. I just interpretted it in the way I think was meant and agreed, because that is a lot easier than trying to change the social contract. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpAuRnjT9ebB.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 02:53:59PM -0400, Daniel Jacobowitz wrote: On Tue, Apr 09, 2002 at 08:25:47PM +0200, Jeroen Dekkers wrote: On Mon, Apr 08, 2002 at 11:47:42PM +0200, Jeroen Dekkers wrote: It's your own fault. You choosed to run non-free software, now you get the consequences. Debian doesn't support vmware, so go somewhere else with your vmware problems. (Debian does support plex86 and bochs, BTW) As this might be a bit too offensive I apologize if you read it that way. Here is an alternative wording which says what I actually meant (I never try to write a mail quickly just before I got to bed): This problem is very common for non-free software. If you want to avoid such problems, you could try one of the free alternatives in Debian, plex86 and bochs. Those might have other problems (like being slower) but you probably won't have the same problems you're having now. We can also help you with problems you are having with plex86 and bochs. If you insist on using vmware, we can't help you, you should go to the vmware guys when you've got problems. Have you ever tried to do any work beyond the boot process in plex86? Not really as I didn't got the Hurd beyond the boot process. It's unbearably slow. If I'm right the plex86 developers know why it's slow. I have a day job, as well as spending plenty of time doing other Debian work; it's not like I have time to sit down, spend hours beating on plex86 (it's a real pain to get going, I did it anyway!), and then spend months of my life making it faster. There is only one program in the caliber of VMWare, and that's VMWare itself. But if it doesn't work because there is a bug in VMWAre and it isn't fixed because the version it too old, we can't help those people who are running VMWare. You're perfectly free to not use it, but those of us who have to get work done are also perfectly free to use it - and Debian's Social Contract, as Anthony pointed out, says that we'll try to help people who need to do that. If I'm right, but correct me if I'm wrong, debian-devel isn't a mailinglist to ask questions about every random piece of software which runs on Debian. Plex86 is not an alternative to VMWare in any reasonable sense of the word. It is IMHO. Just like that GNU/Linux is an alternative to windows. (But it isn't even user-friendly, how could it ever be an alternative???) Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpi88eH6LRlt.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 04:20:38PM -0300, Ben Armstrong wrote: On Tue, Apr 09, 2002 at 08:25:47PM +0200, Jeroen Dekkers wrote: This problem is very common for non-free software. If you want to avoid such problems, you could try one of the free alternatives in Debian, plex86 and bochs. Those might have other problems (like being slower) but you probably won't have the same problems you're having now. We can also help you with problems you are having with plex86 and bochs. If you insist on using vmware, we can't help you, you should go to the vmware guys when you've got problems. s/we/I/i Okay. Suggest free alternatives, yes. Offer help for the free alternatives, yes. I did both. Blow off the non-free software user, no. If you have nothing to offer by way of help with vmware itself, then your silence will be enough to indicate that. And the user will never find out why he's having that problem. I don't think that not telling the user the cause of the problem is helping him. And our priorities are free software, but we aren't allowed with some respects free software is better than non-free software? And for that blow off, I already corrected that, right? Jeroen, I do not appreciate you speaking for the project in this way. Sorry, I will try to not give you the feeling that I speak for the project next time. As a member of the Debian project who believes firmly in the whole of our Social Contract, I cannot comprehend what makes you think you can throw about we can and we can't in blatant disregard for: We will support our users who develop and run non-free software on Debian ... The can't help means not being able to help you, because we can't fix any non-free software we aren't allowed to see and modify the source of. If you have personal problems with the Social Contract's allowing that our users may use non-free software, get it changed. And regardless, give a cordial answer to the non-free software user and lose the thinly-concealed hostility: If you insist on using ... you should go ... is dripping with it. Does the user insist? Have you evaluated his requirements? Do you know for certain that he's not turning to vmware as a last resort? Hmm, I knew somebody would find something to complain about in my second try to word my opinion. I'm not even going to try to do it a third time. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgp7S2XTNIrrc.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 08:11:59PM +0100, Colin Watson wrote: On Tue, Apr 09, 2002 at 08:45:16PM +0200, Jeroen Dekkers wrote: On Tue, Apr 09, 2002 at 01:21:49PM -0500, Colin Watson wrote: On Tue, Apr 09, 2002 at 07:29:14PM +0200, Jeroen Dekkers wrote: Vmware isn't even in Debian. This is truely a problem of vmware itself. IMHO this isn't something for debian-devel. Or do you want to make debian-devel a list where all Debian users can come with their problems running buggy non-free software? What if they turned out to be caused by bugs in our free software? Telling them to go away then would be foolish, since we want to know about bugs, no matter how they were caused. Apparently this breakage was caused by a change in glibc. As a general rule, changes in the C library should not break any software, whether free or non-free. Sometimes this is not the case (e.g. StarOffice's use of private glibc symbols a few years ago), but bugs should be investigated rather than casually dismissed. Did you *read* the thread? The cause of the problem was already found, it was a vmware bug, vmware already provided patches but not for the version Donald was using. I was rather under the impression that we were talking about any discussion of problems with non-free software, regardless of the cause. It certainly sounded that way to me. Well, if everybody just understood each other correctly, it would solve a lot of problems. However that's not the case. :( Even your improved reply says: This problem is very common for non-free software. ... which really doesn't seem all that relevant apart from sounding good; hell, the change in nice()'s return value appears to be a problem for start-stop-daemon in dpkg, see #141500, and a minor problem with X, see #140012. The nice() interface *did* change without versioning - it's true that programs that relied on the old behaviour were buggy, but there are plenty of such programs in Debian main and that is something Debian developers should be aware of. Patting ourselves on the back is great when it's justified, but I think it's somewhat counterproductive when it isn't. Now, it's true that one generally can't fix the non-free stuff when it breaks in this way, nor can Debian. But claiming that the *problem* is common in non-free software, implying that it is not common in free software, is simply not true. The actual problem was that he has an old version for which no patch exists. That problem doesn't occur with free software because 1) If it is in Debian the Debian maintainer would fix it 2) You've the freedom to fix it yourself or let somebody else fix it. Now this is actually one of the things free software is about, I just had to point that out and say there are free alternatives in Debian. I don't see anything wrong with that. Jeroen Dekkers -- Jabber supporter - http://www.jabber.org Jabber ID: [EMAIL PROTECTED] Debian GNU supporter - http://www.debian.org http://www.gnu.org IRC: [EMAIL PROTECTED] pgpxz5N4e5f2R.pgp Description: PGP signature
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 08:16:07PM +0100, Stephen Stafford wrote: On Tue, Apr 09, 2002 at 08:25:47PM +0200, Jeroen Dekkers wrote: On Mon, Apr 08, 2002 at 11:47:42PM +0200, Jeroen Dekkers wrote: It's your own fault. You choosed to run non-free software, now you get the consequences. Debian doesn't support vmware, so go somewhere else with your vmware problems. (Debian does support plex86 and bochs, BTW) As this might be a bit too offensive I apologize if you read it that way. Here is an alternative wording which says what I actually meant (I never try to write a mail quickly just before I got to bed): This problem is very common for non-free software. If you want to avoid such problems, you could try one of the free alternatives in Debian, plex86 and bochs. Those might have other problems (like being slower) but you probably won't have the same problems you're having now. We can also help you with problems you are having with plex86 and bochs. If you insist on using vmware, we can't help you, you should go to the vmware guys when you've got problems. mindless rant I think you totally miss the point. Free software is about choice. What you are saying is that it is okay for a library to change in a way that breaks software which I *choose* to run. The fact that software is non-free is irrelevant. I *choose* to run it. I made an informed choice. I looked at the alternatives, and made a decision. You look like you are wanting to remove my ability to make that choice. I just say the consequences of that choice, that is you're having problems with an old version and you don't have the freedom to fix that. From reading this thread, it looks to me almost as if you would advocate a system whereby Debian refused to run any non-free software at all. s/refused/discouraged/ and I would agree. Isn't the goal of Debian providing a free system so users don't have to run any non-free software anymore? IMHO the we support non-free software clause was only temporary, when there are free alternatives for the non-free software we could drop the support of non-free software. I feel the time has come to drop it. The free alternatives to VMware are not really all that good at all I am afraid. Development on plex86 has pretty much died since Kevin changed jobs. bochs was never really an alternative at all, its aims are somewhat different. True, but plex86 development is going to continue, subscribe to the list if you want to get informed on everything. VMware might be non-free, but it is damn good. I think for the price of a license you can better buy a nice second-hand computer. I'm sure that will a damn bit better!! (I actually use this method, with an old computer I got for free beer) When a libc6 change breaks it, then asking why is not *ever* a bad thing. Expecting changes in libc6 to not break things is sensible. If it does break stuff then we should look at why. We looked at it. We saw it wasn't libc's fault. If it turns out that the breakage is unavoidable, or serves a greater good then fine. I don't really understand this case well enough to know if that is the case or not. The breakage is/was deemed necessary by the libc6 maintainer (presumably) and I tend towards trusting Ben's judgement. It's not really breakage, it's fixing a bug. The programs which now break were buggy, I don't see why there should be any support for that. Instead, the programs should get fixed. Your advocacy looks like so much wind and piss in all honesty. You do no favours either to yourself or to the free software movement by it. You look and sound like a rabid, unthinking, kneejerking moron. That is usually a description reserved for RMS :) I already said people compare me with RMS and I take it as a compliment. Actually, there are people who can work with me (Yes, really!), there are also enough people who can work with RMS. Personally I never worked with RMS or discussed with him, but I don't think I would have big problems with that. I never see why everybody just say that RMS and GNU are bad. Seriously examine what it is that you are saying. What it looks like to me (at least, probably others too) is You run non-free software, so fuck off, we hate you, we hate your mother, we hate your sister's cat. Go whinge to the people who made the non-free software, because they should have forseen when they wrote their software a couple of years ago that we were going to break it. This want not meant so, I already apologized about that. Do I have to do more? When I joined Debian I did so with the understanding that Our priorities are our users and free software. Free software is not served at all by your silly rants, and our users are definitely not served by firstly having the software they *choose* to run break, and secondly being insulted and belittled by you for making that choice. True, the best way would have been
Re: sid: libc6-2.2.5-4 kills vmware workstation 3.0
On Tue, Apr 09, 2002 at 04:30:12PM -0400, Stephen Frost wrote: * Jeroen Dekkers ([EMAIL PROTECTED]) wrote: By knowing the date it was written and what they actually meant instead of what they actually have written down. (For example, they meant non-free but they wrote commercial). And I'm not the only one, I know more Debian developers who don't really support non-free and would rather see it removed. We can all claim to know the intent of the original authors but what they actually wrote down is what everyone who joins the project is asked to agree to. Developers are not asked Have you agreed with the intent of the authors of the Social Contract? because (in steps reality) no one really knows the intent of the original authors except (maybe) the original authors themselves (who, of course, may have disagreed with each other in their intent anyway). I merely seeing it as interpreting the contract. In some respects it's just too vague. There has been debate about that in the past, yes, though I think it's been more about the actual non-free ftp space and whatnot than about users being allowed to run non-free software on Debian and expecting to still be treated with respect and as a user of Debian. Users should be allowed to run non-free software, but Debian shouldn't much waste time and resources on it IMHO. We have to treat non-free users just as normal users, but they should not complain when their non-free software which is not in Debian is buggy. If you want the Social Contract changed then work on changing it. Do not act as if Debian follows your 'New Social Contract' instead of the existing one. You mislead people into thinking you're right when you're not. I merely interpret the social contract different. IMHO we are both not right or wrong, the social contract is just too vague. Indeed we should fix that, but I've got a lot of things on my TODO list. To talk about the social contract, our priorities are free software and our users. Somebody is having problems with non-free software. What is wrong with telling him that the kind of problems he's having is normal with non-free software and say that there are 2 free alternatives in Debian which would probably not have those problems? Nothing is wrong with that. However, that isn't what you said. I did say it, although a bit unfriendly. No, you said 'go somewhere else' to a Debian user asking a question about a Debian change which broke an application they used. Asking a question whether VMWare supports his version which wasn't the case. I said (in an not-so-friendly manner, I agree) that debian-devel isn't the correct place for that. That's quite different from saying there are 2 free alternatives in Debian or any of what else you claimed to have said above. I said there are plex86 and bochs, I said that in that mail and in some other mail in that thread. * Jeroen Dekkers ([EMAIL PROTECTED]) wrote: It's your own fault. You choosed to run non-free software, now you get the consequences. Debian doesn't support vmware, so go somewhere else ^ with your vmware problems. (Debian does support plex86 and bochs, BTW) That's the original message you sent which *is* wrong. Debian supports its users regardless of if they run non-free software or not. In fact, we specifically support their running of non-free software and we provide infrastructure (such as our mailing lists) for them. Does Debian support vmware? So if Debian does support that, where is it written down that Debian supports every piece of non-free software? Debian supports users running non-free software by way of allowing them to ask questions on our mailing lists and use our bug tracking system. So debian-devel is the mailing list where people can ask question about patches for non-free software which isn't in Debian? And can they also use the bug tracking system for that? I thought not, but maybe you can prove me wrong. At the same Debian is a volunteer organization and individual developers are not required to respond to questions they don't want to. And they are not allowed to state their opinion? And they are not allowed to tell the user what the cause of the problem actually is? IMHO, developers should do that. Of course you can say that in the social contract says Thus, although non-free software isn't a part of Debian, we support its use, but if I interpret that correctly, it just means the non-free software packages provided by Debian. And this actually my major complaint with the social contract, it's too vague to actually agree or disagree with it. I just interpretted it in the way I think was meant and agreed, because that is a lot easier than trying to change the social contract. Obviously you have some odd ideas about how to interpret that line. Debian specifically says non
