Bug#990426: www.debian.org: Clarify status of list of old TC decisions
On Thu, 2021-07-08 at 18:08 -0700, Sean Whitton wrote: > Hello, > > On Thu 08 Jul 2021 at 09:12AM +02, Raphael Hertzog wrote: > > > Hi, > > > > On Mon, 28 Jun 2021, Sean Whitton wrote: > > > -NB that decisions from before the 1st of April 2002 are not yet > > > -recorded here. > > > +NB that no decisions from before the 1st of April 2002 are yet > > > recorded > > > +here yet. > > > > That wording doesn't seem correct for me. Maybe: > > « Note that no decisions from before the 1st of April 2002 are > > recorded > > here. » > > or > > « Note that decisions from before the 1st of April 2002 have not been > > recorded here. » > > There should not be two 'yet's, indeed. Thanks. > > > > Formal nontechnical and procedural decisions > > > > > > @@ -337,8 +337,8 @@ recorded here. > > > > > > > > > > > > -NB that decisions from before the 31st of January 2002 are not > > > yet > > > -recorded here. > > > +NB that no decisions from before the 31st of January 2002 are > > > recorded here > > > +yet. > > This one doesn't have the same problem and I think is fine. > I think I understand Raphael's point: the wording felt a bit awkward to me as well on a first read. The "no" should go with the verb, not the subject, and it's a mile away. Plus, I think there's tense weirdness going on with the 'yet' as well: 'yet' indicates past actions, and 'are' indicates the present tense. It should probably be: +NB that all decisions from before the 31st of January 2002 have yet to be recorded here Alternatively, since I think you're trying specifically to remove the "not yet" in the original, try just getting rid of the 'yet': it doesn't add much. +NB that no decisions from before the 31st of January 2002 have been recorded here Or, (and this is the option I personally will be taking), simply ignore this tiny bit of subjectively awkward english, stop being overly pedantic about a tiny phrase that doesn't matter, thank the person adding a much needed note to an out of date page, and take a nap while contemplating the silliness of language. Looking forward to his nap, Calum M signature.asc Description: This is a digitally signed message part
Re: disable wayland
I'm going to try to help you, but I think there are a fair number of misunderstandings on your end. On Wed, 2021-03-24 at 19:08 +0100, Olav Bork wrote: > I have tried to install such simple things like iftop, youtube-dl, > autoremove... Autoremove isn't a package, nor is it an executable. Autoremove is a specific apt subcommand, used to remove out-of-date libraries that are no longer required by any installed packages. > No chance to use Synaptics under Wayland. Synaptic (singular) can be installed and used just fine under wayland. Use sudo apt install synaptic to install this package. > There must be way to stop this stupid Wayland stuff. There is some controversy over Wayland's existence, however, it is not mandatory, nor is it the cause of your problems. > I have tried f.e. > > > # sudo service gdm3 stop (Note that if you type the # on the command line, the command won't run) I appreciate you using 'sudo', however, 'service' is a command used in the now-obsolete SystemV init system. Following a general resolution, Debian has moved to the systemd init system. A modern equivalent would be sudo systemctl stop gdm HOWEVER: That will cause you to stop seeing any graphical applicaitons, which is almost certainly not what you want. > doesn't work > > > # sudo autoremove gdm3 As mentioned earlier, autoremove is not a package or a command. Nor is gdm3. If you want insist on completly uninstalling GNOME, run sudo apt remove gnome-core > the system doesn't know essentiel orders like autoremove. the debian > system 10.7.0 buster is a toy system like wayland. Wayland is not a distribution like Debian. Wayland is a display system that allows graphical applications to be displayed, windows to exist, and similar. Debian can be run without wayland: simply select the KDE or the XFCE desktop environement instead of GNOME during installation. However, Wayland is not at fault for you current problems. The issue appears to be poor and outdated guidance. That is OK and not your fault: the linux world is big and old, and there are many who post guides without understanding them. Many sources that are availible online don't apply to modern Debian, either because they are very old or because they are designed for completly different distributions, such as Red Hat or Arch. For more helpful and accurate guides, see https://www.debian.org/doc/ , in particular the Debian Administrators Handbook (aka the Debian Handbook). For information about Wayland itself, see either the Wikipedia page, or the wayland FAQ here:https://wayland.freedesktop.org/faq.html Lastly, this mailing list is intended for website-related discussion: ie, talking about Debian's internet-facing websites, as opposed to the sofware we distribute. Please send future emails to debian-u...@lists.debian.org, or to #debian-user on the OFTC IRC system. Calum M signature.asc Description: This is a digitally signed message part
Re: https://www.debian.org/mirror/list debian.inode.at 403 Forbidden
On Thu, 2021-03-18 at 10:18 +0100, mx vx wrote: > Hi > > I do not use mobile devices. > > I use the same DSL Line for years. > > In jul 2020 I set up a debian box with: > deb http://debian.inode.at/debian/ bullseye main contrib Having 'contrib' but not 'non-free' isn't an improvement: with only a few exceptions, the 'contrib' section contains packages that depend on those in 'non-free'. That is just a minor and irrelevant quibble: it isn't causing your current problem. > since about march I get this (I tried it today again) > > E: Failed to fetch > http://debian.inode.at/debian/dists/bullseye/InRelease 403 Forbidden > [IP: xx.xx.xx.xx 80] I can confirm that debian.inode.at is giving me a 403 as well. debian.inode.at is not a Debian project website: it appears to be a German internet provider. We have no control over what they do or do not put on their website. If inode.at (or magenta.at) is not your internet service provider, and you don't get discounts for updating from them, I would recommend switching your sources.list to use deb.debian.org. The new file would look like: deb https://deb.debian.org/debian/ bullseye main (I also made a few extra changes. One is using HTTPS, and the other is removing 'contrib'). If you do use them as your service provider, or if you would gain additional charges for potentially international connections, there are a few steps you could take. Firstly, try contacting them. They may have unintentionally stopped their mirror, or have migrated it to somewhere else. If you are a customer of theirs, then you have a decent chance at persuading them to start providing it once more. Second, try finding another German mirror. A list of all such mirrors can be found here: https://www.debian.org/mirror/list Third, you can use deb.debian.org, but minimize the bandwidth usage by also making use of the debdelta package. Debdelta reduces the size of apt updates by only downloading the changes made by an updating package. Install it with sudo apt install debdelta Then use the following commands to upgrade your system: sudo apt update sudo debdelta-upgrade sudo apt upgrade (You would use those commands instead of any graphical software manager, but some software managers may use debdelta if it is present) > E: The repository 'http://debian.inode.at/debian bullseye InRelease' is > not signed. > > I missed the second line: about an unsigned file I guess. > I suppose that is a result of the line above. It is, yes. That error is given whenever the server can be contacted, but the package files in it are not usable. Hope this helps, Calum signature.asc Description: This is a digitally signed message part
Re: https://www.debian.org/mirror/list debian.inode.at 403 Forbidden
> Please note that Debian recommends using the CDN for downloading apt > packages, especially for laptops and other devices that move around. > > https://deb.debian.org/ Is that confirmed? I assume that you would know, but there are many different places where it is stated that you should select a local mirror rather than the CDN, and a large part of the community still holds that belief. I just want to double check before embarking on a quest to change the documentation. signature.asc Description: This is a digitally signed message part
Re: Suggestion
On Fri, 2021-02-19 at 21:42 -0600, Carlos Méndez wrote: > Hello, my name is Carlos Méndez, the reason for this email is not to > report an error, I simply want to suggest a small change in the design > of the main page. > > Exactly in the area that contains the distribution logo and the search > form. > > The vertical size of both elements (the logo and the search form) is not > homogeneous, which breaks the design of the main page a bit. > > My suggestion is to make both elements have a more homogeneous size > (vertically), Resizing the search form using CSS, Optionally, the image > of the logo can be used that distributes the elements horizontally to > take advantage of the space. > > And also optionally the color palette style can be added to the search > form. > > I know that the website development team must be very busy, and I would > like to be able to collaborate to improve the website design. > > I would like to know how I can collaborate in the design of the main > page or another section. > > I have knowledge in HTML, CSS and Javascript. > > I respectfully bid you farewell, and I thank you for taking the time to > read this email. If you're wondering where the website itself is built from, the source is at https://salsa.debian.org/webmaster-team/webwml . It uses a mix of WML and other scripts. WML is a semi-deprecated static site generator, and you probably won't see it in many other places. It's fairly simple to understand: it's syntax is very much HTML based. If you'd like to make contributions to the website, then submitting pull requests to the repositiory is probably the easiest way. signature.asc Description: This is a digitally signed message part
Re: Unable to join the forums.
On Tue, 2021-02-16 at 02:21 +, Paul Wise wrote: > On Mon, Feb 15, 2021 at 7:54 PM User Uber wrote: > > > Incredibly, when I try to register to forum I’m warned that my IP > > address has been used for spamming. > > Which forum are you trying to register to? My guess is the wiki: the message looks like it was fed through Google Translate from Spanish. signature.asc Description: This is a digitally signed message part
Re: broken web page
On Sun, 2021-01-24 at 14:45 -0700, Arv Evans wrote: > https://packages.debian.org/unstable/admin/synaptic.html > > Arv > _._ > Remove the .html from your link, and it should work. Where did you find this address, so we can fix the link? signature.asc Description: This is a digitally signed message part
Re: wiki.debian.org BLOCK
On Thu, 2021-01-14 at 15:16 -0500, a...@abc.com wrote: > When I try to browse wiki.debian.org using the Tor Browser, I get: > 403 forbidden > Forbidden > You are not allowed to access this! > > Why is Debian blocking Tor users? > > -- If you are wondering why a wiki has a blocklist in the first place, it is due to technical limitations is the software (MoinMoin) that is used to run the wiki: there is no way to set an IP-based blocklist that permits banned IP's to read, but not write to the wiki. As such, we have to use the higher-level kludge. signature.asc Description: This is a digitally signed message part
Re: Recent events
On Tue, 2021-01-12 at 08:24 +, David Little wrote: > The developers of Mozzilar Firefox browser has made its bed by siding > with the fascists of Silicon valley Big Tech companies in de-platforming > conservatives and labelling them as right wing supremacists. > Before my company goes forward, I have already closed my Twitter account > Amazon and be closing my Gmail accounts, but I obviously still need > operating systems etc are you siding with Big Tech companies or be > neutral platforms but remove Firefox as the default browser. > > Get Outlook for Android Hi there, Debian does not take political stances, and will likely not change that policy for the current US situation. Additionally, Debian does not have a 'default browser', although we do package Firefox. For reasons related to a lack of volunteer time, Google Chrome is not currently available in Debian: however, that will hopefully be fixed, and we offer many other browsers if you would prefer to avoid any version of Firefox. signature.asc Description: This is a digitally signed message part
Re: CD/FAQ/index
On Sat, 2021-01-09 at 21:32 +0100, The7up wrote: > Hi All! > > Who is responsible for this page (CD/FAQ/index)? Because it is talking > about many CD writer > programs, but not talking about Windows built in, native ISO writing > capability. > > Zibi As you can guess, we don't use Windows especially often, and so often aren't aware of when new changes are made. I have submitted a merge request to fix this at https://salsa.debian.org/webmaster-team/webwml/-/merge_requests/637 signature.asc Description: This is a digitally signed message part
Re: debian
On Sun, 2020-12-06 at 17:43 +, Joshua Hagler wrote: > I have an old 32 bit system on a laptop. Do you happen to have an older > version for that system? As the other respondant noted, that does depend on the system. In general, Debian does have 32-bit support: the archetecture is called i386, and can be downloaded along with other installers at https://www.debian.org/distrib/. signature.asc Description: This is a digitally signed message part
Re: Firefox ESR with NPAPI
First of all, this mailing list is specifically for issues with Debian's website (which this isn't, not really). I reccomend emailing debian-user in the future, as that list is specialized for users of Debian. > could you send me this version of firefox? (firefox-esr_52.8.1esr- > 1_deb8u1_arm64.deb) I always downloaded it from the link below (it was > even saved in my favorites).: > https://packages.debian.org/jessie/arm64/firefox-esr/download > firefox-esr_52.8.1esr-1_deb8u1_arm64.deb It looks like what happened was Jessie got a LTS (long term service) update, which caused them to drop ARM support in Jesse. > However the Url is no longer valid and I don't have any copies of this > package, and I can't find it anywhere on the internet either. I need > this package because it is one of the latest versions that support > NPAPI. If you can make the file available to me, I will save it in the > cloud (so you don't risk losing this rare file). I highly recomend migrating away from NPAPI. It has been deprecated since 2013, and is a significant security risk. However, since you likley can't, you can find old releases of debian on archive.debian.org. In this case, the link "http://archive.debian.org/debian-security/pool/updates/main/f/firefox-esr/"; has the .deb you are looking for. Addtionally, there is a newer version of firefox-esr (still in the 52.x esr branch), 52.9.0. It should still support NPAPI, but it contains several security fixes. That can be found at this link "http://archive.debian.org/debian-security/pool/updates/main/f/firefox-esr/";. > Thanks for the help. No problem. Calum signature.asc Description: This is a digitally signed message part
Re: Why are we blocking some addresses any access to the wiki?
> No one disagrees so I will contact the upstream developers on github > to know if they are interested by such feature. If so, I will try to > implement it. Upstream is currently rewriting moinmoin for python3: however, the new release (moin2) is (in their words) nowhere near production-ready. As such, the version debian uses (and will likely continue to use) is their 1.9 branch: which I believe they have stated is no longer receiving feature updates. Here is their response to an issue I filed asking for a status update on moin2. https://github.com/moinwiki/moin/issues/941 In short, implementing this may require forking from the 1.9 branch. signature.asc Description: This is a digitally signed message part
Re: useful topics and commit messages within git commits on webwml repository
I don’t think you understand the issue. See, when you are making changes to the git repository, you at some point need to commit those changes and send them to other people. Now, you are doing that just fine: but there is one minor issue. When you commit something, it asks for a message. Now the message could be anything: however, the way git is meant to be used treats those messages as little titles. That way, if someone is browsing through the history, they can quickly guess what was done by your commit. However, you are apparently entering the message as “commit”. It’s a bit like titling a file “Essay” or “Document3729”. Yes, it’s valid; but if you are looking through later to find, say, that one file where you wrote down how you fixed the WiFi driver last time it died, you won’t have a great day. What Carsten was asking was if you could enter a more descriptive message. Even if it was, say, “Korean translation fix” for every change, another developer would be able to guess what it was you changed without having to checkout the commit or know that you are the Korean Translation Coordinator. That makes their job much easier if they are, for instance, looking through the history to find the change that broke a feature they use. If they see “commit”, and no context, they will need to spend a few minutes investigating the commit: and that slows them down. TL;DR: Entering a description of the change when git prompts you for a message helps your fellow developers out a lot.
