Le vendredi 31 mai 2019 à 02:15 +0200, Pavel Raiskup a écrit :
> On Thursday, May 30, 2019 10:38:25 AM CEST Miroslav Suchý wrote:
> > Dne 29. 05. 19 v 23:52 Josh Boyer napsal(a):
> > > If we did this, wouldn't it make it very difficult to use tools
> > > like
> > > mock on RHEL / CentOS 7 to build
Le jeudi 30 mai 2019 à 14:29 -0700, Samuel Sieb a écrit :
> On 5/30/19 1:56 PM, Chris Murphy wrote:
> > On Thu, May 30, 2019 at 8:40 AM Daniel Mach
> > wrote:
> > > Dne 30. 05. 19 v 0:05 Neal Gompa napsal(a):
> > > > I'm pretty sure this would break DeltaRPMs, since none of the
> > > > drpm
> > >
Le samedi 08 juin 2019 à 11:23 +0200, Igor Gnatenko a écrit :
> Hi,
>
> Imagine situation that somebody is working on KDE rebase and me on
> libgit2 rebase. Both involve rebuilding/updating some package, let's
> say kf5-ktexteditor.
>
> We both work in different side tags, in KDE rebase
Hi,
Fedora’s new Go packaging macros landed in rawhide (koji) today.
The corresponding Fedora Go packaging conventions are therefore
EFFECTIVE for new rawhide builds. For the first time in Fedora’s
history, we will be able to perform Go package builds conforming to an
approved Fedora Packaging
Le 2019-06-12 10:39, Jakub Cajka a écrit :
Fedora’s new Go packaging macros landed in rawhide (koji) today.
I thought that we have agreed on Go SIG meeting with eclipseo to do
this in side tag along with golang rebase(to avoid 2 rebuilds),
> We could go a step further and extend rpm and dnf to support multiple
> versions of same named packages for installation. This is doable but
> not necessarily trivial.
Having rescued this week a system in abysmal stale, with traces of rpm
forcing right and left, I'd say this would also
Le 2019-06-18 10:42, Miro Hrončok a écrit :
On 18. 06. 19 3:27, Igor Gnatenko wrote:
Hi folks,
as of today, builders have been updated (thanks to Kevin) and
DynamicBuildRequires finally work in Rawhide.
All of the following works? Koji, mock and copr?
Mock already worked IIRC.
Regards.
Le 2019-06-18 03:27, Igor Gnatenko a écrit :
Hi folks,
Hi
as of today, builders have been updated (thanks to Kevin) and
DynamicBuildRequires finally work in Rawhide.
Change Page:
https://fedoraproject.org/wiki/Changes/DynamicBuildRequires
Example of real build:
Le vendredi 21 juin 2019 à 19:16 -0500, Jason L Tibbitts III a écrit :
> (Certainly it's
> better if it misses things because you can always just add them as
> regular BuildRequires:, but it's tougher to deal with things added
> erroneously.)
That's trivial to handle too, just add a
| grep -v
Le vendredi 21 juin 2019 à 18:32 -0500, Jason L Tibbitts III a écrit :
> > > > > > "MC" == Michael Cronenworth writes:
>
> I'm disappointed that the macro doesn't emit the
> %generate_buildrequires
> line as well;
I'm not real sure, this would work, for projects that contain stuff
involving
Le lundi 24 juin 2019 à 18:50 +0200, Igor Gnatenko a écrit :
> But packages will be still built for i686 architecture and then
> shipped in repos (not completely sure if having i686-only repo is
> useful, but they will be in x86_64 repos definitely).
It would be nice if they were finally split
Le 2019-06-19 12:48, Jens-Ulrik Petersen a écrit :
Hi
And yes as Nicolas also said maybe we need: langpacks-ko-fonts and
langpacks-ko-input-methods, etc.
I's much more than input methods, it's anything you need to read/write a
language (input, spell/grammar, fonts, etc)
Though the whole
Le 2019-06-19 14:32, Nicolas Mailhot a écrit :
Le 2019-06-19 12:48, Jens-Ulrik Petersen a écrit :
Hi
And yes as Nicolas also said maybe we need: langpacks-ko-fonts and
langpacks-ko-input-methods, etc.
I's much more than input methods, it's anything you need to read/write
a language (input,
Le 2019-06-18 10:19, Miroslav Suchý a écrit :
Dne 18. 06. 19 v 3:27 Igor Gnatenko napsal(a):
as of today, builders have been updated (thanks to Kevin) and
DynamicBuildRequires finally work in Rawhide.
Change Page:
https://fedoraproject.org/wiki/Changes/DynamicBuildRequires
Example of real
Le 2019-06-17 22:04, Terry Bowling a écrit :
Hi
If I may, since I also represented the customer side not so long ago in
a fortunexxx company.
* Customers think we had too many repos. It is hard to find what
they need.
From a customer point of view you sidestepped the demand.
Le May 6, 2019 4:29:22 PM UTC, Chris Murphy a écrit :
>On Mon, May 6, 2019 at 1:52 AM Nicolas Mailhot
> wrote:
>>
>> Le dimanche 05 mai 2019 à 16:14 -0600, Chris Murphy a écrit :
>> >
>> > Right and that's the same with beta testing, which is how bugs like
>> > this can sometimes not even get
Le dimanche 05 mai 2019 à 12:33 -0400, Steve Grubb a écrit :
> On Sunday, May 5, 2019 11:39:50 AM EDT Nicolas Mailhot via devel
> wrote:
> > It would be nice to have a robust upgradeable bootloader setup. I'm
> > pretty
> > sure that ranks before having a pretty fli
Le dimanche 05 mai 2019 à 16:14 -0600, Chris Murphy a écrit :
>
> Right and that's the same with beta testing, which is how bugs like
> this can sometimes not even get found until after release. A lot of
> tests are done on pristine systems that are throw away. It's entirely
> understandable few
Le mercredi 01 mai 2019 à 13:12 +0100, Tomasz Kłoczko a écrit :
> On Wed, 1 May 2019 at 09:04, Nicolas Mailhot <
> nicolas.mail...@laposte.net> wrote:
> [..]
> > > One of those specs is elfutils.spec in which is:
> > >
> > > %check
> > > # Record some build root versions in build.log
> > > uname
Le vendredi 03 mai 2019 à 09:46 +0100, Tomasz Kłoczko a écrit :
> ial today, because the storage part has not been streamlined.
>
> As I wrote problem only is that without possibility really rollback
> to
> the full state described in set of exact N-E:V-Rs packages recorded
> data such auditing
Le vendredi 03 mai 2019 à 12:04 +0100, Tomasz Kłoczko a écrit :
> On Fri, 3 May 2019 at 11:04, Nicolas Mailhot via devel
> wrote:
> [..]
> > You're assuming the only use is roolback. It's not
>
> Point taken. Can you shortly describe other use cases?
You use apps in o
Le vendredi 03 mai 2019 à 19:59 +0200, Dridi Boukelmoune a écrit :
> On Fri, May 3, 2019 at 1:45 PM Nicolas Mailhot via devel
> wrote:
> > Le vendredi 03 mai 2019 à 12:04 +0100, Tomasz Kłoczko a écrit :
> > > On Fri, 3 May 2019 at 11:04, Nicolas Mailhot v
It would be nice to have a robust upgradeable bootloader setup. I'm pretty sure
that ranks before having a pretty flicker-free boot to Fedora users. Pretty
boot has been a workstation priority for how many releases now?
Baring that, just having a reinstall bootloader option in rescue mode would
Le 2019-06-26 16:07, Josh Boyer a écrit :
On Wed, Jun 26, 2019 at 9:24 AM Roberto Ragusa
wrote:
On 6/26/19 2:34 AM, Michal Schorm wrote:
> I - and a people around me - have plenty of 32-bit hardware.
Just for the record, I've got a couple of AMD XP2400+, AMD XP2000+
machines,
updated to
Le 2019-06-26 15:39, Richard W.M. Jones a écrit :
On Tue, Jun 18, 2019 at 03:27:41AM +0200, Igor Gnatenko wrote:
as of today, builders have been updated (thanks to Kevin) and
DynamicBuildRequires finally work in Rawhide.
Change Page:
Le jeudi 27 juin 2019 à 12:26 -0600, Chris Murphy a écrit :
> On Thu, Jun 27, 2019 at 9:06 AM Bruno Wolff III
> wrote:
> > On Wed, Jun 26, 2019 at 14:19:26 -0600,
> > Chris Murphy wrote:
> > > Short version: Fedora should take responsibility for the
> > > bootloader
> > > being up to date, by
Le jeudi 11 juillet 2019 à 16:43 -0400, Daniel Walsh a écrit :
>
>
> They shouldn't, we have an open Bugzilla on that.
And eclispeo just finished a mass refresh and debundling pass on
Fedora's Go stack (eclispeo has superpowers), the remaining stickers
are all contenairish stuff (k8s…) so it
Le 2019-07-08 09:06, Jakub Cajka a écrit :
- Original Message -
From: "Nicolas Mailhot via devel"
To: "Christophe de Dinechin" , "Development
discussions related to Fedora"
Cc: "Robin Lee" , "nicolas mailhot"
Sent: Saturday, Jul
It would be much clearer and user-friendly to move I*86 packages out of the 64
bit repos and make the i*86 an optional add-on
Le July 14, 2019 9:27:03 PM UTC, Neal Gompa a écrit :
>On Sun, Jul 14, 2019 at 5:21 PM Kevin Fenzi wrote:
>>
>> On 7/14/19 1:15 PM, Neal Gompa wrote:
>>
>> > This will
Le mardi 16 juillet 2019 à 18:53 +0200, Björn 'besser82' Esser a
écrit :
>
>
> Which build chain does look cleaner, shorter, and more semantically
> correct?
>
> 1. systemd (no cryptsetup) --> json-c (new so-ver) --> cryptsetup
> --> systemd (with cryptsetup) --> other consumers in
Le vendredi 28 juin 2019 à 18:49 -0600, Chris Murphy a écrit :
> On Fri, Jun 28, 2019, 1:19 AM Nicolas Mailhot via devel
> wrote:
> > Le jeudi 27 juin 2019 à 12:26 -0600, Chris Murphy a écrit :
> > > Yep, small problem. And I'm not even sure how a 'grub2-install'
> > &g
Hi,
> What should I do at this moment as a packager that maintaining some
> Go packages?
> Should I fix my packages and build against f31-go in Koji?
Yes, sure, if you can that would be appreciated. The vast majority of
packages is easy to clean up (just adapt the templates in go-rpm-
templates
Le 2019-07-31 14:13, Lennart Poettering a écrit :
Hi Lennart
Note that there's a "stable" backport tree maintained outside of the
main repo:
https://github.com/systemd/systemd-stable
Either way, I doubt this discussion is relevant to Fedora, is it?
It was when a lot of users could not test
Le 2019-09-02 19:27, Kevin Kofler a écrit :
Nicolas Mailhot via devel wrote:
2. However the IETF explicitely forbid it when defining the ISO 8501
subset allowed on the Internet
RFC 3339> Although ISO 8601 permits the hour to be "24", this profile
of
ISO
RFC 3339> 8601 on
Le 2019-08-31 10:44, Zbigniew Jędrzejewski-Szmek a écrit :
(I asked a few people what 24:00 means to them, and after getting a
few strange looks and answers,
To be fair:
1. ISO 8501 allows writing 24:00
Wikipedia> Midnight is a special case and may be referred to as either
"00:00" or
Le 2019-09-03 18:52, Kyle Marek a écrit :
Additionally, binding to a specific address does not handle dynamic
networks very well.
Simplify that to binding to a specific address does not handle network
very well, since everything is dynamic nowadays, on desktops, phones or
servers (servers
Le vendredi 13 septembre 2019 à 12:18 +0200, Kevin Kofler a écrit :
> Nicolas Mailhot via devel wrote:
> > That's an historical artefact, that made sense when everyone used
> > the
> > same dozen font on windows, and when each and everyone of them
> > could be
&g
Le 2019-09-13 00:05, Kevin Kofler a écrit :
Marius Schwarz wrote:
(in short: no update to 2.00.5-3 was possible via dnf, as packages
refer
to 2.00.3-1 directly)
They don't actually refer to liberation-fonts-2.00.3-1, but to
liberation-
narrow-fonts, which liberation-fonts-2.00.3-1 claims to
Le 2019-09-13 10:39, Kevin Kofler a écrit :
Nicolas Mailhot via devel wrote:
The correct thing would have been never to create a narrow liberation
subpackage in the first place since narrow is just a face of a font
(like bold).
In theory, in an ideal world, that makes sense. But in practice
Le mercredi 31 juillet 2019 à 17:03 +0200, Andreas Tunek a écrit :
>
>
> On Wed, 31 Jul 2019, 16:10 Nicolas Mailhot via devel, <
> devel@lists.fedoraproject.org> wrote:
> > Le 2019-07-31 14:13, Lennart Poettering a écrit :
> >
> > Hi Lennart
> >
> &
Le mercredi 31 juillet 2019 à 12:25 -0500, Jason L Tibbitts III a
écrit :
> > > > > > "KF" == Kevin Fenzi writes:
>
> KF> * If you use metalinks, rpm signatures are just gravy on top, in
> the
> KF> end you are still just trusing SSL CA's.
>
> Only if you trust every mirror to always serve
Le jeudi 01 août 2019 à 00:27 -0700, Samuel Sieb a écrit :
> On 7/31/19 11:41 PM, Nicolas Mailhot via devel wrote:
> > Le mercredi 31 juillet 2019 à 16:10 -0700, Brian C. Lane a écrit :
> > > If so you can pass
> > > inst.noverifyssl to anaconda to tell it to ignor
Le mercredi 31 juillet 2019 à 16:10 -0700, Brian C. Lane a écrit :
> On Wed, Jul 31, 2019 at 09:05:21PM +0200, Nicolas Mailhot via devel
> wrote:
> > Le mercredi 31 juillet 2019 à 12:25 -0500, Jason L Tibbitts III a
> > écrit :
> > > > > > > > "KF&quo
Le mercredi 31 juillet 2019 à 21:05 +, Zbigniew Jędrzejewski-Szmek
a écrit :
> On Wed, Jul 31, 2019 at 08:52:36PM +0200, Nicolas Mailhot via devel
> wrote:
> > And when,
> > finally, systemd makes a new release, it does not even use
> > integrator
> > and automa
Le mercredi 31 juillet 2019 à 13:34 -0700, Kevin Fenzi a écrit :
> On 7/31/19 12:05 PM, Nicolas Mailhot via devel wrote:
> > Le mercredi 31 juillet 2019 à 12:25 -0500, Jason L Tibbitts III a
> > écrit :
> > > > > > > > "KF" == Kevin Fenzi wri
Le jeudi 01 août 2019 à 14:19 +0200, Lennart Poettering a écrit :
> On Do, 01.08.19 10:14, Fabio Valentini (decatho...@gmail.com) wrote:
>
> > Since these things are both the case, a simple 1:1 mapping from "-"
> > to
> > "~" (and even back) is exactly correct.
> > So I think the systemd.spec is
Le 2019-07-22 21:04, Jeremy Cline a écrit :
On Mon, Jul 22, 2019 at 06:59:04PM +0300, Alexander Bokovoy wrote:
On ma, 22 heinä 2019, Jeremy Cline wrote:
It is mostly due to supportability of the packages in Fedora. Java
products tend to be split into smaller packages and an overhead for
Le 2019-07-23 08:32, Alexander Bokovoy a écrit :
On ma, 22 heinä 2019, Jeremy Cline wrote:
On Mon, Jul 22, 2019 at 06:59:04PM +0300, Alexander Bokovoy wrote:
On ma, 22 heinä 2019, Jeremy Cline wrote:
> On Sun, Jul 21, 2019 at 05:37:10PM -0400, Neal Gompa wrote:
> > Keycloak is not generally
Le 2019-07-23 07:02, drago01 a écrit :
Please just take back this change and come back at April first if it
was supposed to be a joke - if not then submit again in about 10
years.
Fedora used to have the x86 repo for old hardware, and the x86_64 repo
for new hardware. Now that the tech
Le 2019-07-23 09:23, Mikolaj Izdebski a écrit :
On Mon, Jul 22, 2019 at 11:20 AM Nicolas Mailhot via devel
wrote:
Huge Red Hat investments, in the Java ecosystem, that fail to
translate
into an healthy Fedora Java ecosystem. To the point that when IBM
wants
its Java guys to join
Le 2019-07-23 12:48, Peter Robinson a écrit :
On Tue, Jul 23, 2019 at 11:31 AM Nicolas Mailhot via devel
wrote:
Le 2019-07-23 07:02, drago01 a écrit :
> Please just take back this change and come back at April first if it
> was supposed to be a joke - if not then submit again in ab
Le 2019-07-23 12:01, Fellipe Henrique a écrit :
Hi
First, Thanks very much for you reply...
I need to add a "global" argument so I can change the layer of a
repository... For example:
$ dnf repolist --set-layer=mylayer
$ dnf install -y any_repo --set-layer=mylayer
On our setup we
Le 2019-07-23 14:09, Stephen John Smoogen a écrit :
On Tue, 23 Jul 2019 at 08:00, Nicolas Mailhot via devel
wrote:
Le 2019-07-23 12:01, Fellipe Henrique a écrit :
Hi
First, Thanks very much for you reply...
I need to add a "global" argument so I can change the layer of a
As stated in
https://docs.fedoraproject.org/en-US/packaging-guidelines/PkgConfigBuildRequires/
pkgconfig(foo) is a more reliable marker of what ships the devel files,
than the package name.
It does not matter if the config process uses pkgconfig or not.
Depending on the package name is
Le 2019-07-18 15:51, Zdenek Dohnal a écrit :
On 7/18/19 3:39 PM, Vitaly Zaitsev via devel wrote:
Hello, Zdenek Dohnal.
Thu, 18 Jul 2019 13:44:56 +0200 you wrote:
What's your opinion? Is it useful feature of Vim and it should stay
as
default, or it needs to be disabled?
I think, that *.spec
Le vendredi 19 juillet 2019 à 08:48 +0200, Remi Collet a écrit :
> Le 18/07/2019 à 18:26, Nicolas Chauvet a écrit :
> > > "Build dependencies on Fedora packages which provide pkg-config
> > > files SHOULD be expressed
> > > as pkgconfig(foo) and not foo-devel, whether the dependent
> > > package
Hi,
Now that things are starting to move fonts-side[1], I’d like the various
actors to agree on a common font model target.
Without a a common target, we’ll end up working at odds with one
another. Upstream font files can not serve as a an officious target.
They are full of quirks, you end
Le 2019-07-24 13:49, Akira TAGOH a écrit :
Hi Akira
On Tue, Jul 23, 2019 at 10:45 PM Nicolas Mailhot
wrote:
No foo variable, foo hebrew, foo narrow, foo caption, just a single
foo
with different available features (full variability or fixed states on
the default axis, real upstream provided
The builsystem should rebuild all the other participants in the cycle against
the new link, then rebuild the new link against the updated cycle, then rebuild
again the rest of the cycle against the new link
If that fails, attempt to do the same with a bootstrap pass, hoping one of the
cycle
Le mercredi 24 juillet 2019 à 20:05 +0200, Clement Verna a écrit :
> On Wed, 24 Jul 2019 at 16:58, Matthew Miller <
> mat...@fedoraproject.org> wrote:
> > On Wed, Jul 24, 2019 at 07:09:24AM +0200, Clement Verna wrote:
> > > Last couple days a bigger change [2] have been introduced in the
> > >
Le mercredi 24 juillet 2019 à 14:37 +0200, Kevin Kofler a écrit :
Hi, Kevin
Thank you for taking the time to answer,
> Nicolas Mailhot wrote:
> > 2. fontconfig strives to hide all the legacy ways to designate
> > different
> > parts of this ideal font, and strives to expose a single "font"
> >
Le 2019-07-25 12:17, Björn Persson a écrit :
Hit,
An RPM spec is not a place for golfing. Readable code takes priority
over saving keystrokes.
Then it should be implemented cleanly in a declarative syntax,
with %{gpg_signatureX} and %{gpg_keyringX} variables matching
%{sourceX}, and a
Le 2019-07-22 10:22, Miro Hrončok a écrit :
Personally, I wish we had spent less engineering time in
infrastructure on Modularity and more on the contributor UX :(
It’s not just Modularity. Modularity is just a symptom. There is
something deeply broken in the Red Hat / Fedora interface.
Le 2019-07-22 17:29, Pierre-Yves Chibon a écrit :
On Mon, Jul 22, 2019 at 11:19:17AM +0200, Nicolas Mailhot via devel
wrote:
Le 2019-07-22 10:22, Miro Hrončok a écrit :
> Personally, I wish we had spent less engineering time in
> infrastructure on Modularity and more on the contribu
Le vendredi 28 juin 2019 à 09:06 -0700, Adam Williamson a écrit :
> On Fri, 2019-06-28 at 09:18 +0200, Nicolas Mailhot via devel wrote:
> > That's, easy,
> >
> > 1. add a generic bootctl install command that knows the different
> > variants of bootloader used in Fedor
Le samedi 15 juin 2019 à 20:13 +0200, Julen Landa Alustiza a écrit :
> I don't have a clear opinion on this, yet.
>
> In my use case I totally agree with you, I don't really need all this
> support, just a few thing are enough for me.
>
> But I understand that for the general non english
Le vendredi 05 juillet 2019 à 16:33 +0200, Christophe de Dinechin a
écrit :
>
> Also, would anybody mind if I add a note on the guideline page
> stating
> that this is from F31 on, since the go-rpm-macros package does not
> exist before. Unless there is a plan to create branches for earlier
>
Le mercredi 30 octobre 2019 à 12:53 -0400, Stephen John Smoogen a
écrit :
> On Wed, 30 Oct 2019 at 11:59, Iñaki Ucar
> wrote:
> > Hi all,
> >
> > I incidentally discovered today that, since quite recently, there's
> > a
> > Red Hat font [1]. And this led me to think about the popularity of
> >
Hi,
A fonts packaging policy rewrite proposal has been pushed to FPC today:
https://pagure.io/packaging-committee/pull-request/934
It should be clearer, more opinionated, and take into account:
– updates of The OpenType standard
– variable fonts
– web fonts
– upstream depreciation of non
Le samedi 09 novembre 2019 à 12:04 +0100, Nicolas Mailhot a écrit :
> Le samedi 09 novembre 2019 à 11:09 +0100, Tomasz Torcz a écrit :
> > On Thu, Nov 07, 2019 at 06:18:46PM +0100, Nicolas Mailhot via devel
> > wrote:
> > Here's a network management lesson for you:
&
Le samedi 09 novembre 2019 à 01:15 +0100, Sheogorath via devel a
écrit :
> And the owner should be able to delegate this decision to the
> network
> > manager.
> >
>
> Then let's talk on how we properly implement this delegation process
> instead of asking ourselves whenever we want DoH or DoT
Le samedi 09 novembre 2019 à 11:09 +0100, Tomasz Torcz a écrit :
> On Thu, Nov 07, 2019 at 06:18:46PM +0100, Nicolas Mailhot via devel
> wrote:
> > > >
> Here's a network management lesson for you:
> - run DoH resolver* not on ::1, but on IP available on your LAN
> -
Le samedi 09 novembre 2019 à 12:46 +0100, Marius Schwarz a écrit :
> Am 09.11.19 um 10:12 schrieb Nicolas Mailhot via devel:
> > That’s why DoH is intrinsically centralized and rotten to the core.
> >
> > DoH supporters are perfectly happy with a world where the
Le mercredi 06 novembre 2019 à 07:11 +0100, Tomasz Torcz a écrit :
> On Tue, Nov 05, 2019 at 10:00:17PM +0100, Nicolas Mailhot via devel
> wrote:
> > Le mardi 05 novembre 2019 à 19:45 +0100, Tomasz Torcz a écrit :
> > >
> > > I don't agree with centralisation
Le mardi 05 novembre 2019 à 19:45 +0100, Tomasz Torcz a écrit :
>
>
> I don't agree with centralisation. You should run your own DoH
> endpoint,
> using Google's, Cloudflare's or Quad9's servers is a shortcut.
DoH has zero integration and manageability. “It’s not centralized” (but
you have
Le jeudi 07 novembre 2019 à 18:32 +0100, Sheogorath via devel a écrit :
>
> The talk is right on many points, but I think it dismisses the most
> essential point DoH does right: DNS is a decision of the device
> owner.
And the owner should be able to delegate this decision to the network
Le 2019-11-13 10:14, Aleksandra Fedorova a écrit :
Exactly the same way as "stay away" won't work for automatic
BuildRequires generator feature, which we voted for in this cycle.
Sure you can, automated BRs are a specific section in the spec file,
staying away no more complex that not
Le 2019-11-13 07:39, Nicolas Mailhot a écrit :
Le mercredi 13 novembre 2019 à 06:43 +0100, Nicolas Mailhot via devel a
And anyway, if anyone feels the module design is actually needed (I
don’t, because the problems are elsewhere), it could have been *easily*
implemented within existing tools
Le mardi 12 novembre 2019 à 16:09 -0500, Stephen John Smoogen a écrit :
> On Tue, 12 Nov 2019 at 15:36, Stephen Gallagher
> wrote:
> > On Tue, Nov 12, 2019 at 12:40 PM Stephen John Smoogen <
> > smo...@gmail.com> wrote:
> > >
> > The technology allows you to do this. The policy can restrict
Le jeudi 14 novembre 2019 à 13:45 -0500, Stephen Gallagher a écrit :
> On Thu, Nov 14, 2019 at 1:33 PM John M. Harris Jr <
> joh...@splentity.com> wrote:
> > On Thursday, November 14, 2019 11:15:15 AM MST Stephen Gallagher
> > wrote:
> > > I'm not sure what you're asking here. I thought it was
Le 2019-11-14 22:01, Stephen Gallagher a écrit :
On Thu, Nov 14, 2019 at 4:00 PM Miro Hrončok
wrote:
On 14. 11. 19 21:32, Stephen Gallagher wrote:
>I proposed earlier around the major
> upgrade rebuilds (letting us set other modules as `buildrequires:` of
> `python: [ ]` for stream expansion)
Le 2019-11-12 10:06, Akira TAGOH a écrit :
On Tue, Nov 12, 2019 at 5:01 PM Nicolas Mailhot
wrote:
Hi Akira
https://copr.fedorainfracloud.org/coprs/nim/fonts-rpm-macros/builds/
showcases the new policy on 62 real-world source packages, generating
139 installation packages. Some of those are
Le mardi 12 novembre 2019 à 09:00 +0100, Nicolas Mailhot a écrit :
> Hi,
>
> A fonts packaging policy rewrite proposal has been pushed to FPC
> today:
> https://pagure.io/packaging-committee/pull-request/934
>
> It is based on the new fonts-rpm-macros project for automation:
Le mardi 12 novembre 2019 à 17:02 +0100, Aleksandra Fedorova a écrit :
> Hi, Igor,
>
> On Tue, Nov 12, 2019 at 4:20 PM Igor Gnatenko
> wrote:
> > >
> > > On Tue, Nov 12, 2019 at 10:50 AM Dominik 'Rathann' Mierzejewski
> > > wrote:
> > > >
> > So is it really about making tooling (writing new,
Hi Igor
On Fri, Nov 15, 2019, 10:03 Nicolas Mailhot via devel
wrote:
Le 2019-11-14 22:01, Stephen Gallagher a écrit :
wrote:
On 14. 11. 19 21:32, Stephen Gallagher wrote:
I proposed earlier around the major
upgrade rebuilds (letting us set other modules as
`buildrequires:` of
`python
Le samedi 16 novembre 2019 à 03:38 +0100, clime a écrit :
> > A true solution would be blending modularity into RPM.
> > At build time as well as at installation time.
>
> I agree this would be the best. Basically, final
> product of a module build should be an rpm. modulemd
> file should be kind
Le samedi 16 novembre 2019 à 09:35 +0100, Lukas Ruzicka a écrit :
>
>
> > Either the strategy should be:
> >
> > "We offer alternate Perl versions for containers etc. they conflict
> > with the
> > default Perl version and with the non-modular apps. That is known
> > and accepted."
That won't
Le samedi 16 novembre 2019 à 08:37 +0100, Nicolas Mailhot a écrit :
>
> Sure, do some rpm fixing if necessary so the result feels less like a
> kludge than %dist. But, don’t rely on an external framework to do
> things for you instead of doing the necessary work (if any) at the
> component format
Le samedi 16 novembre 2019 à 18:42 +0100, clime a écrit :
> On Sat, 16 Nov 2019 at 08:38, Nicolas Mailhot via devel
> wrote:
> > Le samedi 16 novembre 2019 à 03:38 +0100, clime a écrit :
> > > > A true solution would be blending modularity into RPM.
>
Le samedi 16 novembre 2019 à 19:05 +0100, clime a écrit :
> On Sat, 16 Nov 2019 at 18:54, Nicolas Mailhot via devel
> wrote:
> > Le samedi 16 novembre 2019 à 18:42 +0100, clime a écrit :
> > > On Sat, 16 Nov 2019 at 08:38, Nicolas Mailhot via devel
> > > wrote:
>
Le jeudi 21 novembre 2019 à 01:02 +0100, Kevin Kofler a écrit :
> Fabio Valentini wrote:
> > Today, builds submitted by MBS made up more than 80% of total
> > builds,
> > or over 5x the number of "normal" builds.
> > What an incredible waste of resources.
>
> Especially considering what small
Le mardi 10 décembre 2019 à 07:36 -0700, John M. Harris Jr a écrit :
> Most users,
> just like most American and UK users, set their keyboard layout to
> their primary layout, and then don't change it,
Actually, most non western users spend their time switching between
several input methods, one
Le jeudi 05 décembre 2019 à 16:42 -0700, John M. Harris Jr a écrit :
>
> Why in the world was Docker removed? Docker is the most popular
> container
> technology, so if we must embrace the "container" systems, why not
> include the most popular in Fedora?
Because moby (née docker) is a
Le mercredi 04 décembre 2019 à 20:50 -0700, Orion Poplawski a écrit :
>
> Interesting. Thrift appears to have pretty broken perl packaging as
> well (classes inside of files with a different name).
Thrift is broken for all languages (maybe not Java). It's upstream devs
Apache-side are trying
Le mercredi 04 décembre 2019 à 16:59 -0700, John M. Harris Jr a écrit :
> On Wednesday, December 4, 2019 12:38:20 PM MST Przemek Klosowski via
> devel
> wrote:
> > - stolen/lost laptop: I think this is the most important one for
> > most
> > people; it is mitigaged by a trusted-network-based
Le mercredi 04 décembre 2019 à 17:37 -0700, John M. Harris Jr a écrit :
>
> > The traditional way is unquestionably hostile to international
> > users,
> > and doing better, however untraditional, is absolutely something I
> > strongly favor.
>
> How is it "hostile to international users"?
Le mardi 26 novembre 2019 à 16:58 +0100, Igor Gnatenko a écrit :
Hi, Igor
> And we can't actually
> have multiple versions of a package with same name (without "mangled"
> names) in a repo due to the way how our buildsystem works (and not
> only buildsystem, with some caveats).
I suppose
Le 2019-11-27 11:45, Ian McInerney a écrit :
Tex isn't really the best example for the insane package numbers
(since the main Tex system, CTAN, actually does define them as
separate packages). It would be interesting to know if anyone actually
does just install one or two rather than all... I
Le samedi 30 novembre 2019 à 12:54 -0500, Neal Gompa a écrit :
> On Sat, Nov 30, 2019 at 12:49 PM Miro Hrončok
> wrote:
> > On 30. 11. 19 17:26, Dominik 'Rathann' Mierzejewski wrote:
> > >
> > > 2. It would be useful if it generated the file list
> > > automatically, too.
> > > I had to drop
Le lundi 02 décembre 2019 à 18:16 +, Zbigniew Jędrzejewski-Szmek a
écrit :
>
> How often do you ssh *into* your laptop?
I use the same tech desktop and home server side. If it does not work
on my home server, I don’t want to see it on my desktops. I have other
things to do in life than
1 - 100 of 313 matches
Mail list logo
