Accepted warzone2100 3.2.1-4 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 26 Jun 2019 06:49:41 +0200 Source: warzone2100 Architecture: source Version: 3.2.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Markus Koschany Closes: 930942 Changes: warzone2100 (3.2.1-4) unstable; urgency=medium . * Team upload. * Move the package to salsa.debian.org. * Fix segmentation fault upon multiplayer "Start Hosting Game" Thanks to Phil Morrell for the report and Bernhard Übelacker for the patch. (Closes: #930942) Checksums-Sha1: b0a6f238e711339400dd32d319e7b778382a605c 2681 warzone2100_3.2.1-4.dsc 639d726465d62ed3cde493d5efccbcc498877148 29096 warzone2100_3.2.1-4.debian.tar.xz dd11a9ceae19f6db4d8c6d7ee9508068d17611aa 16032 warzone2100_3.2.1-4_amd64.buildinfo Checksums-Sha256: 76c13733e0fae057c33e7b0750e8c6d0843550033bcf1927dcb09a5d310a0da5 2681 warzone2100_3.2.1-4.dsc 90c38b09c254944fb5366ece5cf60a43063976f533a38b9ffb8c29a46f5b5635 29096 warzone2100_3.2.1-4.debian.tar.xz bf410edfcc5727f5dcf8353685fc08c136d2577f6919fae146d45e82e1003659 16032 warzone2100_3.2.1-4_amd64.buildinfo Files: db11abf07852c4a66c7c530c8d46f3de 2681 games optional warzone2100_3.2.1-4.dsc ed7d349108d0697023fc5cd159844262 29096 games optional warzone2100_3.2.1-4.debian.tar.xz d407d81d1f9b666f39cb4e05057e2156 16032 games optional warzone2100_3.2.1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl0S+8RfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HkMV8P/3390yaelKyZ1ZD7Vrv9m9dDYWrziJb1aCr3 Rmf6mRGfbVaEx96zC5lKaxhTB8UudrwW8YouoR5m63Rh+fpypHByd87ZnAmsp928 AzgGQpeo3Dd0HFTsehUQBcxO7VWOJDvOJ02+VytYq/HTMZdDQXWZqcpvDv1GuN1u 9qIy0imK7ln2m+rixZ+HZhhF+pZ3Q4VqlfbkKUxG4OBcNxXKd3D7S0Xjjdu5n9t8 cMOaThaUf3RrXn7RbJr+XprO8MHoZ3YbBtmxO3T6c7jD8dF3myMrRej6+Z6SCoU9 744yThUgA4lW0QJ1p4WYveIYWeMlwLxUimb2406yKiQ7iEmiEwJDv+Qrjm7LbzsR OGInDPUV1R9rXdzoIrIUkkqsR7w53T5g0rzPad6G3nybkq61hMxGxoh38iJH6ACI fZvQmmJ1JxwllCRjWv3qsJjz6E8CMwuEAl+OF5aDQVjBokCWxt6uLGaKqSfzKaTa 3/m+CQgrRKAtJwovli6nHHq/CoxcuBdp2jmvD7HjjQuq+iWNVPYQD66mNd9smyCs TpFjldy1pMw71xXSTmOV/BMUfrWpedePhiTIWPD/rH0UMXfxFQRTwttzfDmfIXQ3 vyrY1e62NDMdwRzoqDbrXW91lbAHjNfHo7UqeLKbs2Ch+3lb3H2o2RXwzjm20KCQ 5MJs6sg6 =Adlu -END PGP SIGNATURE-
Accepted sl-modem 2.9.11~20110321-16 (source amd64 i386) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 17 Jun 2019 03:39:06 +0200 Source: sl-modem Binary: sl-modem-dkms sl-modem-daemon Architecture: source amd64 i386 Version: 2.9.11~20110321-16 Distribution: unstable Urgency: medium Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) Description: sl-modem-daemon - SmartLink software modem daemon sl-modem-dkms - SmartLink software modem driver - module building source Changes: sl-modem (2.9.11~20110321-16) unstable; urgency=medium . * Add fix-linux-5.0-ftbfs.diff patch from Ubuntu to fix FTBFS with Limux 5.0. Thanks to Seth Forshee (LP: #1818833) * Fix array overrun of st7554_table in st7554_open - fixes array bounds checking error of an index into the table. Thanks to Colin Ian King (LP: #1832718) Checksums-Sha1: 5492cffd92dc855ceeefcbd7bfbf5ae8765a4744 1871 sl-modem_2.9.11~20110321-16.dsc 9b580c9fa21d9698b216a788a4cb1180922c256b 36000 sl-modem_2.9.11~20110321-16.debian.tar.xz 819eee758c2bfdf6add509799cf1d31049e17e20 205724 sl-modem-dkms_2.9.11~20110321-16_amd64.deb c995b2c6d4194f449e5d9b964edbe3b3d1b4e439 468848 sl-modem-daemon_2.9.11~20110321-16_i386.deb a9754da9932521f8d15afdca867939357adcd401 206032 sl-modem-dkms_2.9.11~20110321-16_i386.deb d6869b325324602a7c4471af3e8f262cce0ebb03 4682 sl-modem_2.9.11~20110321-16_amd64.buildinfo Checksums-Sha256: 0433a1862f541a9b7c32e0935a80a193bb57c406f4c475e4d4e65aa9659e0a28 1871 sl-modem_2.9.11~20110321-16.dsc 35cdac1c004eff93d1147047d4d863cd49f0ef24111bdf53c5b88c2d6faaac96 36000 sl-modem_2.9.11~20110321-16.debian.tar.xz 7cdd15089540acc9c36a91d0b4991cf43041ba89a51df39e112717edb84afac5 205724 sl-modem-dkms_2.9.11~20110321-16_amd64.deb 2d8c31e05f78417fb2c3025eddb3501ee01e295c2053590f781d788ee2ab7c9c 468848 sl-modem-daemon_2.9.11~20110321-16_i386.deb cd82d1196ce7fb74a8097cdccc599ba5f39539017660ce635eb937016018ae3e 206032 sl-modem-dkms_2.9.11~20110321-16_i386.deb 8cbcec6be734eda25bc5f5bd93b2759aefda21263da9de82591fb4dee459fea9 4682 sl-modem_2.9.11~20110321-16_amd64.buildinfo Files: 50c64b999e2a186960d5304c38b93f76 1871 non-free/misc optional sl-modem_2.9.11~20110321-16.dsc 682553df8e7b3a0d8a336fbe34ae6262 36000 non-free/misc optional sl-modem_2.9.11~20110321-16.debian.tar.xz 2b917129d80c87af978a8230bb0efd8f 205724 non-free/kernel optional sl-modem-dkms_2.9.11~20110321-16_amd64.deb 8906b3c03ab6e911b49c96304ddd28f9 468848 non-free/misc optional sl-modem-daemon_2.9.11~20110321-16_i386.deb bbf8e6d767ddcf4b901b4621dce4e99a 206032 non-free/kernel optional sl-modem-dkms_2.9.11~20110321-16_i386.deb 56a5f68ca01cb72da42477fc01263a3e 4682 non-free/misc optional sl-modem_2.9.11~20110321-16_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEcBAEBCgAGBQJdEtxHAAoJELwZapTt3aG3dYYH/3wTds9Zix+bq0qpcvj9S0J7 hAZ6ZViNZ4A36EBkbL+3Zq/ATgrC7H7gug2SJFNm0Mhkcawe9A7qt+6hWRk2XcTJ EKQ9cWXGgge6ZV1KagOkC9dHWsFNPia2BlnsRgvMfQbFCnP2/N7lrZzyXxdABwoP YDkwk/NaTxjPL6yjnfo029lLhuh4ncWQfFvFEg1QSsWtnC9zfbFOV3Lhi5oqNb9m PkzMgceU9F4+YlqSaLpw63AXj34tzAd1JiNc+nZomE5cFfhRwGtioV3+cne67GmY eVfBI2qJITOD3koO4KbHYje4Mi0f9xgG8uPxmztgh2lblBiIBIH0tCQJtnotWjc= =zLrL -END PGP SIGNATURE-
Re: Re: Content Rating System in Debian
Emmanuel Arias: IMO this idea represent a big work. And if you want to involved upstream, maybe will be a problem. Some upstream, could not be interest on participate because could be a "extra" work. But if we implement a content rating system, the freedom could be affected because the opinion on a package may be affected by this new system. Regarding freedom, yes it can be affected by CRS because CRS can limit freedom to use programs for some users (particularly non-adults). But CRS limit such freedom in order to protect psychology users for long term from negative impacts of programs they used.
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 4:39 PM Paul Wise wrote:
> On Tue, Jun 25, 2019 at 2:08 PM Ansgar wrote:
>
> > what do people think about getting rid of current suite names ("stable",
> > "testing", "unstable") for most purposes? We already recommend using
> > codenames instead as those don't change their meaning when a new release
> > happens.
>
> I use these (testing, etc) so getting rid of them would be annoying.
I also should mention that I use all of stable stable-updates
proposed-updates and the equivalents for old/oldold. I have them in
the apt sources of a chdist so I can easily look up old versions, do
apt-file searches on old versions, look up non-amd64 architecture info
etc.
I would also love to have stable-backports be a thing, so I don't have
to change my chdist apt sources from codename1-backports to
codename2-backports every time a release happens.
I use chdist for when I'm offline or when I want to see what is on the
mirrors, since rmadison shows the ftp-master view.
PS: apt-venv is another option for this use-case.
--
bye,
pabs
https://wiki.debian.org/PaulWise
Accepted libpaper 1.1.28 (source amd64) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Jun 2019 00:04:32 +0200 Source: libpaper Binary: libpaper-dev libpaper-utils libpaper-utils-dbgsym libpaper1 libpaper1-dbgsym Architecture: source amd64 Version: 1.1.28 Distribution: unstable Urgency: medium Maintainer: Giuseppe Sacco Changed-By: Giuseppe Sacco Description: libpaper-dev - library for handling paper characteristics (development files) libpaper-utils - library for handling paper characteristics (utilities) libpaper1 - library for handling paper characteristics Changes: libpaper (1.1.28) unstable; urgency=medium . * Completely fixed #927226. Checksums-Sha1: 08b46cd6fdaf39f141b1bf0053609af54fece6f3 1633 libpaper_1.1.28.dsc c6583fbdaebe091d11d81c4e59514e58996f22ba 42356 libpaper_1.1.28.tar.gz cd4aa90244b420569c4d7c198a949c475a7a5413 17412 libpaper-dev_1.1.28_amd64.deb de984f4e13d7177cac1f5994e575d2f0385cd56f 7752 libpaper-utils-dbgsym_1.1.28_amd64.deb 510f961b88b32b6f6ea191bc98fae1b066a0f793 18036 libpaper-utils_1.1.28_amd64.deb d324cc5e81baba15670ef6d06b3d01c1bf8fc543 8536 libpaper1-dbgsym_1.1.28_amd64.deb 731a64cf53f18a44242eb081ad92841195f78cf2 21324 libpaper1_1.1.28_amd64.deb 76b9c012345c6a148e66172fa30683b7229e8f26 6619 libpaper_1.1.28_amd64.buildinfo Checksums-Sha256: 298d6347d84ece2f55088e371facc13362c8f4731d80f94c6ad84190309de8b4 1633 libpaper_1.1.28.dsc c8bb946ec93d3c2c72bbb1d7257e90172a22a44a07a07fb6b802a5bb2c95fddc 42356 libpaper_1.1.28.tar.gz fa171427f5e3b4af5caa370ff3d041063e3fa1830220b4ca6205189566be8ae8 17412 libpaper-dev_1.1.28_amd64.deb 44bcc213c1d774800459e05d05e75d632b9531013fee0eb5aae6626aa48b8341 7752 libpaper-utils-dbgsym_1.1.28_amd64.deb 1af340992b4423c95538de62e5502cba260033901bbe9537c21f6e912f273eb1 18036 libpaper-utils_1.1.28_amd64.deb 81a667650c606aaf3803aea501583b55f2bdde5acb872e630346f0fd092953dc 8536 libpaper1-dbgsym_1.1.28_amd64.deb 07382f756322e4993967c4e4f675c5724805a25cd483ee541a25d7ea3c9ba45a 21324 libpaper1_1.1.28_amd64.deb 4af912c63255ca1407a87309e157ca0d248e4f529642c8c32870b0a16267f50e 6619 libpaper_1.1.28_amd64.buildinfo Files: d18798f0f5cc27812028371aae07fb26 1633 libs optional libpaper_1.1.28.dsc 58dcdb3e1074f571b86d0ee937ed0072 42356 libs optional libpaper_1.1.28.tar.gz 18be0284a2446739a4493b128906024c 17412 libdevel optional libpaper-dev_1.1.28_amd64.deb 519e5535ac771da5fc556d473c7f243d 7752 debug optional libpaper-utils-dbgsym_1.1.28_amd64.deb db072b8e670a7a560e07ef9d6a7cba57 18036 utils optional libpaper-utils_1.1.28_amd64.deb 7aeb1b65d62ddba13ff16341f7312c44 8536 debug optional libpaper1-dbgsym_1.1.28_amd64.deb 204503595bc6bc33a2b359a7202d4d82 21324 libs optional libpaper1_1.1.28_amd64.deb 90815400cfdff78c9609e069c4f43851 6619 libs optional libpaper_1.1.28_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEUVOdP2LoUi7Qx8Bwwq7bFEft0yEFAl0SmrkUHGVwcGVzdWln QGRlYmlhbi5vcmcACgkQwq7bFEft0yERuQ//X4+k7r1h3QCCLueVRxFe+M4jSRqC vpznxPKtVwX0mpY4tR7xracGxumHSc/FCYrxXSncnc0Gr6iMU8JKLkSX2DQLqTlc CRePjxr2DwY1/dwaOrqW/1Def7YD1zWHdHr4nLrQBWVfXisK/kYbsyxT9A0k1PZB 794clpyJ17+QcuPfkwxEHiXjUUpNPvFy7QxUPrg5EKstGxx5xeeCsj5hPa1wO64Q 6ENjcNGJswatoMrf54dPp5/NUiYczSspus+FzzEtNSOas/Zkwal2baHTaDR40+9j Alg5/5XdIw8vt1IvSKrSfx4MjbpfCXwTG8ul/TCKdJ8VEJqvXWlP9v+RkLZ/axfE pZqxmC9TAfwLLAqAI2bmerCg47y0hSZCOLsvAorwlntjvWlRNPIl2KqXLQ8jWDTE af5id/7itoXYdq/uPIdSJMbjziu/JNhSXU6huRMunz7+9++Mv7bXrf5qf9E6kbGm 1p57PALph2ovA7vEKg32OthDXnpS1DWMccX84wKRvmJO5uLnxJ7FU8UAyosPlyUJ qFlZc322GsuutVfDUrr9sO7YJakK8hKNBFHiThivuJ4utaRl2fRGLoBgHaGOwoVA OKInU1/AfJ3a2hLG39of2/EACJLy41Ur41r+T2ar3IxQgCweneQzd3gc5QdidrTW +0vbH3ZHhIChlDo= =TbQr -END PGP SIGNATURE-
Accepted igtf-policy-bundle 1.101-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 17 Jun 2019 16:38:17 +0200 Source: igtf-policy-bundle Binary: igtf-policy-classic igtf-policy-mics igtf-policy-slcs igtf-policy-iota igtf-policy-unaccredited igtf-policy-experimental Architecture: source all Version: 1.101-1 Distribution: unstable Urgency: medium Maintainer: Dennis van Dok Changed-By: Dennis van Dok Description: igtf-policy-classic - IGTF classic profile for Certificate Authorities igtf-policy-experimental - IGTF experimental Certificate Authorities igtf-policy-iota - IGTF IOTA profile for Certificate Authorities igtf-policy-mics - IGTF MICS profile for Certificate Authorities igtf-policy-slcs - IGTF SLCS profile for Certificate Authorities igtf-policy-unaccredited - IGTF unaccredited Certificate Authorities Changes: igtf-policy-bundle (1.101-1) unstable; urgency=medium . * New upstream release: * [Changes from 1.99 to 1.101 (24 June 2019, note: 1.100 was not issued)] - added new trust anchor for PolishGrid (2019) for key roll-over (PL) - withdrawn discontinued CILogon OSG CA (US) * [Changes from 1.98 to 1.99 (27 May 2019)] - withdrawn superseded HKU CA (HK) - withdrawn discontinued CyGrid CA following migration to TCS (CY) Checksums-Sha1: 36e46789c4646f004f934ad484c61eeb154c138e 2576 igtf-policy-bundle_1.101-1.dsc 3205d8e9085002c4e2f629f2a44e156f9ba29248 177048 igtf-policy-bundle_1.101.orig.tar.gz 4dd20ca7e13b5f35694e9cbb86b52337ef1c8bb5 198 igtf-policy-bundle_1.101.orig.tar.gz.asc 68eb515123c7142d0cf8cd8a8c8dad4e606f5890 31372 igtf-policy-bundle_1.101-1.debian.tar.xz 36956faebe46e472b1a127b28448baa8d2a2e336 7802 igtf-policy-bundle_1.101-1_amd64.buildinfo 600c1aacc188616b6b2a94c682a14e72cfa3e2c6 166024 igtf-policy-classic_1.101-1_all.deb ad0ad06fccbd6aca492ddd4467d3c83093da41a2 38070 igtf-policy-experimental_1.101-1_all.deb 0cdb0a098787ba0636f04c9feed76fd142f7fbef 50492 igtf-policy-iota_1.101-1_all.deb bca2d115f31a46976f3674aab3b55363cf0e9bd2 49390 igtf-policy-mics_1.101-1_all.deb 8c424dfbce052f11282cf5f37ce547d9e94c4712 50438 igtf-policy-slcs_1.101-1_all.deb 6859824fc429a0b55cd127c10fa6c475c2acd2f7 43298 igtf-policy-unaccredited_1.101-1_all.deb Checksums-Sha256: acaad386fb8dd70c01e1dee27257b63ca24e9642cebeb460210d46ee2c527c2e 2576 igtf-policy-bundle_1.101-1.dsc 311eab746d71d284cc20f573c082032c15bd53c9862e874de2fb2642c11aa38d 177048 igtf-policy-bundle_1.101.orig.tar.gz 48ea5e1c588d03a03224395049d6cb704fe4318ac92de4075650ec30e5f02794 198 igtf-policy-bundle_1.101.orig.tar.gz.asc ea9301fc15baf850d28c42afc7aecb7c7f524ee8bb8000f97af6f991183b4340 31372 igtf-policy-bundle_1.101-1.debian.tar.xz 4e4ee9ef39550e6b2fdaa612c3cfa7aca84865b82fa37d5954477dc9bdb15837 7802 igtf-policy-bundle_1.101-1_amd64.buildinfo 1c398f6117b2586409feff03c6c3cda2dcf6ebe9dad9d91e0b0de33b544ce267 166024 igtf-policy-classic_1.101-1_all.deb f8c4b11c55999768177a68fb58c0f2956a3e793acc07ba34dcfbdbb5ccc74d26 38070 igtf-policy-experimental_1.101-1_all.deb e87c66c721f6b1fdda427c2aab0466d0d6917cb57b111c2d37f3ea1158b2c334 50492 igtf-policy-iota_1.101-1_all.deb c413c856a41801c72178ed5ce5000347f8d3c4121bad88524bbc59fb67a373ab 49390 igtf-policy-mics_1.101-1_all.deb d4fffc29b63f5a3c433eecb72e677da8cfcd6356c411331bc5561a49883e4f1f 50438 igtf-policy-slcs_1.101-1_all.deb 2278e249ca634e125f2cab910901bb2f2fbaebf30c08518bca07b7f6940090ab 43298 igtf-policy-unaccredited_1.101-1_all.deb Files: 0ca6b21d5dc647defca35c7a73397a37 2576 misc optional igtf-policy-bundle_1.101-1.dsc 63567b0c5ca1cc2ef1900905f3fafa99 177048 misc optional igtf-policy-bundle_1.101.orig.tar.gz 097d22d33ac3a83f08cf84711eae7952 198 misc optional igtf-policy-bundle_1.101.orig.tar.gz.asc ac93670684e476e2135984ae611dcb82 31372 misc optional igtf-policy-bundle_1.101-1.debian.tar.xz 6cc979f466e3ccbf67dba7c336f8850e 7802 misc optional igtf-policy-bundle_1.101-1_amd64.buildinfo 99f00a0db63a00d48f3039bc253714a8 166024 misc optional igtf-policy-classic_1.101-1_all.deb 2109319268e86f5353b6b66c299974fd 38070 misc optional igtf-policy-experimental_1.101-1_all.deb ee348fbfae8af13b69325676ea8682f5 50492 misc optional igtf-policy-iota_1.101-1_all.deb a98355eaf8127666ae512aba46eee57b 49390 misc optional igtf-policy-mics_1.101-1_all.deb 9bcf36fe8ea48702e338c302a7547a19 50438 misc optional igtf-policy-slcs_1.101-1_all.deb 928d4cf7dfbf3b9686255b12023fa1b1 43298 misc optional igtf-policy-unaccredited_1.101-1_all.deb -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEhH6IIWnwOOANp8YabVMnw1/XsFYFAl0HppUTHGRlbm5pc3Zk QG5pa2hlZi5ubAAKCRBtUyfDX9ewVtxMD/0TuI3Ctza6yD0KqKqBS9G3pm6ew8BF PpSlKU4FUjEaW7pT/d9M7XV0iCNlPz3q0WmdJs8zXldd1msqx1VS0dIN60vERGBe TyObPOtyPkpPNJBzuz8/ZvAk76rhYW6LSi4yDDDWVpklEsULomtBDxNYegDXaUxv ygqJ6mzcNEbx0WX21bAR4OlnEV0neaPVBFCWswusIg8Mcjwdln+mOPicVMd4LSh6 BG6/1+E2a4PfliZEwn01ft/MDsqaCh8uktHJPDK+hpI5Un7PCSvLL0dosoXprHGp /zveKa3NritW5Cia+qHVUb0+dO2+lv/bX0L25ISPxGd5DdyA+gULDHcYsVu6Hio+
Accepted ocaml-flac 0.1.4-1~exp1 (source amd64) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jun 2019 23:10:15 +0200 Source: ocaml-flac Binary: libflac-ocaml libflac-ocaml-dbgsym libflac-ocaml-dev Architecture: source amd64 Version: 0.1.4-1~exp1 Distribution: experimental Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Kyle Robbertze Description: libflac-ocaml - OCaml interface to the flac library -- runtime files libflac-ocaml-dev - OCaml interface to the flac library -- development files Changes: ocaml-flac (0.1.4-1~exp1) experimental; urgency=medium . * New upstream version 0.1.4 * Bump standards-version (no change) Checksums-Sha1: d0c89991fbdf8562ffe1c443ef4f051b013b548e 2267 ocaml-flac_0.1.4-1~exp1.dsc 88379fa2a071ccec1a3c795a9f83f1f05e9ef6ab 125697 ocaml-flac_0.1.4.orig.tar.gz 63fbece9e1bc7617a4a090c441db2435110c2c68 2872 ocaml-flac_0.1.4-1~exp1.debian.tar.xz a360be81780c4b3ce7e0fe9618e7ed7be668717e 33468 libflac-ocaml-dbgsym_0.1.4-1~exp1_amd64.deb f0a89ee2a3abd999a0d05a798b78c0e94f2296d2 76924 libflac-ocaml-dev_0.1.4-1~exp1_amd64.deb 7ae64fd2ac028a3f653a96464d05d04993d33acb 15448 libflac-ocaml_0.1.4-1~exp1_amd64.deb 716ed8f66d7805795a4bc9950a3c082d59581ccc 6392 ocaml-flac_0.1.4-1~exp1_amd64.buildinfo Checksums-Sha256: 45e2a878c5b9478546342436c757a1997d6ce4b590f9b285254b0f5249803a9f 2267 ocaml-flac_0.1.4-1~exp1.dsc a863ce4d368dc30a6544aeabb9d7c4ee8fcc89f4e8e1e6ffbc3ae3e21358212e 125697 ocaml-flac_0.1.4.orig.tar.gz 668b668d7a9f2ad9471ea73063177e361cbcae6ddc3a443df0c239ed8b0e9f20 2872 ocaml-flac_0.1.4-1~exp1.debian.tar.xz 8e7aab8acd1cb40ddac3aec83adc1e7e88b1b62e251b42a2aa04ff82734e6763 33468 libflac-ocaml-dbgsym_0.1.4-1~exp1_amd64.deb 593c3082732cc1fef05a8ce75ec553b7e18fcc8f15c20b4f57887b8753363360 76924 libflac-ocaml-dev_0.1.4-1~exp1_amd64.deb 670d12a3e5b13855ab8a1894dca05c851a704fd14748cb09b389bbce266c9513 15448 libflac-ocaml_0.1.4-1~exp1_amd64.deb aebabb2e5c599899ed72c1181bc74f83c3414e6bf92e5830d962fdf88292b065 6392 ocaml-flac_0.1.4-1~exp1_amd64.buildinfo Files: 21db62189fc083b22371398a7f8f0a85 2267 ocaml optional ocaml-flac_0.1.4-1~exp1.dsc 6c2850088e927cfacdb2940792fe2e67 125697 ocaml optional ocaml-flac_0.1.4.orig.tar.gz b5585a337cc57f9a9d1f05dd2a825a8b 2872 ocaml optional ocaml-flac_0.1.4-1~exp1.debian.tar.xz 60163533a1ae95a9bcc4e2d9099206a2 33468 debug optional libflac-ocaml-dbgsym_0.1.4-1~exp1_amd64.deb f4a19c8877c2587b7cab703db02993d3 76924 ocaml optional libflac-ocaml-dev_0.1.4-1~exp1_amd64.deb e1e251a1dcbffe9f07195f018c269229 15448 ocaml optional libflac-ocaml_0.1.4-1~exp1_amd64.deb a98accf0034e54374c53ffb07f03c232 6392 ocaml optional ocaml-flac_0.1.4-1~exp1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJMBAEBCgA2FiEElqWPGCu4+bgcXyczhU8Hvggt8U8FAl0Sks8YHHBhZGRhdHJh cHBlckBkZWJpYW4ub3JnAAoJEIVPB74ILfFPYUUP/jwQzWK/qq0Qk97WaNamU2NM b1xO+x/lwmei0rmLy3g+RvEZ1vFG+LubPOuD5/0YcdgPOfA8Qh4gTnQOA2wltsWO lvHLVrfFYmbH5m38E+ruB3PHJXzpuFo8BmIrD6EXyXJHYJumY+wNecfj/7XJ6Fsq ZtN2nbAv6vIVtWPkzEP83XOYxMsQr9MahS5Hytht/a/dwmqjNqrXyPUYDmvDh7Qx cmEj7ce7CJu1sS9SFji+nm/UgRPA8gqFRf6sXjTvnKq7I9i1pHU9wfSainY1sqp9 SOo2bKOD2S2bde+lU8NvMlpZCR3ew2Oj+AZaE8qgpX/wpYeqzUNnsP9nBpEgD87A fLH1O9HVWb5t6CVZLpAHK+vDLv4hMQXl1il80dqVbRbWEr9MmNbWzkmYzDCsf6Xe 7CKbXXXh6n3JhdMFGcTlIEikwsz0q8M61crJJJzJEPu8DYGLvFwwu30f7NSxSY0L kfedOGsPpwJmRByJCQpCN2gvtM/RMaGRfu/sg/s7+b4xF/++nh3KC/3WJGbiuyNH u6HnSFIHYcw8TtUqkpxFW/dk4+kCm6J0RjYCSh1C8+apEED1fNy14XNOuhyZ5I1q WVvubgXArty/eLO+NLuTzkV6/BHY62h0HKisoHP6eK3o/fcdE1mQye4YLm1YJahl M1LpZjmKYXm8TbNe/0pB =Dqmr -END PGP SIGNATURE-
Bug#931089: ITP: ocaml-ffmpeg -- OCaml interface for FFmpeg
Package: wnpp Severity: wishlist Owner: Kyle Robbertze * Package name: ocaml-ffmpeg Version : 0.2.1 Upstream Author : Savonet Team * URL : https://github.com/savonet/ocaml-ffmpeg * License : LGPL Programming Lang: OCaml Description : OCaml interface for FFmpeg The modules currently available are: Av: the module containing demuxers and muxers for reading and writing multimedia container formats. Avcodec: the module containing decoders and encoders for audio, video and subtitle codecs. Swresample: the module performing audio resampling, rematrixing and sample format conversion operations. Swscale: the module performing image scaling and color space/pixel format conversion operations. Avdevice: the module containing input and output devices for grabbing from and rendering to many common multimedia input/output software frameworks. This is a dependency of the new version of Liquidsoap and will be maintained as part of the Ocaml Maintainers team.
Accepted php-phpseclib 2.0.20-1 (source) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jun 2019 07:40:50 -1000 Source: php-phpseclib Architecture: source Version: 2.0.20-1 Distribution: experimental Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: David Prévot Changes: php-phpseclib (2.0.20-1) experimental; urgency=medium . [ Remi Collet ] * fix compat with 5.3 Checksums-Sha1: 56961f76412b02c8465b9b8e22308ac50b98b22d 1802 php-phpseclib_2.0.20-1.dsc 285cb38395e1f173ef0b6c375e4d04218ae7b8f4 326883 php-phpseclib_2.0.20.orig.tar.gz 2c1f9d79c1a717d4afe2f845a704d1381d6a075a 7156 php-phpseclib_2.0.20-1.debian.tar.xz 748eac0850b7c66aa0aaccaad5b105acfe27c476 6882 php-phpseclib_2.0.20-1_amd64.buildinfo Checksums-Sha256: 1de516a731b88549de8f72abe5123a48f52ac33980c90730f18e726f22b62882 1802 php-phpseclib_2.0.20-1.dsc f4ef63485d3bf250479457105e2e490e694589b694394477837fc503d4d715ef 326883 php-phpseclib_2.0.20.orig.tar.gz 08eeedb9a736c3287602d0f9896986e470b4b444da1d3f7fbb77e4e26010834b 7156 php-phpseclib_2.0.20-1.debian.tar.xz 85b9b78cc86a724e1d73217090b750795c31f8f159dddc122379356e66652efa 6882 php-phpseclib_2.0.20-1_amd64.buildinfo Files: 203b1db42c2ee28bef7b53167e1da226 1802 php optional php-phpseclib_2.0.20-1.dsc a2f679e72da043ec087e87d11bd3dfa0 326883 php optional php-phpseclib_2.0.20.orig.tar.gz 11ae4b6e1bc8083726ab4d613dd9b034 7156 php optional php-phpseclib_2.0.20-1.debian.tar.xz a864c89c0488773b748e89164abce665 6882 php optional php-phpseclib_2.0.20-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAl0SbwMSHHRhZmZpdEBk ZWJpYW4ub3JnAAoJEAWMHPlE9r081m8IAKRUC2jcgVXd6va+gSI3sLU2i5m1H2Mv FToDnST8ZGLAN0nWoQd+47T5EeZeOU/ngx6/l+P8z9IcpG4Ymk/TAEXwSF4hd6pG g/igiQHTx4HPjkaWPM4xt+ZtybWm86jWwUFpuAelL9dQCb09ju33NQry31zpJn2g ZgtPiAsgT8EGeAzBGmVFZjYjhQ5RPcX870jzVAOPhA7peY0alU7MBcblw4NftQX7 ZFa+vcA0LilVXrXRPCVLc4Q2AggRaVuj+Gl1wzM5/eNs6/ahSeJBMwFrrgMqlzA4 syOi0ei6xUydGd4YorMwpzmqu+hvBMNNb/SJDiSKcgt1Y6ItOFuzMsA= =Czot -END PGP SIGNATURE-
Accepted pushpin 1.22.0-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 18 Jun 2019 09:13:31 +0200 Source: pushpin Architecture: source Version: 1.22.0-1 Distribution: unstable Urgency: medium Maintainer: Jan Niehusmann Changed-By: Jan Niehusmann Changes: pushpin (1.22.0-1) unstable; urgency=medium . * New upstream version Checksums-Sha1: 6faa8d4582cf6a2749c18a24771a97e577984f79 1732 pushpin_1.22.0-1.dsc 30a69c533e87eaa16def5c332f056b107c10f6e5 211616 pushpin_1.22.0.orig.tar.bz2 e2faac42e5d7ba2db50500edb1b31cd3a9a2648f 20044 pushpin_1.22.0-1.debian.tar.xz 355212dd56759b806a40432eb90bf4d509d6de1d 10834 pushpin_1.22.0-1_amd64.buildinfo Checksums-Sha256: a0f0faf908b7dfc0b6dd1f0ec983ecc284a224917772669056a783c09309ee65 1732 pushpin_1.22.0-1.dsc f4a1034d26ce1bfe55c1ff9071bc2c4ff038a20ab2c5e7492f5bd73de5900b1c 211616 pushpin_1.22.0.orig.tar.bz2 d39a37a9d307180ded25a15f406206dc979d98c65a308965558ba350ef7dd651 20044 pushpin_1.22.0-1.debian.tar.xz 90b1d6629300d093b696e372639daa7599952c7c25edac4c78fac4992d904624 10834 pushpin_1.22.0-1_amd64.buildinfo Files: 99c1779855615f4f473f68d7e701890a 1732 net optional pushpin_1.22.0-1.dsc 94fb0782efc044c7d384c08268d91594 211616 net optional pushpin_1.22.0.orig.tar.bz2 40f497d85c00fc5d9984cbe167d3f8a5 20044 net optional pushpin_1.22.0-1.debian.tar.xz 6eb59ad412d982efb599ef60a3930c79 10834 net optional pushpin_1.22.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQHDBAEBCgAtFiEE+20yASySVog94MmzwkDOmV0CaxEFAl0IqO0PHGphbkBkZWJp YW4ub3JnAAoJEMJAzpldAmsRdLsL/AoYTEMoDDLMLHikJZf/sOfnZauEK4C+WnAy t+GLsdPhNCUYn6xJpQld9S1K7NAuoiCnSaEtOpIWUgBwi0C40fTbCAoSS6HaHEca NZJeJnjat2kE5O6LBQlCDrKH7FsQ+Z6u6zhuz7XYoqv5BQnY+cKIGgA7aFTnhQb7 3KXNJyN+dUSh+FtKfeQyuimd/2ov108qzaNcfl1u7GBnQr7gHraKVCCtW1rvYfqB pcJltTFifwBsKjk2bzibLVr+9jq5f5PDNiGTcUFLM5k+OrImB7MDwx3X4rqVP2mF lKWBe6n1T33Sfts3De/Tyn4xrHbm19+0Wzn8kyM6jIyiG5b1X4tI7kG6U6UwZomD c2saMtiEQmElZSOJLBmFkKkODIUQldu8w5f3M5SRxNolJXPmvCu3p6PhYFDnvpW2 l4J8PkblJ12OGsOwrisktmmPNIAP6L9P3kOLT+JKfar/YOrWv9pHL6iR3EffO9/u etE1sUqemdv5Fds3sANdLwvXltIlVw== =Njor -END PGP SIGNATURE-
Re: getting rid of "testing"
On 6/25/19 8:08 AM, Ansgar wrote:
> Hi,
>
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
>
> Related to that I would like to be able to write something like
>
> deb http://deb.debian.org/debian debian11 main
> deb http://security.debian.org/debian-security debian11-security main
>
> in sources.list as codenames confuse people.
>
> Ubuntu already has no suite names, only codenames, but having to map
> "Ubuntu 18.04" to "bionic" instead of just writing the version in
> sources.list is annoying (I always have to look up the codename to be
> sure as I don't use Ubuntu that much).
>
> Ansgar
Are we going to have rc-buggy as an alias to Experimental? :)
Cheers,
Thomas Goirand (zigo)
Accepted grub-efi-arm64-signed 1+2.02+dfsg1+20 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jun 2019 10:11:12 +0100 Source: grub-efi-arm64-signed Binary: grub-efi-arm64-signed Architecture: source Version: 1+2.02+dfsg1+20 Distribution: sid Urgency: medium Maintainer: GRUB Maintainers Changed-By: Debian signing service Description: grub-efi-arm64-signed - GRand Unified Bootloader, version 2 (arm64 UEFI signed by Debian) Changes: grub-efi-arm64-signed (1+2.02+dfsg1+20) unstable; urgency=medium . * Update to grub2 2.02+dfsg1-20 Checksums-Sha1: 994a21ffa261999f78541862b4bafcd68ce31d01 1754 grub-efi-arm64-signed_1+2.02+dfsg1+20.dsc 3021ae0a8fb0b8c4ec89cab4e94b022807830f5d 4676 grub-efi-arm64-signed_1+2.02+dfsg1+20.tar.xz Checksums-Sha256: b9969366383f87a9ba2355a5f3e130d0632e231b5b9d061959a70834e768a2e9 1754 grub-efi-arm64-signed_1+2.02+dfsg1+20.dsc d63293563c3eed705bfbdf2adced9a61d71059f289ef217b2a2c934754436ca5 4676 grub-efi-arm64-signed_1+2.02+dfsg1+20.tar.xz Files: 72bbfe13bcb57d3fc43f49290cc0a545 1754 admin optional grub-efi-arm64-signed_1+2.02+dfsg1+20.dsc 36bea57706eb7ab9591b999c8cafca4d 4676 admin optional grub-efi-arm64-signed_1+2.02+dfsg1+20.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE8nXL3e4u3Tgu6Vp6qgZoiu+K+NUFAl0SZ9cACgkQqgZoiu+K +NXUaw//XWaot+6CwtAl7dHqXLG1s/SIBt7ty//cCprhzNxIX0r1p6tUe89PSy8A EliXFQfmxQb3FJ7QSreimkLSbBxk0tTvmODs/NjUfUKhe/ZW8SsclVDt8cdDfaJu anwZLka1Ornq7LPcmglWJXezMFS82j9J0j9ysbM/2DeVSfp/fBLBdHQD6/hb74hT X22B4JgYeKKOUpoasssItd2XfNMste9Ap4HimqonbghMDsKaIx4ry7P//pPCMAWG oQ4rBuWUOg2UtFmxjOxMeXQNQHMDMv2Iu6IREyeEPHcc3x5o65t1ZPKlfzaA7BWu N4ORo/8tPB0/C/Ph5FWCsnoICAuu2i8WFxMltcnEggU3pwsfwI5BoACnZCC8zY+Y 9jWJEKmwBu4Dlh5NURj+F/BkR7x+ngsvL6J1UPw+4o974flitMOhZxpujHgIsWju UzmXkdSag8Cccque+zFvZV9lrOPT18GRt0P2GltnV7Y3wLFeCg7EXUngjxxRV3kY udd4oQGN8QyGflimZqNBFTXIlB4Ar9nsa5BTSGugkY9ZcAP1AYU/e8wOw/f5IqQE u+nUfYzruhOj8+Su4WI9dCeb5U+E+LbQXZyUbV/+e/mivAByK/dhRQPM3xKq3Jbs bs+QXU9hZLFwwhNcviQ0lFlnX303KQxVUVV/Ni2rhOdozaHISh8= =/VfJ -END PGP SIGNATURE-
Accepted grub-efi-ia32-signed 1+2.02+dfsg1+20 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jun 2019 10:11:12 +0100 Source: grub-efi-ia32-signed Binary: grub-efi-ia32-signed Architecture: source Version: 1+2.02+dfsg1+20 Distribution: sid Urgency: medium Maintainer: GRUB Maintainers Changed-By: Debian signing service Description: grub-efi-ia32-signed - GRand Unified Bootloader, version 2 (i386 UEFI signed by Debian) Changes: grub-efi-ia32-signed (1+2.02+dfsg1+20) unstable; urgency=medium . * Update to grub2 2.02+dfsg1-20 Checksums-Sha1: 60dcac2a0ff6f6322f96c33634a877a8a1a84a0c 1745 grub-efi-ia32-signed_1+2.02+dfsg1+20.dsc d104b1ed1026818e9207f9384f47c57a9c8871ba 4672 grub-efi-ia32-signed_1+2.02+dfsg1+20.tar.xz Checksums-Sha256: 35e625767ceb3eaecfdbd56cb0304ab65f20a93a153c733de87883339df99a05 1745 grub-efi-ia32-signed_1+2.02+dfsg1+20.dsc d052ca3cd8f92ceee9c4d15b54cf30e6d3e7d177d419ad260666fc8161afc77c 4672 grub-efi-ia32-signed_1+2.02+dfsg1+20.tar.xz Files: b1d8ae3e6973768fa05a384d8c04e236 1745 admin optional grub-efi-ia32-signed_1+2.02+dfsg1+20.dsc 2f7239e381557a781c7976fc37863068 4672 admin optional grub-efi-ia32-signed_1+2.02+dfsg1+20.tar.xz -BEGIN PGP SIGNATURE- iQIyBAEBCAAdFiEE8nXL3e4u3Tgu6Vp6qgZoiu+K+NUFAl0SaFgACgkQqgZoiu+K +NWMjg/4ikfDORWmIJcV4ryT7xox/J8YoFAzMREsKw4mPVj+U8KGAueH6yMBwjK9 U5Vgu8+JSWRupyH05QuSj7YZOQujf5XH8Kd8CuYkDyTtU0O5gtg3k1wpDXRrlMEZ DenZ7jOHu/fhOO9eZs40KVz1VNqMdak5k1dPjEXmMUF3kPFPm3WnFSkKabxaU/Dl E5naE0RS+lFLQ+zbvTLLcwYUT0SeZSpxd3mxRWI2bO0qalQRoPFTjtXt3kmLdwwO r6Q9+H5L/fNkUu3XpisiHT48weqFVorhMU6f9Ms0BjVZlw6ufAO5ut8z1SpwliOW cjYUJtXGyPt0kjvRednn1dwk9H6qnLa3CZyR33HUdG74WW8UhnQeq7C9Ot6o3AuJ qn5yYc1UhQYqR8obF9X/+UCFrmQiBN27MdRoJ58Q5i/BRB4Pv/EzZqXagtx7ylMS xlAP6ylH7uCrQ8ytvDjKtCXfqvThtMMB7ff4xPaR3c1lH1ScyCM0rqZCg1sXWeUl sSjZD62MZuX7JCFfAkhtIcWalPQgH2wnxfxJYzP39TRPNj9Ot9L34Tu1cvq2qopK oRMjGPP48qxinc6Vm/fJ1j7DHgaew3A0srdmGz75ixv6nO6VSvGneT8kxqAC/05u 3wI2uA21PN39HeymaSJ7ZY2AT+wh//Ce0NP88x99+KKHeIEXyg== =IdEI -END PGP SIGNATURE-
Accepted grub-efi-amd64-signed 1+2.02+dfsg1+20 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jun 2019 10:11:12 +0100 Source: grub-efi-amd64-signed Binary: grub-efi-amd64-signed Architecture: source Version: 1+2.02+dfsg1+20 Distribution: sid Urgency: medium Maintainer: GRUB Maintainers Changed-By: Debian signing service Description: grub-efi-amd64-signed - GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian) Changes: grub-efi-amd64-signed (1+2.02+dfsg1+20) unstable; urgency=medium . * Update to grub2 2.02+dfsg1-20 Checksums-Sha1: 9fd71046fd9642870bd86e8e1b44c0806947d8fa 1754 grub-efi-amd64-signed_1+2.02+dfsg1+20.dsc 739132a641dc271280e5c5b9407875d07b9d2fe9 4684 grub-efi-amd64-signed_1+2.02+dfsg1+20.tar.xz Checksums-Sha256: 0d037215ca57952d56a56c84c5d19aa3e4dbb7ae3e63fa52322b2f077c684d66 1754 grub-efi-amd64-signed_1+2.02+dfsg1+20.dsc 3afc577b2ee930cb3b112c02a2290e5de1fde9591acb3ff9871e3dbdb187f615 4684 grub-efi-amd64-signed_1+2.02+dfsg1+20.tar.xz Files: 5521a9950e8d939e23dc4416b4c6c158 1754 admin optional grub-efi-amd64-signed_1+2.02+dfsg1+20.dsc 0e7d8882bfdc9347f5e051bc04ff4878 4684 admin optional grub-efi-amd64-signed_1+2.02+dfsg1+20.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE8nXL3e4u3Tgu6Vp6qgZoiu+K+NUFAl0SZy8ACgkQqgZoiu+K +NVrPBAArIp3HwXNjR1hje2qVKSlgGDRw8unYnMU9usslM+1yrX+hJFWC9g6Vl+Q r06/vrbPywoW1V3DEpIl/CB87V1j/+4M3we+9iuvFpEZWe3WPx1DFOqi57DS6zUZ 2fDOigbPsk2zO4T/ZdIvoB+fGGRwkXX1BMsNOQQEBZvuKvsn7XNH8GlZgB+JmkD2 Fp1GdrusHu+rJEH83V9CLSDlxsT5v380vSgXq4sAHNRsWnR8pv6nIgqc3urYVEYb mRL0ox9HgAses9lgYjK91URQQQkaqifsQT7BHstWEhknTRMEfAKyS4Ro+AWn4QIQ TekV3PB722ZZS/wEbdKJP5v1QurtRXu4X/mOkGqB5wR2K1wGuXu1NkP3WICSiffW Yph64wQsjvgGzGbi7h9j46W/IxxoPsU1GwoxZ1CkH8dmNE+sZnLrkmcy34l0Lz+o L+HXn6cpw585ib1H5hvvEY+t7fCdu/Mnwa1M7R6Vkbi9Vja45ioQD9W7A6H5vUIZ PfRCD1MXPH9nn9esfMiC7fiaZUPQsVCMWVJNhJm6cuQxMTIFcOnawsHHA3g2YUAw MD9YtmIgtM7oDBZmSL8Za7kXhsOAHhSO5FWT8wrrknVLar8k5lluxZAO9fzdptSl cQXqlve2yzpchWkles9kZLdoKun9ztHVWZx++ePEwEaz1nYBStI= =o4TT -END PGP SIGNATURE-
Re: Content Rating System in Debian
On 6/25/19 8:27 AM, Holger Levsen wrote: > On Tue, Jun 25, 2019 at 11:40:04AM +0700, Bagas Sanjaya wrote: >> Based on above, what are your opinions/thoughts/positions about Content >> Rating System in Debian? > just NO. please create a fork and leave Debian without this. Hard but necessary response :-) > IMO this idea represent a big work. And if you want to involved upstream, maybe will be a problem. Some upstream, could not be interest on participate because could be a "extra" work. But if we implement a content rating system, the freedom could be affected because the opinion on a package may be affected by this new system. -- Emmanuel Arias @eamanu https://eamanu.com signature.asc Description: OpenPGP digital signature
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 09:43:02PM +0500, Andrey Rahmatullin wrote: On Tue, Jun 25, 2019 at 12:40:01PM -0400, Michael Stone wrote: > and so on - i take the older releases only as reference. I just do something like look at https://packages.debian.org/ssh Or, if I'm really curious about versions, then something like http://snapshot.debian.org/package/openssh/ rmadison(1) and https://tracker.debian.org/ are probably better. Those are also good options for additional use cases. :) At any rate, putting every release ever into sources.list is generally not the best available mechanism.
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 12:40:01PM -0400, Michael Stone wrote: > > and so on - i take the older releases only as reference. > > I just do something like look at https://packages.debian.org/ssh > Or, if I'm really curious about versions, then something like > http://snapshot.debian.org/package/openssh/ rmadison(1) and https://tracker.debian.org/ are probably better. -- WBR, wRAR signature.asc Description: PGP signature
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 06:28:13PM +0200, Alf Gaida wrote: On 25.06.19 17:48, Michael Stone wrote: oldoldstable has the value of demonstrating some of what's wrong with the current system Can you please explain, i don't get it - maybe i to new at this. For me file like /etc/apt/sources.lists.d/debian.list: wow, that slows down every package operation on the system as you download or search 6+ versions of everything. and so on - i take the older releases only as reference. I just do something like look at https://packages.debian.org/ssh Or, if I'm really curious about versions, then something like http://snapshot.debian.org/package/openssh/ If you've got some kind of weird requirement to have everything local, I'd still rather see something like "debian8" in the output than "oldoldstable"--a name that changes over time and is therefore relative to both a reference system and a specific system at the time that entry was created. If I want a specific version of a package, it will only be in "oldoldstable" up until "oldoldstable" is something entirely different. I'm still not understanding a use case where that's an advantage.
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 06:28:13PM +0200, Alf Gaida wrote: > > oldoldstable has the value of demonstrating some of what's wrong with > > the current system > > Can you please explain, i don't get it That name is stupid. -- WBR, wRAR signature.asc Description: PGP signature
Re: getting rid of "testing"
On 25.06.19 17:48, Michael Stone wrote: oldoldstable has the value of demonstrating some of what's wrong with the current system Can you please explain, i don't get it - maybe i to new at this. For me file like /etc/apt/sources.lists.d/debian.list: deb http://ftp.debian.org/debian/ oldoldstable main contrib non-free deb-src http://ftp.debian.org/debian/ oldoldstable main contrib non-free deb http://ftp.debian.org/debian/ oldstable main contrib non-free deb-src http://ftp.debian.org/debian/ oldstable main contrib non-free deb http://ftp.debian.org/debian/ stable main contrib non-free deb-src http://ftp.debian.org/debian/ stable main contrib non-free deb http://ftp.debian.org/debian/ testing main contrib non-free deb-src http://ftp.debian.org/debian/ testing main contrib non-free deb http://ftp.debian.org/debian/ unstable main contrib non-free deb-src http://ftp.debian.org/debian/ unstable main contrib non-free deb http://ftp.debian.org/debian/ experimental main contrib non-free deb-src http://ftp.debian.org/debian/ experimental main contrib non-free deb http://incoming.debian.org/debian-buildd buildd-unstable main contrib non-free deb-src http://incoming.debian.org/debian-buildd buildd-unstable main contrib non-free deb http://debug.mirrors.debian.org/debian-debug/ testing-debug main contrib non-free deb http://debug.mirrors.debian.org/debian-debug/ unstable-debug main contrib non-free deb http://ftp.debian.org/debian/ stretch-backports main contrib non-free is perfectly fine. So it is possible for me -- strictly running sid with buildd on _my_ production system -- doing things like: % apt policy nano nano: Installiert: 3.2-3 Installationskandidat: 3.2-3 Versionstabelle: 4.1-1 1 1 http://ftp.debian.org/debian experimental/main amd64 Packages *** 3.2-3 500 500 http://ftp.debian.org/debian testing/main amd64 Packages 500 http://ftp.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status 2.7.4-1 500 500 http://ftp.debian.org/debian stable/main amd64 Packages 2.2.6-3 500 500 http://ftp.debian.org/debian oldstable/main amd64 Packages and so on - i take the older releases only as reference. So for me there is a use case, i'm not interested in older versions as old or oldoldstable - and i will never change this file without reason. Cheers Alf
Re: getting rid of "testing"
Am Dienstag, den 25.06.2019, 11:48 -0400 schrieb Michael Stone: > On Tue, Jun 25, 2019 at 05:01:48PM +0200, Alf Gaida wrote: > > Only a few remarks as former simple user and now maintainer: > > * Please don't mix things: release names has a value, distribution > > names like oldoldstable, oldstable, stable, testing, unstable has > > their value too > > oldoldstable has the value of demonstrating some of what's wrong > with > the current system Then running wheezy will be fine once buster is released, because oldoldstable will point to jessie and wheezy won't have a release name any more? Some admins ask: "How many reboots until the next Debian release?" Others ask: "How many Debian releases until the next reboot?" I can images systems that are getting bought, setup, and after several years shutdown and retired without rebooting or dist-upgrading them. -- Benjamin Drung System Developer Debian & Ubuntu Developer 1&1 IONOS Cloud GmbH | Greifswalder Str. 207 | 10405 Berlin | Germany E-mail: benjamin.dr...@cloud.ionos.com | Web: www.ionos.de Head Office: Berlin, Germany District Court Berlin Charlottenburg, Registration number: HRB 125506 B Executive Management: Christoph Steffens, Matthias Steinberg, Achim Weiss Member of United Internet
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 06:06:55PM +0200, Benjamin Drung wrote: Am Dienstag, den 25.06.2019, 11:48 -0400 schrieb Michael Stone: On Tue, Jun 25, 2019 at 05:01:48PM +0200, Alf Gaida wrote: > Only a few remarks as former simple user and now maintainer: > * Please don't mix things: release names has a value, distribution > names like oldoldstable, oldstable, stable, testing, unstable has > their value too oldoldstable has the value of demonstrating some of what's wrong with the current system Then running wheezy will be fine once buster is released, because oldoldstable will point to jessie and wheezy won't have a release name any more? Some admins ask: "How many reboots until the next Debian release?" Others ask: "How many Debian releases until the next reboot?" I can images systems that are getting bought, setup, and after several years shutdown and retired without rebooting or dist-upgrading them. I have no idea what you're trying to say, sorry.
Accepted sortedcontainers 2.1.0-1 (source) into unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 10:36:19 -0500
Source: sortedcontainers
Architecture: source
Version: 2.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Andrej Shadura
Closes: 888218
Changes:
sortedcontainers (2.1.0-1) unstable; urgency=medium
.
* New upstream version.
* Refresh the patch.
* New maintainer/uploader (Closes: #888218).
* Use debhelper-compat 12.
* Switch to pybuild.
* Wrap and sort debian/control.
* Use ${python:Provides} in the Python 2 package.
* Add Built-Using for the Sphinx documentation package.
* Use Python 3 Sphinx.
Checksums-Sha1:
5006e670ce448116df790ec05f35969ef693236e 2175 sortedcontainers_2.1.0-1.dsc
5e8da8ec911f7e32775096de153c0c23971e461d 9220860
sortedcontainers_2.1.0.orig.tar.gz
a0b431274caa684a9d9a2b06a4da1c176397249a 3088
sortedcontainers_2.1.0-1.debian.tar.xz
Checksums-Sha256:
20717e445f72bdc45cb6901d934d180fe1fbf02552f8084e51846d100a0926a0 2175
sortedcontainers_2.1.0-1.dsc
ecd1ed41968d61d49e2ee2d1a852b452535c2edadaac78147fee815610bc845d 9220860
sortedcontainers_2.1.0.orig.tar.gz
50905ee1f132dcc7b77ee5d2ed8709e036d7ef68f2c4d5cea56445b37b8dfa1f 3088
sortedcontainers_2.1.0-1.debian.tar.xz
Files:
9402a2adc0935e878e9056fef38d1696 2175 python optional
sortedcontainers_2.1.0-1.dsc
1aa2d4cef402341fdeea75bc51311e59 9220860 python optional
sortedcontainers_2.1.0.orig.tar.gz
027e14593164e32d605a1d6e3659b16d 3088 python optional
sortedcontainers_2.1.0-1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl0SQ0IACgkQXkCM2RzY
OdKCoAf/XQrY7cRWOmq2uGddR6Tc9PV5L65kSxQeaJlfQQjwuVRgAHMKq6G07ple
mNOVUh3kXTr2xTqUYzsHfwhUe6SjglPnJ2OG1qtdHE2reGuRIk5iQoj8JwYFZBTs
mweJBt0r9iS+KxIHRgo9gbvoSjXzOH81ALs8KeUqKPR/MyoodKrJ0rOBqMAFqLTc
DqEqjWJ5cEcAdzPefcNPbQjfn0MWDNN7B3vuGOzuQOmmFTi6k5Wqdb4iqxOB/ZOj
B5MsAs6HFjuUNQtJ8Sz65lclEHbW0PQklWeVHHZFlREEMLwStKauTinh5k+K65XK
Un593Ynj6tIptrvWpVc45ujzxKb8HQ==
=ml73
-END PGP SIGNATURE-
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 05:01:48PM +0200, Alf Gaida wrote: Only a few remarks as former simple user and now maintainer: * Please don't mix things: release names has a value, distribution names like oldoldstable, oldstable, stable, testing, unstable has their value too oldoldstable has the value of demonstrating some of what's wrong with the current system
Re: getting rid of "testing"
Only a few remarks as former simple user and now maintainer: * Please don't mix things: release names has a value, distribution names like oldoldstable, oldstable, stable, testing, unstable has their value too * the value is that they never change - they are convenient. Especially if one use unstable most of the time, please think of such things like `apt policy $foo` - it is highly unlikely that a sid user want to use old stuff, but will ask from time to time about versions ... * using the release names is convenient to set up systems before the release is done - i can set up a "buster" system now and have to change nothing when it become stable. The other way around is not a good way to go. At all - using distributions like "testing" or "unstable" should mean that the users/admins in charge can handle it - if not they should learn it or never ever do such things again. Might sound stubborn, but hey - i learned it this way. As a user of a rock stable "Sid" system i see no big problems for ten years now - ok, maybe to resist this: Hmm, what will happend if i will hit now ... Cheers Alf
Accepted debian-keyring 2019.06.25 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jun 2019 07:19:02 -0700 Source: debian-keyring Binary: debian-keyring Architecture: source all Version: 2019.06.25 Distribution: sid Urgency: medium Maintainer: Debian Keyring Maintainers Changed-By: Jonathan McDowell Description: debian-keyring - GnuPG keys of Debian Developers and Maintainers Closes: 928222 Changes: debian-keyring (2019.06.25) unstable; urgency=medium . [ Jonathan McDowell ] * Update Security Team role key expiry (0x6BAF400B05C3E651) (Closes: #928222) * Add new DD key 0x4A0CF639427884E3 (Michal Arbet) (RT #7759) * Add new DM key 0x3E1C27E11F69BFFE (Francesco Poli) (RT #7806) * Add new DM key 0xC3860AC59F574E3A (Bastian Germann) (RT #7807) * Add new DN key 0x10589E8283DDA9A7 (Denis Briand) (RT #7809) * Add new DN key 0x96BD4FF64E709FDE (Alban Vidal) (RT #7810) * Add new DD key 0x4CF2B218F54DAE3D (Jakob Haufe) (RT #7811) * Import changes sent to keyring.debian.org HKP interface: * 0x0576302FE189D4D2 Andriy Grytsenko [DM] sig:1 * 0x14AA1EB8A2473DFD Hugo Lefeuvre sub:2 sig:11 * 0x15E09AF4DF5182C8 Daniel Stender sig:3 * 0x17B1CA7D64089528 Chris Boyle sig:5 * 0x17FBDCBFD9928FF4 Jochen Sprickerhof sig:28 * 0x1CB4F0F78DECAFE9 Simon Kainz sig:4 * 0x1E7091B1F14A64A2 Aaron M. Ucko sig:2 * 0x1E759A726A9FDD74 Christopher Knadle sig:2 * 0x2C7C3146C1A00121 Jonas Smedegaard sig:3 * 0x3116BA5E9FFA69A3 Paul Wise sig:3 * 0x357312559D1E064B Ondřej Nový sig:3 * 0x3631D4FB7FF2B8B8 Christopher Stuart Hoskin sig:8 * 0x3AC8F716477EDB23 Ferenc Wágner uid:1 sig:20 * 0x500398DF5AB387D3 Martin Kepplinger [DM] uid:1 sub:1 sig:3 * 0x50C3634D3A291CF9 Philipp Kern sig:3 * 0x5262E7FF491049FE Jonas Meurer sig:13 * 0x5299B4990437AC41 Jan Niehusmann sub:1 sig:3 * 0x5394479DD3524C51 Jonathan Wiltshire sig:2 * 0x554297EDF9CCA585 Guo Yixuan (郭溢譞) [DM] sub:2 sig:5 * 0x5A8830475F7D1061 Nicholas D Steeves [DM] sig:3 * 0x5AD75B414EA41667 Georg Faerber uid:1 sig:1 * 0x634F4BD1E7AD5568 Enrico Zini sig:4 * 0x664F1238AA8F138A Daniel Lange sig:4 * 0x673A03E4C1DB921F Gunnar Wolf sig:10 * 0x689A04020D7EA9A1 Sebastian Humenda [DM] sub:1 sig:7 * 0x6C6ACD6417B3ACB1 Roger Shimizu sig:3 * 0x6DAC3C448773381A Andy Li uid:1 sig:1 * 0x6EA4D2311A2D268D Andrew Shadura sig:8 * 0x7731FCCC63E4E277 Roberto C. Sanchez sig:3 * 0x77C0C75E7B650808 James Valleroy [DM] sig:2 * 0x786C63F330D7CB92 Felix Yan sig:1 * 0x789D6F057FD863FE Salvatore Bonaccorso sig:12 * 0x792152527B75921E Antoine Beaupré sig:4 * 0x79C43E620B039B35 Jens Reyer [DM] sig:3 * 0x7AEAC4EC6AAA0A97 Louis-Philippe Véronneau sig:6 * 0x80AD73734275BDAF Fabian Wolff [DM] sig:3 * 0x8CBF9A322861A790 Micah Anderson sig:2 * 0x8D1F969A08EEA756 Dmitry E. Oboukhov uid:1 sig:2 * 0x8D8337911DEB Emfox Zhou sig:1 * 0x936A835B678B9796 Pau Garcia i Quiles [DM] uid:1 sig:1 * 0x962680C5305A9418 Kåre Thor Olsen sig:2 * 0xA1F751F1A55357E8 Nattie Mayer-Hutchings sig:2 * 0xA3BABAE2408DD6CF Felipe Sateler sig:4 * 0xA81CEA22BC8C7E2E Luca Boccassi uid:1 sig:2 * 0xB01D1A72AC8DC9A1 Jonathan Cristopher Carter sig:3 * 0xB24CA63F6EBBE84D Timothy Potter uid:1 sig:4 * 0xB999CDB58C8DDBD2 Guido Günther sig:10 * 0xBC196A94EDDDA1B7 أحمد المحمودي [DM] sig:6 * 0xC51EA7006E6BDC0D Taowa Munene-Tardif uid:1 sig:1 * 0xC9183BEA0288CDEE Bobby de Vos sig:5 * 0xCAFB3BAD0A75C877 Nathan Harrison Handler sig:3 * 0xCC65B0CDEC275D5B ChangZhuo Chen sig:10 * 0xD003852FBD52529E Thomas Preud'homme sig:3 * 0xD04BA3A00125D5C0 Philip Hands sig:3 * 0xD36F769BC11804F0 Theodore Ts'o sig:3 * 0xD599FF6101809E2A Elena Grandi sig:1 * 0xDA82830E3CCC3A3A Alexandre Viau sig:3 * 0xDAB389329A4CFA16 Ross Vandegrift sig:4 * 0xDD1FAB8937FE9825 Kai-Chung Yan uid:1 sig:5 * 0xDECF849AA6357FB7 Tobias Frost sig:3 * 0xDEE8043EE17EBB30 Rhonda D'Vine sig:2 * 0xE2DCDD9132669BD6 Uwe Kleine-König sig:12 * 0xE523F220AC8DFBD0 Adam Majer sig:5 * 0xF5C83C05D9CE Chris Boot sig:4 . [ John Sullivan ] * Add new DD key 0xC9B0AC74C72B5836 (Sruthi Chandran) (RT #7780) * Add new DM key 0xD39D8D29BAF36DF8 (Jongmin Kim) (RT #7781) . [ Gunnar Wolf ] * Replace 0x427E381D05190E55 with 0x854F07BE082DF14F (Kyle Robbertze) (RT #7785) * Replace 0x762B57BB784206AD with 0x7E4E65C8720B706B (David Bremner) (RT #7792) Checksums-Sha1: 2318f92d989a0c1d08472a234804efb98f265406 1834 debian-keyring_2019.06.25.dsc 4689e97e26d7a528257f07e4a3e5233ae2c03cfa 33629488 debian-keyring_2019.06.25.tar.xz 0db82e2175674813adab2e7f2800bd26ecbd0511 32285732 debian-keyring_2019.06.25_all.deb 2e545dc7e20b5d7b70cbe6cd7c49a8492341d636 6290 debian-keyring_2019.06.25_amd64.buildinfo Checksums-Sha256:
Accepted verilator 4.016-1 (source) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Jun 2019 03:32:47 +0200 Source: verilator Binary: verilator Architecture: source Version: 4.016-1 Distribution: experimental Urgency: medium Maintainer: Debian Electronics Team Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) Description: verilator - fast free Verilog simulator Changes: verilator (4.016-1) experimental; urgency=medium . * Imported Upstream version 4.016 * Refresh patches * d/docs: removed TODO Checksums-Sha1: 426546091c728aab518afaf71d90c4d5be008bfc 1685 verilator_4.016-1.dsc dce30a001574e743198179e4f95939d84b69c7f8 2536449 verilator_4.016.orig.tar.gz 12794c8b34fe9cd2f2cfce3f8771043afb701b06 8972 verilator_4.016-1.debian.tar.xz 550bab1fd6f1c22a67c17841f5ccf40a81654e0d 5508 verilator_4.016-1_source.buildinfo Checksums-Sha256: 6e16e745ccce02f29809cc6eec525ef555072f190b429a980c4f1032f124d3d6 1685 verilator_4.016-1.dsc 328a8f85c4fb0ecdabbf56e3c261485234dd1c28211e413101c533fdaea9d8a1 2536449 verilator_4.016.orig.tar.gz 18216bcfc6e57d9e964cf53c2a4948bbc324549284270ffcbb7e52a8d1509c31 8972 verilator_4.016-1.debian.tar.xz 8d267b4734e4ee203c127b2ca0d64bbd23ca36f3ce5512e8055e918c34745a0d 5508 verilator_4.016-1_source.buildinfo Files: 90fd37ca472f1f68df027dc14c6afcb7 1685 electronics optional verilator_4.016-1.dsc 212649d37840e033ae06da1d95ad2d9e 2536449 electronics optional verilator_4.016.orig.tar.gz cdb9dc9005461325dc9b4ab7bfb989d2 8972 electronics optional verilator_4.016-1.debian.tar.xz 9042b73e64e02332c7e5e8a355100efd 5508 electronics optional verilator_4.016-1_source.buildinfo -BEGIN PGP SIGNATURE- iQEcBAEBCgAGBQJdCZDiAAoJELwZapTt3aG3wJkIALIZzbqOdMCK+PdVd/8WNWb+ Agmf6VHpldgWjR/PWgZE3iXDPVjkYG2+EHXg5QISsP+GOtymv4tzewzLyucioV2i U2pWKqSfzGmW6RhtFZwDWl15s2JzqIfHWzSyzHzXKosQ0gww12U3bOMwIDKn0nBA vUcmtSxDwQGt6w9H9fdYLetnEYCFQQhQ0pnbjzS1bz7d73DdoGbGQrLcHikgCpRU M4wbYbWZLbJXluotz9N69oPslUyvetV2kIsKsc4oA24P0T8eNIM03matCtJcz6nf 63FHWavphL+x6suGX+x6MG4fqoZB704iDrtMo3WcTMn7Evi5eK1+W6h7CdgkAvs= =LAFZ -END PGP SIGNATURE-
Accepted qt3d-opensource-src 5.12.4+dfsg-1 (source) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jun 2019 17:04:53 +0300 Source: qt3d-opensource-src Architecture: source Version: 5.12.4+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Changes: qt3d-opensource-src (5.12.4+dfsg-1) experimental; urgency=medium . [ Scarlett Moore ] * Update packaging to use doc-base as per policy 9.10. . [ Dmitry Shachnev ] * New upstream release. * Drop nonfree_resources.diff, no longer needed. * Bump Qt build-dependencies to 5.12.4. * Make tests fatal on most architectures. * Honor nocheck build option/profile. * Update symbols files from the current build log. Checksums-Sha1: 491bf40f97553e96f549978e7add1d5b02197753 4311 qt3d-opensource-src_5.12.4+dfsg-1.dsc acdb33ea76be5a36d470ea9f59155c555cf44622 79932352 qt3d-opensource-src_5.12.4+dfsg.orig.tar.xz 817c43f33bcaa14d29614774d6dcdcf2a2c95bba 57580 qt3d-opensource-src_5.12.4+dfsg-1.debian.tar.xz fb797d2ccd517efefa85265e094ea9ad50b30fb7 12555 qt3d-opensource-src_5.12.4+dfsg-1_source.buildinfo Checksums-Sha256: 7ab81a501cc00a0797aaf41f00c1bc023178510c1edd49b9857f48e53affb1b3 4311 qt3d-opensource-src_5.12.4+dfsg-1.dsc 12772df948fb823bd3615508151925cefe005b879a923b95e1b93dbc48799f01 79932352 qt3d-opensource-src_5.12.4+dfsg.orig.tar.xz d4abfd3db20405cc2559bf7d99a1f0a6e6772a8dba6dba2cf72738e92a72a97c 57580 qt3d-opensource-src_5.12.4+dfsg-1.debian.tar.xz b62ac31a88d63c66481a37904c8c2e7ea2476f290c5218b334de159e5e27f671 12555 qt3d-opensource-src_5.12.4+dfsg-1_source.buildinfo Files: 0f509e793952b5854f48d09a537ca7eb 4311 libs optional qt3d-opensource-src_5.12.4+dfsg-1.dsc 92d26feb0ba132602db66c043a513749 79932352 libs optional qt3d-opensource-src_5.12.4+dfsg.orig.tar.xz af15a0d161936bcb59fa30d3ac0be6c7 57580 libs optional qt3d-opensource-src_5.12.4+dfsg-1.debian.tar.xz 7efcce946cd48615e2c02980742e63d0 12555 libs optional qt3d-opensource-src_5.12.4+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE8kKZ/xu8kBi5BqTLYCaTbS8ciuAFAl0SK2kTHG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBgJpNtLxyK4L8pD/9c3Gp2BaezroteuP0KhQORk+lGLdP9 LE5STB8VCCJTIV7cF/8mcOWatkKyi/meamdt2GTiCwLDvvSAMe4do6bRlAUVmEQW CkMSwMYchJCqR2u+hvKsO+SeylsdPECm9JTBsqDY6Ly7SfLssZhiSGagKQkYCB9l pvL0EtaPDbcxs4lSewx6SWrgwaEvMYGD+qsls7PuFPqxvPSgsBJe5ozeU8ic7VJ6 Fh8Zo0zFJR4hmdoN41iiOU09cyT8ron9RTp8CX7TK6XTtAlBv85H4ebPABbYAu5l h9J1FHFMDkpiHSK2ZFTECjHHHP9iRPg5uNZJSEp4QfMsRLX/hHDw82Jn2D315rc4 zlPJjr1v4dftsOdOTs2joQw95Etkk/U0m35/vOhjQ1SbBT1h1qe5yDGe40GCHk51 Tj49WdgjhQRd/cRs/nbYZbkxDDAb7ElHEvyHrgcl7GvAu+Gd9d/xgezB5U9bFqOD k9KxP35YAOPWFO2tdR3u2ACA9LreVG8gDxpNBS9cFM6xwVpA7dU8qR1I6RIPXNJG 9aK2OiiTsKNXw0E+iMBAZEG7X46Rg+IcJX5vDYXsn+LLlv8nJD//dqBaGweJoJbf ZfuMX80YXtmN2HqHRWnThOTIiZWjift/ayUunBTO3Ych1hP9vEkCPSKfJ5s6TBao fdMhn3qFIx11qA== =fUeV -END PGP SIGNATURE-
Accepted r-bioc-biocgenerics 0.30.0-1 (source) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jun 2019 15:15:44 +0200 Source: r-bioc-biocgenerics Binary: r-bioc-biocgenerics Architecture: source Version: 0.30.0-1 Distribution: experimental Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Andreas Tille Description: r-bioc-biocgenerics - generic functions for Bioconductor Changes: r-bioc-biocgenerics (0.30.0-1) experimental; urgency=medium . [ Dylan Aïssi ] * Add Testsuite: autopkgtest-pkg-r * Add reference in d/upstream/metadata. . [ Andreas Tille ] * New upstream version * debhelper 12 * Standards-Version: 4.3.0 * rename debian/tests/control.autodep8 to debian/tests/control Checksums-Sha1: d6230ea8b3524065b97ee248e71b421bbe8041df 2172 r-bioc-biocgenerics_0.30.0-1.dsc b2c3c899c3e9091de46a01e9558900d5d89c07ed 45785 r-bioc-biocgenerics_0.30.0.orig.tar.gz 17863ea3143d6f684accb831a3a74648fbe843af 6288 r-bioc-biocgenerics_0.30.0-1.debian.tar.xz Checksums-Sha256: a012457d84f7dce4a52bdec8b92f713e48ece5af54e13aab452859ac0377fe9d 2172 r-bioc-biocgenerics_0.30.0-1.dsc 2e6d2fa6ed389cfae6fd75713379ba7dcd164a8161f37f1bbed596b70c3207d9 45785 r-bioc-biocgenerics_0.30.0.orig.tar.gz ffa78728f83b6ce9903df5c9ba133a3fb45b69bae62675c24a714e4fbbc00e4e 6288 r-bioc-biocgenerics_0.30.0-1.debian.tar.xz Files: 335a20bd31e20cf180da7a53040df74d 2172 gnu-r optional r-bioc-biocgenerics_0.30.0-1.dsc 77e2d121cec79b2656c24621b77923da 45785 gnu-r optional r-bioc-biocgenerics_0.30.0.orig.tar.gz 6bcf6fc70f14c1a4aa840a5724f8a4f2 6288 gnu-r optional r-bioc-biocgenerics_0.30.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl0SH/0RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtHuaQ/8DpwvJrmRew/TqGq3+x9JFuhAlqyQcDmN J8gSuN83L7GZUZ4jiKR5pX97jWEtnLdNh7pObZSfGWAVjcpDAAVaxoDB52tMw6zA 0DrjHocKmfU9u+R8xD3ZQwIPL8GmD28CkTWD1eUAeELs7PUt9iciH1P1fsnnKBFo ONzvxjLVXfDhXBkRfNGvKVJ3aEzg6LjpaWooBap9qTVpWysmy9jQ2XOzThCEaIk+ 8cEJ+VhK7Y9asSir11nFvTkvW9ImfBzrm6qXQKwejjFbFqngu8Bhv40/86bKU0Ia EWfOP6cAT553O7CKOr564p+X1k/Xilo55PBCsDbtFMQOEsUgwEEe9sLjhN37BBMn f/FYr0b3HvMIGwuNa+2p9ai7ck91FtoIZRyEF6+pq/LZwHcC3nokJti94+py7Wz1 DzXGO1MrTd33nJ2uBUz7Vn36kWnX3F9hnUKwCh1DdluCIFB23NVnt9ly7zTmKd57 /II9wwpRfM/8M2ZqIjrXcjt1nKqQMRt3mQcwNJnlO2riI3BvxaZqFq0kqZxuJla1 onDw/VCbtoNyeUPsl39SCcRfrL7AbSl+zzIaJ4LGZHbggXic2Hcy4bruMeehRrVp 9DViw4PraJq35o5WLvcXKCF6jdFVPXsgRvs5cPZAiADXgVTYaZq1Y1FXnan2wxtU mT3vKemOICk= =pNIW -END PGP SIGNATURE-
Re: Re: Re: Content Rating System in Debian
Am Di., 25. Juni 2019 um 11:51 Uhr schrieb Bagas Sanjaya : > > Simon McVittie: > > Appstream metadata, which is canonically provided by upstreams and is > distro- and package-type-agnostic (available in at least apt and Flatpak), > has this as an optional field for self-rating: > > https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-content_rating > https://hughsie.github.io/oars/ > > I suspect that's the only way this could possibly work without money > changing hands. > > There are no age classifications, however. > > So based on content_rating tag on AppStream metadata, we can add logic to apt > in order to determine age rating for our > packages. However, external review (maintainers) may be need in order to > prevent misleading information on > content_rating. To clarify: Age ratings vary wildly between countries. So what we expect is that software centers will not actually display content_rating information, but instead compile an age rating out of it based on the user's current location/locale and then display that. Having a "one-size fits all" generic rating isn't very practical. Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 02:38:43PM +0200, Bastian Blank wrote: On Tue, Jun 25, 2019 at 08:03:49AM -0400, Michael Stone wrote: Having "stable" in sources.list is broken, because one day stuff goes from working to not working, which requires manual intervention, at which point someone could have just changed the name. Once I had unattended-upgrades do the upgrade to the new stable for me over night on quite a few systems, almost everything still worked. "almost" covers quite a lot of territory, and is the reason it's best not to have the upgrade happen accidentally.
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 08:03:49AM -0400, Michael Stone wrote: > Having "stable" in sources.list is broken, because one day stuff goes from > working to not working, which requires manual intervention, at which point > someone could have just changed the name. Once I had unattended-upgrades do the upgrade to the new stable for me over night on quite a few systems, almost everything still worked. Regards, Bastian -- There is an order of things in this universe. -- Apollo, "Who Mourns for Adonais?" stardate 3468.1
Accepted qtconnectivity-opensource-src 5.12.4-1 (source) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jun 2019 15:17:52 +0300 Source: qtconnectivity-opensource-src Architecture: source Version: 5.12.4-1 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Changes: qtconnectivity-opensource-src (5.12.4-1) experimental; urgency=medium . * New upstream release. * Bump Qt build-dependencies to 5.12.4. * Stop passing QMAKE_QMAKE to dh_auto_configure, the qmake cross wrapper already passes it. Checksums-Sha1: 685e116cc0ba124e685010a6ffe8783b8dd2da1e 3279 qtconnectivity-opensource-src_5.12.4-1.dsc e0d701acbe0255b53ee3cda25b29096c5930daa3 2751984 qtconnectivity-opensource-src_5.12.4.orig.tar.xz da84564f9b7516a0abeb63325e9360392ff192d1 14196 qtconnectivity-opensource-src_5.12.4-1.debian.tar.xz d762d4219ac33feef7de7f439b2db2ce8269614c 11796 qtconnectivity-opensource-src_5.12.4-1_source.buildinfo Checksums-Sha256: 62b5632ecd65a2c4b39f8e4f6b1ebf95c5f462b1b7abaf243e291fad5fbcde23 3279 qtconnectivity-opensource-src_5.12.4-1.dsc 749d05242b9fae12e80f569fb6b918dc011cb191eeb05147cbde474ca6b173ef 2751984 qtconnectivity-opensource-src_5.12.4.orig.tar.xz b49c542d7c5f7c79c5ec40676f25eacf422660714923aa324866a5b3fd9e9fb6 14196 qtconnectivity-opensource-src_5.12.4-1.debian.tar.xz 8901109c7685a9f4c06a73d879abe39bc52e3c8c3f7d34c523ca1487000b639b 11796 qtconnectivity-opensource-src_5.12.4-1_source.buildinfo Files: c9b2b8e37a61cc19ab96f85a5d53248d 3279 libs optional qtconnectivity-opensource-src_5.12.4-1.dsc e44edb1286fffb3d1ba74f57ddea0721 2751984 libs optional qtconnectivity-opensource-src_5.12.4.orig.tar.xz 1ade9a39bdd323940d5bed42504d8c78 14196 libs optional qtconnectivity-opensource-src_5.12.4-1.debian.tar.xz c463b777e7e20170884243bef43e1441 11796 libs optional qtconnectivity-opensource-src_5.12.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE8kKZ/xu8kBi5BqTLYCaTbS8ciuAFAl0SEUwTHG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBgJpNtLxyK4Eq0EACgSiynx5KzOKo7+TmdjjO4PgjNhcGK 947tR2Hx3W1fE8zO4l9pg/908yRyrOzFT7nPLoVhXxFQf7xQ4QSDszOvGd9qiFpx B6crMHkh1OHsYCcNNKaqBaiHNyz37be0xRtGAjj1uQ1EqzW36YNkpTugI/6cOw4h YSroKxvcvmK+O+RXuAM97nntm7uKa8yr4esbr5/zXYOlsxARz3Pw1m41Xr0q58kg pLSFdrByzJWCM69XX2tkKsuFrmQWowrIzflTnWQuXoElgOpRxBhDx0Zt9ijtJ5We GSju8Y5ufKEWcGq5vy+7Lk+gpTh7reQgIWvPixIQ29Mrv9YT4fDjhOF/8uViKb4U /SwxLufbM/KIQwm4Xn18upYbGnDAZ3TGL3WSZxk3HUb+5maeBrAMFeKtygMXq+xK BHFQFaxlOMYoeD83VfAtotk0S41Zj0hgarzpG+GT40Mv8lF8GuB8w8iQYW50XBF3 h1rQKWrimS+mUEwc5fdXqos5hJ7vsYaM+JMpHIW9w8gk10Hk6KYroqsLCHAh06Aa gPfPWjRPvDWzWo7IgAQ86EDzOifFO5vIFyyV7F4R1BVWN8IEVSxsQQ0hRlTg0IRJ QyO0d8Y8zcw/V198TdEHSB89Eoc2xpxrE/O3YPfzxHjW3wP6+dJ56uMsmHsOwD9s pqJNzk+PV2JPHg== =De++ -END PGP SIGNATURE-
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 08:07:51PM +0800, Paul Wise wrote: On Tue, Jun 25, 2019 at 8:04 PM Michael Stone wrote: Having "stable" in sources.list is broken, because one day stuff goes from working to not working, which requires manual intervention, at which point someone could have just changed the name. Having codenames in sources.list is broken, because even people who have been developers for two decades can't remember which release is which without looking it up. (Which is harder than it should be; maybe we should have had /etc/debian-releasenames or somesuch from the beginning. lsb_release -a is helpful when available but doesn't have context, and many users don't know it exists.) Personally, I can remember the names and their order much better than which version goes with which codename or suite :) Well, every problem domain has its rainman :) For the rest of us, there's google.
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 8:04 PM Michael Stone wrote: > Having "stable" in sources.list is broken, because one day stuff goes > from working to not working, which requires manual intervention, at > which point someone could have just changed the name. Having codenames > in sources.list is broken, because even people who have been developers > for two decades can't remember which release is which without looking it > up. (Which is harder than it should be; maybe we should have had > /etc/debian-releasenames or somesuch from the beginning. lsb_release -a > is helpful when available but doesn't have context, and many users don't > know it exists.) Personally, I can remember the names and their order much better than which version goes with which codename or suite :) -- bye, pabs https://wiki.debian.org/PaulWise
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 11:09:06AM +0100, Ian Jackson wrote:
~Ansgar writes ("getting rid of "testing""):
Related to that I would like to be able to write something like
deb http://deb.debian.org/debian debian11 main
deb http://security.debian.org/debian-security debian11-security main
in sources.list as codenames confuse people.
Yes, please, absolutely. And this should be the default.
+1
Having "stable" in sources.list is broken, because one day stuff goes
from working to not working, which requires manual intervention, at
which point someone could have just changed the name. Having codenames
in sources.list is broken, because even people who have been developers
for two decades can't remember which release is which without looking it
up. (Which is harder than it should be; maybe we should have had
/etc/debian-releasenames or somesuch from the beginning. lsb_release -a
is helpful when available but doesn't have context, and many users don't
know it exists.)
Accepted wordpress 5.2.2+dfsg1-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jun 2019 21:03:42 +1000 Source: wordpress Binary: wordpress wordpress-l10n wordpress-theme-twentynineteen wordpress-theme-twentyseventeen wordpress-theme-twentysixteen Architecture: source all Version: 5.2.2+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Craig Small Changed-By: Craig Small Description: wordpress - weblog manager wordpress-l10n - weblog manager - language files wordpress-theme-twentynineteen - weblog manager - twentynineteen theme files wordpress-theme-twentyseventeen - weblog manager - twentyseventeen theme files wordpress-theme-twentysixteen - weblog manager - twentysixteen theme files Changes: wordpress (5.2.2+dfsg1-1) unstable; urgency=medium . * New upstream release Checksums-Sha1: 1eec1ce23bda1bdb467e79f02a46c683ae310fe0 2442 wordpress_5.2.2+dfsg1-1.dsc 9ab21e110035620418d141846b39828c06f7c045 7948108 wordpress_5.2.2+dfsg1.orig.tar.xz 3077e6105c222f02bdea8038b5066bdbaf729ae2 6819084 wordpress_5.2.2+dfsg1-1.debian.tar.xz 25749c864c9c23ae8ae094270f1188f46e709ab4 4382432 wordpress-l10n_5.2.2+dfsg1-1_all.deb b02aff0f88019c9a6ba4f8136c40a84569bd873c 314804 wordpress-theme-twentynineteen_5.2.2+dfsg1-1_all.deb ffb519786606c0aac86ee43284c9010e02189e2d 946040 wordpress-theme-twentyseventeen_5.2.2+dfsg1-1_all.deb fe877e47579e227c173ea825c0721af0f520974c 593808 wordpress-theme-twentysixteen_5.2.2+dfsg1-1_all.deb 9f93cc6a1a159765f817d6f0dee118fe16f4e369 6102632 wordpress_5.2.2+dfsg1-1_all.deb c95f88a42e6c12e893d1bb53efabccd1f9b4b431 7255 wordpress_5.2.2+dfsg1-1_amd64.buildinfo Checksums-Sha256: 5c3e594e1519747028a391bb347cb5a104bacdbd84bbdc6a1b6501fdb2debbc9 2442 wordpress_5.2.2+dfsg1-1.dsc b3accda2360c0ee75cbfef6051b038cb7e073065640dd1051a922fa7798feaaa 7948108 wordpress_5.2.2+dfsg1.orig.tar.xz f8f5bf381b2ea551399eb88beb6fa91a1b2936ddbdbb6deb13411dda96a9ebfe 6819084 wordpress_5.2.2+dfsg1-1.debian.tar.xz 657ac9cd9b71b7c781d7c9391e4a2e5b9ba216d4a171294a039651fe09a2811e 4382432 wordpress-l10n_5.2.2+dfsg1-1_all.deb ee33d52c656a4ebf92f2fca8b084813938f5443e4dc34b64c19740f5dafc2fd3 314804 wordpress-theme-twentynineteen_5.2.2+dfsg1-1_all.deb 5eabe8d71c2a4142aa215e1888df7a19946cf6c98c56dfcf447dd743004533fe 946040 wordpress-theme-twentyseventeen_5.2.2+dfsg1-1_all.deb c77260782625fd7a4d6aa79965abc4e9fda347dafb4bec4ec436f3f8459de467 593808 wordpress-theme-twentysixteen_5.2.2+dfsg1-1_all.deb 152689e54d7edf33246d185eff84d4d7958c19c86220af9b7bc7e559237e318f 6102632 wordpress_5.2.2+dfsg1-1_all.deb e5ce66429435447a27b40ed902f2f4563ef4b5bf2383c0ef05f2e6b93b034578 7255 wordpress_5.2.2+dfsg1-1_amd64.buildinfo Files: 524c8fa74fe3f78474e4c1f19ba4 2442 web optional wordpress_5.2.2+dfsg1-1.dsc 8b40371724562aa9432f5e9dea97a604 7948108 web optional wordpress_5.2.2+dfsg1.orig.tar.xz b0a0375d1f063b67866256b3fd455e83 6819084 web optional wordpress_5.2.2+dfsg1-1.debian.tar.xz 1ee9b20cb700b417bf313798f139b7ae 4382432 localization optional wordpress-l10n_5.2.2+dfsg1-1_all.deb c1ac02198667f343ca7781064dac4e8c 314804 web optional wordpress-theme-twentynineteen_5.2.2+dfsg1-1_all.deb eb8f5316a82e774b51d46d046a76fd1f 946040 web optional wordpress-theme-twentyseventeen_5.2.2+dfsg1-1_all.deb b36e642ff9a62c594e57c062d12254a8 593808 web optional wordpress-theme-twentysixteen_5.2.2+dfsg1-1_all.deb 783b9000e3514e7ad18f099d59d4e56a 6102632 web optional wordpress_5.2.2+dfsg1-1_all.deb 66881c8c9324734bf65f9048cd334bd2 7255 web optional wordpress_5.2.2+dfsg1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAl0SAQEACgkQAiFmwP88 hOMEwBAAnbisGmVjWoXgpd3tz2sqbDlFSoJhlaf+emsxW1tDNaFReJAKttlqSmqi iAczbqvLDhn6b4Du2lHZZX+nQ7A01s1bcX0BLd0RmvBk5ls6OCT3OXrg5lU9JKNj QzbJR9QfVwFZRUkrrX/fc+MhrzcjrnntNbh0zglLRVUjK/tZno9JgJAhYUYfREKR mgAlqcbuzLyGFHd4o7RFUumWdt9IciE6betyv+6vz7B50toBQMKb+7y/7wR6h4Dz VTSrikapkrebhfsMIcdTH5OKJvCJR14BtjraidsrIvehZW04WHZaQVUbBLW3f+ix Er02JFsGF5SgEa6PPSg4KKsumpc4AbDzrcZZ4agAMWqATgYw8d0SaOWbsYY6LnkR shH3LXe/jq2qdvouvdPzWk7DnDgGFuLN2RvckZ5ZjzSf7uND7/kXmcWYjsq0DzG1 YhOvNWlqoRsdLc1dRlaUPci9+cHkDGxBVfpcuK+QMDqiQiIN+gcGFarlI+mRt7pV F2qsSGwXVxTSMgc7OgkmnMJ/ZZjq43r3SKN3OGRiqxGTwTWwR+kPj7DMAAFe4VZT OcLmPfCJ+5QQ+gImDYtWv4hhjN3403IYV4HaLCF5x++9KSAlKR23N7ILWafP+TH0 /PMJzSkV7EW2QB0RSLBwYDsGvRD2FxOW1E7eCNLeULh0DD4l9k4= =lTZk -END PGP SIGNATURE-
Accepted ionit 0.3.2+really0.2.1-2 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jun 2019 13:18:08 +0200 Source: ionit Architecture: source Version: 0.3.2+really0.2.1-2 Distribution: unstable Urgency: medium Maintainer: Benjamin Drung Changed-By: Benjamin Drung Closes: 931060 Changes: ionit (0.3.2+really0.2.1-2) unstable; urgency=medium . * Drop After=local-fs.target from ionit.service to break dependency loop (Closes: #931060) Checksums-Sha1: 3cee0321ce6b3c0742a77c134116eea289351dc9 2058 ionit_0.3.2+really0.2.1-2.dsc edbff26003957f4326a576d40994c359f92045e3 10548 ionit_0.3.2+really0.2.1-2.debian.tar.xz cdae63de9680f72ed9cdb1b284c4804ec92f2b60 7064 ionit_0.3.2+really0.2.1-2_source.buildinfo Checksums-Sha256: f15a467e35b8567a5694307ee89aa3b2c5687b3ee450934ad312813509e904b6 2058 ionit_0.3.2+really0.2.1-2.dsc 2bf9958dc6be661e458c0e991e8a40fe738cad3254224eef563b64b353f80666 10548 ionit_0.3.2+really0.2.1-2.debian.tar.xz 6978ee55f8935c71af6d4312da969fb8ea64a868c4b7091209d7858a04eedd42 7064 ionit_0.3.2+really0.2.1-2_source.buildinfo Files: 328423f4f9c2d68afb90b918df7325dd 2058 utils optional ionit_0.3.2+really0.2.1-2.dsc d619de917939b988edd26bb9ceb44074 10548 utils optional ionit_0.3.2+really0.2.1-2.debian.tar.xz 18fc0dfabd53f199e86b21a5f5a83c21 7064 utils optional ionit_0.3.2+really0.2.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE5/q3CzlQJ15towl13YzVpd6MfnoFAl0SA1sACgkQ3YzVpd6M fnoKOA//eDTKIubXI6NAJIVWxNoZrnib7l7FTPrI5cHxLlwiHdMiUDTBo3dLImoU /OfPS0gFnnZwGt0QDTCL2AmaSZphKLIRVyr+9y84amRtoa4tASrq9s1rWP8IRI34 zsMUIBIQ82zEhgAC1vHMAX9Dly6DPtRtN1S8h89Ss6HQthnYWYDl/G84vSvbs2fI nKppbl+4P3ZxqcjUQxzWjbiEUO4LzXd3T1oleWJWh1VjR2Z2a/jDgtck+mYz0AW0 vzcGoxJQdJ5Y9IuLm+P/q0NurlsnZKaIglJA4j7G4CrbSCSNGVx3gS1mGrxKMRqO 1TICDXlykKKlF2hrRPxuMM+now98iMkdrd2ToQY66PLekC6T79bo8jWrhWHeHJxR DIg0s7KU6RutqmfQYZYQNe1YKjRdfeWPsnX1p6pntaxHsQh3MswzJjAZ72EDuFtA sQ7A5SIfoxMWSd28C+ysaSOcTVAB+W0MdIEW2TocweFHNoCCRhLH+mydv8Vute6Q xQy+98cUA5+F5akPXQlVyfQIKdO9aWHMZSuL7JoNbi+phhVrhYO4A29j5Ajl4Epz qi8fC7gpN/NtryijJC8R4WKd8rCUCPmL0By1ei7ef5BHs5O83J8z6dLb+YDz/0SK QhlDsGO7NwystbXaGQJQ3oblhwpAdueBTbgV+AHBSWtyYZheDKM= =lgF+ -END PGP SIGNATURE-
Re: getting rid of "testing"
On Tue, 2019-06-25 at 16:39 +0800, Paul Wise wrote:
> On Tue, Jun 25, 2019 at 2:08 PM Ansgar wrote:
> > what do people think about getting rid of current suite names ("stable",
> > "testing", "unstable") for most purposes? We already recommend using
> > codenames instead as those don't change their meaning when a new release
> > happens.
>
> I use these (testing, etc) so getting rid of them would be annoying.
The "stable" suite names are more annoying than
unstable/testing/experimental as they require updates to suites at
release time that are not related to the release. That shouldn't be
necessary.
For "testing", "unstable" one could probably introduce some `Alias`
field in Release, but I also like minimalist solutions (which already
seem to work well for Ubuntu).
> > Related to that I would like to be able to write something like
> >
> > deb http://deb.debian.org/debian debian11 main
>
> Already kind of possible:
>
> deb http://deb.debian.org/debian Debian9.9 main
Yes, but it gives warnings for issues that I believe should be an error
instead. (And currently a good reason for TLS to talk to mirros so a
MitM that is not a mirror operator cannot give you oldstable when you
want to use unstable.)
debootstrap gives an error for this:
+---
| $ /sbin/debootstrap --print-debs Debian9.9 . http://ftp.de.debian.org/debian
unstable
| [...]
| E: Asked to install suite Debian9.9, but got stable (codename: stretch) from
mirror
+---
As Adam already pointed out having the point release in there also
makes "Debian9.9" rather unhelpful.
> > Ubuntu already has no suite names, only codenames, but having to map
> > "Ubuntu 18.04" to "bionic" instead of just writing the version in
> > sources.list is annoying (I always have to look up the codename to be
> > sure as I don't use Ubuntu that much).
>
> They do have the 'devel' suite, but it is not a proper one:
>
> https://bugs.launchpad.net/ubuntu/+bug/1821272
That is what Debian9.9 (and similar) are currently as well.
Ansgar
Accepted qtsvg-opensource-src 5.12.4-1 (source) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jun 2019 14:03:25 +0300 Source: qtsvg-opensource-src Architecture: source Version: 5.12.4-1 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Dmitry Shachnev Closes: 925815 Changes: qtsvg-opensource-src (5.12.4-1) experimental; urgency=medium . * New upstream release. * Bump Qt build-dependencies to 5.12.4. * Mark one symbol as optional to fix FTBFS with GCC 9 (closes: #925815). Checksums-Sha1: 4f14fb664530dd8a2e8aa54e3f73622c7302fabc 2814 qtsvg-opensource-src_5.12.4-1.dsc bbec375dc52e9a739b93b57152800e682aeb14d0 1859476 qtsvg-opensource-src_5.12.4.orig.tar.xz 6d3d73a0a31d3726bb99b610e87cd117db55ac00 11548 qtsvg-opensource-src_5.12.4-1.debian.tar.xz 269bf8e8634b8b1c06335eacfd04ec72bacf53c6 11603 qtsvg-opensource-src_5.12.4-1_source.buildinfo Checksums-Sha256: 4feafec1203a03234de9799314d9a8fa9c155b3c1660aa7cf8d4f5464af2ef53 2814 qtsvg-opensource-src_5.12.4-1.dsc 110812515a73c650e5ebc41305d9a243dadeb21f485aaed773e394dd84ce0d04 1859476 qtsvg-opensource-src_5.12.4.orig.tar.xz 946ead6469b044e05cf3de3eff60169a465a237049fbe89156101329ea9ebad5 11548 qtsvg-opensource-src_5.12.4-1.debian.tar.xz 6523c81276d336d0b27038c58a581ddf514505ed3c21e520d97b071b7b2f67ce 11603 qtsvg-opensource-src_5.12.4-1_source.buildinfo Files: 048a1d01b54a6248ea58383bf9dcf962 2814 libs optional qtsvg-opensource-src_5.12.4-1.dsc 58600fa4ffad742f6e2d615b7ae4c474 1859476 libs optional qtsvg-opensource-src_5.12.4.orig.tar.xz c120990498e1589f59c98e0b6f7fd608 11548 libs optional qtsvg-opensource-src_5.12.4-1.debian.tar.xz 172a88cdf40f85d0349a454e82dd8ac5 11603 libs optional qtsvg-opensource-src_5.12.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE8kKZ/xu8kBi5BqTLYCaTbS8ciuAFAl0SAHUTHG1pdHlhNTdA ZGViaWFuLm9yZwAKCRBgJpNtLxyK4A4UEACg+tRgrjqjzdGFOVLJ5uNyivN7tzgC VYzNpR1WzB7DcxIfurk1g1ZnAhgOkaq+C1Q3DVWnt766gZTPgo8cE2IhUOfgl4i0 w6HR2oz8lPqFZo7B4bUJzgW/td68Zb/US6vz4HznvVAw+WDBB1psSN7Cw7xtQEF8 hnUEsOttHBOUEY/cehwsnWfpS+NlzLd5GCXKzCaP66+BD0AN6G7UQChPmUPhmhZW lsn7NyX/d9jpCVZAZnmQok3x6MItrawky0ApYI/Ewm3wDVQK6LnvBVPNc3B/yrwQ MRxq8pE+z8njz5m4iW1cnGWVKJuu3ZjHaYzbDYEmPXkMNcI2AE/obZ899LrrwpBE w0XRqb9wujypX59+C6NDn04kI5bHmet9BB+owjp04vwe9HIrkgthMYgT3f8ZZ6Ig o6ccR+EF8uyq3xuGNlrmKx2abBSWYsmjjfpD2Or8ccammLuAIUdpEXnkf2GjASl3 vjNG4csp0HmAYk9tMPFVINDbd5cR0RA4DSAHTM5VrGAmqyYImjM1AMQcbyDRtgq5 kBx06AQA3ZWY7fCODEglaMLFdOC8vICZcR5BTXfodhOxqpvNHPsOA6ooePGYhIbl rqBJwReJJ43Svj3Ea/IaP6AIRHVNGeTbj6xM//G6K1v3ZvXWyPbYZVfSOjHHhOyC kD6qsezRhIrFGw== =l84T -END PGP SIGNATURE-
Accepted gcc-8 8.3.0-15 (source) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jun 2019 12:45:57 +0200 Source: gcc-8 Architecture: source Version: 8.3.0-15 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 930119 Changes: gcc-8 (8.3.0-15) experimental; urgency=medium . * Update to SVN 20190625 (r272643) from the gcc-8-branch. - Fix PR middle-end/64242 (PARISC), PR fortran/90937, PR fortran/90744. * Apply proposed fix for PR libgcc/90712 (ia64 only). Closes: #930119. Checksums-Sha1: 713a15af5ee89501caadb7ca93a99471b7005d34 21577 gcc-8_8.3.0-15.dsc 83214637973a443cdc0a0589384d0cbed52aaa70 839638 gcc-8_8.3.0-15.diff.gz 433b9d825607dd6350d10cfd97a440d7d78eb604 10008 gcc-8_8.3.0-15_source.buildinfo Checksums-Sha256: ec0bb0ae5b1dbf8c78dfbfdeae7dd89a6bc523eee3b5002d7efb69edf9ccedad 21577 gcc-8_8.3.0-15.dsc 8bed5202d788d7e23803d0c898ee59a0d538879bdc6a9ee36315ea0d36b08bd9 839638 gcc-8_8.3.0-15.diff.gz 866d6ae5ddc651d2c6870d255ffae92582a4a8c25c9cb0f6d3d6d12de02e3f13 10008 gcc-8_8.3.0-15_source.buildinfo Files: 2cabe8f4bdeb4e376a0062083edd0f46 21577 devel optional gcc-8_8.3.0-15.dsc 643971ceb1a05f68e6a7fab748431bd3 839638 devel optional gcc-8_8.3.0-15.diff.gz 741276d65865902d0970045e7494b352 10008 devel optional gcc-8_8.3.0-15_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl0SAekQHGRva29AZGVi aWFuLm9yZwAKCRC9fqpgd4+m9Q2GD/wKLoq/kUqeyNP7gaKxotKZQM3KCV2nuICz xSNOZNANOailXK5YOiarc7fqBqHw8NyGTlBt7btTWX8WHXtstZ9JpOKKr0KTfm+U rwAUNJ0ErYERgCSJlKxAd1fjDU+7fL1YErYcM9PhqJqTmCsjnJfB3nHwfvhjdpKC /LuAwpS8qd8chOFLb3ZFZfb2FST1UnC4cSl4FCKXGIZMK7tmkTp4QFTVdchlrkH6 pGNEZYxtSrC2bR0tbeh+vFlVGL37095fjlsrYGYW3qza6VocC47ZmbcFjVftmECv oPWGqefiQDcMVLeSYugZU6Ue2zPjXWMZNCosGax2QyljewAXWedgEmcFCh0DKJyX cVPC8NAB9fhUFFNpbgTTEDpYkWZ9L1MWdz31RjKXMjkx+OpfMPIC1tGHYWBgvEDX 04qMd/U1sDI7lbWXMqyEKbgt0WHE6OyPJ6jvTcv+KU336+EFj3gzrD96Gqy57PR/ ziv1AWFhObQytF2LK4Y/lfcgKOO05zyk6f5zWgRZnROT/sue2TNox4R0Kb2xnGja k7ke38OEGw37OfQQrjb1Ej1hYyIs44Ji/am+ia7ntuA6gdxfhn3jcGJoBHMCqEYq cyZhxobMfN/4TCgg5bNYnCpKMuAAXXI8wBPu4WpI2wQO1giLi0xXGfX9gyOcDpdc ZpbkZupiJA== =v0kD -END PGP SIGNATURE-
Accepted python-vertica 0.9.3-1 (source all) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 25 Jun 2019 13:05:58 +0200 Source: python-vertica Binary: python-vertica python3-vertica Architecture: source all Version: 0.9.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Jean Baptiste Favre Description: python-vertica - native Python client for the Vertica database python3-vertica - native Python client for the Vertica database (Python 3) Changes: python-vertica (0.9.3-1) unstable; urgency=medium . * New upstream version 0.9.3 Checksums-Sha1: 2d31323b36777efd32bd2801f7971c164d9a0336 2404 python-vertica_0.9.3-1.dsc d9a3c6a93150dda86f1599c3e43b9d5c71b3d8b6 62266 python-vertica_0.9.3.orig.tar.gz eee07f8ee714978f94ba71f5660e2cf35482a4c8 2952 python-vertica_0.9.3-1.debian.tar.xz 5d3ea714987c18441749b0b2d01c7eb721b4738a 44220 python-vertica_0.9.3-1_all.deb dcbb6dc724f9fc8dff99f0f8427408848dfd3a0d 6733 python-vertica_0.9.3-1_amd64.buildinfo 786d2b82628e0e149db4048405c3043f2db17262 44228 python3-vertica_0.9.3-1_all.deb Checksums-Sha256: 3d0476e1e8b6424b996e8e32b6afb7dce44fbb64e59a6c12f8902e5fddcbd2ac 2404 python-vertica_0.9.3-1.dsc 4809cd117d2bb15b2b49be4eea0c1f2b0ba95a78f9e2b81ac2eda4ddc6d5 62266 python-vertica_0.9.3.orig.tar.gz 8832905eecad3578b312e9d10454bdc834ceed6eeacd6356e2cc407ce5f394ac 2952 python-vertica_0.9.3-1.debian.tar.xz 088a58eaea34b73d0b144bab92b3813ec897a40dec8095ea1ddaf6ebd78014c1 44220 python-vertica_0.9.3-1_all.deb 5077473dfdc93639078963834e6f5484bd252044e02b0390ae3f6fcba4d4ff85 6733 python-vertica_0.9.3-1_amd64.buildinfo 9aa5c44156d34061eaef6ce4a18bed73e24a2690df40c5806b326d7f69823371 44228 python3-vertica_0.9.3-1_all.deb Files: 5c29eecfb466e1047ebdd051c759a69a 2404 contrib/python optional python-vertica_0.9.3-1.dsc b3795e2f4db32b2c6f5f24781239e579 62266 contrib/python optional python-vertica_0.9.3.orig.tar.gz d68c683d45d155247960d02416e6cbfb 2952 contrib/python optional python-vertica_0.9.3-1.debian.tar.xz 131c9c56c1d27f893e5503f04a2c47a9 44220 contrib/python optional python-vertica_0.9.3-1_all.deb 27fb3a24bd78ac4c48d6d61ec8da21a3 6733 contrib/python optional python-vertica_0.9.3-1_amd64.buildinfo fc58c938cecd31501853da44415a6d73 44228 contrib/python optional python3-vertica_0.9.3-1_all.deb -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEToRbojDLTUSJBphHtN1Tas99hzcFAl0SAidfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRF ODQ1QkEyMzBDQjRENDQ4OTA2OTg0N0I0REQ1MzZBQ0Y3RDg3MzcACgkQtN1Tas99 hzdSWw/+PtlXSRYEx7qNDNtRjvCX4bQbuVclytz3O6dJh4chuf6XtDt/vX1h58+H nvyQxXjD0eUsq9OgVHWbaJfSc7WxpcYr2Ad+P/fY3kd4R+2uDaNyjrhRf0jBd3l0 JMw9Hf86U8ZxtKuolPd5aR5Cq0CB/FVvcba6SCWhlphblzo22EZE9dlJH9wQ7ZoJ LXJo1Op5JHHCx7ByYGI3Q6zeS+o4mJRz5KjKWJjfG9lO/zl6q+bRB/+14UBitUkH 4mFUZyzh+LvdyIg2mzGb1Zi0iENDSkI7X+aM/BkEETgG9G30IHMxZ6X9plO+UWWa ziiycnUKtTixaEMlX9QRGySefF3Nf1TZZM9Y8Erpil8x8R9gGJYyo3+mco+yVT5v YEUkJ3IkpgSOMZz0B1GCBAHf6YYLdCDikymtqCMuF0Nv7vEyuZfCxvlWkYG/zC2r reZxg9CCDbsWC8SNFSjR3f0LcOwQWYltWkYPZoeqCZ457Ad4iISl7EFlPboSSOja GnBkgVDxBVBKZKbXhOwTpUfPZRCVuoYxlEBvu4XkseT3E23Uzc45T6E9se3HbOep q/y/jdj7no5vfPs0ASU6WmycJiQUe7+s+eyiYPZC1fD4mDyFjHDpldYmY6hl7HKG +zfPx5Z4Ph6hIs2a0iR77AvGVulTpIlCakIHGeii0WLY9stkGiY= =a2K7 -END PGP SIGNATURE-
Re: Content Rating System in Debian
Hi, On Tue, 2019-06-25 at 11:40 +0700, Bagas Sanjaya wrote: > Based on above, what are your opinions/thoughts/positions about > Content Rating System in Debian? is this related to your other proposal involving giving "sudo" permissions to teenagers to handle this age recommendation stuff for TV programs? | In fact, many television stations have most programs written for | teens (age 13 and older), so sysadmins there configure sudoers which | allows teens to behave like sysadmins themselves (by giving them full | administrator privileges) on their production systems. Also, parental | monitoring and guidance can reduce likehood of teens breaking such | systems. Maybe because teens are largest marketshare for TVs. Ansgar - rating "kill -KILL" X-rated for extreme violence
Re: Content Rating System in Debian
On Tue, Jun 25, 2019 at 11:40:04AM +0700, Bagas Sanjaya wrote: > Based on above, what are your opinions/thoughts/positions about Content > Rating System in Debian? just NO. please create a fork and leave Debian without this. -- tschau, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Re: Content Rating System in Debian
On Tue, Jun 25, 2019 at 12:43:56PM +0200, Paride Legovini wrote: > My question is: are we trying to solve an actual problem here? No, and please note that the author is not even a Debian user: https://lists.debian.org/debian-devel/2019/06/msg00376.html -- WBR, wRAR signature.asc Description: PGP signature
Dotyczy Twojego FanPage. Sprawdź.
Dzień dobry, w związku z ciągłymi zmianami jakie zachodzą w social mediach, kontaktujemy się z Państwem,aby zaproponować profesjonalne prowadzenie *FanPage na Facebook’u. * Dzięki zdobytemu doświadczeniu, możemy Państwu zapewnić: -zwiększenie liczby fanów -brak długoterminowych umów -brak ukrytych kosztów -wzrost Państwa sprzedaży. Aby móc Państwu przedstawić więcej szczegółów w tym zakresie, prosimy o odpowiedź o treści *Tak. * .. Z wyrazami szacunku, Prowadzenie FanPage
Re: Content Rating System in Debian
Bagas Sanjaya wrote on 25/06/2019: > Hello Debian Developers, > > Debian provides more than 51000 packages. From those packages, some are > appropriate for every ages, and some others are > only for specific age groups for some reasons. > > In order to inform to users, especially parents, about potentially > objectionable content in Debian packages, Content > Rating System (CRS) can be deployed to Debian. With CRS, users can choose to > install packages that is rated for their > age. In some cases, CRS also filter or block certain contents in certain > jurisdictions when legally required. > > As in Google Play, Debian CRS is based on official ratings from International > Age Rating Coalition (IARC). The rating system in Google Play makes some sense (at least on paper) because you can leave a phone to a kid, configured with their Google account, and Google will allow to install only apps deemed appropriate for the account holder's age. There is no such a thing in Debian. There isn't a Debian account which is able to give you partial access to the repositories. If you are root you can install everything; if you aren't you can't install anything. And when installing a package for a kid then checking its description is probably better than any rating system. We can't achieve the same result as Google, which in my opinion wouldn't be useful anyway; see below. > Pros: > - Users, especially parents, can install packages suitable for their age. In > case of parents, this apply to their > sons/daughters. I don't think there is a meaningful "Pro" here. The first and in most cases only packages that would make sense to control are web browsers. Nowadays not installing a web browser makes a computer almost useless for almost any purpose a kid or teenager may want it for. At this point it's just better to install a browser and leave the machine offline. At least they'll have access to offline documentation! Or to a local Wikipedia mirror. > - For users in some jurisdiction, they can only install packages that is > legal in their jurisdiction. For example, Debian > users in USA can only install US version of GnuPG, but in outside USA, users > can install international version of GnuPG > instead. Didn't this stop to be a thing in the late nineties? The issue wouldn't be age-related anyway. > Based on above, what are your opinions/thoughts/positions about Content > Rating System in Debian? My question is: are we trying to solve an actual problem here? Are there packages that you would consider not suitable for young users, and whose impact wouldn't be greatly inferior to the one of web browsers (which, in my reasoning, are going to be installed anyway)? I hope the answer is not fortunes-off here :-) While this email is mostly a "thumbs down", I agree with Russ Allbery: if a group feels strongly enough about CRS to do the work, I think it will fit well in the debtags labeling system. Paride
Accepted ompl 1.4.2+ds1-4 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jun 2019 10:21:42 +0200 Source: ompl Binary: libompl-dev libompl15 ompl-demos ompl-plannerarena Architecture: source Version: 1.4.2+ds1-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Leopold Palomo-Avellaneda Description: libompl-dev - Open Motion Planning Library (OMPL) development files libompl15 - Open Motion Planning Library (OMPL) ompl-demos - Open Motion Planning Library (OMPL) demos ompl-plannerarena - Open Motion Planning Library (OMPL) plannerarena Closes: 931000 Changes: ompl (1.4.2+ds1-4) unstable; urgency=medium . * Changed maintainer patch to upstream patch to solve pkg-config bug. * Changed libode-dev Suggest in libompl-dev to dependency. Closes: #931000 Checksums-Sha1: 7695b51c782c7d79eca351059ccc532303ef7d63 2376 ompl_1.4.2+ds1-4.dsc 6fc0b4c8ef584fc4e3380604761171aed3127ba1 22757110 ompl_1.4.2+ds1.orig.tar.gz 929cf614cceba291e6d4299bc4c1220e1a76728a 7808 ompl_1.4.2+ds1-4.debian.tar.xz f7f0d03c1d8015db18cb8e53d4e2ccdacc478488 10969 ompl_1.4.2+ds1-4_source.buildinfo Checksums-Sha256: cafb3683e5b42512cd77fcb7d17f6cb79f9eea01d7e20a5e0e5805dbde9d100e 2376 ompl_1.4.2+ds1-4.dsc 3cc8df5dcd5bd93ef36ca8c41962f06ac64a64e6c5f6878c261598b3aa9261b1 22757110 ompl_1.4.2+ds1.orig.tar.gz 0d16c2c58f0bc03a81e41d73fa04ebdd456224d1ccfb97d530da4042c3aa7eaf 7808 ompl_1.4.2+ds1-4.debian.tar.xz 5457773c32bd18b46ad8b9b5e4a4d1ddc1d373b1a54a04a66da71e5d1f7b791f 10969 ompl_1.4.2+ds1-4_source.buildinfo Files: 35598063c013d36c9bd3253aa81022b5 2376 libs optional ompl_1.4.2+ds1-4.dsc 39154fd1cca64da7289ecee222a3091f 22757110 libs optional ompl_1.4.2+ds1.orig.tar.gz 2eb1192b836f0bd8b7d72b298b4a7547 7808 libs optional ompl_1.4.2+ds1-4.debian.tar.xz 2104d2ebda95ff3a53cd8d40d9d21dea 10969 libs optional ompl_1.4.2+ds1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEjF/vEZvRbmgP2ZRLBfSnqUmi2aoFAl0R88YACgkQBfSnqUmi 2ariow//aQ2d9IaWT6j39eDIWo7e8V+pX8BESWDp47l98xgbc5TO8np6sug/EGe2 4zph3y5XMwOb5YgMj/yZ3uS6qWJ7Vjek+Z3WrHmeuBw+hXmRc8RAvNXxkX4mbSw8 SjKdkaBahXtkykD+NcE5iIb+uMdN8uLsuFhLXcnJs4h7R+eHJEsBYTameFPTodGz 2IGt4WB+M9KILsBR2epq5EYSxjol9dpW91Bn7siC8MUx2vDnM+X4q6dU0fSb/3KB qNXhi6HtHATdkVFv7N248YvbMqab/RRU4+MPKq2K+WWDbekxR7ddkXCkMrXV8GaP UPAXkA3GJUukvD8o4O3o0F8PZgsO/2dBb4uC0O19zTcYvyfeQWva78xR16Prv5SW Wed63JRgwvtuQosmthhHrOzHdus89HaPmjfYIPVFAy0OPf7WoaqBblvgGGlkLQcy jIzOcvzdy20le6Z/wPs3u+/GlAhi9MJqNVI0iTzQis9dCKxVfp8+RTAt8dL+BfYM 8mHkrKjOyukDlL6JKpoBiAe9u+vwe79FBSeF2/R9SzEm6eU9kXZhzmwgkbiOSN01 /U2Symlxwa/X/zTO3EuzkYsB0iQVZVvETK1Bwl0kFy0d9OAFRTEGQ4WJ7EjN5DZE yAXRmMHc6wUm1b70W0FKqyzSm7W44ePBabejm8m/M748yAI2Ri8= =z0bf -END PGP SIGNATURE-
Re: Content Rating System in Debian
On Tue, 25 Jun 2019 at 16:33:53 +0700, Bagas Sanjaya wrote: > There are no age classifications, however. So based on content_rating tag on > AppStream metadata, we can add logic to apt in order to determine age rating > for our packages. I think this would be unwise. We can never get this right, because the descriptors that are considered suitable for a particular age vary widely between cultures and countries. The most likely outcome would be angry bug reports from parents who felt that the given age rating was inappropriate. Something like OARS is already somewhat subjective (how much violence can a game have and still be considered "moderate"?) but it's a lot closer to being objective than an age rating. smcv
Re: getting rid of "testing"
Ian Jackson [2019-06-25 11:09:06+01:00] wrote:
> ~Ansgar writes ("getting rid of "testing""):
>> deb http://deb.debian.org/debian debian11 main
>> deb http://security.debian.org/debian-security debian11-security main
> Yes, please, absolutely. And this should be the default.
> The syntax "debian11" is precisely right. Please don't add a hyphen
> to it, as hyphens are already used for separating things like
> -security.
> For now, the `debian11' can be an alias.
As a mere user I'd say this is the best approach: add debian10, debian
11 etc. alias or perhaps later make it the proper name.
My first Debian was Woody. I remember that Sarge was after that, then
Etch or Lenny (I think), but it all started to blur at that time. Now I
know that I'm using Debian 9 but don't remember its name. I don't
remember what was the name of the previous version.
I think it's best to use version numbers for communication with users
and to configure Debian (like sources.list).
Anyway, thank you for this excellent operating system.
--
/// Teemu Likonen //
// PGP: 4E1055DC84E9DFF613D78557719D69D324539450 ///
signature.asc
Description: PGP signature
Re: getting rid of "testing"
~Ansgar writes ("getting rid of "testing""):
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
Others have pointed out that "testing" has a specific value. Also,
these suite aliases have a documentary value. It can be helpful to
say things like "when this is languishing in oldstable ...".
So I would prefer to keep them.
> Related to that I would like to be able to write something like
>
> deb http://deb.debian.org/debian debian11 main
> deb http://security.debian.org/debian-security debian11-security main
>
> in sources.list as codenames confuse people.
Yes, please, absolutely. And this should be the default.
I know the codenames thing is fun but it is seriously inconvenient
when talking to anyone who is not completely steeped in Debian stuff.
Even Debian people sometimes make slips - and I'm sure they are more
common because we're having to constantly do these kind of codename
lookups.
I agree entirely with Simon.
The syntax "debian11" is precisely right. Please don't add a hyphen
to it, as hyphens are already used for separating things like
-security.
I don't think I have any software which would go wrong if there were
an extra hyphen but I would be amazed if there weren't a ton of ad-hoc
scripts out there that would be fine with the transition from
`bookwork' to `debian11' but would Go Wrong with `debian-11'.
For now, the `debian11' can be an alias. At some future point this
should become the canonical suite name, replacing the codename. But I
think this should not be done retrospectively to old suites, because
there is software outside the archive that wants to name things by a
single canonical name, and changing that name for an existing suite
will cause trouble.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Accepted grub2 2.02+dfsg1-20 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jun 2019 10:11:12 +0100 Source: grub2 Architecture: source Version: 2.02+dfsg1-20 Distribution: unstable Urgency: medium Maintainer: GRUB Maintainers Changed-By: Steve McIntyre <93...@debian.org> Closes: 931038 Changes: grub2 (2.02+dfsg1-20) unstable; urgency=medium . [ Steve McIntyre ] * Make all the signed EFI arches have a Recommends: from grub-efi-ARCH-signed to shim-signed, not just amd64. Closes: #931038 * Add myself to Uploaders Checksums-Sha1: 66c76040fb5c7e99da361c12f3b8fef264511003 6878 grub2_2.02+dfsg1-20.dsc 7c4c921871ed0cf31133e09721f3c3105a20ec1e 1135984 grub2_2.02+dfsg1-20.debian.tar.xz 778908e49d90f3cbe19ccf8e72e535a5640397f0 14368 grub2_2.02+dfsg1-20_source.buildinfo Checksums-Sha256: 22fdd888f9dad90061767e32d3240f640532b9bf1fd32355acbeeda03dd5326a 6878 grub2_2.02+dfsg1-20.dsc 0a15d960600089cc6261a0321ec0dcf91c9cefb2d47d6cfee2591a43c7aec41a 1135984 grub2_2.02+dfsg1-20.debian.tar.xz b4b90f9726fc4a69bd17cb162877a6636b109cf0f868829af79146ab7ea64a33 14368 grub2_2.02+dfsg1-20_source.buildinfo Files: b8901f7498c2f0417a314d4ceb0bcbce 6878 admin optional grub2_2.02+dfsg1-20.dsc 800b08383ff6f4896913f318ac46cf51 1135984 admin optional grub2_2.02+dfsg1-20.debian.tar.xz b891eeb7d402555e3a8e9dd2edc80a1b 14368 admin optional grub2_2.02+dfsg1-20_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEEzrtSMB1hfpEDkP4WWHl5VzRCaE4FAl0R7DcRHDkzc2FtQGRl Ymlhbi5vcmcACgkQWHl5VzRCaE57fBAAuC38D/oIWAhfQpCwtEDEfO+E36WGzZO0 VPuMBwx1lkZmSyLD5VX36r6sV6qUsSL92DrJXTkqqDl1dJ/Y6zmhATgXd3VPtC82 uajigR84KAcjE0fmaivHdaXiPb8xWu76OIOhzQLr+w3J7lGWVQ3mRiO2cN7S1cy8 RRwNMdNrdntfku/TiBsIaw33Qwc4OuflMkiitGyDI0aeiSn26LfYGYCrCo20pghF KTn6yOTg1CTwPTqpIA9GHclVH3piAI8Koff/GzwZPk2kiHjbd8lT7Mw0svmK7UfU oddPGHDPJBnqnV3X/LiHq4zWjLVRida47v5eVSQRP4HrVwlNcyPAI2WmMe+/R2nj vn52UMDKUEupeGQ9U8idLa+AFy3cGQFUYiFzxbuVaseRIqs1u6awpP0CgzjsYHD+ /hqeQuzdyBkn1YnghaMik3HIt1nMbUxodpuaUszau3oL1OZ+4Q0SF+pe4r7/FYB4 a45Fc83aFfjk5iIz84dhAhvbS95e5cWsQskgI8kUajPvO9ChEV6/tFQQmHguqpcE +k4s/dGamqPe2945tQBS3Ewe1YH55iflpxGDypHzaNv/mmllCKHZSCVZnia+6BW7 HrHod6ZgZ0e4216by7Y7sgMKyrZOc/NQK5JctUWfREm1lu87YWdXxbDQpu+ziJBG hL2fT9cgCJA= =T3YJ -END PGP SIGNATURE-
Re: Re: Re: Content Rating System in Debian
Simon McVittie: Appstream metadata, which is canonically provided by upstreams and is distro- and package-type-agnostic (available in at least apt and Flatpak), has this as an optional field for self-rating: https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-content_rating https://hughsie.github.io/oars/ I suspect that's the only way this could possibly work without money changing hands. There are no age classifications, however. So based on content_rating tag on AppStream metadata, we can add logic to apt in order to determine age rating for our packages. However, external review (maintainers) may be need in order to prevent misleading information on content_rating.
Re: Why do we take so long to realise good ideas (Was: Difficult Packaging Practices)
On 5/29/19 11:01 AM, Raphael Hertzog wrote:
> On Wed, 29 May 2019, Ansgar wrote:
>> On Wed, 2019-05-29 at 10:38 +0200, Raphael Hertzog wrote:
>>> On Wed, 29 May 2019, Andrey Rahmatullin wrote:
One of the popular answers to this and some other problems is "nobody sat
down and wrote the code". Not sure what can we do about this class of
reasons.
>>>
>>> Use the $300,000 on our bank accounts?
>>
>> I heard that this didn't work out well the last time ("dunc tank"),
>> though that was before the time I followed Debian development.
>
> Yes, I was there (and mention it briefly in the questions of the talk I
> gave) but it's been a long time ago. There are things to learn
> from this failed experiment (such as "don't let the DPL decide alone who
> gets paid") but there are also many reasons to believe that we are no
> longer in the same situation. At that time, the number of persons working
> on open source as part of their paid work was rather low and the jealousy
> aspect was likely more problematic than it would be today.
I clearly remember that one heated topic was about the level of salary
for a release manager. Many thought 6K USD was too much and were shocked
about the amount. I probably was at the time. Now, I'm 43, I have
children, higher life cost, and responsibilities. I'm not shocked
anymore, but I can easily understand others would still be.
Let's *not* start this again.
> The topic still needs to be approached carefully
Yes.
> but I believe that we
> should aim to have this discussion and build some framework where we can
> leverage money to complete projects and tasks that we find important
> but that have not gone forward through volunteer work.
I'm not sure if I'm in the favor of Debian slowly transforming itself
into yet another world company.
Cheers,
Thomas Goirand (zigo)
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 08:08:22AM +0200, Ansgar wrote:
> Hi,
>
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
And for this exact reason so many people want "testing" not "buster".
This way they get 5-days-newest versions of everything, without having to
suffer broken uploads, broken dependencies, etc.
Using "buster" would mean that at some moment their updates suddenly stop,
and they have to manually migrate to the next version.
> Related to that I would like to be able to write something like
>
> deb http://deb.debian.org/debian debian11 main
> deb http://security.debian.org/debian-security debian11-security main
>
> in sources.list as codenames confuse people.
Hell no! Even though I'm among most active DDs around, I just had to look
up whether "debian11" means Buster or Bullseye.
It's same eg. for processor names: "Skylake" means Skylake, which is used
within 6 or 7 different numbering schemes. Even people who care what
processor that is will so often need to look up versioning numbers -- as the
public names are about marketing segments and so on, not about how a
processor behaves.
A code name is also so much easier to talk about, especially in speech -- a
codename is one or two fairly unique syllables, while a number is longer,
and it's usually surrounded by other numeric values within other semantic
domains.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Packager's rule #1: upstream _always_ screws something up. This
⢿⡄⠘⠷⠚⠋⠀ is true especially if you're packaging your own project.
⠈⠳⣄
Accepted dkms 2.7.1-1~exp2 (source) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jun 2019 11:09:04 +0200 Source: dkms Binary: dkms Architecture: source Version: 2.7.1-1~exp2 Distribution: experimental Urgency: medium Maintainer: Dynamic Kernel Modules Support Team Changed-By: Gianfranco Costamagna Description: dkms - Dynamic Kernel Module Support Framework Changes: dkms (2.7.1-1~exp2) experimental; urgency=medium . * QA upload * Drop trailing newlines * Use DEB_VERSION_UPSTREAM to guess upstream revision * Drop old get-orig-source target * Bump compat level to 12 * Bump std-version to 4.3.0, no changes required * Apply UEFI patch from Ubuntu, it is not applied in Debian (removed in debian/rules conditional statement) Checksums-Sha1: f8fcda3ba15279961558ef21fabf780473384660 1986 dkms_2.7.1-1~exp2.dsc e75a30bebf880d21ad1f2ef8f85507453b0edd8a 20592 dkms_2.7.1-1~exp2.debian.tar.xz 304904009951d0bd9757955d676bc0f5959826d5 6972 dkms_2.7.1-1~exp2_source.buildinfo Checksums-Sha256: 585ee97162421a52f19cf2f36bc74cf4571a65d9bf615db6cb4e22d9e74874a4 1986 dkms_2.7.1-1~exp2.dsc cd916665b2fa33e3f9a25989c6fb3ab50fbc01e489827d23025d1a1d69c672d6 20592 dkms_2.7.1-1~exp2.debian.tar.xz 7170118544bc447fa9ac4a9f85529c2a35aeefefecea6d3e8b93603df396ca05 6972 dkms_2.7.1-1~exp2_source.buildinfo Files: 002f93500b76b91ff0974e16c573c491 1986 kernel optional dkms_2.7.1-1~exp2.dsc 6e9fc0b16247de95941a21222ef3f2bb 20592 kernel optional dkms_2.7.1-1~exp2.debian.tar.xz d2a50f929e12d03a5892820819d8ed15 6972 kernel optional dkms_2.7.1-1~exp2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl0R5h8ACgkQ808JdE6f Xdl4pg//ZQFGUrmq+PColJfZd3+ttdPCABQYL0VNzVVYfRKDAj3DRk/XbhLkp3sz zD90wlM6nT758qvouW5CDrTDSeB7nNhezIzUNRT30m2jI5d6S2DMv4WYmJtim+PY kuhx3Rw9TfZMiqxuwERI6ONo0nLaPAp/vxCj3vqaJJ325W+5j5JKbWE1pVd+Co3x qgzFJ4EiNTCtY6nf7uLakzJyt3gckN4SpDD5f2UKvTS3V3bQxbVziujfL3WkgqBR nJ5rIHuBMXvYKBiOtrbqECnS54qPF5tWZywJGNr4jJIOt15kwHabl5JOHR8ua4zX mruM90rgM7yn8r41XyYjJ5EYWbTFmzCWRLyjHyx/FknBUQcG6WRQ9YC2mSdRkZQl Gwz/IVfdRmkwZ8NYLZFpt+22hsfTbua6h6WDkjQNFgoNjf+iZ5B9v0jvVahGt9D4 RkL4/gKzURL2P7mHktQPi1v8XhpNP4BRr5K9eqVrl+h0gb+s8VT8O68I1y8NcuWm v0UVIQRu8CywdIwse4yb16kowG6SipAg9+kPQnnX1CFm/CK6zwm1Dg0YV4iAwQZy N3tuD1Iekf9ustdY5pW4lltlwhy5FMuYw675gGo6dL94Q/OHFJgM2GcCDfvATzyA ZOvS8Va/NHY756jxQH2KsWwTfuRrF51PRtHVIIAE1VKjaJPdF38= =aQBb -END PGP SIGNATURE-
Re: getting rid of "testing"
On 2019-06-25 09:39, Paul Wise wrote: On Tue, Jun 25, 2019 at 2:08 PM Ansgar wrote: Related to that I would like to be able to write something like deb http://deb.debian.org/debian debian11 main Already kind of possible: deb http://deb.debian.org/debian Debian9.9 main With the caveat that as soon as 9.10 happens, the 9.9 symlink will cease existing. Regards, Adam
Re: AMDGPU+OpenCL with Debian?
Michael Kesper schrieb: > On 18.06.19 22:55, Moritz M=C3=BChlenhoff wrote: >> You may find https://phabricator.wikimedia.org/T148843/#5078403 >> (and later) interesting,=20 > > This seems to require wikimedia authentication. > Is there some information publicly available about it? Ah, that's just an artefact of the URL, simply use https://phabricator.wikimedia.org/T148843 which doesn't need any login. Cheers, Moritz
Re: Re: Content Rating System in Debian
Am Di., 25. Juni 2019 um 10:15 Uhr schrieb Simon McVittie : > > On Tue, 25 Jun 2019 at 09:31:44 +0200, Philip Hands wrote: > > Also, it seems clear to me that the same game in all Linux disros is > > very likely to get the same rating, so this would be better done as a > > distribution agnostic level > > Appstream metadata, which is canonically provided by upstreams and is > distro- and package-type-agnostic (available in at least apt and Flatpak), > has this as an optional field for self-rating: > > https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-content_rating > https://hughsie.github.io/oars/ > > I suspect that's the only way this could possibly work without money > changing hands. Indeed :-) Also, metainfo files can be written for every software component, not only for apps (although I thing GUI applications are the things age-rating is most relevant for). If any features in this are missing, let me or Richard Hughes know. Cheers, Matthias -- I welcome VSRE emails. See http://vsre.info/
Accepted dkms 2.7.1-1~exp1 (source) into experimental
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 25 Jun 2019 10:45:13 +0200
Source: dkms
Binary: dkms
Architecture: source
Version: 2.7.1-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Dynamic Kernel Modules Support Team
Changed-By: Gianfranco Costamagna
Description:
dkms - Dynamic Kernel Module Support Framework
Changes:
dkms (2.7.1-1~exp1) experimental; urgency=medium
.
* New upstream release
* QA upload
* Drop upstream patches:
- {63,6ef1a48eda99ec0d728302830483fd0137174d17,bash-completions}.patch
Checksums-Sha1:
72c4f138de256217386feb32069f2c7fd7a70c79 1985 dkms_2.7.1-1~exp1.dsc
f01da021a541a08be7bcc4c7d9c84caf618be0a9 102190 dkms_2.7.1.orig.tar.gz
5f4ca9cc0b65486f452307be01fab6eaef6493ea 20300 dkms_2.7.1-1~exp1.debian.tar.xz
32bc2d04555d270b6645cafe021f8faf0c826a6e 6972
dkms_2.7.1-1~exp1_source.buildinfo
Checksums-Sha256:
106ec070ea5b04521d4faf0a7156b2e499d751fa4232eb41d081dc033fb4839f 1985
dkms_2.7.1-1~exp1.dsc
b30408db599367d8268e3db8de81ff0ad4d0d6da56f426f768baee5c22c15a69 102190
dkms_2.7.1.orig.tar.gz
b70befffbf417c544691c1f9d8c7372e832a96592a7a1a4229f3666d45b3e6c4 20300
dkms_2.7.1-1~exp1.debian.tar.xz
88b887c27b87127d2822e92bed88df96161014b00e79aaf8c7f7230ed0fa4e2e 6972
dkms_2.7.1-1~exp1_source.buildinfo
Files:
fd2d51114e799d6a50ad16e5c2c12c74 1985 kernel optional dkms_2.7.1-1~exp1.dsc
3b24016722f1c1aa931fdab4a1e25c64 102190 kernel optional dkms_2.7.1.orig.tar.gz
5ae4bccc756e8700f2559ec7285b7f56 20300 kernel optional
dkms_2.7.1-1~exp1.debian.tar.xz
fe97dc9af2ff94fa4f488eca69a380d8 6972 kernel optional
dkms_2.7.1-1~exp1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl0R4DAACgkQ808JdE6f
Xdk+/Q/8CcPXc7sjX3PgjS5XEKDg3TBQA5SHctrQi3i5wSv94xwtcLNOD4mN0gyL
+Qct3beca0mj8ZpOWhCgVEG6//NNKlAPCTYGWbleAd5Lqif4xQl/d0Dv0GeQ6EV4
FolvJ3RoFuFmC/F0twDW+N4bZb9qfaHU3AUIu/cZurlynhkqgSU0T0gDsEQKhJ45
jnUoCf07u2VYxiDzibdZ+09TH2FzTo7TvRqCMZBD9IzmngdBdUJ6CywFIZhu8m9g
1LhXw+mWVFtMmp4kjPs0nIrEutwgevgtqCTOSE6htnIU1QIAtJXpBe7ZgfP6DF3T
3IhxiF7IA3/++ELlJW/5qqfdQLQkNJctIkRHHaI/pb2k45fX2P8Be5Z1CHuZTeVm
h15cUUKOwxOejI50iwvhC1in6x7L/h+m5aPSdWkoFw3/XeL8DhshzP4prWykxScS
D+kvBmZunVgR3uEsazVKVgTq2uQ4lELs8tcV9+Zzy9dw95jLKgT5b80FucTOJqlT
VQmcJU8gikG0ECh8SeITQHGoXcOVnhiFpDH+qLqtl08GyyWAD+9A4R7ccyfhRcL7
CksgaRO7AqYV7SDqaxrluehThJLoxQZyfMrIaoTp+6klbWZELuq4ddm55/g4tjrL
Hh8ZvOKQckXUoppoaDxgOKpuAFs/aZmutQzvVZ19YnRW+3HKXLo=
=Mx7e
-END PGP SIGNATURE-
Re: getting rid of "testing"
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2019-06-25 09:46, Bastian Blank wrote: > On related notes: For Azure we currently plan (yeah, still not > finished as MS does not provide input, be we still need to change > it): - debian-10 - debian-11 - debian-sid And docker hub have some similar things with the version tags. stable, 9 and stretch are the same target. And for those not familiar with the docker targets: $ docker run debian:stable cat /etc/debian_version More info https://hub.docker.com/_/debian/ I can see good reasons for having the classic names still (testing, unstable and so on) - the great benefit would be to have the version numbers available as well. Different audiences in target I think. - -- brother http://sis.bthstudent.se -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEVlIsX3Eri6ICyZwJOIRDexPY/4sFAl0R4Z0ACgkQOIRDexPY /4tOLA/9EYugAyJWehITg2mpOS0oE75nV1e/UAO1SczBiWNC+io9ostWaANaR4xT eEMLnHfZCtVmiJYlCvepcK6EnSD42vx5nrVbFTUZR82AYR2QyL5yKbYoYUNzC3Px Nj4g2KFzAscr7KXJ6arXdP9GqJmIJR7vao3T0z0TXVcL/gpfyN3kYVt82f99Zpzp 0qAewKZLq5hmhBRSnYHioqWes6WvdybMHzsG9uwVLzuVCTJQQ5BcqXrgBuXJPQG5 5/xhbIxnFpbN74XoiGIydvrPmF2/CcYGGMd8lVS0dwpQbBeTe6wqXOx+edqj3Ioo eSOz8IoQeGVae0THUDSH+Ezp1UMblK47oB/erzyvy3FEufvsyuLxjdz/KuLwL2/H 0uzxhRN5jOlGg+xzR1WeOcxyjrQEKv5sVcuNla64QNuzDopnJqd2gEnxAGiRMKcK N/ftpXRo7WJrROBNu51+hSHxGuACJVajsrE1qQqvCR65ycoRWGj/twABD+HTJ4hm S8392KXpVRqQmFMfZs+u7JPiCAxzzcOmgDolhYZxljNoBRsAosRJfEQvH/tGLpU3 lAbHkzhMjeZ2SmXfFPy11cHbQQVLhBw3C7QZaZaLbxUwVqEMaqQyi8KLlj2DNsP/ jzW2NOXdHogUXL6u6ZzgbDlHAR++lhomKVApYcPaAp8P/b/5J7k= =vGqi -END PGP SIGNATURE-
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 2:08 PM Ansgar wrote:
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
I use these (testing, etc) so getting rid of them would be annoying.
> Related to that I would like to be able to write something like
>
> deb http://deb.debian.org/debian debian11 main
Already kind of possible:
deb http://deb.debian.org/debian Debian9.9 main
> Ubuntu already has no suite names, only codenames, but having to map
> "Ubuntu 18.04" to "bionic" instead of just writing the version in
> sources.list is annoying (I always have to look up the codename to be
> sure as I don't use Ubuntu that much).
They do have the 'devel' suite, but it is not a proper one:
https://bugs.launchpad.net/ubuntu/+bug/1821272
--
bye,
pabs
https://wiki.debian.org/PaulWise
Re: getting rid of "testing"
On Tue, 25 Jun 2019 at 13:11:09 +0500, Andrey Rahmatullin wrote: > On Tue, Jun 25, 2019 at 09:46:00AM +0200, Bastian Blank wrote: > > Can you please elaborate on the "confuse people"? > > I guess only (most?) Debian contributors and hardcore Debian users > remember the order of the codenames and their mappings to current > stable/oldstable/testing and to numeric versions. Yes, exactly. This is a frequent request from those of my colleagues who mostly use other distributions, but occasionally have to interact with Debian, and can't remember whether stretch is older or newer than jessie. This is going to be particularly bad after the buster release, when buster and bullseye are current, and even worse after the bullseye release, when buster, bullseye and bookworm will all be relevant. Ubuntu is easier in some ways (because the alphabetical codenames go in a logical sequence) but harder in others (because the distinction between LTS and non-LTS isn't obvious from the codenames). Back when the release team decided on a per-release basis whether this was a "major" or "minor" release, we had the excuse that we had to use a codename for testing because we didn't know whether etch would be released as Debian 3.2 or Debian 4.0; but now that we've decided that every release is a major version, we can predict well in advance that Debian 10 will be followed by Debian 11 and Debian 12, so there doesn't seem a whole lot of point in obfuscating it. With more emphasis on the version numbers, my non-Debian colleagues would still have to learn (or look up) which release is the current stable, but given that information they would immediately also know which release was the previous one (subtract 1) and which release is under development (add 1). Referring to testing in speech/writing as something like Debian 10 alphas/betas/pre-releases (to express that it *will be* Debian 10, but it isn't really Debian 10 *yet*) might make more sense to non-Debian people, and might have the desirable side-effect of having more Debian contributors get the message that it's a means to an end (making the next release happen) rather than a product in its own right. In machine-readable contexts like sources.list it's probably best to use something like debian10 (or deb10, as in stable updates' version strings, or just 10) so that it doesn't have to change on release day. smcv
Accepted neutron-dynamic-routing 2:14.0.0-1 (source all) into experimental
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 25 Jun 2019 09:40:51 +0200 Source: neutron-dynamic-routing Binary: neutron-bgp-dragent neutron-dynamic-routing-common python3-neutron-dynamic-routing Architecture: source all Version: 2:14.0.0-1 Distribution: experimental Urgency: medium Maintainer: Debian OpenStack Changed-By: Michal Arbet Description: neutron-bgp-dragent - OpenStack Neutron Dynamic Routing - Agent neutron-dynamic-routing-common - OpenStack Neutron Dynamic Routing - common files python3-neutron-dynamic-routing - OpenStack Neutron Dynamic Routing - Python library Changes: neutron-dynamic-routing (2:14.0.0-1) experimental; urgency=medium . [ Thomas Goirand ] * New upstream release. * Removed package versions when satisfied in Buster. * Fixed (build-)Depends for this release. * Standards-Version: 4.3.0 (no change). * Generating the policy file with oslopolicy-sample-generator. . [ Michal Arbet ] * Change driver ryu to os-ken driver Checksums-Sha1: ee59635b187beaf32ca2ca4d776ee480d288ade7 3157 neutron-dynamic-routing_14.0.0-1.dsc 6f7203aecaf57843d16ae878764868f3130d1949 110450 neutron-dynamic-routing_14.0.0.orig.tar.gz 885691c96c5e03e25cb1591656389c2cb7aa3c2a 6652 neutron-dynamic-routing_14.0.0-1.debian.tar.xz fbd9eb17b1c575ee08ec193e3ab5951c0c412142 6716 neutron-bgp-dragent_14.0.0-1_all.deb 906948607f15b53c4c05d8c7b5b67d4cc8d94e7b 15252 neutron-dynamic-routing-common_14.0.0-1_all.deb e498b9f7614fee755f11c73284707e65fb5279d6 17142 neutron-dynamic-routing_14.0.0-1_amd64.buildinfo 6fcd33b6a867e80ba0c90ac714b86ddef073638a 59652 python3-neutron-dynamic-routing_14.0.0-1_all.deb Checksums-Sha256: 7077d11c5ab73dbc81c1b32e0824c3002b90bacb1356ce1f89e86450129a401c 3157 neutron-dynamic-routing_14.0.0-1.dsc 23836541bddf5e3cbb7c1a70e5fa30b3703dd08eaa71b71488f6c4cd4347ae31 110450 neutron-dynamic-routing_14.0.0.orig.tar.gz f9fad2e89a0f52b1f2ff0407fba1d07ee29b7ce8573d64cb615808a40c6a9a31 6652 neutron-dynamic-routing_14.0.0-1.debian.tar.xz 30ecb54d4571800caa79cff6d5e45414183eac2b119c7877aa028e50de35338f 6716 neutron-bgp-dragent_14.0.0-1_all.deb e949587f84d692666b579305f3b9cedfa008925a34bae948a6b6ac21353e94ba 15252 neutron-dynamic-routing-common_14.0.0-1_all.deb 0ae3294be4d488cb8ee429cb854977eb6335fa1c059be3615833fc099a9b1634 17142 neutron-dynamic-routing_14.0.0-1_amd64.buildinfo 32d7640a56928430a2778e8c1545bede8282f5b847875b821ecc960d9e10d176 59652 python3-neutron-dynamic-routing_14.0.0-1_all.deb Files: aab720af871496833650849787878c60 3157 net optional neutron-dynamic-routing_14.0.0-1.dsc 5926b18bb3fbc809108c908d109c3f1b 110450 net optional neutron-dynamic-routing_14.0.0.orig.tar.gz 7d84851782141f03a95e793b2f93274a 6652 net optional neutron-dynamic-routing_14.0.0-1.debian.tar.xz c65a63c04fe9c978792bbb3c27452a19 6716 net optional neutron-bgp-dragent_14.0.0-1_all.deb 0a279944377ac355ab15cb1db6b4a397 15252 net optional neutron-dynamic-routing-common_14.0.0-1_all.deb b61f54074769f76fc87544e4fb458686 17142 net optional neutron-dynamic-routing_14.0.0-1_amd64.buildinfo 150100a2367e08028f8b0f04d29e9e7a 59652 python optional python3-neutron-dynamic-routing_14.0.0-1_all.deb -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE5XQmXq/+PEpA+qGNSgz2OUJ4hOMFAl0R0fEACgkQSgz2OUJ4 hOOjIA//bRgVb0muvxOCEh+gv172J8vRAF3jw/S3XWGKrAkgp9CyzAhGk6LIFDiK Cc4Tofm2T93mtolMbfva0qHcieP10gtbIs8tQQjclwFWg+KyGvu3LBqR1T08iYN+ oLyUkRYtSlqnk2yfBzSgQbbn1gk0fHMnt6nVVYMiPsCje2hv518P3KleipvIG4iK 3uhqxkxu9fG4zdyOYGqkuXHv5P58Wp2Ef3Wgm2eYw042AIymOb5m5OHEZoW4keXX M9NRWjHhy0bjMvQ0ilnjMvjpupHVViDm09VCEQBUHGHuizu98sGuVGK5hfWzranD NL7GUjmO4ehhXXZvXypq7bUY/TxJrovi7s2sfFiVCNOwLj+R9es93nVC8L+A7yj9 GWzEIz4JjbGwCAJ9npfnAY+WC6Qlo1hnc06e22BVflgG0SPeNqzbmNJLBjQ6v6NK sSLbFP7JBCJJahiw9LV0vq1w/4oi/xPPRgaXYkb9U9S0EQhMxnmLaxjrB2MCCe8D LK07EkyNXLVAkUN52ceEm8zblo+qf/k42zGyggh49TspzJYSFtjXOa1Ye6qsTIvn DSkOXgF45Ek83TwjkYjYg467/4UXKXkFJd0XOeyIA/39BQu6iCptU4yRA5LrJoj2 DohYZTuxCJHftaGRXd7oBqsgAR+xTRN8I7jlz7EzuHWcIPyorWQ= =iZFm -END PGP SIGNATURE-
Re: Content Rating System in Debian
On 25/06/19 14.31, Philip Hands wrote: Bagas Sanjaya writes: Russ Allbery: It sounds like a whole ton of work to get a useful amount of coverage (not to mention bothering upstreams with questionnaires that I suspect many of them would find irritating -- I certainly would with my upstream hat on), and I'm not clear on the benefit. Do you have some reason to believe that this is a common request by users of Debian? If so, could you share with us why you believe that? I'm discussing about CRS inspired from Google Play. Do Google Play not pay IARC for this? I would assume that there is a fee that covers IARC's costs in running the service, which is then paid out of the profit that Google makes on the games. What is it going to cost us to get 'bison' rated PG? Why is this useful? Also, it seems clear to me that the same game in all Linux disros is very likely to get the same rating, so this would be better done as a distribution agnostic level, preferably by someone that makes a profit from games or content anyway. For instance, I'd imagine that Steam have some sort of rating mechanism, which might even use IARC already, so one might be able to achieve this aim by talking to them about getting access to their system somehow, and perhaps getting them to include things in their database that they don't actually distribute themselves. One might imagine that one could buy a subscription to their rating database, say. Alternatively, parents who are interested might simply decide to subscribe to Steam if Steam provided a package that allowed subscribers to see the ratings for packages they were about to install. (I'm only saying Steam here because they've been quite Debian friendly AFAIK, but there's nothing stopping anyone else offering such ratings as a service to Debian users). Asking Debian to do it seems like it's just asking for trouble -- what happens when a child is traumatised by content that most people find completely innocuous in a package we've not yet got round to rating? Cheers, Phil. I don't know whether Google Play and Steam pay IARC or not, but if they do, the fee would be so expensive that Debian can't afford (unless we're RedHat or similar). Also, to implement CRS, major overhaul to packaging system (apt/dpkg) and user accounts need to be done in order to accommodate CRS. But CRS can give users insight about maturity of packages. So if sysadmins (parents in home networks) is about to install Apache HTTPD or other packages, they need to answer whether the packages are appropriate for their users' age or not. In multi-user setups (such as in servers) CRS can be a problem, because although majority of users are adults (18+), there are possibilities that children (7+) or teens (12+) also use such packages. Some packages might recommend Parental Guidance (PG) but it is not possible in server setups. I'm agree that CRS should be done on distribution-independent manner. This means that upstream file rating request to IARC in order to get their programs rated. Distributions (Debian/Ubuntu, RedHat, etc.) then package programs which have been rated. In Google Play, rating process is slightly different: upstream upload their applications/games to Google Play, then they fill rating questionnaire provide by Google Play and send it to IARC. Regardless, for CRS, we need a CRS system that is cross-distribution that can be implemented to package managers and user administration tools on most distributions. Erm, not 'PG' -- I meant whatever the "Anyone can watch this" label is. In IARC classification, that is 3+ (for anyone as long as they are not toddlers).
Re: Content Rating System in Debian
Philipp Kern writes: > On 2019-06-25 09:31, Philip Hands wrote: >>> Russ Allbery: It sounds like a whole ton of work to get a useful amount of coverage (not to mention bothering upstreams with questionnaires that I suspect many of them would find irritating -- I certainly would with my upstream hat on), and I'm not clear on the benefit. Do you have some reason to believe that this is a common request by users of Debian? If so, could you share with us why you believe that? >>> I'm discussing about CRS inspired from Google Play. >> Do Google Play not pay IARC for this? > > App developers are generally forced to self-rate their apps, otherwise > they disappear from the store. Right, but is that not done by filling out a questionnaire that is somehow administered/rated by IARC, which presumably means that they need to be paid for providing that somewhere along the line (or is it all government funded?). Also, IARC claim to keep ratings under review, which presumably also needs to be paid for somehow. I was guessing that they collect subscriptions from the platforms to cover the costs. Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Re: Re: Content Rating System in Debian
On Tue, 25 Jun 2019 at 09:31:44 +0200, Philip Hands wrote: > Also, it seems clear to me that the same game in all Linux disros is > very likely to get the same rating, so this would be better done as a > distribution agnostic level Appstream metadata, which is canonically provided by upstreams and is distro- and package-type-agnostic (available in at least apt and Flatpak), has this as an optional field for self-rating: https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-content_rating https://hughsie.github.io/oars/ I suspect that's the only way this could possibly work without money changing hands. smcv
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 09:46:00AM +0200, Bastian Blank wrote: > > Related to that I would like to be able to write something like > > deb http://deb.debian.org/debian debian11 main > > deb http://security.debian.org/debian-security debian11-security main > > in sources.list as codenames confuse people. > > Can you please elaborate on the "confuse people"? I guess only (most?) Debian contributors and hardcore Debian users remember the order of the codenames and their mappings to current stable/oldstable/testing and to numeric versions. -- WBR, wRAR signature.asc Description: PGP signature
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 08:08:22AM +0200, Ansgar wrote:
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
Even if we stop advertising them, could we keep them as a generic set of
aliases?[1]
> Related to that I would like to be able to write something like
> deb http://deb.debian.org/debian debian11 main
> deb http://security.debian.org/debian-security debian11-security main
> in sources.list as codenames confuse people.
Can you please elaborate on the "confuse people"?
I think adding such names would be a good idea, as long as we stay on
simple versions. Or we use "debian-11", then it does not look that ugly
to do "debian-23.42".[2]
What would you do about sid? It got no version.
On related notes:
For Azure we currently plan (yeah, still not finished as MS does not
provide input, be we still need to change it):
- debian-10
- debian-11
- debian-sid
Regards,
Bastian
[1]: I think apt would need to learn about aliases.[2] As would dak, to
maintain them automatically.
[2]: Maybe we could even use them for bullseye/updates ->
bullseye-security and keep the former as alias without apt complaining
about it.
--
There's coffee in that nebula!
-- Capt. Kathryn Janeway, Star Trek: Voyager, "The Cloud"
Re: Content Rating System in Debian
On 2019-06-25 09:31, Philip Hands wrote: Russ Allbery: It sounds like a whole ton of work to get a useful amount of coverage (not to mention bothering upstreams with questionnaires that I suspect many of them would find irritating -- I certainly would with my upstream hat on), and I'm not clear on the benefit. Do you have some reason to believe that this is a common request by users of Debian? If so, could you share with us why you believe that? I'm discussing about CRS inspired from Google Play. Do Google Play not pay IARC for this? App developers are generally forced to self-rate their apps, otherwise they disappear from the store. Kind regards Philipp Kern
Re: Re: Content Rating System in Debian
Philip Hands writes: > What is it going to cost us to get 'bison' rated PG? Why is this > useful? Erm, not 'PG' -- I meant whatever the "Anyone can watch this" label is. Although, I guess one could perhaps argue PG for bison: One could use it to build something that generates offensive content, and perhaps the joys of compiler writing should be saved for an appropriate age ;-) Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Bug#914577: ITP: dropwatch -- A tool for detecting and diagnosing packets being dropped
Package: wnpp Followup-For: Bug #914577 Owner: Alexandros Kosiaris
Re: Re: Content Rating System in Debian
Bagas Sanjaya writes: > Russ Allbery: >> It sounds like a whole ton of work to get a useful amount of coverage (not >> to mention bothering upstreams with questionnaires that I suspect many of >> them would find irritating -- I certainly would with my upstream hat on), >> and I'm not clear on the benefit. Do you have some reason to believe that >> this is a common request by users of Debian? If so, could you share with >> us why you believe that? > I'm discussing about CRS inspired from Google Play. Do Google Play not pay IARC for this? I would assume that there is a fee that covers IARC's costs in running the service, which is then paid out of the profit that Google makes on the games. What is it going to cost us to get 'bison' rated PG? Why is this useful? Also, it seems clear to me that the same game in all Linux disros is very likely to get the same rating, so this would be better done as a distribution agnostic level, preferably by someone that makes a profit from games or content anyway. For instance, I'd imagine that Steam have some sort of rating mechanism, which might even use IARC already, so one might be able to achieve this aim by talking to them about getting access to their system somehow, and perhaps getting them to include things in their database that they don't actually distribute themselves. One might imagine that one could buy a subscription to their rating database, say. Alternatively, parents who are interested might simply decide to subscribe to Steam if Steam provided a package that allowed subscribers to see the ratings for packages they were about to install. (I'm only saying Steam here because they've been quite Debian friendly AFAIK, but there's nothing stopping anyone else offering such ratings as a service to Debian users). Asking Debian to do it seems like it's just asking for trouble -- what happens when a child is traumatised by content that most people find completely innocuous in a package we've not yet got round to rating? Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY signature.asc Description: PGP signature
Re: getting rid of "testing"
On Ma, 25 iun 19, 08:08:22, Ansgar wrote:
>
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
AFAIK "unstable" is always symlinked to "sid", so it wouldn't make a
difference and also manages expectations ;)
"stable", besides significantly changing it's meaning at release may
also be actively harmful if one dist-upgrades by mistake[1] with
'stable' in sources.list.
While dist-upgrades are significantly smoother the Release Notes still
have important items that must be taken care of before/during/after
dist-upgrade.
Depending on your intention using "testing" may or may not be what you
want to have in sources.list even through releases.
Users that dist-upgrade early or install the next release while it's
still in testing for $reasons (e.g. hardware support, newer software
that is not available in backports, etc.) should always use the codename
to avoid surprises at release (as per above for "stable).
Those who want to stick with "testing" no matter what I believe[2] are
actually looking for a rolling distribution so it would probably make
sense to rename "testing" to "rolling"[3][4].
[1] because 'apt-get upgrade' doesn't install new packages many users
have developed a habit to always run 'apt-get dist-upgrade', e.g. to
upgrade their kernel package (in case of ABI change).
Users are slowly migrating to 'apt upgrade', but running 'apt-get
dist-upgrade' on stable just to get security upgrades will not disappear
anytime soon.
[2] based on more than 10 years experience on debian-user.
[3] or remove the "testing" symlink/name and add the "bob" rolling
release that was proposed in
https://lists.debian.org/debian-devel/2011/06/msg00136.html
[4] or "roling" to emphasize that it's incomplete :p
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Description: PGP signature
Re: getting rid of "testing"
what do people think about getting rid of current suite names ("stable",
"testing", "unstable") for most purposes? We already recommend using
codenames instead as those don't change their meaning when a new release
happens.
Hi Ansgar,
Regarding suite names (stable, testing, and unstable), there are for
convenience if you rather just want to stick to
particular distribution. If suite names are removed, you have to update
sources.list whenever a new release is made
in order to keep up to date to your chosen suite. If you e.g. track buster
(which at the time of writing is in testing)
instead of testing, you are tracking buster until EOL.
PS: I'm not Debian User or Developer, so my opinion can be misleading.
Regards, Bagas
Re: getting rid of "testing"
On Tue, Jun 25, 2019 at 08:08:22AM +0200, Ansgar wrote:
> Hi,
>
> what do people think about getting rid of current suite names ("stable",
> "testing", "unstable") for most purposes? We already recommend using
> codenames instead as those don't change their meaning when a new release
> happens.
Are you supposed to change the code name manually if you want to stay on
testing after a release happens?
> Related to that I would like to be able to write something like
>
> deb http://deb.debian.org/debian debian11 main
> deb http://security.debian.org/debian-security debian11-security main
>
> in sources.list as codenames confuse people.
Yes please.
--
WBR, wRAR
signature.asc
Description: PGP signature
Re: Re: Content Rating System in Debian
Russ Allbery: It sounds like a whole ton of work to get a useful amount of coverage (not to mention bothering upstreams with questionnaires that I suspect many of them would find irritating -- I certainly would with my upstream hat on), and I'm not clear on the benefit. Do you have some reason to believe that this is a common request by users of Debian? If so, could you share with us why you believe that? I'm discussing about CRS inspired from Google Play. A case study of implementing CRS is when parents which have Debian system installed on their computer wants to make sure that any programs installed there are appropriate for all family users there. Also we have "Self-Censoring" campaign which encouraging users to filter contents suitable for their age. "Self-Censoring" originates from TV programs, but it can also be applied to computer programs and applications (especially games) as well. Regardless, CRS is good not only to Debian, but also to end-user in longterm, although it is hard to implement and have some maintenance burden.
getting rid of "testing"
Hi,
what do people think about getting rid of current suite names ("stable",
"testing", "unstable") for most purposes? We already recommend using
codenames instead as those don't change their meaning when a new release
happens.
Related to that I would like to be able to write something like
deb http://deb.debian.org/debian debian11 main
deb http://security.debian.org/debian-security debian11-security main
in sources.list as codenames confuse people.
Ubuntu already has no suite names, only codenames, but having to map
"Ubuntu 18.04" to "bionic" instead of just writing the version in
sources.list is annoying (I always have to look up the codename to be
sure as I don't use Ubuntu that much).
Ansgar
