On Wed, Jan 16, 2019 at 2:35 AM Raphael Groner
wrote:
> Hi there,
>
> I tend to orphan winetricks. Reasons noted in the usability bug [¹] with
> known dependency issues, reported from an user.
> Besides, there are better alternatives available for my personal needs.
> Please feel free to request
#x27; composes, but now those went
away and we have these updates composes instead, it doesn't).
It seems the Atomic installer images from the nightly 'updates' and
'updates-testing' composes for F29 started failing as of 20190115.n.0
and still failed in 20190116.n.0.
On Wed, Jan 02, 2019 at 04:14:59PM -0500, Ben Cotton wrote:
> == Detailed Description ==
> At the time those interfaces have been implemented they internally
> relied on using the DES encryption algorithm, that today is widely
> considered unsecure and insufficient for applications which require
No missing expected images.
Failed openQA tests: 2/2 (x86_64)
ID: 345338 Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/345338
ID: 345339 Test: x86_64 AtomicHost-dvd_ostree-iso install_default
URL: https://openqa.fedoraproject.org
No missing expected images.
Failed openQA tests: 2/2 (x86_64)
Old failures (same test failed in testing-20190115.0):
ID: 345336 Test: x86_64 AtomicHost-dvd_ostree-iso install_default@uefi
URL: https://openqa.fedoraproject.org/tests/345336
ID: 345337 Test: x86_64 AtomicHost-dvd_ostree-i
Hi there,
I tend to orphan winetricks. Reasons noted in the usability bug [¹] with known
dependency issues, reported from an user.
Besides, there are better alternatives available for my personal needs.
Please feel free to request ownership for this package if you think it's still
useful in Fedo
splay the actual checkmark or dot or whatever to
indicate they are selected. This appears to be some sort of GNOME
component mismatch, or something, because a new gtk3 build appeared
just after the compose ran:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1179328
with that gtk3, this works f
On Tue, 2019-01-15 at 09:25 -0800, Adam Williamson wrote:
> On Tue, 2019-01-15 at 13:15 +0100, Emmanuel Seyman wrote:
> > * Jan Synacek [15/01/2019 12:45] :
> > > Unless I'm missing something, you have to use "External Trackers" on both
> > > sides. With "SeeAlso", you specified it in one bugzilla
On Tue, 2019-01-15 at 13:15 +0100, Emmanuel Seyman wrote:
> * Jan Synacek [15/01/2019 12:45] :
> > Unless I'm missing something, you have to use "External Trackers" on both
> > sides. With "SeeAlso", you specified it in one bugzilla and it
> > automatically showed in the referenced one.
>
> This o
On Tue, 2019-01-15 at 10:40 -0600, Richard Shaw wrote:
> Ooooaaa...
>
> So this has been around since at least 2017 and there's no fix?
Much longer than that. At least since 2012, probably earlier.
%exclude is discouraged, which is why it doesn't seem to have higher
priority. See also:
ht
=
#fedora-meeting-3: Weekly Meeting of the Modularity Working Group
=
Meeting started by nils at 15:00:00 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meetin
On Mon, Jan 14, 2019 at 07:58:43PM -0500, John Harris wrote:
> > Merging Core and Extras into one thing was absolutely the
> > right thing to do for the project, but not having a unique name for the
> > resulting OS was a mistake and leads to this. Ah well.
> In your opinion, is the purpose of the
Ooooaaa...
So this has been around since at least 2017 and there's no fix?
Is there an option to make it a warning again instead of an error?
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email t
OLD: Fedora-Rawhide-20190114.n.0
NEW: Fedora-Rawhide-20190115.n.0
= SUMMARY =
Added images:2
Dropped images: 0
Added packages: 4
Dropped packages:28
Upgraded packages: 271
Downgraded packages: 1
Size of added packages: 9.63 MiB
Size of dropped packages
After review, Fedora has determined that the Server Side Public License
v1 (SSPL) is not a Free Software License.
It is the belief of Fedora that the SSPL is intentionally crafted to be
aggressively discriminatory towards a specific class of users.
Additionally, it seems clear that the intent of t
Hi all,
a new version rpkg-1.57 is released.
This is mostly a bugfix update with improvements for building modules and
flatpaks
- Set configuration in case of "clone --branches" as well
- Send source mtime to dist-git
- Specify package manager for mock-config
- Add contributing guide
- Validate
Am Dienstag, den 15.01.2019, 15:20 +0100 schrieb Florian Weimer:
> * Simo Sorce:
>
> > > Maybe the stub implementation should just overwrite the argument
> > > with
> > > zeros.
> >
> > I wouldn't overwrite with zeros because then it is clear the
> > encryption
> > failed and if it is used in non
On Tue, Jan 15, 2019 at 1:59 PM Lennart Poettering wrote:
> Maybe use this instead:
>
>"count=fresh" → this is the first dnf invocation on a fresh install
>"count=monthly" → this is used the first time in every 29.53 day
> cycle, except if this is a fresh install
>
On Tue, Jan 15, 2019 at 7:42 AM Richard Shaw wrote:
> Is the %exclude just not working for the build-ids? That's all I can come up
> with.
See:
https://bugzilla.redhat.com/show_bug.cgi?id=878863
https://bugzilla.redhat.com/show_bug.cgi?id=1482698
--
Jerry James
http://www.jamezone.org/
On 15/01/2019 14:41, Richard Shaw wrote:
Is the %exclude just not working for the build-ids? That's all I can
come up with.
Well it is working, but it doesn't exclude them because they
don't match any of the patterns.
Those excludes only match files in %{_libdir} not in the .build-id
director
No missing expected images.
Compose FAILS proposed Rawhide gating check!
1 of 47 required tests failed
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 1/24 (i386), 10/132 (x86_64), 1/2 (arm)
New failures (same test not failed in Rawhide-201
I'm working on the recent release of mythtv and everything compiled fine
until I got to the rpm packaging part which I got the following output:
File listed twice:
/usr/lib/.build-id/01/02700911bb4fe728258f16703a35d816ddb31f
File listed twice:
/usr/lib/.build-id/5f/dc725022956f8f935afc0d29a
* Simo Sorce:
>> Maybe the stub implementation should just overwrite the argument with
>> zeros.
>
> I wouldn't overwrite with zeros because then it is clear the encryption
> failed and if it is used in non-orthodox ways could give an attacker a
> way to exploit the zeroing.
>
> (for example if so
On Thu, Jan 10, 2019 at 07:47:26PM -, Artur Iwicki wrote:
> - Now that I've mentioned it, maybe we should add something like "fedpkg
> fas-login"? Personally I've put "alias koji-init='kinit
> my-fas-acco...@my-domain.org'" in my .bashrc, because looking up how to solve
> the "koji says I'm
On Tue, 2019-01-15 at 14:51 +0100, Florian Weimer wrote:
> * Simo Sorce:
>
> > On Tue, 2019-01-15 at 10:39 +0100, Florian Weimer wrote:
> > > * Ben Cotton:
> > >
> > > > Remove real functionality from encrypt, encrypt_r, setkey, setkey_r,
> > > > and fcrypt from the libxcrypt.so.1 compatibility l
* Simo Sorce:
> On Tue, 2019-01-15 at 10:39 +0100, Florian Weimer wrote:
>> * Ben Cotton:
>>
>> > Remove real functionality from encrypt, encrypt_r, setkey, setkey_r,
>> > and fcrypt from the libxcrypt.so.1 compatibility library and let those
>> > functions set "errno" to "ENOSYS" when invoked.
>
On 15/01/2019 13:42, Simo Sorce wrote:
On Tue, 2019-01-15 at 10:39 +0100, Florian Weimer wrote:
* Ben Cotton:
Remove real functionality from encrypt, encrypt_r, setkey, setkey_r,
and fcrypt from the libxcrypt.so.1 compatibility library and let those
functions set "errno" to "ENOSYS" when invok
On Tue, 2019-01-15 at 10:39 +0100, Florian Weimer wrote:
> * Ben Cotton:
>
> > Remove real functionality from encrypt, encrypt_r, setkey, setkey_r,
> > and fcrypt from the libxcrypt.so.1 compatibility library and let those
> > functions set "errno" to "ENOSYS" when invoked.
>
> encrypt rewrites i
On Mo, 14.01.19 17:15, Ben Cotton (bcot...@redhat.com) wrote:
> # Add a new "countme" variable. This variable will:
> #* Start as a "true" value,
> #* Reset to a "false" value the first time the client successfully
> makes a request to Fedora mirror servers, and
> #* Be reset to a "true" value aft
* Jan Synacek [15/01/2019 12:45] :
>
> Unless I'm missing something, you have to use "External Trackers" on both
> sides. With "SeeAlso", you specified it in one bugzilla and it
> automatically showed in the referenced one.
This only works if both bugs are in the same instance. There's never been
On Tue, Jan 15, 2019 12:45:11 +0100, Jan Synacek wrote:
> On Tue, Jan 15, 2019 at 11:59 AM Emmanuel Seyman wrote:
>
> * Ankur Sinha [15/01/2019 10:21] :
> >
> > I've commented there also, but I'd like to learn how others go about it
> > without "see-also".
>
> Is there anythi
On Tue, Jan 15, 2019 at 11:59 AM Emmanuel Seyman wrote:
> * Ankur Sinha [15/01/2019 10:21] :
> >
> > I've commented there also, but I'd like to learn how others go about it
> > without "see-also".
>
> Is there anything you did with "see-also" that you can't do with
> the "External Trackers" featu
On Tue, Jan 15, 2019 11:58:51 +0100, Emmanuel Seyman wrote:
> * Ankur Sinha [15/01/2019 10:21] :
> >
> > I've commented there also, but I'd like to learn how others go about it
> > without "see-also".
>
> Is there anything you did with "see-also" that you can't do with
> the "External Trackers" fe
On Tue, Jan 15, 2019 10:33:34 +, Tom Hughes wrote:
> On 15/01/2019 10:21, Ankur Sinha wrote:
>
> > The bugzilla upgrade removed the "see-also" field which I found most
> > useful. Would anyone have any tips on reproducing its functionality in
> > the current version?
> >
> > A bug requesting
* Ankur Sinha [15/01/2019 10:21] :
>
> I've commented there also, but I'd like to learn how others go about it
> without "see-also".
Is there anything you did with "see-also" that you can't do with
the "External Trackers" feature?
Emmanuel
___
devel mai
On 15/01/2019 10:21, Ankur Sinha wrote:
The bugzilla upgrade removed the "see-also" field which I found most
useful. Would anyone have any tips on reproducing its functionality in
the current version?
A bug requesting that it be brought back has been closed as WONTFIX:
https://bugzilla.redhat.c
Hello,
The bugzilla upgrade removed the "see-also" field which I found most
useful. Would anyone have any tips on reproducing its functionality in
the current version?
A bug requesting that it be brought back has been closed as WONTFIX:
https://bugzilla.redhat.com/show_bug.cgi?id=1661164
I've co
* Ben Cotton:
> Remove real functionality from encrypt, encrypt_r, setkey, setkey_r,
> and fcrypt from the libxcrypt.so.1 compatibility library and let those
> functions set "errno" to "ENOSYS" when invoked.
encrypt rewrites its argument in place, so this will leave the argument
unencrypted. Thi
Hi Timothée,
sorry am a bit swamped with work. I should be able to get to them
week.
cheers,
Michele
On Tue, Jan 15, 2019 at 09:18:39AM +0100, Timothée Floure wrote:
> Hello,
>
> Does anyone here know how to contact mbaldessari? I can't get him to answer on
> RHBZ#1640405 [0].
>
> Output of `f
Hello,
Does anyone here know how to contact mbaldessari? I can't get him to answer on
RHBZ#1640405 [0].
Output of `fedora_active_user.py`:
```
Last login in FAS:
mbaldessari 2018-06-01
Last action on koji:
Tue, 04 Dec 2018 package list entry revoked: beets in trashcan by oscar
Last package
40 matches
Mail list logo
