Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.rc > #307246 > unrolled thread

Bug#997713: pushpin: FTBFS: error: failed to select a version for the requirement `base64 = "^0.12"`

Started byLucas Nussbaum <lucas@debian.org>
First post2021-10-24 14:40 +0200
Last post2021-11-03 00:00 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.debian.bugs.rc


Contents

  Bug#997713: pushpin: FTBFS: error: failed to select a version for the requirement `base64 = "^0.12"` Lucas Nussbaum <lucas@debian.org> - 2021-10-24 14:40 +0200
    Bug#997713: marked as done (pushpin: FTBFS: error: failed to  select a version for the requirement `base64 = "^0.12"`) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-11-03 00:00 +0100

#307246 — Bug#997713: pushpin: FTBFS: error: failed to select a version for the requirement `base64 = "^0.12"`

FromLucas Nussbaum <lucas@debian.org>
Date2021-10-24 14:40 +0200
SubjectBug#997713: pushpin: FTBFS: error: failed to select a version for the requirement `base64 = "^0.12"`
Message-ID<DbKXe-1mk-129@gated-at.bofh.it>
Source: pushpin
Version: 1.32.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> ./configure --prefix=/usr --qtselect=5 --configdir=/etc --extraconf="$QMAKE_BUILDFLAGS" --verbose
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead.
> Configuring Pushpin ...
> 
> PREFIX=/usr
> BINDIR=/usr/bin
> EX_QTDIR=
> QC_EXTRACONF=QMAKE_CPPFLAGS *= -Wdate-time -D_FORTIFY_SOURCE=2 QMAKE_CFLAGS *= -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 QMAKE_CXXFLAGS *= -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 QMAKE_LFLAGS *= -Wl,-z,relro -Wl,-z,now -Wl,--as-needed
> QC_LIBDIR=
> QC_CONFIGDIR=/etc
> QC_RUNDIR=
> QC_LOGDIR=
> QC_DISABLE_cargo=
> QC_DEFAULT_ENABLE_cargo=
> 
> Verifying Qt build environment ... 
> running: /usr/bin/qtchooser -run-tool=qmake -qt=5 -query QT_INSTALL_BINS
> running: "/usr/lib/qt5/bin/qmake" -query QT_VERSION
> qmake found in /usr/lib/qt5/bin/qmake
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead.
> makespec is
>  -> ok
> conf command: [./configure]
> conf path:    [./configure]
> srcdir:       [/<<PKGBUILDDIR>>]
> builddir:     [/<<PKGBUILDDIR>>]
> profile:      [/<<PKGBUILDDIR>>/pushpin.pro]
> qmake path:   [/usr/lib/qt5/bin/qmake]
> qmakespec:    []
> make tool:    [/usr/bin/gmake]
> 
> Checking for Qt >= 5.2.0 ... yes
> 
>  * extra += APP_VERSION = 1.32.2
>  * extra += LIBDIR = /usr/lib/pushpin
>  * extra += CONFIGDIR = /etc/pushpin
>  * extra += RUNDIR = /var/run/pushpin
>  * extra += LOGDIR = /var/log/pushpin
>  * INCLUDEPATH += $$PWD/src
>  * DEFINES += HAVE_CONFIG
> Checking for libzmq >= 2.0 ...
>  * [pkg-config libzmq --exists]
>  * returned: 0
>  * [pkg-config libzmq --atleast-version=2.0]
>  * returned: 0
>  * [pkg-config libzmq --modversion]
> 4.3.4
>  * returned: 0
>  * [pkg-config libzmq --libs]
> -lzmq
>  * returned: 0
>  * [pkg-config libzmq --cflags]
> -isystem /usr/include/mit-krb5 -I/usr/include/pgm-5.3 -I/usr/include/libxml2
>  * returned: 0
>  * INCLUDEPATH += /usr/include/pgm-5.3
>  * INCLUDEPATH += /usr/include/libxml2
>  * LIBS += -lzmq
>  -> yes
> Checking for cargo >= 1.34.0 ...
>  * [cargo version]
> cargo 1.46.0
>  * returned: 0
>  * extra += CONFIG += use_cargo
>  -> yes
> Info: creating stash file /<<PKGBUILDDIR>>/.qmake.stash
> 
> Good, your configure finished.  Now run /usr/bin/gmake.
> 
> echo "CONFIG += debug" >>conf.pri
> # Upstream Cargo.lock contains versions not valid for debian
> rm Cargo.lock
> # Upstream config.toml references vendored dependencies not part of the debian package
> rm .cargo/config.toml
> cargo update
> error: failed to select a version for the requirement `base64 = "^0.12"`
> candidate versions found which didn't match: 0.13.0
> location searched: directory source `/usr/share/cargo/registry` (which is replacing registry `https://github.com/rust-lang/crates.io-index`)
> required by package `pushpin v1.32.2 (/<<PKGBUILDDIR>>)`
> perhaps a crate was updated and forgotten to be re-vendored?
> make[1]: *** [debian/rules:37: override_dh_auto_configure] Error 101


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pushpin_1.32.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

[toc] | [next] | [standalone]


#308150 — Bug#997713: marked as done (pushpin: FTBFS: error: failed to select a version for the requirement `base64 = "^0.12"`)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2021-11-03 00:00 +0100
SubjectBug#997713: marked as done (pushpin: FTBFS: error: failed to select a version for the requirement `base64 = "^0.12"`)
Message-ID<DfaV4-7Ym-5@gated-at.bofh.it>
In reply to#307246

[Multipart message — attachments visible in raw view] — view raw

Your message dated Tue, 02 Nov 2021 22:49:19 +0000
with message-id <E1mi2al-0000mq-15@fasolo.debian.org>
and subject line Bug#997713: fixed in pushpin 1.32.2-2
has caused the Debian Bug report #997713,
regarding pushpin: FTBFS: error: failed to select a version for the requirement `base64 = "^0.12"`
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
997713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997713
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.rc


csiph-web