Bug#913659: Document that not all bugs are policy violations
On Fri, 16 Nov 2018, Sean Whitton wrote: > On Fri 16 Nov 2018 at 12:22PM -0200, Henrique de Moraes Holschuh wrote: > > How about also adding one that makes it clear that in *Debian*, policy > > follows practice, and not the other way around (which should also > > require seconds just to make sure people agree with this, even if it is > > a decades-long practice in debian-policy)... > > This is already there, in § 1.3.3 Not in such a clearly stated form, but yeah. Anyway, that was a passing comment, it is off-topic on this bug report, and for that I apologise... -- Henrique Holschuh
Processed: developers-reference : styles of handwriting are Bold
Processing control commands: > tags -1 + wontfix Bug #657107 [src:developers-reference] developers-reference : styles of handwriting are Bold Added tag(s) wontfix. -- 657107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#657107: developers-reference : styles of handwriting are Bold
Control: tags -1 + wontfix Nobuhiro Iwamatsu wrote: > A.2.2. debdiff, A.5.3. dcut and A.6.7. dpkg-depcheck styles of > handwriting are Bold. > It seems that it will be changed into bold if it surrounds by . > Commands other than these are surrounded by . > Therefore, the style of handwriting is not Bold. As I see it, this is only a very minor difference, and thus not worse a change. So tagging this bug as wontfix. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#907666: marked as done (developers-reference: Updating the German translation)
Your message dated Fri, 16 Nov 2018 22:40:31 +0100 with message-id <20181116224031.ac3584bfb4f5114dc3c9d...@mailbox.org> and subject line developers-reference: Updating the German translation has caused the Debian Bug report #907666, regarding developers-reference: Updating the German translation to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 907666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: developers-reference-de Severity: minor Tags: patch Translating some previously untranslated sentences and checking other which were marked fuzzy. Note that this is not complete, poedit says there are still 115 tasks open... (I will time permitting, work a bit on them the next few days and update the MR accordingly.) Please see the MR here: https://salsa.debian.org/debian/developers-reference/merge_requests/3 -- tobi -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled developers-reference-de depends on no packages. Versions of packages developers-reference-de recommends: pn debian-policy Versions of packages developers-reference-de suggests: pn doc-base --- End Message --- --- Begin Message --- Tobias Frost wrote: > Translating some previously untranslated sentences and checking other > which were marked fuzzy. Note that this is not complete, poedit says > there are still 115 tasks open... (I will time permitting, work a bit on > them the next few days and update the MR accordingly.) > > Please see the MR here: > https://salsa.debian.org/debian/developers-reference/merge_requests/3 This has been merged in the meantime, so closing this bug. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076--- End Message ---
Bug#913659: Document that not all bugs are policy violations
Hello, On Fri 16 Nov 2018 at 12:22PM -0200, Henrique de Moraes Holschuh wrote: > How about also adding one that makes it clear that in *Debian*, policy > follows practice, and not the other way around (which should also > require seconds just to make sure people agree with this, even if it is > a decades-long practice in debian-policy)... This is already there, in § 1.3.3 -- Sean Whitton signature.asc Description: PGP signature
Bug#865367: marked as done (developers-reference: section 5.5.1: explicitly mention that stable and oldstable uploads must use release codename)
Your message dated Fri, 16 Nov 2018 22:22:41 +0100 with message-id <2018111641.202bb82c715fe9a4aa623...@mailbox.org> and subject line developers-reference: section 5.5.1: explicitly mention that stable and oldstable uploads must use release codename has caused the Debian Bug report #865367, regarding developers-reference: section 5.5.1: explicitly mention that stable and oldstable uploads must use release codename to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 865367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: developers-reference Version: 3.4.18 Severity: normal Section 5.5.1 seems to imply uploads to stable and oldstable should target "stable" or "oldstable" in the distribution field of the changelog entry, which is incorrect. Please add explicit text to section 5.5.1, directing uploaders to use the release codename, instead (e.g. "jessie", "wheezy"...). Suggested text: When uploading to stable, debian/changelog should use the release codename as the target. I.e. upload to "jessie", "stretch", etc. instead of uploading to "stable" or "oldstable". Thank you! -- Henrique Holschuh --- End Message --- --- Begin Message --- Henrique de Moraes Holschuh wrote: > Section 5.5.1 seems to imply uploads to stable and oldstable should > target "stable" or "oldstable" in the distribution field of the > changelog entry, which is incorrect. > > Please add explicit text to section 5.5.1, directing uploaders to use > the release codename, instead (e.g. "jessie", "wheezy"...). This has already been fixed in the meantime (see https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#distribution ) so closing this bug. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076--- End Message ---
Bug#900679: nmu: Migrating developers-reference to Salsa and minor updates
Aurélien COUDERC wrote: > I would like to NMU developers-reference for migrating the repository to Salsa > and a couple of minor changes. > > The complete changelog would be : > > developers-reference (3.4.19+nmu1) UNRELEASED; urgency=medium > > [ Aurélien COUDERC ] > * Non-maintainer upload. > * Move repository to Salsa, update Vcs-* fields. > * d/control: Bump Standards-Version to 4.1.4, no change needed. > * Fix CSS text color to avoid the HTML version being unreadable when > using a light on dark default browser stylesheet. The above changings were committed in the meantime, so the target of the OP and this bug is closed. Thus this bug can closed, right? Any objections? (There was some discussion about maintenance of the devref package in this bug, however this does not deserve keeping this bug open, or it should be renamed accordingly.) Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#690750: Broken links in developers-reference as published on the Debian's website
Пт 16 ноя 2018 @ 20:07 Holger Wansing : > Control: tags -1 + pending > > Lev Lamberov wrote: >> Вс 04 ноя 2018 @ 12:00 Holger Wansing : >> >> > Proposal: maybe the easiest way to make all variants (view via debian.org >> > and opened locally) work correctly, would be to change it this way: >> > >> > "This page is also available in >> > https://www.debian.org/doc/devel-manuals#devref";>French, >> > German, >> > Italian, Russian, and Japanese." >> > >> > since the links on that page are fine and can be linked from everywhere >> > with one single static link. >> > Of course, there are still some corner cases which do not work (for >> > example, >> > when you have the packages installed locally, you cannot switch from the >> > local english to the local german version via that links, and when you >> > have no internet connection, you also get an irritating situation), but >> > most >> > usecases should be fine, and it would be an improvement compared to the >> > current situation, where all links do not work! >> > >> > Would fix #690750 and #912724. >> > >> > Comments? >> >> In case one take a look into other documentation (togather with its >> translation), one will not find any such notes and links to >> translations. Maybe there's no need in such note in "Debian Developer's >> Reference"? Or at least no need in explicit links? What about to remove >> it completely or change text to something like "This documentation is >> also available in some other languages"? > > I have committed this now like this, while 'some other languages' is a link > to https://www.debian.org/doc/devel-manuals#devref Thanks, Holger! Looks like this is the best option for now. Maybe better variant will come later. Cheers! Lev
Bug#908890: developers-reference: As alioth is gone, replace references to Salsa
Tobias Frost created a merge request for this, under https://salsa.debian.org/debian/developers-reference/merge_requests/6 Any objections against me merging this? Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Bug#818850: developers-reference: Join the two chapters about the 'default' field
Control: tags -1 + pending Holger Wansing wrote: > Control: tags -1 - pending > > > Maintainers, what do you think about > https://salsa.debian.org/debian/developers-reference/merge_requests/8/diffs > to > fix this bug? > > Any objections against me merging this? > Since there were no objections, I have merged this into master now. Tagging this bug as pending. Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Processed: Re: developers-reference: Join the two chapters about the 'default' field
Processing control commands: > tags -1 + pending Bug #818850 [developers-reference] developers-reference: two chapters regarding the 'default' field Ignoring request to alter tags of bug #818850 to the same tags previously set -- 818850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #818850 in developers-reference marked as pending
Processing control commands: > tag -1 pending Bug #818850 [developers-reference] developers-reference: two chapters regarding the 'default' field Added tag(s) pending. -- 818850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug #818850 in developers-reference marked as pending
Processing control commands: > tag -1 pending Bug #818850 [developers-reference] developers-reference: two chapters regarding the 'default' field Ignoring request to alter tags of bug #818850 to the same tags previously set -- 818850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818850 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#690750: Broken links in developers-reference as published on the Debian's website
Control: tags -1 + pending Lev Lamberov wrote: > Вс 04 ноя 2018 @ 12:00 Holger Wansing : > > > Proposal: maybe the easiest way to make all variants (view via debian.org > > and opened locally) work correctly, would be to change it this way: > > > > "This page is also available in > > https://www.debian.org/doc/devel-manuals#devref";>French, > > German, > > Italian, Russian, and Japanese." > > > > since the links on that page are fine and can be linked from everywhere > > with one single static link. > > Of course, there are still some corner cases which do not work (for > > example, > > when you have the packages installed locally, you cannot switch from the > > local english to the local german version via that links, and when you > > have no internet connection, you also get an irritating situation), but > > most > > usecases should be fine, and it would be an improvement compared to the > > current situation, where all links do not work! > > > > Would fix #690750 and #912724. > > > > Comments? > > In case one take a look into other documentation (togather with its > translation), one will not find any such notes and links to > translations. Maybe there's no need in such note in "Debian Developer's > Reference"? Or at least no need in explicit links? What about to remove > it completely or change text to something like "This documentation is > also available in some other languages"? I have committed this now like this, while 'some other languages' is a link to https://www.debian.org/doc/devel-manuals#devref Tagging these bugs as pending Holger -- Holger Wansing PGP-Finterprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Processed: Re: Broken links in developers-reference as published on the Debian's website
Processing control commands: > tags -1 + pending Bug #690750 [developers-reference] developers-reference: no link to English manual Added tag(s) pending. -- 690750: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#913659: Document that not all bugs are policy violations
On Fri, 2018-11-16 at 12:22:35 -0200, Henrique de Moraes Holschuh wrote: > How about also adding one that makes it clear that in *Debian*, policy > follows practice, and not the other way around (which should also > require seconds just to make sure people agree with this, even if it is > a decades-long practice in debian-policy)... Not always, two cases that quickly come to mind are the nocheck and terse DEB_BUILD_OPTIONS. Thanks, Guillem
Bug#913659: Document that not all bugs are policy violations
On Tue, 13 Nov 2018, Ian Jackson wrote: > Package: debian-policy > Version: 4.2.1.4 > > The discussion in #913572 is just another instance of the following > antipattern: > >Submitter: program X does strange thing Y which is undesirable >Maintainer: Y is not against policy > > I suggest adding something like this to s1.1, "Scope", as a new 3rd > paragraph: > > This manual cannot and does not prohibit every possible bug or > undesirable behaviour. The fact that something is not forbidden by > Debian policy does not mean that it is not a bug, let alone that it > is desirable. Questions not covered by policy should be evaluated > on their merits. Seconded. How about also adding one that makes it clear that in *Debian*, policy follows practice, and not the other way around (which should also require seconds just to make sure people agree with this, even if it is a decades-long practice in debian-policy)... -- Henrique Holschuh signature.asc Description: PGP signature
