Re: Bug#1053686: pandoc: cannot fulfill the build dependencies
Quoting Paul Gevers (2023-11-16 11:22:45) > On Thu, 12 Oct 2023 06:36:05 +0200 Jonas Smedegaard wrote: > > Quoting Scott Talbert (2023-10-12 02:33:45) > > > It looks like pandoc can be updated to v3.0.1 and be compatible with the > > > dependencies that are in unstable currently (LTS 21). Can you please let > > > us know if there are any dependencies still missing? > > > I will look at it soon - probably this upcoming weekend. > > Is there any progress with fixing this bug? It seems that this issue is > one of the last blocking issues in the haskell transition. src:pandoc is > a key package, we can't easily remove it from testing to "fix" the blockage. Thanks for pinging/nudging, Paul. Upstream project has restructured to now be organized as multiple projects to be built as dependencies of each other. I had hoped to be able to orchestrate such chain-of-builds internally in the single source package, but the Haskell build helper tools seem to be in too bad shape for that: Apparently all Haskell packages use CDBS which is quite cumbersome to use for "looping" subtasks, and both of the two available non-CDBS debhelper tools existing in Debian are broken. I therefore give up on that approach, and see no other way forward than to introduce the libraries of Pandoc as a new source package, and then have the existing src:pandoc package depend on that to build the binary. I will now file an RFP for that new dependent package, in the hope that the Haskell team can adopt maintenance of that. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1055044: RM: sugar-artwork/0.120-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm X-Debbugs-Cc: sugar-artw...@packages.debian.org Control: affects -1 + src:sugar-artwork -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 (explain the reason for the removal here) The binary package gtk2-engines-sugar is obsolete, and seems to need manual removal from testing for newer releases to migrate. Kind regards, - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmU/QSoACgkQLHwxRsGg ASFNvw/9HSlA4lJHHlAmU5RA3GalGUrva9zOV6IYimWxw67FUaM03JNdc8uk79+W KR0qVha2/oFzUMWCLlQeZrNB9tOIQfkobSGbMzERWmnYVEU9Z+zJypHrlwWcieVr k13hX5/9hqmOJsfEH8Mo7suau05T9SVT2MxapK+v13bjvdFPp+Jwj0L04uOhOJVk HiQ3yvN2EvNgpm+ofbxdTKvsrJl4VnrdL/ZfO34CvYv4ZQQ+BfEj6Zp4bdooI5Qq 9xTI47Iu70aLJ2/MncxrvD8kKO1c/ELhESQeHCDCMJyjL3jHKJxbuSbzTAAr4eMr bgt1Jb3Em0TyH7uzc3kmgb9/bkADaAEYaaxH5v9YodtF5sQPxu6AurmJqYNkKSf6 qUt9Tyt8WCz7bpIUl5gUftLGWf3bFSm00kWtF3k68aF0MvH6N++CwCzTNiANQyen UA7DB7VosSh15GB6acH7AgSAa1OWou37OgOpQHkVBBVtoZtlI9QcfP6R1+eMAmZC OgzjgjvHQG+sv5yAHzGw84c5oDpmZntPttHoSlQQlq+8i4C/EsUD2rXXOsDYkz11 YKzyJS4V9UWTmahpZmSTrc5XrTrtuAQAX57ydKItuCZ76UkqxDGiPp0bFIs6nMp2 zTPyu1upM8OTjwV8DF+BLzfjbUhOmt8Ki8Sb7781p3G0V/yE/qY= =O0Q3 -END PGP SIGNATURE-
Bug#1042581: nmu: uwsgi-plugin-php_2.0.21+4+0.0.15
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: uwsgi-plugin-...@packages.debian.org Control: affects -1 + src:uwsgi-plugin-php -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please do the following binNMU: nmu uwsgi-plugin-php_2.0.21+4+0.0.15 . ANY . unstable . -m "rebuild against new upstream release of uwsgi" -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTGh7MACgkQLHwxRsGg ASF2Yw/9GNnYp74L/nJlh08lZztmevdNQFwIxYd+gEptpykPBjN0Mi4AYK5tYUhJ DTLZ+6d6NjvJnrpV0IRZ//5NqbYFHzKLph5XaVHQGtNY2iRVYEiHmUvG0HGpKad9 LQiijOMDj1RGqsKWHRe0HeAo5azb14gJxr653W8U52VcTF+fxCxoXh0pAU+DYV4q eYk4XSp1Z79suEWd88Lyux2wcY6Hi/IMPQ8bDldYY5VfkQ4VwI25fhGDuPmxeWY6 Aa6ecBnt2cFjEdDi36IWFHyCySCTYaFqsw72bqUq4ts/xOjMz87tODw8NhR2R3WF hWpoSgn0RMba8ISnFp/lQhySkaRds0J2T59zfIx+RHfOGyxDElLjsbJzqXG4dLFU HFjIm6tiP+T8uc6TZOqD0ONarlfuwvMnAaOs1Gi5OqCvN+LnZxpv/4ZpYqEotZ+I UiXN7P0gWpuqhXSAsV9Z4vnjecU5fqHBX7NXtbxv1Ekn0rlkl6npdhcjwnVgfC9y PwF3Is0jdvNHFrA7AlckMcEDT2VZZ36sACcKqS7sPUmOIh9D+4kcyjHsRtjeCfPA KuwKVX3rTW1KHGYosDZZb3mfMSfjiRIXBgArm1FH2I/o7bEZlA1OrYvPtushMwlS cpw40x8O4qhuRKtoz+eATOcooPkY0bEYMKM0G+xCtJD7DNJCCvo= =I2Mp -END PGP SIGNATURE-
Bug#1042580: nmu: uwsgi-plugin-mongo_2.0.21+3+0.0.9
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: uwsgi-plugin-mo...@packages.debian.org Control: affects -1 + src:uwsgi-plugin-mongo -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please do the following binNMU: nmu uwsgi-plugin-mongo_2.0.21+3+0.0.9 . ANY . unstable . -m "rebuild against new upstream release of uwsgi" -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTGh3AACgkQLHwxRsGg ASES0Q/+LYkAmouI7IDjUW66+4FAWiWPpBrXVAg/pe6fzgCDtexclL094jP/wtp2 DDzV4c4uViYZ7ei5y5BsVsuPDJa19NX8x2EpLrSVaHvCGSkpB0fpgz9JZOYIHdyb B/AJsUOr93RDcZUAxwP5jmyqRtmrAFgTa1Clk7IEUbhPXCuob+d70HeJkrgKJAlY LUwuf9JrB8csJdfkj5uugKggoZvQmNVQYDRU6qP+J2Z0WyY29/JTmf8NVqUe1uMe SFZ8PdoOI/jjFREtq9dtjlUlAlb4UpaKhEz2rOzT68IFh28SwGYweuk3BMietHfg aR4TUdD0InpaIVlLeZSx+pX1I9rpQrh++Gin0Ts/lKiBKeF3mckfA298GAHFg/PQ rNU86WMgKu2CBq89/pCLdBcwAZ71uLMxGa1Om2Z+eE/LYeZaxIgvCAxhM/41VgAD 6bBignM8cAeZYF4i0sQezBhgGHX8IQ9vW/GP2SdXphxXuQPkuQu0/tkha7N2HX3U oNJnRzv6rRzFjfVtSmNqrWXbTQaT2BTLXvl3lFkXoU9OrCwL9Q4FaK7Xto2T5BJ6 RGOsH0GoBAW0JxH9rW98rkryjqlpaaCfEVIBdGc+yqhBfJkNvlxTo5J/vHsjO3JN s5Qn74ZtnhTPCUHk+bjeTyL4p31P6VJ7UqXW7ubFGcyAstwI58E= =zTnH -END PGP SIGNATURE-
Bug#1042579: nmu: uwsgi-plugin-luajit_2.0.21+3+0.0.8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: uwsgi-plugin-lua...@packages.debian.org Control: affects -1 + src:uwsgi-plugin-luajit -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please do the following binNMU: nmu uwsgi-plugin-luajit_2.0.21+3+0.0.8 . ANY . unstable . -m "rebuild against new upstream release of uwsgi" -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTGhycACgkQLHwxRsGg ASFhkQ//U/uhDBLRzirRgFOTEnO1OkNZYs2jIEPSI8GaP51qQfnHE7Y4eYJgvzM0 CKJdRSFQ2jDtHzkxnddW/0Y4HAL63+dK3B6Y6crpyzu+/dYoPPCdKCDW7dLzn5V7 lcoN8og3huEy4nanYFYhwl+eoQ/TZN67t+VAxQWpPx8m6uMkPaYY4+GJcdFi27Gc 361kEB7a9kdK7375kL2ZWdauQ3of6Tj4xPvhA8hPDTsSZU/5ZTQzK+zC+UpbpntH i5iA04VIcKKX4J29fT54gyEVd9FuKWc1oceqhZyJWTbvWkRcK0yLGqyaTGkC+6dV Sj4dEBQnOVMJfaDKfs9GqImC6oV/hOQkhD0Tci03rhDemTOz26fv07XLRz819rOm ZGrChXs+MOwZGspzqKMup9SEqroAhTmsbCQ8U3gPWuEFH7F7/58Y41gB+nSs3J3i dOTe7STc1+GfWKVvC97cTJfeybOyZdAm3UKaWuF/phEXmuYrbtGIeKo6AxENc9Xd mH+0oO2kN7twf+wA7Ri4PU9g0JQBnrMipVdcr+am89Nu3BHWEIQ5tTwXJjTPupe6 0dRrFcuRkgsKk3lccVeKhm+sBa7L879SNcyze7sJXnrqUzj+IAuDbrNiTE9UAbpu 2xDbsZdlADIAiWXwT8aX0shjJ8q6CdfmhhZbvOlqC+DfMwXVBns= =NJQY -END PGP SIGNATURE-
Bug#1031128: release.debian.org: please suppress ppc64el and s390x CI tests for src:rust-ureq
Package: release.debian.org Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The package src:rust-urew is currently blocked from entering testing. CI tests are generally not completing, as tracked as bug#1030883. For two arches, ppc64el and s390x, CI tests now complete which reveals that on those arches the CI infrastructure bogusly thinks that a dependency on the virtual package librust-rustls-0.20+dangerous-configuration-dev should be resolved as arch-specific package which is not true for more than a week now. Please therefore mark rust-urew as ignore CI tests for ppc64el and s390x since those test environments are apparently broken. Kind regards, - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmPooSAACgkQLHwxRsGg ASFhPA/9FGuD+NW8pl2FiAGqwUAUFRvpxji8PUyDoWGxopsURUeT0iwHrigRiJG/ YAhrN7I1oY3qNDXT4PevH3q39XD7zMDpeFU+Yg/b/VFND1Htl3B3GW9qQEnVeSpG yy/KMHfznxPMtni47CUFEHxbfPBnLOePJzCfjSM/kL0r7LheOMuXwOtxKbrVRcP+ 0gmAK5DUikXfvwjOL+QsVlkpd2hwJhNMmS+WwLZRHRpX0nzRKJsDHUP+d6dZkIKW ex47RpDWvFEeSeBfXK67dKLdKDMzKsBx/67iXL7S6XYeU642+DT86hWow7Kqp88e sDNDu9CSV+NzsYkGS8UFRtBne5RfMps+JiuJIb1qdX8Q5+YCMtRg61F+ml+yUOwA cWZxEohddH0rOObE27mrQvNGP+ZtRXeEi7PgnMHN5Hy0CdC4mIY1xSzKGrD1M2sh OasZT6X4KcVtI2mouBs+tJr2pJw9js7cEiU+F5LOLUh424YMcBhMzEscKoOWlAm7 PdJDEOiW/n4j6F+ko+Sr468rZEKLrc0aYrZFuRH/iw+HHLEqqG6cAVBLJghPtiwK KHFekI3XyNMpojyxCAjarZMzPiB0igaSbfE1EtZ2oeFlnYQY5ND2kz1NOAwL57zE 7j4LVaobwyh4jvS+P+6ibHY77TKvD9Q2GYPPr3J0it9P5WInzys= =Pqlk -END PGP SIGNATURE-
Bug#1030957: release.debian.org: please have rust-rustls ignore CI tests for s390x and ppc64el
Quoting Paul Gevers (2023-02-10 21:14:52) > On 09-02-2023 23:59, Jonas Smedegaard wrote: > > I can only interpret that as the test environment on thos arches being > > broken. Please don't punish the package for that :-( > > I think your interpretation it wrong. librust-rustls-dev Depends on > librust-ring-0.16+default-dev which is only available on amd64, arm64, > armel, armhf and i386. The test used to be skipped on ppc64el and s390x, > because you had skip-not-installable enabled, so the results were > neutral. You removed the skip-not-installable restriction, so now the > test fails. The regression is your own making, don't blame the test > environment. Ah, I am very sorry for throwing blame with stuff I don't understand. I shall stop doing that! > Having said that, as I mentioned before I regret I added the > skip-not-installable restriction, although it has it's use of giving > maintainers some control. I'll add the hint shortly. > > > There seems to be same problem for rust-oxhttp, and rust-hyper-rustls. > > Do you want a separate bugreport for each, or is it fine just mentioning > > it here? > > I'll have a look and if they're fine, I'll handle them too. Thanks! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1030957: release.debian.org: please have rust-rustls ignore CI tests for s390x and ppc64el
Quoting Sam Hartman (2023-02-10 23:10:03) [concerns over binNMUing due to static linking snipped: irrelevant!] > If on the other hand your packages aren't going to need to be rebuilt > when their dependencies change, it may not be a big deal. librust-*-dev packages contain no static linking. I am unaware of this being a big deal (besides those hickups in infrastructure when switching from arch-any to arch-all which as I understand it is a bug somewhere which just hasn't been shaken out because a move like the one I did is rare). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1030957: release.debian.org: please have rust-rustls ignore CI tests for s390x and ppc64el
Quoting Sebastian Ramacher (2023-02-10 10:30:53) > Control: tags -1 moreinfo > Control: severity -1 normal > > On 2023-02-09 23:59:25 +0100, Jonas Smedegaard wrote: > > Package: release.debian.org > > Severity: important > > > > ckage src:rust-rustls is not migrating to testing because tests fail for > > s390x and ppc64el. On both arches the failure is that the test > > environment thinks it needs to install an arch-specific > > librust-rustls-dev to satisfy a virtual dependency pointing back to > > itself, which is (since recently) an arch-all package. > > > > I can only interpret that as the test environment on thos arches being > > broken. Please don't punish the package for that :-( > > > > There seems to be same problem for rust-oxhttp, and rust-hyper-rustls. > > Do you want a separate bugreport for each, or is it fine just mentioning > > it here? > > What's the added benefit of the conversion to Architecture: all > packages? Currently there does not seem to be a concensus to do this > switch for rust packages and doing them shortly before the soft freeze > apparently just generates work for the RT. Reduced size in the archive: Avoids multiple identical copies of library source code Reduced complexity of APT: Avoids replicated packaging metadata Avoids certain types of impossible-to-satisfy scenarios: https://github.com/sagebind/threadfin/issues/3 is an example of a complexity which due to differences in how crates.io and APT handles variety in architecture support caused a dependency of src:rust-threadfin to be impossible to migrate to testing because a test-dependency was unavailable on a lesser-used architecture and could not (easily) be skipped for single architectures. That concrete example was luckily solved now before the freeze, but would have been quite problematic to handle afte the freeze, and was the trigger for my decisison to switch all of the Rust libaries I maintain to use the format which is generally better understood in Debian context: arch-all code should be packaged as arch-all packages. Yes, I am aware that the Rust team packages arch-all code as arch-any packages, but I am unaware that their reasoning is well documented anywhere. The only reason I was aware of when I did the switch was that Debian has a convenient processing of binNMUs but annoyingly require source-only releases for rebuilding arch-all packages. I certainly had no intention of causing additional burden for the release team, and only learned about the hickups in infrastructure now experienced when I did the switch. On the contrary, as explained above, one of my reasons for doing the switch was to _reduce_ the risk of release team headaches _after_ the freeze. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private
Bug#1030957: release.debian.org: please have rust-rustls ignore CI tests for s390x and ppc64el
Package: release.debian.org Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 ckage src:rust-rustls is not migrating to testing because tests fail for s390x and ppc64el. On both arches the failure is that the test environment thinks it needs to install an arch-specific librust-rustls-dev to satisfy a virtual dependency pointing back to itself, which is (since recently) an arch-all package. I can only interpret that as the test environment on thos arches being broken. Please don't punish the package for that :-( There seems to be same problem for rust-oxhttp, and rust-hyper-rustls. Do you want a separate bugreport for each, or is it fine just mentioning it here? - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmPlesoACgkQLHwxRsGg ASHWew/+P4ARdVeceSslT016FEdGE8y5oQ0Ee/gcNqLFQN7U/xwLLvyFq2PDcIWH uwAJUL4QVipEwQd1J7AzpCuWly5ac7G1iQB/wAslAs9SbFeoQ2rOhZNQZv6Qf9vj OkLB1v1hDkGgiQAjwDSc7mUhn7O/p/o0FZwlbtcoMAFm5se8rWptrMvmcUy9AweR PJkc08guOQD8+Fn28BwbEduprHCqPwwdVWzgMZwNT7ID10TTl7nuY365HvguOa5z iHcctNoQd4Sm3wQMp3YaZp0LFa7MpZH6wvf4mNGheKzLsn0HZuRaVd0gJBo5MJCD OZ9izaiicGGgE+2QGOLoomT9/UT6K6xsfkTJnDnXjyOYH4FmPNorCNlfz/dvKtEo PdAvoxE9gO+sMXFUuxc7HJZAxV1zOo85WGBoB8Bjfb0sSX9+KC/GyULLdVEGJ0su zKzLh99jQRhLXPYifBt9JpstLWdg7WGOd1GEvNW0J8/lpQoC627TDF4hutLb4KFl Ffzl9Y91e1oI59L5mO8BfYezjJe8VifFM4QR2kQqGUe/7fIUVRFvNGis/FKX67wn b2/t0rBJymqkdrz+hoavmV/iO3iBiNjDCLxak3VW6d8CVsfkn3mHVZeJ4UQU9qyu 05j7I0D1rSagheRAjpfVyfC3yIMMz1/GaFQGOqbJIimJhQ7mNhc= =GkQb -END PGP SIGNATURE-
Bug#1030883: release.debian.org: CI for rust-ureq mysteriously "in progress" for 5 days even on most powerful arches
Quoting Paul Gevers (2023-02-08 21:20:04) > On 08-02-2023 19:31, Jonas Smedegaard wrote: > > omething seems wrong in autopkgtests for rust-ureq: status is listed as > > "Test in progress" on all arches, except ppc64el and s390x that had > > failed, seemingly due to choking on the src:rust-rustls package recently > > switching from arch-any to arch-all - I have requested rechecking of > > those. The others that are "in progress" for suspiciously long do not > > offer me a request to recheck, so I am asking you to please try > > investigate what is going on there... > > I think this is more something for debian-ci (in cc). Very interesting. > On all architectures, there's 1 package pending longer than 5 days, and > on all but one that's rust-ureq. What worries me however, is that > https://ci.debian.net/packages/r/rust-ureq/ mentions also 2 days old > triggered tests in unstable that haven't run. The queue on most > architectures is empty at the moment. > > I've just started a manual run on one of our workers (ci-worker01, > amd64) to see if I see something odd. [some time later] ... and it > passes without issues. (You probably have an unintended test name with > gzip, but otherwise, manual running is OK) > > So it's either the timing was extremely unfortunate and your package hit > something unknown on our infrastructure, or it's actually the package > that's causing issues on our infrastructure. @terceiro; do you have > ideas where to look? I suspect somehow the results of this package cause > the rabbitmq to choke, so the test gets removed from the queue, but its > results not added to the database (that's the opposite of our s390x (and > old riscv64) issue). In case it is helpful: That same day I released between 20 and 40 package updates, all Rust libraries and all involving a switch from arch-any to arch-all, and received some feedback that it had triggered temporary FTBFS for other Rust library packages. My vague impression is that some infrastructure caches package names for virtually provided packages, and then fails to resolve a dependency on "rust-foo-2+bar-dev" which it internally assumes should resolve to "rust-foo-dev:same-arch" but has changed to resolve to "rust-foo-dev:all". - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1030883: release.debian.org: CI for rust-ureq mysteriously "in progress" for 5 days even on most powerful arches
Package: release.debian.org Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 omething seems wrong in autopkgtests for rust-ureq: status is listed as "Test in progress" on all arches, except ppc64el and s390x that had failed, seemingly due to choking on the src:rust-rustls package recently switching from arch-any to arch-all - I have requested rechecking of those. The others that are "in progress" for suspiciously long do not offer me a request to recheck, so I am asking you to please try investigate what is going on there... Kind regards, - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmPj6mkACgkQLHwxRsGg ASFRDhAAj8TkU5voEEtYUYqRTKO6em1sDezRY3o2VBY2yXZ/bw09nrR2BxpvGyri jOFpdOEVVitL6MTpjU2zALT6Gk1jWJfOT6FIrRbCo43J1fFyDuse+p+TI5nr2iWq jRyL81TF+F6UssK2qw5oKVijbc7pEEXvReHSF4MHAkQm0vaIH4mX9bFvTBByfa8l v2FqLo3EeYvuR8mLDig7h9uv2XmR2zbZq1A/wCP02O+YRaGFEsjWeVDo8LzH93ef aQ883hzWYYEXNFwqHd+M5pj4+jeuD3iEVCjFmlF4a4NAWMKLFO5FYhaAgzrOGGO4 kck51HCq/4p1tfp+UtDqpItsYImyfNR9FiI//Sb/drA40d73yY01CB9yj1fFlaS4 iHc2kgzEIMSbUxNCJMf8BRIj+MZUuHjkvYklGxFzwciG/flFDPq1QMXudOI2+R43 jGNblioXBsh32W367J1YPgaGm6zubudaWauoMqtGnLP+ajWQ7tErAAl8Jy8E/Xt0 ksHsx3dV9eKN7iX875Cvglhko1hPPpQe57qgekm3p2wkBp9TSZeRv1dybnUNnflT 1TLuGxaHwothyoNJZetdR61NZVM4S7dey6hX5LyBkuDmnyMRt1PG95VBfSVImleo rHdvIsk4lVVLyY+d8yepPfxnbwzwZj4yIX05aLC82/0zrAr225o= =rupV -END PGP SIGNATURE-
Bug#1030881: release.debian.org: please have rust-rustls-native-certs ignore CI tests for s390x and ppc64el
Package: release.debian.org Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 rust-rustls-native-certs currently fails to migrate to testing due to dependency rust-ring missing on archs ppc64el and s390x. rust-rustls-native-certs is arch-all, and ideally rust-ring would be arch-all as well and this issue would not occur. (for completeness sake I should mention that Rust team would likely argue that the ideal was that I joined the Rust team, obeyed their team policy, and released rust-rustls-native-certs as arch-any in which case the World would burn slightly more fossil fuel and this issue also would disappear). Please marg ppc64el and s390x as irrelevant archs for rust-rustls-native-certs to let the package migrate to testing. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmPj6JMACgkQLHwxRsGg ASHZlg//S5x+A0F985fyq/hns5h/cm9i4mwjPerar+slBGktHdvvmqyG2ltRHkoS th4Ir3e/HhBkBkv56Lm0d7JIk5/6vqANNeH5yIqXi6TLM/BrzghJD52F6khebgR6 VIyqWjWMj67LhAQrXtifKLBlYed9we4g/kjMRWqEXxW20AQqwNlLB80o7Z15z/x8 MIQ6KHrjDCEP0RHmnZk/VymCYUsdgsmNqVZRjHmLyMKluJ9KTdVVRa4GXT4SR+iZ J+QzZo65/dly1roWQk1vuHsosgPPQYWdmxoaWVHe3N1vYlyyYJhAFh8myIc1ZJFa VG7jlHBKGnOiJhk0wSL468LDi4w1Dtq51R5deYxo4QtQkQHGCnmSCw6D11zoewCU ik8g6s9yboUGGBi2mJ6SPPTE8SwUIMrjKe+Dlm6SLjQnzyh12FcRzy8NREb8QOC3 9Vu6IDl39SM1+tOC4BtIveUAvyEMVHr2J6iMAVpRzYjAdXOWeR1/AKB+iWjAfcLW oI7IcFuxUo2QxH5Im35XoXiMRLC9z0jE2plaeGhKWvmYqEdnx/PSPyVDqBhxHwB7 mP+uuNwzUnGpSZnj8vGOoh0Jq0KRQErefILbrXUN3noq2YhBnyOpaZcGpdvzo4I6 nsGLJ/vMLDMcia42FvRtN5uYMBxPVTUZjd7xc1Q9MdyLmnfgMjM= =LzC6 -END PGP SIGNATURE-
Bug#1022705: unplanned transition: ghostscript
Quoting Emilio Pozuelo Monfort (2022-10-24 13:41:51) > Have you tested if the rdeps build fine against this new version? I had not (shame on me!). I have now tested these packages (thanks to `build-rdeps libgs-dev`): dvisvgm gimp libspectre roger-router xdvik-ja xfig Of those, dvisvgm fails to build (both 2.14-1 and experimental 3.0-1), and I have filed bug#1022714 about that issue. > Also, it would have been nice to disentangle the -common rename from the > SONAME > bump. Yes, I agree that would have been more elegant. On a related note, I have decided to orphan Ghostscript. Obviously I will help get through the current mess that I started. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1022705: unplanned transition: ghostscript
Quoting Simon McVittie (2022-10-24 13:24:07) > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > X-Debbugs-Cc: d...@jones.dk > Forwarded: https://release.debian.org/transitions/html/auto-ghostscript.html > Affects: src:ghostscript src:gimp src:dvisvgm src:libspectre src:xfig > > ghostscript appears to have started an unscheduled transition from libgs9 > and libgs9-common to libgs10 and libgs-common. libgs-common Breaks and > Replaces libgs9-common, so the affected packages will all have to migrate > together. > > Looking at ghostscript's changelog, it seems this might have been > accidental? There's no mention of the experimental version having been > intentionally re-uploaded to unstable. > > https://release.debian.org/transitions/html/auto-ghostscript.html looks > like it is tracking the affected packages, so I haven't tried to write a > ben file for this. > > Please coordinate with the release team to either finish or revert > this transition. Sorry, I forgot to warn the release team ahead. Ghostscript upstream has bumped its SONAME. There should be no breakage (other than the kind of breakage already done in "9" releases, due to security tightening of the internal Postscript interpreter), but yes it requires a rebuild for those package directly linking with libgs. I am frankly clueless about ben files and other transition magic, and would appreciate if someone more skilled in the art can guide this process. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: chromium: Update to version 94.0.4606.61 (security-fixes)
Quoting Andres Salomon (2022-02-14 08:55:22) > I've finally give up and am just using ALL the bundled node packages: > https://salsa.debian.org/chromium-team/chromium/-/commit/a418d219f0217d6398a01c30035d35c42f7a76f1 > > It's not ideal, but at least with this we'll match all of the node > stuff with what upstream is testing, with the single exception of > nodejs itself (which we're still using from debian). The only other > alternative I can think of is to get all the node packages into > debian, and they'd also need to be backported to bullseye. I haven't > looked into this yet, but it might be necessary if upstream breaks > compatibility with nodejs 12. So, uh, if anyone is bored and looking > for some node packages to maintain :) I fully recognize the pain of maintaining a big package and then on top of that paying attention to packaging a pile of Node.js modules. It is also, however, a pain to maintain a pile of Node.js modules and then on top of that paying attention to big packages struggling with bundled Node.js modules. Suggestion: Please consider filing RFP bugreports for each Node.js module that you give up on unbundling. That is far more helpful towards delegating the work than mentioning deep inside a mailinglist thread without "help needed packaging Node.js modules" as subject. A next step (independent, not necessarily by you) could then be to user-tag RFP bugs tied to unbundling, to help prioritize those among the many WNPP bugreports. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1005343: nmu: asterisk-flite_3.0-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 nmu asterisk-flite_3.0-4 . ANY . unstable . -m "rebuild against asterisk-1:18.10.0~dfsg+~cs6.10.40431411-1" -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmIGoHwACgkQLHwxRsGg ASFhMQ/9G8Ef5zhHcBYz898NFx3l9hw8g0cITEyoNZgo/f5Kqi5H1AEoEYV5i99Q YZORP89rFcwhy8jVN4ggBB6IIVzmAiWf0mo0QTExd5vfAjPrk6/y1AXIf2IM7xSX LU6rAhIGMh6ITVuBjlzmWwj3hKWa7vtuXupLdcf+jVUJ9SpJqpOnOuI46hG8+pHb kQxXidURsrQbBHocTdTYAD279VI9XdTCg7dKQRS3iZa2rNoO/dJfXC3riCWvOyFv NC1Gx8L1MHhBnn8cd9etmP4xKu202HhSRKpjUgRsZ3LOtDqHaYYtvd/qW0aPJTJv M+LhQ0xTJzgXRgT15JUSHjczoqydd6v7u59IyTRx/kaRL385W6H1kMTezPIjU9fY rwyiGu3LwHDlEfj0OV/kXHPQwRkw9Yp7ROkDWalyvdeomg6r3EmWd7eEw7C37K3Q DOgYEJsHh9UULwTvA38MJM6j1Ddd+aNKJqAlxsv1dAHBxV3tZvmd1EVqBhAHlOpl /HYBh6/B43ju6BKbF1i7jQiv5WTxhKMR1EKctrodzNHaYOaS6b7nYBhCEd5glizf AiJPqWx888NEcumnKHNTBlwCzVqM/o8CAlffcSlc2vHVf8YIKY1KY2MUR+zBGzFX rrUNoWguaQ0KshOw41nCwBaAllEXwWp1wZKpt98NyhWiQOtCu+8= =9LuI -END PGP SIGNATURE-
Bug#1005328: RM: uglifyjs/2.8.29-8
[ adding Yadd as cc ] Quoting Sebastian Ramacher (2022-02-11 15:25:19) > On 2022-02-11 14:48:00 +0100, Jonas Smedegaard wrote: > > Quoting Sebastian Ramacher (2022-02-11 13:24:16) > > > Control: tags -1 moreinfo > > > > > > On 2022-02-11 12:08:52 +0100, Jonas Smedegaard wrote: > > > > Package: release.debian.org > > > > Severity: normal > > > > User: release.debian@packages.debian.org > > > > Usertags: rm > > > > X-Debbugs-Cc: Debian Javascript Maintainers > > > > > > > > > > > > uglifyjs v2 was last updated upstream in 2017, and has no real > > > > maintainer in Debian since December 2020 - see bug#958117 > > > > > > > > The package should not be released with bookworm, but may still have > > > > reverse (build-)dependencies, and I therefore request removal only from > > > > testing for now. Please advice if another approach is more sensible. > > > > > > So this is the same request as #968137. The current situation is: > > > > > > I: [2022-02-11T12:19:15+] - trying: -uglifyjs > > > I: [2022-02-11T12:19:15+] - skipped: -uglifyjs (0, 33, 62) > > > I: [2022-02-11T12:19:15+] - got: 123+0: > > > a-3:a-0:a-0:a-0:i-119:m-0:m-0:p-0:s-1 > > > I: [2022-02-11T12:19:15+] - * amd64: rails, ruby-uglifier > > > > Package requested for removal is src:uglifyjs, building binary package > > node-uglify which provides virtual package uglifyjs. > > > > Packages (build-)depending (unversioned or with only lower bounds) on > > "uglifyjs" should _not_ break: Such dependency is satisfied by package > > src:uglify-js, building binary package uglifyjs. > > > > (i.e. there are 2 packages, one with and one without dash) > > > > > > > Checking reverse dependencies... > > [ false positive satisfied by src:uglify-js snipped ] > > > > > ruby-uglifier: ruby-uglifier > > > > Current upstream code FTBFS with Uglifyjs: see bug#981224 > > > > v2 branch currently in Debian unstable last update upstream in 2015: > > https://github.com/lautis/uglifier/tags?after=v3.0.0 > > > > > > > # Broken Build-Depends: > > [ false positives satisfied by src:uglify-js snipped ] > > > > > class.js: node-uglify > > > > Bug#979888 > > > > > flightgear-phi: node-uglify > > > > Bug#979902 > > > > > jquery-coolfieldset: node-uglify > > > > Bug#979906 > > > > > jquery-lazyload: node-uglify > > > > Bug#979911 > > > > > jquery-reflection: node-uglify > > > > Bug#979907 > > > > > jquery-watermark: node-uglify > > > > Bug#979943 > > > > > jquery-caret.js: node-uglify > > > > Bug#979934 > > > > > jquery-simpletreemenu: node-uglify > > > > Bug#979940 > > > > > jquery-throttle-debounce: node-uglify > > > > Bug#979886 > > > > > raphael: node-uglify (>= 1.1.1-2~) > > > > Bug#979937 > > > > > ruby-rails-assets-favico.js: node-uglify > > > > Bug#979962 > > > > > ruby-rails-assets-jquery-fullscreen-plugin: node-uglify > > > > Bug#979955 > > > > > ruby-rails-assets-perfect-scrollbar: node-uglify > > > > Bug#979936 > > > > > ruby-uglifier: libjs-uglify > > > > (see reasons at build-dependency above) > > > > > slick: node-uglify > > > > Bug#979954 > > > > > sockjs-client: node-uglify (>= 2.0) > > > > Bug979958 > > > > > > > If you want to get uglifyjs removed from testing, there needs to > > > be an upgrade path to uglify-js 3.15.0 or all of these packages > > > need to be updated. So what's your plan here? > > > > I have no plan. What plan might be sensible? > > As I have no idea what uglifyjs is used for, I cannot tell you. If > it's a drop in replacement, update the build dependencies or establish > an upgrade path via transitional packages. If it's not, patch them. > > In the end, the above bugs need to be fixed to get uglifjs removed. @Yadd: You did the mass-filing - can I ask you to please bump severity, since the normal process of bumping _after_ a package releationship changes to be a FTBFS cannot be used here because src:uglifyjs is transitively a key package. Maybe my post to bug#979886 is useful for such followup mail. > > > > (I tried to g
Bug#1005328: RM: uglifyjs/2.8.29-8
Quoting Sebastian Ramacher (2022-02-11 13:24:16) > Control: tags -1 moreinfo > > On 2022-02-11 12:08:52 +0100, Jonas Smedegaard wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: rm > > X-Debbugs-Cc: Debian Javascript Maintainers > > > > > > uglifyjs v2 was last updated upstream in 2017, and has no real > > maintainer in Debian since December 2020 - see bug#958117 > > > > The package should not be released with bookworm, but may still have > > reverse (build-)dependencies, and I therefore request removal only from > > testing for now. Please advice if another approach is more sensible. > > So this is the same request as #968137. The current situation is: > > I: [2022-02-11T12:19:15+] - trying: -uglifyjs > I: [2022-02-11T12:19:15+] - skipped: -uglifyjs (0, 33, 62) > I: [2022-02-11T12:19:15+] - got: 123+0: > a-3:a-0:a-0:a-0:i-119:m-0:m-0:p-0:s-1 > I: [2022-02-11T12:19:15+] - * amd64: rails, ruby-uglifier Package requested for removal is src:uglifyjs, building binary package node-uglify which provides virtual package uglifyjs. Packages (build-)depending (unversioned or with only lower bounds) on "uglifyjs" should _not_ break: Such dependency is satisfied by package src:uglify-js, building binary package uglifyjs. (i.e. there are 2 packages, one with and one without dash) > Checking reverse dependencies... [ false positive satisfied by src:uglify-js snipped ] > ruby-uglifier: ruby-uglifier Current upstream code FTBFS with Uglifyjs: see bug#981224 v2 branch currently in Debian unstable last update upstream in 2015: https://github.com/lautis/uglifier/tags?after=v3.0.0 > # Broken Build-Depends: [ false positives satisfied by src:uglify-js snipped ] > class.js: node-uglify Bug#979888 > flightgear-phi: node-uglify Bug#979902 > jquery-coolfieldset: node-uglify Bug#979906 > jquery-lazyload: node-uglify Bug#979911 > jquery-reflection: node-uglify Bug#979907 > jquery-watermark: node-uglify Bug#979943 > jquery-caret.js: node-uglify Bug#979934 > jquery-simpletreemenu: node-uglify Bug#979940 > jquery-throttle-debounce: node-uglify Bug#979886 > raphael: node-uglify (>= 1.1.1-2~) Bug#979937 > ruby-rails-assets-favico.js: node-uglify Bug#979962 > ruby-rails-assets-jquery-fullscreen-plugin: node-uglify Bug#979955 > ruby-rails-assets-perfect-scrollbar: node-uglify Bug#979936 > ruby-uglifier: libjs-uglify (see reasons at build-dependency above) > slick: node-uglify Bug#979954 > sockjs-client: node-uglify (>= 2.0) Bug979958 > If you want to get uglifyjs removed from testing, there needs to be an > upgrade path to uglify-js 3.15.0 or all of these packages need to be > updated. So what's your plan here? I have no plan. What plan might be sensible? > > (I tried to get the package auto-kicked from testing by filing > > release-critical bug#958117 but evidently that didn't work.) > > uglifyjs is a key package, so auto-removal does not apply. What does "key package" mean? Simply that other packages (build-)depend on it, or perhaps some manually maintained list by the release team? If the latter, then please remove src:uglifyjs as key package and instead treat src:uglify-js as key package. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1005328: RM: uglifyjs/2.8.29-8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm X-Debbugs-Cc: Debian Javascript Maintainers -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 uglifyjs v2 was last updated upstream in 2017, and has no real maintainer in Debian since December 2020 - see bug#958117 The package should not be released with bookworm, but may still have reverse (build-)dependencies, and I therefore request removal only from testing for now. Please advice if another approach is more sensible. (I tried to get the package auto-kicked from testing by filing release-critical bug#958117 but evidently that didn't work.) - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmIGQ8EACgkQLHwxRsGg ASGcbw//TF1/n+bTOHNqo2UR5/PNAs818+b7CN2uKH+xFXSY3seSnyE95DEHng7K 2rNOTgo7Io2mOvQ2ND+vE0niPqm/p1wwFl70q1Owl0TQ4Dibw5MniXjc55wwQxX4 8wfJY3c4xlLneeiIr9+AskrqbafonDrRTxCC+NAtvTSQSBgsPdOUDPG15umHwSu3 /sx6bfsmH/LzSw6L6/yiskys3C4CfA4FYlcPdKZK+gWkmb+VWdhn1T4hRaUAN2I8 HCuJFGQns7ckb7O/RwSnOkC5ct9c00P8Y1O1kEUxkrGlBmMEq0mIvlCEP63t31Ud ZtmJt/K4WQJ4G/IVfG4/dtcEomPGmZIn07CFEqOU9B1r++nubeCULiCa2Tc9WsmQ eTziPFTcX24lRQ+O69ukg5G+N5WHKKu9uHYacZJa9jdS6qe5TKp07IH+BwTe4w9E LyG8AegBAVjnJ8U68B+KWFXrdpAkcjv3En7IeU3vryUXNPsZr2b3go/Ac2XecdFX 268H9z2rlUiamWQ6bOUNW8DYRvHF7CFNlVJ0tfgyo1bLNNjKjEwCfkHsTSsXQOt5 8g0UkVc168m//PrXQlNWJLWUV4VT+p0QLQGoEC6ES6N61U0H8zVRBEu048b3DFs3 W0QBhZDHxyJUAm1MbiAnRGmzY4/dxkFs4uZmAXRU/zired3XnaM= =40Qo -END PGP SIGNATURE-
Re: please stop block janus from entering testing
Quoting Paul Gevers (2021-12-05 21:06:21) > Hi Jonas, > > On 05-12-2021 16:25, Jonas Smedegaard wrote: > > Now, I have changed my mind and decided that it makes sense for Debian > > to include Janus in its stable releases despite upstream lack of > > official support for that. I find the Janus codebase as stable if not > > more than a lot of other code that we ship with Debian stable > > uncoordinated from upstream maintenance promises. > > > > Therefore, please lift the "ban" on Janus. > > Can you please also document this in your still open RC bug #946412 > against janus for future reference? Oh, certainly :-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
please stop block janus from entering testing
Hi release managers, During (or close to?) last freeze, I requested that janus be kicked from testing, because upstream does not promise long-term stability of its releases. you responded by not only kicking it but also blocking it from re-entering. Thanks! Now, I have changed my mind and decided that it makes sense for Debian to include Janus in its stable releases despite upstream lack of official support for that. I find the Janus codebase as stable if not more than a lot of other code that we ship with Debian stable uncoordinated from upstream maintenance promises. Therefore, please lift the "ban" on Janus. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: delayed package removal from testing
Quoting Paul Gevers (2021-11-28 14:09:22) > On 28-11-2021 11:41, Jonas Smedegaard wrote: > > I wonder why debian-parl was removed from testing today, since (as I > > understand it) the reason for removal was solved 2 days ago. > > parl-desktop-eu in testing at the time of removal had a dependency on > iitalian. It's iitalian that has an RC bug. The only way to remove > iitalian from testing was to also remove reverse dependencies. Ah, right - makes sense. (silly me - what did I even expect should have happened instead?) > > Is there perhaps some spell I could have thrown when uploading a > > known close-to-deadline package? E.g. the trick of posting > > something to a bugreport to reset its timer? > > Pinging the RC bug that's causing the removal is indeed the way to > delay the removal (mind you, there's some delay between updating a bug > and the removal script being aware of the ping, so don't wait till the > last moment). In this case slightly inappropriate as the bug is in > another package, but we don't have anything better. Right. I was aware that the underlying issue was in iitalian. I began preparing an NMU but then realized that upstream project is dead since years so maybe better to let the package die as well. That's all why I chose to not ping the bug. Thanks again for the explanation. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
delayed package removal from testing
Hi release team, I wonder why debian-parl was removed from testing today, since (as I understand it) the reason for removal was solved 2 days ago. Not complaining - I know it should only be a matter of few days be getting re-added automatically - my concern is if something similar happens during freeze as that would then require manual intervention from you at a time where you are already quite busy. Is there perhaps some spell I could have thrown when uploading a known close-to-deadline package? E.g. the trick of posting something to a bugreport to reset its timer? Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#991165: RM: compass-yui-plugin/0~20100724-4
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please drop compass-yui-plugin from Debian testing. It is dead upstream and obsoleted by newer major YUI releases. Last dependency, debian-design, dropped its dependency few days ago. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmDxVowACgkQLHwxRsGg ASEsNA//UI4BOdreODXSKgL/NA2H1Z8xDXnfzi3brxpmyfWV8lYn/9nQqG1l/3/d kf7GjScsWbH0Bap7d4G4zFTb8DfEF1JmBRkE8MrVT0KABiCiR12+rlLPNsFrAleA qo5NDgRsU+3QVxVj8feV2eg2MHTRziBjfg4qF/kGy46Avk7BvDc6GGQ+XwCCwI/i YNN4bCX8T6zyotSHRrv+aK6TaQQ0B6c7KnqLWI85z9PLLfCguvR1lwkZ/ejcdK77 ROAgpGVJIBS74pF5lLKdvDOz58BZt/CrEevcNCAAalU0IgjUbIk9zbL8vlgjubCz SpOvaSfa+yPdSCUFtmwGf+Te7hOuflGG1NEgRZKXB23XG3eWbKtikrsfo8peVFab iVPIc80jp1FWbQY/9YzZsyN+HqQixdO9HDkDeK6e/u2sm0dhA7gmP3EbM9rHm81b x7IWi8v+2ORFpGmyl8+sqprjVUL8jU1YThCeAfzbK4dPZ3ozZq61Dc5xs+Qw16Gt apYJUXZAuS0eDd6VlLGOnF9G3CdSqbwIUIhj4U5vUvxBXWaUj8jyZg/+Ecuk7f6m 42aUVb0qIw7OkExP8KA6RhQPRuTwYeMX719eHUFgmcSiLwM8EQyLFqRA4j6qWwE9 N0gT5k/SLq0wNrgkrbtpVR0Ti/V71XkEmtr4Z3yy3U811JR6hOo= =Cl/8 -END PGP SIGNATURE-
Bug#991164: RM: compass-slickmap-plugin/0.5.1.1-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please drop compass-slickmap-plugin from Debian testing. It is dead upstream and has little if any use with modern Sass tools (it has closer ties to ruby-sass which is also dead upstream but unfortunately cannot be dropped yet due to reverse dependencies). Last dependency, debian-design, dropped its dependency few days ago. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmDxVlAACgkQLHwxRsGg ASG+QA/+KttDnbsflcIvAsCzVfZnEGdlG3Ep6PiCLNf/kGGB94G0BK98aj9+AL62 PMIwuopMUiw4dBvJ4IgxEDqSBeYCFqUNB2OEtlLKFPwBf2TqOxpGcJ8kfyWSHmxb jIy+yiYiAi5xyRpnPKa8vlmyIXuCG4CzupHctQ6NwM5Kx9orRjEZ4hQoeakd7hR2 PVPZsr3fvBToejdalQUeDzneO2RvRyaomw26rInVFLw9XEWEtM/lOkrNjRrMD84m b+72btX5zaTmfKWRzCVPvlzmF0CP8NgHaV9khXSkovST9cZrGBMrp6lJibAX2psb CUhbr6vjEMkOUxPrVhey612FzSx3cNZzpl69gA3ZEvrkO2fkgR2ALUcwbyJ0M61A JiMAV5mETxzxb3k6cHWtdIwrVUj3XMKL1Hx+pwgjEpj6y0PIaI0W3SQ3iPPFet8e Aqo2jcM3JKq9wN5ma7XpWhT7n83K/X5qlPAMp7s8sFERE20anSG0VxmTJn+PrrKF xki8hYt+7mPwqdL3HB6naECyuyHfSAwzmatC9xK2X0RcrcNp7R5rHWW2eVYTuTRH HIHX6C21I1pR/IAela6H0H/9ETnzOY6z79P0pR9sZ61/6GfuIGRWqGx25/b3DnJx uzWxSFiDptfYrU2rekQquPBt527cPDlV68/f1whpHb+1VrakLjk= =V71c -END PGP SIGNATURE-
Bug#991163: RM: compass-susy-plugin/2.2.12-1.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please drop compass-susy-plugin from Debian testing. It is dead upstream and obsoleted by newer CSS3 Grid techniques. Last dependency, debian-design, dropped its dependency few days ago. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmDxVd4ACgkQLHwxRsGg ASGbRQ//YS9UYzgPHozwOmwZoMdmQC8NnwlfLXITfmvGBez5BvNSH2NhgEaHq1sN DBSvK1T+EQgi9XesgKkzxFftax1bnZC9R5n/Wt70z2ImQMk9dFp7ckl3HQ67I2Ir MQudkZFjXYyEJPSp95fzK1cUqkOtzidOWEnnbEXffv1t5CIOaLOd1rh1Par7y7En GuDnYcNq6JR+2lEzjP1Rlupl7PHghBjwphUvXqXo8q7vyxfClTrh4BF2a2hqIqJb 9GKUr72wiKmX66HvTo75mWT8WLPoEEMD7yCPU0Otb2RLA6kM7tXIKu3PUpMsSpWR ohIAWtcLaEKcUCTBgwSM8a+9alrfBByCXfWmli/seC1v5i868h3NmFb9EH5Ylf+h CAm1BS4TbSViwv7TrIcxElchhZgjaZP9HDfZNr5/C6cle0ae2xFBOZFPJxxUB2x6 NMh7nSzkJeheuTJ2QizYS4OZ7clZ+OBp1ZFjeBRaKGAqnd/MPPlavrmYRgAytPoi p5biCxA6A2uaKMhkWDTf2WYQTTqkcLLXsMjtomrK5cUDkqFdI3W7Sz9AUKgQVJ70 Zu6XJ1y84RXAy6bsVW2IfrT+buwfGwpKNDKH4beXi0czvVFb9su4B3f8EdTMA7Lu 16m1wVI1rulXpgzalUyhDy5GByWTFLQUZ/AwNbvIGN4o5v7yA+U= =/t8U -END PGP SIGNATURE-
Bug#991162: RM: compass-singularitygs-plugin/1.8.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please drop compass-singularitygs-plugin from Debian testing. It is dead upstream and obsoleted by newer CSS3 Grid techniques. Last dependency, debian-design, dropped its dependency few days ago. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmDxVYoACgkQLHwxRsGg ASHBNg//VvBv8OcMWcBp5EAu+r+q2O3iLJKGMBKb5WL/inrRikEoC7pZ+pkqm/RZ pcC6qUaHtnRkej60YTdX33o6Tm9a7SO3jB7UW0BEh/HQrLB3GZ3pxwAUaK1mQ8Gs c7ZSy6c/rNlFe16ZJpQHpT9/2VSZihwzBMAyko9xluZ4Y5yvSaE6backKArIaHrh Amgn07znwmLwy+tad7uvC3MF0kgNLqhwJ2i0L9wqSwhfwMprGhi4HWLzabB3V3QQ BjOckVjv1Wl3qTeEzceT9pmLx24ozxZWASSShLJLBeLEug4jYCfFam5txPYIO+XI q/zjvOdaAyXwg8A63FR7RlLeySW2yXdB/QJ49eoGhy5rPJByy+CKdBHd8V1Fpqbb A18yfgOo+XjhV49pJdxDOYJR+owoTWMhgxqh8BPP2bm2ZhxAnToskIc5QshOvZGF zbtH0YTq+vcWtpyeY5GTExi0sZqxTYR9oc7xGzm7KWPGf8ZT6CiI9GkrkbbLY5cv uswrbB1xeq/QtjgED7RZvt6KvWtoQj5yxlxnifOONFWlnqQnKhuKOzWeSt5FSrb9 Goxvpk7ANI++veIjjeQWPAPjqmRxZaP7S5mbN0hK7SYuSpD3IlLqtx3/gCyq03S2 RolJ9OOVgr5cESsOyRx3Yr1TR8/c28mM5ijkIegxvdw4y0+BTAk= =Q95r -END PGP SIGNATURE-
Bug#989851: pre-approval unblock: uwsgi/2.0.19.1-8
Quoting Graham Inggs (2021-06-16 17:12:00) > Hi Thomas, Jonas > > On Wed, 16 Jun 2021 at 16:07, Thomas Goirand wrote: > > I'm hereby attaching the output of: > > git diff -u -r debian/2.0.19.1-6 -r debian/2.0.19.1-7 > > Thanks. > > > Maybe you could unblock debian/2.0.19.1-7 considering this is a > > target patch? Otherwise, Jonas may agree to revert the patch? > > According to the upstream commit message, these TSRMLS_* macros were > inert since PHP 7. If you and Jonas can agree that this makes no > difference for bullseye, then I will unblock uwsgi/2.0.19.1-7 and let > uwsgi-plugin-php/0.0.12 migrate. Thereafter, you can upload > uwsgi/2.0.19.1-8. Correct: the changes in debian/2.0.19.1-7 should not affect Debian. Sorry for the mess. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#987363: RM: janus/0.10.9-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 As tracked in bug#946412, janus is unsuitable for long-term maintained releases and should therefore sbe dropped from bullseye now it is frozen. Thanks, - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmCBcFoACgkQLHwxRsGg ASFe4A//UxMow4rUwQ3nhh4TpqP4PHqhOBvD1D+0E7CKZbgDiCt8rdFx2wr8VorT 2jofqz3qP7xYFgiV+zINW1L5F9pml2CzMHO78moFo1L3rTNADNRnV9MOiB5wj9Vw 35SkylzqWBnRxIPpNgDV/TAqBXGDsLwiXtPLuYxWx1yYOogqbOJKMHKAgTh7KU1d eAvAcnTvVUpAZA9rKi36+5ZZfFGfrvcBJIU9Ag+q066re1d8URi+X5EkzqBrFJyS IIryHS83azAW80ddlJIypmqi7lso0C1zwS08IO+UPIOF9fVbta5egpKixnSQIMLe aXN/ZiUL/CYl5iIecwm9JsQKN2B7ySZeYVxM7DPpk/o3j3apCCITNWY5WmRyFstC HrnuUiKIorgodsyc7wNiohedmE2h8KLk9lSCEBvyaInR+w0x34kShTOO1qVSr6Kb +FETWmk+1IOYc0ufZ5HsqHATRbnlfXFFy7rRf1OTmLRSU5ynPAUWQlRNlrnH8SKv IHZG9KMapy0JK3SI5SxhbHeLNhBpqm4up8geQgouxJTlzlkxcnC40EIyHtm6meer entT5pLXeCPDtvdwQMpZJo0zdxmDcFA5krjLoRKPQ9sEQYAVuOq8wswwrqH/lBbc bgG/pLj5cBeSfY9vEwkR9YO0EnfxLvNbKILvY5Tp8oRfJFsFm8M= =wMkA -END PGP SIGNATURE-
Bug#987352: unblock: leaflet-markercluster/1.4.1~dfsg-10
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please unblock package leaflet-markercluster [ Reason ] leaflet-markercluster/1.4.1~dfsg-10 does not work at all for its main purpose: JavaScript code can be structured 3 different ways: a) for server-side Node.js use, or for client-side browser either b) in old-style UMD form or in new-style ESM form. Officially upstream, Leaflet and leaflet-markercluster provides only old-style UMD form, so that form is generally expected from users and must work for the package to be considered in working shape. Patches exist to also support new-style ESM form, while still supporting old-style as well. Leaflet in Debian includes such patches, and leaflet-markercluster since 1.4.1~dfsg-9 does as well but the patches used turns out to not work as intended and broke old-style form. leaflet-markercluster/1.4.1~dfsg-10 has switched to a different patch set and has been tested to properly work in old-style UMD form. [ Impact ] leaflet-markercluster/1.4.1~dfsg-9 now in testing fails to work for the official use in old-style UMD form. Concretely within the realm of Debian itself, it seems that this will affect the package wireshark (but seemingly for an arguably exotic use requiring custom configuration to enable a Maxmind GeoIP dataset). [ Tests ] Tested that the map http://purism.biks.dk/world/staff/ (authored by me) works. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock leaflet-markercluster/1.4.1~dfsg-10 -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmCBNxkACgkQLHwxRsGg ASHEig/8CoGI6N58GoheKfhgq1hcorxTiQyYf2MeFEopRnJFWSLMYI4Qkk0j0tn6 dOjft4fYIuD9D2pcpyh1rdO68zAWfgsjRTjBZc+uEvTUig/AM/PZinMc2saWoD+b IwmLeHt/wRbuPj8r6Q5SGKeJgDI1f3yAKc1R9Y1t85oMAKgA2ztVFpp2m554xKuA aoXof8obBDmrgCC832SnOvapgNZ/Vll9xiFEeCavyTOKVrYR4m2Bj0X4h58NviJC 2RUIjHAUt8KMqHFGIIIjrqEWU28wUO3cqvGeJkPkpnNIONvfogzLDlnCxQJ9U9q2 beWKBLidpFMDYJ8xMUxZfKxr6z3X0qWsBjhyslX6RdTY5Y8sGKAW1HWNdjeVaTNm Rzn8K0JTeZygNex71vXp6U3rSLx2qyVNZcROFHGJDam2EiaGcDIUK44s+ysaZkJ9 M/ECvjFudo980GZ3EiUA2glWpVqZymEmCUY80z5+nRntoy9XY6MoDL7TkcIyrLHg 8z35/SnX1sRtOc61Sw2wqxFHRCPA7FxQhLNKiqdH4aTKVonpjPv04fAIT7y7iVvg SocFCRSzOn3OuQhUDGhWWXSg9kKXj0tgRajR4xSrUTbrlZHufVtgHGnV4rAGkAK1 8dY/b2TQ3RN6mpyJvk2+OQ8cgSTowVlXFLbT3bbGA5Uzb+RrCDU= =GPQY -END PGP SIGNATURE- diff -Nru leaflet-markercluster-1.4.1~dfsg/debian/changelog leaflet-markercluster-1.4.1~dfsg/debian/changelog --- leaflet-markercluster-1.4.1~dfsg/debian/changelog 2020-12-02 22:08:03.0 +0100 +++ leaflet-markercluster-1.4.1~dfsg/debian/changelog 2021-04-21 12:23:19.0 +0200 @@ -1,3 +1,13 @@ +leaflet-markercluster (1.4.1~dfsg-10) unstable; urgency=medium + + * add patch cherry-picked from upstream pull request +to avoid global L using Rollup plugin inject, +and stop use earlier more invasive yet non-working patch; +build-depend on node-rollup-plugin-inject; +closes: bug#987128 + + -- Jonas Smedegaard Wed, 21 Apr 2021 12:23:19 +0200 + leaflet-markercluster (1.4.1~dfsg-9) unstable; urgency=medium * use brotli compression suffix .brotli diff -Nru leaflet-markercluster-1.4.1~dfsg/debian/control leaflet-markercluster-1.4.1~dfsg/debian/control --- leaflet-markercluster-1.4.1~dfsg/debian/control 2020-12-02 22:07:39.0 +0100 +++ leaflet-markercluster-1.4.1~dfsg/debian/control 2021-04-21 11:46:33.0 +0200 @@ -8,6 +8,7 @@ Build-Depends: brotli, debhelper-compat (= 12), + node-rollup-plugin-inject, node-rollup-plugin-json, pandoc , pigz, diff -Nru leaflet-markercluster-1.4.1~dfsg/debian/patches/0~020200121~60a6e18.patch leaflet-markercluster-1.4.1~dfsg/debian/patches/0~020200121~60a6e18.patch --- leaflet-markercluster-1.4.1~dfsg/debian/patches/0~020200121~60a6e18.patch 1970-01-01 01:00:00.0 +0100 +++ leaflet-markercluster-1.4.1~dfsg/debian/patches/0~020200121~60a6e18.patch 2021-04-21 11:46:33.0 +0200 @@ -0,0 +1,44 @@ +Description: Do not rely on global L +Origin: https://github.com/m1gu3l/Leaflet.markercluster/commit/60a6e18 +Bug: https://github.com/Leaflet/Leaflet.markercluster/pull/984 +Author: Michal Przybys +Last-Update: 2020-01-21 +--- +This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ +--- a/build/rollup-config.js b/build/rollup-config.js +@@ -1,6 +1,7 @@ + + // Config file for running Rollup in "normal" mode (non-watch) + ++import inject from '@rollup/plugin-inject'; + import rollupGitVersion from 'rollup-plugin-git-version' + import json from 'rollup-plugin-json' + +@@ -36,8 +37,14 @@ + legacy: true, // Needed to create files loadable by IE8 + name: 'Leaflet.markercluster', + sourcemap: true, ++
Bug#987079: unblock: boxer-data/10.8.21
Hi Paul, Quoting Paul Gevers (2021-04-17 21:23:53) > Control: tags -1 moreinfo > > On 17-04-2021 11:24, Jonas Smedegaard wrote: > > [ Tests ] > > This bug is covered by autopkgtest (that's how it was spotted), and > > the bugfix is confirmed to succeed that test. > > If you fix the autopkgtest to not be amd64 specific, but also work on > the other architectures, in the current phase of the freeze it > wouldn't be blocked and we wouldn't need to unblock. Please fix your > autopkgtest. Oh. I thought that "hard freeze" in effect since March 12th required unblock request for _all_ packages - not sure how I missed that: When I now read (again, did it multiple times previously) the text is clear and I have no ideas how it might be improved. Sorry for this needless bugreport. Also, thanks for pointing out the arch-specific tests, I had forgotten about those. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#987079: unblock: boxer-data/10.8.21
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please unblock package boxer-data (Please provide enough (but not too much) information to help the release team to judge the request efficiently. E.g. by filling in the sections below.) [ Reason ] the removal of citadel-server from bullseye caused the autopkgtest for boxer-data to fail, as tracked in Bug#986726. [ Impact ] boxer-data is used to generate package lists e.g. to build metapackages. This bug occurs when using boxer to make a list of Debian packages which epxplicitly excludes all packages providing an MTA *and* using that list in a context which chokes non-existing packages being explicitly listed. No reverse (build-)dependencies are affected by this bug, but direct use of boxer to generate a local metapackage or script to avoid MTAs on a system is not an unusual use of boxer. [ Tests ] This bug is covered by autopkgtest (that's how it was spotted), and the bugfix is confirmed to succeed that test. [ Risks ] Code change needed to fix this bug was trivial: commenting out virtual package "citadel-mta" previously provided by src:citadel. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock boxer-data/10.8.21 -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmB6qV0ACgkQLHwxRsGg ASHFwQ/7BP9ePDsqLJwobkIWd+TCk/+KcHCFSKEz8uOSYQLerj+F9SOh606tiaza ntUYxYThp0dvy1mXOM98OjfRp5XAfzCTuZDeYwxZG2idE2Xzhn/qnGMRU4dKHpsG p7tPA2K7qbF95PiI3ouZmhilPZiUigcEWiH/KyZYTKxTB6Hool4spiTyml4nhF9a eOk75FQb/q/6RJ9EFkeJp8H1Zr0m/MPSUwMkXtZthNCA7ExWxgNkNLzMjoN4wuBs Z+b+P2AGpoLF7ELh+ii6/TgfdRaABe+uhy1XlRX1iZdCQ8yjCK7MQTBJnk/pzSTf XGMQmCSbOxQvsefgFaZXRJs5+sm3QaSeNj0r5TbA5aHWMnLsTzN/0LEr2DaraYPW QUG/e8yBj/SrfKUWGoKRIeVNSCtXbH3+vhKmAVB5KBZn/2s9ajbguuJZEcecCcpC KV3pUabWxrJAGrYEAS+OwDeR+svBOrPigLaoZMuv0PLrWlR7yXwt5/kDheka5+Js uRmDRGmKEqAT6aplaKb24BVRLG4JvY+mEg9CcjYB6MTGRQGPA3o5ilCsY6EynYz/ GF15QAz9DMaB61/SR28EKQdjss7OeXOlkJsuMIdaH0e4BDN/iGYXbrTtZJEtUBNm KrFVe7y0DypWaDB5CIJy3Pk3Hi8wmzUGFHDJDyCVYSYO96Unhfs= =/VWB -END PGP SIGNATURE- diff -Nru boxer-data-10.8.21/bullseye/classes/Service/mail/avoid.yml boxer-data-10.8.22/bullseye/classes/Service/mail/avoid.yml --- boxer-data-10.8.21/bullseye/classes/Service/mail/avoid.yml 1970-01-01 01:00:00.0 +0100 +++ boxer-data-10.8.22/bullseye/classes/Service/mail/avoid.yml 2021-04-17 10:44:49.0 +0200 @@ -0,0 +1,23 @@ +# FIXME: avoid citadel-mta (or citadel-server) when available in Debian +classes: + - Service.mail.base +parameters: + doc: +service-mail: + pkg: +- avoid mail transport agent + pkg-avoid: +- masqmail +- dma +- courier-mta +- esmtp-run +- msmtp-mta +- qmail-run +- ssmtp +- postfix +- exim4-daemon-light +- exim4-daemon-heavy +- opensmtpd +- sendmail-bin +#- citadel-mta +- nullmailer diff -Nru boxer-data-10.8.21/debian/changelog boxer-data-10.8.22/debian/changelog --- boxer-data-10.8.21/debian/changelog 2021-03-02 15:47:13.0 +0100 +++ boxer-data-10.8.22/debian/changelog 2021-04-17 10:47:12.0 +0200 @@ -1,3 +1,11 @@ +boxer-data (10.8.22) unstable; urgency=medium + + * fix class Service.mail.avoid: +stop avoid citadel-mta unavailable since bullseye; +closes: bug#986726, thanks to Graham Inggs + + -- Jonas Smedegaard Sat, 17 Apr 2021 10:47:12 +0200 + boxer-data (10.8.21) unstable; urgency=medium * update class Desktop.design.web.sass:
Re: why was bitcoin package removed from testing?
Quoting Paul Gevers (2021-01-30 19:49:31) > On 30-01-2021 11:50, Jonas Smedegaard wrote: > > If the release team consider bitcoin unacceptable for Debian stable, > > then please elaborate why. > > We consider it unacceptable for Debian bullseye because the security > team doesn't want to support it. Thanks for the clarification. Now, if only the security team would clarify... :-/ - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
why was bitcoin package removed from testing?
The bitcoin package was removed from testing some hours ago - https://tracker.debian.org/news/1225530/bitcoin-removed-from-testing/ references bug#718272 but that bug is closed. If the removal accidental (e.g. cause by bug closure flip-flop, then please consider correcting that by fast-trackign a re-acceptance. If the release team consider bitcoin unacceptable for Debian stable, then please elaborate why. Please don't just point to the bug log (as security team did): This bug log contains a variety of claims, and it is quite helpful that we are transparent about _which_ reasons Debian consider release-critical. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#980032: [Pkg-javascript-devel] Bug#980032: RM: node-request/2.88.1-5
Quoting Pirate Praveen (2021-01-13 13:42:22) > > > On Wed, Jan 13, 2021 at 12:22 pm, Xavier wrote: > > CC to pkg-javascript-devel for node-yarnpkg elements > > > We can try to update yarnpkg to version 2 by building corepack [1]. > > I need help with these packages, > > New modules: clipanion terser-webpack-plugin ts-loader > @zkochan/cmd-shim > > Update terser to 4.8 at least Draft of node-terser 4.8.0 is now pushed to Salsa - help making it work is quite welcome, just please do *not* introduce pkg-js-tools. > I'm currently trying to update node-babel7 in buster-backports and it > can take some more time before I can get to these. > > We can embed a copy of request in yarnpkg as a last resort. Do *not* embed for the reason of hiding obsoletion! If node-request cannot be removed then do not remove it! Instead, place it in package section oldlibs, change package description to clarify its deprecated state and strongly warn against relying on it, and file RC bugreports against any package that rely on it anyway. Then each such RC bug can be treated individually. Either lowered to non-RC, or better: keep it RC and request an exception from release managers. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#971022: how to override piuparts for package transition to testing
Hi Paul,
Quoting Paul Gevers (2020-09-07 19:24:22)
> On 07-09-2020 09:33, Jonas Smedegaard wrote:
> > Quoting Rebecca N. Palmer (2020-09-06 18:08:16)
> >> Ask the release team ("unblock" bug against release.debian.org, or
> >> debian-release@l.d.o): they can override the automated checks.
>
> [...]
>
> > (in the meantime the package magically entered testing, but still
> > helpful for eventual future cases)
>
> Not magically, but because I told britney to ignore the piuparts
> results. Some of the release team members are reading d-devel as well
> ;).
Could you please nudge it again? Seems to be in exact same limbo now.
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
Bug#971022: unblock: src:debian-parl/1.9.25
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please unblock package src:debian-parl [ Reason ] Bug in piuparts: https://alioth-lists.debian.net/pipermail/piuparts-devel/2020-September/009165.html This same issue was already unblocked by Paul Gevers for previous release of debian-parl, as discussed on d-devel@l.d.o: Message-ID: <842301ac-bb3e-f551-6bcd-422a7ebd0...@debian.org> unblock src:debian-parl/1.9.25 -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl9vNxgACgkQLHwxRsGg ASEX1g//UPscpilxby5wsQX62Fy8BCPUlpEcz9S6D5qXuCRqTfVv7/rnCRYYeQ3E EpFzVJTyYZh90AOVqSOEqPKOOaXczM5NHWfkS7Uc44DrsGWJNNAdDxc0yONfkTNT iNKiYatwv8RRcSblvb4XcEw5FvNzhHXen8Ofk92MormHlD+XaJPXacR9acykdaH+ eearUMSW7NMhFofh9vSIvSlD9q1zRrocuKQOxDVBN49TVluZr7GXe08ZEbEeszce jHZzgPblf/X2S5O9jIE2KmtPjcpJMKyRW2G1DwT7KEkh9a4lFijTOvOIC0XmDNEe VZ+fhOgXO0h3vb69Zyd7i/HmHEoieKbv/lYMMR8ZFT6wSkpzXMrqjsqF6ydupU2P pbykCsVm0Pdn3g03Nf2qmZlcCAbrpzle/sAb4qk5Gi8edbzLcEAbPu9TCN887RXU 9/5Dn2mi3hs5q2tCqpUtgbO6AM2l3QRiDoP74vJPJHrFN0e4VPwhlCKT8SQw+Nku JJvZZTgpvRmV2TWYSkt1EntVsoFXZyZwlzwGXd2vBVRzYTAo5uymhPfPxJeoUnbm b053ystkLIy4IX9s5zfSSaI9r9BS5NDiVnAyDHVs9FvZsJY+GzmGppxJxvSBAQhC f6rut2JPO2o1HQLg0SArQJm0ms50jTkVz8RLfqh6clgDJtAlfmw= =RP6H -END PGP SIGNATURE-
Bug#970491: nmu: ghostscript_9.53.1~dfsg-1
Quoting Paul Gevers (2020-09-17 10:22:59) > Hi Jonas, > > On 17-09-2020 10:12, Jonas Smedegaard wrote: > > Ghostscript package uses dh_linktree, which has this to say: >^^^ answers my question. > > >> Since symlink trees are created statically at build-time, they are not > >> very future-proof and have a risk to miss some files introduced by a > >> newer version of the package providing the file tree which is > >> duplicated. That's why the generated dependencies generally ensure > >> that the same upstream version be used at run-time than at build-time. > > > > In my understanding, ghostscript _could_ become broken _if_ a newer font > > package changes paths: Ghostscript wuold then ship with dangling > > symlinks (which might in itself be an RC-level issue) and this would > > cause some functionality of the ghostscript package to fail. > > > > Does that answer your question? > > So, because of the way dh_linktree works, every reverse dependency needs > to be rebuild. Luckily, we have transition trackers for those: > > https://release.debian.org/transitions/html/auto-upperlimit-fonts-urw-base35.html > > And the tracker/qa package of fonts-urw-base35 mentions it too: > Issues preventing migration: > migrating fonts-urw-base35/20200910-1/amd64 to testing makes > libgs9-common/9.52.1~dfsg-1/amd64 uninstallable > migrating fonts-urw-base35/20200910-1/i386 to testing makes > libgs9-common/9.52.1~dfsg-1/i386 uninstallable > > I'll binNMU shortly. Arrgh - I realixed only now that the issue is in a arch-all package. Sorry for the fuss - I will need to do a propoer release after all. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#970491: nmu: ghostscript_9.53.1~dfsg-1
Hi Paul, Quoting Paul Gevers (2020-09-17 10:04:39) > On 17-09-2020 09:43, Jonas Smedegaard wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: binnmu > > > > nmu ghostscript_9.53.1~dfsg-1 . ANY . unstable . -m "re-sync symlinks with > > newer release of fonts-urw-base35" > > > > A new release of fonts-urw-base35 was introduced to unstable, and > > ghostscript need to symlink direct paths for those fonts (not go > > through fontconfig) which requires a rebuild when font is updated. > > Without having looked at details myself, but what does it mean if we > wouldn't do this? I.e. is ghostscript broken? If so, only in unstable > because fonts-urw-base35 won't migrate? If the answers are yes to the > first and no the second there is something wrong with dependencies. Ghostscript package uses dh_linktree, which has this to say: > Since symlink trees are created statically at build-time, they are not > very future-proof and have a risk to miss some files introduced by a > newer version of the package providing the file tree which is > duplicated. That's why the generated dependencies generally ensure > that the same upstream version be used at run-time than at build-time. In my understanding, ghostscript _could_ become broken _if_ a newer font package changes paths: Ghostscript wuold then ship with dangling symlinks (which might in itself be an RC-level issue) and this would cause some functionality of the ghostscript package to fail. Does that answer your question? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#970491: nmu: ghostscript_9.53.1~dfsg-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 nmu ghostscript_9.53.1~dfsg-1 . ANY . unstable . -m "re-sync symlinks with newer release of fonts-urw-base35" A new release of fonts-urw-base35 was introduced to unstable, and ghostscript need to symlink direct paths for those fonts (not go through fontconfig) which requires a rebuild when font is updated. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl9jE4cACgkQLHwxRsGg ASG8pA//etjnTDdvRVtq4NE9pce/sFumfQqzWP8mJfXFhu/6EQu9RwPlkUegdMl8 AmpqifiJIf+v06gqGPvkME3LQltmHMfjEhZyBS+It6wpNpCivDsCQy7acVf5Foue 3Q13/5XcpHmngodlHPcIb25/SYiCgmzSHVIA9c2IEtyyERAJeDz6yPSN8J6N+8BX n7iiC3eM0X8w+g0O6r/Ua+RttTIwlvu2GzkWdowPQm5rfnBvY0FoltDPKkIEUt/Z cuu5BsiMF5tus+GyOeqL51sr9O0GKwbzzaJRVnSvBMtDAgstrgLez3MzWbNiUfLA rjFXtS3LWXVsP893MJAJ27VNqUE5S19oKWQpT1XtNC0ysUx53xWhBtfpB19wCnC0 rKRNn5PLiDaqtmhgF6nnS/4OiuvmdWP1UB/8uWMKtY4SUNa1SOvLElKOn1QNqNEM B6Gz6fhHdY3m6zdKjgFxMhnVFb48Z7BMDHBDE+1ykCkRjwG6Heosm1GCyMcwGIgC bvT2zykxOz9xPYMXkXC/TIwj9JEPRJLrSQgk2QYoQt5lzwxdU5nC4AQhT+RPvEfA L78NT/U2twsBAnA4usTQw+lhVx3zbFkbmH070vjRUP2Lgdc2LwMq5M7wOuhnpRRf rQfJUaN2HwqmVHYlP6R7N641KrJlGRcEE9nrZQBz7fJHGexnalg= =ASaf -END PGP SIGNATURE-
Bug#968137: RM: src:uglifyjs/2.8.29-6
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Source package uglifyjs is dead upstream (or more accurately that v2.x _branch_ is dead upstream, the v3.x branch is actively maintained and packaged as src:uglify-js). Please drop src:uglifyjs as intended by release-critical bug#958117. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl8wHusACgkQLHwxRsGg ASHLZBAAqpShYbX5Gs/B8n437fHqHU4ICRU4vBxLg5J7xlyYUlT+2bstdVjrHuWJ ZIaIoLRl8NUEmMHycBCU1CI/Kyw8sz6BP+Z6PvU54llC2+mMgbtV8MCZHCC8NZpc /1ayllMZa6MIQ/YhJb7Zmgo1PQsdHD0S6H8X4a0VS15gVJSOgs1a+OFlII0ixUDf jVBAobafrggJwGfxjDiHYwtHZ4Y7eijST7zqBg3+xJ2mYL1CpIp9/lLV7IcApj5O V1kacPFoZ6A6i5Qm9LgsnRjgr6xl32h8+tz9ZphQD/iWKbYV9bjZL4ILgWpcxTBJ pUe8LbE2KyNgi4CHJ3FRsaa2480XcjXucebmeFGpPvbt9da4kNF8u11lU6mqZp0R jwbNCgpq2U+pm7tEz5Oh6Yhr0fCKZK6f6K5sVlxfeDo78EyK/bO0AqIaxGZimCx+ JIQ4+leT5He52cNx+XxicdaVjvgPG64bVNt+07dBwRZcxXda6AK4CRmjs3jfTNzf iwo14S+LlJKV8ISsqm0R2R5HVBO1hiLbn+tVbp8MJpAbBOc30OuJdPPYJugwuDX5 Q5gFJJWhPe+mmu6LIhnO++VAWZN5Kj3ylimCoQiHo0vP3dEJQYU5/7pJc6LJ2O6F aAIPYa0GOWF7L135aMu5djKL8qIIYWLP99DsvtDIFr65l/9QrUA= =S+lG -END PGP SIGNATURE-
Bug#962694: RM: janus/0.6.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please drop janus from Debian stable (Buster): Upstream explicitly do not commit to long-term maintenance: https://github.com/meetecho/janus-gateway/commit/eac063c - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl7jMt4ACgkQLHwxRsGg ASH8Ag/8DVrxeiMMIezWlaoAyEJXNFs5yW9dwn1FoF4QkQ2AWCYakfKIG7n496Uc GAYgUFiieI61UojZ0I8r/8HMfkN8x+3CvTFbzzH0L6O3/9yf3e4PSRr0KjrGKBk8 j6/MzvpzLOn6kBYYs9ajT/zu8kE7kpZpLsmD+gwdIL07qy3jRfQtPL0pKDTns4xk Sjz2R2+1hhaj4OI7kHGiBujVRtPoRSZAs1+wlyd4JPUj3oO+Uuqo4yTp6PCdd6xb iG++1T1Fr/hjXOAPXHqMr1pdgU3izE7Vks+jipawbn+hQcaZpll+kO98NYsMcpPO KHFez1tK6PhTdatD6qmw2tAXn1xqvETLlHEQobCHjV9IBRkHHYo+duw3Zp1lbETc nBwOcKWJS8AT7YoHcFukI3S1d2pf+anV5qwRtuau+A8Lnl7LCBK/TLQOn4abzYGR NeyCkwQy9RSXRLW9cUpaAcPxUAgUCSF0/cgm8+zSXACP0u3EyFIiWnCS3JtXMNcV LxMKQzWEt833MZetcShjNnD2Ls+3UbkTS8XcHvSodXjzxChGgzw9GNj/vQzWsp1Y 1bPNErsrDKnmfqj/8OUGMj/Gglgs687TMp/WiYw7qhghOwaO2O84qtVLj2F7aQhC 0UyTDWyT6l2QUrp6ZzSxODmyqBF5GSpC+V3OJ/RzhIon/0CLdmk= =6SjL -END PGP SIGNATURE-
Bug#958561: nmu: eye_20.0411.2226~ds-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 eye needs same runtime version as used at build-time. A new release of swi-prolog-nox therefore needs a rebuild of eye. nmu eye_20.0411.2226~ds-2 . ANY . unstable . -m "rebuild to pick up swi-prolog-nox" - -- System Information: Debian Release: bullseye/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.5.0-rc5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8), LANGUAGE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl6h1FEACgkQLHwxRsGg ASG2tw//TDQe/eSZy028TjF99xMUyLa/thgOlEIP+Rnjvr8lbVI56ihftlPgXA04 m6aJgEtc5fAE/OUWrUel7WJk1VAP/OrCLzA90ZCTKM7WR2ayfLu9jqqxejoP3CfN 64VR8jdyl9A1+5JNpzXwzvcImPDHnn+0/w4A2k83JN4y0aulIQzsic8LskoedwSq l3W9S7aSy9WjhF+al4J5pxPbpKaWZDm7mPpOi1UaCDrZ/X0izcloF3U1CYg36L8O HjeWi0xhSrJTFl+V+7rC5swx+MtvCs5Zm63VLOaeMQY/gSbsxIWrWMHYVbZyjopK xJcufpZb7r3HLZpzAeCOpPQ+W4S+jy1Pa+yvxdHYuSN0v5fcm5fW3BX996yNJGVp nSyG81xhNvWgrkyDQKMxojAjr4ZbUNtP4WoTyA5AZZqzImEWw7M1ScM8zGJInpng asLp6Mm6qbKP8TgrDCt6OwGCu4vYMs2G9X/NBIpOnK2mzRvYn5O65tzpq2S762Nk 0c3vj4XsGbVl4xX1PquX+4tN10LOokXWkzcmPPo+usDTLvfwbUYt+M8WLEniPbjF +iQgQbt0TgK/X9QK+v9M6yM9CEYQLb+QZidN7UfjAVTeSgnbbwrW4e8Za9nlRRUQ wR6j+ttmU5z+Uir6BGzMFWbRnAyrmLsowfvxKkr5XK4ZelFi6Bg= =UBYJ -END PGP SIGNATURE-
Bug#940632: nmu: mupdf_1.15.0+ds1-1+b1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi release team, Due to libjbig2dec0 upstream API being unstable, and a new release of libjbig2dec0 introduced a new symbol, mupdf needs a bunNMU to catch up. libjbig2dec0 tracks symbols changes, so a simple rebuild should properly tighten dependency to only the new API. Please rebuild mupdf against libjbig2dec0 0.16+20190905-2 to bump its dependency on libjbig2dec0. nmu mupdf_1.15.0+ds1-1+b1 . ANY . unstable . -m "Rebuild against libjbig2dec0 to correct dependency" -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl2BzTYACgkQLHwxRsGg ASHWFg//abNUxllNBJ1Y3srHCddAlIiZ89nZx3dPOFJIptNBUWJM+07ggrChzNJC 6PPel6F5jQ8i7wDt6SRCrkfZMgve6T4vFm0nMiOSm2lWlojGfRuMqtxhX+YmdBFt o8piYgvvQ1K2Eg2P0hJ74O435bgrIIt1+TkyOWu6OHOBGPlbFDaOeqoZnAeygFpm NqHJBkuqWJNtoTMEYWnU4n+sbHFCg7OIIRq6HOMCT66ZmKNj0dg6Mx39/EX1YTMz TuaZ+uBkLtx26NBZdngE7HxyKv2/MeQGIHJKGh5maNnv0oB5WNGOedgNM7mPwu3C UmQTqc4+28HBk0NFrdImt+BTPPKHkzaNb3AZZ3mPzE0FmOwPDl0XhEIt90D07nTF lrMiC3li3tNx8UfAIIiJv9B1n3p1g964/sejnGjBCXNhPwsZoQhJxgmWAHjNEfAB tK1odp6b5CGIT67/pGfat23/IECsKQXPrrLVWscGtmkJSh/s5Zfx65wT6xPRlnRq mOJ0NMGUgJk/Cu/2fmGa7vAH9b51nu/fXqArOdS8kxla6tW2gIB+mdTidue3zlSn /iMYuuQEYYzZD8v7IIBpYf7Nd/0z2U1vrNYH4BpxWEDq3JBjte06k4ZgZt/Dk5f0 LnSpowUV4ETHhzNJi8QN3K4DCYczGPf3Q9Slul435Xc83b63p58= =f6Tn -END PGP SIGNATURE-
Bug#929873: unblock: radicale/2.1.11-6
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Please unblock package radicale
Compared to -4 now in buster, -6 now in sid contains a fix for bug#919339
which affects new installs (not upgrades) of Radicale.
This is the diff for the bugfix specifically:
- ---
radicale-2.1.11_buster/debian/etc/uwsgi/apps-available/radicale.ini>2019-01-15
02:40:10.0 +0100
+++
radicale-2.1.11/debian/etc/uwsgi/apps-available/radicale.ini<-->2019-04-08
22:07:57.0 +0200
@@ -39,13 +39,15 @@
module = radicale
env = RADICALE_CONFIG=/etc/radicale/config
.
- -chdir = /var/lib/radicale/collections
+umask 027
.
- -if-not-exists = /var/lib/radicale
- -exec-as-root = mkdir -p /var/lib/radicale
+if-not-exists = /var/lib/radicale/collections
+exec-as-root = mkdir -p /var/lib/radicale/collections
endif =
if-not-exists = /var/log/radicale
- -exec-as-root = mkdir -p /var/log/radicale/collections
+exec-as-root = mkdir -p /var/lib/radicale
endif =
- -exec-as-root = if ! dpkg-statoverride --list /var/lib/radicale >/dev/null
2>&1; then chown radicale: /var/lib/radicale /var/lib/radicale/collections;
chmod g-w,o-rwx /var/lib/radicale; fi
+exec-as-root = if ! dpkg-statoverride --list /var/lib/radicale >/dev/null
2>&1; then chown radicale: /var/lib/radicale /var/lib/radicale/collections;
chmod g-w,o-rwx /var/lib/radicale /var/lib/radicale/collections; fi
exec-as-root = if ! dpkg-statoverride --list /var/log/radicale >/dev/null
2>&1; then chown radicale:adm /var/log/radicale; chmod g-w,o-rwx
/var/log/radicale; fi
+
+chdir2 = /var/lib/radicale/collections
Attached is the full debdiff, additionally fixing/improving documention
and example code, and adding a missing package suggestion.
unblock radicale/2.1.11-6
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlzzl3kACgkQLHwxRsGg
ASFOqhAAgfaSAZNh2OzRAkbtU3j+63mDnsQoWcf2Rr4sVeG4Td+/qveDyNWD79w/
86OiQ9DwZQB4HnYSKTWJJCGgUFl+kHfokpB/vVM14hbvcp/nft2bbrbscxqScSro
PBUXi/aQrsnGru6bCp89yp3AG7cieBaa6RRBKanOsdeZSwmdksZAgM8QWTAs+YNn
efQe63AGDxlnAwweBUmR3dLzDZXLhVyrshgPoHBnAwZj07svsnek9pSQeYYrP+jR
t2P5I+0AyXyJQw922WNyRynl+PXFrMXPJevFMzwVuVAAxRGTWqTModPFr3CAdgF+
2WZnCHcc1xZa1TYoSLk8JYhEcpfc8Y9FuwE2AGhW8MBJ/VNJfHRUOinnBaNE66zV
6mnqbV3ba450+v1IqHGNLVSrRp8UpJZdkFpRJ+7hSM2dGK82ht0fEpTFPpZWsPxI
7UtpcVrDvlLPSH3QI4LLiq/Z9dafyE2v+Ur2v3tyZR4kqbcqJzoZ0EgfBO3jeAOc
L0Y2fRTN6ddiMj7pTFZlE8fo1ZG813CM8RgXGZQakZYeRJEFyfQ62qQK9NmTGJjo
1bU41JGqlnXq7039Pcj7iwftzkCnRJo11ZGpFkELMFVAhxiyqPTalloH8mHmmC3I
p5HfAChID8VkjpTa7Myvf6ZuN+uo7dJbJVI8ca8RE2NMdVfEwPk=
=r5Mo
-END PGP SIGNATURE-
diff -ruN radicale-2.1.11_buster/debian/changelog
radicale-2.1.11/debian/changelog
--- radicale-2.1.11_buster/debian/changelog 2019-02-07 02:28:00.0
+0100
+++ radicale-2.1.11/debian/changelog2019-04-08 22:11:56.0 +0200
@@ -1,3 +1,26 @@
+radicale (2.1.11-6) unstable; urgency=medium
+
+ * Really fix directory creation and access rights of /var/lib/radicale.
+Closes: Bug#919339. Thanks to Slavko.
+
+ -- Jonas Smedegaard Mon, 08 Apr 2019 22:11:56 +0200
+
+radicale (2.1.11-5) unstable; urgency=medium
+
+ * Update watch file:
++ Rewrite usage comment.
++ Simplify regular expressions.
+ * Fix suggest uwsgi-plugin-python3,
+and adapt long description and README.Debian.
+Thanks to A. F. Cano.
+ * Fix typos DOMAIN → _DOMAIN in example vhost snippet.
+Thanks to A. F. Cano.
+ * Fix have uwsgi snippet create collections subdir below /var/lib
+(not bogusly below /var/log).
+Closes: Bug#919339.
+
+ -- Jonas Smedegaard Mon, 08 Apr 2019 12:52:13 +0200
+
radicale (2.1.11-4) unstable; urgency=medium
* Add NEWS entry about incompatible changes to storage format.
diff -ruN radicale-2.1.11_buster/debian/control radicale-2.1.11/debian/control
--- radicale-2.1.11_buster/debian/control 2019-01-15 02:41:55.0
+0100
+++ radicale-2.1.11/debian/control 2019-03-27 08:18:37.0 +0100
@@ -44,6 +44,7 @@
python3-bcrypt,
python3-passlib,
uwsgi,
+ uwsgi-plugin-python3,
Provides:
${python:Provides},
Description: simple calendar and addressbook server - daemon
@@ -62,8 +63,8 @@
python3-bcrypt.
.
Serving directly with uWSGI
- requires the package uwsgi.
- Serving with Apache as front-end and uWSGI as middleware
+ requires the packages uwsgi and uwsgi-plugin-python3.
+ Serving with Apache as front-end and uWSGI only as middleware
additionally requires the packages apache2 and libapache2-mod-proxy-uwsgi.
Package: python3-radicale
diff -ruN radicale-2.1.11_buster/debian/etc/uwsgi/apps-available/radicale.ini
radicale-2.1.11/debian/etc/uwsgi/apps-available/radicale.ini
--- radicale-2.1.11_buster/debian/etc/uwsgi/apps-available/radicale.ini
2019-01-15 02:40:10.0 +0100
+++ radicale-2.1.11/debian/etc/uwsgi/apps-available/radicale.ini
2019-04-08 22
Re: Is ghostscript/9.27~dfsg-2 not going to testing?
Hi Hideki-san, [adding bugreport as recipient] Quoting Hideki Yamane (2019-05-23 03:18:01) > Hi again, > > Is ghostscript/9.27~dfsg-2 not going to testing? > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927429 > > It seems that it should be in there. Yes, agreed. I am lousy at dealing with release team. Help much appreciated. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#927681: unblock: khal/1:0.9.10-1.1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Please unblock package khal
Previous fix for bug#908497 (FTBFS with python-dateutil 2.7.3-1) was
incomplete and hid the real underlying problem.
Release 1:0.9.10-1.1 replaces the patch introduced in 1:0.9.10-0.1 with
the corresponding patch cherry-picked upstream.
unblock khal/1:0.9.10-1.1
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAly8D/wACgkQLHwxRsGg
ASF8IRAAjOZxfUyRsypsRARlnht7k3Tw9/ZSzWCI4Ml4v0azph9C52vi0nfL7cBN
hAZ8wSj4uumTLITYRyt2l38U17nlfvwrWt4D9Pv0AHWGZVBRGdsGjiSS03UIm9QX
an+rjx5GhL+r1/mFhgHgC0Pb+fvotV7pMZ89rSxy3g1gv1Xt6Cxcm9zW2ME+ZjOT
uofAhDB4nl5EbTOxXCEw/q+kgATgmS1CNeErWdj7iu86oKTDVfcYpW2nb0ldM2TL
Iw9aDDgJey+cvpCeGad/lxsOZTBfNU/Nn1SgkIXWHWcb5FcuLlXlSsvBLlcxl0h3
g6RPtp9aT1a1nAkiKIfjCr7r4WoDRsrsBweeiFIgVAuxADjnnKzfRaLMcjralEzA
NQgGVsxueJnj8NoMd1lYJwqALaeT5uaDVi8BXUAnBYpC/zqmh89Qx0bhQiS4Miic
ID4FUNel48X1W7i/UZ1aNJcaf/LrfMaQlImp7Ns4MCdpy20jwwSSt7m4vFpsjUbj
Hz6DFf7Ffx6njRhJ2wPtDoEZL1kp+6wrNOIYgctlu8ZzG1M73a3jfTB/pAciPWxu
5quR1cInyFuEQ15pe0Yk5P7jnokadIDebvcRlasUSu8bMLNQOCdQIOBi23EspFLk
IL4v2nQiuJZShHO1OGiczJc4Og6d1O12cNUT8nTFFVVpc4H+0AE=
=qK2A
-END PGP SIGNATURE-
diff --git a/debian/changelog b/debian/changelog
index 292fbb6..3100246 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+khal (1:0.9.10-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add patch cherry-picked upstream to fix parse categories as list,
+superseding patch 0008 only fixing testsuite.
+Tighten build-dependency on python3-icalendar.
+
+ -- Jonas Smedegaard Tue, 26 Mar 2019 09:56:46 +0100
+
khal (1:0.9.10-1) unstable; urgency=medium
[ Ondřej Nový ]
diff --git a/debian/control b/debian/control
index 254176e..d0501fc 100644
--- a/debian/control
+++ b/debian/control
@@ -15,7 +15,7 @@ Build-Depends: debhelper (>= 12),
python3-dateutil,
python3-doc,
python3-freezegun,
- python3-icalendar,
+ python3-icalendar (>= 4.0.3),
python3-pytest,
python3-setuptools,
python3-setuptools-scm,
diff --git
a/debian/patches/-20190325~c58fb88-fix-parse-categories-as-list.patch
b/debian/patches/-20190325~c58fb88-fix-parse-categories-as-list.patch
new file mode 100644
index 000..1d69783
--- /dev/null
+++ b/debian/patches/-20190325~c58fb88-fix-parse-categories-as-list.patch
@@ -0,0 +1,121 @@
+Description: fix pass categories as list
+ Support (only) icalendar >= 4.0.3
+ .
+ With icalendar 4.0.3 the CATEGORIES Property became a list
+ as mandated by the RFC.
+Author: Christian Geier
+Bug: https://github.com/pimutils/khal/issues/825
+Last-Update: 2019-03-26
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/khal/cli.py
b/khal/cli.py
+@@ -335,7 +335,7 @@
+ @click.option('--location', '-l',
+ help=('The location of the new event.'))
+ @click.option('--categories', '-g',
+- help=('The categories of the new event.'))
++ help=('The categories of the new event, comma separated.'))
+ @click.option('--repeat', '-r',
+ help=('Repeat event: daily, weekly, monthly or yearly.'))
+ @click.option('--until', '-u',
+--- a/khal/controllers.py
b/khal/controllers.py
+@@ -349,6 +349,8 @@
+ categories=None, repeat=None, until=None, alarms=None,
+ timezone=None, format=None, env=None):
+ """Create a new event from arguments and add to vdirs"""
++if isinstance(categories, str):
++categories = list([category.strip() for category in
categories.split(',')])
+ try:
+ event = utils.new_event(
+ locale=conf['locale'], location=location, categories=categories,
+@@ -489,7 +491,10 @@
+ value = prompt(question, default)
+ if allow_none and value == "None":
+ value = ""
+-getattr(event, "update_" + attr)(value)
++if attr == 'categories':
++getattr(event, "update_" + attr)(list([cat.strip() for cat in
value.split(',')]))
++else:
++getattr(event, "update_" + attr)(value)
+ edited = True
+
+ if edited:
+--- a/khal/khalendar/event.py
b/khal/khalendar/event.py
+@@ -409,13 +409,16 @@
+
+ @property
+ def categories(self):
+-return self._vevents[self.ref].get('CATEGORIES', '')
++try:
++return self._vevents[self.ref].get('CATEGORIES',
'').to_ical().decode('utf-8')
++except AttributeError:
++return ''
+
+ def update_categories(self, categories):
+-if categories.strip():
+-self._vevents[self.ref]['CATEGORIES'] =
Re: Is using experimental distribution for shelter during freeze useful?
Quoting Hideki Yamane (2018-11-27 12:38:46) > Hi, > > Well, we use experimental as "shelter" during freeze, but it's not good > in my point of view. > > - During freeze, it is just ignored by most of the users since they >wouldn't know there's a newer package in there (and they also afraid >because it's in "experimental" ;). It means "not tested" if they were >in Debian repository for a long time period > - Re-uploading to unstable is just boring, and no values are added by it > - unstable users wants new valued packages constantly. After release, >"package flood" to unstable is not good. > > So, I guess putting fixed packages into "testing-proposed-updates" and > to continue to upload packages to unstable during freeze period is better. > > Pros) > - unstable distribution stays newest > - No "unintended" changes will be introduced into testing during freeze > > Cons) > - Maybe you should do cherry-picking changes from unstable to >testing-proposed-updates, not just ask "unblock" to Release Managers. > - Harder to get users for test with testing-proposed-updates repository > > Your thoughts? Let's not make freeze more comfortable. Let's make freeze more efficient - and uncomfortable to ignore. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#912465: RM: mozvoikko/2.2-0.1
Quoting Moritz Mühlenhoff (2018-11-01 22:33:10) > Adding the maintainer to CC. Jonas, are you still maintaining > debian-parl or shall I file removal bugs? Yes, I am still maintaining debian-parl. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#901431: RM: ruby-compass/1.0.3~dfsg-5
Quoting Emilio Pozuelo Monfort (2018-07-15 12:13:34) > On 13/06/18 09:55, Jonas Smedegaard wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: rm > > > > ruby-compass is dead upstream, and does not work with recent ruby-sass. > > This is tracked in bug#876608 of severity serious. > > > > For some reason, instead of bug#876608 kicking out (and keeping out) > > ruby-compass from testing, apparently instead it has caused recent > > ruby-sass to be kept out of testing instead. > > > > Please remove ruby-compass from testing, since it has no future. > > Hinted for removal, though if it's got no future and no rdeps, you may want to > get it removed from unstable with an ftp.debian.org RM bug. Thanks. There is no future in sight for Compass, but rdeps exist in unstable. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#901431: RM: ruby-compass/1.0.3~dfsg-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 ruby-compass is dead upstream, and does not work with recent ruby-sass. This is tracked in bug#876608 of severity serious. For some reason, instead of bug#876608 kicking out (and keeping out) ruby-compass from testing, apparently instead it has caused recent ruby-sass to be kept out of testing instead. Please remove ruby-compass from testing, since it has no future. - Jonas - -- System Information: Debian Release: buster/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-rc3-amd64 (SMP w/4 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8), LANGUAGE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlsgzekACgkQLHwxRsGg ASFr1g/+KMLm7uPgDTzNmau0M0N9ObKluw3rPxlpltlFFGrlmj0GaMJKETFrvo0A HbrV2p+SAreD3nRMvL/zJCJfwnnaab8VEB9VwyccJjl86c5cl+sdGTnXjZ2m1FSL iudR9cFc57npEZnPA/S4JflEQArf7Jb8roBH+P15BjIEDSkpEcn8dkfMpSX8QXkY bd9QRz6TO5tT2ifXgJI7QwW26XT6TQQNVJoxXCRClg2SDlqDOwkE48K68Njq6oxa sjdUDNXT/KqY3yiNtmZa9Jjtr4oUy/SgardNtFM2/8jFtEWKeGDr4Mh4SQBURrmT zsU/ic88NW6RXwszRDHKv61io/+qeAtU/p4PIigklg8TPgsy/nCJcLNbvYzNDaUB 9WovAd4axhPxAtMkxvVAdEzEZZTKODF/J9hdo848FmLEWjLmk9GDUFjlzFSV5xrN /EDGWNV0qRYECLbkDJj+3FJZWT49p00dd4XG7pRVwigaJZcsKPjXyn7esrI0i6/L 0h8eBYF46bLGmIJtwEcK2S5+yG6Ha2ACf96kjtKyi6YD/urZ4EkchDZDl5Dghfnb RBbdSDlkmTSOFRgbxMMZOY1xf2uc8t2BakKXSt1GfEbjlktv5pF/c4UjsqRTon6K KX77WDd3TaGul216IfiOMcC2PhiCy+KpqKt88ZqdEMeI0c94I5E= =2ZtP -END PGP SIGNATURE-
Re: Bug#857986: [Pkg-javascript-devel] Bug#857986: npm: This pakcage is 3 years old? (consider removal)
Quoting Pirate Praveen (2017-05-22 16:10:32) > On തിങ്കള് 22 മെയ് 2017 06:41 വൈകു, Jonas Smedegaard wrote: >> ...for the _initial_ packaging work. >> >> We are package *maintainers*. > > If you have not realized, we are discussing about maintaining an > existing package. I think you have also not realized the meaning of > team maintained packages. The person who did the initial package need > not be the maintainer of the packager for ever. When there is enough > interest in the package, it will remain maintained else it gets > removed. Exactly: Packages poorly _maintained_ should be removed. E.g. npm! My point in previous post was that focusing only on the workload for _initial_ packaging masks the actual real workload, which is being discussed here! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Bug#857986: [Pkg-javascript-devel] Bug#857986: npm: This pakcage is 3 years old? (consider removal)
Quoting Pirate Praveen (2017-05-22 13:27:35) > On വെള്ളി 19 മെയ് 2017 03:45 വൈകു, Jérémy Lal wrote: >> There are complications to distributing npm: it depends on a LOT of >> modules, which means it requires a lot of debian-maintainer time to >> package, and update. > > https://wiki.debian.org/Javascript/Nodejs/Tasks/npm ie, roughly about > 78 new modules to package. If one person were to work full time, I > think about 10-15 days time. ...for the _initial_ packaging work. We are package *maintainers*. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#854621: jessie-pu: package uwsgi/2.0.7-1
Quoting Adam D. Barratt (2017-02-19 21:43:08) > On Wed, 2017-02-08 at 20:10 +0100, Jonas Smedegaard wrote: >> a FTBFS was discovered which affects uwsgi in stable (and only that): >> Bug#854535 > > + * Add patch cherry-picked upstream to fix compilation with recent GCC. > > My understanding was that the change was in glibc, not gcc; is that > incorrect? Indeed it was glibc, not gcc. Thanks for catching my mistake! > Please go ahead. Thanks. I will now upload with changelog entry adjusted, targeted "jessie", and closing bug#854535 - but not mention nor close this bug#854621. Hope that is correct procedure - if not please do correct me. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#854621: jessie-pu: package uwsgi/2.0.7-1
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
a FTBFS was discovered which affects uwsgi in stable (and only that): Bug#854535
Attached is a debdiff of a prepared package update.
- Jonas
diff -Nru uwsgi-2.0.7/debian/changelog uwsgi-2.0.7/debian/changelog
--- uwsgi-2.0.7/debian/changelog2014-10-25 21:07:28.0 +0200
+++ uwsgi-2.0.7/debian/changelog2017-02-08 16:19:43.0 +0100
@@ -1,3 +1,10 @@
+uwsgi (2.0.7-1+deb8u1) jessie; urgency=medium
+
+ * Add patch cherry-picked upstream to fix compilation with recent GCC.
+Closes: Bug#854535. Thanks to Masahiro Yamada.
+
+ -- Jonas Smedegaard <d...@jones.dk> Wed, 08 Feb 2017 16:19:43 +0100
+
uwsgi (2.0.7-1) unstable; urgency=medium
[ upstream ]
diff -Nru uwsgi-2.0.7/debian/patches/020150415~f6e5db9.patch
uwsgi-2.0.7/debian/patches/020150415~f6e5db9.patch
--- uwsgi-2.0.7/debian/patches/020150415~f6e5db9.patch 1970-01-01
01:00:00.0 +0100
+++ uwsgi-2.0.7/debian/patches/020150415~f6e5db9.patch 2017-02-08
10:40:53.0 +0100
@@ -0,0 +1,21 @@
+Description: Fix compilation with recent GCC
+Origin: upstream, https://github.com/unbit/uwsgi/commit/f6e5db9
+Author: Unbit <i...@unbit.it>
+Forwarded: yes
+Bug: https://github.com/unbit/uwsgi/issues/883
+Bug-Debian: https://bugs.debian.org/854535
+Last-Update: 2017-02-08
+
+diff --git a/core/utils.c b/core/utils.c
+index 0715b5b3..d900caaa 100755
+--- a/core/utils.c
b/core/utils.c
+@@ -3515,7 +3515,7 @@ int uwsgi_tmpfd() {
+ tmpdir = "/tmp";
+ }
+ #ifdef O_TMPFILE
+- fd = open(tmpdir, O_TMPFILE | O_RDWR);
++ fd = open(tmpdir, O_TMPFILE | O_RDWR, S_IRUSR | S_IWUSR);
+ if (fd >= 0) {
+ return fd;
+ }
diff -Nru uwsgi-2.0.7/debian/patches/series uwsgi-2.0.7/debian/patches/series
--- uwsgi-2.0.7/debian/patches/series 2014-10-25 21:06:53.0 +0200
+++ uwsgi-2.0.7/debian/patches/series 2017-02-08 10:43:09.0 +0100
@@ -1,3 +1,4 @@
+020150415~f6e5db9.patch
1001_avoid_setting_RPATH.patch
1002_fix-reload-process-name.patch
1003_remove-php-libs.patch
Re: fact++ is marked for autoremoval from testing
Quoting James Cowgill (2016-08-29 10:55:30) > On 29/08/16 09:43, Jonas Smedegaard wrote: >> [please cc me on replies: I am not subscribed] >> >> I am puzzled about this one: >> >> Quoting Debian testing autoremoval watch (2016-08-29 06:39:03) >>> fact++ 1.6.4~dfsg-1 is marked for autoremoval from testing on >>> 2016-08-31 >>> >>> It (build-)depends on packages with these RC bugs: >>> 806865: ppl: FTBFS when built with dpkg-buildpackage -A (No rule to make >>> ppl_c.h) >>> 811825: ppl: FTBFS with GCC 6: no match for >> >> As I understand it, packages ppl (mentioned above) and cloog-ppl >> (build-dependency of fact++) are independent projects. >> >> Could this be a flaw somewhere in the autoremoval scripts? > > cloog-ppl depends on libppl-c4 and libppl13v5 from the ppl source > package, so fact++ is being autoremoved due to transitive > dependencies. Ahh. Thanks for opening my eyes :-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: fact++ is marked for autoremoval from testing
Hi, [please cc me on replies: I am not subscribed] I am puzzled about this one: Quoting Debian testing autoremoval watch (2016-08-29 06:39:03) > fact++ 1.6.4~dfsg-1 is marked for autoremoval from testing on 2016-08-31 > > It (build-)depends on packages with these RC bugs: > 806865: ppl: FTBFS when built with dpkg-buildpackage -A (No rule to make > ppl_c.h) > 811825: ppl: FTBFS with GCC 6: no match for As I understand it, packages ppl (mentioned above) and cloog-ppl (build-dependency of fact++) are independent projects. Could this be a flaw somewhere in the autoremoval scripts? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#791305: transition: ucommon (libucommon7v5)
Quoting Simon McVittie (2015-08-17 10:44:47) reopen 791305 retitle 791305 transition: ucommon (libucommon7v5) reassign 791305 release.debian.org severity 791305 normal user release.debian@packages.debian.org usertags 791305 + transition forwarded 791305 https://release.debian.org/transitions/html/auto-ucommon.html thanks On Fri, 03 Jul 2015 at 13:14:43 +, Matthias Klose wrote: Then reassign the issue to release.debian.org and properly tag it as a transition issue, by sending an email to cont...@bugs.debian.org Reopening to do this. This issue is not fully resolved until libucommon7v5 has reached testing. Jonas, I believe the current RT policy is that transitioning packages can be uploaded to unstable as soon as their build-dependencies have transitioned. In the case of ucommon, I think that means you can upload to unstable now. Thanks for enlightening me. Preparing a build for unstable now... - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Bug#782572: RM: sugar-presence-srvice-0.84/0.84.3-1.1, sugar-presence-service-0.88/0.88.0-3.1, sugar-presence-service-0.90/0.90.2-1, src:sugar-toolkit-0.96/0.96.3-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sugar is severely broken (see bug#782414) and not suitable for Jessie. Please drop *all* sugar packages for Jessie. In addition to the directly affected packages listed in subject, please also drop all of its reverse (build-)dependencies, and libraries with no reverse dependencies besides those of dropped packages. Here is a complete list of packages to drop: src:python-aiml/0.8.6-2 src:python-elements/0.13+svn20090823.230+dfsg-2 src:python-xklavier/0.4-4 src:sugar-0.96/0.96.1-2.1 src:sugar-0.98/0.98.8-1 src:sugar-artwork-0.84/0.84.4-3 src:sugar-artwork-0.88/0.88.1-4 src:sugar-artwork-0.96/0.96.2-2 src:sugar-artwork-0.98/0.98.4-1 src:sugar-base-0.84/0.84.2-4 src:sugar-base-0.88/0.88.0-4 src:sugar-base-0.96/0.96.0-1 src:sugar-base-0.98/0.98.0-1 src:sugar-datastore-0.84/0.84.1-3.1 src:sugar-datastore-0.88/0.88.0-4 src:sugar-datastore-0.96/0.96.0-1 src:sugar-datastore-0.98/0.98.1-1 src:sugar-presence-srvice-0.84/0.84.3-1.1 src:sugar-presence-service-0.88/0.88.0-3.1 src:sugar-presence-service-0.90/0.90.2-1 src:sugar-toolkit-0.96/0.96.3-1 src:sugar-toolkit-gtk3/0.98.7-1 src:sugar-toolkit-0.88/0.88.1-4 src:sugar-toolkit-0.84/0.84.17-1 src:sugar-toolkit-0.98/0.98.1-1 sugar-terminal-activity/28-1.2 sugar-record-activity/82-1.2 sugar-pippy-activity/46~dfsg-2 sugar-physics-activity/7+dfsg-1.2 sugar-moon-activity/11-1.1 sugar-memorize-activity/35-1.1 sugar-log-activity/24-1.1 sugar-irc-activity/8-1.2 sugar-connect-activity/22-1.2 sugar-chat-activity-0.84/65-5.1 sugar-calculate-activity/40-2 sugar-browse-activity/137-1 sugar-etoys-activity/116-3 One additional reverse dependency - education-desktop-sugar - is part of a larger set of binary packages and thus need special care (see bug#782504): This should be solved by an upload tonight. One other package - sugar-turtleart-activity - arguably should be dropped as well, but it is maintained outside of the Sugar/OLPC team and do not declare any tight relationships with infrastructural Sugar packages so a) do not technically affect dropping Sugar, and b) possibly is indeed usable on its own - i.e. if not then that's an independent bug. Regards, - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVLPMAAAoJECx8MUbBoAEhNOoP/iuzVzb7xufvMIlqkRSlE6qO 4D8z4lF4oDfYyaqbOrerhYQEWmptbPek3WVz/wcdE/Zw3Y9eMfVakgdWRDFL33Eb IGShoz9fN3jNI4YR44HyPOH4LMeekku7rTWa7GxZ7EKwUp8a1hp8KkrdtYUIKMfe G1xW5K0TH3SBw+o8OIluSZ+JsLVZrOjP7gx8M+uixiB3dQ0XkqhT9yMJcW51VnoZ fqqjvc8dU3NMZhsqMjapwtQL/PE61zkRsDt7mtJ9PkKa58Xw2NiCglbb7gusSKF3 aOM2fXs5ohUD+rNCNEpeE6ZYPuBuKH9K7BzAhBFc5duvjGHUpSNp85ATWG9l2G51 ptbK8DvHrb7EanO9d8UkpgJr7rymRIkoSoY1QtTlZe3cMwHLgXeP/KPYMaN+BvNs LDRmmRlbEGVOEpt38/foQAZgyrt1PNKQ+lPaLDDgDDVSpIWRDxu5Ej2vrCfGmZL7 CsHTcCA/vo+hGPUP49BMWZyS2575x5YTUP/4TtuGCSACUmsg88POaNPx4lCzaN0G hQjQmXqkSKQ0WH3kFTHswcgvXk5jqbwFqXmoIniaYHRa09tfEZ4Vt6r5rWc36zz6 W43xgKycapLKxVjyYl+znkReVDUu2Xn6CYApR7s57ijezH4FsM3aU3ALP8MSajlN I763HOv+CZAzpEYafbkq =6p3C -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150414105915.20707.40886.report...@bastian.jones.dk
Bug#781413: unblock: cdbs/0.4.130
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please unblock package cdbs Fixes quoting of compiler flags in perlmodule-vars.mk, causing FTBFS of at least 20 perl libraries. debdiff attached. unblock cdbs/0.4.130 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVFxXrAAoJECx8MUbBoAEhH0MQAIM8z6plqvFXHMSsw49bmWW5 ICHmsxBRZvtB1PJndDaB2gc44qCiHI4ul9Qr6MYXqBEEdcUD4kwazPJXxiQ9j2DW x4Ncj7fE1uRkvNUA8hVWN1uETVUnij54cULqL1MAs0fq0zQvDmaF0w29aaVhALKe gZ7Vfarb+6cgu2QnNdxsOEtReInEQbwG9W05RoYCupfa4IZFtwiLUTF6MRxbgKhy dpqjDwY6w9Ak72xfaq7GdmCrV3PGptR1dWfxpvOEePsZmrwr6DqHO7FJy2vb9vwf EaZra9k5BJqR1rT8In8t+rxfT4OJqYnZ8BYlt8FRxiru1xmMQXBrV9ALk2qBQz8p 9aVLcUW8NLqfhjCodWZTQxpDilylcPn+MOJ2kngL9eSgTJq1MIOq1L4ep7Bornxx yhO3MkN/u5O15uuJTVriWizbm8E1ezqA7BP/+gEucfN5hElyydyfZqF7XWvpAMi/ cutrNzApbxhOaqpZk3Zs1bevgj44cn8k0h0VkVESII/H0KMapPi2XADI0Ma24Dxn fI+IAMOMDTKk84VHefI7QlPiVvGfncfFLT171+BA65E0uAZRBvf20TvtsEV2srp3 d3gYAh6uXdp8X5GMFpGOba2z+eNMQER5h9kO+1nMh+dVePyJfs7FNfag5+uKwFbq Ph7J0aANd1ggPRBmKVr+ =wJ6j -END PGP SIGNATURE- diff -Nru cdbs-0.4.129/1/class/perlmodule-vars.mk.in cdbs-0.4.130/1/class/perlmodule-vars.mk.in --- cdbs-0.4.129/1/class/perlmodule-vars.mk.in 2015-03-06 03:52:06.0 +0100 +++ cdbs-0.4.130/1/class/perlmodule-vars.mk.in 2015-03-28 13:24:41.0 +0100 @@ -41,8 +41,8 @@ $(or $(CPPFLAGS_$(cdbs_curpkg)),$(CPPFLAGS)) \ $(cdbs_perl_cppflags)) \ LDDLFLAGS=$(strip \ - $(or $(LDFLAGS_$(cdbs_curpkg)),$(LDFLAGS))) \ - $(cdbs_perl_lddlflags) \ + $(or $(LDFLAGS_$(cdbs_curpkg)),$(LDFLAGS)) \ + $(cdbs_perl_lddlflags)) \ $(DEB_MAKE_PARALLEL) # Install into first listed package by default. diff -Nru cdbs-0.4.129/debian/changelog cdbs-0.4.130/debian/changelog --- cdbs-0.4.129/debian/changelog 2015-03-16 14:15:07.0 +0100 +++ cdbs-0.4.130/debian/changelog 2015-03-28 15:21:30.0 +0100 @@ -1,3 +1,10 @@ +cdbs (0.4.130) unstable; urgency=medium + + * Fix quoting of compiler flags in perlmodule-vars.mk. +Closes: bug#781076. Thanks to Niko Tyni. + + -- Jonas Smedegaard d...@jones.dk Sat, 28 Mar 2015 15:20:37 +0100 + cdbs (0.4.129) unstable; urgency=medium * Fix quoting of compiler flags in perl-makemaker-vars.mk.
Bug#780594: unblock: cdbs/0.4.129
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please unblock package cdbs Recent fix for bug#770767 contained a typo: Ending quote was applied too early in perl-makemaker-vars.mk, leading to broken compiler flags. This affects _all_ packages using perl-makemaker.mk snippet, as the compiler flags are passed always (not only to arch-dependent packages). Debdiff against the package in testing is attached. unblock cdbs/0.4.129 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVBt4BAAoJECx8MUbBoAEhYQUP/3i+FpFs5esbCIX+7K+pkIdE kfgjrDQliLipQlZJeyK8DcN2uEIVDU/MOUOVUNiBNzHgHAvBbKrscCAsZM0ckxmU Gin8/9sca5z/NpnuiEiZOngoLWnHb2RlMSBWr5VXw+z5MINtO2hIEx39gQU9DzmZ TcgBEchqZW13jFzzIJ+WeDdqA6aT9QmADQAqgCZgyt5pogIK5QilgD7719PhLjY0 YlKwazUfB9Dn+/rLT9/kq52GqGy8Tz5V+IgNQuYkMghUFJhnhDaigQ9OgrJhV3ul LuwE9I6MlT+MKQuD2uyIloMVVMihrDPdTWo/npaPf3VwO2FoZ55+vBitqlKA1lyt VWrnxVVP6Ugo38DEOO+7pIlT8B6COudZqY6u9DFEBIfyiC0jAUmbegqKbbbw8C/r QlRHJVul1s2GqWNtzPYviOBkMS57PPvIhXTAXdSrCNpiXg1sgBXDuSOmh2H8lQq7 /HV1F39Adcd/BBnDjBMnIYhyjxIWVuzIJYbNRU12ke2+UbSsbkRgqIBJi/63BnV7 EOTYbZlwGuz5gYTKNrtXn52srO1+dmHFnrPkU4yKQ0KPpZcYWbceAkgGwx5nAAMy u7TN06R/w19RcVNcnsPi3oKg+EO1pzNy8AHLuQseHQHaMACfqFN6Rh5TxbqbAMbP G1Gf0sdCg+tFZKvb3voM =Y9gz -END PGP SIGNATURE- diff -Nru cdbs-0.4.128/1/class/perl-makemaker-vars.mk.in cdbs-0.4.129/1/class/perl-makemaker-vars.mk.in --- cdbs-0.4.128/1/class/perl-makemaker-vars.mk.in 2015-03-06 03:52:06.0 +0100 +++ cdbs-0.4.129/1/class/perl-makemaker-vars.mk.in 2015-03-16 14:03:37.0 +0100 @@ -40,8 +40,8 @@ $(or $(CPPFLAGS_$(cdbs_curpkg)),$(CPPFLAGS)) \ $(cdbs_perl_cppflags)) \ LDDLFLAGS=$(strip \ - $(or $(LDFLAGS_$(cdbs_curpkg)),$(LDFLAGS))) \ - $(cdbs_perl_lddlflags) \ + $(or $(LDFLAGS_$(cdbs_curpkg)),$(LDFLAGS)) \ + $(cdbs_perl_lddlflags)) \ $(DEB_MAKE_PARALLEL) DEB_MAKEMAKER_INVOKE ?= /usr/bin/perl Makefile.PL \ diff -Nru cdbs-0.4.128/debian/changelog cdbs-0.4.129/debian/changelog --- cdbs-0.4.128/debian/changelog 2015-03-06 03:53:48.0 +0100 +++ cdbs-0.4.129/debian/changelog 2015-03-16 14:15:07.0 +0100 @@ -1,3 +1,10 @@ +cdbs (0.4.129) unstable; urgency=medium + + * Fix quoting of compiler flags in perl-makemaker-vars.mk. +Closes: bug#780592. + + -- Jonas Smedegaard d...@jones.dk Mon, 16 Mar 2015 14:14:37 +0100 + cdbs (0.4.128) unstable; urgency=medium * Fix resolve compiler flags in perl snippets:
Bug#779912: unblock: cdbs/0.4.128
#770767. Thanks to Niko Tyni.
+ * Fix support control fields case-insensitively.
+Closes: bug#772429. Thanks to Guillem Jover.
+
+ -- Jonas Smedegaard d...@jones.dk Fri, 06 Mar 2015 03:53:47 +0100
+
cdbs (0.4.127) unstable; urgency=medium
* Fix use unversioned Python runtime for default flavor in
diff -Nru cdbs-0.4.127/scripts/list-packages cdbs-0.4.128/scripts/list-packages
--- cdbs-0.4.127/scripts/list-packages 2013-12-28 02:55:55.0 +0100
+++ cdbs-0.4.128/scripts/list-packages 2015-03-06 03:53:30.0 +0100
@@ -54,7 +54,7 @@
while (CONTROL) {
chomp;
s/\s+$//;
- if (/^Package:\s*(.*)/) {
+ if (/^Package:\s*(.*)/i) {
$package=$1;
# Detect duplicate package names in the same control file.
if (! $seen{$package}) {
@@ -64,7 +64,7 @@
error(debian/control has a duplicate entry for $package);
}
}
- if (/^Architecture:\s*(.*)/) {
+ if (/^Architecture:\s*(.*)/i) {
$arch=$1;
}
Bug#779912: unblock: cdbs/0.4.128
Quoting Niels Thykier (2015-03-06 12:10:47) On 2015-03-06 11:58, Jonas Smedegaard wrote: Additionally, the fix for #770767 is believed to also fix applying all default security-strengthening compiler flags for arch-any packages that uses a CDBS perl snippet. Since that is a release goal, and since missing default flags may also lead to other breakage on i386 due to how that platform links perl code (see bug#770767), unblocking of cdbs should probably be followed by BinNMUs + unblock of e.g. all arch-any packages matching regext '^include\s+.*perl.*\.mk' for its rules file. We might not want that actually. Why? Please note that your search below include far too many packages: most perl libraries are arch-all which need not - and cannot - be BinNMUed. I don't know (and am not skilled so now is probably the wrong time to start if others can help) how to reliably locate such package list, but can do it among the packages I maintain myself which might be adequate (I am not alone in using CDBS but might be for perl libs specifically). Probably http://codesearch.debian.net/results/include%5Cs+.*perl.*%5C.mk%20path:debian/rules/page_0 I knew of that search, but it locates _all_ packages using perl snippet - not only arch-any packages. I can only think of needing to both grep rules file for snippet inclusion and control file to exclude arch-all - but I don't think such cross-file combo is possible with codesearch.d.n. And then the To see all packages which contain results: cmd. Where is that command? - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#774759: [pre-approval] unblock: ghostscript/9.06~dfsg-2
Quoting Didier 'OdyX' Raboud (2015-01-07 09:20:05) I'd like to get the patch for #732440 included in Jessie. The bug was reported three independent times and is a premature abort in Ghostscript processing. The patch that fixes that bug was included in upstream's 9.14 version and can be directly cherry-picked on top of 9.06~dfsg-1 as currently in jessie. Here goes the proposed changelog: ghostscript (9.06~dfsg-2) unstable; urgency=medium * Add patch cherry-picked upstream to fix /typecheck error in /findfont (Closes: #732440) The cherry-picked patch as well as the full debdiff are attached. Newer Ghostscript is licensed AGPL. Is that patch compatible with the more relaxed licensing of older Ghostscript? - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#773239: Did unblock of libcatalyst-authentication-credential-http-perl perhaps fail somehow?
Hi, Web page https://packages.qa.debian.org/libc/libcatalyst-authentication-credential-http-perl.html indicates no freeze exception as this bugreport states has been applied. Sorry if I am simply too impatient... - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#773214: unblock: ciderwebmail/1.05-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please unblock package ciderwebmail Ciderwebmail in testing is arguably unusable: You can read mails and reorganize IMAP mail folders, but cannot send mails. Change consists of a one-line patch, verified to fix the bug. debdiff attached. unblock ciderwebmail/1.05-3 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUjxGOXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWcvkIAIqA3SPFHcMRPebQFRLl1bcv Cl8AugFLo3ox5+D/c4rcWPAzsv4CrwmqAZN0RWdEV3t5W2pDiqHB0D/+vk9lmIQi 3XgqbpVam43RnLNU9+bebuA2NmwbCWBlX9eWoLdEIRZf1ZapOlfRSG+AIjSt5jxA eWKGjypPcppfduS9TbCMXpbjfETwSJCRIYYwExRY8eNuXVw7QxOnU0SpibZTHfhN ANgZKDeJw/CSSUfy/+I2jBcuhBOjkx8LfonOL4K1yeVJi3MSvu01sy5Lo7fyEZWw bp4BT6F3Wj542Kpv2OHTlTo4ZiZD4fYjZGR5H63RLW7vy/NnMW3G5shcIp6rOFM= =nCl9 -END PGP SIGNATURE- diff -Nru ciderwebmail-1.05/debian/changelog ciderwebmail-1.05/debian/changelog --- ciderwebmail-1.05/debian/changelog 2014-10-25 18:49:46.0 +0200 +++ ciderwebmail-1.05/debian/changelog 2014-12-15 17:11:12.0 +0100 @@ -1,3 +1,10 @@ +ciderwebmail (1.05-3) unstable; urgency=medium + + * Add patch 1002 to fix submit button for sending mail. +Closes: bug#773207. + + -- Jonas Smedegaard d...@jones.dk Mon, 15 Dec 2014 17:10:44 +0100 + ciderwebmail (1.05-2) unstable; urgency=medium * Add patch 1001 to fix resolve supported languages. diff -Nru ciderwebmail-1.05/debian/patches/1002_fix_message_submit.patch ciderwebmail-1.05/debian/patches/1002_fix_message_submit.patch --- ciderwebmail-1.05/debian/patches/1002_fix_message_submit.patch 1970-01-01 01:00:00.0 +0100 +++ ciderwebmail-1.05/debian/patches/1002_fix_message_submit.patch 2014-12-15 17:08:09.0 +0100 @@ -0,0 +1,16 @@ +Description: Fix submit button for sending mail +Author: Jonas Smedegaard d...@jones.dk +Bug-Debian: https://bugs.debian.org/773207 +Last-Update: 2014-12-15 + +--- a/root/templates/base/compose.xml b/root/templates/base/compose.xml +@@ -71,7 +71,7 @@ + /fieldset + fieldset + legendSend/legend +-input type=button name=send onClick=return send_mail(this.form); return false; i18n:translate= value=Transmit message / ++input type=submit name=send onClick=return send_mail(this.form); return false; i18n:translate= value=Transmit message / + /fieldset + /form + /div diff -Nru ciderwebmail-1.05/debian/patches/series ciderwebmail-1.05/debian/patches/series --- ciderwebmail-1.05/debian/patches/series 2014-10-25 18:48:43.0 +0200 +++ ciderwebmail-1.05/debian/patches/series 2014-12-15 16:47:26.0 +0100 @@ -1,2 +1,3 @@ 1001_fix_resolve_langs.patch +1002_fix_message_submit.patch 2001_avoid_autoinstall.patch
Bug#773239: unblock: libcatalyst-authentication-credential-http-perl/1.016-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please unblock package libcatalyst-authentication-credential-http-perl Version in Jessie depends on libcatalyst-modules-perl, a deprecated bundle package pulling in 22 Catalyst plugins, two of them deprecated and discouraged code. This is the only package in Jessie depending on the deprecated bundle package (ciderwebmail depends on it too, but only as fallback for more specific Catalyst plugin packages). Debdiff is attached. A few cosmetic changes was applied too, but diff is still pretty small and none of it should pose any risk. unblock libcatalyst-authentication-credential-http-perl/1.016-2 Thanks for considering, - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUj1DJXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWWlsH/1cCALx+VaZ/6IefKQ4qYbuS OE3sb6rKYn7TEUFi8pAJZGlqhHDz0yEPJyOyo13kq6nieYt+hb9b0IibtKbKfxjN qWtmprP5QuXWKEN5HR06gH2cKB7Mh6Ri63WIRzRTAQj9FPro6GIjBAlo3xvrOS0f qOQqIKbggyLwRRVufBP4YzPYCaDf8CpsV1tvI0G5GzJubkokY7d9shQ7AGYeEdY7 hr3rsFSlvJB89luwMP3MK/4FO0gW2AiV338mk3LAbVXBetLl7xYxPaV2s2i4k6SK YzPIchaX1cKN3AyjXfgHDwcfzV2w67vSjb6K3q6TCkgSVpsuWlXwKdjqfQ/hYtI= =P+Tx -END PGP SIGNATURE- diff -Nru libcatalyst-authentication-credential-http-perl-1.016/debian/changelog libcatalyst-authentication-credential-http-perl-1.016/debian/changelog --- libcatalyst-authentication-credential-http-perl-1.016/debian/changelog 2013-08-02 17:42:36.0 +0200 +++ libcatalyst-authentication-credential-http-perl-1.016/debian/changelog 2014-11-04 23:06:44.0 +0100 @@ -1,3 +1,17 @@ +libcatalyst-authentication-credential-http-perl (1.016-2) unstable; urgency=medium + + [ Salvatore Bonaccorso ] + * Update Vcs-Browser URL to use cgit web frontend. + + [ Jonas Smedegaard ] + * Fix use canonical URL in Vcs-Git. + * Fix (build-)depend on libcatalyst-plugin-authentication-perl, +favored over catalyst-modules. +Closes: Bug#768092. + * Declare compliance with Debian Policy 3.9.6. + + -- Jonas Smedegaard d...@jones.dk Tue, 04 Nov 2014 23:06:40 +0100 + libcatalyst-authentication-credential-http-perl (1.016-1) unstable; urgency=low [ upstream ] diff -Nru libcatalyst-authentication-credential-http-perl-1.016/debian/control libcatalyst-authentication-credential-http-perl-1.016/debian/control --- libcatalyst-authentication-credential-http-perl-1.016/debian/control 2013-08-02 17:43:10.0 +0200 +++ libcatalyst-authentication-credential-http-perl-1.016/debian/control 2014-11-04 23:05:35.0 +0100 @@ -6,19 +6,19 @@ perl, debhelper, dh-buildinfo, - libcatalyst-modules-perl, libcatalyst-perl, libclass-accessor-perl, libstring-escape-perl, liburi-perl, libossp-uuid-perl | libdata-uuid-perl, + libcatalyst-plugin-authentication-perl | catalyst-modules, libtest-exception-perl, libtest-mockobject-perl Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Uploaders: Jonas Smedegaard d...@jones.dk -Standards-Version: 3.9.4 -Vcs-Git: git://anonscm.debian.org/git/pkg-perl/packages/libcatalyst-authentication-credential-http-perl -Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libcatalyst-authentication-credential-http-perl.git +Standards-Version: 3.9.6 +Vcs-Git: git://anonscm.debian.org/pkg-perl/packages/libcatalyst-authentication-credential-http-perl +Vcs-Browser: https://anonscm.debian.org/cgit/pkg-perl/packages/libcatalyst-authentication-credential-http-perl.git Homepage: http://search.cpan.org/dist/Catalyst-Authentication-Credential-HTTP/ Package: libcatalyst-authentication-credential-http-perl diff -Nru libcatalyst-authentication-credential-http-perl-1.016/debian/control.in libcatalyst-authentication-credential-http-perl-1.016/debian/control.in --- libcatalyst-authentication-credential-http-perl-1.016/debian/control.in 2013-07-20 23:54:57.0 +0200 +++ libcatalyst-authentication-credential-http-perl-1.016/debian/control.in 2014-11-04 23:03:23.0 +0100 @@ -4,9 +4,9 @@ Build-Depends: @cdbs@ Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Uploaders: Jonas Smedegaard d...@jones.dk -Standards-Version: 3.9.4 -Vcs-Git: git://anonscm.debian.org/git/pkg-perl/packages/libcatalyst-authentication-credential-http-perl -Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-perl/packages/libcatalyst-authentication-credential-http-perl.git +Standards-Version: 3.9.6 +Vcs-Git: git://anonscm.debian.org/pkg-perl/packages/libcatalyst-authentication-credential-http-perl +Vcs-Browser: https://anonscm.debian.org/cgit/pkg-perl/packages/libcatalyst-authentication-credential-http-perl.git Homepage: http://search.cpan.org/dist/Catalyst-Authentication-Credential-HTTP/ Package: libcatalyst-authentication-credential-http-perl diff
Re: Bug#771126: Bug#771191: Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
Quoting Fabian Greffrath (2014-12-03 08:56:41) Am Dienstag, den 02.12.2014, 23:29 +0100 schrieb Bastien ROUCARIES: And offencive (sexist) for 50% of the population the women... Now it's getting really ridiculous. Gosh, it's a picture of a woman! I disagree with you. Honestly, when you mentioned you'd replaced with a photo of your own, I got very curious and checked if you'd made a self-portrait posing similarly - looking over your shoulder and into the camera with an invitation in the eyes. You chose food. Had you done that (in an honest attempt, inspired by but without making fun on the original), your comment now would have more meaning to me. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Bug#771126: Bug#771191: Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
Quoting Jonas Smedegaard (2014-12-03 11:33:17) Quoting Fabian Greffrath (2014-12-03 08:56:41) Am Dienstag, den 02.12.2014, 23:29 +0100 schrieb Bastien ROUCARIES: And offencive (sexist) for 50% of the population the women... Now it's getting really ridiculous. Gosh, it's a picture of a woman! I disagree with you. Honestly, when you mentioned you'd replaced with a photo of your own, I got very curious and checked if you'd made a self-portrait posing similarly - looking over your shoulder and into the camera with an invitation in the eyes. You chose food. Had you done that (in an honest attempt, inspired by but without making fun on the original), your comment now would have more meaning to me. Whoops - sorry: I mixed up you and Reinhard. :-( - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
Quoting Reinhard Tartler (2014-12-02 14:11:19) On 2014-11-27 23:23, Jonas Smedegaard wrote: In prior similar bugreport https://bugs.debian.org/760171#10 - referenced from https://bugs.debian.org/771191#10 - distribution is documented as permitted only for research and education which I interpret as unacceptable for Debian. FTR, this whole business feel incredibly silly. Welcome to the Real World: Some stuff is incredibly stupid, yet Real. lena.pnm has become the *de-facto* standard image for every CS student to do his graphics courses homework on, Proprietary operating systems, word processors and spreadsheet editors have become the *de-facto* standard e.g. for most public servants in the World. Incredibly silly as free (and technically superior) alternatives exist. But this bugreport is about DFSG... The copyright holder is going to have a very hard time enforcing his right if he wanted to prevent distribution of the image, DFSG is is about Debian respecting copyright and licensing (no matter if difficult for copyright holders to defend or enforce their rights). (perhaps you confuse copyright and licensing with trademarks or patents, in some cases considered irrelevant for Debian to care about) Jonas, would you mind taking over from here and upload https://libav.org/releases/libav-11.1.tar.xz to unstable? I don't mind doing the technical work of packaging, but prefer if someone else takes to dialogue with release team about freeze exception, as I don't have the stomach for that (no blame on the release team for that!). I also don't mind doing the additional technical work of cherry-picking only the fix for this bug and apply to 6:11-2 currently targeted Jessie. Which of those to do would probably need input from the person willing to do the negotiation with release team, however. So I await someone volunteering for that (and while waiting will prepare that new upstream release, and if noone have appeared before done release it targeted experimental). - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#771396: unblock: librdf-trine-perl/1.011-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Please unblock package librdf-trine-perl
Fixes bug#767174 with a 3-line patch cherry-picked upstream.
The issue fixed is not security-related but a violation of the SPARQL1.1
specification, and since RDF::Trine is a reference implementation of the
standard it would be quite beneficial for this to be corrected.
unblock librdf-trine-perl/1.011-2
Regards,
- Jonas
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQF8BAEBCgBmBQJUeN38XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0
RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWVEwH+wdJjX9voL5Fq64YOeKUjurE
v590qoRHC8rwhVg6PC2riSZb2syrVOQ3ip33DJsO4cPUxwMOkNBshFV6mKjCMLts
ZPS9rSfRZ47AiJiihmW049ncJ3lwyyV0L21G9M+hAPtv3Y1Hkdor8zoaUve9Sb0+
dnNjSrziVzqRhJev7jkzv78BvalBFS1jM/qVE++FvEovrCuIhhAXVYF6ojrESNTB
dOhwf+GelfP2ANSANd5lsJ3zDuGAq/aFv5EhEoW6i+fHvSRtOBqFMwNE1SGWUfF4
8ke2Wqkt05c80uW5dEWID5ewNkNvUH5E9RUyjrorhJk27m+5ZEj5WI6Fg5W3uKs=
=MMr0
-END PGP SIGNATURE-
diff -Nru librdf-trine-perl-1.011/debian/changelog librdf-trine-perl-1.011/debian/changelog
--- librdf-trine-perl-1.011/debian/changelog 2014-10-25 01:11:13.0 +0200
+++ librdf-trine-perl-1.011/debian/changelog 2014-11-28 21:08:13.0 +0100
@@ -1,3 +1,11 @@
+librdf-trine-perl (1.011-2) unstable; urgency=medium
+
+ * Add patch cherry-picked upstream to fix SPARQL XML serialization of
+boolean results.
+Closes: bug#767174.
+
+ -- Jonas Smedegaard d...@jones.dk Fri, 28 Nov 2014 21:07:39 +0100
+
librdf-trine-perl (1.011-1) unstable; urgency=medium
[ upstream ]
diff -Nru librdf-trine-perl-1.011/debian/patches/020141028~825c37c.patch librdf-trine-perl-1.011/debian/patches/020141028~825c37c.patch
--- librdf-trine-perl-1.011/debian/patches/020141028~825c37c.patch 1970-01-01 01:00:00.0 +0100
+++ librdf-trine-perl-1.011/debian/patches/020141028~825c37c.patch 2014-11-28 21:00:21.0 +0100
@@ -0,0 +1,21 @@
+Description: Fix SPARQL XML serialization of boolean results.
+Origin: upstream, https://github.com/kasei/perlrdf/commit/825c37c
+Author: Gregory Todd Williams g...@evilfunhouse.com
+Last-Update: 2014-10-28
+Forwarded: Yes
+Bug-Debian: http://bugs.debian.org/767174
+
+--- a/lib/RDF/Trine/Iterator/Boolean.pm
b/lib/RDF/Trine/Iterator/Boolean.pm
+@@ -107,10 +107,8 @@
+ my $xml = END;
+ ?xml version=1.0 encoding=utf-8?
+ sparql xmlns=http://www.w3.org/2005/sparql-results#;
+-head/head
+-results
++ head/head
+ boolean${value}/boolean
+-/results
+ /sparql
+ END
+ return $xml;
diff -Nru librdf-trine-perl-1.011/debian/patches/series librdf-trine-perl-1.011/debian/patches/series
--- librdf-trine-perl-1.011/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ librdf-trine-perl-1.011/debian/patches/series 2014-11-28 21:00:08.0 +0100
@@ -0,0 +1 @@
+020141028~825c37c.patch
Re: Bug#771126: libav/tests/lena.pnm: also not mentioned in debian/copyright
Quoting Niels Thykier (2014-11-27 22:14:25) FTR, I believe Holger is referring to [1]. At first glance, it seems to mostly apply to this particular case. I say mostly because it is not immediately clear to me that we got an exact license (combined with ... and there is *no doubt about the license* of the files [...] from [1], emphasis mine). That said, provided that we *are permitted* to distributable, I see no issue with the -ignore tag for Wheezy. In prior similar bugreport https://bugs.debian.org/760171#10 - referenced from https://bugs.debian.org/771191#10 - distribution is documented as permitted only for research and education which I interpret as unacceptable for Debian. You might also want to read Holger's conclusion which contradicts the other stuff he extracted from the material I referenced. Sigh... - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#768777: unblock: node-jake/0.7.9-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please unblock package node-jake Severity of bug#761670 was set too high, lowered only after the freeze. No debdiff, as no changes was needed, only an adjustment of severity. unblock node-jake/0.7.9-1 Thanks for considering, - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUXyr9XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWh3UIALZ6/JiA8WM4CFV4Kq01vcHf qeAGu6MgvbeesZ2SHgvry7ea6199QyweMzoPcDI8dCA/dbicFfl1XekFgQ0TJjZT 9Z5zq65qpDUUGZt5SEY5lysfNsW9Vnm+s5JeHFYmIAw5/eGWcEvP7u64k7eItv2W WMgTNzhMy9/Is/v0xm7cMQxqaAgbjp8727i/aplQC87JM3VguNJrhAGVreHUPM2/ A+uKMjz6GC5DmGajS/r9YE5NzuHuOBGSXeXz32bqqLFIpt9DQrUT++OJj+sm8K/z Knv7xTG9JnNCFekxbShvWPeUIap5+FsUMblE2Qgt21ImOIP+hT1Z6VDTc7flwFE= =DMWB -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141109085112.27004.99540.report...@bastian.jones.dk
Bug#768779: unblock: libcatmandu-marc-perl/0.206-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Please unblock package libcatmandu-marc-perl A some build-dependencies, causing FTBFS in testsuite, was missing and has now been corrected. Debdiff attached. unblock libcatmandu-marc-perl/0.206-2 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUXzCdXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWXNoH/2TqwIuVrWp/9NhH6iAt+jQN MFHEMSGIXqHuwSg4eNFEP9q+bCvpcLA+Jf4QC9s1HHA2ibsKKyw3RUAi+sFOTPY9 Mjfviy0zZwnD7ygmi+mUxYjuvu6SqEXeAgxxMKwrp3+3xQEp0nPbbSVnGe8SruTh sOFuqiGpiCmWvnrPRrgmrBO/KOiMTUz8Cvoyy2rMxwtvQ7U1klSeGYxA8diJvfUG PlZJNwm/6vnr8yw7dHXyFU0jeL7ylmsn8aXi31yIZFEItd0pzXBtX62oIvm5qLiB u9AO/epdnFwMARv2GI+MUCD1051OtleXbCyFKM8JFCOHcEQRDdn2JAQIoY9JXvw= =wspa -END PGP SIGNATURE- diff -Nru libcatmandu-marc-perl-0.206/debian/changelog libcatmandu-marc-perl-0.206/debian/changelog --- libcatmandu-marc-perl-0.206/debian/changelog 2014-10-22 00:02:24.0 +0200 +++ libcatmandu-marc-perl-0.206/debian/changelog 2014-11-09 09:57:29.0 +0100 @@ -1,3 +1,9 @@ +libcatmandu-marc-perl (0.206-2) unstable; urgency=medium + + * Fix resolve build-dependencies. Closes: bug#768744. + + -- Jonas Smedegaard d...@jones.dk Sun, 09 Nov 2014 09:57:26 +0100 + libcatmandu-marc-perl (0.206-1) unstable; urgency=low * Initial Release. diff -Nru libcatmandu-marc-perl-0.206/debian/control libcatmandu-marc-perl-0.206/debian/control --- libcatmandu-marc-perl-0.206/debian/control 2014-10-22 00:01:44.0 +0200 +++ libcatmandu-marc-perl-0.206/debian/control 2014-11-09 09:56:56.0 +0100 @@ -7,6 +7,10 @@ libmodule-build-perl, debhelper, dh-buildinfo, + libcatmandu-perl, + libmarc-file-marcmaker-perl, + libmarc-file-mij-perl, + libmarc-parser-raw-perl, libjson-xs-perl (= 2.300), libmarc-xml-perl (= 0.93), libmarc-record-perl (= 2.0.6), diff -Nru libcatmandu-marc-perl-0.206/debian/rules libcatmandu-marc-perl-0.206/debian/rules --- libcatmandu-marc-perl-0.206/debian/rules 2014-10-21 17:13:13.0 +0200 +++ libcatmandu-marc-perl-0.206/debian/rules 2014-11-09 09:55:18.0 +0100 @@ -28,6 +28,7 @@ # Needed by upstream build and (always) at runtime perl-deps = catmandu marc-file-marcmaker marc-file-mij marc-parser-raw +deps = $(patsubst %,$(comma) lib%-perl, $(perl-deps)) deps +=, libjson-xs-perl (= 2.300) deps +=, libmarc-xml-perl (= 0.93) deps +=, libmarc-record-perl (= 2.0.6)
Re: Re-Proposal - preserve freedom of choice of init systems
Quoting Daniel Kahn Gillmor (2014-10-17 18:38:35) On 10/17/2014 12:06 PM, Ian Jackson wrote: And the GR text is quite careful: it doesn't say that failure to work with one init system is worse than any other bug. It is only _requiring a specific init system to be pid 1_ which is forbidden. If the requirement is testing a literal string match against /proc/1/cmdline or $(readlink -f /sbin/init) or whatever, then that's pretty silly, and surely that's *already* a bug that upstream would be grateful for a fix. in this case, we don't need a GR. But if the requirement is hey, i'm not going to work without something else on the system performing functionality X, and a given init system *doesn't provide* functionality X, then it sounds like either a bug in the lacking initsystem (should provide functionality X), or a straightforward case of an explicit dependency. It could also be resolved by making some part of the dependent package's functionality more limited in scope, and saying we can run but we can't to Y if we don't have access to system functionality X. These are all legitimate options for resolving the problem, and they're already available to folks who want to work on them today. It sounds like the gdm issue was actually resolved already through some combination of these approaches (thanks to Aigars for the recap upthread). Why do we need a GR that's unlikely to change this situation? We need the GR to ensure situation stays good. No big deal. I'm going to stop commenting on this thread now and try to fix some bugs that need fixing before the freeze. Me too :-) - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#760560: RM: ghostscript-cups/9.06~dfsg-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Seems from https://qa.debian.org/excuses.php?package=ghostscript and https://release.debian.org/migration/testing.pl?package=ghostscript that binary package ghostscript-cups needs to explicitly be removed from testing to allow new release (which has that package dropped) is allowed to migrate to testing. ...and reportbug tells me you are the ones to task to about that. - Jonas - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUCZXaXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWB4AIAI6xk3D6qHsFmNFH/Kosu6lE kpuuccpiDf/etE8ctjnbQPSLbQ7qmW1OlISNYouDQ2hNOWF4Q6eh9I0BW1jdlS9w 4yF3ebmD8Tij+hOo4b+NGezNYV1kEXduVk6MxzZnx/u+p7W7SKCP/OwvqOovjJZW dH9vp4ZqFoI3rKMbZn18L6GQk/1tHEssJKuK3faaQrgFzhqCi6FdT9ochQBakjMo xgnBUGhEJxYxL2GdTUpjlGztxYxXQ4OafImEPibYMXlo0SRCgIN7ccDdswELwNXs 9Y7NSY0eTeGRTil/GGEijHBmZqgBuqxtHHS6rixKI3ubo67x0JO8uPXzrUGHBdI= =UOB5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140905105213.839.27228.report...@bastian.jones.dk
Any plans getting fix for bug#747532 into next stable release?
Hi, Good that bug#747532 was fixed in icedove 30.0~b1-1. That is arguably of no use, however, if not then also fixed in stable. Any plans on doing that? - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Any plans getting fix for bug#747546 into next stable release?
Hi, Good that bug#747546 was fixed in icedove 30.0~b1-1. That is arguably of no use, however, if not then also fixed in stable. Any plans on doing that? (see also the related bug#747532 - sorry for not posting together) - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: Bug#747546: Any plans getting fix for bug#747546 into next stable release?
Hi Carsten, Quoting Carsten Schoenert (2014-06-12 15:14:40) Am 12.06.2014 14:58, schrieb Jonas Smedegaard: That is arguably of no use, however, if not then also fixed in stable. Any plans on doing that? yes of course. Great you see it that way - and sorry if my lack of faith was seen as rude. version 24.6.0 for the Thunderbird package was released an Tuesday this week, as far as I know Christoph will prepare the upload for stable-security this weekend. [1] http://anonscm.debian.org/gitweb/?p=pkg-mozilla/icedove.git;a=commit;h=ddd0d7e761e24b24873cf2ef6dda70692a5841d3 Great! - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#740683: provide web service client package via stable-updates
Quoting Hideki Yamane (2014-03-04 03:26:19) Some web service client software package need to be updated timely manner to deal with its API changes (e.g. twitter, see [*1]). If not, it'd be *completely* useless and make users confuse. If I understand the issue correctly, I believe the solution is web server specific, and I therefore suggest to split and reassign against the various web servers in Debian - or at least the default one, Apache2. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#714639: pu: package ghostscript/9.05~dfsg-6.3
Quoting Paul Wise (2013-07-01 16:17:28) On Mon, 2013-07-01 at 15:09 +0100, Adam D. Barratt wrote: ghostscript currently has the same version in wheezy, jessie and sid; is there a plan for getting sid fixed? I expect the maintainers intend to upload the new upstream 9.07 soon, it contains the patch. CCing the maintainers to find out their plans. The 9.07~dfsg-1 release is blocked by bug#701993. I will now prepare a 9.05~dfsg-8 release for Sid with this bugfix applied. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#714639: pu: package ghostscript/9.05~dfsg-6.3
Quoting Jonas Smedegaard (2013-07-04 13:51:52) Quoting Paul Wise (2013-07-01 16:17:28) On Mon, 2013-07-01 at 15:09 +0100, Adam D. Barratt wrote: ghostscript currently has the same version in wheezy, jessie and sid; is there a plan for getting sid fixed? I expect the maintainers intend to upload the new upstream 9.07 soon, it contains the patch. CCing the maintainers to find out their plans. The 9.07~dfsg-1 release is blocked by bug#701993. ...and for Sid/Jessy also blocked by bug#659226. I will now prepare a 9.05~dfsg-8 release for Sid with this bugfix applied. Compiling now. Please consider adopting for the backport this other patch for a similar endless loop, included with the 9.05~dfsg-8 release: http://bugs.ghostscript.com/show_bug.cgi?id=694353 - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#689103: nmu: asterisk-flite_2.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu asterisk-flite_2.1-1 . ALL . -m Re-link against newer asterisk (that has broken shlibs file). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120929075524.28271.67239.report...@auryn.jones.dk
Bug#689104: nmu: asterisk-espeak_2.1-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu asterisk-espeak_2.1-1 . ALL . -m Re-link against newer asterisk (that has broken shlibs file). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120929075812.28482.10351.report...@auryn.jones.dk
Bug#689103: nmu: asterisk-flite_2.1-1
On 12-09-29 at 04:27pm, Adam D. Barratt wrote: On Sat, 2012-09-29 at 09:55 +0200, Jonas Smedegaard wrote: nmu asterisk-flite_2.1-1 . ALL . -m Re-link against newer asterisk (that has broken shlibs file). I assume the point is actually that the new asterisk has a /fixed/ shlibs file? No. What I meant to say is that asterisk-dev provides broken shlibs _information_ - and looking closer it turns out that it contains no shlibs file at all (and depend on no other package that does). Therefore asterisk-flite and asterisk-espeak simply depends unversioned on asterisk, which then breaks when ABI changes :-( So binNMU fixes the concrete problem - I have not yet filed a bugreport against asterisk about the underlying problem of providing shlibs data to fix it for good (with another binNMU). ...or did I misunderstand things somehow? - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Re: Possible release note for systems running PHP through CGI.
On 12-08-19 at 11:17am, Charles Plessy wrote: - PHP scripts can be executed by Apache httpd through libapache2-mod-php5 or php5-cgi. Debian recommends libapache2-mod-php5, but there are still thousands of installations wich report the use of php5-cgi according to the Popularity Contest statistics. FWiW, out of the ~7'500 popcon hits of regular use of php5-cgi, ~900 also regularly uses suphp, so might be unaffected by this issue. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#684044: unblock: nodejs/0.6.19~dfsg1-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package nodejs
We have now adjusted nodejs as ruled by tech-ctte at
https://lists.debian.org/debian-devel-announce/2012/07/msg2.html,
and consider it ready for inclusion in Wheezy.
Attached is a debdiff of changes made since 0.6.19~dfsg1-2 - the version
that would've entered testing had it not been held back by bugs #611698
and #681360.
Kind regards, and thanks for your tireless work,
- Jonas
unblock nodejs/0.6.19~dfsg1-4
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -Nru nodejs-0.6.19~dfsg1/debian/changelog nodejs-0.6.19~dfsg1/debian/changelog
--- nodejs-0.6.19~dfsg1/debian/changelog 2012-06-06 23:36:53.0 +0200
+++ nodejs-0.6.19~dfsg1/debian/changelog 2012-08-06 14:51:34.0 +0200
@@ -1,3 +1,44 @@
+nodejs (0.6.19~dfsg1-4) unstable; urgency=medium
+
+ * Update package relations:
++ Break only packages actually calling /usr/bin/node (directly or
+ via env).
++ Tighten breaks for packages with fixed release.
+ * Set urgency=medium as this change affects only packaging hints so
+should not need reset of aging timer in unstable.
+
+ -- Jonas Smedegaard d...@jones.dk Mon, 06 Aug 2012 14:51:31 +0200
+
+nodejs (0.6.19~dfsg1-3) unstable; urgency=low
+
+ [ Jérémy Lal ]
+ * debian/patches:
++ 2012_fix_v8_3_10.patch, fix crash on exit when building
+ against libv8-3.10.8.
++ 2013_waf_linkflags.patch, waf must support LINKFLAGS,
+ Closes: #678563.
+
+ [ Jonas Smedegaard ]
+ * Rename binary node → nodejs:
++ Adjust paths of binary and manpage.
++ Fix avoid bogus explicit installation of debug files.
++ Adjust install scripts and add cleanup for old alternative.
++ Patch manpage to adjust command name.
++ Have binary package nodejs break any packages in Debian that
+ reference /usr/bin/node.
++ Add new binary package nodejs-legacy, and have that (not nodejs)
+ conflict with node.
++ Add NEWS entry.
+Closes: bug#611698, #681360. See also bug#614907. Thanks to
+tech-ctte and everyone else helping to resolve this.
+ * Work around upstream shipping docs in wrong subdir, and disable huge
+patch 1002 attempting same but causing FTBFS for me. Keep patch 1002
+in source, to ease proof-reading by release team.
+ * Add patch 2004 to fix FTBFS: Relax a test to work with slightly
+different output when linked against recent v8.
+
+ -- Jonas Smedegaard d...@jones.dk Sat, 28 Jul 2012 11:19:38 +0200
+
nodejs (0.6.19~dfsg1-2) unstable; urgency=low
* debian/patches:
diff -Nru nodejs-0.6.19~dfsg1/debian/control nodejs-0.6.19~dfsg1/debian/control
--- nodejs-0.6.19~dfsg1/debian/control 2012-05-16 01:59:26.0 +0200
+++ nodejs-0.6.19~dfsg1/debian/control 2012-08-06 14:45:13.0 +0200
@@ -51,7 +51,24 @@
Architecture: any
Depends: ${shlibs:Depends},
${misc:Depends}
-Conflicts: node
+Breaks:
+ buddycloud-server (= 0.3.1-1),
+ carto (= 0.4.6+ds1-1),
+ coffeescript ( 1.3.3-3~),
+ node-bones (= 2.0.1+ds1-1),
+ node-cli (= 0.4.2~20120411-1),
+ node-express (= 2.5.9-1),
+ node-get (= 1.1.5+ds1-1),
+ node-jake (= 0.2.32-1),
+ node-less ( 1.3.0~20120310-3~),
+ node-mapnik (= 0.6.7-2),
+ node-mbtiles (= 0.2.3-1),
+ node-optimist (= 0.3.1-1),
+ node-semver (= 1.0.13-1),
+ node-tilelive (= 4.2.1-3),
+ node-uglify ( 1.2.6-2~),
+ node-vows (= 0.6.3-1),
+ npm (= 1.1.4~dfsg-1),
Description: Node.js event-based server-side javascript engine
Node.js is similar in design to and influenced by systems like
Ruby's Event Machine or Python's Twisted.
@@ -81,3 +98,27 @@
HTTP, Multipart Parsing, TCP, DNS, Assert, Path, URL, Query Strings.
.
This package contains the debugging symbols.
+
+Package: nodejs-legacy
+Priority: extra
+Architecture: all
+Depends: ${misc:Depends},
+ nodejs (= 0.6.19~dfsg1-3~)
+Conflicts: node
+Description: Node.js event-based server-side javascript engine (legacy symlink)
+ Node.js is similar in design to and influenced by systems like
+ Ruby's Event Machine or Python's Twisted.
+ .
+ It takes the event model a bit further - it presents the event
+ loop as a language construct instead of as a library.
+ .
+ Node.js is bundled with several useful libraries to handle server tasks :
+ System, Events, Standard I/O, Modules, Timers, Child Processes, POSIX,
+ HTTP, Multipart Parsing, TCP, DNS, Assert, Path, URL, Query Strings.
+ .
+ This package contains a symlink for legacy Node.js code requiring
+ binary to be /usr/bin/node (not /usr/bin/nodejs as provided in Debian).
+ .
+ No other Debian packages should depend on this package. For more
+ information, see
+ http://lists.debian.org/debian-devel-announce/2012/07/msg2.html
Bug#684046: unblock: coffeescript/1.3.3-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package coffeescript
We have now adjusted coffeescript to use nodejs (not node) as hashbang.
https://lists.debian.org/debian-devel-announce/2012/07/msg2.html,
and consider it ready for inclusion in Wheezy.
Attached is a debdiff of changes made since the version that would've
entered testing had it not been held back by nodejs and bug#614907.
Kind regards, and thanks for your tireless work,
- Jonas
unblock coffeescript/1.3.3-3
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
diff -Nru coffeescript-1.3.3/debian/changelog coffeescript-1.3.3/debian/changelog
--- coffeescript-1.3.3/debian/changelog 2012-05-23 21:28:43.0 +0200
+++ coffeescript-1.3.3/debian/changelog 2012-08-06 14:40:01.0 +0200
@@ -1,3 +1,20 @@
+coffeescript (1.3.3-3) unstable; urgency=low
+
+ * Really fix build-depend on nodejs.
+
+ -- Jonas Smedegaard d...@jones.dk Mon, 06 Aug 2012 14:40:00 +0200
+
+coffeescript (1.3.3-2) unstable; urgency=low
+
+ * Fix explicitly build-depend on nodejs (used in cakefile to build
+coffeescript).
+ * Add patch to call binary /usr/bin/nodejs (not node) during build,
+adjust rules file to do the same for installed wrappers, and tighten
+(build-)dependency on nodejs.
+See bug#614907.
+
+ -- Jonas Smedegaard d...@jones.dk Mon, 06 Aug 2012 02:24:17 +0200
+
coffeescript (1.3.3-1) unstable; urgency=low
* New upstream release.
diff -Nru coffeescript-1.3.3/debian/control coffeescript-1.3.3/debian/control
--- coffeescript-1.3.3/debian/control 2012-05-23 21:34:48.0 +0200
+++ coffeescript-1.3.3/debian/control 2012-08-06 14:38:24.0 +0200
@@ -8,6 +8,7 @@
devscripts,
debhelper,
dh-buildinfo,
+ nodejs (= 0.6.19~dfsg1-3~),
node-uglify,
help2man
Standards-Version: 3.9.3
diff -Nru coffeescript-1.3.3/debian/patches/series coffeescript-1.3.3/debian/patches/series
--- coffeescript-1.3.3/debian/patches/series 2011-08-20 17:15:15.0 +0200
+++ coffeescript-1.3.3/debian/patches/series 2012-08-06 02:31:18.0 +0200
@@ -1,2 +1,3 @@
support-system-wide-install.patch
avoid-tests-during-build.patch
+use_usr-bin-nodejs.patch
diff -Nru coffeescript-1.3.3/debian/patches/use_usr-bin-nodejs.patch coffeescript-1.3.3/debian/patches/use_usr-bin-nodejs.patch
--- coffeescript-1.3.3/debian/patches/use_usr-bin-nodejs.patch 1970-01-01 01:00:00.0 +0100
+++ coffeescript-1.3.3/debian/patches/use_usr-bin-nodejs.patch 2012-08-06 02:50:19.0 +0200
@@ -0,0 +1,32 @@
+Description: Use /usr/bin/nodejs (not /usr/bin/env node)
+Author: Jonas Smedegaard d...@jones.dk
+Forwarded: no
+Last-Update: 2012-08-06
+
+--- a/bin/cake
b/bin/cake
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env node
++#!/usr/bin/nodejs
+
+ var path = require('path');
+ var fs = require('fs');
+--- a/bin/coffee
b/bin/coffee
+@@ -1,4 +1,4 @@
+-#!/usr/bin/env node
++#!/usr/bin/nodejs
+
+ var path = require('path');
+ var fs = require('fs');
+--- a/Cakefile
b/Cakefile
+@@ -34,7 +34,7 @@
+
+ # Run a CoffeeScript through our node/coffee interpreter.
+ run = (args, cb) -
+- proc = spawn 'node', ['bin/coffee'].concat(args)
++ proc = spawn 'nodejs', ['bin/coffee'].concat(args)
+ proc.stderr.on 'data', (buffer) - console.log buffer.toString()
+ proc.on'exit', (status) -
+ process.exit(1) if status != 0
diff -Nru coffeescript-1.3.3/debian/rules coffeescript-1.3.3/debian/rules
--- coffeescript-1.3.3/debian/rules 2012-05-23 21:24:20.0 +0200
+++ coffeescript-1.3.3/debian/rules 2012-08-06 02:40:02.0 +0200
@@ -29,7 +29,7 @@
# suppress checking binary file, to not upset dpkg-source
DEB_COPYRIGHT_CHECK_IGNORE_REGEX = ^documentation/images/logo\.png|debian/(changelog|copyright(|_hints|_newhints))$
-CDBS_DEPENDS_coffeescript = nodejs
+CDBS_DEPENDS_coffeescript = nodejs (= 0.6.19~dfsg1-3~)
CDBS_RECOMMENDS_libjs-coffeescript = javascript-common
CDBS_SUGGESTS_coffeescript = libjs-coffeescript
CDBS_SUGGESTS_libjs-coffeescript = coffeescript
@@ -73,11 +73,11 @@
MINIFY=false bin/cake build:browser
$(if $(filter nocheck,$(DEB_BUILD_OPTIONS)),,bin/cake test:browser)
- echo '#!/usr/bin/env node' debian/$(cake)
+ echo '#!/usr/bin/nodejs' debian/$(cake)
echo debian/$(cake)
echo require('../lib/coffee-script/lib/coffee-script/cake').run(); debian/$(cake)
- echo '#!/usr/bin/env node' debian/coffee
+ echo '#!/usr/bin/nodejs' debian/coffee
echo debian/coffee
echo require('../lib/coffee-script/lib/coffee-script/command').run(); debian/coffee
Bug#684044: unblock: nodejs/0.6.19~dfsg1-4
On 12-08-06 at 03:12pm, Adam D. Barratt wrote: On 06.08.2012 14:20, Jonas Smedegaard wrote: Please unblock package nodejs We have now adjusted nodejs as ruled by tech-ctte at https://lists.debian.org/debian-devel-announce/2012/07/msg2.html, and consider it ready for inclusion in Wheezy. I'm afraid that, at least imo, more than a month after freeze is far too late to be adding substantial new packages to Wheezy - particularly as I assume a successful unblock would be followed by requests to unblock all of the reverse dependencies. Thanks for looking at this so swiftly. I understand the worry of a slippery slope of opening the gates to everything Nodejs. I do find it sensible, however, to consider e.g. one of these subsets: 1) nodejs 2) nodejs + uglifyjs 3) nodejs + ugifyjs + revert inferior fix for bug#679665 True that Nodejs has never entered testing before. Code has been stable and usable in unstable for more than a year, however. Only reason it didn't progress was the node/nodejs issue. Doing 1) would promote the node → nodejs change to the World, whereas postponing till next stable release would likely cause the (from Debian POV) badly names node to stick much harder in the larger FLOSS ecosystem. Doing 1) would also ease the kickstart for Nodejs users tremendously, as it has proven quite a difficult beast to tame individually at each host needing it. Doing 2) would additionally allow users of jquery (for which I suspect there are many!) to locally minify the code which is currently pretty much unusable for serving content for the web (instead of the already quite large 95k minified the fix for bug#679665 made the package offer only the non-minified 252k file. Doing 3) would make a long list of packages (300 in unstable currently) suitable for serving via web, not only locally, out of the box. Please reconsider unblocking nodejs: It is quite usable even if not letting in all of the node libraries as well. Kind regards, - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#682279: unblock: libweb-id-perl/1.921-3
Hi Julien, and others, On 12-07-28 at 01:33pm, Julien Cristau wrote: For a request like this, if it takes more than 5 minutes to process it's a waste of our time. Having a clear changelog helps avoid that, as does not arguing or getting on your high horse when asked clarification questions. And by helping that, it helps get your request approved, which I guess is what you want? Yes, that is what I want. My apologies for not following rules and getting on my high horse. How to proceeed from here? Should I now... * Wait for you to ask clarification questions or make a verdict? * Make a new package fixing the bad things pointed out by Cyril - i.e. a) mention in changelog relevant bugs that was filed after last package release, and b) more descriptive changelog regarding how changes was made, and c) random noise reverted? * Something else? Regards, - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#683030: unblock: vlc/2.0.3-1
On 12-07-28 at 04:47pm, Adam D. Barratt wrote: - this change looks slightly odd: * Do not run doxygen if it is not installed. doxygen is in B-D-Indep and only appears to be used when building the arch:all -doc package. On that basis, why would it not always be installed when required? I did not apply this change but recognize it from Emdebian sprint: Reason is, I believe, to ease bootstrapping new architectures by suppressing build of arch-all packages. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#682279: unblock: libweb-id-perl/1.921-3
On 12-07-21 at 01:05am, Cyril Brulebois wrote: Hello, Salvatore Bonaccorso car...@debian.org (21/07/2012): libweb-id-perl has a missing dependency which causes another package to FTBFS. I have cloned the original Bugreport now as [1], see in particular Jonas' message in [2]. [1]: http://bugs.debian.org/682277 [2]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682277#17 no bug reference in the changelog isn't helpful… ...which is the reason it was provided in above email, I guess. I do believe inclusion of bug references in changelog is optional (see Debian Policy §4.4). +libweb-id-perl (1.921-3) unstable; urgency=low + + * Fix depend on libmousex-types-perl or libmoosex-types-perl (in +addition to recommending libmousex-types-perl). Surely this could have been more descriptive, like “fix misconcatenation for the CDBS_DEPENDS_ALL variable”. A naïve mind would be looking at debian/control otherwise, and would think something was overlooked… I agree that my choice of words was not ideal for release team review. My target audience when writing changelogs is our users, however, and I do find my actual changelog entry more descriptive for them than your proposed one. + * Relax to build unversioned on cdbs: Needed version satisfied in +stable, and oldstable no longer supported. + * Fix use pseudo-fields in copyright file (license-in-comment for +verbatim dual-license text covered in separate License sections, +and comment-in-license for non-verbatim parts of License sections): +File format 1.0 mandates License field to either be single-line or +include all licensing info. Looks like random noise to me. Just when I thought the rules were clear… http://release.debian.org/wheezy/freeze_policy.html Then reject it, if you find it too unpleasing!!! - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#682279: unblock: libweb-id-perl/1.921-3
On 12-07-21 at 01:53pm, Philipp Kern wrote: On Sat, Jul 21, 2012 at 11:02:33AM +0200, Jonas Smedegaard wrote: Then reject it, if you find it too unpleasing!!! I hope you realize that Cyril is only doing his job. You're not being helpful and albeit I'm tempted to just say No problem to that statement it would still leave an RC bug open. Sorry for my brevity and for the trailing exclamation marks. I read the mail from Cyril and was puzzled as to how to react on it. Let me try in a nicer manner to elaborate on my confusion...: Is the noise of the non-crucial changes so problematic (a.k.a. unpleasing) that the release team considers the current package unsuitable for getting an exception from the freeze? I honestly did not consider that noise as significant changes not related to the bug to be fixed, as it is phrased at the fine http://release.debian.org/wheezy/freeze_policy.html. Do the release team consider the package unsuitable for freeze exception due to the lack of bug reference in the changelog (the bug was unfortunately unavailable to reference at the time the package was produced and I honestly was unaware that such reference was problematic for the release team to get passed in the freeze exception bugreport)? Do the release team consider the package unsuitable for freeze exception due to the user-only oriented changelog entry - i.e. lack of verbose enough details in changelog for release managers to follow _how_ the issue was fixed? Would it be more helpful of me to upload another package release that rephrased the changelog to be more helpful for release managers to understand how non-newest-debhelper-style packaging was performed internally? Should I do that in addition to the user-oriented changelog entry or instead of it? Would it be more helpful if I had not asked these questions but instead just uploaded a new package fixing these three issues raised by Cyril? Especially that last question I ask explicitly so that I can most smoothly help you guys do your jobs for other of packages I may be involved in requesting freeze exceptions for. Kind regards, and thanks for your great work, Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#668008: uw-imap transtion: asterisk
On 12-06-20 at 01:55pm, Adam D. Barratt wrote: On 17.05.2012 07:33, Cyril Brulebois wrote: Jonas Smedegaard d...@jones.dk (17/05/2012): On 12-05-16 at 11:55pm, Tzafrir Cohen wrote: What modifications? Alternatively: where can I find the new package? They need to change from current build-depending on libc-client2007e-dev to build-depending on either libc-client2007f-dev or libc-client-dev. As Adam said, I can't find any bug reports against said packages, asking maintainers to prepare for this change; bug reports that we would make RC when the transition starts. As far as I can see, those bugs never got filed. Binary package libc-client*-dev is from source package uw-imap. New package has not been released yet (that's the issue of this bugreport) but is prepared and can be fetched and examined with this command: debcheckout uw-imap You can always upload to experimental. Among other things, that helps you clear the NEW queue in advance. There also doesn't appear to be a newer uw-imap in experimental. Given the timing, I think it's too late to start this transition now I'm afraid. Too bad. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#677574: [Pkg-javascript-devel] Bug#677574: transition: libv8
On 12-06-17 at 12:06pm, Jérémy Lal wrote: according to [1] we have After Sunday the 20th of May, any new transitions are likely not to be processed until after the release. So that transition is way too late, and the result is that libv8 3.10.8 should be uploaded to experimental instead. Closing this bug. Whoa - would you mind reconsidering that? unlikely != impossible ...and this transition seems a pretty lightweight one to me: three packages (with no other packages depending on them) needing a simple rebuild, and one package not even in testing at all at the moment and also cauising no other ripples as I can see, which needs minor work. Why give up without even trying? Regards, - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#677574: [Pkg-javascript-devel] Bug#677574: transition: libv8
On 12-06-17 at 01:04pm, Julien Cristau wrote: On Sun, Jun 17, 2012 at 12:52:40 +0200, Jonas Smedegaard wrote: On 12-06-17 at 12:06pm, Jérémy Lal wrote: according to [1] we have After Sunday the 20th of May, any new transitions are likely not to be processed until after the release. So that transition is way too late, and the result is that libv8 3.10.8 should be uploaded to experimental instead. Closing this bug. Whoa - would you mind reconsidering that? Why? He's done the right thing... You dropped my explanation from your quote. But if you do not consider that reasonable, then I see no point in elaborating. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#677574: [Pkg-javascript-devel] Bug#677574: transition: libv8
[dropping cc - we should all be following bugreport by now] On 12-06-17 at 01:22pm, Jérémy Lal wrote: On 17/06/2012 12:52, Jonas Smedegaard wrote: On 12-06-17 at 12:06pm, Jérémy Lal wrote: according to [1] we have After Sunday the 20th of May, any new transitions are likely not to be processed until after the release. So that transition is way too late, and the result is that libv8 3.10.8 should be uploaded to experimental instead. Closing this bug. Whoa - would you mind reconsidering that? unlikely != impossible ...and this transition seems a pretty lightweight one to me: three packages (with no other packages depending on them) needing a simple rebuild, and one package not even in testing at all at the moment and also cauising no other ripples as I can see, which needs minor work. Why give up without even trying? Cons: * one month too late * chromium isn't even using libv8 nor libv8-i18n * nodejs won't be in wheezy * current libv8 seems good enough for drizzle and osmium I disagree that it is too late. We were only told it is less likely to be approved the later we request it. If Chromium don't use libv8 it is not a Con but a pro (if having any weight here at all): It merely simplifies the transition! Nodejs not getting into Wheezy is similarly a pro if anything: simplifies transition! Pros: * libv8 3.10.8 won't require transition for each patch-level fix, and that is something really good from a security-team P.O.V. * i spent a hell of a lot of time to make sure it runs on mipsel * and as a bonus it runs on kfreebsd-* More cons that pros, still if someone (a DD, of course) want to make that transition *today* i'll be happy to do my part of the job (i.e. upload nodejs compatible with libv8-3.10.8). So as a pro you argue that it enables more architectures and relieves security team in the future, and as a con you argue that it is good enough as-is. I disagree with your judgement. ...but I consider my role in our team to be helping you out, so I won't go against you and push this without you agreeing. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Bug#677574: [Pkg-javascript-devel] Bug#677574: transition: libv8
Hi Steven, On 12-06-17 at 12:58pm, Steven Chamberlain wrote: On 17/06/12 12:50, Jonas Smedegaard wrote: I disagree that it is too late. We were only told it is less likely to be approved the later we request it. I thought this transition had already been requested, approved, and just waiting on an upload to stable? On 15/06/12 00:34, Cyril Brulebois wrote: Tracker is at: http://release.debian.org/transitions/html/libv8.html Please go ahead with an upload to unstable. I agree: this transition was approved - but then dropped instead of fulfilled when finally ready, by the requester himself (Jérémy). What I am quoted for commenting on above is not this specific transistion, however, but a general message about the release process. - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
Re: haskell transition: Remove, Transition, Upload Fix or Upload Fix, Wait, Transition?
On 12-06-08 at 02:13pm, Mehdi Dogguy wrote: On 08/06/12 14:01, Joachim Breitner wrote: As we are resetting the age timer anyways I guess this means that John can also get his new pandoc version in (http://lists.debian.org/debian-haskell/2012/06/msg00010.html). No, it doesn't mean that. Please let's keep things stable until this migration is sorted out. Acknowledged: I'll hold my breath until explicitly given a green light! - Jonas -- * Jonas Smedegaard - idealist Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature
