ation (or misuse) with now two
fields with slightly tighter definitions and some significant overlap.
In short this is a case of "now you have two problems".
--
Julien Plissonneau Duquène
Le lundi 21 octobre 2024 à 15:05 +1100, Russell Coker a écrit :
>
Others have already given hints, but if you needed to ask the question,
then some sample code is better: there are two places where
modifications are needed in the packaging. [Aside: which I find is one
too much...]
Your d/copyri
Le mardi 13 août 2024 à 15:54 +0500, Andrey Rakhmatullin a écrit :
> On Tue, Aug 13, 2024 at 12:15:22PM +0200,
> julien.pu...@gmail.com wrote:
> > And of course, this is where I came to my wits' end: I can compile
> > the
> > new elpi successfully... but I have no way to install this new elpi
> > b
Hi,
there was a thread "Any way to install packages+run autopkgtests on
porterbox machines?" in march already. Let me add another problematic
use case.
I'm trying to work on bug #1078549 about the coq-elpi package on
ppc64el. With platti.debian.org I could confirm the failure with the
package cur
Hi,
Julien here, maintainer and main contributor of ifupdown2 since 2016.
> Since Cumulus has been bought by Nvidia, things have changed and
> development of ifupdown2 is now done behind closed doors.
NVIDIA acquisition of Cumulus didn't change anything for ifupdown2. The team
stay
Hi
Le lun. 8 avr. 2024, 14:45, Simon Richter a écrit :
> The web interface presented by salsa also does not have the necessary
> data<->metadata filters to provide an actual insight into what is really
> happening in the repository.
>
It's been several times already some people complain about s
Le samedi 03 février 2024 à 10:16 +0100, julien.pu...@gmail.com a
écrit :
>
> About flint: if you need anything done, don't hesitate to ask me.
>
In fact multi-arch is broken for flint and I can probably fix it: would
a new upload go in your way or on the contrary help you ? [I'll refrain
any mo
Hi,
Le vendredi 02 février 2024 à 08:21 -0800, Steve Langasek a écrit :
> The packages previously not reported are:
>
> flint
> flint-arb
About flint: if you need anything done, don't hesitate to ask me.
About flint-arb: its code has been merged into flint, so it's abandoned
upstream. T
Le dimanche 26 novembre 2023 à 16:34 +0100, Matthijs Kooijman a écrit :
> Hi,
>
> I've also gotten a bunch of bug reports from this MBF. Some were easy
> to
> fix, but there is one subtype of this issue where I think the
> commonly
> given advice and policy currently contradict.
>
> This concerns
Hi
Le mer. 20 sept. 2023, 04:11, Paul Wise a écrit :
>
> So I would like to suggest Debian relax our requirements around binary
> package descriptions, especially for Rust binary packages.
>
> Does anyone object to this change?
>
Yes, definitely.
I know it is a pain to write those texts, but t
Hi,
Le sam. 15 juil. 2023, 17:36, Nicolas Boulenguez a
écrit :
> Julien Puydt
> > - Indeed this is quite fragile; I have two scripts for Coq packages [1]:
> > one to tell me about the deps (I give it which package I have to upgrade
> > and it gives the list of affected
Hi
Le sam. 15 juil. 2023, 10:05, Jonas Smedegaard a écrit :
> Quoting Nicolas Boulenguez (2023-07-12 15:55:09)
> > The Ada maintainers are considering a new naming scheme for -dev
> packages,
> > where
> > libada-foo-dev Provides: libada-foo-dev-HASH.
> > source packages Build-Depend: libada
Package: wnpp
Severity: wishlist
Owner: Julien Puydt
X-Debbugs-Cc: debian-devel@lists.debian.org, Debian OCaml Maintainers
, jpu...@debian.org
* Package name: ppx-cold
Version : 0.16.0
Upstream Contact: opensource-conta...@janestreet.com
* URL : https://github.com
Package: wnpp
Severity: wishlist
Owner: Julien Palard
X-Debbugs-Cc: debian-devel@lists.debian.org, jul...@palard.fr
* Package name: sphinx-lint
Version : 0.6.7
Upstream Contact: Julien Palard
* URL : https://sphinx-contrib/sphinx-lint/
* License : Python
Le mercredi 26 octobre 2022 à 11:49 +0200, Jędrzej Dudkiewicz a écrit :
>
> in its postinstall script. As this causes rsyslog to be restarted a
> few times in a row it sometimes results in rsyslog not functioning.
>
High-severity issue right there: restarting should just work no matter
what. Ins
Le vendredi 21 octobre 2022 à 16:47 +1100, Phillip Smith a écrit :
> On Fri, 21 Oct 2022 at 16:30, Julien Puydt
> wrote:
> > In general they are ; just attach them to a bug report against the
> > package.
>
> Thanks! Is there a (recommended) tool to do this? I p
Hi
Le ven. 21 oct. 2022 à 07:28, Phillip Smith a écrit :
> Apologies if this is the wrong place to be asking this, but my
> Google-fu isn't guiding me to any results... Where/How do I submit
> patches for Debian packages?
>
> I have a small improvement for the iptables-persistent package; I
> cl
On Thu, Oct 13, 2022 at 05:17:59PM +0200, Tobias Frost wrote:
> On Thu, Oct 13, 2022 at 05:08:57PM +0200, Julien Cristau wrote:
> > On Thu, Oct 06, 2022 at 05:13:22PM +0200, Tobias Frost wrote:
> > > Maybe and idea would to do something like isa-support does for e.g
> >
ke "new package" |
> "you-need-to-enable-nonfree-firmware-reminder-package"
>
Failing on installation is a terrible user experience, let's not, pretty
please.
Cheers,
Julien
On Thu, Oct 6, 2022 at 15:45:25 +0100, Steve McIntyre wrote:
> On Wed, Oct 05, 2022 at 10:11:27PM +0200, Julien Cristau wrote:
> >On Sun, Oct 02, 2022 at 08:21:31PM +0100, Steve McIntyre wrote:
> >> On Sun, Oct 02, 2022 at 11:08:47AM -0400, Michael Stone wrote:
> >>
yway on upgrades.
>
I think in the absence of a release upgrade script (which I very much
doubt will happen, and be tested, and we can rely will be used, for
bookworm), Michael's suggestion seems like a reasonable way forward. I
imagine we'll need to patch dak to allow that, but it seems like it
should be tractable?
Cheers,
Julien
Package: wnpp
Severity: wishlist
Owner: Julien Puydt
X-Debbugs-Cc: debian-devel@lists.debian.org, jpu...@debian.org,
debian-ocaml-ma...@lists.debian.org
* Package name: ocaml-uucp
Version : 15.0.0
Upstream Author : Daniel Bünzli
* URL : https://erratique.ch/software
Package: wnpp
Severity: wishlist
Owner: Julien Puydt
X-Debbugs-Cc: debian-devel@lists.debian.org, jpu...@debian.org,
debian-ocaml-ma...@lists.debian.org
* Package name: ocaml-uunf
Version : 15.0.0
Upstream Author : Daniel Bünzli
* URL : https://erratique.ch/software
Package: wnpp
Severity: wishlist
Owner: Julien Puydt
X-Debbugs-Cc: debian-devel@lists.debian.org, jpu...@debian.org,
debian-ocaml-ma...@lists.debian.org
* Package name: ocaml-uucd
Version : 15.0.0
Upstream Author : Daniel Bünzli
* URL : https://erratique.ch/software
Package: wnpp
Severity: wishlist
Owner: Julien Puydt
X-Debbugs-Cc: debian-devel@lists.debian.org, jpu...@debian.org,
debian-ocaml-ma...@lists.debian.org
* Package name: ocaml-afl-persistent
Version : 1.3
Upstream Author : Stephen Dolan
* URL : https://github.com
Package: wnpp
Severity: wishlist
Owner: Julien Puydt
X-Debbugs-Cc: debian-devel@lists.debian.org, jpu...@debian.org,
debian-ocaml-ma...@lists.debian.org
* Package name: crowbar
Version : 0.2.1
Upstream Author : Stephen Dolan
* URL : https://github.com/stedolan
Hi
Le lun. 26 sept. 2022 à 23:42, Adrian Bunk a écrit :
>
> If we limit the problem to avoiding build failures in cases that
> upstream does not support, there would be the trivial solution of
> having a package ship Provides like:
> - architecture-is-64bit
> - architecture-is-32bit
> - architec
Hi,
Le lundi 19 septembre 2022 à 20:50 +0900, Hideki Yamane a écrit :
>
> Recent changes in GitHub releases pages, I cannot check upstream
> version with uscan. How do you deal with it?
It's not that recent ; here is a working example:
version=4
opts="\
dversionmangle=s/\+dfsg.*$//,\
filenamem
Le vendredi 19 août 2022 à 09:04 +0200, Fabio Fantoni a écrit :
> Il 19/08/2022 03:01, Paul Wise ha scritto:
> > On Thu, 2022-08-18 at 21:18 +0200, Gioele Barabucci wrote:
> >
> > > Does anybody have objective objections against activating
> > > automatic
> > > changelog trimming in binary package
Hi,
Le lundi 01 août 2022 à 14:20 +0200, Joachim Breitner a écrit :
>
> it looks like you re-created the setup that the Haskell and Ocaml
> packages use, with the provides/depends and hashes.
>
Yes, dh-ocaml was a great help. I learned Perl to write dh-coq...
> We have a tool that produces a f
Hi,
Le lundi 01 août 2022 à 14:20 +0200, Joachim Breitner a écrit :
>
> Am Sonntag, dem 31.07.2022 um 12:33 +0200 schrieb
> julien.pu...@gmail.com:
> > I have a little script that tells me the following packages needs
> > to be
> > rebuilt when a transition has to be done ; for example:
> >
> >
Le dimanche 31 juillet 2022 à 12:43 +0200, Sebastian Ramacher a écrit :
> On 2022-07-31 12:33:35 +0200, julien.pu...@gmail.com wrote:
> > Hi,
> >
> > I tried to ask on debian-release because it seemed more sensible
> > but didn't get feedback. [1]
>
> Please file a transition bug. The mailing lis
Le dimanche 31 juillet 2022 à 12:43 +0200, Sebastian Ramacher a écrit :
> On 2022-07-31 12:33:35 +0200, julien.pu...@gmail.com wrote:
> > Hi,
> >
> > I tried to ask on debian-release because it seemed more sensible
> > but
> > didn't get feedback. [1]
>
> Please file a transition bug. The mailing
Hi,
I tried to ask on debian-release because it seemed more sensible but
didn't get feedback. [1]
The Coq-related packages have a habit of breaking their ABI with almost
each upload, and until recently that meant broken user configurations:
installed packages stopped working because of an upgrade
Hi,
Le jeudi 14 juillet 2022 à 14:16 +0200, Marc Haber a écrit :
> On Thu, 14 Jul 2022 12:54:52 +0100, Steve McIntyre
> wrote:
> > And I see you uploaded ~immediately - why even bother with an ITP?
>
> Is it proper procedure to upload without an ITP?
>
No ; I have to admit a large percentage o
Le mardi 28 juin 2022 à 16:17 -0400, Scott Talbert a écrit :
> On Tue, 28 Jun 2022, julien.pu...@gmail.com wrote:
> >
> > Wild guess: were your new uploads _*source-only*_ ?
>
> I looked at a couple of them and they were (source all) so that does
> appear to be the problem. All uploads need to
Le mardi 28 juin 2022 à 22:08 +0200, Bastian Venthur a écrit :
> Hi,
>
> sorry I didn't follow the conversation but it seems that all my
> Python
> packages are still not migrating to testing and I don't really
> understand how to fix it. The error I see consistently in my Python
> packages is:
Le mercredi 15 juin 2022 à 11:11 +0300, Tommi Höynälänmaa a écrit :
> ke, 2022-06-15 kello 09:55 +0200, julien.pu...@gmail.com kirjoitti:
> >
> > Let your new package migrate to testing, since it's that one which
> > doesn't have the autoremoval issue?
>
> I'm not sure I understand what you mean.
Le mercredi 15 juin 2022 à 10:29 +0300, Tommi Höynälänmaa a écrit :
>
> I recently received e-mail that package guile-cairo is to be
> autoremoved 2022-07-09. The reason is that it depended on guile 2.2.
> However, I made new version guile-cairo-1.11.2-5 that depends only on
> guile 3.0. What shal
Le jeudi 02 juin 2022 à 14:31 -0500, Richard Laager a écrit :
>
> There are a couple different ways to do Python to C. I think the
> terms are CFFI (or FFI or ctypes, maybe some of those are different
> though?) vs CPython extension, but I'm not 100% certain of that.
May I suggest debian-pyt...@l
Hi
Le ven. 27 mai 2022 à 09:27, Andreas Tille a écrit :
> Am Thu, May 26, 2022 at 08:47:20AM +0200 schrieb Nilesh Patra:
> > Would it be possible to manually remove this item from the list that
> generates
> > autoremovals?
>
> ... or generate a blacklist of packages that should not trigger thos
Le jeudi 26 mai 2022 à 09:32 +0300, Timo Lindfors a écrit :
>
> On 5/24/22 21:34, Paul Gevers wrote:
> > https://bugs.debian.org/1011268 (but apparently my first assumption
> > was wrong and it's another bug, most likely Simon was right.
>
> Thanks for the link. I was quite puzzled this morning w
Le mercredi 04 mai 2022 à 10:12 -0700, Russ Allbery a écrit :
> Bill Allombert writes:
>
> > I plan to add support for 'XB-Popcon-Reports: no' to popularity-
> > contest.
> > This allows to build packages with private names that will not be
> > reported to popcon, by adding 'XB-Popcon-Reports: no
> My limited understanding of the landscape of git workflows is that a
> > workflow that is quite popular among packages still using the 1.0 format
> > is the one used by the Debian X strike force. Julien Cristau described
> > it as follows when I asked about it on IRC:
> >
&
Le mardi 01 mars 2022 à 10:34 +0100, Sebastiaan Couwenberg a écrit :
> On 3/1/22 10:28, Julien Puydt wrote:
> > Is there really no mips64el porterbox, or is it only a transitory
> > situation?
>
> eller.debian.org has mips64el chroots.
>
How do I use one of those and not
Hi,
one of my package has a failure on mips64el and upstream is ready to
help me find the cause and debug the issue.
Unfortunately, on https://db.debian.org/machines.cgi I only see five
developer machines on this architecture -- all buildd!
Is there really no mips64el porterbox, or is it only a
Le samedi 05 février 2022 à 15:07 +, Andrew M.A. Cater a écrit :
> There's a huge amount of software that's undistributable: Debian's
> good faith attempt to review this is one of the crucial arguments I
> have with $DAYJOB about the benefits of a curated distribution,
> however fallible we may
Hi,
I got an RC bug on python-anyio, because its testsuite fails when run
on an IPv6-only host [1].
I pushed the issue upstream, and upstream has a patch proposal [2].
Now comes the question: how do I test this patch?
Cheers,
J.Puydt
[1] https://bugs.debian.org/1004461
[2] https://github.com/
On Wed, Jan 26, 2022 at 09:43:16PM -0800, Ross Vandegrift wrote:
> On Wed, Jan 26, 2022 at 07:58:23PM +0100, Julien Cristau wrote:
> > I think we (DSA) have been reluctant to add new third-party-run services
> > under debian.org, and it's not clear to me if that infrastructure
ud team on behalf of debian, or if the cloud team would
control the names but point them at mirrors run by the cloud providers
themselves.
Either way as Stefano said if you go for a new domain name it should be
possible to use the same setup as our other domains if you want.
Cheers,
Julien
ns or policy changes IMO.
Libs.private is a bit different because static linking is not typically
used for Debian packages, but Requires and Requires.private are quite
clear cut.
Cheers,
Julien
On Thu, Dec 09, 2021 at 03:24:27PM +0100, Alexander Traud wrote:
> Linux distributions, which have
Hi
Le jeu. 2 déc. 2021 à 11:36, Yadd a écrit :
>
> Another idea to have a compromise:
> * uscan is released with versioned schemes (GitHub.json, sf.json,...)
> * when launched, it tries to download new version from a new Debian API
> (static json files)
> * if no response or no new v
Hi
Le sam. 9 oct. 2021 à 18:52, Jonas Smedegaard a écrit :
> Quoting Julien Puydt (2021-10-09 18:48:07)
> > Hi
> >
> > Le sam. 9 oct. 2021 à 17:40, Jeremy Stanley a écrit
> :
> >
> > > On 2021-10-09 08:53:57 +0200 (+0200), Yadd wrote:
> > > [..
Hi
Le sam. 9 oct. 2021 à 17:40, Jeremy Stanley a écrit :
> On 2021-10-09 08:53:57 +0200 (+0200), Yadd wrote:
> [...]
> > If you really consider minified files as binary, there's a room for
> > creating a lot of RC bugs
>
> The more appropriate question is whether Debian considers minified
> file
Le lundi 20 septembre 2021 à 11:11 +0200, Markus Frosch a écrit :
>
> I would keep using the versioning style of upstream.
>
> dpkg and uscan should be pretty much fine with this:
>
> $ dpkg --compare-versions 2021.8.23 eq 2021.08.23; echo $?
> 0
Oh, you mean 2021.9.9 won't be seen as the last
Hi,
I'm having an issue with an upstream where the latest git tag is
v2021.8.23 ; I would have liked them to (also) tag v2021.08.23, but
that won't happen.
So I need some uversionmangle magic.
I know how to get the parts $1=2021, $2=8 and $3=23, but I don't know
how to say $2 ($3 will need a sim
x27;re connecting to via SNI happening unencrypted,
>
> SNI is not unencrypted if you do TLS1.3...
>
It is, though... ECH (née ESNI)
https://datatracker.ietf.org/doc/draft-ietf-tls-esni/ is still WIP.
Cheers,
Julien
a lower severity and consider bumping it
to serious once you're down to a manageable number (and possibly a
couple of NMU campaigns).
Cheers,
Julien
Le lundi 19 avril 2021 à 14:05 +0100, Jonathan Dowland a écrit :
> On Mon, Apr 19, 2021 at 11:30:48AM +0800, Benda Xu wrote:
> > The winning option "Debian will not issue a public statement on
> > this
> > issue" implies that the majority of DDs is not interested in such
> > non-technical affairs.
, so long as that
> is open, i.e. until the last point release. So it looks as if the copy
> to the main archive failed for some reason.
>
The samba package is held in stable-new by bug#939419, see
https://release.debian.org/proposed-updates/stable.html
Cheers,
Julien
> > Somet
Hi
Le mar. 30 mars 2021 à 12:49, Gard Spreemann a écrit :
>
> In order to calibrate what is considered merely "a foolish thing said"
> from your perspective, I feel a need to ask: what is, from your
> perspective, the least of the sufficiently bad things that a person can
> do in order for Debia
On Mon, Mar 08, 2021 at 05:13:35PM +0100, Job Snijders wrote:
> Dear Julien,
>
>
> > Description : Free, functional, and secure implementation of the
> BGP-4 protocol.
>
> the above short description has 3 useless words in it, I suggest you drop
&g
them.
If it wasn't free it wouldn't be in Debian; if it wasn't functional why
would anyone release or package it; same with "secure", plus it's a
rather meaningless descriptor that'll be wrong the day somebody finds a
bug (especially combined with "implemented in C"...).
Cheers,
Julien
hanging, at which
point both filenames change.
Cheers,
Julien
in #955603 despite many objects.
>
These hardware drivers belong in the kernel. Do aiptek USB devices not
show up as regular input devices that generic userspace drivers can
handle?
Cheers,
Julien
[1] https://tracker.debian.org/pkg/root-system
>
Please re-use the old name. "root" is a terrible choice of package name.
Thanks,
Julien
Hi Antonio,
On Thu, Jan 21, 2021 at 02:47:25PM -0300, Antonio Terceiro wrote:
> On Thu, Jan 21, 2021 at 03:10:47PM +0100, Julien Cristau wrote:
> > And which of standard or important made most sense (AIUI, standard
> > means "installed by default in d-i" and impo
d. And which of
standard or important made most sense (AIUI, standard means "installed
by default in d-i" and important means "installed by default in
debootstrap").
Thanks,
Julien
binNMU'd, it
> automatically gets Provides: foo-data (= 1.2-3)
>
> - Change some more central component so that the dependencies are edited
> or the Provides is added globally
>
> - Something clever that I haven't thought of
>
Make no-change-other-than-version-bump source uploads easier?
Cheers,
Julien
Le lundi 09 novembre 2020 à 21:08 +, Sudip Mukherjee a écrit :
> I have attached the list.
> Do you want me to add them in my MBF list and raise bug reports for
> them?
If I remember well, I'm the main culprit behind those, and I'll refresh
them -- probably at the end of the week:
node-ast-ty
Le mardi 20 octobre 2020 à 18:00 +0200, Jonas Smedegaard a écrit :
> > > - bad: the tarball contains the whole sources (no repack) ;
> > > - bad: the bare checkout isn't cleared.
> >
> > Still current.
>
> Please file bugreports about concrete weaknesses of Debian tools.
>
> If you are still ask
Le lundi 19 octobre 2020 à 10:06 +0200, Jonas Smedegaard a écrit :
> You might find some inspiration in the source package
> jsbundle-web-interfaces which uses version type "group" and
> mode=git,
> and sets individual version numbers for each binary package.
>
> Another example is matrix-mirage
Le mardi 20 octobre 2020 à 10:02 +0200, Julien Puydt a écrit :
> Hi,
>
> Le lundi 19 octobre 2020 à 20:03 +, PICCA Frederic-Emmanuel a
> écrit :
> > what about the git mode of uscan
> >
> > then you would have all the tags ?
>
> Ah, yes, I had forgott
Hi,
Le lundi 19 octobre 2020 à 20:03 +, PICCA Frederic-Emmanuel a
écrit :
> what about the git mode of uscan
>
> then you would have all the tags ?
Ah, yes, I had forgotten that!
I tried with a simpler version (one component), and my d/watch is :
version=4
opts=\
component=algorithm,\
dve
Hi,
Le lundi 19 octobre 2020 à 11:51 +0200, Julien Puydt a écrit :
> Even in that case, will uscan see the tag subpackage42/3.14 on
> github?
> In my experience, it only sees a handful of last tags, so it will see
> the releases of something like subpackage1/* to subpackage23/*, b
Hi,
Le lundi 19 octobre 2020 à 20:33 +0200, Jonas Smedegaard a écrit :
> Quoting Julien Puydt (2020-10-19 19:27:11)
> > Am I getting somewhere with today's tools? Can someone propose a
> > nicer way in the future?
>
> My apologies for mistaking the scope of your quest
Hi,
Le lundi 19 octobre 2020 à 12:15 +0200, Jonas Smedegaard a écrit :
> Quoting Pirate Praveen (2020-10-19 12:01:47)
> > On 2020, ഒക്ടോബർ 19 12:45:28 PM IST, Julien Puydt
> > wrote:
> > > I was trying to update the ipywidgets package. It once had a
> > > quite
Le lundi 19 octobre 2020 à 16:42 +0530, Pirate Praveen a écrit :
>
> On Mon, Oct 19, 2020 at 11:51, Julien Puydt
> wrote:
> > Here is what I have in d/control for my src:lumino experiments :
> >
> > Provides: node-lumino-algorithm (= 1.3.3),
> >
Hi,
Le lundi 19 octobre 2020 à 10:06 +0200, Jonas Smedegaard a écrit :
> Hi Julien, and others,
>
> Quoting Julien Puydt (2020-10-19 09:15:28)
> > I was trying to update the ipywidgets package. It once had a quite
> > normal upstream, but then things went wild, if not st
Hi,
I was trying to update the ipywidgets package. It once had a quite
normal upstream, but then things went wild, if not stellar : they went
monorepo.
For those lucky ones who never crossed the principle, the idea is to
have a single repository, and make dozens of different packages live
within.
Hi,
Le dim. 9 août 2020 à 18:16, Simon McVittie a écrit :
> Unfortunately, to the best of my knowledge, this is currently the least bad
> thing to do.
>
if the current practices/software doesn't give enough leeway, perhaps we
should seek to improve the situation.
How would that fly if there we
Hi,
I have packaged a few mods for the minetest game these last years.
Recent minetest versions have a feature where you can download mods
directly online.
So the questions are :
(1) should I go on updating the existing packages? or ask for their
removal? orphan them? whatever?
(2) should I go
Hi,
Le jeudi 18 juin 2020 à 09:21 +0200, Gard Spreemann a écrit :
> It seems to me that the "Lintian E+W" column on the QA packages
> overview
> page currently incorrectly shows a checkmark even when there are
> Lintian
> warnings for a package. Is this a known bug?
I was about to ask around why
Le mercredi 27 mai 2020 à 22:06 +0300, Otto Kekäläinen a écrit :
> Do we have Debian devs here who have pimped their shell heavily with
> custom prompts, colors, command line fonts, shell window title hacks,
> perhaps using zsh etc? Have you written blogs about you experiences,
> can you share some
On Sat, Apr 25, 2020 at 00:51:34 +0800, Shengjing Zhu wrote:
> And another question for DSA is, whether the lists.alioth.debian.org
> address is expected to work, as long as the alioth-lists.debian.net
> exists?
>
I don't see a reason to break it.
Cheers,
Julien
Le mardi 24 mars 2020 à 14:03 +0100, Vincent Bernat a écrit :
>
> There are other reasons, notably that you speed up builds by having
> all
> the source code ready.
Sorry, I don't know much about how go works, but : can't the developer
just have the deps ready -- and just not commit them to the
eir side, without imposing that decision on the debian
archive.
Cheers,
Julien
Hi,
Le vendredi 20 mars 2020 à 07:44 +0100, Ansgar a écrit :
>
> We should probably also not ship the same changelog in multiple
> packages, especially when one depends on the other.
>
Switching to per src:package changelogs would cover that.
But that will probably mean making dpkg smarter.
J
it'll eventually get retried and (assuming it passes) the migration
block will lift.
Cheers,
Julien
defaulting to not doing so.
>
How is this worse than what we're already doing by default, namely
sending the same data to whoever happens to be on the network, in
addition to whoever happened to be listed in an unauthenticated dhcp
response? (Which, if you're lucky, is your ISP, aka a 3rd party.)
Cheers,
Julien
backports being non available.
>
> Is the problem linked to buster-backports not existing yet ? Is backports
> repo not created automatically on new releases?
>
buster-backports exists. AIUI this is an apt bug when dealing with
empty repos. (Although why are you setting default-release to
buster-backports?)
Cheers,
Julien
orkstation install" is the wrong
> class of standard (whether I have a grasp on it or not). If it's not going
> to
> cause an FTBFS on a buildd, I think it's not RC. That would limit it to
> packages that are build-depends (direct or indirect) of other packages, i.e.
> no leaf packages.
>
> So my answer to both your questions is no.
>
+1
I'd say (1) and (2) range somewhere from minor to normal severity.
Cheers,
Julien
ackage names is usually worse than reusing
source package names, in that it's a lot more likely to affect users.
Sometimes it happens anyway, but IMO it's best avoided.
Cheers,
Julien
is instead of hglib,
which:
- is already in debian
- is maintained by mercurial upstream
- has pretty much the exact same package description as the above
?
This seems like useless duplication.
Thanks,
Julien
On 12/7/18 4:34 PM, Cyrille Bollu wrote:
> The URL https://release.debian.org/transitions/html/perl5.28.html is
> 404 :-(
>
With Perl 5.28 in testing, the transition is over.
Cheers,
Julien
equivalent to sbuild-createchroot(8).
https://salsa.debian.org/dsa-team/mirror/dsa-puppet/tree/master/modules/schroot/
Cheers,
Julien
On 11/23/18 12:18 PM, Dmitry Shachnev wrote:
> On Thu, Nov 22, 2018 at 11:05:27PM +0100, Julien Cristau wrote:
>> At least mesa drivers can be used for desktop GL or GLESv2 just fine,
>> AFAIK. Maybe the answer for Qt is to switch to GLESv2 for all
>> architectures, to st
y
> box and use it as a normal OpenGL accelerated desktop (did that already
> few years ago).
>
At least mesa drivers can be used for desktop GL or GLESv2 just fine,
AFAIK. Maybe the answer for Qt is to switch to GLESv2 for all
architectures, to stop the special-casing madness, instead of making it
spread? :)
Cheers,
Julien
t with the same filenames.
>
>> I think the policy should be changed.
>
> I'd very very strongly oppose any such change.
>
Ditto.
Cheers,
Julien
t seem like something we want or need to
do. browserify doesn't seem to be that special, IMO.
Cheers,
Julien
1 - 100 of 1017 matches
Mail list logo
