Bug#1037116: Debian Edu bookworm not ready

[Holger Levsen]

package: release-notes
x-debbugs-cc: debian-...@lists.debian.org

hi,

maybe we should have a release notes entry stating that debian-edu bookworm
is not yet ready?!? :((

https://wiki.debian.org/DebianEdu/Status/Bookworm has the details what
needs doing.


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Stop saying that we are all in the same boat.
We’re all in the same storm. But we’re not all in the same boat.


signature.asc
Description: PGP signature

Bug#963964: release-notes: document aufs removal for bullseye

[Holger Levsen]

On Tue, May 25, 2021 at 09:02:08PM +0200, Paul Gevers wrote:
> This has been pushed.

yay! thank you!


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

People call vaccine mandates "Orwellian" even though Orwell died at 46 of
tuberculosis, which is now preventable with a vaccine.


signature.asc
Description: PGP signature

Bug#963964: release-notes: document aufs removal for bullseye

[Holger Levsen]

package: release-notes
x-debbugs-cc: Timo Weingärtner , Jan Luca Naumann 
, 963...@bugs.debian.org, debian-de...@lists.debian.org

in #963191 on Mon, Jun 29, 2020 at 10:06:33AM +0200, Bastian Blank wrote:
> On Mon, Jun 29, 2020 at 09:32:09AM +0200, Timo Weingärtner wrote:
> > 20.06.20 13:26 Bastian Blank:
> > > Since the kernel supports overlayfs since some time now, what blocks
> > > it's removal?
> > There are Debian installations on filesystems that are incompatible with 
> > overlayfs, for example xfs without d_type.
> > I ran into this while trying to get rid of aufs.
> So we need to document this problem in the release notes.  That's an
> easy task.

filing a bug to make it a bit easier. 


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Re: Bug#928026: release-notes: document the state of security support for golang packages in Buster

[Holger Levsen]

On Fri, Apr 26, 2019 at 10:29:58AM +, Holger Levsen wrote:
> Also, I believe this bug should be cloned and reassigned to
> src:debian-security-support as well, so it's also documented there. Will
> do so once the bug arrives back.

done, #928027 it is.


-- 
tschau,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#928026: release-notes: document the state of security support for golang packages in Buster

[Holger Levsen]

package: release-notes
x-debbugs-cc: j...@inutil.org, elb...@debian.org, t...@security.debian.org, 
release-no...@packages.debian.org, debian-rele...@lists.debian.org

On Sat, Apr 20, 2019 at 11:07:34PM +0200, Moritz Mühlenhoff wrote:
> > Are there other concerns or warnings and
> > should they already be mentioned in the release notes?
> 
> There has been no visible movement on the issues with Go as mentioned in
> https://lists.debian.org/debian-release/2018/07/msg2.html (and
> this dates back much further, initial discussions were from 2016 or
> earlier).
> 
> This is already an issue in Stretch (e.g. #922170), but will be much
> worse in Buster, so unless someone reliably commits to work on
> this ASAP the available options are to drop everything Go apart
> from the toolchain packages from buster or exclude of all that mess
> from security updates so that people know what they can expect.
 
filing a bug (in coordination with Moritz) so this doesnt get forgotten.

Also, I believe this bug should be cloned and reassigned to
src:debian-security-support as well, so it's also documented there. Will
do so once the bug arrives back.


-- 
tschau,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Re: Documenting installer issues for jessie LTS

[Holger Levsen]

Hi,

thanks for your work on documenting how to install jessie these days!

On Sat, Nov 10, 2018 at 10:23:45PM +, Ben Hutchings wrote:
> I assume this is going to appear at
> .  That seems
> a fairly prominent place, though the errata are quite a way down the
> page so may be missed.
 
speaking of stuff which might be missed: 
https://www.debian.org/releases/jessie/debian-installer/ has a prominent
note (marked with a red icon) saying/starting with: "If any of the
hardware in your system requires non-free firmware to be loaded with the
device driver..."

I think it would be great if "Debian 8 has been superseded by Debian 9
("stretch")..." could have such a red warning icon as well!


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#896717: buster release notes: python2 will be EOL upstream by 2020

[Holger Levsen]

package: release-notes
severity: wishlist
x-debbugs-cc: debian-de...@lists.debian.org

On Tue, Apr 24, 2018 at 05:37:00AM +, Niels Thykier wrote:
> Reminder: The release-notes does have a section for "deprecations" (Note
> as I recall, it was empty for stretch, so it is probably not visible there).

thanks for that reminder.

> If there is consensus that buster is the last release to support
> python2, then we can document it in the release-notes.
 
i'm not sure we have consensus that buster is the last release to
support python2, but it's definitly time to have a note there saying
that python2 will be EOL upstream by 2020.


-- 
cheers,
Holger


signature.asc
Description: PGP signature

Bug#863259: document that jessie2stretch upgrades need to involve backports if django is upgraded

[Holger Levsen]

package: release-notes
x-debbugs-cc: codeh...@debian.org, debian-backpo...@lists.debian.org

On Wed, May 24, 2017 at 02:53:00PM +0100, Neil Williams wrote:
[...about python-django]
> Agreed. 1.8 *must* remain available. The only supportable route
> otherwise is to push 1.8 into jessie.
>  
> > Upgrading from 1.7 in Jessie to 1.10 is highly likely to break user
> > code (even if it doesn't break things in the archive).
> 
> 1.8 is a *mandatory* step to get to 1.10 - packages using databases
> *cannot* upgrade from 1.7 to 1.10 or 1.11 without going via a new
> release in backports which requires >= 1.8 and then to 1.10 or 1.11.
> 
> We've had exactly this problem with lava-server.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847277
> 
> Upgrades from developer versions of django *must* go via the
> intermediate django LTS. LTS versions can then upgrade to a developer
> version or to the next LTS.
> 
> This upgrade path is completely broken in django:
> 
> 1.7 -> 1.9 | 1.10 | 1.11
> 
> This upgrade path is required for all packages depending on django in
> jessie:
> 
> 1.7 -> 1.8 -> 1.9 | 1.10 | 1.11
> 
> Critically, at the point where 1.8 is installed a *new upstream
> release* of that dependency needs to be co-installed to use the
> functionality in 1.8 and this upgrade *must* complete before 1.9 or
> later can be installed.
> 
> Debian released jessie with 1.7 and that is the source of all these
> problems. 1.7 is a developer release - it's a bit of a dead end as far
> as upgrades are concerned. 1.7 can only be upgraded to 1.8, no further.
> 1.8 can then be upgraded to the next LTS or developer releases in
> between.
> 
> > Removal would be better.  If we can't fix 1.8, we should just get rid
> > of the backport.
> 
> Removing the django backport forces the removal of the dependencies
> that would be broken by letting in 1.10 so what on earth is gained by
> doing that?
> 
> Policy is not a stick to bash developers or users. 1.8 needs to stay
> available in backports at all costs.
> 
> Anything else makes backports completely unusable. More than that, it
> makes all packages depending on django in *stretch* RC buggy. So
> removing 1.8 from jessie-backports would directly cause the removal of
> dozens of packages from testing and unstable.
> 
> Packages already in jessie-backports *depend* on python-django >= 1.8
> and can no longer work with 1.7.
> 
> Removal of 1.8 is *not* an option at any cost.

If this indeed is the case and stays the case we ought to document this in 
the release notes, to minimize the number of users suffering data loss on a
broken upgrade from jessie to stretch…

(I'm neither convinced this upgrade path is the best we can do nor do
I know anything about the state of django in Debian. So please don't cc:
me, I'm just the clueless messanger trying to make sure this situation
gets at least noted in the release notes.)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#782836: Debian Edu Jessie Beta 1 should be mentioned

[Holger Levsen]

package: release-notes
tags: + patch
x-debbugs-cc: debian-...@lists.debian.org, debian-public...@lists.debian.org

Hi,

please include the following patch to the release-notes. I also assume this is 
a nice information for the planned live-denting...

section id=debian-edu
titleNews from Debian Edu Blend/title
para
The Debian Edu / Skolelinux project is proud to announce the first Beta 
release of Debian Edu based on Debian Jessie. For the first time Debian Edu is 
only made up out of packages from the main Debian archive, thus the Debian Edu 
team was able to drop their own package repository.

Debian Edu provides an out-of-the box environment for a completely configured 
school network. To ease installation and maintainance the comprehensive
ulink url=https://wiki.debian.org/DebianEdu/Documentation/Jessie; Debian 
Edu Jessie manual/ulink has been translated into in seven languages.

An overview of educational software packages included in Debian Edu is 
provided by the ulink url=http://blends.debian.org/edu/tasks;Debian Edu 
task pages/ulink - though any Debian package is just an apt-get install 
away!

Our current plan is to release Debian Edu Jessie with the first Debian Jessie 
pointrelease. Please consider reporting feedback to make this happen!
 /para
 /section


Thanks for maintaining the release-notes!

cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#772963: new release-notes CSS looks really good

[Holger Levsen]

Hi,

I just noticed the new CSS for the release-notes and am very happy how nicely 
it looks now! Kudos and thanks for your work!


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#706610: no migration from isdn4linux to mISDN possible: there is no

[Holger Levsen]

tags 706610 - moreinfo
retitle 706610 no migration from isdn4linux to mISDN possible: there is no 
userland
thanks

Hi,

h01ger GyrosGeier, can you comment and contribute to 706610 (Migration guide 
from isdn4linux to mISDN)?
GyrosGeier [10:31:26] h01ger, ow
GyrosGeier [10:31:37] it has been ages since I did anything ISDN related
GyrosGeier [10:32:48] mISDN has been dropped from Debian because it was so 
buggy
GyrosGeier [10:33:02] (I refused to let it migrate to unstable)
GyrosGeier [10:33:26] so in essence that means someone should revive it
h01ger GyrosGeier, if you could just comment on 706610 that the missing 
userland is indeed a showstopper..
GyrosGeier h01ger, IIRC mISDN would work with just the kernel and something 
like the mISDN asterisk channel
h01ger apt-cache search misdn on wheezy just reveals nothing. so no 
userland i assume
h01ger incl no mISDN asterisk channel
GyrosGeier indeed
h01ger ok, will update the bug accordingly. 
h01ger thanks


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#594135: still useful to upgrade locales first?

[Holger Levsen]

tags 594135 + moreinfo
thanks

Hi,

594135 is about documenting to upgrade the locales packages first, on 
lenny2squeeze upgrades. Am I right to assume this is not needed for wheezy 
upgrades anymore and thus this bug should be closed?


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

reassign, suggestsions for improving 4.6.3

[Holger Levsen]

reassign 655347 release-notes
retitle 655347 improve 4.6.3. of release notes not from end user perspective
thanks


signature.asc
Description: This is a digitally signed message part.

Bug#548336: restart gnome on squeeze2wheezy upgrades?

[Holger Levsen]

Hi,

is it desirable to restart gnome on squeeze2wheezy upgrades, like it was for 
lenny2squeeze upgrades? 

If not, we should close #548336.

Else, we should document this as requested by this bug. Patches welcome.


cheers,
Holger



signature.asc
Description: This is a digitally signed message part.

easy to workaround

[Holger Levsen]

reassign 705452 release-notes
# though maybe better: reassign 705452 xml-core
thanks

Hi,

this problem is rather easy to workaround, this is the code now run on 
jenkins.debian.net after changing sources.lists from squeeze to wheezy:

 apt-get update
+# workaround #705452
+(dpkg -l xml-core  apt-get -y install xml-core) || true
 apt-get -y upgrade
 apt-get -y dist-upgrade
 apt-get -y dist-upgrade

And voila, 
http://jenkins.debian.net/job/chroot-installation_squeeze_install_kde_upgrade_to_wheezy/207
 is the first successful test since April 8th, 208 is the one using the code 
shown above. 
(207 also explicitly installed docbook-xml, but as 208 shows this is not 
needed.)

IOW: if xml-core is installed, one shall upgrade xml-core first, before 
upgrading other packages. And this should be documented.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#610551: munin issues for the release notes

[Holger Levsen]

Hi Osamu,

On Donnerstag, 20. Januar 2011, Osamu Aoki wrote:
 to something along:
 | In most cases, packages should upgrade smoothly between lenny and
 | squeeze. There are a small number of cases where some intervention may
 | be required, either before or during the upgrade; these are detailed
 | below on a per-package basis.
 |
 | If you encounter such cases, please read
 | /usr/share/doc/*/NEWS.Debian.gz of the corresponding package.

I like making this a general statement but I think it would also be good to 
explicitly list the packages where we know this is the case, ie evolution and 
munin.


thanks,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#610551: munin issues for the release notes

[Holger Levsen]

package: release-notes
x-debbugs-cc: mu...@packages.debian.org

Hi,

for squeeze, the default location for the generated web content of munin has 
been changed from /var/www/munin to /var/cache/munin/www and 
therefore /etc/munin/munin.conf needs to be adapted on upgrades, if it has 
been changed by the admin. If you are upgrading, please 
read /usr/share/doc/munin/NEWS.Debian.gz

(Data gathering will continue to work just fine, only the view will not be 
updated.)

I currently dont have time to work on a proper wording for this :(


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#603728: usplash has become obsolete

[Holger Levsen]

Hi,

On Mittwoch, 17. November 2010, Javier Fernandez-Sanguino wrote:
 Now it does, at least in SVN :) See:
 http://svn.debian.org/viewsvn/ddp/manuals/trunk/release-notes/en/upgrading.
dbk?r1=7764r2=7766

thanks, Javier!


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#603728: usplash has become obsolete

[Holger Levsen]

package: release-notes

Hi,

http://www.debian.org/releases/squeeze/i386/release-notes/ch-upgrading.en.html#obsolete
 
doesnt tell that usplash has become obsolete with plymouth as the successor.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#581729: [SQUEEZE] Document the umask change for new installs

[Holger Levsen]

Hi Andrei,

On Samstag, 15. Mai 2010, Andrei Popescu wrote:
 Suggested text:

Thanks for that!

I have one small addition...:

 This change can however create security and/or privacy issues if the
 system administrator is not aware of it and adds users to the private
 group of another user. Also, in order to prevent security issues, some
 software will detect this and refuse to operate when there are other
 members in the user's private group and relevant files have permissions
 as created with a umask of 0002.

This paragraph should be accompanied by something like:

Instead of adding users to other users private groups (which has issues as 
explained above) it is recommend to create dedicated groups for these users 
for collaboration. 



As in: not only describe how not to do it, but also how to do it.

cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#557245: large packages dropped from CDs

[Holger Levsen]

package: release-notes
x-debbugs-cc: debian...@lists.debian.org, debian-de...@lists.debian.org

On Freitag, 20. November 2009, Steve McIntyre wrote:
 For now, I've added a cutoff of 300,000,000 bytes as a maximum package
 size for adding to CDs. That means that the following 3 packages will
 be dropped from the squeeze CD builds:

  306308472 pool/main/o/openarena-data/openarena-data_0.8.1-2_all.deb
  53450 pool/main/v/vtk/vtk-doc_5.2.1-11_all.deb
  793400238 pool/main/n/nexuiz-data/nexuiz-data_2.5.2-1_all.deb

 The debian-cd code will automatically pick up on dependencies too, so
 any packages that *depend* on these will also be dropped.

 For DVD and BD disks we'll accept any size (for now).

 This should also be added to the release notes, please.

On Freitag, 20. November 2009, Frans Pop wrote:
 Would it be possible to generate a list of excluded packages and add that
 as a README on CD1?


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.

Re: Illustrated Guide to Installing Debian GNU/Linux

[Holger Levsen]

Hi Eric,

On Sonntag, 22. Februar 2009, Eric Doviak wrote:
 At Holger's suggestion, I placed the Illustrated Guide to Installing
 Debian on the Debian Wiki[1].
 [1] http://wiki.debian.org/LennyIllustratedInstall

Cool!

 I'm not sure what the next step is here, so please let me know what
 else I can do/should do to help.


I'll blog about it, to make it a bit more known :-)


regards,
Holger




signature.asc
Description: This is a digitally signed message part.

Bug#517828: please document changed mount option for limiting disk usage with vservers

[Holger Levsen]

package: release-notes

Hi,

to use the disk limit feature of vserver (see 
http://linux-vserver.org/Disk_Limits_and_Quota) one had to use the mount 
option tagxid for a partition holding vserver guest filesystems with the 
2.6.18 kernel in etch.

With the 2.6.26 kernel in lenny this option has been renamed to tag. If this 
isn't changed in /etc/fstab manually, the partition won't be mounted and thus 
the vservers wont start.

Please add this to the release notes for 5.0.1. 


Thanks,
Holger


signature.asc
Description: This is a digitally signed message part.

Bug#515526: Whoos with GnuTLS and md5-signed certificates

[Holger Levsen]

package: release-notes
x-debbugs-cc: pkg-gnutls-ma...@lists.alioth.debian.org, 
debian-de...@lists.debian.org, debian-rele...@lists.debian.org

Hi,

On Sonntag, 15. Februar 2009, Daniel Kahn Gillmor wrote:
 I just wrote a blog post trying to outline some concrete steps that
 people (users, developers, maintainers, and sysadmins) can take to deal
 with these changes:
   https://www.debian-administration.org/users/dkg/weblog/42

Thanks!

 Are there any concrete proposals for how to deal with this
 systematically within debian...

The least we can do is report the issue in the release-notes, 
filing a bug now to track that this for lenny.


regards,
Holger

  Are you sure this isn't #514807?
 Also see #514578.


signature.asc
Description: This is a digitally signed message part.

Bug#496815: please mention collab-maint on alioth

[Holger Levsen]

package: developers-reference
severity: wishlist
x-debbugs-cc: [EMAIL PROTECTED]

On Tuesday 26 August 2008 10:28, Lucas Nussbaum wrote:
 Probably not well advertised. developers-reference doesn't mention
 collab-maint anywhere.

 http://wiki.debian.org/Alioth/CollabMaintImport 


regards,
Holger


pgpkcjiB2qbKf.pgp
Description: PGP signature

Bug#474879: please improve documentation on translation updates

[Holger Levsen]

package: developers-reference
severity: wishlist
x-debbugs-cc: Christian Perrier [EMAIL PROTECTED]

Hi,

subject says all I know, Christian asked me to file this bugreport, after
I pestered him with questions on a howto ;-)

Christian, thanks already would be soo wrong :-) Thank you for all your 
continued work on i18n in Debian is more correct!! Very cool  very much 
appreciated. Keep on rocking!


regards,
Holger


pgpxT19fOAnhB.pgp
Description: PGP signature

Bug#403780: Draft release notes and errata for RC1 - please comment

[Holger Levsen]

package: release-notes
severity: wishlist

On Friday 10 November 2006 17:16, Sven Luther wrote:
 We could also mention architecture support changes :

   - PowerPC: dropped support for powerpc/apus.
   - PowerPC: Added support for 64bit PowerPC architectures (IBM pSeries,
 Apple G5 powermacs).
   - PowerPC: not supported : Apple Nubus and IBM pre-power5 Iseries.

 Well, to be complete, one could have the list of supported subarches too :

   - Apple newworld and G5 powermacs
   - IBM CHRP machines (RS6K, pseries, iseries, ...)
   - Genesi CHRP machines (Pegasos, maybe Efika)
   - PReP machines (IBM 43P-140, Motorola PowerStack, ...)


regards,
Holger


pgpKdyJJAKMyC.pgp
Description: PGP signature

Bug#387108: pts keyword summary is not a _planned_ extension anymore

[Holger Levsen]

package: developers-reference
severity: wishlist

Hi,

http://www.debian.org/doc/manuals/developers-reference/ch-resources.en.html#s-pkg-tracking-system
 
or 4.10 The Package Tracking System says summary: (This is a planned 
expansion.) The regular summary emails... while 
http://people.debian.org/~henning/trille/ indicates that summary is indeed 
working.


regards,
Holger


pgpCX2cu5k9dL.pgp
Description: PGP signature

Bug#258437: patch

[Holger Levsen]

Hi,

attached is a patch for the developers reference. Please review and comment on 
it, I'll be happy to fix stuff that's wrong or missing.


regards,
Holger
diff -Nur developers-reference-3.3.7_258437-fixed/common.ent developers-reference-3.3.7/common.ent
--- developers-reference-3.3.7_258437-fixed/common.ent	2006-06-17 15:38:43.0 +
+++ developers-reference-3.3.7/common.ent	2005-12-26 11:13:32.0 +
@@ -67,7 +67,6 @@
 !ENTITY url-cvsweb http://cvs.debian.org/;
 !ENTITY url-devel-machines http://db.debian.org/machines.cgi;
 !ENTITY url-buildd http://buildd.debian.org/;
-!ENTITY url-buildd-doc http://www.debian.org/devel/buildd/;
 !ENTITY url-lintian http://lintian.debian.org/;
 !ENTITY url-debian-qa http://qa.debian.org/;
 !ENTITY url-debian-qa-orphaned http://qa.debian.org/orphaned.html;
diff -Nur developers-reference-3.3.7_258437-fixed/developers-reference.sgml developers-reference-3.3.7/developers-reference.sgml
--- developers-reference-3.3.7_258437-fixed/developers-reference.sgml	2006-06-17 15:38:43.0 +
+++ developers-reference-3.3.7/developers-reference.sgml	2006-04-04 21:41:26.0 +
@@ -1536,7 +1536,7 @@
 that you can do is send a second news item that will deprecate the
 information contained in the previous one.
 
-   sect id=ddpoDeveloper's packages overview
+sect id=ddpoDeveloper's packages overview
 	p
 A QA (quality assurance) web portal is available at url
 id=url-ddpo; which displays a table listing all the packages
@@ -1550,14 +1550,7 @@
 you don't forget any open bug, and so that you don't forget which
 packages are under your responsibility.
 
-sect id=build-infoInformation about the buildd network
-	p
-A package is usually uploaded as a binary package built for one architecture. 
-Once it's moved into the archive it gets build for those architectures which 
-are defined in ttdebian/control/tt. More details about what happens then
-can be found in ref id=buildd.
-  
- sect id=aliothDebian *Forge: Alioth
+sect id=aliothDebian *Forge: Alioth
 	p
 Alioth is a fairly new Debian service, based on a slightly modified version
 of the GForge software (which evolved from SourceForge). This software
@@ -2870,14 +2863,22 @@
 headingpackagebuildd/package/heading
 p
 The packagebuildd/package system is used as a distributed,
-client-server build distribution system, which is described in 
-more detail at url id=url-buildd-doc;.  It is usually used in
+client-server build distribution system.  It is usually used in
 conjunction with emauto-builders/em, which are ``slave'' hosts
 which simply check out and attempt to auto-build packages which need
 to be ported.  There is also an email interface to the system, which
 allows porters to ``check out'' a source package (usually one which
 cannot yet be auto-built) and work on it.
 	  p
+packagebuildd/package is not yet available as a package; however,
+most porting efforts are either using it currently or planning to use
+it in the near future.  The actual automated builder is packaged as
+packagesbuild/package, see its description in ref id=sbuild.
+The complete packagebuildd/package system also collects a number of as yet unpackaged
+components which are currently very useful and in use continually,
+such as prgnandrea/prgn and
+prgnwanna-build/prgn.
+	  p
 Some of the data produced by packagebuildd/package which is
 generally useful to porters is available on the web at url
 id=url-buildd;.  This data includes nightly updated information
@@ -2890,20 +2891,11 @@
 general interest (for instance, a flavor of Debian built with prgngcc/prgn
 bounds checking).  It will also enable Debian to recompile entire
 distributions quickly.
-	  p
+  p
 The buildds admins of each arch can be contacted by the mail address
 [EMAIL PROTECTED]
-	  p
-packagebuildd/package is not yet available as a package; however,
-most porting efforts are either using it currently or planning to use
-it in the near future.  The actual automated builder is packaged as
-packagesbuild/package, see its description in ref id=sbuild.
-The complete packagebuildd/package system also collects a number of as yet unpackaged
-components which are currently very useful and in use continually,
-such as prgnandrea/prgn and
-prgnwanna-build/prgn.
-   sect1 id=packages-arch-specificWhen your package is emnot/em 
-   portable or does emnot/em build
+
+   sect1 id=packages-arch-specificWhen your package is emnot/em portable
p
 Some packages still have issues with building and/or working on some
 of the architectures supported by Debian, and cannot be ported at all,
@@ -2949,34 +2941,7 @@
 If in the past some binary packages were uploaded on unsupported architectures,
 request their removal by filing a bug against
 packageftp.debian.org/package
-	p
-A quick list of what to do if a package doesn't build on a buildd:
-	list
-	item
-	p
-Read the buildd logs, if they are 

Bug#258437: more info

[Holger Levsen]

Hi,

In the list A quick list of what to do if a package doesn't build on a 
buildd: I didn't mention to (to me) useful resources, because they are not 
official, do you think they should be included anyway:

http://people.debian.org/~igloo/
http://buildd.debian.net


regards,
Holger


pgpCfKzC9iBHi.pgp
Description: PGP signature

Bug#258437: correct patch

[Holger Levsen]

Hi,

sorry, this is the right patch. The first one has the order of changes 
reversed, that is added lines have a - and removed lines a +.


regards,
Holger
diff -Nur developers-reference-3.3.7/common.ent developers-reference-3.3.7_258437-fixed/common.ent
--- developers-reference-3.3.7/common.ent	2005-12-26 11:13:32.0 +
+++ developers-reference-3.3.7_258437-fixed/common.ent	2006-06-17 16:24:57.0 +
@@ -67,6 +67,7 @@
 !ENTITY url-cvsweb http://cvs.debian.org/;
 !ENTITY url-devel-machines http://db.debian.org/machines.cgi;
 !ENTITY url-buildd http://buildd.debian.org/;
+!ENTITY url-buildd-doc http://www.debian.org/devel/buildd/;
 !ENTITY url-lintian http://lintian.debian.org/;
 !ENTITY url-debian-qa http://qa.debian.org/;
 !ENTITY url-debian-qa-orphaned http://qa.debian.org/orphaned.html;
diff -Nur developers-reference-3.3.7/developers-reference.sgml developers-reference-3.3.7_258437-fixed/developers-reference.sgml
--- developers-reference-3.3.7/developers-reference.sgml	2006-04-04 21:41:26.0 +
+++ developers-reference-3.3.7_258437-fixed/developers-reference.sgml	2006-06-17 16:27:16.0 +
@@ -1550,7 +1550,14 @@
 you don't forget any open bug, and so that you don't forget which
 packages are under your responsibility.
 
-sect id=aliothDebian *Forge: Alioth
+sect id=build-infoInformation about the buildd network
+	p
+A package is usually uploaded as a binary package built for one architecture. 
+Once it's moved into the archive it gets build for those architectures which 
+are defined in ttdebian/control/tt. More details about what happens then
+can be found in ref id=buildd.
+  
+ sect id=aliothDebian *Forge: Alioth
 	p
 Alioth is a fairly new Debian service, based on a slightly modified version
 of the GForge software (which evolved from SourceForge). This software
@@ -2863,22 +2870,14 @@
 headingpackagebuildd/package/heading
 p
 The packagebuildd/package system is used as a distributed,
-client-server build distribution system.  It is usually used in
+client-server build distribution system, which is described in 
+more detail at url id=url-buildd-doc;.  It is usually used in
 conjunction with emauto-builders/em, which are ``slave'' hosts
 which simply check out and attempt to auto-build packages which need
 to be ported.  There is also an email interface to the system, which
 allows porters to ``check out'' a source package (usually one which
 cannot yet be auto-built) and work on it.
 	  p
-packagebuildd/package is not yet available as a package; however,
-most porting efforts are either using it currently or planning to use
-it in the near future.  The actual automated builder is packaged as
-packagesbuild/package, see its description in ref id=sbuild.
-The complete packagebuildd/package system also collects a number of as yet unpackaged
-components which are currently very useful and in use continually,
-such as prgnandrea/prgn and
-prgnwanna-build/prgn.
-	  p
 Some of the data produced by packagebuildd/package which is
 generally useful to porters is available on the web at url
 id=url-buildd;.  This data includes nightly updated information
@@ -2894,8 +2893,17 @@
   p
 The buildds admins of each arch can be contacted by the mail address
 [EMAIL PROTECTED]
-
-   sect1 id=packages-arch-specificWhen your package is emnot/em portable
+		  p
+packagebuildd/package is not yet available as a package; however,
+most porting efforts are either using it currently or planning to use
+it in the near future.  The actual automated builder is packaged as
+packagesbuild/package, see its description in ref id=sbuild.
+The complete packagebuildd/package system also collects a number of as yet unpackaged
+components which are currently very useful and in use continually,
+such as prgnandrea/prgn and
+prgnwanna-build/prgn.
+   sect1 id=packages-arch-specificWhen your package is emnot/em 
+   portable or does emnot/em build
p
 Some packages still have issues with building and/or working on some
 of the architectures supported by Debian, and cannot be ported at all,
@@ -2941,7 +2949,34 @@
 If in the past some binary packages were uploaded on unsupported architectures,
 request their removal by filing a bug against
 packageftp.debian.org/package
-
+	p
+A quick list of what to do if a package doesn't build on a buildd:
+	list
+	item
+	p
+Read the buildd logs, if they are available at url id=url-buildd; 
+(if there was no build attempt yet, there won't be any logs)
+	p
+	item
+Wait a few days for the build attempt
+	p
+	item
+Check the build statistics at url id=http://buildd.debian.org/stats/;; to see
+if a port is falling behind 
+	p
+	item
+Check if missing build depends are going to be built later
+	p
+	item
+Check if missing build depends are failing to build
+	p
+	item
+Ask in the appropriate port mailing list for help/information
+	p
+	item
+Try to build the package yourself on the arch which is 

Bug#258437: wanna-build info available on http://www.debian.org/devel/buildd/ now

[Holger Levsen]

Hi,

the information Wouter started to collect is now available on 
http://www.debian.org/devel/buildd/

(As part of my NM process Anthony Towns requested me to provide the 
documentation requested in this bug.)

To make the above mentioned URL more visible I suggest to put this information 
in 
http://www.debian.org/doc/manuals/developers-reference/ch-pkgs.en.html#s-porter-automation
 
at section 5.10.3.3 and also to create a new section at the of 
http://www.debian.org/doc/manuals/developers-reference/ch-resources.en.html - 
I would call it 4.12 Information about the buildd network which would just 
be a pointer to 5.10.3.3.

I would also integrate the checklist from the original bugsubmitter into 
section 5.10.4 and rename that to When your package doesn not build or is 
not portable

What do you think? If you think this is a good idea, I'll happily provide a 
patch against the developers-reference source.


regards,
Holger


pgpcjvfoyyLHT.pgp
Description: PGP signature