Re: Wheezy release: CDs are not big enough any more...

[Holger Wansing]

Hi,

Steve McIntyre  wrote:
> Remembering the fun that we had during the Squeeze release with trying
> to make single-CD installations work well, it's time to consider what
> we're going to *claim* to support in Wheezy. We've had a history of
> supporting the following single-CD installations:
> 
>  * Gnome desktop from CD#1
>  * KDE desktop from "KDE CD#1"
>  * XFCE desktop from "light CD#1"
>  * LXDE desktop from "light CD#1"
>  * base system only from netinst CD

FYI: With the alpha1 images, it is not possible, to do an installation
from only one CD image and without internet access, getting an X system
as result.
When using  Alpha1 Binary-CD #1
Alpha1 KDE CD
Alpha1 xfce-lxde CD
and, as said before, having no internet access while installing, you are
only provided the "Standard system tools" task, no "Desktop environment" 
is provided.

See #673200.

If you knew this already, sorry for the noise.


Holger


-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Powered by Sylpheed 3.0.2 under
Debian GNU/ / _  _  _  _  _ __  __
 / /__  / / / \// //_// \ \/ /
// /_/ /_/\/ /___/  /_/\_\6.0 / Squeeze.
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120517224902.9a3a4552.li...@wansing-online.de

salsa.debian.org: merge requests and such

[Holger Wansing]

Hi all,

how is the new Salsa collaborative concept supposed to work with the "old"
workflow in Debian?

Means: it seems to me, that with Salsa there is a second parallel world is
getting evolved (in parallel to the old world: BTS, mailinglists ...), 
containing things like patches in form of merge requests, which do not interact 
well with the old world (BTS, mailinglists).
It looks to me, that many merge requests are lying around on Salsa, but the
responsible package maintainers / teams are not aware of them.

As far as I see it for installer team for example, the debian-boot mailinglist
does not get a mail forwarded, when a installer repo gets a merge request.
Isn't that the way, how it should work?
Comparing Salsa with the BTS, it should work that way IMO.
When writing comments on those merge requests, who gets those messages?
I had the impression that the responsible people are not getting involved.

Or similar seems to be the case for debian-doc, too...

Maybe I'm completely wrong here, or it's just these few packages/teams, where 
this is not optimal?

How is this all set up, how is it supposed to work?


Holger

-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: salsa.debian.org: merge requests and such

[Holger Wansing]

Hi,

Joseph Herlant  wrote:
> Hi,
> 
> > The consensus seems to be that people should enable email notifications in 
> > salsa and open a bug when filing a merge request.
> 
> That's indeed the best way to make the bridge between the BTS and the
> merge requests on Salsa.

Unsure, if this is an acceptable solution:
- since filing such bugreports is a manual step 
- and most Debian volunteers are short on time
this is most likely to not happen very often IMO.
At least there is still a high chance for that merge requests, to rott on 
Salsa for a long time.

Also, that would lead to two different places, where discussions on the
topic might be running, with different audience, which are not aware of
the other site.

And: for small things, that might be not worth a bugreport, one could think
that a merge request at salsa is a suitable way, but if package maintainers
are not aware of it, ...

In summary, this sounds like a semi-optimal solution to me.


Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Please drop anacron from task-desktop

[Holger Wansing]

[ Forwarding this to -devel ]


Hi,

Laurent Bigonville  wrote:
> On Mon, 03 Dec 2018 09:44:05 +0100 Michael Biebl  wrote:
> 
> Hello,
> 
>  >
>  > anacron was added to the desktop-task a long time ago.
>  > The changelog doesn't mention why it was added, but I assume it was to
>  > support systems which are not running 24/7 and to ensure that cron jobs
>  > have a chance to run.
>  >
>  > Nowadays, we have systemd .timer units, which handle this issue much
>  > nicer. I checked a default desktop installation, and all important cron
>  > jobs have a corresponding .timer unit.
>  > It thus seems safe to drop anacron from task-desktop.
>  >
> 
> I'm actually wondering if this is a good idea..
> 
> There are lot of other packages installing cronjobs and people, I would 
> assume, expect that they will run.
> 
> I would personally revert his patch as long as all the cronjobs have not 
> a corresponding systemd .timer

Any thoughts on this?

Is there still a broad necessity for anacron?
Are there still many packages, that don't rely on systemd timer units?


Holger




-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Changing quote signs in GPL allowed? [Was: Bug#929752: installation-guide: left quotes in gpl.xml are not correctly rendered in pdf ]

[Holger Wansing]

[Adding debian-devel for a bigger audience]


Hi,

Holger Wansing  wrote:
> Control: retitle -1 Replace grave accents/single quotes by  in 
> gpl.xml
> 
> Samuel Thibault  wrote:
> > Hello,
> > 
> > Changwoo Ryu, le jeu. 30 mai 2019 22:22:05 +0900, a ecrit:
> > > In en/appendix/gpl.xml, ordinary double quotes (") and grave accent
> > > character (`)
> > > are used for left single/double quotes. But they are not correctly
> > > rendered in pdf.
> > > 
> > > See the English PDF at
> > > https://www.debian.org/releases/stable/amd64/install.pdf.en.
> > > Opening double quotes are rendered as right double quotes. And grave 
> > > accents are
> > > rendered just as grave accents, not a left single quotes.
> > 
> > AIUI we should just replace "" and `' in the xml file with
> > .

I was about to commit these changes, however it came to my mind if such
changes to the GPL are allowed?

At least the English variant of the GPL is 'official' and is not to be
changed, so what about changing the quoting signs into   
entities?


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Bug#929752: Changing quote signs in GPL allowed? [Was: Bug#929752: installation-guide: left quotes in gpl.xml are not correctly rendered in pdf ]

[Holger Wansing]

Control: tags -1 + pending


lsore...@csclub.uwaterloo.ca (Lennart Sorensen) wrote:
> On Tue, Aug 06, 2019 at 08:30:56PM +0200, Holger Wansing wrote:
> > I was about to commit these changes, however it came to my mind if such
> > changes to the GPL are allowed?
> > 
> > At least the English variant of the GPL is 'official' and is not to be
> > changed, so what about changing the quoting signs into   
> > entities?
> 
> gpl.xml isn't official.  It isn't one of the files from the FSF.
> There is a gpl-2.0.dbk[1] version available which in fact does use 
> and  while every other file format uses ` and '.  So at least
> there is precedence for using  tags instead.  After all if you
> decided to use the docbook file as your source text, you would get the
> quotes desired.
> 
> [1] https://www.gnu.org/licenses/old-licenses/gpl-2.0.dbk

Therefore I have committed the changes; tagging this bug as pending.


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: #932957 Please migrate Release Notes to reStructuredText

[Holger Wansing]

[[ debian-devel in CC, to get a wider audience regarding reStructuredText ]]


Hi,

I worked on this recently, and I have something like a prototype ready.
It can be found (as html) at
https://people.debian.org/~holgerw/release-notes_sphinx/
while the git repo containing the migration is at
https://salsa.debian.org/holgerw/release-notes


However, I may have some objections against the migration at all:
as far as I know, sphinx/reStructuredText is still lacking some functionality,
which is heavily used in the release-notes.
That is the use of substitutions within URLs.
In docbook speach these were entities, and you could use them in URLs like this:

Please follow the instructions in the https://www.debian.org/releases/&oldreleasename;/releasenotes";>Release
Notes for &debian; &oldrelease; to upgrade to &debian;
&oldrelease; first if needed.

Please note the &oldreleasename; in the URL!
I could not get this working with sphinx (if someone knows better, please
contact me!)
In sphinx, I used hardcoded codenames like
https://www.debian.org/releases/bullseye/releasenotes instead, which means,
that there is much work to do to make the release-notes fit for the next 
release,
while with docbook you only need to change the entity in one place !!!
In sphinx you need to change every single occurence, and don't forget the 
translations !!!



Beside this, I need help to adapt the buildchain, to get the possibility of
building the release-notes for the different architectures.
I have no python knowledge, so I will most likely not get this running myself.

And the last point is the integration into the debhelper tools: I don't know
if it is required, to have the release-notes fit for building as a whole
package with sbuild or debuild or similar. Salsa tries to build it via CI
at every push, but currently fails.
However, there is no package "release-notes" in the archive, so currently
it is only a matter of building it on wolkenstein for www.debian.org, right?


Regards
Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: #932957 Please migrate Release Notes to reStructuredText

[Holger Wansing]

Hi,

RL  wrote (Sat, 20 May 2023 12:52:25 
+0100):
> Holger Wansing  writes:
> 
> > However, I may have some objections against the migration at all:
> > as far as I know, sphinx/reStructuredText is still lacking some 
> > functionality,
> > which is heavily used in the release-notes.
> > That is the use of substitutions within URLs.
> > In docbook speach these were entities, and you could use them in URLs like 
> > this:
> >
> > Please follow the instructions in the  > 
> > url="https://www.debian.org/releases/&oldreleasename;/releasenotes";>Release
> > Notes for &debian; &oldrelease; to upgrade to &debian;
> > &oldrelease; first if needed.
> >
> > Please note the &oldreleasename; in the URL!
> > I could not get this working with sphinx (if someone knows better, please
> > contact me!)
> 
> No idea about sphinx, but we could we just run a simple sed script to update

That will not work. 
You cannot replace all 'bullseye' by 'bookworm' for example. 
There are places, where the 'bullseye' needs to stay. 
So that needs to be done selective one-by-one.

> i've submitted several patches to release notes, and found the use of
> entities and XML more confusing than helpful (especially '&debian;' for
> 'Debian') - this is meant to be a document for people, and needs a
> decent proof-read anyway.

I dropped that &debian; entity already in Sphinx for the release-notes :-)


Holger




-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Bug#932957: Please migrate Release Notes to reStructuredText

[Holger Wansing]

[[ Replying to two mails in one ]]


Hi,

Holger Wansing  wrote (Sat, 20 May 2023 23:26:47 +0200):
> James Addison  wrote (Fri, 19 May 2023 23:28:55 +0100):
> > > Please note the &oldreleasename; in the URL!
> > > I could not get this working with sphinx (if someone knows better, please
> > > contact me!)
> > 
> > Could the 'extlinks' feature[1] of Sphinx be helpful to migrate those?
> 
> Yes, thanks for the pointer! I used that now to get the manpage links fixed!
> 
> > (it allows defining URL pattern aliases, so for example :oldreleasenotes: 
> > could
> > map to https://www.debian.org/releases/bullseye/releasenotes and 
> > :releasenotes:
> > could map to https://www.debian.org/releases/bookworm/releasenotes for D12)
> > 
> > Parameters are supported too, and that could be useful for 
> > package-or-filepath
> > refs (re: grep -r '`.*<' source |grep -o '' | sort | uniq -c |sort 
> > -n)
> 
> The drawback is, it is not as flexible as the entities in docbook.
> For example, there is the following URL in this manual in docbook:
> 
> &url-debian-mirror-eg;/debian/dists/&releasename;/main/binary-&architecture;/...
> 
> You see, there are three entites in this URL!
> This seems to be not supported by extlinks :-((

I focused a bit too much on the URL front here.
There is also a problem using entities (or now called substitutions) in 
quoted lines like

deb https://deb.debian.org/debian RELEASENAME main contrib

or

# script -t 2>~/upgrade-RELEASENAMEstep.time -a 
~/upgrade-RELEASENAMEstep.script

These also do not work.
That's the biggest blocker in the upgrading chapter IMHO.


> > > Beside this, I need help to adapt the buildchain, to get the possibility 
> > > of
> > > building the release-notes for the different architectures.
> > > I have no python knowledge, so I will most likely not get this running 
> > > myself.
> > 
> > I'll try to take a look into that soon to see what I can find out.  Do you
> > know how the current docbook-based build varies by architecture?
> 
> There are some chapters, which are only visible for specific architectures, 
> like
> in installing.dbk:
> 
>   
> Cloud installations
> 
>   The cloud team publishes
>   Debian &releasename; for several popular cloud computing services
>   including:
> 
> 
> > Perhaps we can borrow some build scripting from developers-reference and/or
> > debian-policy.. but I suppose those don't have per-architecture output.
> 
> I think so, yes. That will be of no help, I fear...
> 
> > > And the last point is the integration into the debhelper tools: I don't 
> > > know
> > > if it is required, to have the release-notes fit for building as a whole
> > > package with sbuild or debuild or similar. Salsa tries to build it via CI
> > > at every push, but currently fails.
> > 
> > It's possible I've misunderstood, but would be the goals here to be to get
> > the release-notes documentation built by CI, and also for it to be 
> > distributed
> > as a Debian package itself?
> > 
> > (someone who knows more may correct me, but I think it would be great to 
> > have
> > the package available for install using apt in addition to the website)
> 
> That was my first thought as well, yes.





Hi,

Holger Wansing  wrote (Sat, 20 May 2023 23:10:59 +0200):
> Hi,
> 
> Richard Lewis  wrote (Fri, 19 May 2023 
> 00:58:26 +0100):
> > On Thu, 18 May 2023 22:39:11 +0200 Holger Wansing  
> > wrote:
> > Unfortunately, my first impression is that it the output has quite a
> > few issues which make it a lot harder to read than
> > the docbook version - which im sure is because it's still only a
> > prototype, but thought it might helpful to list the things that jumped
> > out at me:
> > - It is a lot more cluttered than the docbook version - it feels
> > off-putting and dense to read
> > - it's all a bit 'blue' - i'd suggest red is more on-brand for debian
> > - the "next"/"prev" links at the bottom-right are white on green  ---
> > I totally missed at first, and found hard to read
> 
> I copied style and font settings from developers-reference, another
> document, which has been migrated recently from docbook to sphinx.
> So I consider this as a quasi-standard at the moment.
> I copied it by intent, to get a consistent look for all manuals generated
> with sphinx.
> We can work on that later on, as Laura already pointed o

Re: #932957 Please migrate Release Notes to reStructuredText

[Holger Wansing]

[ Sending this to #932957 as well, as it contains valueable info on that topic ]


Jeremy Stanley  wrote (Wed, 24 May 2023 18:22:09 +):
> On 2023-05-24 19:40:56 +0200 (+0200), Agathe Porte wrote:
> [...]
> > Maybe the idea was to introduce %OLD_RELEASE_NAME% and to call sed to
> > replace this kind of strings in a build step, and not rely on sphinx
> > substitution at all.
> > 
> > I know that I have done this a few times and it works fine as a very
> > simple preprocessor.
> 
> Similar things can be done at sphinx-build time with a custom Sphinx
> extension (can be a trivial Python module). We do that for the
> published security advisories list upstream in OpenStack:
> 
> https://opendev.org/openstack/ossa/src/commit/136b24c/doc/source/conf.py#L31
> 
> https://opendev.org/openstack/ossa/src/commit/136b24c/doc/source/_exts/vmt.py
> 
> That's a more complex example because we generate a ton of content
> out of structured data (YAML) files by splatting the relevant fields
> into substitutions in a Jinja2 template, but for basic string
> substitution you could get away with something far simpler, or even
> use a canned one like (this was simply my first web search result):
> 
> https://pypi.org/project/Sphinx-Substitution-Extensions/
> 
> The examples in its readme look to be along the lines of the Debian
> Release Notes use case anyway. There's also basic substitutions
> support in the reStructuredText specification, which might be useful
> to reduce the amount of actual content you need to swap at build
> time:
> 
> https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#substitution-definitions

The above seem related to the issue in question, but the solution pointed
out by James Addison in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932957#90
(use parsed-literal ('.. parsed-literal::') blocks)
seems to be the easier one (at least for this document) and it works fine
here. So I would go for it.

Thanks anyway

Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Bug#932957: Please migrate Release Notes to reStructuredText

[Holger Wansing]

Hi,

Stéphane Blondon  wrote (Sun, 28 May 2023 13:16:24 
+0200):
> > > Richard Lewis  wrote (Fri, 19 May
> > 2023 00:58:26 +0100):
> >
> > > - are the red hyphens in eg the 'deb...' line near the top of
> > > >
> > https://people.debian.org/~holgerw/release-notes_sphinx/en/html/issues.html
> > > > meant to be red? (maybe it is a syntax error?)
> > >
> 
> 
> 
> Sphinx uses Pygments to highlight source code. I guess no language is
> defined so Sphinx uses a wrong lexer. We should force Sphinx to use
> 'SourceListLexer' with:
> .. code-block :: sources.list

The highlighting feature is great, thanks for pointing this out!
However, we cannot use it here in most cases for sources.list entries,
since resolving substitutions does not work within such lines :-(
like in
   deb https://deb.debian.org/debian |RELEASENAME| main contrib


But in many cases the highlighting gives us a great benefit, so I will
merge your MR and adapt the rare cases, where it does not work.

Thanks again!

Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Teléfono Samsung: no puedo borrar el idioma Alemán

[Holger Wansing]

Could this guy be blacklisted from Debian lists, please?



Am 21. April 2024 22:23:10 MESZ schrieb Jose Luis Alarcon Sanchez 
:
>On abr. 21 2024, at 10:02 pm, José Luis González González
> wrote:
>
>> En mi teléfono móvil Samsung Galaxy A13 no puedo borrar ahora el
>> idioma Alemán del telclado y la corrección ortográfica.
>>  
>
>Y que puede tener esto que ver con Debian o con Linux???. Llévalo a un
>punto de Servicio Técnico de Samsung.
>

-- 
Sent from /e/ OS on Fairphone3

Re: Debian Installer Bullseye Alpha 3 release

[Holger Wansing]

Hi,

Karl-Heinz Künzel  wrote:
> Downloaded alpha 3 from official source and put the iso on an USB stick.
> Disconnected all drives on my PC and connected a fresh SSD.
> 
> Ran graphic and standard installer. No fault, no errors.
> 
> After reboot, grub shows up and after count-down I get a black screen.
> 
> I used a clean HDD instead of the SSD. Same result. Removed Hauppauge TV
> vard and add. SATA card. Same result.
> 
> Made a post in German DEBIAN forum, but no one seams to be willing to do
> tests.
> 
> When choosing 'advance options', messages show up, but stops without any
> error message.

Maybe that's an issue of missing firmware for your graphics card.
Installing firmware-misc-nonfree (from non-free) might fix your problem.
(Because it's non-free software, it's not installed by default.)


Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Making Debian available

[Holger Wansing]

Hi,

Alexis Murzeau  wrote:
> 
> Maybe by adding a "Other" link under the big Download link pointing to other 
> places ?
> 
> For example see attachment with "Other architectures and options" linking to:
> https://www.debian.org/distrib/
> 
> And maybe add a link from https://www.debian.org/distrib/ to
> images with non-free firmwares

+1

By adding a hint/warning like that one we have at
https://www.debian.org/releases/buster/debian-installer/
for example.


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Making Debian available

[Holger Wansing]

[ Adding debian-www to the loop ]

Hi,

Marc Haber  wrote:
> On Sun, 17 Jan 2021 01:53:24 +, Paul Wise  wrote:
> >On Sat, Jan 16, 2021 at 11:52 PM Russell Stuart wrote:
> >
> >> Testing doesn't produce netinst with non-free firmware
> >
> >There are both daily and weekly testing netinsts with firmware:
> >
> >https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/daily-builds/sid_d-i/current/amd64/iso-cd/
> >https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/amd64/iso-cd/
> 
> We should really at least mention them somewhere. We're losing
> installations each day because they are so hard to find.

So, to turn this discussion into a real change:

debian-www team: what do you think about adding some more hint/warning
banners pointing to firmware-including installation images?

We already have one at 
https://www.debian.org/releases/stable/debian-installer/

So we could also add it to other pages (and re-use the translations as well):
https://www.debian.org/distrib/
https://www.debian.org/distrib/netinst
https://www.debian.org/CD/http-ftp/
https://www.debian.org/CD/torrent-cd/

Of course it's not optimal to be forced to add it to so many pages,
but the restructuring of the download / "getting-debian" section is 
already on the agenda, so in the long term we can hopefully reduce the amount 
of pages with that warning back to a low number like 2 or 3?

The above is for stable.
We could also do similar for the testing firmware-including images
(that's probably the more important part, since there is no mention of such
images at all on the website).


Should I try to work out a proposal/patch?
Or is there another plan for these issues already?

Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Making Debian available

[Holger Wansing]

Hi,

Timo Lindfors  wrote:
> 
> On Sun, 17 Jan 2021, Marc Haber wrote:
> > Absolutely. The Installation Experience is one of the first contacts
> > with the distribution for most people¹, and since we all know that the
> 
> Yep. I think using the live environment for installation could be more 
> user-friendly as the user is already familiar with how to use e.g. USB drive 
> or 
> browser during the installation if they need to search for help or copy 
> some additional firmware files. The number of people who know how to do 
> this in the current d-i images is much lower since you'd need to use the 
> command-line with a really restricted set of tools.

Hmm, AFAICS the calamares installer does not include functionality to
pull non-free firmware.
At least I cannot see a checkbox or similar, where to activate/deactivate
such feature / where to enable non-free...

Or did I miss something?


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Making Debian available - patch for webwml

[Holger Wansing]

[ Now added debian-boot to CC, since a page included in the attached patch is ]
[ under their responsibility ]



Holger Wansing  wrote:
> [ Adding debian-www to the loop ]
> 
> Hi,
> 
> Marc Haber  wrote:
> > On Sun, 17 Jan 2021 01:53:24 +, Paul Wise  wrote:
> > >On Sat, Jan 16, 2021 at 11:52 PM Russell Stuart wrote:
> > >
> > >> Testing doesn't produce netinst with non-free firmware
> > >
> > >There are both daily and weekly testing netinsts with firmware:
> > >
> > >https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/daily-builds/sid_d-i/current/amd64/iso-cd/
> > >https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/amd64/iso-cd/
> > 
> > We should really at least mention them somewhere. We're losing
> > installations each day because they are so hard to find.
> 
> So, to turn this discussion into a real change:
> 
> debian-www team: what do you think about adding some more hint/warning
> banners pointing to firmware-including installation images?
> 
> We already have one at 
> https://www.debian.org/releases/stable/debian-installer/
> 
> So we could also add it to other pages (and re-use the translations as well):
> https://www.debian.org/distrib/
> https://www.debian.org/distrib/netinst
> https://www.debian.org/CD/http-ftp/
> https://www.debian.org/CD/torrent-cd/
> 
> Of course it's not optimal to be forced to add it to so many pages,
> but the restructuring of the download / "getting-debian" section is 
> already on the agenda, so in the long term we can hopefully reduce the amount 
> of pages with that warning back to a low number like 2 or 3?
> 
> The above is for stable.
> We could also do similar for the testing firmware-including images
> (that's probably the more important part, since there is no mention of such
> images at all on the website).
> 
> 
> Should I try to work out a proposal/patch?

First patch attached.

For an easy overview of how that might look like, I have uploaded some 
patched html pages to people.debian.org:

https://people.debian.org/~holgerw/webwml_non-free-firmware/english/distrib/index.en.html
https://people.debian.org/~holgerw/webwml_non-free-firmware/english/distrib/netinst.en.html
https://people.debian.org/~holgerw/webwml_non-free-firmware/english/CD/http-ftp/index.en.html
https://people.debian.org/~holgerw/webwml_non-free-firmware/english/CD/torrent-cd/index.en.html

https://people.debian.org/~holgerw/webwml_non-free-firmware/english/devel/debian-installer/index.en.html


(relative links inside of debian.org do not work there)


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
diff --git a/english/CD/http-ftp/index.wml b/english/CD/http-ftp/index.wml
index d23e1c87bc8..c535a0dfe07 100644
--- a/english/CD/http-ftp/index.wml
+++ b/english/CD/http-ftp/index.wml
@@ -28,6 +28,9 @@ download:
 
   Official CD/DVD images of the stable release
 
+  Unofficial CD/DVD images for stable with
+  non-free firmware included
+
   https://cdimage.debian.org/cdimage/weekly-builds/";>Official
   CD/DVD images of the testing distribution (regenerated
   weekly)
@@ -104,6 +107,26 @@ walkthrough of the installation process. Other useful documentation includes:
 
 
 
+Unofficial CD/DVD images with non-free firmware included
+
+
+
+If any of the hardware in your system requires non-free firmware to be
+loaded with the device driver, you can use one of the
+https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/buster/current/";>\
+tarballs of common firmware packages or download an unofficial image
+including these non-free firmwares. Instructions how to use the tarballs
+and general information about loading firmware during an installation can
+be found in the Installation Guide.
+
+
+https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/";>unofficial
+installation images for stable with firmware included
+
+
+
+
+
 Registered mirrors of the debian-cd archive
 
 Note that some mirrors are not up to date —
diff --git a/english/CD/torrent-cd/index.wml b/english/CD/torrent-cd/index.wml
index e3e5e260432..78d174ada22 100644
--- a/english/CD/torrent-cd/index.wml
+++ b/english/CD/torrent-cd/index.wml
@@ -74,3 +74,19 @@ walkthrough of the installation process. Other useful documentation includes:
 If you can, please leave your client running after your download is complete,
 to help others download images faster!
 
+
+
+
+If any of the hardware in your system requires non-free firmware to be
+loaded with the device driver, you can use one of the
+https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/buster/current/";>\
+tarballs of common firmware packages or download an unoffici

Re: Making Debian available - patch for webwml v2

[Holger Wansing]

Hi,

Thomas Lange  wrote:
> >>>>> On Mon, 18 Jan 2021 12:37:37 +0100, Holger Wansing 
> >>>>>  said:
> 
> >> debian-www team: what do you think about adding some more hint/warning
> >> banners pointing to firmware-including installation images?
> I really like to have a hint, but warning is a too negative word.
> Having those non-official images can help our users.
> 
> > First patch attached.
> I would use admon-important.png or admon-tip.png, but not admon-warning.png.
> 
> Please let us treat non-free firmware as something positive, that our
> users need for certain hardware and not use FUD when talking about
> non-free firmware.

Sounds good.
I would vote for the 'important' class (the exclamation mark attracts more
attention IMO).

Patch updated.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
diff --git a/english/CD/http-ftp/index.wml b/english/CD/http-ftp/index.wml
index d23e1c87bc8..9006f3e8bc6 100644
--- a/english/CD/http-ftp/index.wml
+++ b/english/CD/http-ftp/index.wml
@@ -28,6 +28,9 @@ download:
 
   Official CD/DVD images of the stable release
 
+  Unofficial CD/DVD images for stable with
+  non-free firmware included
+
   https://cdimage.debian.org/cdimage/weekly-builds/";>Official
   CD/DVD images of the testing distribution (regenerated
   weekly)
@@ -104,6 +107,26 @@ walkthrough of the installation process. Other useful documentation includes:
 
 
 
+Unofficial CD/DVD images with non-free firmware included
+
+
+
+If any of the hardware in your system requires non-free firmware to be
+loaded with the device driver, you can use one of the
+https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/buster/current/";>\
+tarballs of common firmware packages or download an unofficial image
+including these non-free firmwares. Instructions how to use the tarballs
+and general information about loading firmware during an installation can
+be found in the Installation Guide.
+
+
+https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/";>unofficial
+installation images for stable with firmware included
+
+
+
+
+
 Registered mirrors of the debian-cd archive
 
 Note that some mirrors are not up to date —
diff --git a/english/CD/torrent-cd/index.wml b/english/CD/torrent-cd/index.wml
index e3e5e260432..5175bab8734 100644
--- a/english/CD/torrent-cd/index.wml
+++ b/english/CD/torrent-cd/index.wml
@@ -74,3 +74,19 @@ walkthrough of the installation process. Other useful documentation includes:
 If you can, please leave your client running after your download is complete,
 to help others download images faster!
 
+
+
+
+If any of the hardware in your system requires non-free firmware to be
+loaded with the device driver, you can use one of the
+https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/buster/current/";>\
+tarballs of common firmware packages or download an unofficial image
+including these non-free firmwares. Instructions how to use the tarballs
+and general information about loading firmware during an installation can
+be found in the Installation Guide.
+
+
+https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/";>unofficial
+installation images for stable with firmware included
+
+
diff --git a/english/devel/debian-installer/index.wml b/english/devel/debian-installer/index.wml
index ef00806e51c..d531f47b4fa 100644
--- a/english/devel/debian-installer/index.wml
+++ b/english/devel/debian-installer/index.wml
@@ -172,14 +172,28 @@ available version of installer components.
 
 
 
+
 
-If any of the hardware in your system requires firmware to be
+If any of the hardware in your system requires non-free firmware to be
 loaded with the device driver, you can use one of the
 https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/";>\
-tarballs of common firmware packages. Instructions how to use the tarballs
+tarballs of common firmware packages or download an unofficial image
+including these non-free firmwares. Instructions how to use the tarballs
 and general information about loading firmware during an installation can
-be found in the Installation Guide (see Documentation below).
+be found in the https://d-i.debian.org/manual/";>Installation Guide.
 
+
+https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/daily-builds/sid_d-i/current/";>unofficial
+images with firmware included - daily builds
+
+
+https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/";>unofficial
+images with firmware included - weekly builds
+
+
+
+
+
 
 
 Notes
diff --git a/english/distrib/index.wml b/english/distrib/index.wml
index 527725adb23..317409e845d 100644
--- a/english/distrib/index.wml
+++ b/english/distrib/index.wml
@@ -109,3 +109,19 @@ An

Re: Making Debian available

[Holger Wansing]

Am Samstag, 23. Januar 2021 schrieb Emanuele Rocca:
> On 22/01 08:30, Jeremy Stanley wrote:
> > Taking away the choice for users who care about software freedom to
> > opt out of non-free content in the installer and find alternative
> > options would be a loss of freedom, in service of convenience for
> > users who aren't as invested in trying to minimize their use of
> > non-free software.
> 
> Having the option to opt-out firmware during the installation procedure
> seems reasonable to me, and I don't think anyone was suggesting
> otherwise.
> 
> The situation we are in today is very different though: we build a
> Defective by Design image that fails to install Debian on lots
> of computers because it does not include the firmware most WiFi cards need

In any case: if any of these ideas are wished to become reality, I fear 
someone will need to step in into the installer team and do some coding ...


Holger 

-- 
Sent from my Jolla phone
http://www.jolla.com/

Re: Making Debian available

[Holger Wansing]

Hi,

Bjørn Mork  wrote:
> It has been documented in this thread it is possible to install Debian
> on such systems.  But the images which allow this without additional
> steps is well hidden. And the procedure supported the default images is
> so complicated that even expert longtime Debian users have a hard time
> using it.

FYI: we have a chapter in the installation-guide about that:
https://www.debian.org/releases/stable/amd64/ch06s04.en.html


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Making Debian available

[Holger Wansing]

 
> I personally think the main page could have also have a "Other downloads"
> link to one of the more complete download pages (like /distrib), so
> users not familiar with the wiki can find it one click away.
> 
> Maybe I can propose a patch for at least this small link to /distrib

Such link is already there:

"More: Further links to downloads and software"
That gives you a list, and the first entry points to -
ta-da  - distrib/
 
Holger 

-- 
Sent from my Jolla phone
http://www.jolla.com/

Re: Making Debian available

[Holger Wansing]

Hi again,

Am Sonntag, 24. Januar 2021 schrieb Alexis Murzeau: 
> > The installation image remains 100% free.  But at some point the
> > installer asks the user if they wish to add another media containing
> > software.  Users would then be able to put another CD or USB key (for
> > example) containing a bundle of non-free drivers.
> > 
> > Bundles of non-free drivers would be generated regularly and provided on
> > a webpage which clearly indicates the downsides of having non-free
> > software installed.  But it could give a clear tutorial on how to copy
> > the bundle to a USB key and how to tell the debian-installer to use it.
> > 
> 
> In fact, I think this already exists as stated here:
> https://www.debian.org/releases/stable/amd64/ch06s04.en.html
> 
> But the issue is probably just to make it more easy to find for users.

Yes. But another issue is that firmware for video cards is not
installed even it is provided on such stick.
See my proposal from end of december:
https://lists.debian.org/debian-boot/2020/12/msg00160.html


Holger

-- 
Sent from my Jolla phone
http://www.jolla.com/

Re: Making Debian available

[Holger Wansing]

Hi,

Andrei POPESCU  wrote:
> On Lu, 25 ian 21, 19:35:25, Thomas Lange wrote:
> > Another very odd thing I found.
> > 
> > On https://www.debian.org/CD/faq/
> > there's no hint about images including non-free firmware. No hint
> > about firmware at all. And then this FAQ
> > 
> > 
> > Where is the CD image with non-free?
> >   .
> > Sometimes, someone is kind enough to create unofficial non-free CDs. If you 
> > cannot find any links on this website, you can try asking on the debian-cd 
> > mailing list.
> > 
> > 
> > So we do not tell our users that we (the CD team I guess) already
> > create these very usefull images including non-free firmware. And then
> > we tell the users to search the link themselves. Not very friendly.
> 
> As far as I recall that entry refers to CDs with the entire non-free 
> component of the archive, not just firmware packages (which were seldom 
> or even inexistent at the time the FAQ was written).

As it seems, some relicts of this can be found at the end of
./english/CD/http-ftp/index.wml


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Making Debian available - patch for webwml

[Holger Wansing]

Hi,

Holger Wansing  wrote:
> > debian-www team: what do you think about adding some more hint/warning
> > banners pointing to firmware-including installation images?
> > 
> > We already have one at 
> > https://www.debian.org/releases/stable/debian-installer/
> > 
> > So we could also add it to other pages (and re-use the translations as 
> > well):
> > https://www.debian.org/distrib/
> > https://www.debian.org/distrib/netinst
> > https://www.debian.org/CD/http-ftp/
> > https://www.debian.org/CD/torrent-cd/
> > 
> > Of course it's not optimal to be forced to add it to so many pages,
> > but the restructuring of the download / "getting-debian" section is 
> > already on the agenda, so in the long term we can hopefully reduce the 
> > amount 
> > of pages with that warning back to a low number like 2 or 3?
> > 
> > The above is for stable.
> > We could also do similar for the testing firmware-including images
> > (that's probably the more important part, since there is no mention of such
> > images at all on the website).
> > 
> > 
> > Should I try to work out a proposal/patch?
> 
> First patch attached.

FYI: a patch has been applied in the meantime, adding such hint to nearly all
d.o pages, which have links to download images

www.debian.org/CD/http-ftp/
www.debian.org/CD/live/
www.debian.org/CD/netinst/
www.debian.org/CD/torrent-cd/
www.debian.org/distrib/
www.debian.org/distrib/netinst
www.debian.org/releases/bookworm/debian-installer/
www.debian.org/releases/bullseye/debian-installer/
www.debian.org/releases/buster/debian-installer/
www.debian.org/devel/debian-installer/

to make users aware of those images.


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Making Debian available, non-free promotor

[Holger Wansing]

Hi,

Paul Sutton  wrote:
> 
> 
> On 29/01/2021 03:23, Yao Wei wrote:
> > Hi,
> > 
> > Could there be the way that, with installer unable to connect to the
> > internet, it detects the list of missing blobs, and generate a webpage
> > in the thumb drive, and let user plug in another flash drive to download
> > them.
> 
> I agree with this idea, it would be really helpful, in fact the step in 
> the installer that asks for a driver disk could perhaps be removed,  So 
> in terms of extra steps remove one, add this.

Again: a mechanism doing exactly this is already there, and it's documented 
here:
https://www.debian.org/releases/stable/amd64/ch06s04.en.html


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: debian 11 Bullseye RC 1

[Holger Wansing]

Am 29. Mai 2021 18:33:34 MESZ schrieb "Andrew M.A. Cater" :
>Are you using the unoffcial non-free firmware .iso to install from?
>
>Are you installing firmware-amdgpu from the non-free repository if not?

Please note that there is no such package with name
"firmware-amdgpu" !
(You have already been told so in the past.)

It's named "firmware-amd-graphics".

Holger


-- 
Sent from /e/ OS on Fairphone3

Re: BTS not archiving Bcc: mails? [was: Re: inconsistent mailgraph settings]

[Holger Wansing]

Am 23. August 2021 07:19:26 MESZ schrieb Tomas Pospisek :
>
>The thing is, if you close a bug report via `Bcc: 
>-cl...@bugs.debian.org` then the mail that arrives at the 
>BTS does *not* have the -cl...@bugs.debian.org address in 
>the email header but only in the mail envelope - that is, when 
>connecting the sending MTA will tell the BTS MTA "RCPT TO: 
>-cl...@bugs.debian.org"
>and that's it. This will close the bug, but the address 
>-cl...@bugs.debian.org will not be visible in the email 
>that's archived...

Funny, just some minutes before your mail I have filed 
bug #992755 as a place to test and document this
behaviour.

It's indeed as you stated.

Thus, I will reopen and rename that bug accordingly.


Holger


-- 
Sent from /e/ OS on Fairphone3

Re: connman does not respect /etc/network/interfaces when upgrading from buster to bullseye and more general considerations

[Holger Wansing]

Hi,

Andreas Tille  wrote (Thu, 23 Sep 2021 07:20:57 +0200):
> On Wed, Sep 22, 2021 at 10:21:10PM +0200, Ervin Dine wrote:
> > I have not had any problems with conman in my LXDE Debian 11 install
> > but if I may give my suggestion, gnome-network-manager works fine with
> > LXDE and it has more features. Why not bundle that instead of conman?
> > Conman does not even have an icon in the status bar where you can
> > toggle wifi on and off or choose another connection. 

LXDE is one of the light-weighted desktops, and LXDE is not Gnome.
So, if you add gnome-network-manager to the LXDE task, how much of Gnome will
be pulled in via dependencies?
This might be an argument pro connman.

I have just installed an LXDE system to test this, and now adding 
network-manager-gnome, installs 24 new packages, taking 39 MB of additional
disk space, according to the apt-get output (the whole LXDE system having 
3,4 GB of disk space used).

I guess this would be worth it.


What do others think? LXDE people?



> 
> The missing icon in the status bar triggered bug #988696.  I personally
> consider this very unfriendly to new users.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: No network management in LXDE task

[Holger Wansing]

Control: retitle -1 LXDE: Please include a user-friendly network management tool
Control: tags -1 + patch


[ Returning back to #988696 as the correct bug for this issue; dropping 994875 
from CC ]

Jaycee Santos  wrote (Thu, 23 Sep 2021 20:42:05 +):
> On Thursday, September 23rd, 2021 at 1:05 PM, Michael Biebl 
>  wrote:
> > Am 23.09.21 um 21:35 schrieb Jaycee Santos:
> > >  Is there a reason why to choose gnome-network-manager over something like
> > >  nm-tray for LXDE?
> >
> > I think nm-tray (being based on Qt5) is a reasonable choice for LXQT (which 
> > is also Qt5 based). LXDE on the other hand uses GTK, so I think 
> > network-manager-gnome is a better fit there. (both disk footprint and 
> > memory usage wise)
> 
> Ah. My apologies. I thought nm-applet was provided by nm-tray. I was wrong.
> I did not know that nm-applet was part of network-manager-gnome!
> 
> So I agree with network-manager-gnome being a better fit for LXDE.

Regarding LXQT: this DE already installs cmst by default (an Qt based
GUI for connman, which also has a system tray icon), and since there were
no complains so far from LXQT users related to the network management tool 
used, I would not touch LXQT for this.


A patch to address this issue for LXDE is attached.

Holger



diff --git a/debian/changelog b/debian/changelog
index 148cd82d..f4fba03e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,21 +1,22 @@
 tasksel (3.69) UNRELEASED; urgency=medium
 
   * Install CUPS for all *-desktop tasks, now that task-print-service is no
 longer existing. Closes: #993668
+  * Install network-manager-gnome in LXDE environment. Closes: #988696
 
  -- Holger Wansing   Wed, 08 Sep 2021 22:20:05 +0200
 
 tasksel (3.68) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 1f469e86..ec6ced7e 100644
--- a/debian/control
+++ b/debian/control
@@ -208,34 +208,36 @@ Package: task-lxde-desktop
 Architecture: all
 Description: LXDE
  This task package is used to install the Debian desktop, featuring
  the LXDE desktop environment, and with other packages that Debian users
  expect to have available on the desktop.
 Depends: ${misc:Depends},
task-desktop,
lightdm,
lxde,
 Recommends:
lxtask,
lxlauncher,
xsane,
 # libreoffice widgets using just gtk, and also accessibility needs the GTK 
frontend
libreoffice-gtk3,
 # Package management.
synaptic,
+# desktop network setup
+   network-manager-gnome,
 # libreoffice is the best word processor / office suite at the moment
libreoffice-writer,
libreoffice-calc,
libreoffice-impress,
 # make help menu work
libreoffice-help-en-us,
 # make thesaurus work
mythes-en-us,
 # make spellchecker work
hunspell-en-us,
 # make hyphenation work
hyphen-en-us,
 # gui for configuration of the print service
system-config-printer,
 # orca works with lxde, adding accessibility
orca,
 




-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: No network management in LXDE task

[Holger Wansing]

Hi,

Michael Biebl  wrote (Sat, 25 Sep 2021 22:17:48 +0200):
> Am 25.09.21 um 22:05 schrieb Holger Wansing:
> > A patch to address this issue for LXDE is attached.
> 
> 
> So now you have 3 network configuration systems involved:
> 
> - ifupdown, which is still installed by default
> - connman, which is pulled in by the lxde package (via connman-gtk)
> - network-manager(-gnome), which is pulled in via task-lxde-desktop
> 
> that doesn't sound like a good solution.

Hmm, as there are no Conflicts dependencies set for those, I assumed this
is no problem... ?


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Evolution

[Holger Wansing]

Hi,

Am 31. Dezember 2021 15:10:14 MEZ schrieb Devops PK Carlisle LLC 
:
>Just a quick question as to whether Evolution Mail is still
>supported/updated?
>
>Wikipedia and Gnome support pages don't have much information on it.

Looking at the package tracker under
https://tracker.debian.org/pkg/evolution
should give you a bright overview of latest updates.


Holger



-- 
Sent from /e/ OS on Fairphone3

Re: Lucy Wayland - FOSDEM beer night

[Holger Wansing]

Am 5. Februar 2022 11:47:54 MEZ schrieb marku...@net-c.com:
>
>I read the coroner's report published by the Debian community news, Lucy died 
>alone, an unpaid Debian volunteer who was alone working at night, drank too 
>much and fell down the stairs
>
>
>
>Lucy was lying in the morgue while many of us were at the FOSDEM beer night 
>(death: 28 January, beer night 31 January)

Hmm, in march 2019 Debian has announced the loss of Lucy Wayland:
https://www.debian.org/News/2019/20190308.en.html

What's this news now?
Another Debian member with the same name?
Fake news?


Holger



-- 
Sent from /e/ OS on Fairphone3

debian-faq in NEW - or: remove documentation from the archive at all

[Holger Wansing]

Hi all,


debian-faq is waiting in NEW queue for more than 4 months now (upload is
from 23.11.2021), with no visible activity from ftp-masters (and even with no 
message at all!).
I pinged ftp-masters at the end of January, but got no reaction at all.

Again my question, if there is something wrong with this upload or this 
package???

There have been countless NEW processings since then, but this (in my opinion)
uncritical documentation-only package is still waiting.

Any comments on this?

If documentation is that unimportant, we could save a long of work and time,
if we remove all documentation packages from the archive and the website!!!


Holger
(being extremly sad about all this)




Holger Wansing  wrote (Sat, 29 Jan 2022 20:36:19 +0100):
> [Uploader in CC]
> 
> 
> Hi all,
> 
> I would like to see the 11.0 version of debian-faq accepted to unstable.
> 
> Are there any issues with this one?
> 
> Being this purely a documentation-only package, I had naively thought, it's 
> an 
> easy case for going through NEW, but I might be wrong here?
> 
> 
> Thanks for all your work
> Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: debian-faq in NEW - or: remove documentation from the archive at all

[Holger Wansing]

Hi,

Am 6. April 2022 06:40:54 MESZ schrieb "Joost van Baal-Ilić" 
:
>
>Luckily ftp-masters in the mean time did accept the faq upload.  Thanks!

Yes, That's great. Many thanks

Now I can look into activating the new Portuguese translation
on the website (which is one major point in this upload, and indeed the
reason, why this had to go through NEW).


Regards

Holger



-- 
Sent from /e/ OS on Fairphone3

d-i alpha release?

[Holger Wansing]

Hi,

we have less than 5 months until the planned beginning of bookworm's freeze.

What about a d-i alpha/beta release?
(there was no d-i release since the release of bullseye)


Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Fwd: holg...@debian.org Authentication/Restriction

[Holger Wansing]

Just received this.
This is to let others know of such attacks






 Ursprüngliche Nachricht 
Von: "debian.org Service" 
Gesendet: 12. Oktober 2022 18:41:11 MESZ
An: holg...@debian.org
Betreff: holg...@debian.org Authentication/Restriction

[ holg...@debian.org ] Account

Please confirm email account: [ holg...@debian.org  ] ownership to authenticate 
and continue usage. 

Some of your incoming messages have been blocked by debian.org due to 
authentication failure.

Authenticate Your E-mail Account 


Note: Please do not fail to authenticate your email account to avoid further 
email issues.
-- 
Sent from /e/ OS on Fairphone3

ath9k-htc free firmware still an issue in free software distributions

[Holger Wansing]

Hi all,

now that there's massive work on making non-free firmware to work easily in
debian-installer and the distribution, would it be possible, to bring the
topic of ath9k-htc free firmware forward?

There are some longstanding bugreports for this (and related, some in CC); is 
there any chance to get this finally fixed for bookworm?

Wouldn't it be a shame, if non-free firmware works flawlessly, while this
free firmware still stays an issue?



Regards

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Bug#934822: ath9k-htc free firmware still an issue in free software distributions

[Holger Wansing]

Hi,

Am 28. Januar 2023 17:27:28 MEZ schrieb Cyril Brulebois :
>Holger Wansing  (2023-01-28):
>> now that there's massive work on making non-free firmware to work easily
>> in debian-installer and the distribution, would it be possible, to bring
>> the topic of ath9k-htc free firmware forward?
>> 
>> There are some longstanding bugreports for this (and related, some in
>> CC); is there any chance to get this finally fixed for bookworm?
>> 
>> Wouldn't it be a shame, if non-free firmware works flawlessly, while
>> this free firmware still stays an issue?
>
>If you look around in hw-detect or debian-cd repositories, you'll see that
>I'm working on main & non-free & main-non-free-firmware, soon to become
>main & non-free-firmware (once the move is complete). I don't have such
>hardware to confirm what happens at runtime though.

I did not find any mention of ath9k-htc firmware
in the list of packages you identified for this apptoach,
which mad me ask for this.
Sorry for the noise


Holger



-- 
Sent from /e/ OS on Fairphone3

Re: Starting the weekly live images for Bookworm building again

[Holger Wansing]

Hi,

Steve McIntyre  wrote (Tue, 31 Jan 2023 15:36:53 +):
> On Mon, Jan 16, 2023 at 05:35:50PM +0100, Roland Clobus wrote:
> >* localechooser: A minor fix [A3]
> 
> No idea about that, leaving for somebody else.

A (small) change, that we want, I guess, to add Curaçao to Carribean region,
where it belongs, and skip no-longer existing country 'Netherlands Antilles' 
from the list.

Tested on a local build; works as it should.
Thus merged.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Testing of LXDE live image

[Holger Wansing]

Hi,

Steve McIntyre  wrote (Sun, 19 Mar 2023 15:13:47 +):
> So, *builds* work fine but I've not *yet* tested actually
> booting/using one of these images in any way. I've just triggered a
> full build of "testing" live images now, please help test if you can
> once they're in place at [2] in a couple of hours from now.

Wow, that's great news!
Glad, that we seem to get live images for bookworm!
Thanks Roland and Steve!!!


I have started some testing with debian-live-testing-amd64-lxde.iso image
in a VM, and I'm happy to see that it does not look that bad:

- Testing of the menu entries of live-installer boot menu:
Looks good, as far as I tested. 

- Starting the debian-installer from the boot menu:
d-i starts as we know it; after some screens we get the message,
that no kernel modules are found.
Well, that's not a problem of the live system I guess, we know
that the daily/weekly builds tend to get outdated quite fast
sometimes.
I think this will settle down soon, at the latest with the next 
d-i release.

- Start-up the live system (LXDE environment):
Works fine. Good performance! (Well, that depends on hardware,
sure, and LXDE is lightweight, but hey, live system is fast, so what?
Big ups!)

- Testing some applications in the live system, adding a keyboard layout
  for German and switching between English and German; installing additional
  packages within the live system:
All fine.

- Starting the Calamares installer:
Works fine all together.
First got the message, that not enough RAM is available.
Then, installed one more chip into the VM, and here it goes :-)
Installation succeeds, system boots fine!


So, AFAICS: good job guys!!!

Thanks!
Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Debian Daily build installation fails with choosing language..

[Holger Wansing]

Hi,

Steve McIntyre  wrote:
> On Fri, Dec 13, 2019 at 04:19:19PM +0100, André Verwijs wrote:
> >
> >
> >Debian Daily build (2019-12-13 10:46) installation fails with choosing
> >language. (first question). please take a look at it before next build.
> 
> ACK, thanks for reporting. Confirmed here. In the syslog, copied out
> by hand:
> 
> main-menu[247]: WARNING **: Deep recursion configuring package libc6-udeb 
> (dep loop?)
> main-menu[247]: WARNING **: Menu item 'localechooser' failed.
> 
> If I try to save logs, that also fails:
> 
> main-menu[247]: WARNING **: Deep recursion configuring package libcrypt1-udeb 
> (dep loop?)
> main-menu[247]: WARNING **: Menu item 'save-logs' failed.

Based on the daily built netboot mini.iso's from 
https://d-i.debian.org/daily-images/amd64/
it turns out, that until 20191207 everything looks fine, and starting with 
20191208
it fails.

But I wasn't able to find out, what changed in between...

And building the netboot mini.iso image locally here, creates a working
installer. Hmmm


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: PixelPlex listing inquiry (Debian consultants list)

[Holger Wansing]

Hello,

the following mail came to my notice, which showed there is an (old) copy of
the Debian website mirror'd at http://ftp2.pl.vim.org/pub/mirrors/debian-www/
(from 2008 as it seems).
Is there anything that needs to be done (and can be done) about this?
(and maybe more/other mirrors like this?)
On a first glance, visitors may be unable to detect, that it's not the
original site...

(Dejavu: 'uncensored' copy of debian planet comes to mind)


Holger




Date: Mon, 20 Apr 2020 12:16:05 +0300
From: "PixelPlex Inc." 
To: consulta...@debian.org
Subject: PixelPlex listing inquiry


Hello there,

I am writing to introduce our company — PixelPlex — and establish a
relationship with your platform. We would like to be listed on your Debian
consultants page
<http://ftp2.pl.vim.org/pub/mirrors/debian-www/consultants/>. Here is all
the required information about PixelPlex:

*Name*: Alex Dulub

*Company*: PixelPlex

*Address*: 520 West 28th St., Suite 31, New York, NY 10001, United States

*Phone*: + 1-646-490-0772

*Email*: i...@pixelplex.io

*URL*: https://pixelplex.io

*Rates*: Please contact for rates.

Thank you for your time and consideration. Hope to hear from you soon.



Best regards,
PixelPlex Team


email: i...@pixelplex.io
website: pixelplex.io


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Bug#944713: www.debian.org: Developer Locations map empty

[Holger Wansing]

Hi,

Uwe Kleine-König  wrote:
> https://www.debian.org/devel/developers.loc shows a world map without
> the usual markers for the coordinats where DDs live. Also
> https://www.debian.org/devel/developers.coords is empty.

The '6map' cron script at wolkenstein relays on a so-called 'markers' file
under /var/lib/misc/wolkenstein.debian.org/ and this file is empty too:

debwww@wolkenstein:/home/holgerw$ ls -la 
/var/lib/misc/wolkenstein.debian.org/markers 
-rw-r--r-- 1 root root 0 Mai  1 18:06 
/var/lib/misc/wolkenstein.debian.org/markers

Therefore, no DD locations are added to the earth image.

I fail to see where exactly this markers file is populated from.

Any pointers?


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Bug#944713: www.debian.org: Developer Locations map empty

[Holger Wansing]

Hi,

Holger Wansing  wrote:
> Hi,
> 
> Uwe Kleine-König  wrote:
> > https://www.debian.org/devel/developers.loc shows a world map without
> > the usual markers for the coordinats where DDs live. Also
> > https://www.debian.org/devel/developers.coords is empty.
> 
> The '6map' cron script at wolkenstein relays on a so-called 'markers' file
> under /var/lib/misc/wolkenstein.debian.org/ and this file is empty too:
> 
> debwww@wolkenstein:/home/holgerw$ ls -la 
> /var/lib/misc/wolkenstein.debian.org/markers 
> -rw-r--r-- 1 root root 0 Mai  1 18:06 
> /var/lib/misc/wolkenstein.debian.org/markers
> 
> Therefore, no DD locations are added to the earth image.
> 
> I fail to see where exactly this markers file is populated from.
> 
> Any pointers?

Hmm, I found
https://salsa.debian.org/dsa-team/mirror/userdir-ldap/-/blob/master/ud-xearth
Maybe it's related here?
But I can't get any further ...


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Bug#944713: www.debian.org: Developer Locations map empty

[Holger Wansing]

Hi,

Paul Wise  wrote:
> Control: tags -1 + pending
> 
> On Fri, May 1, 2020 at 11:14 PM Holger Wansing wrote:
> 
> > Hmm, I found
> > https://salsa.debian.org/dsa-team/mirror/userdir-ldap/-/blob/master/ud-xearth
> > Maybe it's related here?
> > But I can't get any further ...
> 
> This came up on IRC, I debugged it and fixed it in git. Next time we
> deploy the code it should get fixed on the site automatically.
> 
> https://salsa.debian.org/dsa-team/mirror/userdir-ldap/commit/274133ad8c512553620e6cb363fcb2a419a83cb4

Looks great now. Thanks!


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

gpg: signing failed, permission denied

[Holger Wansing]

Hi,

I am unable to clearsign a file with gpg, always getting
permission denied errors.
However it does not tell me which is the file where permissions
are missing.
I checked all files I am aware of:
- the file to sign, 
- all files in .gnupg and the .gnupg dir itself,

They are all fine.

How can I find out, which file is the problem?
 
Or maybe it is not a file, which makes the error, but a missing
permission for a process or  ?


Holger


-- 
Sent from my Jolla phone
http://www.jolla.com/

Re: gpg: signing failed, permission denied

[Holger Wansing]

Hi,

"W. Martin Borgert"  wrote:
> On 2018-08-09 19:27, Holger Wansing wrote:
> > I am unable to clearsign a file with gpg, always getting
> > permission denied errors.
> 
> Maybe https://bugs.debian.org/836772 or similar?

Yes! That's was exactly the problem: using gpg inside of su -.

Thanks for preventing me from going crazy


Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

changing git tags on the remote repo

[Holger Wansing]

Hi,

I am curious about how to change an already existing git tag afterwards
(means: change the commit it points to).

Locally, I can change an existing tag, and then create it newly.
But I cannot push it to the remote repo (get
"! [rejected]139 -> 139 (already exists) "

There is -f (--force) option to replace an existing tag and locally it seems
to work, since it says 
"Tag '139' updated (was 02108ec)"
but the push to remote repo fails nevertheless.


Any help?

Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: changing git tags on the remote repo

[Holger Wansing]

Hi,

Alf Gaida  wrote:
> git push --tags --force - if one have the needed rights and the remote
> settings allow it.

This goes at least so far, that I get a clear error message:

remote: GitLab: You are not allowed to change existing tags on this project.


Thanks anyway
Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Failed to create sbuild chroot for cross-compiling

[Holger Wansing]

Hi all,

I need to get some debian-installer packages uploaded for s390x and mips.

Since I have no hardware for that archs, I suspect the way to go is to create
a chroot for that archs, right?
My hardware is amd64.

I have a working sbuild chroot for amd64, for creation of that I followed
https://wiki.debian.org/sbuild

Based on this, I tried to create chroots for s390x and mips, too. 
But that fails.

Is there some documentation for this use case?
The manpage of sbuild-createchroot contains commandline examples for several
use cases, but not for cross-compiling.


I used:

sbuild-createchroot --arch=s390x --foreign --include=eatmydata,ccache,gnupg 
unstable /srv/chroot/unstable-s390x-sbuild http://deb.debian.org/debian

and the output ends with:

snip-
I: Please add any additional APT sources to 
/srv/chroot/unstable-s390x-sbuild/etc/apt/sources.list
I: schroot chroot configuration written to 
/etc/schroot/chroot.d/unstable-s390x-sbuild-awxveq.
   +
   |[unstable-s390x-sbuild]
   |description=Debian unstable/s390x autobuilder
   |groups=root,sbuild
   |root-groups=root,sbuild
   |profile=sbuild
   |type=directory
   |directory=/srv/chroot/unstable-s390x-sbuild
   |union-type=overlay
   +
I: Please rename and modify this file as required.
W: The selected architecture and the current architecture do not match
W: (s390x versus amd64).
I: You probably need to add a personality option (see schroot(1)).
I: You may want to report your use case to the sbuild developers so that
I: the appropriate option gets automatically added in the future.

I: sudo chroot configuration linked as /etc/sbuild/chroot/unstable-s390x-sbuild.
/usr/sbin/chroot: der Befehl „/bin/sh“ konnte nicht ausgeführt werden: No such 
file or directory
/usr/sbin/chroot: der Befehl „/bin/sh“ konnte nicht ausgeführt werden: No such 
file or directory
E: Failed to create build directory /build
Failed to set up chroot
E: Error creating chroot session: skipping apt update
I: Successfully set up unstable chroot.
I: Run "sbuild-adduser" to add new sbuild users.
snap--


After that, I execute

/srv/chroot/unstable-s390x-sbuild/debootstrap/debootstrap unstable 
/srv/chroot/unstable-s390x-sbuild/

as documented for sbuild-createchroot's --foreign option. And that finishs 
without error.


However, sbuild cannot create a chroot session, the sbuild command
sbuild --build=s390x --host=amd64 -s -d unstable --source-only-changes 
--run-lintian
fails with

snip
Package: s390-dasd
Version: 0.0.60
Source Version: 0.0.60
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: s390x
Build Type: source,any

E: Failed to execute “/usr/bin/getent”: No such file or directory
sh: 1: cannot create 
/var/run/schroot/mount/unstable-s390x-sbuild-66ca4af6-72c6-4bec-9c69-ae9dd9d3bab0/etc/group:
 Permission denied
E: Failed to create group sbuild
Failed to set up chroot
E: Error creating chroot session: skipping s390-dasd

+--+
| Summary  |
+--+

Build Architecture: s390x
Build Type: source,any
Build-Space: 0
Build-Time: 0
Distribution: unstable
Fail-Stage: create-session
Host Architecture: amd64
Install-Time: 0
Job: /home/holgerw/uploading-d-i/d-i/packages/s390-dasd_0.0.60.dsc
Machine Architecture: amd64
Package: s390-dasd
Package-Time: 0
Source-Version: 0.0.60
Space: 0
Status: failed
Version: 0.0.60

Finished at 2018-08-25T18:24:29Z
Build needed 00:00:00, 0k disk space
E: Error creating chroot session: skipping s390-dasd
-snap-


I fail to see what's wrong.
"Permission denied" points on some lacking permissions. I have added the user
to the sbuild group, as documented on
https://wiki.debian.org/sbuild
And: the sbuild chroot for amd64 works fine for the same user.


Could somebody help me?
Thanks

Holger



-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Failed to create sbuild chroot for cross-compiling

[Holger Wansing]

Hi,

Raphael Hertzog  wrote:
> Hi Holger,
> 
> On Sat, 25 Aug 2018, Holger Wansing wrote:
> > I need to get some debian-installer packages uploaded for s390x and mips.
> 
> FTR, Holger is referring to packages which are built only on those
> architectures (and that can't be built on amd64).
> 
> > Since I have no hardware for that archs, I suspect the way to go is to 
> > create
> > a chroot for that archs, right?
> 
> No. You just have to do a source only upload and let the auto-builder
> take care of actually compiling the packages.
> 
> Use "debuild -S" or "gbp buildpackage -S" and upload the resulting
> *_source.changes.

My intention was indeed, to do a source-only upload. But apparently
sbuild builds the binary package nevertheless, even when told to prepare
for a source-only upload.

So the main point here is: don't use sbuild, it's the wrong tool for this.
Thanks!


Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Failed to create sbuild chroot for cross-compiling

[Holger Wansing]

Hi,

Paul Wise  wrote:
> On Sun, Aug 26, 2018 at 4:12 PM, Holger Wansing wrote:
> 
> > My intention was indeed, to do a source-only upload. But apparently
> > sbuild builds the binary package nevertheless, even when told to prepare
> > for a source-only upload.
> 
> I don't think it is a good idea to upload packages you haven't
> test-built yourself, so this seems like a very good default for sbuild
> to have.

Definitely.

> > So the main point here is: don't use sbuild, it's the wrong tool for this.
> 
> That seems like the wrong conclusion here.

Hmm, now I am confused.
Raphael and you told me to not built the package here locally, but just
do a source-only upload. 
But sbuild does not support this use case.

So I can say, that sbuild is the wrong tool for this, isn't it?

Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Failed to create sbuild chroot for cross-compiling

[Holger Wansing]

Hi,

Raphael Hertzog  wrote:
> Hi,
> 
> On Sun, 26 Aug 2018, Holger Wansing wrote:
> > My intention was indeed, to do a source-only upload. But apparently
> > sbuild builds the binary package nevertheless, even when told to prepare
> > for a source-only upload.
> > 
> > So the main point here is: don't use sbuild, it's the wrong tool for this.
> 
> It might not be very useful to use sbuild to build a source package but it
> should be able to do it with the following options:
> $ sbuild --no-arch-any --no-arch-all --source

I managed to build s390 or mips packages on my amd64 chroot with
$ sbuild --host=s390x -s -d unstable --source-only-changes --run-lintian
(the --host part being documented at https://wiki.debian.org/CrossCompiling).

And according to https://wiki.debian.org/SourceOnlyUpload
source-only uploads are recommended now and are recommended to be done with 
pbuilder or sbuild.

That procedere seems sensible at least for me.


Thanks
Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: Failed to create sbuild chroot for cross-compiling

[Holger Wansing]

Hi,

Am Montag, 27. August 2018 schrieb Johannes Schauer: 
> Quoting Holger Wansing (2018-08-25 20:30:15)
> > The manpage of sbuild-createchroot contains commandline examples for several
> > use cases, but not for cross-compiling.
> 
> yes, because sbuild-createchroot has nothing to do with cross-compiling.
> chroots that you use to compile natively or cross with sbuild are exactly the
> same. That's why creating a chroot for cross compilation is no different from
> creating a chroot for native compilation.
> 
> To cross compile with sbuild, you give it the --build and --host arguments on
> the command line. It will then pick the right chroot for you but that chroot
> does not need to have anything special in it.

Yes, I already found that out in the meantime.
Thanks for clarifying.

Why I made that assumption: when trying to get sbuild
running for cross-compiling, I got error messages, that made
think I would have to create "some special sort of chroot".

And why did I get such errors: I used the options in a incorrect
form: I wanted to build a package for s390x, and therefore used
--build=s390x or  --arch=s390x. Using --host=s390x (which 
would have been correct) did not seemed correct for me and
the manpage does not explain it in detail.

I thought like one would think when it comes to virtual machines:
there the host is the hardware you are running the VM on.
And the virtual OS is the guest.
Porting this logic to sbuild would mean,  --host=amd64 must
be correct (my laptop, the "host",  is amd64)  but it wasn't.

Maybe that could be made clearer in the sbuild manpage?
 
The manpage of sbuild.conf says it clear:
It uses terms like "architecture we are building on" and
"architecture we are building for".


I just added an example for cross-compiling to the wiki page
of sbuild BTW. 


Thanks
Holger 



-- 
Sent from my Jolla phone
http://www.jolla.com/

Re: Failed to create sbuild chroot for cross-compiling

[Holger Wansing]

Am Montag, 27. August 2018 schrieb Sean Whitton:
> Hello,
> 
> On Mon 27 Aug 2018 at 12:52PM +0200, Holger Wansing wrote:
> 
> > And according to https://wiki.debian.org/SourceOnlyUpload
> > source-only uploads are recommended now and are recommended to be done with
> > pbuilder or sbuild.
> 
> I don't think this statement is really true.
> 
> What's recommended is that you do binary builds, before you upload,
> using sbuild or pbuilder.
> 
> Since you're doing that anyway, --source-only-changes is a convenience
> feature to avoid having to run another command to make the
> _source.changes.  There's no advantage to using --source-only-changes
> instead of plain `dpkg-buildpackage'.

Ok guys, in that case someone should overwork that wiki page,
since it says exactly this!!!
I have just quoted what I read there!

/me as new DM getting totally confused with all this,  one person
says something, the other one says exactly the opposite.
Hrrr



-- 
Sent from my Jolla phone
http://www.jolla.com/

Re: Failed to create sbuild chroot for cross-compiling

[Holger Wansing]

Hi,

Paul Wise  wrote:
> On Sun, Aug 26, 2018 at 4:42 PM, Holger Wansing wrote:
> 
> > Raphael and you told me to not built the package here locally, but just
> > do a source-only upload.
> 
> In general, one should build locally and do a source-only upload. This
> is so that you confirm the build works and, by testing it manually,
> that the resulting package works before wasting upload bandwidth and
> buildd time and so that the package is built on the buildds, which
> means it is built in a clean environment (regenerated every few days)
> and that the build log is published on buildd.d.o.
> 
> sbuild supports doing both of these at once with the
> --source-only-changes option or SOURCE_ONLY_CHANGES configuration
> variable.
> 
> > But sbuild does not support this use case.
> 
> sbuild supports this with the option mentioned above, AFAICT the issue
> here is cross-building.
> 
> You appear to have created an s390x chroot rather than an amd64 chroot
> that builds packages for s390x.

Ok, thanks for clarifying.
That was indeed the problem: I mis-used the different architecture options,
as I already answered to Johannes.


Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Re: installation-guide is marked for autoremoval from testing

[Holger Wansing]

Hi,

Debian testing autoremoval watch  wrote:
> installation-guide 20180603 is marked for autoremoval from testing on 
> 2018-10-11
> 
> It is affected by these RC bugs:
> 898665: installation-guide: [installation-guide] change "Alioth" and "svn" to 
> "Salsa" and "git"

we got this note today.

However, the mentioned bug #898665 has been closed with the latest upload
3 days ago.


What can be done about this?

Holger


-- 

Created with Sylpheed 3.5.1 under 
D E B I A N   L I N U X   9   " S T R E T C H " .

Registered Linux User #311290 - https://linuxcounter.net/

Fw: Mail delivery failed: returning message to sender ( cdvendors@d.o )

[Holger Wansing]

Hi,

apparently the two addresses below (spaillard and atterer) are included in
the cdvendors@d.o alias. 
Please remove them, since they are no longer existing. Thanks

I am unsure, who is responsible for this, so sorry for sending this to
debian-devel@l.d.o


Holger



Date: Sun, 21 Oct 2018 08:45:01 +
From: Mail Delivery System 
To: hwans...@mailbox.org
Subject: Mail delivery failed: returning message to sender


This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  spaill...@debian.org
Unrouteable address
  atte...@debian.org
Unrouteable address


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
--- Begin Message ---
Hi,

"submit_cdvendor.pl"  wrote:
> Submission-Type: new
> 
> Vendor name="lavorato IT"
>   url="https://lavorato.wordpress.com/";
>   deburl="https://lavorato.wordpress.com/debian/";
>   contacturl="mailto:lavorat...@gmail.com";
>   country="AR Argentina"
>   contribution="no"
>   ship="no"
>   dvd="yes"
>   architectures="amd64 i386 "
> Comment: Gracias (Thanks!)
> 

Just added to the list. 


Sorry for the long delay

Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

--- End Message ---

debian-www / debian-doc teams no longer responsive [Was: Re: Bad release in install documentation]

[Holger Wansing]

Hi,

Holger Wansing  wrote:
> Hi,
> 
> Holger Wansing  wrote:
> > Hi,
> > 
> > Cyril Brulebois  wrote:
> > > Samuel Thibault  (2016-02-06):
> > > > Hello,
> > > > 
> > > > a a, on Wed 03 Feb 2016 11:03:19 +, wrote:
> > > > > https://www.debian.org/releases/stable/i386/index.html.en. It says in
> > > > > abstract that the documentation is for debian strech and the url says
> > > > > about stable release.
> > > > 
> > > > It's worse than that: it seems it's really the current Stretch
> > > > installation guide which ended up on the website in stable/, I don't
> > > > know why. Www people, any idea?
> > > 
> > > Because 
> > > http://anonscm.debian.org/cgit/debwww/cron.git/tree/lessoften-parts/1installation-guide
> > > 
> > > It would be nice if it could put stuff targetting s(-p-u) under stable, 
> > > and
> > > stuff targetting unstable under testing, but I didn't reach this point of 
> > > my
> > > todo list yet.
> > 
> > For the time being:
> > 
> > Looking at 
> > http://anonscm.debian.org/cgit/debwww/cron.git/commit/lessoften-parts/1installation-guide?id=c8148aba41b484964cb7a627c5c954a19f056d38
> > it seems, we have the same situation again now:
> > 
> > The latest upload of installation-guide was for Stretch (Changelog does
> > not mention that explicitly, but there are several changings effecting
> > Stretch), so that script has to be adapted around that:
> > 
> > all occurences of 'jessie' have to be changed into 'stretch' and
> > all 'wheezy' be changed into 'jessie'.
> > 
> > 
> > Am I correct?
> > If yes, could someone commit that, please !!!
> 
> I have tried to apply this, but I'm lacking proper permissions.
> 
> Anyone?

I have asked for membership in the relevant alioth project "debwww"
~ 10 days ago, but got no answer yet :-((

What can be done about this?

Somebody here, who minds doing the above changing?
(Noone on debian-www objected against this for weeks, so I assume change 
this is the right thing to do, to get the problem solved.)


Holger 


-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

Re: debian-www / debian-doc teams no longer responsive [Was: Re: Bad release in install documentation]

[Holger Wansing]

Hi,

Laura Arjona Reina  wrote:
> I'm in debwww since some days ago and this is one of the things I wanted to 
> look at, but couldn't put time yet.
> I hope I can have a look at it in the following days.
> 

That would be fine indeed.

While I think about, if recruting new people to the team wouldn't make
sense, nevertheless. As said above, debian-www and debian-doc seem not 
very responsive ATM ...


Holger


-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

Re: debian-www / debian-doc teams no longer responsive [Was: Re: Bad release in install documentation]

[Holger Wansing]

Hi,

Rhonda D'Vine  wrote:
> * Holger Wansing  [2016-03-07 10:33:15 CET]:
> > Laura Arjona Reina  wrote:
> > > I'm in debwww since some days ago and this is one of the things I wanted 
> > > to 
> > > look at, but couldn't put time yet.
> > > I hope I can have a look at it in the following days.
> > > 
> > 
> > That would be fine indeed.
> > 
> > While I think about, if recruting new people to the team wouldn't make
> > sense, nevertheless. As said above, debian-www and debian-doc seem not 
> > very responsive ATM ...
> 
>  Personally I wouldn't object to adding you to the team from what I've
> seen from you so far.  You would need to go through NM process
> (non-uploading maybe) for that though because it doesn't make much sense
> to add people to debwww on alioth but actually not being able to deploy
> the changes in the end.  Also adding non DDs to the alioth project would
> require an additional level of checking what got added by a non DD of
> the group before deploying anything while it is a bit more convenient
> (and trust based) so far with respect to expecting that only people are
> able to push there who are also able to deploy it directly.

Ok, thanks for the answer!
Now I have an answer, better than hear nothing.


Holger


-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/

Re: Bits from the Release Team: trixie freeze started

[Holger Wansing]

Am 31. März 2025 11:55:53 MESZ schrieb Joop! <724j...@gmail.com>:
>Hallo Paul,
>
>De unsubsribe werkt niet goed. Ik krijg elke keer nog mailtjes. Hoe kan ik
>mij hier uitschrijven?
>
>Groet
>
>Joop
>
>Op za 29 mrt 2025 om 09:13 schreef Paul Gevers :
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> Hi all,
>>
>> === trixie Transition and Toolchain freeze ===
>>
>> We're pleased to announce that the freeze for Debian 13 'trixie' has
>> begun. On March 15th we stopped accepting transition requests and we are
>> working to complete the transitions in progress. We ask the maintainers
>> of packages that are part of the toolchain to stop uploading those
>> packages [1] without prior approval from us. We remind everybody to stop
>> uploading large or disruptive changes to unstable, from here on
>> experimental is the place to do that.
>>
>> Further details of the freeze are available in the freeze policy [2].
>> The freeze contains 3 more milestones:
>> * 2025-04-15 - Milestone 2 - Soft Freeze
>>no new packages, delayed migration
>> * 2025-05-15 - Milestone 3 - Hard Freeze - key packages and packages
>>without autopkgtests need a manual unblock for migration
>> * TBA- Milestone 4 - Full Freeze
>>all packages need a manual unblock for migration
>>
>> === RC bugs ===
>>
>> The current list of Release Critical bugs for trixie [3] is
>> progressively looking better. Thanks to everybody who is helping
>> out. That said, we're not there yet, ideally the number of RC bugs goes
>> down to zero. And autoremoval has done it's job, there's a large set of
>> packages that are currently *not* in trixie, so this is your last chance
>> to bring them back.
>>
>> Don't forget to organize your bug squashing parties:
>> https://wiki.debian.org/BSP/ There's one planned for the end of April.
>>
>> === release notes ===
>>
>> We like to draw your attention to the release notes. We have hardly
>> received any proposals (or even ideas), don't forget to file things
>> worth mentioning against the release-notes pseudo package in the bts or
>> prepare your MR on salsa [4]. The release notes editors will be helping
>> you to shape the text, so don't be shy and submit those rough ideas
>> already.
>>
>> === testing upgrades ===
>>
>> If you are in the position to already upgrade some hosts from bookworm
>> to trixie, we like to hear from you if you run into issues. If you
>> don't know which package is to blame, please don't be shy and report it
>> against the upgrade-reports pseudo package and people following that
>> package will try and help find the right package (help wanted for the
>> triaging).
>>
>> === your packages ===
>>
>> Please take this opportunity to check packages are in their final shape
>> and stay vigilant for release-critical bugs.
>>
>> On behalf of the Release Team,
>> Paul
>>
>> [1] https://release.debian.org/testing/essential-and-build-essential.txt
>> [2] https://release.debian.org/testing/freeze_policy.html
>> [3] https://udd.debian.org/bugs.cgi
>> [4] https://salsa.debian.org/ddp-team/release-notes/
>>
>>
>>
>> -BEGIN PGP SIGNATURE-
>>
>> iQEzBAEBCgAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmfnqfwACgkQnFyZ6wW9
>> dQo5RQf6AuEPvHQpueKMm9Md+yCQB5BW0LFN8pcZtIHkpeuGKu5K4Dz2rpx983kP
>> FmLU7o3nqxEuuIvc6XQKC/YL7MboY9moGD4fl6ozRvaLOGQRM3KGc0aTuPQG5NWU
>> 4ec7hg+Dp2XZchiAWlas4OnLMsCCqKMFy5ZHY4Wf5fhY4Vln91czmxhdozKrATqb
>> 0FlVZ8+NCqcosjGBpIeRlZO7nyOaNjUMbDQu9zzSONmQmHEXAy1Tkka7M8mhUds1
>> P44wEtv+dAvgXWqkoStz9LJm99WWGZu3bDBXmRxS8HORoHTULd1bR3G3jjji4m82
>> NTQQfZTgL/HoIWZmJVKi4hM3uuMzGA==
>> =TvxU
>> -END PGP SIGNATURE-
>>
>>

-- 
Sent from /e/ OS on Fairphone3

Broken in links in Debian History document - old news removed from www.debian.org

[Holger Wansing]

Helge Kreutzmann  wrote (Thu, 8 May 2025 17:28:59 +):
> Also the Japanese translator found a broken link:
> 
> > About this translation, I found the url on the line # 3498
> > https://www.debian.org/News/2003/20031202
> > the page doesn't exist on the debian.org

H. 
This is not the only broken link! There are 7 more!!!
Search for "debian.org/News" in project-history.en.dbk.

Could someone revert this?
(removing old news from the website and create masses of dead links! )

Do we have a big need for more work? Or why do we create additional work 
this way (fix dead links in documents, wiki etc.) ?


Proposal:
Probably we should also move the Debian History document away as well?
If Debian's history is no longer relevant ...



I think about removing myself from the debian-www team.
Better no longer be part of it, otherwise people might blame me for such 
decisions ... 



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076