Update to gitlab 10.4.0 scheduled for 2018-01-23 21:00 UTC. Release notes: https://about.gitlab.com/2018/01/22/gitlab-10-4-released/

Commit cc40e073 by Julien Cristau

Update a bunch of links for alioth to salsa move, and use https where possible

parent 6d17e75f
......@@ -40,7 +40,7 @@ Ati driver
* _Why is it I’m getting low performances, or even crashes?_ +
Make sure you have installed the
package]. The driver might still be working without the firmware,
but using code paths which aren’t supported as well as the “normal”
......@@ -51,7 +51,7 @@ Intel driver
* _Why isn’t it working?_ +
KMS is mandatory, as documented in its `README.Debian` (view it
http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-intel.git;a=blob;f=debian/README.Debian[git.debian.org]). You
https://salsa.debian.org/xorg-team/driver/xserver-xorg-video-intel/blob/debian-unstable/debian/README.Debian?viewer=simple[salsa.debian.org]). You
probably disabled KMS or didn’t include it in your kernel
configuration if you’re using a custom kernel.
......@@ -59,7 +59,7 @@ Intel driver
Unfortunately, old cards are not very well supported, and you can’t
do much more than switching to a generic driver, like `fbdev` or
`vesa`, as documented in `README.Debian` (view it online:
http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-intel.git;a=blob;f=debian/README.Debian[git.debian.org]). Please
https://salsa.debian.org/xorg-team/driver/xserver-xorg-video-intel/blob/debian-unstable/debian/README.Debian?viewer=simple[salsa.debian.org]). Please
note that you need to disable `KMS` if you want to use the `vesa`
driver. A minimal `xorg.conf` would look like:
......@@ -77,8 +77,7 @@ Nouveau driver
interfaces aren’t stable yet, so the driver has particular
dependencies on the kernel, which are documented in `README.Debian`
(view it online:
http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-nouveau.git;a=blob;f=debian/README.Debian;h=27ced6b1bf5102a5b72525318439efdfb330745d;hb=6c2f12ca18f55b55d49e083d86d87d970ce53a07[for squeeze],
http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-nouveau.git;a=blob;f=debian/README.Debian[for sid]).
......@@ -41,7 +41,7 @@ Get started by installing `mesa-utils`, which contains `glxinfo`.
↪ Yes.
* _Is this the classic or http://en.wikipedia.org/wiki/Gallium3D[Gallium] driver?_
* _Is this the classic or https://en.wikipedia.org/wiki/Gallium3D[Gallium] driver?_
$ glxinfo | grep 'renderer string'
OpenGL renderer string: Mesa DRI Intel(R) 945GM GEM 20100330 DEVELOPMENT
......@@ -11,7 +11,7 @@ Foreword
The Debian wiki also contains an
http://wiki.debian.org/XStrikeForce/InputHotplugGuide[input hotplug guide]
https://wiki.debian.org/XStrikeForce/InputHotplugGuide[input hotplug guide]
which contains some context around X’s input subsystem. The present
document is meant to be an executive summary, and might miss some
bits. (*FIXME:* Merge those bits.)
......@@ -9,7 +9,7 @@ Packaging bugs or upstream bugs?
It’d be nice to get all upstream bugs tagged as such (`upstream` tag),
forwarded upstream (which means the bugzilla instance on
http://bugs.freedesktop.org/ for most packages), and marked as such.
https://bugs.freedesktop.org/ for most packages), and marked as such.
A mail to `control@bugs.debian.org` would look like:
......@@ -19,7 +19,7 @@ forwarded X https://bugs.freedesktop.org/show_bug.cgi?id=Y
Then http://bts-link.alioth.debian.org/[`bts-link`] comes into play
Then https://bts-link.alioth.debian.org/[`bts-link`] comes into play
and helps us tracking upstream status, which is pretty nice to have.
......@@ -33,7 +33,7 @@ that’s `debian-x@lists.debian.org`.
The list of all usertagged bugs can be seen on the following page; the
list of all used usertags is at the bottom, in the form. +
→ http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x%40lists.debian.org
→ https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x%40lists.debian.org
Let’s give some examples:
......@@ -50,8 +50,8 @@ Let’s give some examples:
(_e.g._ security bugs).
Here’s an example of URL, for the last tags: +
→ http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x%40lists.debian.org&tag=squeeze-candidate +
→ http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x%40lists.debian.org&tag=needs-forwarding
→ https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x%40lists.debian.org&tag=squeeze-candidate +
→ https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x%40lists.debian.org&tag=needs-forwarding
By the way one should keep an eye on the list of found/fixed
versions since those bugs are likely marked as resolved (in `unstable`
......@@ -59,7 +59,7 @@ or `experimental`), but might still affect a stable release.
To list the bugs marked `squeeze-candidate` but not
`squeeze-accepted`: +
→ http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x%40lists.debian.org&tag=squeeze-candidate&exclude=tag:squeeze-accepted
→ https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-x%40lists.debian.org&tag=squeeze-candidate&exclude=tag:squeeze-accepted
......@@ -72,11 +72,11 @@ based on usertags as well, but one has to use the package address
than team-specific.
Categories are
http://wiki.debian.org/bugs.debian.org/usertags[documented on the wiki],
https://wiki.debian.org/bugs.debian.org/usertags[documented on the wiki],
and they would probably be welcome in the `intel` and `ati` cases
above, as well as in the “multiple tools in a single bundle”
cases… An example of what we could achieve is the
http://bugs.debian.org/devscripts[devscripts bug page] (it takes
https://bugs.debian.org/devscripts[devscripts bug page] (it takes
some time to load, plenty of bugs).
Needed steps for that to happen:
......@@ -11,8 +11,8 @@ What is xrandr?
`xrandr` is a command-line tool to interact with the X `RandR`
extension [see http://www.x.org/wiki/Projects/XRandR[x.org],
http://en.wikipedia.org/wiki/RandR[wikipedia]], which allows for
extension [see https://www.x.org/wiki/Projects/XRandR[x.org],
https://en.wikipedia.org/wiki/RandR[wikipedia]], which allows for
live (re)configuration of the X server (_i.e._ without restarting it):
It provides automatic discovery of modes (resolutions, refresh rates,
etc.) together with the ability to configure outputs dynamically
......@@ -6,12 +6,12 @@ _The “X Strike Force” takes care of packaging X.Org for Debian._
These documents are shipped in the
metapackage (under `/usr/share/doc/xorg`), starting with
`wheezy`. They are also available online at
http://x.debian.net/[x.debian.net], which is an alias for the
Getting started
......@@ -45,7 +45,7 @@ Feedback
* Sources for these documents are available on
* Patches, suggestions, flames, etc. are welcome, using the
http://lists.debian.org/debian-x/[debian-x] mailing list.
https://lists.debian.org/debian-x/[debian-x] mailing list.
......@@ -8,7 +8,7 @@ Upstream-side: ABI version numbers
The X server defines several
http://en.wikipedia.org/wiki/Application_binary_interface[ABI] version numbers in the
https://en.wikipedia.org/wiki/Application_binary_interface[ABI] version numbers in the
`hw/xfree86/common/xf86Module.h` header, through the
`SET_ABI_VERSION(maj,min)` macro. In this document, the focus is on
......@@ -221,7 +221,7 @@ Some comments:
out-of-tree. The `xsf` sequence is explained in the previous part.
If one needs to build several flavours,
http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-video-fbdev.git;a=blob;f=debian/rules[++fbdev++’s rules file]
https://salsa.debian.org/xorg-team/driver/xserver-xorg-video-fbdev/blob/debian-unstable/debian/rules[++fbdev++'s rules file]
can be used as an example.
......@@ -6,7 +6,7 @@ Cyril Brulebois <kibi@debian.org>
The old documentation is still available on the wiki:
this documentation is just a draft for now.
......@@ -14,11 +14,11 @@ Getting started
Upstream repositories are hosted on
Debian repositories are hosted on
http://git.debian.org/[git.debian.org] under the `pkg-xorg/*`
namespace. Each repository is about a single Debian source package.
https://salsa.debian.org/[salsa.debian.org] under the `xorg-team`
group. Each repository is about a single Debian source package.
We have two types of repositories:
......@@ -29,26 +29,26 @@ We have two types of repositories:
A local git repository can have several remotes. In the context of
Debian packaging, one usually starts by cloning the Debian repository,
so `origin` will likely point to `git.debian.org`. One can use
so `origin` will likely point to `salsa.debian.org`. One can use
`upstream` to point to `anongit.freedesktop.org`. The following
documentation assumes this convention.
The following bits in `~/.gitconfig` will make it possible to fetch
updates using the `git` protocol (anonymously), and to push updates
updates using `https` (anonymously), and to push updates
through `ssh` without having to fiddle with the remote’s URL (in other
words: using `git://git.debian.org` everywhere):
words: using `https://salsa.debian.org` everywhere):
[url "ssh://git.debian.org"]
pushInsteadOf = "git://git.debian.org"
[url "ssh://git@salsa.debian.org"]
pushInsteadOf = "https://salsa.debian.org"
To get the repository from `git.debian.org` one can run `debcheckout
To get the repository from `salsa.debian.org` one can run `debcheckout
$package` (or `debcheckout $package $package.git`), which will use the
`Vcs-Git` fields in the APT cache to pick the appropriate git
location. To add the `upstream` remote (using the info stored in
`debian/watch`), one can use `xsf-remote-add-upstream` script from the
**TODO:** There will be more information about how to deal with the
......@@ -25,7 +25,7 @@ package maintainers.
The usual link:http://backports-master.debian.org/[backports instructions]
The usual link:https://backports.debian.org/[backports instructions]
apply. But let’s gather everything in a single place.
Add that to your `sources.list`:
......@@ -10,7 +10,7 @@ Getting announcements
* Almost everything: `xorg-announce@lists.freedesktop.org`
* Mesa: `mesa-announce@lists.freedesktop.org`
_(Source: http://wiki.x.org/wiki/XorgMailingLists[XorgMailingLists])_
_(Source: https://wiki.x.org/wiki/XorgMailingLists[XorgMailingLists])_
Developer lists
......@@ -20,18 +20,18 @@ Developer lists
Almost everything:
* `xorg-devel@lists.freedesktop.org` — doc:
— module maintainers:
* ATI: `xorg-driver-ati@lists.x.org`
* Intel: `intel-gfx@lists.freedesktop.org` — doc:
http://intellinuxgraphics.org/how_to_report_bug.html[How to file a good bug report]
[https://01.org/linuxgraphics/documentation/how-report-bugs][How to file a good bug report]
* Nouveau: `nouveau@lists.freedesktop.org`
* VMMouse & VMWare: `thellstrom@vmware.com` — source:
http://wiki.x.org/wiki/vmware[vmware wikipage]
https://wiki.x.org/wiki/vmware[vmware wikipage]
......@@ -41,6 +41,6 @@ Other:
* Wayland: `wayland-devel@lists.freedesktop.org`
* XCB: `xcb@lists.freedesktop.org`
* XKeyboardConfig/xkb-data: `xkb@listserv.bat.ru` — source:
_(Source: http://wiki.x.org/wiki/XorgMailingLists[XorgMailingLists])_
_(Source: https://wiki.x.org/wiki/XorgMailingLists[XorgMailingLists])_
......@@ -11,7 +11,7 @@ Multitouch/touchpads
Touchpad features, by Peter Hutterer: +
→ http://who-t.blogspot.com/2010/06/incomplete-roundup-of-touchpad-features.html
→ https://who-t.blogspot.com/2010/06/incomplete-roundup-of-touchpad-features.html
What multitouch really is about, by Peter Hutterer: +
→ http://who-t.blogspot.com/2010/10/thoughts-on-linux-multitouch.html
→ https://who-t.blogspot.com/2010/10/thoughts-on-linux-multitouch.html
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment