Le vendredi 26 juin 2020 à 07:41 -0700, PGNet Dev a écrit :
> hi,
>
> On 6/25/20 11:58 PM, Nicolas Mailhot wrote:
> > forgemeta works in release mode, with release archives published
> > over
> > http(s). It does not talk at all to source projects using the gi
Le vendredi 26 juin 2020 à 07:41 -0700, PGNet Dev a écrit :
> hi,
>
> On 6/25/20 11:58 PM, Nicolas Mailhot wrote:
> > forgemeta works in release mode, with release archives published
> > over
> > http(s). It does not talk at all to source projects using the gi
their own boot in the process.
Thus, Anaconda EFI support is terrible period.
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https:
rformance points over the competition.
Therefore, using btrfs in Fedora, is inherently more ambitious, than
using it at Facebook.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le
not have an IT organisation to back it up in a professional way.
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedorapro
dware vendor did
not test fully, does not bode well for the reliability of the
integrated software+hardware system.
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorapro
mething. And, the last time a problem occurred, it was traced to an
undocumented and unannounced rpm change that no one knew how to fix
rpm-side, and that you spent more energy proving it need not be fixed
than on constructive solution-finding.
I freely admit that my code suck
t; redhat-rpm-config will be updated to add patching support to forge
> > macros, a plug-able framework to register macros to execute in
> > specific sections, and rpm changelogs in detached files.
> >
> > == Owner ==
> > * Name: [[User:nim| Nicolas Mailhot]]
> &
Le mardi 30 juin 2020 à 23:04 +0200, Nicolas Mailhot via devel a
écrit :
> Le mardi 30 juin 2020 à 21:45 +0200, Igor Raits a écrit :
> >
> > I think this would be already at least 30 times
That unpleasantness aside if anyone wants to engage in constructive
technical discussion,
, anyway. It'd be similar to the
> existing %packager macro, too.
This is certainly doable and will simplify the code. Therefore, I will
do it. I was formatted by the way name and email are separated in
.gitconfig
Please ask any other technical question you may have, they are helping
me to mak
lone when reinstalling, while someone always seems too
invent a new Fedora change that justifies the reformatting of /.
Good luck dealing with user data the next time workstation (or any
other group) feels the / filesystem should change, once you've put user
data on the same mount point
Regards
Le mercredi 01 juillet 2020 à 10:27 -0400, Neal Gompa a écrit :
> On Wed, Jul 1, 2020 at 10:26 AM Nicolas Mailhot via devel
> wrote:
> >
> > Le mercredi 01 juillet 2020 à 11:09 +, Zbigniew Jędrzejewski-
> > Szmek
> > a écrit :
> > >
> >
king the browser walk a remote location is not good for
performance and will have all kind of interesting effects in restricted
networks
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe se
ping rpmbuild results as usual and
exposing them to users.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedo
Le 2020-07-02 09:52, Florian Weimer a écrit :
* Nicolas Mailhot via devel:
How do I let rpm generate the changelog automatically?
This feature is not changelog generation, just changelog bumping on
build events. You still need some other method to put non-build events
in the changelog
Le 2020-07-02 09:59, Vitaly Zaitsev via devel a écrit :
On 02.07.2020 07:35, Nicolas Mailhot via devel wrote:
The detached changelog is just one more file in SRPM sources, which is
modified by rpmbuild at `%build` time with other files rpmbuild
modifies.
I don't like that. %changelog s
Le 2020-07-02 11:17, Nicolas Mailhot via devel a écrit :
This may seem a bit complex and convoluted, but that’s because
autobumping
https://fedoraproject.org/wiki/Changes/rpm_level_auto_release_and_changelog_bumping
is a small addition over the big %auto_macros change.
https
Le 2020-07-02 11:21, Igor Raits a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 2020-07-02 at 11:17 +0200, Nicolas Mailhot wrote:
Le 2020-07-02 09:52, Florian Weimer a écrit :
> * Nicolas Mailhot via devel:
>
> > > How do I let rpm generate the changelo
Le 2020-07-02 10:51, Miro Hrončok a écrit :
On 01. 07. 20 19:34, Nicolas Mailhot via devel wrote:
Le mercredi 01 juillet 2020 à 18:35 +0200, Miro Hrončok a écrit :
Given the /usr/share font links in CSS won't work when the
documentation is
exposed via a webserver, I assume the docs are m
Le 2020-07-02 11:38, Igor Raits a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Thu, 2020-07-02 at 11:27 +0200, Nicolas Mailhot via devel wrote:
Le 2020-07-02 09:59, Vitaly Zaitsev via devel a écrit :
> On 02.07.2020 07:35, Nicolas Mailhot via devel wrote:
> > The
Le 2020-07-02 11:59, Florian Weimer a écrit :
* Nicolas Mailhot via devel:
Le 2020-07-02 09:59, Vitaly Zaitsev via devel a écrit :
On 02.07.2020 07:35, Nicolas Mailhot via devel wrote:
The detached changelog is just one more file in SRPM sources, which
is
modified by rpmbuild at `%build
because tuning a production process is more
than the "it works" POC stage, but that’s tuning, not reconception).
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email t
Le July 2, 2020 2:47:49 PM UTC, Vitaly Zaitsev via devel
a écrit :
>On 02.07.2020 11:27, Nicolas Mailhot wrote:
>> Why? Koji schedules a build. The build registers its own build date
>in
>> the produced packages. Koji decides to keep and commit the result, or
>> drop i
build features that were devilishly hard to
implement before something like %auto_call was available, and is pretty
simple to do with %auto_call implemented
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscri
e server setup with systematic
backup/restore procedures.
For workstations? Even in an Enterprise context? Not so much.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an ema
Le 2020-07-02 15:11, Kamil Dudka a écrit :
On Thursday, July 2, 2020 1:02:05 PM CEST Nicolas Mailhot via devel
wrote:
If there is buy-in, it will be implemented by goodwill people. If
there
is no buy-in, it won’t, normal community development process. Put
yourself in the category you want to
ora downstreams (as AWS and others
already did).
(this is not an endorsement of any other position in this thread, I
hate all our bootloaders equally, they’ve been a lost cause since
someone decided to hide the bootloader menu in the default install,
makin
the git (or hg, or svn,
or…) command, it’s a pure URL munger, so it won’t pull in your scm of
choice in the buildroot.
Presumably your workflow is so git oriented your local setup always has
git installed.
Regards,
--
Nicolas Mailhot
___
d
Le vendredi 03 juillet 2020 à 10:06 +0200, Pierre-Yves Chibon a écrit :
> On Thu, Jul 02, 2020 at 03:44:51PM +0200, Nicolas Mailhot via devel
> wrote:
> > Le 2020-07-02 15:11, Kamil Dudka a écrit :
> > > On Thursday, July 2, 2020 1:02:05 PM CEST Nicolas Mailhot via
> >
Le vendredi 03 juillet 2020 à 09:48 +0200, Pierre-Yves Chibon a écrit :
> On Thu, Jul 02, 2020 at 12:10:58PM +0200, Björn Persson wrote:
> > Nicolas Mailhot wrote:
> > > The same process that commits a new state of the changelog file
> > > in
> > > sources,
>
Le vendredi 03 juillet 2020 à 11:03 +0200, Pavel Raiskup a écrit :
> On Friday, July 3, 2020 9:51:20 AM CEST Nicolas Mailhot via devel
> wrote:
> > it will certainly be possible to compute a second level of sources
> > during the dynamic buildrequires first pass over prep,
Le vendredi 03 juillet 2020 à 11:03 +0200, Pavel Raiskup a écrit :
>
> I'd appreciate the link to spectool rewrite, though.
Here it is:
https://pagure.io/rpmdevtools/blob/master/f/rpmdev-spectool
Regards,
--
Nicolas Mailhot
___
devel m
Le vendredi 03 juillet 2020 à 08:24 -0700, PGNet Dev a écrit :
>
>
> On 7/3/20 12:01 AM, Nicolas Mailhot wrote:
> > You added some processing that depends on the git command (that
> > forgemeta does not use) but forgot to BuildRequire the package
> > providing that c
th
people not in your own timezone.
Reagrds,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/projec
art up)
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guid
r’s experimental
system with current year’s experimentalk system because nothing had
settled yet.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code
https://fedoraproject.org/wiki/Changes/rpm_level_auto_release_and_changelog_bumping
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Cond
Le dimanche 05 juillet 2020 à 17:46 +0200, Björn Persson a écrit :
> Nicolas Mailhot via devel wrote:
> > So if you want to push Fedora release logic to its ultimate
> > conclusion,
> > the thing that should be in charge of committing the new
> > release/changelog build
Le dimanche 05 juillet 2020 à 18:41 +0200, Nicolas Mailhot a écrit :
>
> While timestamping would remove the need to pass the last build info
> to the next one it would also break all the workflows where several
> rebuilds are done in parallel for separate needs, and the latest
>
wrong with writing a spec for things not specified yet,
quite the countrary.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Le dimanche 05 juillet 2020 à 23:36 +0200, Dan Čermák a écrit :
> Nicolas Mailhot via devel writes:
>
> > Le dimanche 05 juillet 2020 à 17:46 +0200, Björn Persson a écrit :
> > > Nicolas Mailhot via devel wrote:
> > > > So if you want to push Fed
se for patches), but that could be changed if
people wanted it changed, and is an artefact of the general mess sources
and patches are in rpm, with layers over layers of confusing things
named almost the same, but not exactly the same.
Regards,
--
Nicolas Mailhot
__
to admit I am biaised. Had I not been convinced
it was the right approach, I would not have invested the coding time in
the first place.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsu
Le lundi 06 juillet 2020 à 13:06 +0200, Nicolas Mailhot a écrit :
>
> Because the build state exists in koji only, there is no need to
> commit back to git.
BTW I’m fairly certain I could have managed to implement the thing
without adding source files to the SRPM, removing the need
ing
editing the boot CLI).
Otherwise you end up in keypress & display timing hell (not to mention
that non-qwerty users have the additional hurdle of guessing where keys
are mapped, which is why using anything except escape/space and
function keys will break hard in the field).
Regards,
--
Le 2020-07-06 16:33, Gerd Hoffmann a écrit :
On Mon, Jul 06, 2020 at 03:45:45PM +0200, Nicolas Mailhot via devel
wrote:
Le lundi 06 juillet 2020 à 15:33 +0200, Gerd Hoffmann a écrit :
> Â Â Hi,
>
> See above. sd-boot allows to edit the kernel command line too. Same
> hotke
bump from here' info between builds.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/
doing their parts.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code
Facebook relies on to make btrfs
corruption non events, were available workstation side.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
hardware-side.
Leading to vast deployments of abandoware.
A lot of things, starting with the DRM target that funded secure boot,
would not exist if manufacturers were serious about updates, because
those systems are increadibly brittle and incompatible with a long term
support v
rtificate of this remote point, has zero need for secure
boot.
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.
Le vendredi 10 juillet 2020 à 07:51 -0400, Solomon Peachy a écrit :
> On Fri, Jul 10, 2020 at 01:37:14PM +0200, Nicolas Mailhot via devel
> wrote:
> > If you remove end users from the loop there is zero zip nada need
> > for
> > secure boot in the first place. The sole
g. And those buttons will keep working far after the IOT
manufacturer will have screwed up the software update part.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedo
Le vendredi 10 juillet 2020 à 13:22 +0200, Pavel Raiskup a écrit :
> On Wednesday, July 8, 2020 6:25:57 PM CEST Nicolas Mailhot via devel
> wrote:
> > Le 2020-07-08 17:19, Pavel Raiskup a écrit :
> >
> > > Small experiment (few-liner) for copr with "%bid, buil
Le vendredi 10 juillet 2020 à 14:59 +0200, Nicolas Mailhot a écrit :
> Le vendredi 10 juillet 2020 à 13:22 +0200, Pavel Raiskup a écrit :
> > On Wednesday, July 8, 2020 6:25:57 PM CEST Nicolas Mailhot via
> > devel
> > wrote:
> > > Le 2020-07-08 17:19, Pavel Raiskup
hardware is
an additional external expense. IOT manufacturers are first and
foremost hardware people, they sell devices not bags of bits, they know
how to make hardware as cheap as possible, and how to market hardware
features so the marginal cost does not cost them a dime.
Regards,
--
Nicola
Le dimanche 12 juillet 2020 à 13:07 -0700, Kevin Fenzi a écrit :
> On Sun, Jul 05, 2020 at 02:15:23PM +0200, Nicolas Mailhot via devel
> wrote:
> >
> > This is now done in the latest code refresh and in the test copr
> > https://src.fedoraproject.org/fork/nim/
ing cost of more English variants is their
footprint in language selectors
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
Le dimanche 19 juillet 2020 à 10:39 -0700, Kevin Fenzi a écrit :
> On Mon, Jul 13, 2020 at 10:17:11AM +0200, Nicolas Mailhot via devel
> wrote:
> > Tough it is a litteral key = value file with no fancy formatting
> > nor
> > even ini-like sections, and a handful of variabl
Alternatively, prepare to maintain the “Symbol” aliasing stack in
fontconfig (and fight with wine for it), because *no* *one* *else*
*cares* about this legacy Windows-specific stuff.
Fontconfig upstream already told this to R users in its own issue
tracker.
Regards
ing about the people you want to enroll.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US
Le mercredi 25 mars 2020 à 07:19 -0700, Troy Dawson a écrit :
> On Wed, Mar 25, 2020 at 6:15 AM Nicolas Mailhot via devel
> wrote:
> >
> > rpm state in EL prevents most downstreaming. Please focus efforts
> > there.
> >
> > I don’t see how you will
A picture is worth a thousand words. Please draw us what you are
attempting to achieve. That will make it so much easier for everyone
here to understand it.
And you can say “it’s only for @rh employees”. But that’s giving up on
making Fedora work as a community project.
Regards
e hassle to package and maintain
than the software it tests (and, with little to show for all this
bother).
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedo
dev-
side. But who is going to exercise packaging tools if packagers are
forbiddent to use them?
That being said, yes Fedora has been a terrible rpm stackaholder. That
has hurt both Fedora and rpm upstream. Half the NIH reinventing
packaging tools people just can not stand the delays associated wi
ted
yourself ssh accesss is not blameless either.
Gitlab and Github work in https mode. Pagure does not. End of story.
Expecting others to hole their security with corkscrew because of the
ssh holy cow was never going to impress any third party.
Regards,
--
Nicolas Mailhot
e strange.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List G
hing but accessory to the project.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/pr
I don’t say it is
impossible, but it is a huge gamble).
What I am sure, is that the CPE statement “Gitlab is cool because they
will think about the roadmap in our stead” is a complete
misunderstanding of what makes Fedora tick.
Regards,
--
Nicolas Mailhot
_
Le jeudi 02 avril 2020 à 10:04 +0200, Miro Hrončok a écrit :
>
> If there anything you need to add to the agenda, just ask and I'll
> add the tag.
https://pagure.io/packaging-committee/pull-request/951 please?
Will just wither away without FPC attention
Regards,
--
N
s of things use fonts server side, they’re not a desktop-only thing
(though on may argue the selection should be more minimal server-side)
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le..
o calls in my rawhide specs,
that evaluate to nothing for Fedora. *declarative* syntax is a lot less
scary maintenance-wise than free-form spec programming.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe s
rojects, in
various upstreams, on user systems, and years of fontconfig
documentation, referencing "fonts.dtd" without the urn protection. And,
a lot of people do not validate (*we* did not validate for years).
Just remember: if validation tools do not find the fontconfig
t careful when referencing stuff right and left.
https://docs.fedoraproject.org/en-US/packaging-guidelines/Golang/
It is, IMHO, a mistake to attempt packaging software, without reading
the Fedora guidelines, for the language this software is written in.
Regards,
--
Nicolas Mailhot
means enabling tests.
Good syntax does not need line-by-line comments.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of
nes and the list. But, it
is a bias in favor of people who do stuff, and use the list to
coordinate, ie the portion of the packaging community you least want to
ignore, because they pull all the others.
--
Nicolas Mailhot
___
devel mailing list -- deve
y* activity. As in, the packager finished something, and
was active a specific week landing the result in Fedora. It does not
count all what happens outside Fedora infra before the result lands.
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fe
ths before stable branching and only land
sporadic fixes in between.
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.
en-US/packaging-guidelines/SourceURL/
> (that I just read)
While documented and official %forge macro use is not mandatory in
Fedora (of course, if you do things some other way, and the result
breaks, you ’ve no excuse for the breakage)
Regards,
--
Nicolas Mailhot
___
There is a problem right now with the part of koji that tags builds and
adds them to the various repos koji uses for new builds. So you can
build new packages, but can not rely on further builds seeing your
just-built packages.
--
Nicolas Mailhot
9.1.0 package.
Then use .el.9.dev. That should still order mostly fine, and the dev
bit will scare away any corp user.
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorapr
Le mercredi 14 août 2019 à 23:50 -0400, James Antill a écrit :
> Following is the list of topics that will be discussed in the FPC
> meeting
Sadly, I find myself forced to request adding
https://pagure.io/packaging-committee/issue/968
to FPC‘s agenda
Regards,
--
Nicolas M
, mock or Fedora git.
Regards,
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of
y refusing the
short-termist non future-proof self-defeating shortcuts that plague
some of Fedora’s downstreams.
Fedora takes the long view. Over a significant span of time, that
produces better results than quick hacks.
Regards,
--
Nicolas Mailhot
___
de
is not
> valid, I think.
Right now Fedora guidelines can not handle Go modules, and they are
just as likely to be removed altogether (with the corresponding
packages) than built on further, due to backwards-breaking rpm changes.
--
Nicolas Mailhot
___
ur of just a few % of distribution packages,
you need to be extra careful.
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs
complex spec file.
The rpm parser will now insult you with messages like
warning: undefined macro(s) in %{_sourcedir}:
/var/lib/builder/rpmbuild/SOURCES/%{name}
if you try to use %{name} at the srpm level.
This is an rpm 4.15 change
https://src.fedoraproject.org/rpms/redhat-rpm-config/pull-
For example, I see we have a
java-1.8.0-openjdk
java-11-openjdk
java-latest-openjdk
As you see the magic '-' makes it possible to use non-numeric version
qualifiers later without breaking naming conventions.
Regards
--
Nicolas Mailhot
___
devel
sed the special case in compat guidelines,
ignoring distribution history that showed versionned naming could
easily be done without special cases that annoys humans and break
automation and scripts for years afterwards, therefore, do as you want.
--
Nicolas Mail
n. Of course before you apply such automation you
start by filtering package names in some way. What you do *not* want to
do is use two different processing patterns instead of one.
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproje
Le mercredi 29 avril 2020 à 19:43 +0200, Miro Hrončok a écrit :
> On 29. 04. 20 19:37, Nicolas Mailhot wrote:
> > Le mercredi 29 avril 2020 à 19:18 +0200, Miro Hrončok a écrit :
> >
> > > All [compat packages] MUST include the base name suffixed by
> > > eithe
. The Go macro code will
just dump -qualifier- in the name without bothering with arcane testing
for example.
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.
ampire is
probably not, vnumericsomething may be a version with some made up
pre/post release garbage at the end, or something else entirely.
All because Linus did not bother defining a clean version separator
but reused the v letter, because “it was obvious”
Le jeudi 30 avril 2020 à 10:03 +0200, Nicolas Mailhot a écrit :
>
> Clever “it’s obvious in the few cases we imagine today, we do not
> need a clean version separator” syntaxes fail hard once exposed to
> the real world.
Also, to get back to the original subject, the whole py
Le jeudi 30 avril 2020 à 10:03 +0200, Nicolas Mailhot a écrit :
>
> Old human languages did not use word separators like space in
> writing, because "everyone knew" where one word started and the next
> finished. Even scholars that spent their life studying one of those
>
Le jeudi 30 avril 2020 à 10:49 +0200, Petr Šabata a écrit :
> On Tue, Apr 28, 2020 at 9:55 AM Nicolas Mailhot via devel
> wrote:
> > Le mardi 28 avril 2020 à 08:43 +0200, Petr Pisar a écrit :
> > > On Mon, Apr 27, 2020 at 04:33:52PM +0200, Petr Šabata wrote:
> &
route, it was not their best decision.
Regards
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org
lease will probably error not
warn on those.
warning: undefined macro(s) in %{_sourcedir}:
…/rpmbuild/SOURCES/%{name}
You may fool things for a while with the %_rpmtopdir + %{?name:%name}
but I doubt that will survive the purge long.
Regards,
--
Nicolas Mailhot
__
impossible to
contribute to independently without cloning its complex closed garden
environment.
Every Fedora package has a dual upstream, the source project for the
project code, and Fedora rpm/macro enhancements for the spec code.
Regards,
--
Nicolas Mailhot
was actually build in what order. That can never work reliably.
Just bite the bullet, builds are controlled by the build system, no one
*but* the build system can record them accurately in Fedora git.
Regards
--
Nicolas Mailhot
___
devel mailing list
801 - 900 of 1099 matches
Mail list logo
