Re: Error when make w3m package
Thank you for the clarification. Athos Ribeiro 於 2022年11月28日 週一，上午8:29寫道： > On Thu, Nov 24, 2022 at 03:47:45PM +0800, River Chiang wrote: > >Hello list, > > Hi, > > > > >I tried to make w3m from the source ( > https://packages.ubuntu.com/jammy/w3m > >) but got some errors. Please refer to the following error messages. Could > >something be wrong? > > I can successfully build the package from sources through dpkg (i.e., > the package is not failing to build from sources at the moment). > > From your logs, it seems you are not properly linking the package with > the libs it depends on. If you want to compile the sources without using > the packaging tooling, please, refer to the upstream docs under docs/*. > > debian/control may help you figuire out what packages you want to > install as build dependencies and debian/rules may help you > understanding how the deb package is compiled. > > >(cd libwc && make CC='gcc' OPTS='') > >make[1]: Entering directory > '/home/user/src/w3m/w3m-0.5.3+git20210102/libwc' > >make[1]: Nothing to be done for 'all'. > >make[1]: Leaving directory > '/home/user/src/w3m/w3m-0.5.3+git20210102/libwc' > >gcc -I. -I. -g -O2 -I./libwc -DHAVE_CONFIG_H > >-DAUXBIN_DIR=\"/home/user/app/w3m/libexec/w3m\" > >-DCGIBIN_DIR=\"/home/user/app/w3m/libexec/w3m/cgi-bin\" > >-DHELP_DIR=\"/home/user/app/w3m/share/w3m\" > >-DETC_DIR=\"/home/user/app/w3m/etc\" > >-DCONF_DIR=\"/home/user/app/w3m/etc/w3m\" -DRC_DIR=\"~/.w3m\" > >-DLOCALEDIR=\"/home/user/app/w3m/share/locale\" -o w3m main.o file.o > >buffer.o display.o etc.o search.o linein.o table.o local.o form.o map.o > >frame.o rc.o menu.o mailcap.o image.o symbol.o entity.o terms.o url.o > ftp.o > >mimehead.o regex.o news.o func.o cookie.o history.o backend.o keybind.o > >anchor.o parsetagx.o tagtable.o istream.o version.o -lm -L. -lindep > -lgc > >-L./libwc -lwc > >/usr/bin/ld: terms.o: in function `put_image_osc5379': > >/home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:482: undefined reference > >to `tgoto' > >/usr/bin/ld: terms.o: in function `writestr': > >/home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:465: undefined reference > >to `tputs' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:465: > >undefined reference to `tputs' > >/usr/bin/ld: terms.o: in function `put_image_osc5379': > >/home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:485: undefined reference > >to `tgoto' > >/usr/bin/ld: terms.o: in function `writestr': > >/home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:465: undefined reference > >to `tputs' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:465: > >undefined reference to `tputs' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:465: > >undefined reference to `tputs' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:465: > >undefined reference to `tputs' > >/usr/bin/ld: terms.o: in function `put_image_sixel': > >/home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:590: undefined reference > >to `tgoto' > >/usr/bin/ld: terms.o: in function `writestr': > >/home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:465: undefined reference > >to `tputs' > >/usr/bin/ld: terms.o: in function `put_image_sixel': > >/home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:667: undefined reference > >to `tgoto' > >/usr/bin/ld: terms.o: in function `writestr': > >/home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:465: undefined reference > >to `tputs' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:465: > >undefined reference to `tputs' > >/usr/bin/ld: terms.o: in function `setlinescols': > >/home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:1083: undefined reference > >to `tgetnum' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:1085: > >undefined reference to `tgetnum' > >/usr/bin/ld: terms.o: in function `getTCstr': > >/home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:987: undefined reference > >to `tgetent' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:994: > >undefined reference to `tgetstr' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:995: > >undefined reference to `tgetstr' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:996: > >undefined reference to `tgetstr' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:999: > >undefined reference to `tgetflag' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:1008: > >undefined reference to `tgetstr' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:1009: > >undefined reference to `tgetstr' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:1010: > >undefined reference to `tgetstr' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:1011: > >undefined reference to `tgetstr' > >/usr/bin/ld: /home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:1012: > >undefined reference to `tgetstr' > >/usr/bin/ld: > terms.o:/home/user/src/w3m/w3m-0.5.3+git20210102/terms.c:1013: > >more undefined references to
Re: Extended call for Ubuntu Technical Board candidates
On Tue, Nov 29, 2022 at 07:07:26PM +, Torsten Franz wrote: > In > order to make a good decision in this selection, we would like to give the > candidates the opportunity to introduce themselves here and to say a few > words about their application and provide a few links to their work. Hi, I'm Robie. I've been using GNU/Linux since the late nineties, professionally as a sysadmin since 2001, Ubuntu as a power user/developer since about 2005, and have been working on Ubuntu itself since I joined Canonical in 2011. My first sponsored upload to Ubuntu was in 2011, I became an uploader in 2013, and a Core Dev in 2014. I've served on the DMB and SRU teams since 2016, and the Technical Board for this past two year term. I'm also a Debian Developer since 2018. Since I'm an incumbent I thought I'd try to give you an idea of some of the proactive things I've done in my time on the Technical Board, and you can decide if you want more of the same, or a change. I believe the best way to make progress is to build consensus and negotiate rather than to force things with a Technical Board hat, *except when decisiveness is actually required*. An example of where I think this worked well is in the resurrection of the backports pocket. I started this thread[1], found volunteers and built consensus that turned out quite different from my original proposal[2], we negotiated in the thread with previous team members on the details of how to hand the team over, and thanks to our excellent new volunteer backports maintainers we have a functional backports pocket again. Crucially, at no point did I need my Technical Board hat to force anything. Eventually all I did as a TB member was to implement some ACL changes on which we had consensus first. I think this is a shining example of how the Technical Board ought to operate most of the time: we get to a point where all the stakeholders are agreed, and then any required TB approval becomes a fait accompli rather than something that must be contentious. Along the same lines of building consensus, my biggest piece of work in my time on the Technical Board has been what we're currently calling "third party repository requirements". From before my time on the TB, Ubuntu's policy on quality requirements for snaps that we ship by "default" has been in a draft state[3], even though seeded and other types of default snaps have already shipped. I've been driving the work on finishing this properly. In doing so we found that there is value in defining general principles that we want to uphold and document, in order to help with setting user expectations on what they can expect from Ubuntu in this area. This meant it ended up encompassing packaging systems and user expectations of them generally, and not just for snaps. Since this is being done retroactively it has been much harder to negotiate - mostly in terms of time taken to make sure all stakeholders' views and concerns are incorporated, rather than any particular pushback. And there are things we identified that are what we think are shortcomings in the current snap UX that we'd like to see addressed; these needed negotiating with snap infrastructure upstreams first! For this reason I've been focusing on conversations with stakeholders directly, although discussion has generally been available to follow to anyone following TB meetings. I managed to resolve the remaining blockers directly with stakeholders in-person in Prague, but haven't managed to catch this up in the draft yet. I hope to do this very soon, and then consult more directly with the entire set of Ubuntu developers, with a view to getting TB approval in the next few months. I mention this because the "diplomacy" to get to the point of the stakeholder consensus that I've achieved this far is something that I'm proud of as an example of my proactive Technical Board work, even though I've unfortunately fallen short by just a week or two in terms of sharing it all more directly before this election. I think you would be pleased with the result so far, but it is probably inappropriate to push this further this instant just because the TB election is on. It would be disappointing for me if I had to step down without having pushed this over the line, but I'd be happy to hand it over to the new TB if I am not re-elected. When I stood for this past term, I said that I wanted better communication on decisions and goings-on in Ubuntu. I think I've been achieving that - usually by asking behind the scenes for things to be documented, which has often been followed by a public post. I think we're doing a little bit better now, but there's still plenty of room for improvement. On attendance: from a quick tally, by my count there were 52 Technical Board meetings in this last term to date. I attended 84%, with absences generally only for collisions with vacations or Canonical company events. The other
Re: Extended call for Ubuntu Technical Board candidates
Hey there! I'm Sebastien Bacher, member of the Ubuntu Desktop Team and working for Canonical since 2004. I'm also an Ubuntu Archive members since 2007 and joined the DMB this year. I do care about Ubuntu as a project, and not only the desktop part, which is why I try to help things moving by being active on the dev channels (IRC, lists, discourse), sponsor uploads (to Ubuntu and to Debian), keep an eye on launchpad reports to direct reporters to the right place and toward a resolution of the issues if possible, try to lower our packages delta with Debian, etc. I'm also trying to push for us to communicate better and it a way which is accessible to everyone. I've been around for long time and I think I know Ubuntu, our community and our upstreams well enough to represent the project interests as a member of the board. I would like to help ensuring that the project keeps being welcoming and interesting to everyone by providing the right infrastructure and processes and by helping us to set the right technical decisions. Cheers, Sebastien Bacher Le 29/11/2022 à 20:07, Torsten Franz a écrit : Hi everyone, We have received some applications for the new election of the Ubuntu Technical Board. A lot of great applications from very good candidates. In order to make a good decision in this selection, we would like to give the candidates the opportunity to introduce themselves here and to say a few words about their application and provide a few links to their work. Everyone will also have the opportunity to ask the candidates questions. We will start the election on 6 December. All five seats (besides Mark) will be filled. Here is the list of candidates (by alphabetical order of surname): - Sebastien Bacher - Robie Basak - Ben Collins - Steve Langasek - Lukas Märdian - Alex Murray - Simon Quigley - Mathieu Trudel-Lapierre - Łukasz Zemczak If any questions arise, then the Ubuntu Community Council is available to help. On behalf of the Ubuntu Community Council, Torsten Franz Am 22.11.2022 22:51 schrieb Merlijn Sebrechts: WE ARE STILL LOOKING FOR CANDIDATES TO JOIN THE UBUNTU TECHNICAL BOARD! The call remains open until NOVEMBER 27TH, 2022, at 23:59 UTC. This is a bit longer than initially anticipated. Are you interested or do you know of someone who you want to see in this role? Please submit the nomination. WHAT IS THE UBUNTU TECHNICAL BOARD? The Ubuntu Technical Board is responsible for the technical direction of Ubuntu. It makes decisions on package selection, packaging policy, installation systems and processes, kernel, X server, display management, library versions, and dependencies. The board works with relevant teams to establish a consensus on the right path to take, especially where diverse elements of Ubuntu cannot find consensus on shared components. The current Technical Board is expiring at the end of the year, and the Community Council would like to confirm a new Technical Board, consisting of five people, who will serve for two years. The eligibility requirements are: WHO IS ELIGIBLE? Everyone who meets the following criteria: * Be an Ubuntu Core Developer * Be available during typical meeting hours [see https://wiki.ubuntu.com/TechnicalBoardAgenda [1]] * Have insight into the Ubuntu Development process, architecture, and technical culture HOW DO YOU NOMINATE YOURSELF OR SOMEONE ELSE? Send the Community Council an email (community-council AT lists.ubuntu.com [2]). With your nomination. Note that you can nominate yourself too! HOW DOES THE ELECTION WORK? The call remains open until November 27th, 2022, at 23:59 UTC. After that, the Community Council will review the submissions, submit them to Mark Shuttleworth for shortlisting, and proceed with a vote by the Ubuntu Development team. Links: -- [1] https://wiki.ubuntu.com/TechnicalBoardAgenda [2] http://lists.ubuntu.com -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: MOTU application: Frank Heimes (continuation)
Many thx Utkarsh - and the entire DMB ! On Thu, Dec 1, 2022 at 9:36 AM Utkarsh Gupta wrote: > Hello, > > On Thu, Aug 25, 2022 at 1:20 AM Frank Heimes > wrote: > > Dear DMB, > > I would like to continue my MOTU application on Mo Sept the 5th. > > At the last meeting (2022-07-25) we were late and didn't had enough time > to finish. > > > > I've also added myself to the next DMB agenda. > > After some back and forth and finally voting via the mailing list (due > to lack of quorum during the meeting), DMB voted in Frank's favor and > thus we'd like to welcome Frank to the MOTU family. Congratulations > and welcome aboard. :) > > > Utkarsh, > On behalf of DMB > -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: MOTU application: Frank Heimes (continuation)
Hello, On Thu, Aug 25, 2022 at 1:20 AM Frank Heimes wrote: > Dear DMB, > I would like to continue my MOTU application on Mo Sept the 5th. > At the last meeting (2022-07-25) we were late and didn't had enough time to > finish. > > I've also added myself to the next DMB agenda. After some back and forth and finally voting via the mailing list (due to lack of quorum during the meeting), DMB voted in Frank's favor and thus we'd like to welcome Frank to the MOTU family. Congratulations and welcome aboard. :) Utkarsh, On behalf of DMB -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
