Page MenuHomeFreeBSD

net-im/linux-telegram-desktop: Update from 1.1.7 to 1.1.23
ClosedPublic

Authored by joneum on Aug 9 2017, 11:16 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Jun 19, 4:39 PM
Unknown Object (File)
May 21 2024, 7:24 PM
Unknown Object (File)
Apr 29 2024, 4:37 AM
Unknown Object (File)
Apr 19 2024, 12:33 PM
Unknown Object (File)
Apr 14 2024, 2:35 AM
Unknown Object (File)
Apr 13 2024, 10:40 PM
Unknown Object (File)
Apr 13 2024, 9:17 PM
Unknown Object (File)
Apr 13 2024, 7:24 PM
Subscribers

Details

Summary

PR: 220758
Reported by: tm+freebsd@core.io
Approved by: Henry Su <henry.su@gmail.com> (maintainer)
Approved by: xxx (mentor)
#Differential Revision: https://reviews.freebsd.org/Dxxxxx

Test Plan

~/dev/ports/net-im/linux-telegram-desktop % portlint -AC
WARN: Makefile: for new port, make $FreeBSD$ tag in comment section empty, to make SVN happy.
WARN: Makefile: using hyphen in PORTNAME. consider using PKGNAMEPREFIX and/or PKGNAMESUFFIX.
0 fatal errors and 2 warnings found.

poudriere testport:

10.3-amd64
10.3-i386
11.1-amd64
11.1-i386
12.0-CURRENT r321899 amd64
12.0-CURRENT r321913 i386

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Hmm, does these messages mean that the port does not run on 10.3?

> Registering installation for linux-telegram-desktop-1.1.19

(linux-telegram-desktop-1.1.19) /wrkdirs/usr/ports/net-im/linux-telegram-desktop/work/stageusr/local/lib/telegram-desktop/Telegram - required shared library libxcb.so.1 not found
(linux-telegram-desktop-1.1.19) /wrkdirs/usr/ports/net-im/linux-telegram-desktop/work/stage
usr/local/lib/telegram-desktop/Telegram - required shared library libX11.so.6 not found
(linux-telegram-desktop-1.1.19) /wrkdirs/usr/ports/net-im/linux-telegram-desktop/work/stageusr/local/lib/telegram-desktop/Telegram - required shared library libX11-xcb.so.1 not found
(linux-telegram-desktop-1.1.19) /wrkdirs/usr/ports/net-im/linux-telegram-desktop/work/stage
usr/local/lib/telegram-desktop/Telegram - required shared library libdbus-1.so.3 not found
(linux-telegram-desktop-1.1.19) /wrkdirs/usr/ports/net-im/linux-telegram-desktop/work/stageusr/local/lib/telegram-desktop/Telegram - required shared library libdl.so.2 not found
(linux-telegram-desktop-1.1.19) /wrkdirs/usr/ports/net-im/linux-telegram-desktop/work/stage
usr/local/lib/telegram-desktop/Telegram - required shared library libglib-2.0.so.0 not found
(linux-telegram-desktop-1.1.19) /wrkdirs/usr/ports/net-im/linux-telegram-desktop/work/stageusr/local/lib/telegram-desktop/Telegram - required shared library libpthread.so.0 not found
(linux-telegram-desktop-1.1.19) /wrkdirs/usr/ports/net-im/linux-telegram-desktop/work/stage
usr/local/lib/telegram-desktop/Telegram - required shared library libm.so.6 not found
(linux-telegram-desktop-1.1.19) /wrkdirs/usr/ports/net-im/linux-telegram-desktop/work/stageusr/local/lib/telegram-desktop/Telegram - required shared library libc.so.6 not found
(linux-telegram-desktop-1.1.19) /wrkdirs/usr/ports/net-im/linux-telegram-desktop/work/stage
usr/local/lib/telegram-desktop/Telegram - required shared library ld-linux.so.2 not found

In D11940#248810, @rene wrote:

Hmm, does these messages mean that the port does not run on 10.3?

Hey Rene,
i will check it with VirtualBox and FreeBSD 10.3 amd64.

In D11940#250624, @miwi wrote:

Any update?

currently not. I have informed the maintainer and are waiting for a feedback.
10.3 does not build. Either fix or mark as broken for 10.3.

tz requested changes to this revision.Sep 7 2017, 10:55 AM

I change the status of the review to make clear, that changes are needed

This revision now requires changes to proceed.Sep 7 2017, 10:55 AM
joneum retitled this revision from net-im/linux-telegram-desktop: Update from 1.1.7 to 1.1.19 to net-im/linux-telegram-desktop: Update from 1.1.7 to 1.1.23.Sep 30 2017, 8:13 AM
joneum edited the summary of this revision. (Show Details)
joneum edited the test plan for this revision. (Show Details)
net-im/linux-telegram-desktop/Makefile
19 ↗(On Diff #33581)

This happens too late.

Also, why += ?

without the + then its fine.

This revision was automatically updated to reflect the committed changes.