Package: wnpp
Severity: wishlist
Owner: Otto Kekäläinen
* Package name: glow
Version : 1.2.0-1
Upstream Author : Charm
* URL : https://github.com/charmbracelet/glow
* License : Expat
Programming Lang: Go
Description : Render Markdown on the CLI
Glow
Package: wnpp
Severity: wishlist
Owner: Otto Kekäläinen
* Package name: golang-github-muesli-mango-pflag
Version : 0.1.0-1
Upstream Author : Christian Muehlhaeuser
* URL : https://github.com/muesli/mango-pflag
* License : Expat
Programming Lang: Go
Package: wnpp
Severity: wishlist
Owner: Otto Kekäläinen
* Package name: golang-github-muesli-mango-cobra
Version : 1.2.0-1
Upstream Author : Christian Muehlhaeuser
* URL : https://github.com/muesli/mango-cobra
* License : Expat
Programming Lang: Go
u might want to take a peek at the source code of
https://salsa.debian.org/otto/debcraft how it supports both Podman and
Docker, and how it generates the 'root.tar.gz' equivalent container
automatically based on debian/control and debian/changelog contents,
and then runs the actual build as
Enriching original email:
This is about whether packages transmission-gtk should use embedded copy of
libb64 or depend on the outdated Debian package libb64.
Upstream for libb64 seems dead and transmission devs have improved their
embedded/vendored copy of libb64.
Direct link: https://bugs.debia
Hi!
> https://mentors.debian.net/package/uriparser/
> https://mentors.debian.net/package/mailgraph/
This is the same maintainer, I can take this on.
> https://mentors.debian.net/package/selint/
I have worked with this maintainer before, I can help him now too.
After this Hexwalk still needs a
Hi!
On Thu, 4 Jul 2024 at 13:32, Debian Project Secretary - Kurt Roeckx
wrote:
> A general resolution about tag2upload has been started. Details are at:
> https://www.debian.org/vote/2024/vote_002
This GR was published without much context. I at least was much more
enlightened after reading the
makes sense, please press the thumbs up button.
If you have comments, please share them here or on the draft itself.
Thanks,
Otto
Hi!
> > I have drafted a new DEP at
> > https://salsa.debian.org/dep-team/deps/-/merge_requests/8 titled "DEP-18:
> > Enable true open collaboration on all Debian packages".
> >
> > Direct link to raw text:
> > https://salsa.debian.org/dep-team/deps/-/raw/798bfa5a1e1609afd4e48ee20aff80a82bcd4a2f/w
o reword "5. Allow changes to be reviewed before uploads
to Debian" to be explicit about not prescribing anything too specific.
It is up to each team and maintainer to decide what and when to ask
for reviews. The main point in DEP-18 is that when you use
salsa.debian.org, the code is published as source first, tested with
Salsa CI and potentially reviewed instead of just being uploaded
directly without any room for collaboration.
- Otto
Hi!
On Fri, 2 Aug 2024 at 02:27, Andrea Pappacoda wrote:
..
> Before a certain way of doing things can be mandated or "warmly
> recommended", the technology has to be as flawless as possible - and
> today I wouldn't call Salsa "flawless", would you? Issues with
> Salsa/GitLab:
>
> 1. It is so slo
Hi,
On Fri, 2 Aug 2024 at 16:27, Johannes Schauer Marin Rodrigues
wrote:
> Quoting Otto Kekäläinen (2024-08-02 17:23:51)
> > I agree that Salsa is sometimes a bit sluggish
> > (https://salsa.debian.org/salsa/support/-/issues/395),
>
> what kind of hardware do you have? For p
Hi!
> I have three feelings.
>
>
> 1. Debian workflows are too fractured. The project would be better if we
> asked people to standardize around a single (or a small number) of workflows.
> To do so, the workflow would need to be flexible enough to handle the wide
> range of technical needs
Hi!
On Fri, 9 Aug 2024 at 04:12, Nicolas Peugnet wrote:
> > If there is interest in providing a page that only list the tag
> > description (without the affected packages), it would be easier to add
> > it to the existing UDD page (with an additional parameter for example)
> > than to create a se
u probably guessed, I am a heavy user of Salsa, and very grateful
to Salsa admin for maintaining it!
- Otto
Yes to finalizing DEP-14 soon, but first I think we need to complete the
technical work to have git-buildpackage use DEP-14 branch names by default.
I tried implementing it but turned out a bit too involved..
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829444
Use DEP14 branch layout by defa
ad all of them to do stats on what they contain.
- Otto
Hi!
## How many source packages are in Debian unstable as of today?
± zgrep "^Package: " Sources.gz | wc -l
38199
## How many source packages have a gbp.conf?
± ls -1 *_gbp.conf | wc -l
13570
(24629 do not have it)
## What is the most popular 'debian-branch'?
Note! The Sources.gz used to anal
Hi!
In short:
I would very much like to see all top-150 packages run Salsa CI at
least once before being uploaded to unstable. What people think is a
reasonable way to proceed to reach this goal?
Background:
We have had several cases recently where an upload to Debian unstable
causes widespread
Hi!
> > I would very much like to see all top-150 packages run Salsa CI at
> > least once before being uploaded to unstable. What people think is a
> > reasonable way to proceed to reach this goal?
> Advertise widely and frequently that there is a pool of people which is
> happy to help investigat
nding a working pipeline configuration for these
> could improve the situation. Would it also make sense to source
I have done that - details visible in my MR history at
https://salsa.debian.org/dashboard/merge_requests?scope=all&state=all&author_username=otto&search=%22enable+sa
Hi!
> And is this web page authoratative? Or just a false search positive?
>
> https://salsa.debian.org/salsa-ci-team/pipeline#basic-use
>
> It doesn't mention the "salsa" command at all, but maybe that isn't
> the right web page. This goes back to my observation that it would be
> helpful i
Hi Helmut!
> > Let me suggest that there are more ways to do this. Freexian is putting
> > a ton of effort into https://debusine.debian.net. It can do much of the
> > same tasks as salsa-ci already (with less flexibility). Extending it to
> > act as an upload-proxy that forwards your upload to the
On Tue, 2 Apr 2024 at 17:19, Jeremy Stanley wrote:
> On 2024-04-02 16:44:54 -0700 (-0700), Russ Allbery wrote:
> [...]
> > I think a shallow clone of depth 1 is sufficient, although that's not
> > sufficient to get the correct version number from Git in all cases.
> [...]
>
> Some tools (python3-re
some kind of formal
sign-offs from at least two people before upload. Initially, perhaps
only for the top-150 packages. But before we can institute review
workflows, we need to have more unification around the version control
and basic packaging workflows.
- Otto
hauer
Marin Rodrigues, Andrea Pappacoda, and Gioele Barabucci, complained
about Salsa/GitLab being slow or unreliable at times, which deterred
contribution. Improvements to performance and uptime were seen as
important. In response, Otto Kekäläinen noted that the Salsa admins
had posted about upcoming
Hi!
> NOTE: The following idea might be out-of-scope in DEP-18, but specific
> use-case to improve
> collaboration in Debian, IMHO.
>
> Here is just an idea: put collaboration policy metadata in debian/control.
> (The following idea assumes that non-maintainer DD tend to hesitate to
> commit/merge
e proposal. I will notify when
published.
- Otto
Lab CI pipeline and do occasional
code reviews, if you want to consider hosting the code at
https://salsa.debian.org/lintian, Debian's official code hosting and
collaboration platform. It can be instead of or in parallel with your
GitHub repository.
- Otto
Hi!
> Hi Otto,
> Until recently I generally found Salsa response to be adequate,
> but for the last couple of days it has been so
> excruciatingly slow as to be almost unusable.
>
> > In response, Otto Kekäläinen noted that the Salsa admins
> > had posted about upc
, in particular in this case as it is a legit and working
implementation to produce renewed contents for lintian.debian.org.
- Otto
> On Wed, 29 Sep 2004, Pedro Larroy wrote:
>
> As a long standing debmirror user and with the knowledge that there is a
> debpartial-mirror project which is very actively developed I just wonder
> if people have to much spare time to invent one wheel after an other.
>
Sorry for the late reply but
> > Can anyone explain why rsync is no longer considered an appropriate
> > method for fetching Packages files?
>
> IIRC the problem is that rsync is quite CPU-heavy on the servers, so while
> the mirrors have the (network) resources to feed downloads to 100s of
> users, they don't have the (CPU)
> > > IIRC the problem is that rsync is quite CPU-heavy on the servers, so while
> > > the mirrors have the (network) resources to feed downloads to 100s of
> > > users, they don't have the (CPU) resources for a few dozen rsyncs.
> >
> > Why do you keep on saying this without providing _any_ figur
Tim Cutts <[EMAIL PROTECTED]> wrote:
> > Seriously. There's just no way you're going to change the way Debian
> > makes releases, or rather, doesn't. It's too big, and there are just
> > too damn many people involved, many of whom simply don't care about
> > releases. As long as we maintain our cu
Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
> > Sure? Anyway DpartialMirror "http://dpartialmirror.sourceforge.net/";
> > can.
> >
> A note of caution:
>
> | 2004-04-03 (wyo) Since Debian does not change its policy to add
> | adequate support for rsync'ing package mirrors, I don't actively
>
Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Otto Wyss) writes:
>
> > Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
> >
> >> > Sure? Anyway DpartialMirror "http://dpartialmirror.sourceforge.net/";
> >> > c
Goswin von Brederlow wrote:
>
> > Why there isn't there already a rsync method for apt is probably a
> > mystery nobody ever will solve.
>
> It is not wanted due to rsync causing excessive server load.
>
That is simply not true. This statement is repeated all the time but
nobody ever was able to
Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
> Otto Wyss <[EMAIL PROTECTED]> writes:
>
> reply (that is what I get roughly) to the server would waste 75 hours
> on waiting for the initial three-way handshake for a connect. And
> another 50 hours for the round-robin
Sorry if I ask here but nobody in debia-users seems to know an answer.
During installation of console-tools a few weeks ago I lost the keymap
of my swiss-german keyboard in the console. As typical console-tools
doesn't have a man page and it's documentation is useless.
Does anybody know how to re
> Tried to work around this with a simple script that merges my
> packages into the local mirror and regenerates everything as
> needed. But sadly this doesn't seem to be perfect :-( The installer
> just doesn't want to get some of these packages, even if the md5's
> are correct. Switching from htt
Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
> Debmirror is purely a mirror tool. It will download the Meta files
> just like any other file.
>
> You can easily switch between mirror of equal contents but not create
> Packages files reflecting what is locally available.
>
Sure? Anyway Dpartia
Since around last October, I've considered to make my concept for a
modern package distribution public but I wanted to wait until
Debian/sarge was released which is now the case. And since the Debconf5
in Helsinki is just around the corner it's about the right time.
The concept is based on an LDAP
> On Fri, Jun 24, 2005 at 06:14:46PM +0200, Otto Wyss wrote:
> > The concept is based on an LDAP server (or simiar) as a replacement for
> > the Packages file and on a P2P network for package distribution (see
> > http://wyodesktop.sourceforge.net/index.php?page=pkgdist.ht
I've set the s attrtibute of halt since on my desktop any user may stop
the system. But about each second month or so it's set back to it's
original rights probably by a package upgrade. Is there a way to keep
the access rights or any better way to handle these kind of problems.
O. Wyss
--
Devel
Sorry, I don't know if this is the right group for this kind of message.
I've discovered that serveral identical packages in stable and unstable does
have different size/md5sum listed in the corresponding "Packages.gz" files.
I.e. "perspic-texts_1.4.6.deb" in "binary-all/misc" on a debian mirror a
With the introduction of the packages pool, I'm going to propose the
following change to the Packages files:
1. The filename tells what the Packages files contains:
Packages files should be independent of the their location, therefor the
name has to reflect their contents, i.e.
"Packages-$
It's commonly agreed that compression does prevent rsync from profit of
older versions of packages when synchronizing Debian mirrors. All the
discussion about fixing rsync to solve this, even trough a deb-plugin is
IMHO not the right way. Rsync's task is to synchronize files without
knowing what's
>> So why not solve the compression problem at the root? Why not try to
>> change the compression in a way so it does produce a compressed
result
>> with the same (or similar) difference rate as the source?
>
>Are you going to hack at *every* different kind of file format that you
>might ever want
> > gzip --compress-like=old-foo foo
> >
> > where foo will be compressed as old-foo was or as aquivalent as
> > possible. Gzip does not need to know anything about foo except how it
> > was compressed. The switch "--compress-like" could be added to any
> > compression algorithmus (bzip?)
> > gzip --compress-like=old-foo foo
>
> AFAIK thats NOT possible with gzip. Same with bzip2.
>
Why not.
> I wish it where that simple.
>
I'm not saying it's simple, I'm saying it's possible. I'm not a
compression speciallist but from the theory there is nothing which
prevents this
>>> > gzip --compress-like=old-foo foo
>
>gzip creates a dictionary (that gets realy large) of strings that are
>used and encodes references to them. At the start the dictionary is
>empty, so the first char is pretty much unencoded and inserted into
>the dictionary. The next char is encoded usi
> From time to time the question arises on different forums whether it is
> possible to efficiently use rsync with apt-get. Recently there has been a
> thread here on debian-devel and it was also mentioned in Debian Weekly News
> June 24th, 2003. However, I only saw different small parts of a huge
I just upgraded to the current Sarge and also got GCC 3.3. It seems this
version can't compile all the drivers in kernel 2.4.21. Which version
should I use? And how do I set this version (Environment variable?)
without deinstalling GCC 3.3?
O. Wyss
--
See "http://wxguide.sourceforge.net/"; for
I know I'm getting off topic but I don't know a better place to ask and
this subject might be interesting of other developers as well.
> On Fri, 8 Aug 2003 04:14, Otto Wyss wrote:
> > I just upgraded to the current Sarge and also got GCC 3.3. It seems this
> > vers
kicked
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello
My name is Natalia.
how are you?
I find your profile and e-mail on a site of acquaintances.
I want to find the more friend and my love.
If you is real are interested, answer to me and we can begin our acquaintance.
A little about me. I was born 30 DEC 1979.
I work as the manager in the insura
Sorry this message go to the poster instead of the list.
> > > There have always been some kernel headers in libc6-dev, they've just
> > > been split out into a separate package now. Several of these headers
> > > are referenced by headers provided by glibc which would break those
> > > headers i
> On Fri, Nov 07, 2003 at 10:45:32AM +, Jonathan Dowland wrote:
> > On Thu, Nov 06, 2003 at 07:55:03PM +0100, Eduard Bloch wrote:
> >
> > > What not rename linux-kernel-headers to simple system-headers-linux?
> > > This will prevent confused users (or: lazy to read the description users)
> >
The discussion about the libc6-dev package and its headers let me to the
impression that the Debian package structure isn't optimal for
libraries. If anyone wants to build his own version of a package (i.e.
libwxgtk2.4) he has to get all the dependent underlying dev packages as
well. This is a long
Currently there seems to be a problem with the Sarge-i386-1.jigdo file.
I tried to build/download a new CD but it complains 57 files where
missing. Even getting the .jigdo/.template files again or choosing
another mirror didn't help. The script can only be stopped so I don't
know how to proceed fur
> Hello,
>
> Hoping this won't turn into a flame war, I am looking for
> recommendations for a window manager. I tried quiet a few but none seem
> to fit the bill yet.
>
I don't know if XFCE fits all your requirements but since it's not only
a window manager but a light weight desktop I like it.
I tried to upgrade the 2.2 kernel from Woody to 2.4.22 and installed
kernel-image-2.4.22. During installation a large text but barely
interpretable text about initrd.img is shown. Why can't the install make
a fully correct lilo.conf by itself? Besides the text is wrong instead
of "initrd=initrd.img
I've installed alsa-modules-2.4.22-1-k6 but made a mistake when
selecting the driver. So I tried
dpkg-reconfigure alsa-modules-2.4.22-1-k6
but this doesn't show the driver list again! Okay getting dselect out,
purge the package and install it again. But now the list isn't shown
either. How do
> Otto Wyss dijo:
> > dpkg-reconfigure alsa-modules-2.4.22-1-k6
> >
> > but this doesn't show the driver list again! Okay getting dselect out,
> > purge the package and install it again. But now the list isn't shown
> > either. How do I get the dri
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.22-1-k6/alsa/snd-pdaudiocf.o
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.22-1-k6/alsa/snd-vx-cs.o
> > depmod: *** Unresolved symbols in
> > /lib/modules/2.4.22-1-k6/alsa/snd-vxp440.o
> > depmod: *** Unresolved symbols in
> >
> Install discover, read-edid and mdetect before you install X, and you're
> set.
>
mdetect hopefully doesn't choke on an USB-mouse anymore!
O. Wyss
>In fact, most of the options could be auto-detected from
>/proc/cpuinfo.
>
>It could also be useful as a hardware tester at install time:
>"Would you like to test your hardware (and get a kernel custom
>build for your hardware at the same time)? This process will
>potentially take a long time."
I considered to include Debian non-free into my synchronisation scripts
(see "http://dpartialmirror.sourceforge.net/";) but I couldn't find any
mirror nor any information about. Where is non-free located?
O. Wyss
Since I hated to start dselect again and again just to read a package
description I wrote a script "dsc2man" which creates appropriate man
pages for each package.
To minimize possible conflicts with other names it creates man pages in
section 6 (games!). Of course this can be configured in the co
> dpkg -s
>
This doesn't show the package description!
O. Wyss
--
Author of "Debian partial mirror synch script"
("http://dpartialmirror.sourceforge.net/";)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> > To minimize possible conflicts with other names it creates man pages in
> > section 6 (games!). Of course this can be configured in the config file.
> > I'd rather like to know which is a better place for it.
>
> Use a subsection. For instance, somepackage(1dsc) goes in
> $(mandir)/man1/somepa
> Is it better than `apt-cache show foo` ?
>
No if you are a power user, otherwise yes. Beside not everbody has
apt-cache installed.
O. Wyss
--
Author of "Debian partial mirror synch script"
("http://dpartialmirror.sourceforge.net/";)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a su
> On Thu, Apr 04, 2002 at 11:03:53PM +0200, Otto Wyss wrote:
> > I've now choosen "7dsc" since packages aren't commands.
>
> How about something more descriptive than "dsc"? Say, "package",
> "pkg", or "deb" (in my
> > Some questions that need to be asked:
> > Howmany of our mirrors are rsyncable?
> How much load can the servers handle?
> How much more load does rsync do than a fast http server like tux?
>
Please show use any figures first before you assert this.
I know rsync imposes some load for the compu
> A large mirror in Australia does provide an rsync server to access debian
> packages. When redhat 7.0 came out so many people tried to rsync it at the
> same time, the machine promptly fell over.
>
What amazes me is that nobody is able or willing to provide any figures.
So I guess no provider o
> On Sat, Apr 06, 2002 at 10:01:16AM +0200, Otto Wyss wrote:
> > The best would be if "man would bring up a list of man pages
> > with a choose facility when more than one page exists. Maybe this change
> > in behavior could be set through an environment variable.
> http://lists.debian.org/debian-devel/2001/debian-devel-200111/msg00757.html
Thanks for this pointer.
My debiansynch script never runs into problem "1. rsync -r" since it
always does single file transfers. And for problem "2. rsync of near
identical files" it's not astonishing using a high cpu l
> > 3.1 Compressed files cannot be differenced
>
> I recall seeing some work done to determine how much savings you could
> expect if you used xdeltas of the uncompressed data. This would be the
> best result you could expect from gzip --rsyncable. I recall the numbers
> were disapointing, it was
> > http://rsync.samba.org/rsync-and-debian/
> >
> > I'd appreciate comments.
>
This is certainly a very informative page. I'd appreciate if the CPU
load problem could be solved somehow.
IMO the versioning patch from Paul Russell is not the right approach
since this is Debian specific and has
Most of the scripts/methods I've seen which downloads Debian packages
with rsync do only single file transfer. IMO this must be much more
server friendly than a multi file transfer (no filelist).
Is it possible run a rsync server with anonymous login but restricted to
single file transfer next to
IMO each package should at least once per release upload a status
report. Also there was ample time for the transition of each package to
the pool. These are the reason behind the mailing to each maintainer of
packages still in Potato.
While most of the answers I got were positive, there were some
Thanks for your interest in the package. I am the submitter and I
haven't gotten any feedback so far on the package, so I assume it is
simply waiting for somebody to have time to review it. It is almost
identical to the current mariadb-5.5 package in Debian, so there
shouldn't be any actual issues
Hello,
2013/5/6 Thomas Goirand :
> I wonder what the plans of the MySQL maintainers are concerning MySQL vs
> MariaDB. Famously, Fedora made the switch. What will happen in Debian?
> What kind of transition would this mean? Would it be a drop-in
> replacement like Monty is pretending, or would it
2013/5/6 Steven Ayre :
> Having a policy on how such packages can coexist could then allow
> other options to also be added cleanly (MySQL Cluster, Percona, Galera
> etc).
I've done my best to package MariaDB following best practices on
Debian control files and conflict/replace rules. So I am conf
2013/12/25 Thomas Goirand :
> Don't you think it would be more reasonable if the mariadb-client
> contained a Provides: mysql-client, rather than changing each and every
> software dependency in Debian?
Currently the package contains "Provides: virtual-mysql-server" but I
guess this needs to be re
Hello,
2013/12/25 Thomas Goirand :
> Don't you think it would be more reasonable if the mariadb-client
> contained a Provides: mysql-client, rather than changing each and every
> software dependency in Debian?
>
> Adding debian-devel@, as I think it should be discussed more broadly.
We discussed
2013/12/30 Otto Kekäläinen :
> We discussed this on the pkg-maint-mysql list and the recommended policy is
> now:
>
> All packages that at the moment depend directly on mysql-client should
> instead have something like:
>
> Depends: the-one-they-tested-with | virtual-mysql-
omes from the mariadb-10.0 source package is a
drop-in replacement, and I am glad to help with any issues you have
regarding those packages.
Regards,
Otto
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contac
y MariaDB repos at https://salsa.debian.org/mariadb-team since
August, and it has been great. I have also got Merge Requests on Salsa
where the contributor has used the same CI test as well.
I warmly recommend everybody to adopt this in their workflow!
- Otto
are a few ones tagged newcomer friendly as well!
Build status in Debian (for porters!):
https://buildd.debian.org/status/package.php?p=mariadb-10.3
Please pick something that is close to your expertise and help out if
you can! :)
- Otto
--
News about my work at https://twitter.com/ottokekalainen
Hello fellow Debian Developers and those who want to be one!
MariaDB is a big package and it needs help.
I've updated the list of newcomer friendly bugs in
mariadb-10.3:https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=mariadb-10.3
Perfect for anybody who wants to learn Debian pa
Hello!
Is there any hardening flag / cmake expert around who could help me
get the hardening flags perfect in MariaDB 10.3?
Current state of build logs issues:
https://qa.debian.org/bls/packages/m/mariadb-10.3.html
The blhc tool currently outputs this:
$ blhc --debian --line-numbers --color ${W
Hello!
> > Is there any hardening flag / cmake expert around who could help me
> > get the hardening flags perfect in MariaDB 10.3?
> Start with https://wiki.debian.org/Hardening#Notes_for_packages_using_CMake
I've read this section many times over but I don't get it. A
workaround is presented bu
So apparently the 'D_FORTIFY_SOURCE=2' is in CPPFLAGS (not read by
cmake) but not in CXXFLAGS (read by cmake)[1].
So maybe I should define?
CXXFLAGS=$(CXXFLAGS) $(CPPFLAGS)
This is the current state of mysqld, should I be happy with this or is
it relevant that all functions are protected?
harden
Hello!
Thanks everybody for the pointers. I fixed it now with:
Subject: [PATCH] Ensure cmake builds also apply CPPFLAGS flags for hardening
to fully work
---
debian/rules | 5 +
1 file changed, 5 insertions(+)
diff --git a/debian/rules b/debian/rules
index 3a16f8bfa..2e7536b9c 100755
---
> > > Host lintian.debian.org not found: 3(NXDOMAIN)
> > >
> > > is this expected ?
> >
> > Yes, it is replaced by the UDD interface:
> >
> > https://wiki.debian.org/Services/lintian.debian.org
> > https://udd.debian.org/lintian/
Could we please have a HTTP 301 redirect from lintian.debian.org to
being the main drivers of
https://salsa.debian.org/salsa-ci-team/pipeline since 2018.
- Otto
> > > > Host lintian.debian.org not found: 3(NXDOMAIN)
> > > >
> > > > is this expected ?
> > >
> > > Yes, it is replaced by the UDD interface:
> > >
> > > https://wiki.debian.org/Services/lintian.debian.org
The page above links to two bug reports but I can't find any actual
information about *why
a URL to share to them. Perhaps I could implement
that later in the year.
- Otto
1 - 100 of 273 matches
Mail list logo
