[Fuego] [Bug] bsd-mailx package has been removed from Debian repository

[Fuego] [Bug] bsd-mailx package has been removed from Debian repository

[Hoang Van Tuyen]

[-- Attachment #1.1: Type: text/plain, Size: 2433 bytes --]

Hello all,

Recently, I have pulled the newest source code of fuego and fuego-core 
repositories (master branch).

I have run the ./install script from fuego folder.

I have got the below issue.

/Get:458 http://httpredir.debian.org/debian/ jessie/main u-boot-tools 
amd64 2014.10+dfsg1-5 [80.4 kB]//
//Get:459 http://httpredir.debian.org/debian/ jessie/main unzip amd64 
6.0-16+deb8u3 [162 kB]//
//Get:460 http://httpredir.debian.org/debian/ jessie/main vim-runtime 
all 2:7.4.488-7+deb8u3 [5048 kB]//
//Get:461 http://httpredir.debian.org/debian/ jessie/main vim amd64 
2:7.4.488-7+deb8u3 [953 kB]//
//Get:462 http://httpredir.debian.org/debian/ jessie/main xauth amd64 
1:1.0.9-1 [38.2 kB]//
//Get:463 http://httpredir.debian.org/debian/ jessie/main xdg-user-dirs 
amd64 0.15-2 [52.1 kB]//
//Get:464 http://httpredir.debian.org/debian/ jessie/main xml-core all 
0.13+nmu2 [24.2 kB]//
//Get:465 http://httpredir.debian.org/debian/ jessie/main xmlstarlet 
amd64 1.6.1-1 [280 kB]//
//Get:466 http://httpredir.debian.org/debian/ jessie/main netcat all 
1.10-41 [8962 B]//
//Get:467 http://httpredir.debian.org/debian/ jessie/main sshpass amd64 
1.05-1 [11.2 kB]//
//E: Failed to fetch 
http://httpredir.debian.org/debian/pool/main/b/bsd-mailx/bsd-mailx_8.1.2-0.20141216cvs-2_amd64.deb 
403  Forbidden//
//
//E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?//
//Fetched 244 MB in 7min 9s (568 kB/s)//
//The command '/bin/sh -c DEBIAN_FRONTEND=noninteractive apt-get update 
&& apt-get -yV install    apt-utils daemon gcc make cmake 
python-paramiko python-lxml python-simplejson   python-matplotlib 
python-serial python-yaml python-openpyxl python-requests     
python-reportlab libtool xmlstarlet autoconf automake rsync 
openjdk-7-jre openjdk-7-jdk         iperf netperf netpipe-tcp sshpass 
wget git diffstat sudo net-tools vim curl     inotify-tools g++ bzip2 bc 
libaio-dev gettext pkg-config libglib2.0-dev         time python-pip 
python-xmltodict at minicom lzop bsdmainutils u-boot-tools      mc 
netcat lava-tool openssh-server python-parsedatetime         
libsdl1.2-dev libcairo2-dev libxmu-dev libxmuu-dev iperf3' returned a 
non-zero code: 100/


When We install */at/* package, it depends on several other packages and 
the end, it requires /bsd-mailx/ package.
I see that the /bsd-mailx /package is not available from Mar 23.
Does anyone get the same issue?

Best regards,
Tuyen


[-- Attachment #1.2: Type: text/html, Size: 4191 bytes --]

[-- Attachment #2: Bitdefender.txt --]
[-- Type: text/plain, Size: 102 bytes --]

-- 
This mail was scanned by BitDefender
For more information please visit http://www.bitdefender.com

Re: [Fuego] [Bug] bsd-mailx package has been removed from Debian repository

[Tim.Bird]

> -----Original Message-----
> From: Hoang Van Tuyen
> 
> Recently, I have pulled the newest source code of fuego and fuego-core
> repositories (master branch).
> 
> I have run the ./install script from fuego folder.
> 
> I have got the below issue.
> 
> Get:458 http://httpredir.debian.org/debian/ jessie/main u-boot-tools amd64
> 2014.10+dfsg1-5 [80.4 kB]
> Get:459 http://httpredir.debian.org/debian/ jessie/main unzip amd64 6.0-
> 16+deb8u3 [162 kB]
> Get:460 http://httpredir.debian.org/debian/ jessie/main vim-runtime all
> 2:7.4.488-7+deb8u3 [5048 kB]
> Get:461 http://httpredir.debian.org/debian/ jessie/main vim amd64
> 2:7.4.488-7+deb8u3 [953 kB]
> Get:462 http://httpredir.debian.org/debian/ jessie/main xauth amd64
> 1:1.0.9-1 [38.2 kB]
> Get:463 http://httpredir.debian.org/debian/ jessie/main xdg-user-dirs
> amd64 0.15-2 [52.1 kB]
> Get:464 http://httpredir.debian.org/debian/ jessie/main xml-core all
> 0.13+nmu2 [24.2 kB]
> Get:465 http://httpredir.debian.org/debian/ jessie/main xmlstarlet amd64
> 1.6.1-1 [280 kB]
> Get:466 http://httpredir.debian.org/debian/ jessie/main netcat all 1.10-41
> [8962 B]
> Get:467 http://httpredir.debian.org/debian/ jessie/main sshpass amd64
> 1.05-1 [11.2 kB]
> E: Failed to fetch http://httpredir.debian.org/debian/pool/main/b/bsd-
> mailx/bsd-mailx_8.1.2-0.20141216cvs-2_amd64.deb  403  Forbidden
> 
> E: Unable to fetch some archives, maybe run apt-get update or try with --fix-
> missing?
> Fetched 244 MB in 7min 9s (568 kB/s)
> The command '/bin/sh -c DEBIAN_FRONTEND=noninteractive apt-get update
> && apt-get -yV install    apt-utils daemon gcc make cmake python-paramiko
> python-lxml python-simplejson   python-matplotlib python-serial python-
> yaml python-openpyxl python-requests     python-reportlab libtool xmlstarlet
> autoconf automake rsync openjdk-7-jre openjdk-7-jdk         iperf netperf
> netpipe-tcp sshpass wget git diffstat sudo net-tools vim curl     inotify-tools
> g++ bzip2 bc libaio-dev gettext pkg-config libglib2.0-dev         time python-pip
> python-xmltodict at minicom lzop bsdmainutils u-boot-tools      mc netcat
> lava-tool openssh-server python-parsedatetime         libsdl1.2-dev libcairo2-
> dev libxmu-dev libxmuu-dev iperf3' returned a non-zero code: 100
> 
> 
> 
> When We install at package, it depends on several other packages and the
> end, it requires bsd-mailx package.
> I see that the bsd-mailx package is not available from Mar 23.
> Does anyone get the same issue?

I haven't seen this, but it looks like I'm using my docker cache to build images.
This means I might not be seeing effects of upstream changes.

I'm going to try to bypass the cache, and try to reproduce this.

But in the meantime, can I ask a few questions to clarify the problem?

Is it the 'at' package that depends on bsd-mailx? I don't see it in the list for the
Fuego apt-get.  If it's not 'at', do we know which fuego-desired package depends
on bsd-mailx?

Does anyone know of a way to break a dependency with apt-get?
Can we just omit 'at' (or which package is requiring bsd-mailx' from the main list
and load it separately with 'apt-get --no-deps install <problem-package>'?

Isn't this a big problem upstream?  If upstream is changing and has broken
package dependencies, should we report this and see if there's a fix in
progress?

 -- Tim

Re: [Fuego] [Bug] bsd-mailx package has been removed from Debian repository

[Tim.Bird]

> -----Original Message-----
> From: Hoang Van Tuyen
> I have got the below issue.
> 
...
> E: Failed to fetch http://httpredir.debian.org/debian/pool/main/b/bsd-
> mailx/bsd-mailx_8.1.2-0.20141216cvs-2_amd64.deb  403  Forbidden
> 
> E: Unable to fetch some archives, maybe run apt-get update or try with --fix-
> missing?

I just tried it, without using my docker cache, and it loaded bsd-mailx OK.
I think this may just have been httpredir.debian.org being flaky.

Can you try again?

The profusion devs mentioned that httpredir.debian.org is flaky and have
replaced it in their work with a different repository.  Hopefull, when we adopt
their Dockerfile, we'll get less flaky behavior for the docker image build
(or actually no builds at all, if things work out.)
 -- Tim

Re: [Fuego] [Bug] bsd-mailx package has been removed from Debian repository

[Daniel Sangorrin]

Hi Tim,

What do you think about providing signed docker images in the docker hub registry for users that
don't want to go through the process of building their own images?

Thanks,
Daniel

> -----Original Message-----
> From: fuego-bounces@lists.linuxfoundation.org [mailto:fuego-bounces@lists.linuxfoundation.org] On Behalf Of Tim.Bird@sony.com
> Sent: Wednesday, March 28, 2018 3:03 AM
> To: tuyen.hoangvan@toshiba-tsdv.com; fuego@lists.linuxfoundation.org
> Subject: Re: [Fuego] [Bug] bsd-mailx package has been removed from Debian repository
> 
> 
> 
> > -----Original Message-----
> > From: Hoang Van Tuyen
> > I have got the below issue.
> >
> ...
> > E: Failed to fetch http://httpredir.debian.org/debian/pool/main/b/bsd-
> > mailx/bsd-mailx_8.1.2-0.20141216cvs-2_amd64.deb  403  Forbidden
> >
> > E: Unable to fetch some archives, maybe run apt-get update or try with --fix-
> > missing?
> 
> I just tried it, without using my docker cache, and it loaded bsd-mailx OK.
> I think this may just have been httpredir.debian.org being flaky.
> 
> Can you try again?
> 
> The profusion devs mentioned that httpredir.debian.org is flaky and have
> replaced it in their work with a different repository.  Hopefull, when we adopt
> their Dockerfile, we'll get less flaky behavior for the docker image build
> (or actually no builds at all, if things work out.)
>  -- Tim
> 
> _______________________________________________
> Fuego mailing list
> Fuego@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/fuego

Re: [Fuego] [Bug] bsd-mailx package has been removed from Debian repository

[Hoang Van Tuyen]

[-- Attachment #1.1: Type: text/plain, Size: 2742 bytes --]

Hello Tim,

On 3/28/2018 12:39 AM, Tim.Bird@sony.com wrote:
> I haven't seen this, but it looks like I'm using my docker cache to build images.
> This means I might not be seeing effects of upstream changes.
>
> I'm going to try to bypass the cache, and try to reproduce this.
>
> But in the meantime, can I ask a few questions to clarify the problem?
>
> Is it the 'at' package that depends on bsd-mailx? I don't see it in the list for the
> Fuego apt-get.  If it's not 'at', do we know which fuego-desired package depends
> on bsd-mailx?
The /at/ package recommends /exim4-daemon-light/ package, 
/exim4-daemon-light/ depends on /exim-base/
and /exim4-base/ suggests/bsd-mailx.
/On my side, I have used option /--no-install-recommends/ for installing 
the /at/ package as a workaround.
It looks like:

/RUN if [ -n "$HTTP_PROXY" ]; then echo 'Acquire::http::proxy 
"'$HTTP_PROXY'";' > /etc/apt/apt.conf.d/80proxy; fi//
/*/RUN DEBIAN_FRONTEND=noninteractive apt-get update && apt-get -yV 
install --no-install-recommends at psmisc/*/
//RUN DEBIAN_FRONTEND=noninteractive apt-get update && apt-get -yV 
install \//
//        apt-utils daemon gcc make cmake python-paramiko python-lxml 
python-simplejson \//
//        python-matplotlib python-serial python-yaml python-openpyxl 
python-requests \//
//        python-reportlab libtool xmlstarlet autoconf automake rsync 
openjdk-7-jre openjdk-7-jdk \//
//        iperf netperf netpipe-tcp sshpass wget git diffstat sudo 
net-tools vim curl \//
//        inotify-tools g++ bzip2 bc libaio-dev gettext pkg-config 
libglib2.0-dev \//
//        time python-pip python-xmltodict at minicom lzop bsdmainutils 
u-boot-tools \//
//        mc netcat lava-tool openssh-server python-parsedatetime \//
//        libsdl1.2-dev libcairo2-dev libxmu-dev libxmuu-dev iperf3//
///
I have added installing the /psmisc/ package which Jenkins depends on.
Before, /psmisc/ was installed when we installed /at.

Best regards,
Tuyen
/
>
> Does anyone know of a way to break a dependency with apt-get?
> Can we just omit 'at' (or which package is requiring bsd-mailx' from the main list
> and load it separately with 'apt-get --no-deps install <problem-package>'?
>
> Isn't this a big problem upstream?  If upstream is changing and has broken
> package dependencies, should we report this and see if there's a fix in
> progress?

-- 
================================================================
Hoang Van Tuyen (Mr.)
TOSHIBA SOFTWARE DEVELOPMENT (VIETNAM) CO., LTD.
16th Floor, VIT Building, 519 Kim Ma Str., Ba Dinh Dist., Hanoi, Vietnam
Tel: 84-4-22208801 (Company) - Ext.251
Fax: 84-4-22208802 (Company)
Email: tuyen.hoangvan@toshiba-tsdv.com
================================================================


[-- Attachment #1.2: Type: text/html, Size: 3976 bytes --]

[-- Attachment #2: Bitdefender.txt --]
[-- Type: text/plain, Size: 102 bytes --]

-- 
This mail was scanned by BitDefender
For more information please visit http://www.bitdefender.com