On Mon, 29 Apr 2024, Jan Rękorajski wrote:
> On Mon, 29 Apr 2024, Jakub Bogusz wrote:
>
> > What happens here?
> > ENOSPC?
> >
> > Offending file is ~700MB big.
>
> Yeah, cvs/git vm is out of disk space (that's where the files are
> fetched):
>
> /dev/mapper/cvs-cvs xfs45G 45G 316M
On Mon, 29 Apr 2024, Jakub Bogusz wrote:
> What happens here?
> ENOSPC?
>
> Offending file is ~700MB big.
Yeah, cvs/git vm is out of disk space (that's where the files are
fetched):
/dev/mapper/cvs-cvs xfs45G 45G 316M 100% /cvs/root
Who can run lvextend/xfs_resize there?
> On Mon,
What happens here?
ENOSPC?
Offending file is ~700MB big.
On Mon, Apr 29, 2024 at 09:04:51PM +0200, qboosh wrote:
> Request by: qboosh
>
> FATAL: cannot move ./upload/kicad-packages3D-8.0.2.tar.bz2 to
> ./tmp/87b03bfe-24d2-4f8c-bd46-d36c7fcaba9b
> ERROR: cannot write
>
On 22/04/2024 20:58, Jakub Bogusz wrote:
Since Saturday new packages don't appear in th-test.
Could it be fixed?
ENOSPC on ftp disk and stale locks... fixed.
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
___
pld-devel-en mailing
Dnia Sat, Mar 30, 2024 at 01:57:22PM +0100, Jan Palus napisał(a):
> On 30.03.2024 01:49, arekm wrote:
> > commit b369fe78b7b4a02e900fb6fe7ac035a9bba39436
> > Author: Arkadiusz Miśkiewicz
> > Date: Fri Mar 29 23:50:59 2024 +0100
> >
> > Revert back to 5.4.6 as 5.6.x are BACKDOORED!
> >
On 30.03.2024 01:49, arekm wrote:
> commit b369fe78b7b4a02e900fb6fe7ac035a9bba39436
> Author: Arkadiusz Miśkiewicz
> Date: Fri Mar 29 23:50:59 2024 +0100
>
> Revert back to 5.4.6 as 5.6.x are BACKDOORED!
> https://www.openwall.com/lists/oss-security/2024/03/29/4
>
> xz.spec | 4 ++--
>
On 25/03/2024 10:22, Jan Palus wrote:
On 25.03.2024 11:05, arekm wrote:
commit d073fb40c26996aedc0c52fdea5af8b596e4f395
Author: Arkadiusz Miśkiewicz
Date: Mon Mar 25 09:58:15 2024 +0100
python points to python3 now
python3.spec | 4
1 file changed, 4 insertions(+)
---
diff
On 25.03.2024 11:05, arekm wrote:
> commit d073fb40c26996aedc0c52fdea5af8b596e4f395
> Author: Arkadiusz Miśkiewicz
> Date: Mon Mar 25 09:58:15 2024 +0100
>
> python points to python3 now
>
> python3.spec | 4
> 1 file changed, 4 insertions(+)
> ---
> diff --git a/python3.spec
On Sun, Mar 10, 2024 at 10:56:22AM +0100, Jan Palus wrote:
> Shouldn't it be the other way around -- "bootstrap" bcond in glib2 for
> building without introspection? Currently while gobject-introspection
> does not build-time depend on glib2-devel >= 2.80, it does runtime
> depend on glib2 >= 2.80
On 09.03.2024 22:33, qboosh wrote:
> commit a0c12f9cf03d0222dbb6357f6da0f70e72260664
> Author: Jakub Bogusz
> Date: Sat Mar 9 22:31:00 2024 +0100
>
> - updated to 1.80.0; added bootstrap bcond for glib 2.78->2.80 transition
>
> gobject-introspection.spec | 55
>
On Sun, Feb 04, 2024 at 03:04:21PM +0100, Witold Filipczyk via pld-devel-en
wrote:
> Dnia Sat, Feb 03, 2024 at 08:56:25PM +0100, Jakub Bogusz napisał(a):
> > On Sat, Feb 03, 2024 at 08:39:39PM +0100, witekfl wrote:
> > > commit 3b3013be1262989c7a7df78ffab6d797766b6486
> > > Author: Witold
On 05/02/2024 02:02, Jan Palus wrote:
I've tried to replicate the env (i686 VM, XFS) but without success. Not
sure if it's block device driver? XFS? or something else? Can't do much
more without ability to reproduce. Any ideas are welcome.
All builders run on the same physical machine as VMs
On 05.02.2024 00:50, PLD th-i686 builder wrote:
> test.spec (cryptsetup-debug): FAILED
...
> + test cafa743b687f1581b71a20ebfc068f9fe12653e945c417311b861c9217e66adf '='
> 06e2f159d6d541169da75222a7f0bedd0fc700502d63809f577b48f41eace335
Something concerning is going on i686/x32 builders. All
Dnia Sat, Feb 03, 2024 at 08:56:25PM +0100, Jakub Bogusz napisał(a):
> On Sat, Feb 03, 2024 at 08:39:39PM +0100, witekfl wrote:
> > commit 3b3013be1262989c7a7df78ffab6d797766b6486
> > Author: Witold Filipczyk
> > Date: Sat Feb 3 20:24:04 2024 +0100
> >
> > - updated to 5.249.0; rel 0.1
> >
On Sat, Feb 03, 2024 at 08:39:39PM +0100, witekfl wrote:
> commit 3b3013be1262989c7a7df78ffab6d797766b6486
> Author: Witold Filipczyk
> Date: Sat Feb 3 20:24:04 2024 +0100
>
> - updated to 5.249.0; rel 0.1
>
> kf5-attica.spec | 41 -
> 1 file
On 02/02/2024 00:14, Jan Palus wrote:
None of packages built today on builders is available on ftp.
Can someone check?
Something bad happened on ep09 machine (which is main ftp machine;
doesn't let ssh in; disconnects).
No idea who else beside RMF has access to console on this VM.
--
On Fri, 05 Jan 2024, Jan Palus wrote:
> On 23.12.2023 10:53, baggins wrote:
> > commit 201cb6739a14557a0ec8bf7c3dd171b4fc06afeb
> > Author: Jan Rękorajski
> > Date: Sat Dec 23 09:24:52 2023 +0100
> >
> > - add triggers for removed modules
> >
> > pam.spec | 10 +-
> > 1 file
On 23.12.2023 10:53, baggins wrote:
> commit 201cb6739a14557a0ec8bf7c3dd171b4fc06afeb
> Author: Jan Rękorajski
> Date: Sat Dec 23 09:24:52 2023 +0100
>
> - add triggers for removed modules
>
> pam.spec | 10 +-
> 1 file changed, 9 insertions(+), 1 deletion(-)
> ---
> diff --git
On 31.12.2023 13:10, atler wrote:
> Request by: atler
>
> scp problems: scp -pr -B -q
> ./tmp/a3fa32b0-8779-4bcb-a2b9-de2c39648f88/6eeab51025bb3492aa197d7d32be3184/
> pldd...@distfiles.pld-linux.org:ftp//by-md5/6/e:
> scp: Connection closed
>
> The command has exited with a non-zero status.
>
On Fri, Oct 20, 2023 at 07:01:56PM +0200, arekm wrote:
> commit 616994dbf9872356085c234c4c1efaa050d74ce3
> Author: Arkadiusz Miśkiewicz
> Date: Fri Oct 20 19:01:24 2023 +0200
>
> Started work on 8.1.0 upgrade and also started making this package
> coinstallable with other
On Mon, Oct 09, 2023 at 02:59:52PM +0200, atler wrote:
> commit dabbd0362fbd2a2345f450a5efceb62eb321741b
> Author: Jan Palus
> Date: Mon Oct 9 14:11:26 2023 +0200
>
> fix build with doc; rel 2
>
> replace unicode apostrophe with ascii one. from:
>
On 12.07.2023 17:10, Mateusz Kocielski wrote:
> Dnia Wed, Jul 12, 2023 at 01:22:08PM +0200, Jan Palus napisał(a):
> >
> > Override pam configuration shipped with i3lock with custom one that has:
> >
> > auth include system-auth
> >
> > just like (all?) other screensavers/lockers and
Dnia Wed, Jul 12, 2023 at 01:22:08PM +0200, Jan Palus napisał(a):
>
> Override pam configuration shipped with i3lock with custom one that has:
>
> auth include system-auth
>
> just like (all?) other screensavers/lockers and it should be fine.
>
> Other than this
>
> 1. Fix case in
On 11.07.2023 20:30, Mateusz Kocielski wrote:
> Dnia Tue, Jul 11, 2023 at 03:59:41PM +, Mateusz Kocielski napisał(a):
> > > That's peculiar -- what screen locker needs suid bit for? Why wheel
> > > group?
> >
> > Wheel group is taken from my BSD heritage I guess, fixed it. :) It requires
> >
Dnia Tue, Jul 11, 2023 at 03:59:41PM +, Mateusz Kocielski napisał(a):
> > That's peculiar -- what screen locker needs suid bit for? Why wheel
> > group?
>
> Wheel group is taken from my BSD heritage I guess, fixed it. :) It requires
> PAM for an authentication.
>
> > >
Dnia Tue, Jul 11, 2023 at 01:36:19PM +0200, Jan Palus napisał(a):
> Hi,
>
> thanks for contributing! Overall looks good. Some comments below.
>
Hello,
thanks for your helpful comments, below my comments and fixed version of the
spec.
> > Summary:improved screen locker
>
> Start summary
Hi,
thanks for contributing! Overall looks good. Some comments below.
On 11.07.2023 10:29, Mateusz Kocielski wrote:
> Hi there,
>
> I've prepared spec file to build i3lock [1]. This is my first spec file, so
> please review it carefully. The software requires suid to be able to verify
>
On 26.06.2023 10:38, Arkadiusz Miśkiewicz via pld-devel-en wrote:
> On 26.06.2023 10:31, atler wrote:
> > On 26.06.2023 11:24, atler wrote:
> > > Request by: atler
> > >
> > >
> > > Files fetched: 1
> > >
> > > ALREADY GOT:
> > >
On 26.06.2023 10:31, atler wrote:
On 26.06.2023 11:24, atler wrote:
Request by: atler
Files fetched: 1
ALREADY GOT:
https://download.savannah.gnu.org/releases/freetype/freetype-2.13.1.tar.xz
e4c3f0d8453a2a7993ae784912d6f19a freetype-2.13.1.tar.xz
STORED:
On 26.06.2023 11:24, atler wrote:
> Request by: atler
>
>
> Files fetched: 1
>
> ALREADY GOT:
> https://download.savannah.gnu.org/releases/freetype/freetype-2.13.1.tar.xz
> e4c3f0d8453a2a7993ae784912d6f19a freetype-2.13.1.tar.xz
> STORED:
>
On Sat, 24 Jun 2023, Jan Palus wrote:
> $ dnf clean all
> $ dnf download rpm-whiteout
> PLD Linux (Th) - Architecture specific
> 16 MB/s | 17 MB 00:01
> PLD Linux (Th) - Architecture independent
On 26.05.2023 02:18, Jan Palus wrote:
On 25.05.2023 15:41, Krzysztof Mrozowicz via pld-devel-en wrote:
Dnia 2023-05-25, o godz. 14:59:56
Jan Palus [1] napisal/(a):
Yes, that's after reboot. Could be Mesa, it's upgraded too..
Do you mind sharing output (remmina.strace) of:
strace -o
On 25.05.2023 15:41, Krzysztof Mrozowicz via pld-devel-en wrote:
> Dnia 2023-05-25, o godz. 14:59:56
> Jan Palus napisał(a):
>
> > >
> > >Yes, that's after reboot. Could be Mesa, it's upgraded too..
> >
> > Do you mind sharing output (remmina.strace) of:
> >
> > strace -o remmina.strace
Dnia 2023-05-25, o godz. 14:59:56
Jan Palus napisał(a):
> >
> >Yes, that's after reboot. Could be Mesa, it's upgraded too..
>
> Do you mind sharing output (remmina.strace) of:
>
> strace -o remmina.strace -f -e '/open.*' -z remmina
I observe a similar problem on my computer. The strace
On 25.05.2023 13:14, Andrzej Zawadzki wrote:
>On 25.05.2023 12:35, Jan Palus wrote:
>
> On 25.05.2023 12:04, Andrzej Zawadzki wrote:
>
>Hi!
>
>$ remmina
>** Message: 11:54:59.423: Remmina does not log all output statements.
>Turn on more verbose output by using
On 25.05.2023 12:35, Jan Palus wrote:
On 25.05.2023 12:04, Andrzej Zawadzki wrote:
Hi!
$ remmina
** Message: 11:54:59.423: Remmina does not log all output statements.
Turn on more verbose output by using "G_MESSAGES_DEBUG=all" as an
environment variable.
More info available
On 25.05.2023 12:04, Andrzej Zawadzki wrote:
>Hi!
>
>$ remmina
>** Message: 11:54:59.423: Remmina does not log all output statements.
>Turn on more verbose output by using "G_MESSAGES_DEBUG=all" as an
>environment variable.
>More info available on the Remmina wiki at:
>
On Fri, Jul 22, 2022 at 11:03:54AM +0200, Jan Rękorajski wrote:
> Can someone explain why are we using split sources/packages for Qt?
Beside build time and space requirements, I see one more reason now:
rebuilding after dependent package soname change is more painful.
Current case: jasper 3.x.
On 24.03.2023 12:42, Jan Palus wrote:
That's expected and GitHub host key needs an update, see:
https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/
Updated.
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
___
pld-devel-en
On 22.02.2023 21:38, Jan Palus wrote:
On 22.02.2023 19:55, glen wrote:
commit fa6a978633bd3fbae3c510fb6299ddb67af8da00
Author: Elan Ruusamäe
Date: Wed Feb 22 20:54:40 2023 +0200
Add _metainfodir, rev 2.023
-
On 22.02.2023 19:55, glen wrote:
> commit fa6a978633bd3fbae3c510fb6299ddb67af8da00
> Author: Elan Ruusamäe
> Date: Wed Feb 22 20:54:40 2023 +0200
>
> Add _metainfodir, rev 2.023
>
> -
>
On 30.01.2023 14:26, atler wrote:
-%define_noautoreq 'perl(path_tre)'
+%define_noautoreq perl\\(path_tre\\)
just use _noautoreq_perl
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
W dniu wt., 7.02.2023 o 21:37 Arkadiusz Miśkiewicz via pld-devel-en <
pld-devel-en@lists.pld-linux.org> napisał(a):
> 123...
Nope, doesn't work.
--
Łukasz [Deejay1] Jernaś
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
Dnia wtorek, 7 lutego 2023 21:37:29 CET Arkadiusz Miśkiewicz via pld-devel-en
pisze:
> 123...
Seems to work.
--
Łukasz Maśko_o)
Lukasz.Masko(at)ipipan.waw.pl /\\
Registered Linux User #61028
On 20.01.2023 22:04, Jakub Bogusz wrote:
On Thu, Jan 19, 2023 at 09:14:51AM +0100, Arkadiusz Miśkiewicz via pld-devel-en
wrote:
On 18.01.2023 16:08, Jakub Bogusz wrote:
Could rust be installed on carme-x32?
I'd like to (try to) fix mozjs102 build (required for new gjs), but
I cannot install
On Thu, Jan 19, 2023 at 09:14:51AM +0100, Arkadiusz Miśkiewicz via pld-devel-en
wrote:
> On 18.01.2023 16:08, Jakub Bogusz wrote:
> >Could rust be installed on carme-x32?
> >
> >I'd like to (try to) fix mozjs102 build (required for new gjs), but
> >I cannot install rust myself because of x86_64
On 18.01.2023 16:08, Jakub Bogusz wrote:
Could rust be installed on carme-x32?
I'd like to (try to) fix mozjs102 build (required for new gjs), but
I cannot install rust myself because of x86_64 packages requirements.
Should be available now.
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl |
On 18.01.2023 16:48, Jakub Bogusz wrote:
> On Wed, Jan 18, 2023 at 01:02:34PM +0100, Arkadiusz Miśkiewicz via
> pld-devel-en wrote:
> > On 18.01.2023 09:56, Jan Palus wrote:
> > >On 18.01.2023 07:54, Arkadiusz Miśkiewicz via pld-devel-en wrote:
> > >>On 17.01.2023 12:23, Jan Palus wrote:
> >
On Wed, Jan 18, 2023 at 01:02:34PM +0100, Arkadiusz Miśkiewicz via pld-devel-en
wrote:
> On 18.01.2023 09:56, Jan Palus wrote:
> >On 18.01.2023 07:54, Arkadiusz Miśkiewicz via pld-devel-en wrote:
> >>On 17.01.2023 12:23, Jan Palus wrote:
> >>>Noticed during build of
On 18.01.2023 09:56, Jan Palus wrote:
On 18.01.2023 07:54, Arkadiusz Miśkiewicz via pld-devel-en wrote:
On 17.01.2023 12:23, Jan Palus wrote:
Noticed during build of kodi-addon-inputstream-adaptive that contrary to
x86_64 and i686, x32 builder downloaded external sources successfully:
bind
On 18.01.2023 07:54, Arkadiusz Miśkiewicz via pld-devel-en wrote:
> On 17.01.2023 12:23, Jan Palus wrote:
> > Noticed during build of kodi-addon-inputstream-adaptive that contrary to
> > x86_64 and i686, x32 builder downloaded external sources successfully:
>
> bind was installed there and seems
On 17.01.2023 12:23, Jan Palus wrote:
Noticed during build of kodi-addon-inputstream-adaptive that contrary to
x86_64 and i686, x32 builder downloaded external sources successfully:
bind was installed there and seems that even if there is no access to
/etc/resolv.conf glibc fallbacks to
On 22.12.2022 11:49, Arkadiusz Miśkiewicz via pld-devel-en wrote:
> udev-core change:
>
> -Requires: uname(release) >= 3.13
> +Requires: uname(release) >= 4.15
>
>
> Is this true requirement?
This R: was updated purely based on very first entry in release notes for 251:
On 30.10.2022 18:08, Jan Palus wrote:
On 24.10.2022 09:17, Jan Palus wrote:
On 24.10.2022 09:13, atler wrote:
Request by: atler
wget -nv --no-iri --user-agent=PLD/distfiles -O
./tmp/c988e5de-3fbe-4f8d-9c0e-892a6cc71ea2/bc928a9897698ec397b11c3dbff40e53/qt-everywhere-src-6.3.2.tar.xz
On 24.10.2022 09:17, Jan Palus wrote:
> On 24.10.2022 09:13, atler wrote:
> > Request by: atler
> >
> > wget -nv --no-iri --user-agent=PLD/distfiles -O
> > ./tmp/c988e5de-3fbe-4f8d-9c0e-892a6cc71ea2/bc928a9897698ec397b11c3dbff40e53/qt-everywhere-src-6.3.2.tar.xz
> >
> >
On 24.10.2022 09:13, atler wrote:
> Request by: atler
>
> wget -nv --no-iri --user-agent=PLD/distfiles -O
> ./tmp/c988e5de-3fbe-4f8d-9c0e-892a6cc71ea2/bc928a9897698ec397b11c3dbff40e53/qt-everywhere-src-6.3.2.tar.xz
>
>
> On 20. Oct 2022, at 15:37, Elan Ruusamäe wrote:
>
>
>
> pldth@ep09-pld SRPMS/.metadata$ pfa-signpkg test *pecl*
> Checking signatures of 164 files from 17 packages
> 164/164
> /home/pld/admins/th/ftp/test/x86_64/debuginfo/php82-pecl-xmlrpc-debugsource-1.0.0-1.RC3.1.x86_64.rpm
> Total 164
On Mon, Oct 17, 2022 at 09:14:27PM +0300, Elan Ruusamäe wrote:
> wth. how is this any good?
>
> just add the -n python3-git-filter-repo to main git-filter-repo package!
>
> with your package split and the require-line in old spec, you force us
> to keep two .spec files up todate with each
wth. how is this any good?
just add the -n python3-git-filter-repo to main git-filter-repo package!
with your package split and the require-line in old spec, you force us
to keep two .spec files up todate with each release of git-filter-repo,
additionally deal with sending to builders, and in
On Sat, 24 Sep 2022, Jan Palus wrote:
> For some time now freshness report at
> http://ep09.pld-linux.org/~pldth/qa.php?q=freshness does not seem to be
> updated. Can someone have a look?
Fixed. Leftover lock in SPECS repo :/
--
Jan Rękorajski| PLD/Linux
SysAdm |
On Mon, Sep 19, 2022 at 6:08 PM Elan Ruusamäe wrote:
>
> rpm-4.17.1.1-1.x86_64
>
> dokuwiki* packages don’t build due that:
>
> ```
>
> + %{_usrlibrpm}/dokuwiki-find-lang.sh
> /home/users/glen/tmp/dokuwiki-20180422c-x86_64-root-glen dokuwiki.lang
> /home/users/glen/tmp/rpm-tmp.oRtxaL[82]:
On 14.09.2022 10:29, Andrzej Zawadzki wrote:
>On 14.09.2022 01:40, Krzysztof Mrozowicz via pld-devel-en wrote:
>
> Dnia 2022-09-13, o godz. 16:15:06
> Andrzej Zawadzki [1] napisal/(a):
>
>
>Qt 5.15.6 - similar problem. For example kwallet doesn't work with
>NetworkManager.
>
>
Dnia 2022-09-14, o godz. 10:29:58
Andrzej Zawadzki napisał(a):
> Works now.
>
> But... should KDE be strictly dependent on the Qt version?
>
> Second time when Qt update broke my KDE environment.
As a non-programmer, I'm guessing that KDE expects that all its
components will be build with the
On 14.09.2022 01:40, Krzysztof Mrozowicz via pld-devel-en wrote:
Dnia 2022-09-13, o godz. 16:15:06
Andrzej Zawadzki [1] napisal/(a):
Qt 5.15.6 - similar problem. For example kwallet doesn't work with
NetworkManager.
Downgrade help, so looks like after Qt upgrade rebuild off all
Dnia 2022-09-13, o godz. 16:15:06
Andrzej Zawadzki napisał(a):
>Qt 5.15.6 - similar problem. For example kwallet doesn't work with
>NetworkManager.
>
>Downgrade help, so looks like after Qt upgrade rebuild off all kde5
>packages will help.
I sent all ka5 and kp5 packages to
On 1.07.2022 19:22, Peri Noid wrote:
Dnia piatek, 1 lipca 2022 14:31:04 CEST Andrzej Zawadzki pisze:
OK Qt5 was to fresh. I found in logs:
*plasmashell[2012]: Cannot mix incompatible Qt library (5.15.4) with this
library (5.15.5)*
Hmm, rebuild is needed?
I did a full downgrade of Qt5 to
> On 31. Aug 2022, at 13:21, Jan Rękorajski wrote:
>
> On Wed, Aug 31, 2022 at 11:41 AM Arkadiusz Miśkiewicz via pld-devel-en
> wrote:
>>
>> On 31.08.2022 11:27, Jan Rękorajski wrote:
>>> Where will it land now? If you want to protect against landing in
>>> non-existing directory you can use
On Wed, Aug 31, 2022 at 11:41 AM Arkadiusz Miśkiewicz via pld-devel-en
wrote:
>
> On 31.08.2022 11:27, Jan Rękorajski wrote:
> > Where will it land now? If you want to protect against landing in
> > non-existing directory you can use '[ -d "$__PWD" ] && cd "$__PWD"'
> > I really prefer to be
On 31.08.2022 11:27, Jan Rękorajski wrote:
Where will it land now? If you want to protect against landing in
non-existing directory you can use '[ -d "$__PWD" ] && cd "$__PWD"'
I really prefer to be staying in the same directory where I launched
the script in.
Do you include (via source/dot)
On 31.08.2022 11:27, Jan Rękorajski wrote:
> Where will it land now? If you want to protect against landing in
> non-existing directory you can use '[ -d "$__PWD" ] && cd "$__PWD"'
> I really prefer to be staying in the same directory where I launched
> the script in.
I considered doing `test -d`
Where will it land now? If you want to protect against landing in
non-existing directory you can use '[ -d "$__PWD" ] && cd "$__PWD"'
I really prefer to be staying in the same directory where I launched
the script in.
On Wed, Aug 31, 2022 at 12:59 AM atler wrote:
>
> commit
On 16.08.2022 21:53, Jakub Bogusz wrote:
> On Tue, Aug 16, 2022 at 09:28:58PM +0200, Jan Palus wrote:
> > On 16.08.2022 20:31, Jakub Bogusz wrote:
> > > In glibc 2.36 build debuginfo extraction process removes .note.GNU-stack
> > > section:
> >
> > ...
> >
> > > For now only i686 builds are
On Tue, Aug 16, 2022 at 09:28:58PM +0200, Jan Palus wrote:
> On 16.08.2022 20:31, Jakub Bogusz wrote:
> > In glibc 2.36 build debuginfo extraction process removes .note.GNU-stack
> > section:
>
> ...
>
> > For now only i686 builds are affected because x86_64 and x32 glibc-devel
> > packages
> >
On 16.08.2022 20:31, Jakub Bogusz wrote:
> In glibc 2.36 build debuginfo extraction process removes .note.GNU-stack
> section:
...
> For now only i686 builds are affected because x86_64 and x32 glibc-devel
> packages
> haven't been updated on builders.
>
>
> Any guesses what changed?
I
On 08.08.2022 23:34, Jan Rękorajski wrote:
> On Mon, 08 Aug 2022, Jan Palus wrote:
>
> > On 08.08.2022 08:32, Jan Rękorajski wrote:
> > > On Fri, 22 Jul 2022, Jan Palus wrote:
> > >
> > > > On 22.07.2022 11:03, Jan Rękorajski wrote:
> > > > > Can someone explain why are we using split
On Mon, 08 Aug 2022, Jan Palus wrote:
> On 08.08.2022 08:32, Jan Rękorajski wrote:
> > On Fri, 22 Jul 2022, Jan Palus wrote:
> >
> > > On 22.07.2022 11:03, Jan Rękorajski wrote:
> > > > Can someone explain why are we using split sources/packages for Qt?
> > > >
> > > > I want to add Qt6 and
On 08.08.2022 08:32, Jan Rękorajski wrote:
> On Fri, 22 Jul 2022, Jan Palus wrote:
>
> > On 22.07.2022 11:03, Jan Rękorajski wrote:
> > > Can someone explain why are we using split sources/packages for Qt?
> > >
> > > I want to add Qt6 and building from the monolythic source is s much
> > >
On Mon, 08 Aug 2022, Neal Gompa wrote:
> On Mon, Aug 8, 2022 at 2:32 AM Jan Rękorajski wrote:
> >
> > On Fri, 22 Jul 2022, Jan Palus wrote:
> >
> > > On 22.07.2022 11:03, Jan Rękorajski wrote:
> > > > Can someone explain why are we using split sources/packages for Qt?
> > > >
> > > > I want to
On Mon, Aug 8, 2022 at 2:32 AM Jan Rękorajski wrote:
>
> On Fri, 22 Jul 2022, Jan Palus wrote:
>
> > On 22.07.2022 11:03, Jan Rękorajski wrote:
> > > Can someone explain why are we using split sources/packages for Qt?
> > >
> > > I want to add Qt6 and building from the monolythic source is s
On Fri, 22 Jul 2022, Jan Palus wrote:
> On 22.07.2022 11:03, Jan Rękorajski wrote:
> > Can someone explain why are we using split sources/packages for Qt?
> >
> > I want to add Qt6 and building from the monolythic source is s much
> > easier. No need for bootstrap, no intertwined build
On 22.07.2022 11:03, Jan Rękorajski wrote:
> Can someone explain why are we using split sources/packages for Qt?
>
> I want to add Qt6 and building from the monolythic source is s much
> easier. No need for bootstrap, no intertwined build dependencies, just
> configure -> build -> build docs
On 14.07.2022 16:38, Jakub Bogusz wrote:
> As more and more packages are getting bash/zsh completions, separate
> completions packages are becoming useless (harder to find, even not
> suggested).
>
> My proposal:
> 1) add %{bash_compdir}, %{zsh_compdir} and maybe %{fish_compdir} (and upper
>
On Thu, 14 Jul 2022, Jakub Bogusz wrote:
> As more and more packages are getting bash/zsh completions, separate
> completions packages are becoming useless (harder to find, even not
> suggested).
>
> My proposal:
> 1) add %{bash_compdir}, %{zsh_compdir} and maybe %{fish_compdir} (and upper
>
On 14.07.2022 16:38, Jakub Bogusz wrote:
As more and more packages are getting bash/zsh completions, separate
completions packages are becoming useless (harder to find, even not suggested).
My proposal:
1) add %{bash_compdir}, %{zsh_compdir} and maybe %{fish_compdir} (and upper
level) dirs to
My bad , I meant PLD English section
My mind is stuck with poldek so I wrote poldek by mistake
On Tue, Jul 12, 2022, 7:44 PM Saleem Ceann Khan Marwat
wrote:
> Sorry if I posted it in wrong place but I thought I posted it in poldek
> English section
>
> And strangely now there is no more kernel
Sorry if I posted it in wrong place but I thought I posted it in poldek
English section
And strangely now there is no more kernel 5.18 available on th , it has
disappeared from packages available for upgrade
So I'm currently on 5.17
Thanks
On Tue, Jul 12, 2022, 7:41 PM Jan Palus wrote:
> On
On 12.07.2022 19:26, Saleem Ceann Khan Marwat wrote:
> Thanks but that did not help either
>
> as can be seen from this log
> poldek:/all-avail> upgrade *
> error: kernel-5.18.5-1.x86_64: refusing to upgrade held package
> error: kernel-drm-5.18.5-1.x86_64: refusing to upgrade held package
>
On 12.07.2022 19:26, Saleem Ceann Khan Marwat wrote:
> Thanks but that did not help either
>
> as can be seen from this log
> poldek:/all-avail> upgrade *
> error: kernel-5.18.5-1.x86_64: refusing to upgrade held package
> error: kernel-drm-5.18.5-1.x86_64: refusing to upgrade held package
>
Thanks but that did not help either
as can be seen from this log
poldek:/all-avail> upgrade *
error: kernel-5.18.5-1.x86_64: refusing to upgrade held package
error: kernel-drm-5.18.5-1.x86_64: refusing to upgrade held package
error: kernel-headers-5.18.5-1.x86_64: refusing to upgrade held package
On Thu, Jul 7, 2022 at 7:46 PM Saleem Ceann Khan Marwat
wrote:
>
> Hello,
>
> I am having issue with kernel upgrade to 5.18 due to held packages
>
> I tried --nodeps --force but still can not upgrade any of the kernel
> related packages.
>
> How to fix this?
Use install instead of upgrade for
Dnia piątek, 1 lipca 2022 14:31:04 CEST Andrzej Zawadzki pisze:
> OK Qt5 was to fresh. I found in logs:
>
>
> *plasmashell[2012]: Cannot mix incompatible Qt library (5.15.4) with this
> library (5.15.5)*
>
> Hmm, rebuild is needed?
I did a full downgrade of Qt5 to 5.15.4 and it works - so yes,
On 01.07.2022 14:31, Andrzej Zawadzki wrote:
> OK Qt5 was to fresh. I found in logs:
>
>
> *plasmashell[2012]: Cannot mix incompatible Qt library (5.15.4) with this
> library (5.15.5)*
> Hmm, rebuild is needed?
`rpm -qa 'Qt5*' | grep -F 5.15.4` will likely be the reason. Needs
upgrade to 5.15.5
OK Qt5 was to fresh. I found in logs:
*plasmashell[2012]: Cannot mix incompatible Qt library (5.15.4) with this
library (5.15.5)*
Hmm, rebuild is needed?
On Fri, Jul 1, 2022 at 2:19 PM Łukasz Maśko wrote:
>From which version did you upgrade? Works without major problems for
>me.
>
From which version did you upgrade? Works without major problems for
me.
--
Pozdrawiam. �ukasz Ma�ko
1 lip 2022 14:04 Andrzej Zawadzki napisa�(a):
Hi!
My KDE is broken after upgrade (plasma-shell, basically useless).
How
this looks on yours computers?
On 29.06.2022 18:38, Elan Ruusamäe wrote:
> On 24.06.2022 11:42, arekm wrote:
>
>> commit 8b8822b9a17c06cd1d3f0b803e6a9830c962353e
>> Author: Arkadiusz Miśkiewicz
>> Date: Fri Jun 24 10:42:47 2022 +0200
>>
>> Rel 2; base on /etc/php directories since these always exist
>> (while binaries
On 24.06.2022 11:42, arekm wrote:
commit 8b8822b9a17c06cd1d3f0b803e6a9830c962353e
Author: Arkadiusz Miśkiewicz
Date: Fri Jun 24 10:42:47 2022 +0200
Rel 2; base on /etc/php directories since these always exist (while
binaries are optional)
yet /etc/phpXY may be just some *.rpmsave or
On Mon, 13 Jun 2022, Elan Ruusamäe wrote:
> On 12.06.2022 20:09, Jan Rękorajski wrote:
>
> > Please don't think about updating mongodb past 4.0.3, as any later
> > version uses very restrictive license that's risky and we don't
> > want it in PLD.
>
> i'm sure people have discovered docker for
On 12.06.2022 20:09, Jan Rękorajski wrote:
Please don't think about updating mongodb past 4.0.3, as any later
version uses very restrictive license that's risky and we don't
want it in PLD.
i'm sure people have discovered docker for deploying such servers.
please consider adding that license
Dnia 2022-06-12, o godz. 20:38:18
Jan Palus napisał(a):
> On 12.06.2022 11:09, mrozowik wrote:
> > commit 7b38363a6951facd5787b69e5afe2001cc3b6380
> > Author: Krzysztof Mrozowicz
> > Date: Sun Jun 12 09:09:12 2022 +
> >
> > - excluding x32
> >
> > ka5-messagelib.spec | 1 +
> > 1
On 12.06.2022 11:09, mrozowik wrote:
> commit 7b38363a6951facd5787b69e5afe2001cc3b6380
> Author: Krzysztof Mrozowicz
> Date: Sun Jun 12 09:09:12 2022 +
>
> - excluding x32
>
> ka5-messagelib.spec | 1 +
> 1 file changed, 1 insertion(+)
> ---
> diff --git a/ka5-messagelib.spec
1 - 100 of 6904 matches
Mail list logo