|
Size: 11564
Comment: squeeze one more item in
|
Size: 6521
Comment: edition 58 sent
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 20: | Line 20: |
| === anacron might be disabled if 2.3-33 was ever installed === If you run Debian testing/unstable and ever installed anacron 2.3-33 on a systemd based system, then anacron will no longer be enabled and the daily/weekly/monthly cron jobs will not be run until it is. Since not all cron jobs have migrated to systemd timers, Debian testing/unstable systems with systemd and anacron may be missing some essential cron jobs, such as making backups of aptitude state. To see if a system is affected you can use these commands: {{{ zgrep -i anacron.*2.3-33 /var/log/apt/history.log* systemctl status anacron.service anacron.timer }}} To re-enable anacron you can use these commands: {{{ sudo systemctl enable anacron.service anacron.timer sudo systemctl start anacron.service anacron.timer }}} More details of this problem are available in these bugs: https://bugs.debian.org/1019554 https://bugs.debian.org/1020966 https://bugs.debian.org/1021496 -- Paul Wise === riscv64 porterbox === There is now a [[https://blog.aurel32.net/riscv64-porterbox.html|porterbox for riscv64]] available for Debian contributors to [[https://wiki.debian.org/PorterBoxHowToUse|use]] for porting packages to RISC-V. Thanks to SiFive for providing the HiFive Unmatched board, OSUOSL for assembling and hosting the hardware and Aurélien Jarno for installing and setting up the porterbox. -- Paul Wise === porterbox DNS alias maintainers needed === Jakub Wilk has [[https://lists.debian.org/msgid-search/20221107213046.atgukd2iogsaynxo@jwilk.net|mentioned]] that the DNS aliases to Debian porterboxes is now unmaintained and in need of new maintainers. -- Paul Wise === debtags.d.o maintainers needed === Enrico Zini has announced [[https://lists.debian.org/msgid-search/20221019132043.d4c4liyt6s6qewgy@enricozini.org|debtags.d.o]] is in need of new maintainers and will be shut down if none are forthcoming. -- Paul Wise === lintian contributors needed === The primary lintian contributors have [[https://lists.debian.org/msgid-search/5e4d0e28-a3f4-4302-8364-5afd93d8ae17@www.fastmail.com|stopped]] [[https://lists.debian.org/msgid-search/CAFHYt550_6hc-2SRjqYv0z9kgpWuLpGnnxVOonPOHP3R+pAQZA@mail.gmail.com|working]] on it. Axel Beckert has [[https://bugs.debian.org/1012289|stepped up]] to provide maintenance work, but requests help adding new tags, performance tuning and other important work. If you are interested in working on it, please join the [[https://salsa.debian.org/lintian|lintian group on salsa]] (DD will be accepted instantly, non-DD should show some contributions first, e.g. via Merge Requests), add yourself to the [[https://wiki.debian.org/Teams/Lintian|lintian team wiki page]], join the [[https://lists.debian.org/debian-lint-maint/|debian-lint-maint]] mailing list, and review the [[https://bugs.debian.org/src:lintian|bugs filed against lintian]], [[https://salsa.debian.org/groups/lintian/-/issues|issues on salsa]] and merge requests on salsa ([[https://salsa.debian.org/lintian/lintian/-/merge_requests|1]] [[https://salsa.debian.org/groups/lintian/-/merge_requests|2]]). -- Paul Wise + Axel Beckert === Experimental manual migration pseudo-excuses === The [[https://release.debian.org/britney/pseudo-excuses-experimental.html|experimental pseudo-excuses]] (warning: large file) help maintainers discover problems that will be introduced when they manually migrate packages from experimental to unstable. These excuses are now imported into the [[https://qa.debian.org/excuses.php|Debian QA excuses page]], which allows checking individual package excuses for testing migration and now also pseudo-excuses for experimental manual migration. This is much more convenient than loading the very large excuses and pseudo-excuses HTML files. [[https://bugs.debian.org/944737|Help]] is [[https://bugs.debian.org/991237|needed]] from Python/Django developers to integrate the pseudo-excuses into the [[https://tracker.debian.org|Debian Package Tracker]], see the [[https://qa.pages.debian.net/distro-tracker/contributing.html|guide to contributing]] if you would like to help. === CPU instruction selection documentation === New documentation has been written summarising all the [[https://wiki.debian.org/InstructionSelection|options for selection of CPU instructions]], including porting between SIMD instructions, emulating atomic instructions, manual runtime code path selection, manual runtime function selection, compiler function multi-versioning, glibc hwcaps library selection, runtime binary selection, blocking installation and blocking running binaries. When you discover a package has limited portability due to a higher baseline, use of SIMD/atomic instructions, or other CPU instruction related problem, please consider perusing the new documentation, improving the portability using the documented techniques and contributing your changes upstream where possible. If you see others discovering these issues, please suggest they take a look at the documentation. -- Paul Wise, Gioele Barabucci and Bastien Roucaries |
|
| Line 89: | Line 23: |
| [[https://lists.debian.org/debian-devel-announce/2022/11/msg00001.html|58]] |
Translation(s) : English - español - Français - 日本語
News for Debian developers
This wiki page collects small news that all developers should know but that are not worth a dedicated mail to debian-devel-announce. Follow the template "Example of news" and add your news below it. If there are some other items already, please sort your item in descending order of importance to the Debian development community. See /Help for more information on how to write entries. If you have any questions, please ask the publicity team or the Debian English localisation mailing-list.
If you are able to post to debian-devel-announce (all Debian members can) and there are 5 or more items below, you might want to send out the news. To send out a new issue, you can use this helper script to generate the email version of this page. After generating the mail, proof-read it, correct any spelling, formatting or grammatical errors and send out the mail. Once the mail is sent and archived, please delete the items that were sent, add a link to the archived mail in the Previous news section and mention the mail in ProjectNews.
Example of news
This is a sample news. Copy it and edit the title, content and signature... You can use links like this. Put real news below this sample.
-- Your Name
Previous news
58 57 56 55 54 53 52 51 50
49 48 47 46 45 44 43 42 41 40
39 38 37 36 35 34 33 32 31 30
29 28 27 26 25 24 23 22 21 20
19 18 17 16 15 14 13 12 11 10
9 8 7 6 5 4 3 2 1